Repository navigation
ci: manual release via workflow_dispatch tag input - #3
Merged
Merged
Conversation
Direct tag pushes are not always possible; workflow_dispatch now accepts a tag name and action-gh-release creates the tag together with the release.
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Permet de publier une release manuellement :
workflow_dispatchaccepte désormais un nom de tag, etaction-gh-releasecrée le tag en même temps que la release (utile quand le push direct de tags n'est pas possible). Le comportement sur push de tagv*est inchangé.🤖 Generated with Claude Code
https://claude.ai/code/session_01XmGfBz6k1Z8YFPitFjuEGp
Generated by Claude Code