Skip to content

Wrong label on branch dropdown #3525

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
1 of 3 tasks
vbrandl opened this issue Feb 17, 2018 · 1 comment · Fixed by #3715
Closed
1 of 3 tasks

Wrong label on branch dropdown #3525

vbrandl opened this issue Feb 17, 2018 · 1 comment · Fixed by #3715
Labels
Milestone

Comments

@vbrandl
Copy link

vbrandl commented Feb 17, 2018

  • Gitea version (or commit ref): 1.3.2
  • Git version: 2.11.0
  • Operating system: Debian 9
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No
    • Not relevant

https://try.gitea.io/foobar42/test-repository

Description

When pushing a non-default branch (e.g. everything except master) to an empty repository, the dropdown menu for branch selection is wrongly labeled master. The dropdown menu shows the correct branches.

On further investigation I noticed that the link to the commits for the current branches links to https://try.gitea.io/foobar42/test-repository/commits/branch/master which produces a 404 error.

Also visiting the branches overview (https://try.gitea.io/foobar42/test-repository/branches/) lists master as default branch (which does not exist) but does not list the develop branch.

In general it seems like the UI gets confused when there is only one branch which at the same time is not the default branch.

Screenshots

@lunny
Copy link
Member

lunny commented Feb 20, 2018

should be fixed by #3190

@lunny lunny added this to the 1.5.0 milestone Apr 12, 2018
@go-gitea go-gitea locked and limited conversation to collaborators Nov 24, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants