tylermilner
commented
3 months ago It looks like being able to treat manually cancelled workflow runs as non-failures is a requested feature, but hasn't been implemented yet:
- https://github.com/orgs/community/discussions/8336
- https://github.com/orgs/community/discussions/27174
As a workaround, I removed the step that cancelled the workflow run using the GitHub CLI if no changes were detected.
Now the status badge shows as "Passing":
The workflow run also shows as passing now:
Clicking into the run shows that the deployment job was actually skipped:
The above behavior is in contrast to when the workflow run was manually cancelled, which showed the run as being skipped/cancelled:
It looks like the "Deploy" badge in the README might be red due to the workflow being skipped when no changes are detected. We need to see if we can consider "skipped" as "passed" or just make the workflow pass if no deployment needs to happen (as it recently was).