yes, we should disable force push for the default branch (master) everywhere by default. not sure if we have modules where the default branch is not called master.
regarding erics remark: > It would be better if that could somehow be made the default for the sling > organization instead of having to change hundreds of .asf.yaml files. there is not "sling" organization on github. there is only a single "apache" organization which we share with all other asf projects. so we have to deal with each repo sepaerately in its .asf.yaml files. stefan > -----Original Message----- > From: Konrad Windszus <k...@apache.org> > Sent: Wednesday, April 30, 2025 3:31 PM > To: dev@sling.apache.org > Subject: Disable force push on default branch > > Hi, > It seems that a git force push on the main branch is not disabled by > default for the Apache repositories. > However I would strongly suggest to enforce this. > This seems to require a dedicated item within the .asf.yaml for each > repository (https://github.com/apache/infrastructure-asfyaml?tab=readme- > ov-file#branch-protection): > > ... > github: > protected_branches: > master: {} > … > > This will not add any additional branch protection but just the basic > disable force push (IIUC). > WDYT about adding this to all our .asf.yaml’s? > Do we use the branch name “master” consistently as default branch for all > our repos? > > Thanks for your comments, > Konrad
