No branches in non-bare repository #1644

Closed
opened 2025-11-02 04:08:13 -06:00 by GiteaMirror · 3 comments
Owner

Originally created by @Governa on GitHub (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.

Originally created by @Governa on GitHub (Mar 22, 2018). - Gitea version (or commit ref): 05abd03 - Git version: 2.15.0 - Operating system: Ubuntu - Database (use `[x]`): - [ ] PostgreSQL - [x] MySQL - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [x] 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.
GiteaMirror added the type/bug label 2025-11-02 04:08:13 -06:00
Author
Owner

@Bwko commented on GitHub (Mar 27, 2018):

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

@Bwko commented on GitHub (Mar 27, 2018): Is this bug present in the latest master (4c6e170ceb56a8c316e523dd44137fa02ca29735)? I've created a new repo (without branches) and pushed a tag, but no 500.
Author
Owner

@lunny commented on GitHub (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.

@lunny commented on GitHub (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.
Author
Owner

@melekhine commented on GitHub (Feb 6, 2019):

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.

@melekhine commented on GitHub (Feb 6, 2019): 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.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#1644