About commits
Assim como ao salvar um arquivo que foi editado, um commit registra alterações em um ou mais arquivos no seu branch. O Git atribui a cada commit um ID exclusivo, denominado SHA ou hash, que identifica:
- Cada uma das alterações feitas;
- O momento em que as alterações foram feitas;
- O autor das alterações.
Ao fazer um commit, você deve incluir uma mensagem que descreva brevemente as alterações.
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 Como gerenciar a política de aprovação de confirmação para seu repositório.
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 Sobre a troca de base do 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.
Observação
The file tree will not display if your screen width is too narrow or if the commit only includes one file.
