- Explain that it is okay to have a merge commit for pull requests.
- Describe
git pull
instead ofgit merge
in the "Keep Your Fork Updated" section.
- Define
pretty.fmt
config option and usefmt
as the format name in thegit log
aliases for compact commit logs.
- Typo: "its status would appear as Merged" => "its status would not appear as Merged".
- Use
git pull
to keep the fork's main development branch updated with changes in the upstream instead ofgit fetch
andgit 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 co
forgit checkout
command. - Alias
git cob
forgit checkout -b
command. - Alias
git ca
forgit commit --amend
command. - Staging partial changes with
git add -p
.
- Discuss editing previous comments in general with
git rebase -i
command rather than squashing commits in particular. - Include
git pull
command to update the main development branch while merging pull requests in local clone of upstream repository. - Discuss
git push -f
command in a separate section.
- Explain that downloads are for stable version only.
- Provide a list of all placeholders used in the document.
- Aliases
git br
andgit brr
forgit branch
commands.
- Use shorter alias names for
git log
aliases. - Simpler
git rebase
commands. - 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.