-
Notifications
You must be signed in to change notification settings - Fork 7
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
We are requesting help to disable branch protection rules for django-fsm-log #368
Comments
@jezdez Sorry to mention you. I don't see an alternative that doesn't involve your direct support. Or maybe, someone else has access to the branch protection rules settings ? |
Sorry for the long delay. I've just removed Python 3.7 from the required CI checks. The best solution without removing branch protection outright is to use someting like https://github.com/re-actors/alls-green. Removing branch protection completely isn't a good idea, sadly (due to malicious actors in Jazzband). You should be able to roll out something like alls-green now with the maintainer permissions to the repo I just gave the project leads. Can you verify this? |
Thanks a lot @jezdez, I didn't know about this project. I will definitely try to take advantage of it. I'll get my hands on it in the following days. |
@ticosax feel free to tag me if you face challenges integrating it! |
Hi,
Over time, the branch protection rules, that expect some checks related to python versions, might become obsolete. Like observed in this pull request.
jazzband/django-fsm-log#192
I'm suggesting to disable the branch protection rules, if only the roadies can keep them up to date. Unless the maintainers can control them, in that case it should probably become a maintainer responsibility, in order to remove dependency on the roadies for such ongoing tasks.
Thanks.
The text was updated successfully, but these errors were encountered: