#1230 Create a pull request from an existing pull request on a different branch
Closed: Won't Fix a year ago by wombelix. Opened 7 years ago by bruno.

For fedora-kickstarts it is somewhat common to want to do a cherry-picked version of a change for one branch, on a second. It would be convenient if Pagure had an easy way to create a rebased version of a pull request for another branch. This doesn't provide anything you can't do yourself, but it can save some time. I don't know if enough people would use it to justify the development work, but it would be nice to have eventually.


This sounds interesting so what you want is to make a PR with the same changes to a different branch just to check things right ? This will be like opening two different PR for same changes in different branch , I feel it will be a little confusing :tongue: ! Lets see what @pingou has to say on that.

It is not just to check things. We often want to apply the same changed to the branch corresponding to branched and the branch corresponding to rawhide without merging the branches together. It might be rare for projects to have two active development branches going at the same time, but it could also be used for backporting fixes, which is a bit more mainstream.
This would essentially provide an easy way to cherry pick fixes to other branches.

I see the issue there, so maybe all we need is a page/form allowing to specify the input branch and the target branch from the list of all available branches.

This would allow you to open 2 PRs from the same origin to two different target branches.

Does that sound right?

I'm not sure of the exact semantics you are suggesting. I'm not looking to have the same fork merged into two different branches. Want I want is the fork being merged into one branch, and same changes being made (after rebase) to another branch. For the single commit case this would be a cherry pick.

The last update was 6 years ago, no further requests, updates or actionable tasks since then, I'm going to close this issue for now to reduce our backlog.

Metadata Update from @wombelix:
- Issue close_status updated to: Won't Fix
- Issue status updated to: Closed (was: Open)

a year ago

Login to comment on this ticket.

Metadata