Signed Commits Using Git Experience

Git Experience supports signed commits when committing changes to your GitHub repo using Harness.

Git Experience supports signed commits when committing changes to your GitHub repo using Harness. Signed commits add a layer of trust and security to your commits. They prove that a commit was genuinely created via Harness, and that the code changes have not been tampered with since.

Before you begin

GitHub App connector required

To use signed commits, configure a GitHub App-based connector in your Harness account. Go to Use a GitHub App in a GitHub connector to configure one.

Enable signed commits for your account

Enable signed commits in Git Experience:

• Navigate to Account Settings → Default Settings → Git Experience.

• Select Enable Signed Commit for GitHub.

• Click Save.

Once you have enabled signed commits for your account, you can start committing pipeline changes to your GitHub repo with signed commits.

Use signed commits

In the Pipeline Studio, when you make a change in your pipeline and click Save, the changes are committed to your GitHub repo with a signed commit.

The signed commit appears in your GitHub repository with a Verified tag.