Feature Requests

Ideally when we have Code Repository as one of the Harness provided SCM, there should be a default connectivity between SEI and Code Repository. We are using Code Repository for our internal projects, but cannot demonstrate DORA metrics properly as there is no connectivity / integration available between SEI and Code Repository, hence the request

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.

Add dark mode option to Gitness UI

We need to enable tagging feature in code repository in RBAC so that when we create resource groups, one can filter the repos by tags. Currently we can either select all the repos or individual repos while creating the resource group. Please let us know if you need any more details?

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.

It is requested to implement in the repositories the functionality to register a GPG key, in order to allow the cryptographic signature of commits and tags made by developers. This functionality is already widely used on platforms such as GitHub, where GPG keys are associated with user accounts to validate the authenticity of the source code and reinforce the security of the repository. Objective: Allow developers to upload their GPG public key to repositories. Automatically verify the signature of commits and tags when pushing. Visually indicate in the repository history if a commit is signed and valid. Align version control security with standard industry practices Justification: Implementing this functionality will improve traceability and trust in the authorship of changes, and helps prevent malicious alterations to the source code, thus contributing to a more secure development environment.

We would like to request the ability to add and use SSH keys for authentication in Code repo. This would enable easier and more secure cloning workflows, especially for environments that prefer or require SSH over HTTPS.

Can support for mermaid diagrams please be added when rendering markdown in Code Repositories?

I'd like to send a trigger event to pipelines when a tag is created in a repo

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.