Committing
suggest changeIntroduction
Commits with Git provide accountability by attributing authors with changes to code. Git offers multiple features for the specificity and security of commits. This topic explains and demonstrates proper practices and procedures in committing with Git.
Syntax
git commit [flags]
| Parameter | Details |
|---|---|
| --message, -m | Message to include in the commit. Specifying this parameter bypasses Git's normal behavior of opening an editor. |
| --amend | Specify that the changes currently staged should be added (amended) to the previous commit. Be careful, this can rewrite history! |
| --no-edit | Use the selected commit message without launching an editor. For example, git commit --amend --no-edit amends a commit without changing its commit message. |
| --all, -a | Commit all changes, including changes that aren't yet staged. |
| --date | Manually set the date that will be associated with the commit. |
| --only | Commit only the paths specified. This will not commit what you currently have staged unless told to do so. |
| --patch, -p | Use the interactive patch selection interface to chose which changes to commit. |
| --help | Displays the man page for git commit |
| -S[keyid], -S --gpg-sign[=keyid], -S --no-gpg-sign | Sign commit, GPG-sign commit, countermand commit.gpgSign configuration variable |
| -n, --no-verify | This option bypasses the pre-commit and commit-msg hooks. See also <http://stackoverflow.com/documentation/git/1330/hooks#t=201609151909429849523 |
Found a mistake? Have a question or improvement idea?
Let me know.
Table Of Contents