GitHub Actions on.push.tags glob does not match the pushed tag
on.push.tags filters by tag-name glob. If the pattern does not match the pushed tag exactly - missing a prefix, wrong wildcard, or a v that is not there - the workflow is never triggered for that tag.
What this error means
Pushing a tag does not start the workflow even though it has an on.push.tags trigger.
github-actions
on:
push:
tags: ['v*.*.*']
# pushed tag 'release-1.2.3' does not match -> no runCommon causes
Glob does not match the tag scheme
v*.*.* requires a leading v and three dot-separated segments; other schemes do not match.
Pushing branch, not tag
A push that does not create/update a tag ref never satisfies on.push.tags.
How to fix it
Broaden or correct the tag glob
- Match the actual tag naming with a correct glob (e.g. v* or a more permissive pattern).
- Test against a real tag name before relying on it.
.github/workflows/release.yml
on:
push:
tags:
- 'v[0-9]+.[0-9]+.[0-9]+'
- 'release-*'Ensure the tag is actually pushed
- Push tags explicitly with git push origin <tag> or git push --tags.
- Confirm the ref appears under refs/tags on the remote.
How to prevent it
- Align the tags glob with your real tag naming convention.
- Push tags explicitly so the tag ref event fires.
Related guides
GitHub Actions Workflow Not Triggering - Fix the on: BlockFix a GitHub Actions workflow that never runs - wrong on: events, path or branch filters that exclude your ch…
GitHub Actions GITHUB_REF_NAME contains a slash and breaks tag-derived namesFix downstream tagging or naming that breaks because github.ref_name contains a slash from a hierarchical ref.
GitHub Actions "No event triggers defined in 'on'"Fix GitHub Actions "No event triggers defined in `on`" - an empty, null, or malformed on: block means the wor…