I rarely push to master (only minor doc fixes and changes to my own
code, which no one would care anyhow) so the change does not effect me
much, but I don't think
"Require branches to be up to date before merging"
option should be toggled, this just creates friction for no real
benefit, I am going to turn that back off, I think you might have it on
by mistake, if not I'd like an argument as to why it should be toggled...
*Luca Toniolo*
On 9/17/2026 7:56 AM, Rene Hopf via Emc-developers wrote:
Due to the recent events on github, I have turned on branch protection
on github. This means that everything that goes into master must go
through a PR, like we all have agreed to for a long time.
This gives other developers a chance to review and talk about your
changes. Now it is enforced by github. The changes have been reverted.
Same applies for 2.x branches.
René
_______________________________________________
Emc-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/emc-developers
_______________________________________________
Emc-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/emc-developers
