Feature Requests

Problem: Teams store Docs-as-Code in .adoc files. In Harness CODE, AsciiDoc files show as raw text; there’s no rendered preview. Gap: CODE’s repo viewer/PR UI doesn’t natively render AsciiDoc, creating friction for reviews and onboarding, and lacking parity with platforms like GitLab. ER request: Add native AsciiDoc (.adoc) rendering in CODE: Render .adoc in the repo file viewer with a Preview/Source toggle. Resolve relative links/images within the repo. (Nice to have) Support rendered view in PR diffs.

When creating a Pull Request, users face difficulty finding the correct branch in repositories with many similarly named branches (e.g., multiple branches containing “release”). Since pagination isn’t supported, even exact matches like release may not appear in search results. Users currently rely on a regex workaround (e.g., release$) to locate branches, which isn’t intuitive. We should improve branch discovery by adding pagination, enhancing search logic to prioritize exact matches, and optionally providing a tooltip or hint explaining regex usage.

I believe it’s a good idea to integrate Dependabot with the Harness codebase. You can use open-source projects such as Mend Renovate and build capabilities like internal organization dependency checks from your own artifact modules, JFrog, etc. This integration will enable DevEx teams to publish new inter-organization packages while ensuring that teams keep their dependencies up to date. It will also help development teams track their dependency versioning effectively.

Provide a feature to Mirror repo into any other repository like Gitlab, Gitness, Bitbucket others. This is required maintain local copy of Repo for Escrow purposes.

Hi Harness Team, Could you please implement group or folder structure in Code Repo because we have multiple git repos where we want to group same set of repos into one group or folder so that we can view repos related to that group. Example we have AWS set of repos where we want to group all AWS set of repos into AWS group similarly for GCP and On-Prem. GitLab provided this feature. Due to this missing functionality we have to scroll or search every repo causing hinderances to our productivity. Request you to implement this feature as soon as possible. Awaiting your speedy response. Regards Venkat Raja Tirukovela

As the number of users getting added to Codowners file increases, it becomes very difficult to search or manage. The format should either be vertical or provide a better way from a UX perspective.

Add dark mode option to Gitness UI

Description : As it stands, the permissions we are applying at the project level are being enforced at the repository level. This overlap is causing a delay for various teams. We wanted to implement an access control at the repo level rather than project level. This change would allow us to set specific permissions for each repository, which could inherit certain permissions from the project level as needed which will facilitate a proper approval process. Expected Solution : We should have an option or check box at the project level enable a rule at selected repos and another to select the repositories which should inherit where we have isolation on both. Simply put, at Project level, there should be an option to exclude repos from the rules created.

Support for native Issue tracking and Epics in Gitness

We have new requirement from one of customer is to maintain local copy of the code repo with a continuous sync using a mirror option similar to what we have in gitlab and bitbucket. Once configured every commit will have sync done on the target code repo.