... | ... | @@ -3,7 +3,7 @@ This section defines our git-workflow for developers. Contributors should use th |
|
|
|
|
|
Merge Requests which aren't following our Merge-Contract (below) will be closed.
|
|
|
|
|
|
## Git-Workflow
|
|
|
## The workflow
|
|
|
* Direct pushes to staging and master aren't allowed. There must be a new branch with a merge request for every change (bugfixes, typos, label-/text-changes, codestyles, refactoring, etc...)
|
|
|
* On finishing coding, a Merge-Request to the staging-branch should be created. Merge Requests to Master will always be denied.
|
|
|
* A Master will review and test the MR. Better you test before (at least a smoke test, it's recommended to do some additional testing).
|
... | ... | |