You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
GitHub Actions runner fails to trigger workflows when multiple tags are pushed simultaneously using git push --tags. The workflow only triggers successfully when pushing a single tag.
To Reproduce
Create workflow with tag trigger:
on:
push:
tags:
- releases/**
Create multiple tags:
git tag releases/v1.0.0
git tag releases/v1.0.1
Push tags: git push --tags
Observe: No workflow runs are triggered
Expected behavior
Workflow should trigger for each matching tag pushed, regardless of whether tags are pushed individually or in bulk.
Runner Version and Platform
Runner: Latest GitHub-hosted runner
OS: Ubuntu-latest
What's not working?
When pushing multiple tags simultaneously, no workflows are triggered despite tags matching the pattern. Same workflow triggers correctly when tags are pushed individually.
Job Log Output
N/A - Issue is that jobs don't trigger at all with multiple tags.
Runner and Worker's Diagnostic Logs
N/A - No logs available as runners aren't initiated.
The text was updated successfully, but these errors were encountered:
Describe the bug
GitHub Actions runner fails to trigger workflows when multiple tags are pushed simultaneously using
git push --tags
. The workflow only triggers successfully when pushing a single tag.To Reproduce
git push --tags
Expected behavior
Workflow should trigger for each matching tag pushed, regardless of whether tags are pushed individually or in bulk.
Runner Version and Platform
What's not working?
When pushing multiple tags simultaneously, no workflows are triggered despite tags matching the pattern. Same workflow triggers correctly when tags are pushed individually.
Job Log Output
N/A - Issue is that jobs don't trigger at all with multiple tags.
Runner and Worker's Diagnostic Logs
N/A - No logs available as runners aren't initiated.
The text was updated successfully, but these errors were encountered: