> For the complete documentation index, see [llms.txt](https://developer.harness.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.harness.io/harness-platform/3.0/harness-platform-resources/git-experience/signed-commits-harness.md).

# Signed Commits Using Git Experience

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

{% hint style="info" %}
**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](/harness-ai/use-harness-platform/connectors/code-repositories/git-hub-app-support.md) to configure one.
{% endhint %}

### Enable signed commits for your account <a href="#enable-signed-commits-for-your-account" id="enable-signed-commits-for-your-account"></a>

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 <a href="#utilize-signed-commits" id="utilize-signed-commits"></a>

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.