Closed jamacku closed 2 years ago
Thanks for this issue.
I have to create an automation, how to do it as soon as PR is merged.
The tag v1
is still moving manually, but trying to find out an action for it.
@phracek You can try something like this: https://github.com/redhat-plumbers-in-action/differential-shellcheck/blob/main/.github/workflows/publish-release.yml
Just exclude release-drafter action. Then when you publish new minor tag, major tag will get automatically updated.
See how publish-release.yml works. Issue https://github.com/release-drafter/release-drafter/issues/1073
sclorg/testing-farm-as-github-action@v1
is now working
Currently documentation shows an example of using
testing-farm-as-github-action
assclorg/testing-farm-as-github-action@v1
. But since there is no tagv1
this will resolve with following error:As noted in https://github.com/sclorg/testing-farm-as-github-action/pull/19#issue-1123969843 you need to add tag
v<major-version>
in order to use it like that. If not, users need to reference the exact minor version, at the moment it'sv1.1
and then setup dependabot to automatically look for updates.From Docs:
We recommend creating releases using semantically versioned tags – for example, v1.1.3 – and keeping major (v1) and minor (v1.1) tags current to the latest appropriate commit. For more information, see "About custom actions" and "About semantic versioning".