-
Notifications
You must be signed in to change notification settings - Fork 121
Workflow
Alexander von Trostorff edited this page Jun 23, 2020
·
2 revisions
- Create an issue, if there is none already. Everything you work on needs an issue. And issues should be as atomic as possible. Issues are later used for release notes.
- Create a new branch that you call either feature/# or bugfix/# followed by the issue number and the title of the branch seperated with "-". Just have a look at the other branches around.
- Make changes and commit those. To keep the git history clean you are advised to use the amend functionality, to make one commit per change set. The commit message should be formatted in the following way:
[title]
[description]
Fixes #[issue number]
This allows GitHub to auto close the issue when a Pull Request is merged into develop.
- Make a Pull Request. And what for it to be merged. Make sure it links to the issue.