Can't find branch named "QA" as a target for merging PR #12317

New Issue

2025-11-02T10:05:24-06:00

GiteaMirror commented

2025-11-02 10:05:24 -06:00

Originally created by @retched on GitHub (Jan 9, 2024).

Description

There is a branch within my repo named QA. It has been receiving pushes and pulls for the duration of the last two months at a minimum.

Trying to use the web portal to accept and a merge request but I cannot set "QA" as a target that PR.

I can't even find the branch named "QA" in the branch listing BUT I can visit the QA branch page by directly typing the web address to it into my browser. But I cannot select it in any way.

Gitea Version

1.21.3

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

No response

Screenshots

Git Version

2.43.0

Operating System

Windows

How are you running Gitea?

Self Hosted, using the pre-built download "gitea-1.21.3-gogit-windows-4.0-amd64.exe"

Database

SQLite

Originally created by @retched on GitHub (Jan 9, 2024). ### Description There is a branch within my repo named `QA`. It has been receiving pushes and pulls for the duration of the last two months at a minimum. Trying to use the web portal to accept and a merge request but I cannot set "QA" as a target that PR. I can't even find the branch named "QA" in the branch listing BUT I can visit the QA branch page by directly typing the web address to it into my browser. But I cannot select it in any way. ### Gitea Version 1.21.3 ### Can you reproduce the bug on the Gitea demo site? No ### Log Gist _No response_ ### Screenshots ![image](https://github.com/go-gitea/gitea/assets/1572532/4a093f94-0662-462a-bd3b-f47fb5da22be) ![image](https://github.com/go-gitea/gitea/assets/1572532/9f4ac48e-b705-4916-8073-94279ac0aa28) ![image](https://github.com/go-gitea/gitea/assets/1572532/1ed4455a-6950-4c14-8893-915a7f5f2bfc) ### Git Version 2.43.0 ### Operating System Windows ### How are you running Gitea? Self Hosted, using the pre-built download "gitea-1.21.3-gogit-windows-4.0-amd64.exe" ### Database SQLite

GiteaMirror added the issue/needs-feedback label 2025-11-02 10:05:24 -06:00

GiteaMirror closed this issue

2025-11-02 10:05:24 -06:00

GiteaMirror commented

2025-11-02 10:05:25 -06:00

@KN4CK3R commented on GitHub (Jan 10, 2024):

From your screenshot it looks like you are trying to search for Rebirth:QA but the repo is called bin?

@KN4CK3R commented on GitHub (Jan 10, 2024): From your screenshot it looks like you are trying to search for `Rebirth:QA` but the repo is called `bin`?

GiteaMirror commented

2025-11-02 10:05:25 -06:00

@retched commented on GitHub (Jan 10, 2024):

Even typing in just QA yields the same:

Again, there is a branch named QA... I can navigate to it by using the direct URL.... but the name QA is missing from all views and switches. Even trying to make a branch named QA yields an error.

@retched commented on GitHub (Jan 10, 2024): Even typing in just QA yields the same: ![image](https://github.com/go-gitea/gitea/assets/1572532/a6e2fdc6-2617-448c-aff4-1b0f060c1132) Again, there is a branch named QA... I can navigate to it by using the direct URL.... but the name QA is missing from all views and switches. Even trying to make a branch named QA yields an error.

GiteaMirror commented

2025-11-02 10:05:25 -06:00

@lunny commented on GitHub (Jan 16, 2024):

Please sync the branches on admin panel first. This maybe caused by a previous bug but fixed.
And a further bug fixes has been merged into 1.22 but it's difficult to be backported to 1.21 which can fix the Case Insensitive problems about branch names.

@lunny commented on GitHub (Jan 16, 2024): Please sync the branches on admin panel first. This maybe caused by a previous bug but fixed. And a further bug fixes has been merged into 1.22 but it's difficult to be backported to 1.21 which can fix the Case Insensitive problems about branch names.

GiteaMirror commented

2025-11-02 10:05:26 -06:00

@retched commented on GitHub (Jan 29, 2024):

Updated to 1.21.4 and ran the sync branches options on the admin. That seemed to fix it. Can see it now on the listing. Will close as resolved.

@retched commented on GitHub (Jan 29, 2024): Updated to 1.21.4 and ran the sync branches options on the admin. That seemed to fix it. Can see it now on the listing. Will close as resolved.

GiteaMirror commented

2025-11-02 10:05:26 -06:00

@github-actions[bot] commented on GitHub (Feb 29, 2024):

Automatically locked because of our CONTRIBUTING guidelines

@github-actions[bot] commented on GitHub (Feb 29, 2024): Automatically locked because of our [CONTRIBUTING guidelines](https://github.com/go-gitea/gitea/blob/main/CONTRIBUTING.md#issue-locking)

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#12317