Repository navigation
gh pr create --fill-from and --fill-latest arguments #8163
Description
Activity
@brawaru Thanks for opening this feature request. This is something the team discussed when talking about adding the
--fill-firstflag and we were unable to come up with a decision at that time. I am going to add the discuss label here so that the team can have another talk about if we want to support this feature.Reacted by Sasha Sorokin- added and removed
on Oct 12, 2023 @brawaru The team discussed this at length and while we can understand the desire for the functionality, at this time we are lot looking to support it. We are very hesitant to add additional
--filloptions as that is one of our most controversial features with everyone wanting their pull request to be filled in differently. I added this issue to our tracking issue #7575 for the various issues we want to address with thepr createcommand. I am going to leave this issue open for discovery purposes and for other community members to comment on.
Describe the feature or problem you’d like to solve
I like to chain pull requests, which is very nice when, for example, you want to merge dependencies updates, and then stack fixes for these for updates on top, having each middle branch checked, before they all lend into master.
Unfortunately, in these cases creating pull requests with
gh pris quite annoying, because it cannot auto-fill the title and message. There is--filland--fill-first, but they aren't useful, because--fillwon't provide a useful message, and the first commit will be first merged PR.Proposed solution
I think having
--fill-from=<commit>and--fill-latestarguments will be useful. With--fill-from, CLI would automatically pick the title and message using a specific commit, whereas--fill-latestwould use the message from the latest commit.Additional context
N/A