You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To introduce new, tested and stable changes, push requests to the development branch are used.
30
+
To introduce new, tested and stable changes, pull/ merge requests into the master branch are used.
31
31
32
-
If the master branch is not ahead of the push and no other push request to master is open, the request can go directly to master instead.
32
+
Pull request drafts can be used to communicate about changes and new functionality.
33
33
34
-
Push request drafts to the development branch can be used to communicate about changes and new functionality.
35
-
36
-
After reviewing the changes, they will be merged into the branch.
37
-
38
-
Merges to development must be tested again after merging master into it before merging it to master. If there is an open push request to master, it must be merged with development and tested as well before pushing development to master.
34
+
After reviewing and testing the changes, they will be merged into master.
39
35
40
36
Every merge with master is followed by introducing a new version tag corresponding to the semantic versioning pradigm.
0 commit comments