About commits
类似于保存已经编辑的文件，提交会记录对分支中一个或多个文件的更改。 Git 将为每个提交分配唯一的 ID，称为 SHA 或哈希，用于识别：
- 具体的更改
- 进行更改的时间
- 更改创建者
在进行提交时，必须包含简要描述更改的提交消息。
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 管理存储库的提交签字策略.
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 关于 Git 变基.
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.
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.
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.
注意
The file tree will not display if your screen width is too narrow or if the commit only includes one file.
Further reading
- 在 GitHub Desktop 中提交并审查对项目的更改 on GitHub Desktop