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
{{ message }}
This repository has been archived by the owner on Mar 8, 2023. It is now read-only.
I ran into the situation where I didn't want to publish anything on merge to master, but I did want to redeploy the docs using primer/deploy, but because the version in package.json for the package hadn't changed, the publish Action exited with a neutral status, which stopped the primer/deploy Action from running.
Is it possible to exit with a status that doesn't stop any other Actions from running? I figured that was the point of neutral statuses but I guess not!
I ran into the situation where I didn't want to publish anything on merge to master, but I did want to redeploy the docs using primer/deploy, but because the version in package.json for the package hadn't changed, the publish Action exited with a neutral status, which stopped the primer/deploy Action from running.
Is it possible to exit with a status that doesn't stop any other Actions from running? I figured that was the point of neutral statuses but I guess not!
https://github.com/primer/blueprints/runs/66380774
The text was updated successfully, but these errors were encountered: