Stacked GitHub PRs: Auto-switch between "single" and "overlap" workflows - #1408
Open
rejc2 wants to merge 2 commits into
Open
Stacked GitHub PRs: Auto-switch between "single" and "overlap" workflows#1408rejc2 wants to merge 2 commits into
rejc2 wants to merge 2 commits into
Conversation
|
This pull request has been imported. If you are a Meta employee, you can view this in D115309565. (Because this pull request was imported automatically, there will not be any future comments.) |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When submitting stacked GitHub PRs, automatically switch between "single" and "overlap" workflows based on whether the repo is a fork or not.
Because the SINGLE workflow matches the pattern needed for GitHub's native PR stacks, it makes for a good default.
However, the SINGLE workflow generally doesn't work across repo forks – the OVERLAP workflow is needed here, which is why it is the current default.
This PR automatically switches between the SINGLE workflow (by default) for non-forked repos, and the OVERLAP workflow for forked repos. (The original config stays in place, so OVERLAP workflow can still be chosed for all repos, but the default is SINGLE.)
("SINGLE" workflow means each PR in the stack targets the head of the PR below it in the stack; "OVERLAP" workflow means every PR targets the
mainbranch.)