Thanks for the input. Removing the protection is it straightforward and doesn’t require ASF INFRA involvement. You just temporarily change the asf.yaml again (as outlined in https://github.com/apache/infrastructure-asfyaml?tab=readme-ov-file#branchpro). Meanwhile the GitHub branch protection is also applied to GitBox (through the same .asf.yaml directive)
However I don’t have any experience with those mass repository changes as I struggle a bit with the repo tool. Is there any volunteer who can help/perform the changes (the actual steps are described in https://github.com/apache/sling-aggregator?tab=readme-ov-file#updating-the-asfyaml-files) Thanks, Konrad > On 2. May 2025, at 12:27, Robert Munteanu <romb...@apache.org> wrote: > > On Wed, 2025-04-30 at 11:51 -0700, Eric Norman wrote: >> Also, we may need to think of the process to handle the exceptions to >> that >> rule if a force push is temporarily necessary for some special case. > > That is a good point. I think the the only way out is to ask ASF Infra > to remove branch protection. We should document that in the Git with > Sling [1] page. > > [1]: > https://cwiki.apache.org/confluence/display/SLING/Using+Git+with+Sling
