First of all really nice github action, everything in one action that one can need for updating git from Github action.
However we have a small issue with the tag updating feature. Our use case is to commit updated version in package.json file and generated changelog file when ever Github Release is made. So we naturally would also like to update the tag to point to the latest commit. However since this action first deleted the tag and then re-creates it Github will change the release back to draft state (deleting of the tag causes this).
So is there a reason why this action deletes the tag first and then creates it again? It would be much better if it would just force push the tag.
Of course we can always use another action to update the tag or set the release back to published state, but would be much nicer to be able to do everything in one step.
First of all really nice github action, everything in one action that one can need for updating git from Github action.
However we have a small issue with the tag updating feature. Our use case is to commit updated version in package.json file and generated changelog file when ever Github Release is made. So we naturally would also like to update the tag to point to the latest commit. However since this action first deleted the tag and then re-creates it Github will change the release back to draft state (deleting of the tag causes this).
So is there a reason why this action deletes the tag first and then creates it again? It would be much better if it would just force push the tag.
Of course we can always use another action to update the tag or set the release back to published state, but would be much nicer to be able to do everything in one step.