Allow customizing commit message pattern in prepare-release command#996
Merged
AArnott merged 4 commits intodotnet:mainfrom Nov 15, 2023
Merged
Allow customizing commit message pattern in prepare-release command#996AArnott merged 4 commits intodotnet:mainfrom
prepare-release command#996AArnott merged 4 commits intodotnet:mainfrom
Conversation
…ve as default value "{0}" before the default was null and had error on some unit test
Contributor
Author
|
@dotnet-policy-service agree |
FernandoCalmet
approved these changes
Nov 9, 2023
wchoque
approved these changes
Nov 9, 2023
AArnott
changed the title
prepare-release command
AArnott
requested changes
Nov 10, 2023
Collaborator
AArnott
left a comment
AArnott
left a comment
There was a problem hiding this comment.
I like it. Just a few changes please. The design change idea (about reducing what {0} is replaced with) is just an idea. It's at your discretion.
…message pattern to customize all the message
AArnott
force-pushed
the
enhancement991
branch
from
f62eaec to
b63cb81
Compare
FernandoCalmet
approved these changes
Nov 15, 2023
wchoque
reviewed
Nov 15, 2023
AArnott
force-pushed
the
enhancement991
branch
from
b63cb81 to
33ef3ef
Compare
Contributor
Author
|
@AArnott, do you know when it will be published in the new release? |
Collaborator
|
I can issue a prerelease to nuget.org if that will suffice for you. |
Contributor
Author
|
Yes, please. It will be great. Thanks |
Collaborator
This was referenced Aug 1, 2025
This was referenced Aug 15, 2025
This was referenced Sep 22, 2025
This was referenced Sep 29, 2025
This was referenced Oct 24, 2025
This was referenced Jan 16, 2026
This was referenced Jan 23, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
By default, the
prepare-releasecommand generates a commit message with the format "Set version to {version}". So with this new option, You can add a prefix or suffix to the default commit message (which will replace just the version).For example, running the following command on
masterSo your commit message is going to be this:
Note: Must include {0} in the pattern to represent the version.
closes #991