after update release, commit id and release time not change
See original GitHub issueDescribe the bug
after update release, artifacts, body can be changed, but commit id and github-actions released time not change.
To Reproduce
- uses: ncipollo/release-action@v1
with:
token: ${{ secrets.GITHUB_TOKEN }}
tag: "test"
commit: master
allowUpdates: true
replacesArtifacts: true
removeArtifacts: true
artifacts: "test.zip"
body: |
test
Expected behavior update commit id and release time
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:6 (1 by maintainers)
Top Results From Across the Web
Gerrit error when Change-Id in commit messages are missing
You have to change the messages of every commit that you are pushing to include the change id ( using git filter-branch )...
Read more >Change-Ids - Gerrit Code Review
Change -Ids are created at commit time on the client side. A standard 'commit-msg' hook is provided by Gerrit, and can be installed...
Read more >Git Basics: Adding more changes to your last commit - Medium
With this post you'll learn how to modify your last commit, adding (or removing) some changes. You can also follow this tutorial to...
Read more >Chapter 21 Git Version Control - Bioconductor Packages
A minimal workflow is to checkout, update, commit, and push changes to your ... If you do not use the command to get...
Read more >git-tag Documentation - Git
git tag [-n[<num>]] -l [--contains <commit>] [--no-contains <commit>] ... a release tag from you, you cannot just change the tag for them by...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

use a workaround to update commit id and time, delete it before
release-actionby usedev-drprasad/delete-tag-and-releaseHi!
Unfortunately the described behavior is outside the scope of this action. This action primarily focuses on the management of the release, not the tag associated with the release. Github won’t use the commit hash if the tag associated with the release already exists: https://docs.github.com/en/rest/reference/repos#update-a-release
I think your best bet would be to have a separate action in your work flow which updates the tag prior to the release action running. Something like
git checkout <branch>;git tag -f <tag>;git push -f <tag>.