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 Apr 4, 2024. It is now read-only.
We have some jobs that don't always run. We work in a monorepo and there is a lot of code in the repo not specifically related to our main application, so when nothing in the application actually changes, there is little point in actually running the very long running test suites.
I sucessfully setup GitHub Actions to skip these jobs if nothing in the app code has changed, but this seems to confuse bors which still expects them to run. Maybe some option like status_if_exists? Not sure how difficult it would be to implement, but I imagine it might be fairly trivial 🤞
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
We have some jobs that don't always run. We work in a monorepo and there is a lot of code in the repo not specifically related to our main application, so when nothing in the application actually changes, there is little point in actually running the very long running test suites.
I sucessfully setup GitHub Actions to skip these jobs if nothing in the app code has changed, but this seems to confuse bors which still expects them to run. Maybe some option like
status_if_exists
? Not sure how difficult it would be to implement, but I imagine it might be fairly trivial 🤞The text was updated successfully, but these errors were encountered: