-
-
Notifications
You must be signed in to change notification settings - Fork 612
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
Require branches to be up to date before merging #1085
Comments
kindly ping @jezdez |
@atugushev which of the status check should be required to be passing (as mentioned in the help text to the "Require branches to be up to date before merging")? Status checks found in the last week for this repository: |
@jezdez I wouldn't require any of that, because the coverage could be decreased or tests failed (canceled for example) for any unimportant reason and it could be inappropriate to block merge on that. |
Okay... Let's try these two then:
|
For GitHub Actions I add an all:
name: All
runs-on: ubuntu-latest
needs:
- test
- linting
steps:
- name: This
shell: python
run: |
import this |
@atugushev Done. |
What's the problem this feature will solve?
Currently, the master might be broken by merging a PR that has not been tested with the latest code. I believe we could adjust the repository settings to avoid this issue.
Describe the solution you'd like
Update the repository settings to protect the master branch:
Additional context
#824 (comment)
The text was updated successfully, but these errors were encountered: