-
Notifications
You must be signed in to change notification settings - Fork 342
Basic git contribution
Alexis Haumaitre edited this page Jun 9, 2018
·
2 revisions
You never directly commit to master, always create a branch and a Pull Request.
Your branch shoud start with either add/update/feat/fix/hotfix/clean
followed by a couple of meaningfull words about your feature
- Moove to master branch (git checkout master)
- Fetch it and pull it (git pull --rebase)
- Create a branch from this freshly update master branch (git checkout -b my-feature)
- Commit and push you work often.
- When you finished your features or pack of fixes, create a Pull Request and request a review from
A3-Antistasi/contributors
. - Add a more or less long description so we can know what this PR is more precisly doing (especially for bug fixes you can just #numberofissue to link it)
- Keep working on this branch until the branch (PullRequest) is merged to master.
- Delete the branch once it has been merged.
As soon as the branch/pull request has been merged you need to re-create a branch starting from a fresh updated master.