-
Notifications
You must be signed in to change notification settings - Fork 7.8k
Closed
Labels
bugSomething isn't workingSomething isn't workinggh-prrelating to the gh pr commandrelating to the gh pr commandp2Affects more than a few users but doesn't prevent core functionsAffects more than a few users but doesn't prevent core functions
Description
Describe the bug
Relates #8423
In the latest release 2.44.0, the behavior of gh pr create has changed in a way that breaks my most common workflow. What I want to do is this: create a PR with sensible defaults for title and body (based on the commits) and edit the body before submitting it. This was the old default behavior, and when the branch only contained one commit, the PR title would be the commit headline. Now the default PR title is the branch name, which is rarely as descriptive.
I appreciate the --fill-verbose and --fill-first options, and would use them, but using any of the --fill* options leads to the PR being created straight away with no ability to edit the body.
$ gh --version
gh version 2.44.0 (2024-02-12)
https://github.com/cli/cli/releases/tag/v2.44.0
Steps to reproduce the behavior
- Have a branch with a single commit
gh pr createorgh pr create --fill-first
Expected vs actual behavior
Expected behavior:
- The PR title is set to the commit headline
- We can edit the body locally before creating the PR
OR
- We can use
--fill-firstor--fill-verboseto influence how the title and body are set - We can edit the body locally before creating the PR
Actual:
- If no
--fill*option is provided, the PR title defaults to the branch name - If a
--fill*option is provided, there is no ability to edit the body, the PR is created instantly.
dlandis, mscrivo, peplin and heathsdlandis
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't workinggh-prrelating to the gh pr commandrelating to the gh pr commandp2Affects more than a few users but doesn't prevent core functionsAffects more than a few users but doesn't prevent core functions