Commits log remains blank. #574

New Issue

GiteaMirror · 2025-11-02T03:28:37-06:00

GiteaMirror commented

2025-11-02 03:28:37 -06:00

Originally created by @MNickelson on GitHub (Mar 25, 2017).

Gitea version (or commit ref): 1.1.0+75-g6a451a2b
Git version: 2.8.3
Operating system: Docker (latest), Debian testing host
Database (use [x]):
- PostgreSQL
- MySQL
- MSSQL
- SQLite
Can you reproduce the bug at https://try.gitea.io:
- Yes (provide example URL)
- No
- Not relevant
Log gist:

Description

When I create a new repository I can push/pull and everything seems to be working, but the commit log never updates (when I go to the code tab I see the Quick Guide and how to clone the repo).
I saw a similar issue with gogs when the first push used ssh but was able to work around it by using http. Neither way seems to help with gitea.

Originally created by @MNickelson on GitHub (Mar 25, 2017). - Gitea version (or commit ref): 1.1.0+75-g6a451a2b - Git version: 2.8.3 - Operating system: Docker (latest), Debian testing host - Database (use `[x]`): - [ ] PostgreSQL - [ ] MySQL - [ ] MSSQL - [X] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [X] No - [ ] Not relevant - Log gist: ## Description When I create a new repository I can push/pull and everything seems to be working, but the commit log never updates (when I go to the code tab I see the Quick Guide and how to clone the repo). I saw a similar issue with gogs when the first push used ssh but was able to work around it by using http. Neither way seems to help with gitea.

GiteaMirror added the type/question issue/stale labels 2025-11-02 03:28:37 -06:00

GiteaMirror closed this issue

2025-11-02 03:28:37 -06:00

GiteaMirror commented

2025-11-02 03:28:38 -06:00

@lunny commented on GitHub (Mar 26, 2017):

Do you have follow the upgrade docs? https://docs.gitea.io/en-us/upgrade-from-gogs/

@lunny commented on GitHub (Mar 26, 2017): Do you have follow the upgrade docs? https://docs.gitea.io/en-us/upgrade-from-gogs/

GiteaMirror commented

2025-11-02 03:28:38 -06:00

@MNickelson commented on GitHub (Mar 26, 2017):

I didn't actually end up running an upgrade from GoGs, since I'm using docker and didn't have too many repositories yet, I just started over with a fresh container. Repositories that are mirrored from github seem to work fine, it's newly created Gitea repositories that are having this issue.

I did just go check the directory structure and app.ini file just to be sure though, and everything there seems to be in order.

@MNickelson commented on GitHub (Mar 26, 2017): I didn't actually end up running an upgrade from GoGs, since I'm using docker and didn't have too many repositories yet, I just started over with a fresh container. Repositories that are mirrored from github seem to work fine, it's newly created Gitea repositories that are having this issue. I did just go check the directory structure and app.ini file just to be sure though, and everything there seems to be in order.

GiteaMirror commented

2025-11-02 03:28:38 -06:00

@lunny commented on GitHub (Mar 26, 2017):

And there is any log?

@lunny commented on GitHub (Mar 26, 2017): And there is any log?

GiteaMirror commented

2025-11-02 03:28:38 -06:00

@MNickelson commented on GitHub (Mar 26, 2017):

I cleared out gitea/log then created and pushed to a new repository.
It created an empty serv.log file and an xorm.log file that has 5 SQL select statments and one update statement that doesn't look particularly interesting, but I can upload if it might help.

@MNickelson commented on GitHub (Mar 26, 2017): I cleared out gitea/log then created and pushed to a new repository. It created an empty serv.log file and an xorm.log file that has 5 SQL select statments and one update statement that doesn't look particularly interesting, but I can upload if it might help.

GiteaMirror commented

2025-11-02 03:28:38 -06:00

@MNickelson commented on GitHub (Oct 21, 2017):

I found part of the problem.
If I have "Initialize this repository with selected files and template" when it is created in gitea everything works as expected, but merging in my original branch is giving problems.
If that box is not checked I never see anything in the commit log.

@MNickelson commented on GitHub (Oct 21, 2017): I found part of the problem. If I have "Initialize this repository with selected files and template" when it is created in gitea everything works as expected, but merging in my original branch is giving problems. If that box is not checked I never see anything in the commit log.

GiteaMirror commented

2025-11-02 03:28:38 -06:00

@stale[bot] commented on GitHub (Feb 11, 2019):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

@stale[bot] commented on GitHub (Feb 11, 2019): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

GiteaMirror referenced this issue

2025-11-02 03:33:15 -06:00

Feature: Upload Files in Wiki Pages #687

GiteaMirror referenced this issue

2025-11-02 03:45:24 -06:00

Add attachments to Wiki pages #1015

GiteaMirror referenced this issue

2025-11-02 05:09:23 -06:00

Unify issue and wiki editors #3346

GiteaMirror referenced this issue

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

Unify issue and wiki editors #3346