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
To finish porting the current Azure Pipeline to GitHub Actions, which we used as an opportunity to split off the tagging into its own GitHub workflow (tag-git, we need to teach the /git-artifacts command to trigger that tag-git workflow, and upon successful completion trigger the git-artifacts workflow runs (one per architecture).
To finish porting the current Azure Pipeline to GitHub Actions, which we used as an opportunity to split off the tagging into its own GitHub workflow (
tag-git
, we need to teach the/git-artifacts
command to trigger thattag-git
workflow, and upon successful completion trigger thegit-artifacts
workflow runs (one per architecture).This requires the GitForWindowsHelper to pay attention not only to queued and completed Windows/ARM64 workflow jobs but also to completed workflow runs.
And to make things more transparent, we need to update the comment that reported that the workflow runs were started, much like #9 suggests.
The text was updated successfully, but these errors were encountered: