Feature Requests

We are trying to configure a webhook from Harness Code Repository to an Argo CD instance using the standard Argo CD webhook endpoint: https://argocd-instance/api/webhook The request reaches Argo CD successfully, but Argo CD rejects it with: HTTP 400 Unknown webhook event From our investigation, Argo CD expects webhook requests in one of the SCM formats it supports, such as GitHub, GitLab or Bitbucket. Harness Code currently sends its own webhook payload format, for example: { "trigger": "branch_created", "repo": { "id": 68, "identifier": "OCM", "default_branch": "main", "git_url": " https://MY_GIT_URL.git " }, "ref": { "name": "refs/heads/argocd-test" }, "sha": "aaa0c10789f206ffdfa312e8226a443dcd028123", "old_sha": "0000000000000000000000000000000000000000" } Argo CD does not recognize this payload and therefore returns Unknown webhook event. Would it be possible to configure Harness Code Repository webhooks to send an Argo CD-compatible payload, for example by using the GitHub or GitLab webhook format?

Add dark mode option to Gitness UI

Provide a fully supported and documented way to expose Harness Code SSH access in Self-Managed Platform (SMP) deployments Harness Code Repository provides a code_ssh_enabled configuration option and creates the required Kubernetes Service exposing the SSH port. However, enabling this option alone is not sufficient to make SSH cloning functional in many self-managed Kubernetes environments. And with SSH cloning being a standard workflow used by developers, automation systems, and CI/CD platforms, it would be one of the most benefitiary implementation and improvements for end users using the Harness SMP

Hi Team, Currently, Harness has no native connector to send audit logs to the Microsoft Sentinel SIEM platform. We would like Harness to send its logs directly to a Microsoft Sentinel Data Collection Endpoint (DCE) via HTTP, which will allow for security teams to monitor these logs. Requirements: Embed the tenant ID, application ID, app secret (from customer) in application code, so that Harness can obtain access token to POST logs to Microsoft Sentinel DCE. Key benefits of CCF push: Application-controlled data flow: Your application controls when and how to send data, enabling intelligent batching strategies and optimized network usage. Real-time ingestion: Send data immediately as events happen, without waiting for polling intervals. Simplified architecture: No need to maintain API endpoints for Sentinel to poll. Secure authentication: Uses Microsoft Entra applications with OAuth 2.0 for secure data submission. Kind Regards,

Enable feature Flag for Code Coverage

We would love to hide archived Repositories for non Code Maintainers i see this as its own RBAC Permission

Currently, excluding a repo from an account-level rule applies globally — any project can bypass it, not just the approved one. We'd like exceptions to be scoped to a specific project so only the approved team gets the deviation while all others remain governed by the account-level rule. This would let us maintain strong account-level governance with controlled, targeted exceptions.

Hello Harness Support Team, Could you please assist us in enabling the feature flag CI_CODE_COVERAGE for our environment?

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

Currently, the Harness GitHub connector primarily supports integration with the public github.com . This limitation prevents organizations that use GitHub Enterprise Server (on-premise) or GitHub Enterprise Cloud with EU data residency (*. ghe.com ) from natively connecting their repositories to the Harness platform. GitHub now offers data residency options, including for the EU, allowing enterprises to store their code and repository data within specific regions to meet compliance and data sovereignty requirements. Harness documentation shows that connections to GitHub Enterprise Server are possible for some modules like SEI (Software Engineering Insights). However, broader and more direct connector support across the Harness platform is needed. Feature Request: We request that the Harness GitHub connector be enhanced to officially support connections to: GitHub Enterprise Server: Allow users to provide the URL of their self-hosted GitHub Enterprise instance for a direct integration. GitHub Enterprise Cloud with EU Data Residency: Support the *. ghe.com domain structure used for GitHub Enterprise Cloud instances with data residency, enabling a seamless connection for organizations with these specific compliance needs. In addition to the core request for GitHub Enterprise Server and EU data residency support, it is critical that Harness also includes support for OIDC-based authentication for the GitHub connector. As we are moving to standardized, secure, and passwordless authentication methods. OIDC will be an important feature we are looking forward.