-
Notifications
You must be signed in to change notification settings - Fork 156
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
Specify release title #1682
Labels
Comments
@yegor256 What do you think? |
@volodya-lombrozo I like this one:
|
@yegor256 What about the default behaviour? Do you want to leave it as is (== "the last commit message")? |
@volodya-lombrozo yes, it would be most logical, since there could be users who expect this behavior |
volodya-lombrozo
added a commit
to volodya-lombrozo/rultor
that referenced
this issue
May 13, 2023
volodya-lombrozo
added a commit
to volodya-lombrozo/rultor
that referenced
this issue
May 13, 2023
volodya-lombrozo
added a commit
to volodya-lombrozo/rultor
that referenced
this issue
May 13, 2023
volodya-lombrozo
added a commit
to volodya-lombrozo/rultor
that referenced
this issue
May 13, 2023
volodya-lombrozo
added a commit
to volodya-lombrozo/rultor
that referenced
this issue
May 13, 2023
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As far as I know, when Rultor creates a release, the release has a name of the last commit, for example like:
It's not so beautiful and I have to search for the tag that was attached to that release, I believe it would be better to give more meaningful name to a release, for example:
Also we can allow to pass the custom release name in rultor command:
The text was updated successfully, but these errors were encountered: