Skip to content
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

No branches in non-bare repository #3704

Closed
2 of 7 tasks
Governa opened this issue Mar 22, 2018 · 3 comments · Fixed by #4923
Closed
2 of 7 tasks

No branches in non-bare repository #3704

Governa opened this issue Mar 22, 2018 · 3 comments · Fixed by #4923
Labels
Milestone

Comments

@Governa
Copy link

Governa commented Mar 22, 2018

  • Gitea version (or commit ref): 05abd03
  • Git version: 2.15.0
  • Operating system: Ubuntu
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No (Unavailable right now, but probably yes)
    • Not relevant
  • Log gist:

Description

If an user creates a repository and don't push any branches to it(just tags for example) Gitea shows an 500 error.

The problem is that it is not clear for the user why the error is being shown and what to do to solve it. Even worse is that it makes it difficult to delete the repository and try again.

@lunny lunny added the type/bug label Mar 22, 2018
@Bwko
Copy link
Member

Bwko commented Mar 27, 2018

Is this bug present in the latest master (4c6e170)?
I've created a new repo (without branches) and pushed a tag, but no 500.

@lunny
Copy link
Member

lunny commented Sep 13, 2018

After #4923 merged. When a repo has tags but not branches, 500 will be disappeared but the releases tab isn't displayed. I will open another issue to improve the situation.

@melekhine
Copy link

Have this issue with one of the repos, think it was empty. This happened after I switches docker image tag from latest to 1.7.

@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.

4 participants