-
-
Notifications
You must be signed in to change notification settings - Fork 5.9k
Description
Feature Description
I would like to suggest PR retargeting functionality. Meaning: If PR B targets branch A, and PR C targets branch (/PR) B, merging PR B into A would cause the target of PR C to automatically change from B to A.
See also the description on the same github functionality .
The use case is enabling a developer to split up a PR into more manageable pieces. Say we are developing a large piece of functionality with both back-end ( featureA
) and front-end ( featureB
) components. One could write the featureA
, targeting a project's main
branch. Once this functionality exists, a front-end developer could use this as a starting point for featureB
. Targeting the project's main
branch would not work, since this does not yet contain the (unreviewed) back-end functionality. And continuing in the back-end branch would create a larger PR than needed, making the review process more difficult.
My current workaround is that featureB
branches from featureA
, but targets main
. However, this makes featureB
impossible to review before featureA
has been completely reviewed and merged, because otherwise the featureB
PR will also contain the changes in featureA
.
Would also solve #19190 (See this comment specifically, suggesting the same idea).
Screenshots
No response