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
{{ message }}
This repository has been archived by the owner on Jan 19, 2021. It is now read-only.
Similar to GitLab's merge trains, but without the hassle of having to use merge request pipelines nor merge commits
Initially, this should be about merging commits automatically as long as checks/CI is passing. Internally we'll use some queue mechanism where we'll stack commits to be merged there. For each MR in the queue, we'll take it, rebase it on master, wait for checks and merge if they pass.
In the future we might add more configurability to it, like commands in the PR to alter the order, multiple strategies for when one MR in the queue can't be rebased, possibility of enabling/disabling this functionality on a per PR bases (with labels, or command or whatever)
This should work in both GitLab and GitHub
The text was updated successfully, but these errors were encountered:
aexvir
changed the title
Mr Automation
Pull request automation
May 2, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Similar to GitLab's merge trains, but without the hassle of having to use merge request pipelines nor merge commits
Initially, this should be about merging commits automatically as long as checks/CI is passing. Internally we'll use some queue mechanism where we'll stack commits to be merged there. For each MR in the queue, we'll take it, rebase it on master, wait for checks and merge if they pass.
In the future we might add more configurability to it, like commands in the PR to alter the order, multiple strategies for when one MR in the queue can't be rebased, possibility of enabling/disabling this functionality on a per PR bases (with labels, or command or whatever)
This should work in both GitLab and GitHub
The text was updated successfully, but these errors were encountered: