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
Goal: remove the need for the
🚂 PR trainPR which follows another one.
label.
Context
Merge trains as we use them today, while reducing PR size, are hard to track and are blocking progress. With merge queues I would hope to not have to track connected PRs anymore because they're in the queue and will be merged when appropriate.
This discussion was converted from issue #4253 on December 13, 2024 10:31.
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-a-merge-queue
Goal: remove the need for the 🚂 PR trainPR which follows another one.
label.
Context
Merge trains as we use them today, while reducing PR size, are hard to track and are blocking progress. With merge queues I would hope to not have to track connected PRs anymore because they're in the queue and will be merged when appropriate.
Beta Was this translation helpful? Give feedback.
All reactions