1.0.1 • Published 5 years ago
git-rebase-flow v1.0.1
If you follow the fork rebase flow for git, this makes things slightly less annoying so:
- 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
- You ask your employees to squash commits for merge requests to keep your master branch clean with features.
- Your master branch is always ready for deploy, you expect it to be in production shape
Running
git-rebase "commit message"
does the following:
- Assumes your fork is origin and your master fork is upstream
- Assumes you want to squash all your commits into one for that feature and branch
- Assumes you are done with a feature and now have multiple commits you want to squash
- Gets latest from upstream and rebases your current branch
- Checks with upstream/master to see how many commits you have that master does not
- Resets the branch to upstream/master
- Re-commits the reset data with the message supplied in the command
- Force pushes the branch to origin
npm link #links so you can access this command anywhere npm unlink# basically uninstall
1.0.1
5 years ago