If you follow the fork rebase flow for git, this makes things slightly less annoying so:

1. You have a master fork and you force everyone else to fork that instead of branch off of it to keep the master fork clean
2. You ask your employees to squash commits for merge requests to keep your master branch clean with features.
3. Your master branch is always ready for deploy, you expect it to be in production shape

Running git-rebase "commit message" does the following:

1. Assumes your fork is origin and your master fork is upstream
2. Assumes you want to squash all your commits into one for that feature and branch
3. Assumes you are done with a feature and now have multiple commits you want to squash
4. Gets latest from upstream and rebases your current branch
5. Checks with upstream/master to see how many commits you have that master does not
6. Resets the branch to upstream/master
7. Re-commits the reset data with the message supplied in the command
8. Force pushes the branch to origin

npm link #links so you can access this command anywhere npm unlink# basically uninstall