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
I've noticed failures of the "publish" job (and therefore apparently "failing" CI) on my fork and on my PR builds.
These will always fail, and it would be better to skip the job in these contexts to get clearer feedback.
I believe that the job should be guarded with an if that looks to make sure it's running on funcx-faas/funcX@main.
The GitHub env vars and workflow expression language should make this possible.
To Reproduce
Fork the repo
Create a new branch off of main with no changes
Push to your fork
GitHub will email you a build failure
Expected behavior
Since the new branch is taken off of main, you would expect a passing build.
The text was updated successfully, but these errors were encountered:
Describe the bug
I've noticed failures of the "publish" job (and therefore apparently "failing" CI) on my fork and on my PR builds.
These will always fail, and it would be better to skip the job in these contexts to get clearer feedback.
I believe that the job should be guarded with an
if
that looks to make sure it's running onfuncx-faas/funcX@main
.The GitHub env vars and workflow expression language should make this possible.
To Reproduce
main
with no changesExpected behavior
Since the new branch is taken off of
main
, you would expect a passing build.The text was updated successfully, but these errors were encountered: