Respository's home page not updated after first push #2851

Closed
opened 2025-11-02 04:51:10 -06:00 by GiteaMirror · 4 comments
Owner

Originally created by @FloMiau on GitHub (Feb 2, 2019).

  • Gitea version (or commit ref): 1.7.0
  • Git version: 2.17.1
  • Operating system: Ubuntu 18.04 LTS
  • 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

I think it is the same problem as in Issue #3458

The fix was:
https://github.com/go-gitea/gitea/issues/3458#issuecomment-381531981

Screenshots

Originally created by @FloMiau on GitHub (Feb 2, 2019). <!-- 1. Please speak English, this is the language all of us can speak and write. 2. Please ask questions or configuration/deploy problems on our Discord server (https://discord.gg/NsatcWJ) or forum (https://discourse.gitea.io). 3. Please take a moment to check that your issue doesn't already exist. 4. Please give all relevant information below for bug reports, because incomplete details will be handled as an invalid report. --> - Gitea version (or commit ref): 1.7.0 - Git version: 2.17.1 - Operating system: Ubuntu 18.04 LTS - Database (use `[x]`): - [ ] PostgreSQL - [x] MySQL - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [ ] No - [x] Not relevant - Log gist: ## Description I think it is the same problem as in Issue #3458 The fix was: https://github.com/go-gitea/gitea/issues/3458#issuecomment-381531981 ## Screenshots <!-- **If this issue involves the Web Interface, please include a screenshot** -->
GiteaMirror added the issue/stale label 2025-11-02 04:51:11 -06:00
Author
Owner

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

any more details?

@lunny commented on GitHub (Feb 6, 2019): any more details?
Author
Owner

@Sebazzz commented on GitHub (Mar 28, 2019):

We noticed this happening after a migration from SVN to gittea using Subgit.

@Sebazzz commented on GitHub (Mar 28, 2019): We noticed this happening after a migration from SVN to gittea using Subgit.
Author
Owner

@stale[bot] commented on GitHub (May 27, 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 (May 27, 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.
Author
Owner

@stale[bot] commented on GitHub (Jun 10, 2019):

This issue has been automatically closed because of inactivity. You can re-open it if needed.

@stale[bot] commented on GitHub (Jun 10, 2019): This issue has been automatically closed because of inactivity. You can re-open it if needed.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#2851