If we are in a position where new developments or bug fixes need to be merged from a branch back to master, follow the rules defined here. If there is anything unclear also in specific cases, we can always discuss in our meetings.
If we are in a position where new developments or bug fixes need to be merged from a branch back to master, follow the rules defined here. If there is anything unclear also in specific cases, we can always discuss in our meetings.
Keep merge request as small as possible; changes limited to one problem/issue/bug. This will help to get MRs reviewed and closed quickly.
It is very useful and will speed up the process described here if particular developments have already been discussed in meetings or gitlab Issues BEFORE a Merge Request or any development is started.
It is very useful and will speed up the process described here if particular developments have already been discussed in meetings or gitlab Issues BEFORE a Merge Request or any development is started.
A merge request is not complete, if there are no Labels assigned.
A merge request is not complete, if there are no Labels assigned. Labels help the code review.
- Select between: Bug, Feature, Development
- Select between: Bug, Feature, Development
- Specify, if needed: Critical (must be addressed immediately), Important (blocks other things)
- Specify, if needed: Critical (must be addressed immediately), Important (blocks other things)
