Skip to content
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

Enable "Require branches to be up to date before merging" #3744

Open
pponnuvel opened this issue Aug 8, 2024 · 0 comments
Open

Enable "Require branches to be up to date before merging" #3744

pponnuvel opened this issue Aug 8, 2024 · 0 comments

Comments

@pponnuvel
Copy link
Contributor

Sometimes commits can reintroduce pylint issues accidentially when it was already fixed in main.

Can we enable https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/managing-protected-branches/about-protected-branches#require-status-checks-before-merging

so that all PRs are up to date?

I think it's a good idea in general, not just for preventing pylint issues, to have this so that any PR passes all tests with the latest code.

To enable it:
[Settings]->Branches->main->"Require status checks to pass before merging" + "Require branches to be up to date before merging".

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant