- Explain that it is okay to have a merge commit for pull requests.
- Describe
git pullinstead ofgit mergein the "Keep Your Fork Updated" section.
- Define
pretty.fmtconfig option and usefmtas the format name in thegit logaliases for compact commit logs.
- Typo: "its status would appear as Merged" => "its status would not appear as Merged".
- Use
git pullto keep the fork's main development branch updated with changes in the upstream instead ofgit fetchandgit merge.
- Rebase options to get rid of merge commit while merging without commit.
- Caveats of various rebase options.
- Amending last commit with
git commit --amend. - Alias
git coforgit checkoutcommand. - Alias
git cobforgit checkout -bcommand. - Alias
git caforgit commit --amendcommand. - Staging partial changes with
git add -p.
- Discuss editing previous comments in general with
git rebase -icommand rather than squashing commits in particular. - Include
git pullcommand to update the main development branch while merging pull requests in local clone of upstream repository. - Discuss
git push -fcommand in a separate section.
- Explain that downloads are for stable version only.
- Provide a list of all placeholders used in the document.
- Aliases
git brandgit brrforgit branchcommands.
- Use shorter alias names for
git logaliases. - Simpler
git rebasecommands. - Simpler description of some steps.
- README.md with the following top-level sections:
- Introduction
- Quick Reference
- Create Pull Request
- Merge Pull Request
- Nifty Commands
- License
- Support
- Generate PDF and TXT output files from README.md.