Repository navigation
Allow setting commit title defaults in gh repo edit #8320
Description
Describe the feature or problem you’d like to solve
I would like to be able to call gh repo edit ... to set these flags on the repository:
- Allow squash merging (
--enable-squash-merge):squash_merge_commit_title=PR_TITLE|COMMIT_OR_PR_TITLEsquash_merge_commit_message=PR_BODY|COMMIT_MESSAGES|BLANK
- Allow merge commits (
--enable-merge-commit):merge_commit_title=PR_TITLE|MERGE_MESSAGEmerge_commit_message=PR_BODY|PR_TITLE|BLANK
Note: ignore use_squash_pr_title_as_default as it's deprecated.
Proposed solution
Modify https://github.com/cli/cli/blob/trunk/pkg/cmd/repo/edit/edit.go
Augment gh repo edit --enable-squash-merge option to allow for values other than =false, e.g. --enable-squash-merge=pr-title-and-body. Same for --enable-merge-commit.
or
Create 4 new separate options to mirror the Repository REST API.
Additional context
Issue is about setting these dropdowns from CLI:
For SEO the values of the dropdown are:
- Default message
- Default to pull request title
- Default to pull request title and commit details
- Default to pull request title and description
Activity
samcoe commentedon Nov 13, 2023
@TWiStErRob Thanks for the feature request, I think it would make a nice improvement to allow for setting the default title and body for squash and merge commits. I do not think that changing the
--enable-squash-mergeand--enable-merge-commitflags is the right approach though. I think that would overload those flags making them confusing along with being a backwards incompatible change.I would rather have flags that match the API
--squash-merge-commit-title,--squash-merge-commit-message,--merge-commit-title, and--merge-commit-message. What do you think?TWiStErRob commentedon Nov 13, 2023
I was thinking of augmenting because there's a dependency between the merge type (e.g. squash) being on and the title/body setting. Although nothing preventing us from setting the body/title and then turning the merge type off, so maybe the dependency is only on the UI.
Your argument makes sense though, that's what I meant by "4 separate options". Happy to get the ability in any way. :)
igallart commentedon Feb 8, 2024
Hi, is there any date if it will be implemented? I think it is important when you want to switch to many repositories massively.
VOVELEE commentedon Feb 13, 2024
Any updates? It will be nice feature for batch changes
arifbalik commentedon Aug 7, 2024
I would love to see this added for the new release
BagToad commentedon Feb 4, 2025
A PR to resolve this was merged, but quickly reverted because #10363 (comment)
Closing as duplicate of #10092 because that is where the current core team has discussed and produced more thorough Acceptance Criteria for this feature.