Feature Requests

We need to enable the CODE_FORK_ENABLED feature flag, in order to Because we need to create an independent copy of a repository for a security fix, that's need to be independed of the current code. The new feature is mandatory.

Add dark mode option to Gitness UI

Following industry standards, when viewing a README.md file, when hovering over headers, show a link to header button that, when clicked, copies a link to that header (referenced by an anchor tag, which references the header it refers to)

Allow a Harness Service Account to be authenticated by a JWT signed by an external issuer (e.g. Keycloak, SPIRE, a Kubernetes cluster's projected-token issuer) for Harness Code Git operations. Harness would validate the JWT against a configured external JWKS and claim mapping, and authorize the Git request as the bound Service Account. similiar to this API: https://developer.harness.io/docs/platform/automation/api/default-settings-for-jwt-token/

We're looking for a way to create OPA policies from Git so we can ensure they're version controlled.

During internal review with the Harness CODE team, it was confirmed that the current CODE - Jira integration does not support restricting or mapping a Harness Project/Repository to specific Jira projects or boards. Once the integration is enabled, Jira references and automations are allowed across all Jira projects without an “allowlist” or project‑scoped control. Given the security and governance requirements for our environment, we request an enhancement to introduce a feature that allows administrators to define which Jira projects/boards a particular Harness Project or repository is permitted to interact with.

Please enable FF CODE_IMPORTER_V2_ENABLED for import harness code repo from bitbucket.

Currently, Harness does not support Teams connector in the code repository, with the help of which one can automatically get notifications in the Teams channel for any events in git.

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.

When listing Repositories within a Project, it would be very useful to have a tags/labels method to filter searches for a particular Repository