Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Error 422: Validation Failed: `{"resource":"Release","code":"already_exists","field":"tag_name"}`
See original GitHub issueIs your feature request related to a problem? Please describe. If the tag and release already exists the action fails. Is there a way to just ignore updating the release if the action fails? Here, is the configuration of my action:-
Run ncipollo/release-action@58ae73b360456532aafd58ee170c045abbeaee37
with:
allowUpdates: false
prerelease: false
artifactErrorsFailBuild: true
removeArtifacts: false
replacesArtifacts: false
token: ***
tag: <tag_name>
body: <body>
artifacts: <artifact_path>
Describe the solution you’d like We don’t want the action to fail the workflow but just omit overwriting the release.
Describe alternatives you’ve considered Considered skipping the action completely if the tag/release exists but cannot find any git command or any other suitable way to do it in github actions workflow since we want to publish the release the first time if it does not exists.
Additional context Add any other context or screenshots about the feature request here.
Issue Analytics
- State:
- Created a year ago
- Comments:11 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
It will create the tag only if it doesn’t exist. Either way that error is coming from github and indicating either the tag name is invalid or it already exists.
I added a
skipIfReleaseExistsinput which you can set to true. This will cause the action to bail if the release already exists.