About commits
편집된 파일을 저장하는 것과 마찬가지로 커밋은 분기에서 하나 이상의 파일에 변경 내용을 기록합니다. Git은 각 커밋에 다음을 식별하는 SHA 또는 해시라는 고유 ID를 할당합니다.
- 특정 변경 내용
- 변경된 시점
- 변경 내용을 만든 사람
커밋할 때 변경 내용을 간략하게 설명하는 커밋 메시지를 포함해야 합니다.
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
