Squashing Commits

We try to keep the history for pdf.js relatively clean and we may ask contributors to "squash" their commits before we merge.

Note: These directions assume that you named the Mozilla pdf.js repo (not your fork) upstream and you have a branch called super-feature. See Contributing for details.

1. Add the following to your git config. Either the global one or the config within your pdf.js fork (.git/config).

[alias]
	squash = !sh -c 'git checkout upstream/master && git merge --no-commit --squash $0 && git checkout -B $0 && git commit -e'

1. Then you simply need to do:

git squash super-feature

1. That will bring up your editor to allow you to put in the commit message you want. After entering a commit message, press Esc and type :wq to exit the editor (if the editor is set to vim).
2. Then update the pull request:

git push --force origin super-feature

Alternatives

1. Step-by-step commands

# fetches the current upstream repository
git fetch upstream
# resets HEAD to the current upstream
git checkout upstream/master
# merges all commits from the local branch
git merge --no-commit --squash super-feature
# re-creates the branch starting from current HEAD (old commits will be lost)
git checkout -B super-feature
# lets you edit the commit and checks in the changes (you can also use git commit -m "message")
git commit -e
# pushes the changes (in general, be careful with the --force parameter)
git push --force origin super-feature

1. Or, you can use rebase. Let's say you have 5 commits to squash and you don't have merge commits:

git rebase -i HEAD~5