|
Hi all,
Due to a broad consensus on IRC, with Gitlab's addition of Merge
Trains[1]
we are moving away from using Marge Bot. The changes to the code
base
itself are not massive. We're no longer running the usual tests
(e.g. everything
other than overnight ones) on master, as they would have already
been ran
on their branch previously.
Regarding developer work flow: instead of assigning Marge Bot to
an accepted
MR, we should just add the MR to a merge train (or start one
should none be
already running), as explained in the documentation below.
This change should make accepting and merging multiple MR's at
once
easier to do and manage with Gitlab's support.
Regards,
Alex
[1] Gitlab
merge trains
|
