New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
gh pr create
Add option to use first commit as PR title/description
#7239
Comments
Since |
What if the option accepted an arg, or if it were a new option, in order to avoid a breaking change? |
We discussed this and we're open to People who want to help us implement this can start here: cli/pkg/cmd/pr/create/create.go Lines 483 to 484 in 8460a70
|
If Expectation:
Please let me know if I am missing out anything. |
This comment was marked as spam.
This comment was marked as spam.
@kousikmitra: that sounds almost correct, just a clarification: if |
Got it. Will raise a PR soon. |
It would be nice if you could specific a commit and have it default to HEAD |
It doesn't default to HEAD but the first commit of the difference |
For example, I might do the main work first and then do some other refactoring work that I want to keep separate as additional work afterwards (spacing changes, rearranging lists, etc). I'd like to be able to specify the first commit I did for the |
Describe the feature or problem you’d like to solve
gh pr create --fill
has a good default if you only have a single commit: it creates a PR with the commit's details as title/description. However I generally write my first commit's message knowing that it will be used as the PR title/desc and will have follow-up commits that I expect will be squashed at some point. When usinggh pr create --fill
when there are multiple commits, it uses the branch name as PR title and the list of git commit titles as the PR description.Proposed solution
Add a CLI option that will always fill the PR title/description using only the first commit's message. This won't disrupt the default and helps support a different and reasonable workflow.
The text was updated successfully, but these errors were encountered: