We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
You might want to configure CircleCI tests to run on pull requests, and mark them as requirements for merging.
Mostly this one: https://circleci.com/docs/2.0/enable-checks/
Background info:
https://docs.github.com/en/github/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks
https://docs.github.com/en/github/administering-a-repository/defining-the-mergeability-of-pull-requests/about-protected-branches#require-status-checks-before-merging
That way, you know whether tests run before merging 😄
The text was updated successfully, but these errors were encountered:
No branches or pull requests
You might want to configure CircleCI tests to run on pull requests, and mark them as requirements for merging.
Mostly this one: https://circleci.com/docs/2.0/enable-checks/
Background info:
https://docs.github.com/en/github/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks
https://docs.github.com/en/github/administering-a-repository/defining-the-mergeability-of-pull-requests/about-protected-branches#require-status-checks-before-merging
That way, you know whether tests run before merging 😄
The text was updated successfully, but these errors were encountered: