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
The merging of PR #232 should have triggered the Release workflow, which then should have created a tag that would trigger the Build workflow on that tag. Neither of these things happened.
To Reproduce
Steps to reproduce the behavior:
Push a commit to the release branch.
See if the Release action is triggered.
Expected behavior
The Release workflow runs and creates a new tag and a new GitHub release. The tag triggers the Build workflow on that tagged commit. The build runs, then the use tests run, then the artifacts are uploaded to the GitHub Release.
Additional context
I worked around the problem by manually triggering the Release workflow on the release branch, and then manually triggering the Build workflow on the new tag.
The text was updated successfully, but these errors were encountered:
Describe the bug
The merging of PR #232 should have triggered the Release workflow, which then should have created a tag that would trigger the Build workflow on that tag. Neither of these things happened.
To Reproduce
Steps to reproduce the behavior:
release
branch.Expected behavior
The Release workflow runs and creates a new tag and a new GitHub release. The tag triggers the Build workflow on that tagged commit. The build runs, then the use tests run, then the artifacts are uploaded to the GitHub Release.
Additional context
I worked around the problem by manually triggering the Release workflow on the
release
branch, and then manually triggering the Build workflow on the new tag.The text was updated successfully, but these errors were encountered: