Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Possible to tag the last commit rather than generate a new commit? #907

Closed
JeffersonBledsoe opened this issue May 30, 2022 · 0 comments · Fixed by #911
Closed

Possible to tag the last commit rather than generate a new commit? #907

JeffersonBledsoe opened this issue May 30, 2022 · 0 comments · Fixed by #911

Comments

@JeffersonBledsoe
Copy link

Using GitHub actions, I'd like to be able to create a preRelease version every merge into my project's main branch by tagging whatever the previous commit was with a certain version. In theory, I should be able to do something like this to achieve that : npx release-it --preRelease --ci --git.commitMessage="" --git.commitArgs="--amend -C HEAD", however release-it currently seems to always configure a message commit even if I specify an empty message. Is it possible to be able to tag the previous commit version with release-it currently?

Came across release-it recently and it's been great!
@blzsaa blzsaa mentioned this issue Jun 16, 2022
Merged
webpro pushed a commit that referenced this issue Jun 21, 2022
@blzsaa
feat(git): make commitMessage optional parameter in git commit (#911)
f730eb6 
Due to git.commitMessage being optional t is now possible to amend previous commit instead of
creating a new one.

Example usage:
release-it minor --git.commitArgs='--amend --no-edit' --git.commitMessage=''

closes #907

Co-authored-by: blzsaa <blzsaa@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

feat(git): make commitMessage optional parameter in git commit
1 participant
@JeffersonBledsoe