Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow jumping the merge train #259

Closed
bertptrs opened this issue Apr 12, 2024 · 1 comment · Fixed by #260
Closed

Allow jumping the merge train #259

bertptrs opened this issue Apr 12, 2024 · 1 comment · Fixed by #260
Assignees

Comments

@bertptrs
Copy link

Sometimes, a fix needs to go out now, and waiting orderly in the queue isn't the best thing to do. It can make sense to reduce throughput of the overall merge train by letting a single commit

I propose we add a NOW or similarly dramatic suffix to all commands that cause a merge (and potentially a tag/deploy) that allows a PR to become the head of the merge train.

This invalidates any progress made on building the existing merge train, but I believe that's an acceptable trade-off for incidental use.

CC @rkrzr

Tangentially related to #253 which also tries to address this; I think we need both.

@Riscky
Copy link

Riscky commented Apr 12, 2024

and potentially a tag/deploy

We should also add a field in the commit message to convey this information to deployment software, like we did with Auto-deploy for example (perhaps Priority?).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants