Feature Requests

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.

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.

As a user I want to revert a PR. This should be available in UI and as an API call. Use cases: PR merged into release branch and either deployment fails or deployment needs to be rolled back including the PR. Release can be rolled back by reverting the PR in CR and letting downstream rollback the changes. Release can be rolled back in CD and pipeline automatically reverts the PR User can quickly find PRs that have been reverted

Add dark mode option to Gitness UI

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.

Code Owners should be reviewers so that they can be informed about changes to Repos under their ownership.

Add support of PR listing to harness. This is so that someone can see all PRs they have created, along with All PRs awaiting their approval. It would also be good to be able to see the status of the PR