Feature Requests

Enable read‑only collaborators to contribute code by forking a repository to their own project/org and opening a pull request back to the upstream repo—without requiring write access to the upstream. There are workarounds that offer a similar functionality, but we lose the PR UX and it makes policies and implementation more complex. Forks Allow a user to fork a repo into a chosen scope (account/org/project), preserving a fork linkage to the upstream (like GitHub). Provide Sync from upstream (UI and API) to update the fork’s default branch (equivalent to “Fetch upstream / Sync fork”). Cross‑Repository PRs (across forks): Allow creating a PR where base is an upstream repo/branch and compare is a branch in the user’s fork (“compare across forks” UX). Support the common flags: “Allow edits from maintainers,” status checks, merge strategies, and branch protections enforced by the destination repo’s rules. Governance & RBAC: Org/account setting to allow/disallow forks (private repos), mirroring GitHub’s forking policy toggles for private scopes. Clear visibility of the fork network, limits on fork depth, and audit events for fork/sync/PR actions

HTTP Headers for outgoing webhooks in Harness Code Repositories. Currently, when a webhook is triggered by a repository event (e.g., Push, PR Merge), the payload is sent with standard headers. We need the ability to inject custom key-value pairs (e.g., Authorization: Bearer <token> or X-Custom-Auth: <secret>) into the request header.

Requesting this feature for Harness Repositories. Other repository software vendors like Github already offer this feature, and when migrating to Harness Repos, developers express some challenge when they want to share or reference specific code in large files. Highlighting the selected line(s) is a bonus as well. Some other terms to aid in feature request searching: deeplinking, deep link, line code link, line anchor link

Hi, Just wanted to check if we can add a feature in harness to send notifications to the code owners and the PR creator if the PR is not merged for a week. This should trigger automatically and send email for all the repos which we have in harness. Regards Lokesh

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.

Developers using Harness Code may not have a need to navigate outside of the Code Repo context in the Harness UI. Today, they have to navigate to the Pipelines context to see the execution history and filter for their code repo. Harness has the trigger activity history for a pipeline. In that data is the code repository that caused the trigger to fire. There would be a better and more intuitive user experience for developers if the pipeline execution history related to a code repo was shown in the code repo context.

Harness support equipment, I would like you to enable the option of cloning repositories by SSH, in addition to the creation of SSH keys per profile to be able to clone the git the harness repositories that we own

Harness support equipment, I would like you to enable the option of cloning repositories by SSH, in addition to the creation of SSH keys per profile to be able to clone the git the harness repositories that we own

Dear Harness Support Team, I'd like you to enable the SSH option to clone our harness git repositories. Also the option to create SSH keys to clone them. Best regards.

Problem: Teams store Docs-as-Code in .adoc files. In Harness CODE, AsciiDoc files show as raw text; there’s no rendered preview. Gap: CODE’s repo viewer/PR UI doesn’t natively render AsciiDoc, creating friction for reviews and onboarding, and lacking parity with platforms like GitLab. ER request: Add native AsciiDoc (.adoc) rendering in CODE: Render .adoc in the repo file viewer with a Preview/Source toggle. Resolve relative links/images within the repo. (Nice to have) Support rendered view in PR diffs.