Skip to content

Fix bug the protected branch rule name is conflicted with renamed branch name (#36650)#36661

Merged
silverwind merged 1 commit into
go-gitea:release/v1.25from
GiteaBot:backport-36650-v1.25
Feb 17, 2026
Merged

Fix bug the protected branch rule name is conflicted with renamed branch name (#36650)#36661
silverwind merged 1 commit into
go-gitea:release/v1.25from
GiteaBot:backport-36650-v1.25

Conversation

@GiteaBot

Copy link
Copy Markdown
Collaborator

Backport #36650 by @lunny

Fix #36464

@GiteaBot GiteaBot added the lgtm/need 2 This PR needs two approvals by maintainers to be considered for merging. label Feb 17, 2026
@GiteaBot GiteaBot added this to the 1.25.5 milestone Feb 17, 2026
@GiteaBot GiteaBot added lgtm/need 1 This PR needs approval from one additional maintainer to be merged. and removed lgtm/need 2 This PR needs two approvals by maintainers to be considered for merging. labels Feb 17, 2026
@GiteaBot GiteaBot added lgtm/done This PR has enough approvals to get merged. There are no important open reservations anymore. and removed lgtm/need 1 This PR needs approval from one additional maintainer to be merged. labels Feb 17, 2026
@silverwind silverwind enabled auto-merge (squash) February 17, 2026 21:09
@silverwind silverwind merged commit 216cf96 into go-gitea:release/v1.25 Feb 17, 2026
26 checks passed
@go-gitea go-gitea locked as resolved and limited conversation to collaborators May 19, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

lgtm/done This PR has enough approvals to get merged. There are no important open reservations anymore. type/bug

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants