-
Notifications
You must be signed in to change notification settings - Fork 129
Mark pull request as depending on another #959
Comments
related #210 |
It would be nice if the branch to which the PR is targeted even automagically updated:
|
Also after merging branch cache still shows changes from dependent branch |
This is a feature that I really miss from Gerrit. It's more common for me to have pull requests that depend on other pull requests than to have isolated pull requests. |
This is the workflow I imagined also. The dependant PR should follow the merge of its dependency. |
Fwiw, I had requested something similar directly from Github in 2016:
They told me that they'd consider it:
|
This is especially annoying when the repo you're contributing to can take weeks to review / merge, and devs are left having to somehow manually keep track of the follow-up changes instead of getting completed work into the pipeline and move on with their life. |
Is it normal that an issue has been open for over a year? |
This is just an unofficial "ideas" repo. GitHub doesn't officially follow these issues. |
GitHub should make it so that if a dependency PR was merged, all dependent PRs that had that merged PR's branch as a base should automatically have their base branches changed to that of the merged PR. This way it would become really straight-forward to merge PRs in a bottom to top approach (merging PRs closer to |
@amcsi commented on November 29, 2018 11:07 AM:
Agreed. The need for this auto-rebase (or at least auto-change-base) feature was also noted in #950. |
These might help: |
So is there any chance that we're getting this |
Wonder if this "early next year for stacked diffs" tweet by Nat has anything to do with this discussion: https://twitter.com/natfriedman/status/1170804894241972224 |
Here's a GitHub action that does this: https:/marketplace/actions/pr-dependency-check |
FYI, I just released Dependent Issues 🎉 . The successor of the 3 years old DEP bot. It's a GitHub action that lets you mark a PR or an issue as dependent on another. It works with cross-repository dependencies as well. Check the repo for more info: https:/z0al/dependent-issues |
For what it's worth, it's now also a feature in Mergify. When using the merge action, which enables automatic merge, it'll respect |
Also suffering from these same stacked pull request headaches, I wrote a client side tool that manages pull request stacks for you automagically. |
Are you going to clone this proposal to https:/github/feedback/discussions ? |
@oprogramador commented on July 6, 2021 3:52 AM:
This was already done, so please don't submit a duplicate - thanks ;-) |
Thanks. |
@oprogramador commented on July 8, 2021 7:51 PM:
No worries. But that exactly proves the importance of GitHub doing this migration properly, and quickly. Please can you link to the discussion you filed, and also close it with an explanation which links to community/community#4477 and to here? |
I haven't opened any discussion related to this issue. |
Ah I see, by "I submitted this" I guess you meant "I wrote the above comment" rather than "I submitted a new discussion topic". I misunderstood it as meaning the latter. |
Yes, I meant posting a comment. |
It would be stupidly easy to implement this feature but yet this issue is open for a decade. 2021! |
@webzorg There are a few custom solutions:
The GitHub team can't possibly be expected to implement every possible feature that everyone wants. That's why they gave the open source community access to GitHub APIs, GitHub Actions, and GitHub Apps. If there are community-run solutions out there, I encourage you to use them. And if they don't exist, make them! |
... Dependency-check from me |
Thanks, added to the list. I'll use that list if similar discussions arise. EDIT: Here's the discussion on the official GitHub feedback repo: community/community#4477 (comment) |
Quite often I find myself raising a pull request that contains another within it as a dependency. I want the diff to be exclusive of the dependency pull request’s changes, otherwise my colleagues end up reviewing more than they need to, or worse, the same changes twice (in both pull requests).
To workaround this, I usually set the base of my pull request to the dependency pull request, however this has caveats:
I would like to see some UI in GitHub to make this workflow first class:
The text was updated successfully, but these errors were encountered: