Git commits refuse to show up in the web interface #1603

New Issue

2025-11-02T04:06:19-06:00

GiteaMirror commented

2025-11-02 04:06:19 -06:00

Originally created by @adelowo on GitHub (Mar 6, 2018).

Gitea version (or commit ref): 1.4.0+rc2 (bug exists in 1.4.0+rc1 )
Git version: 1.8
Operating system: centos
Database (use [x]):
- PostgreSQL
- MySQL
- MSSQL
- SQLite
Can you reproduce the bug at https://try.gitea.io:
- Yes (provide example URL)
- No
- Not relevant

Couldn't use the demo (try.gitea.io) as it kept on throwing a HTTP 500 error

Description

When creating a repository, there is this Initialize this repository with selected files and template_ checkbox, I just noticed that checking or doing otherwise actually impacts the way gitea functions. If I refuse to check the box, my commits do not show up in the web interface but they do if the box is checked.

I looked into the logs, there isn't a trace of failure or whatever. I also did a cat $GITEADB/org/repo.git/refs/heads/master, it gave me the commit hash which is ( obviously ) the same with what I have locally. The only amazing thing is I still get the empty repository page.

I was able to replicate this 3 times ( on 3 newly created repositories ). But if I check the box, the commits show up in the UI. I am not sure if there is a regression somewhere but I want to believe I must created repositories without checking the box prior to making use of v1.4.0rc-1

Originally created by @adelowo on GitHub (Mar 6, 2018).  - Gitea version (or commit ref): 1.4.0+rc2 (bug exists in 1.4.0+rc1 ) - Git version: 1.8 - Operating system: centos - Database (use `[x]`): - [x] PostgreSQL - [ ] MySQL - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [ ] No - [ ] Not relevant > Couldn't use the demo (`try.gitea.io`) as it kept on throwing a `HTTP` 500 error ## Description When creating a repository, there is this ___Initialize this repository with selected files and template____ checkbox, I just noticed that checking or doing otherwise actually impacts the way gitea functions. If I refuse to check the box, my commits do not show up in the web interface but they do if the box is checked. I looked into the logs, there isn't a trace of failure or whatever. I also did a `cat $GITEADB/org/repo.git/refs/heads/master`, it gave me the commit hash which is ( obviously ) the same with what I have locally. The only amazing thing is I still get the empty repository page. I was able to replicate this 3 times ( on 3 newly created repositories ). But if I check the box, the commits show up in the UI. I am not sure if there is a regression somewhere but I want to believe I must created repositories without checking the box prior to making use of `v1.4.0rc-1`

GiteaMirror added the issue/duplicate label 2025-11-02 04:06:19 -06:00

GiteaMirror closed this issue

2025-11-02 04:06:19 -06:00

GiteaMirror commented

2025-11-02 04:06:19 -06:00