Feature Requests

We'd like to have a method to be able to stop commits that are attempted if they don't meet certain criteria. For example as a part of our licensing for 3rd party software, they look at the emails for the commit authors and charge by the author. Some of our teams use multiple emails, so we want to restrict our users from only using the authorized emails.

This is not available, but it is useful for our deployments

Looking for something of a similar feature parity to commit author verification hook in some other competitors to address licensing issues we have with other tooling. For example in Bitbucket this is a pre-receive repository hook named Verify Committer. https://confluence.atlassian.com/bitbucketserver/using-repository-hooks-776639836.html Checkmarx specifically uses the commit author email address for licensing.

With the recent Semantic Search feature update to the existing Code Search functionality of Harness Code Repository, please add a note in the documentation that we need to enable a certain feature flag to use the new feature.

The Governance policies set on repositories like protecting branches is available for each project, however there is no policy or way to enable the Goverance globally .

Today, if a merge conflict shows up in a Pull Request, Gitness shows steps for resolving the conflict in the CLI. It would be nice to allow users to resolve merge conflicts directly in the PR experience.

We need to update specific labels/annotations in the delegate. The values are not exposed via the value file: https://github.com/harness/delegate-helm-chart/blob/1392fd3ac5c6334db529f06554fbbe6fdc4f0146/harness-delegate-ng/templates/_helpers.tpl#L44-L48 We need another setting in the values.yaml file so we can add to those tags. We are trying to add the labels and annotations shown here: https://app.datadoghq.com/apm/service-setup?architecture=container-based&collection=Helm%20Chart%20%28Recommended%29&environment=kubernetes&language=java

Add dark mode option to Gitness UI

we use the Git Experience when creating all our resources. After a recent update we noticed that every time we create a new resource it chooses the Harness Code Repository by default. We checked the account settings and did not see a way to disable this. Can we disable the Harness Code Repository? We do not want this as an option, just our GitHub.

Needed a Feature for a collapse all option on all files in a merge request?