Thanks, Rain, for the information. I’ve tried both cases (with and without protected_branches), but I still can’t create a 'release-' prefixed branch. I guess some of the original branch protection rules were not removed during the repo migration. I may seek help from Infra. Thanks again.
On Fri, Dec 5, 2025 at 4:08 PM Rain Yu <[email protected]> wrote: > Hmm. If you have defined a branch name in protected_branches, I think you > won’t be able to push to it. You should remove the branch name from > protected_branches. By the way, you can find more information here: > https://github.com/apache/infrastructure-asfyaml/blob/main/README.md. I > know this because the infra team sent an email to the Dubbo community > earlier. ^v^ > > Yonny Hao <[email protected]> 于2025年12月5日周五 15:48写道： > > > Hi all, > > > > I’m preparing the 4.0.0-incubating RC release and ran into an issue with > > creating a new release branch on GitHub. > > > > Historically, before the project entered the Apache Incubator, the > > repository had branch protection rules configured for release-* branches. > > After migration into the Apache org, these rules remained, but I no > longer > > have access to GitHub repository settings to adjust them. To resolve > this, > > I updated our .asf.yaml to explicitly declare: > > > > > protected_branches: > > > main: > > > ... > > > *release-v4.0: {} # release branch for 4.0.x-incubating* > > > > According to the ASF Infra documentation, this should override previous > > GitHub configurations. However, after waiting ~30 minutes for the Infra > bot > > to apply the update, I still cannot push or create the release-v4.0 > branch, > > receiving the same protection error (“must not contain merge commits / > not > > authorized to push”). > > > > Before opening an INFRA ticket, I’d like to check here: > > > > *Is there anything I might be missing regarding .asf.yaml branch > > protection, or any additional steps required for the change to take > > effect?* > > > > Any guidance from mentors or anyone familiar with this mechanism would be > > greatly appreciated. > > > > Thanks, > > -- > > Yonny(Yu) Hao > > > -- Yonny(Yu) Hao
