-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ci: split tests and coverage #286
Conversation
@supernovahs would it be possible to allow PRs to be merged without the "Generate Coverage" check passing? That way external contributors can skip it (since it uses secrets they don't have access to). |
696cb59
to
cc167d4
Compare
checking if there's a setting like this in github |
I think leaving that job out of the "Required" list of jobs is enough. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'll disable it once this gets merged in main
Fixes # ### What Changed? Fireblocks tests don't work for external contributors. This PR splits the test run in the CI into two: "Run Tests" and "Generate Coverage". The idea is to have the first one run without fireblocks, while the second one runs with it and is not required for merge. ### Reviewer Checklist - [ ] New features are tested and documented - [ ] PR updates the changelog with a description of changes - [ ] PR has one of the `changelog-X` labels (if applies) - [ ] Code deprecates any old functionality before removing it
Fixes #
What Changed?
Fireblocks tests don't work for external contributors. This PR splits the test run in the CI into two: "Run Tests" and "Generate Coverage". The idea is to have the first one run without fireblocks, while the second one runs with it and is not required for merge.
Reviewer Checklist
changelog-X
labels (if applies)