146 |
147 |
148 | ))
149 | )}
150 |
151 | >
152 | );
153 | }
154 |
--------------------------------------------------------------------------------
/README.md:
--------------------------------------------------------------------------------
1 | # GitLab merger bot
2 |
3 | 
4 |
5 | ## What does it do?
6 |
7 | The goal is to have green master after every merge. To achieve this, you have to rebase every single merge request just before a merge and wait for the pipeline status. It takes a lot of time to manually maintain, especially when you have to process multiple merge requests at once (common situation for large projects, monorepos etc.). So let's automate it with GitLab MergerBot.
8 |
9 | 1) When your merge request is ready to be merged, assign it to the bot.
10 | 2) The bot will add your request to its own serial (FIFO) queue. (single queue for every repository)
11 | 3) When your request is on the turn, the bot will rebase the MR and start waiting for the pipeline.
12 | 4) When the bot detects some problems with the merge request it'll reassign the merge request back to the author.
13 | Reasons can be for example:
14 | - Failing pipeline or pipeline waiting for a manual action
15 | - The merge request has unresolved discussions
16 | - The merge request can't be rebased due to a conflict
17 |
18 |