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
Similar story to how gha-merge-up action did not trigger the gha-ci action, instead we needed to "manually" trigger the gha-ci via a githubaction call
We should be able to do this within the action-ci.yml workflow - just do a step to validate that the repo starts with "gha-" has the auto-tag.yml workflow before triggering auto-tag
There's an existing card to deal with that #96 - we need this one merged first though because it has the 'workflow_dispatch' event added to the action. Will close this card since everything is merged
Similar story to how gha-merge-up action did not trigger the gha-ci action, instead we needed to "manually" trigger the gha-ci via a githubaction call
We should be able to do this within the action-ci.yml workflow - just do a step to validate that the repo
starts with "gha-"has the auto-tag.yml workflow before triggering auto-tag--
Example workflow run: https://github.com/emteknetnz/gha-issue/actions/runs/5887182035
PRs
The text was updated successfully, but these errors were encountered: