This repository has been archived by the owner on Jan 5, 2024. It is now read-only.
Add a new workflow to generate release on tag push #164
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This way, when running `git push --tags`, after appropriately tagging a commit as `vx.y.z`, a GitHub release page will be created titled `vx.y.z` (that is, the name of the tag) and with two pieces of contents: - the title and body of the tagged commit. This assumes that the commit message is properly sanitized, so its inclusion in the release page is worthwhile and/or informative - the changelog since the last tag, assuming semver GitHub gives a higher priority to releases than to tags. Releases show up on the side of the repository, can have special triggers for workflows, can be subscribed to (so that downstream users will know to update). The last item is especially relevant since dependency update bots (e.g., Dependabot) can be configured to look for releases of GitHub actions used in the workflows of a repository and update them when these change. This is especially useful if the upstream actions are pinned by hash instead of by short tag name (as recommended by supply-chain security best guidelines -- not implemented here, as the goal is to follow the setup of the other actions). Tested on https://github.com/mihaimaruseac/actions/releases Prompted by discussion on #148, after closing. Signed-off-by: Mihai Maruseac <[email protected]>
Signed-off-by: Mihai Maruseac <[email protected]>
andreasabel
added
pr: squash-me
re: releases
|
Thanks Mihai @mihaimaruseac! |
|
@mihaimaruseac : I like this "auto-release" workflow! This is the first result: https://github.com/haskell/actions/releases/tag/v2.3.0 Nice! |
|
This is awesome! |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This way, when running
git push --tags, after appropriately tagging a commit asvx.y.z, a GitHub release page will be created titledvx.y.z(that is, the name of the tag) and with two pieces of contents:GitHub gives a higher priority to releases than to tags. Releases show up on the side of the repository, can have special triggers for workflows, can be subscribed to (so that downstream users will know to update). The last item is especially relevant since dependency update bots (e.g., Dependabot) can be configured to look for releases of GitHub actions used in the workflows of a repository and update them when these change. This is especially useful if the upstream actions are pinned by hash instead of by short tag name (as recommended by supply-chain security best guidelines -- not implemented here, as the goal is to follow the setup of the other actions).
Tested on https://github.com/mihaimaruseac/actions/releases
Prompted by discussion on #148, after closing.
Signed-off-by: Mihai Maruseac [email protected]