Behavior of --title when creating a release #12650
-
|
I’m trying to understand how automatic title generation works when creating a release. When I create a release locally using the CLI and do not explicitly specify a title (while targeting a manually specified repository), the release title consistently defaults to the tag name. However, when I create a release from a GitHub Action using the CLI without explicitly specifying a title and with a tag checked out in the repository, the behavior is inconsistent. In some cases, the title defaults to the tag name; in others, it uses the commit message instead. I’d appreciate any insight into what determines this behavior and what I should expect in each scenario. Thanks! |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
|
I don't have the time to double check right now but I think this is related to whether you have one or more commits in the PR. One commit results in commit message as title, more than one commit results in tag/branch name as title. Does that sound right to you? |
Beta Was this translation helpful? Give feedback.
-
|
Ahh, brilliant, that is exactly the difference. Thank you very much! |
Beta Was this translation helpful? Give feedback.
I don't have the time to double check right now but I think this is related to whether you have one or more commits in the PR. One commit results in commit message as title, more than one commit results in tag/branch name as title. Does that sound right to you?