- Keeps your project more organized by splitting features into separate branches for review.
- Avoids merge commits and keep your git history clean.
Repeat this process for every feature you want to add.
- Make sure the
masterbranch of your fork is even withupstream/master - Create a feature branch, leave the
masterbranch untouched (important!) - Make your changes in your feature branch
- Create a PR/MR to upstream
- Review changes in PR/MR
- Choose rebase merging as merging strategy (can be set in GH repository configuration)
- Delete the feature branch (optional)
Note:
If the feature takes a while to develop it's quite likely that it will diverge from
master. So rebase the feature branch toupstream/masteron a regular basis.