> 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/code-repository/use-harness-code/collaborate-and-develop/commit.md).

# Commit

With Harness Code, you can commit directly in the Harness Code UI or you can [clone your repo](/code-repository/use-harness-code/collaborate-and-develop/clone-repos.md) and commit and push from your local machine.

Commits you see in the Harness Code UI exist on your remote branches. If you're working from a [local clone](/code-repository/use-harness-code/collaborate-and-develop/clone-repos.md), you need to commit and push to the remote to see your changes in Harness Code.

This topic primarily explains how to work with commits in the Harness Code UI. For details about committing, pushing, and reverting with command line Git, an IDE, or another local Git tool, refer to the documentation for your preferred tool.

### Create a commit <a href="#create-a-commit" id="create-a-commit"></a>

1. When viewing a repository in Harness Code, go to **Files** and select the branch you want to work on from the branch dropdown menu.

   Commits made in the Harness Code UI can be committed directly to the selected branch. *You are editing a remote branch when you commit in Harness Code.* Make sure you select the correct branch or [create a branch](/code-repository/use-harness-code/collaborate-and-develop/branch.md#create-a-branch) to isolate your changes.
2. Select the file you want to edit or create a **New File**.
3. Modify the file as desired. If you are editing an existing file, select **Edit** to enable editing.

   You must commit your changes to save them. There is no way to preserve an uncommitted draft within the Harness Code UI. However, you can isolate work-in-progress by selecting the **Create a new branch** option when you commit changes.
4. Select **Commit changes**.
5. Enter a **Commit message** and optional extended description.
6. Select whether you want to **Commit directly to the current branch** or **Create a new branch and start a PR**.
7. Select **Commit** to commit your changes.

   If you selected **Commit directly to the current branch**, your changes are instantly applied to the current branch.

   If you selected **Create a new branch and start a PR**, a new branch is created and you're be prompted to [create a PR](/code-repository/use-harness-code/pull-requests/create-pr.md).

### Inspect a commit <a href="#inspect-a-commit" id="inspect-a-commit"></a>

When viewing a repository in Harness Code, there are several ways you can inspect commits to get SHAs or view diffs.

* The **Commits** page lists the commit history for a specific branch or tag.
  * You can select a commit's short SHA to inspect that commit.
  * The default branch is selected automatically. Select the default branch name to select a different branch or tag.
  * If a commit was part of a PR, the PR number is listed on next to the commit message. You can select the PR number to view that PR.
* The **Files** page shows the short SHA and commit message for the latest commit to each file in the context of the current branch or tag.
  * You can select a commit's short SHA to inspect the changes in that commit.
  * If a commit was part of a PR, the PR number is listed on next to the commit message in the files list. You can select the PR number to view that PR.
* When reviewing a pull request, the **Commits** tab lists the commits that are included in that PR. Select a commit's short SHA to inspect the changes in that commit.

{% hint style="info" %}
Select the **Copy** icon next to a commit's short SHA to copy the full commit SHA.
{% endhint %}

Upon selecting a short SHA, the **Commits** page opens to the diff view. Here you can compare line-by-line changes in the selected commit, including changes, additions, and deletions.

Select the **Settings** icon to select your preferred **Diff View** and **Line Breaks** options.

Select **Browse files** to inspect files in that commit.

### Revert a commit <a href="#revert-a-commit" id="revert-a-commit"></a>

You can't directly revert commits in the Harness Code UI. Instead, you need to [create a commit](#create-a-commit) to overwrite the previous commit.

Alternately, if you're working from a [local clone](/code-repository/use-harness-code/collaborate-and-develop/clone-repos.md), you can use more nuanced controls available through command line Git, your IDE, or another Git tool.

### Next steps <a href="#next-steps" id="next-steps"></a>

[Sign commits](/code-repository/use-harness-code/collaborate-and-develop/signing-commits.md): Cryptographically sign commits to prove authorship and prevent tampering.