I have a workflow that triggers on push branches:
steps: - uses: actions/checkout@v2 - uses: <some simple git tag action> - name: Push Version Update run: git push origin --follow-tags
Now the job is successful, the push tag step is successful, and I see the tag in the remote repository. However, a subsequent workflow to publish does not get triggered:
on: push: tags: ['v*']
If I manually create a tag and push it to the remote, the on.tags workflow will trigger.
I believe this is related to some internal Actions mechanism as to avoid workflow infinite loops. I realize I could be butchering the adoption of Actions with this approach. any ideas or suggestions as to how to properly adopt this type of workflow using Actions, where one workflow creates a tag and pushes it back to its repository, which can then be observed and trigger another flow?