link to

parent 60cb381f
......@@ -10,7 +10,7 @@ Use following labels:
4. Customer journey
When creating a new MR tag it with a corresponding label.
When creating a new MR tag (label) it with a corresponding label.
Every team (currently modal team, customer journey team and delivery team) is responsible for merge requests connected with their work (tagged by label).
......@@ -19,3 +19,11 @@ Every author is responsible for his/her own merge request (if his or her MR is s
Two thumbs 👍 (except author) up are enough -> MR can be assigned to Petr.
**After merge:** In case of trouble with the code, the author is responsible for fixing it. The reviewers will also be notified so they know what to check next time.
## How to
All merge request should be assigned to `pool`
So all merge request for code review can be found in the pool 🦥
https://git.easy.cz/dashboard/merge_requests?state=opened&assignee_id=93
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment