close

Commits

Learn how commits save changes to your files, track authorship, and organize your project's history in GitHub.

In diesem Artikel

About commits

Ähnlich wie beim Speichern einer Datei, die bearbeitet wurde, zeichnet ein Commit Änderungen an einer oder mehreren Dateien in Ihrem Branch auf. Git weist jedem Commit eine eindeutige ID zu, die als SHA oder Hash bezeichnet wird. Damit wird Folgendes identifiziert:

  • Die jeweiligen Änderungen
  • Der Zeitpunkt der Änderungen
  • Wer die Änderungen vorgenommen hat

Wenn Du einen Commit durchführst, musst Du eine Commit-Mitteilung hinzufügen, in der die Änderungen kurz beschrieben werden.

If the repository you are committing to requires commit signoffs, and you are committing in the web interface, you will automatically sign off on the commit. See Verwalten der Richtlinie für das Abzeichnen von Commits für dein Repository.

You can add a co-author on any commits you collaborate on. See Creating a commit with multiple authors or on behalf of an organization.

You can also create a commit on behalf of an organization. See Creating a commit with multiple authors or on behalf of an organization.

Rebasing lets you change a series of commits and can change the order of the commits in your timeline. See Informationen zu Git-Rebase.

About commit branches and tag labels

Commit pages can show labels for branches and tags that contain the commit. These labels help you understand where a commit appears in the repository history.

Screenshot of a commit summary. A branch icon and "main" are highlighted with an orange outline.

If your commit is not on the default branch (main), the label will show the branches which contain the commit. If the commit is part of an unmerged pull request, you can click the link to go to the pull request.

Once the commit is on the default branch, any tags that contain the commit will be shown and the default branch will be the only branch listed. See Git Basics - Tagging in the Git documentation.

Screenshot of a commit summary. The tag icon and "v2.3.4" are highlighted with an orange outline.

Using the file tree

The file tree helps you navigate between files in a commit and focus on the diffs that matter. You can select a file to view its diff or filter by file path when a commit changes many files.

Hinweis

The file tree will not display if your screen width is too narrow or if the commit only includes one file.

Screenshot of the "Files changed" tab of a pull request. In the left sidebar, the file tree is outlined in dark orange.

Further reading