1. Never break the Master
2. Always change the Master with Pull-Requests and use push only for minors.
3. Commit early and commit often
Description
The master always needs to be deployable. When developing features or resolving bugs, create new branches to group your commits by topic and always pull from the remote master.
The branch maintainer is responsible for testing his feature branch against the newest master version. He can always use a pull-request to invite others for discussion and testing of his branch.
Always keep syncing your branches with the remote repository and commit early and often. Every contribution as little it might be, can be valuable inspiration and input for others.
Description
Create new branch from remote master
git checkout -b FeatureTitle origin/master
Earlier