This workflow will be automatically launched on a published release.
It finds regex (GIT_TAG) [0-9a-f]+ in README.md and replaces the git tag with the one which is relevant for the created release.
So basically the workflow will do something like this:
This way there will be no need to update the tag manually and therefore repository users will not have to additionally verify latest release tag.
I have also replaced current 0817715923c9705e68994eb52ef9df3f6845beba tag in readme with the most recent released 3b15fa82ea74739b574d705fea44959b58142eb8 so there is no need to create a new release once the changes are merged.
Note that the workflow uses third-party Action for committing changes: stefanzweifel/git-auto-commit-action@v5
This workflow will be automatically launched on a published release. It finds regex
(GIT_TAG) [0-9a-f]+in README.md and replaces the git tag with the one which is relevant for the created release.So basically the workflow will do something like this:
This way there will be no need to update the tag manually and therefore repository users will not have to additionally verify latest release tag.
I have also replaced current
0817715923c9705e68994eb52ef9df3f6845bebatag in readme with the most recent released3b15fa82ea74739b574d705fea44959b58142eb8so there is no need to create a new release once the changes are merged.Note that the workflow uses third-party Action for committing changes:
stefanzweifel/git-auto-commit-action@v5