Theorems for polite open source development
Use feature branch and pull request/merge request
Have as granular pull/merge requests as possible with as few commits as possible
Never break things that works.
If you break something on master: Fix asap and write tests for the fix.
Commit messages should consist of a consise description of the changes are.
Use merge commits
When merging a feature branch into master, use merge commits with a link to the pull/merge request
Pull/merge requests titles should be unique and konsise.
A pull/merge requests should always describe:
- Why its needed.
- What it changes.