Skip to content
Discussion options

You must be logged in to vote

GitHub blocks events created with GITHUB_TOKEN from triggering new workflow runs, so a tag pushed inside a workflow will not start another workflow. This is intentional and can’t be overridden.

If you need the tag to trigger a release workflow, the only supported option is to use a fine-grained PAT stored as a secret (repo or org). Otherwise, keep the entire release process in a single workflow instead of relying on a second workflow triggered by the tag.

User accounts don’t have org-level secrets, so PAT rotation must be done per repo.

Replies: 2 comments

Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Answer selected bylaur89
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment
Category
Actions
Labels
ActionsBuild, test, and automate your deployment pipeline with world-class CI/CDQuestionAsk and answer questions about GitHub features and usageWorkflow ConfigurationTopics about workflow files, YAML setup, job dependencies, and general workflow configuration issuesMiscGeneral discussions about GitHub Actions that don't fit other found themes.
3 participants
@laur89@omaarjb@devahmadshoukat