Extra entry for previous commit on dashboard with "git push --mirror" #2184

New Issue

GiteaMirror · 2025-11-02T04:26:26-06:00

GiteaMirror commented

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

Originally created by @markshep on GitHub (Aug 13, 2018).

Gitea version (or commit ref): 1.5.0
Git version: 2.18.0
Operating system: Debian GNU/Linux 9.5
Database (use [x]):
- PostgreSQL
- MySQL
- MSSQL
- SQLite
Can you reproduce the bug at https://try.gitea.io:
- Yes: https://try.gitea.io/markshep/duplicate-dashboard-entries
- No
- Not relevant
Log gist:
?

Description

When a client/downstream repo has a post-commit hook that invokes "git push --mirror origin" then whenever a push happens two new entries will appear on the dashboard. There's the expected one for the commit that just happened, but then an extra one that refers to the previous commit, but with with "refs/remotes/origin/master" listed as the branch rather than just "master".

Screenshots

Originally created by @markshep on GitHub (Aug 13, 2018). - Gitea version (or commit ref): 1.5.0 - Git version: 2.18.0 - Operating system: Debian GNU/Linux 9.5 - Database (use `[x]`): - [ ] PostgreSQL - [ ] MySQL - [ ] MSSQL - [x] SQLite - Can you reproduce the bug at https://try.gitea.io: - [x] Yes: https://try.gitea.io/markshep/duplicate-dashboard-entries - [ ] No - [ ] Not relevant - Log gist: ? ## Description When a client/downstream repo has a post-commit hook that invokes "git push --mirror origin" then whenever a push happens two new entries will appear on the dashboard. There's the expected one for the commit that just happened, but then an extra one that refers to the previous commit, but with with "refs/remotes/origin/master" listed as the branch rather than just "master". ## Screenshots ![phontom](https://user-images.githubusercontent.com/490067/44025557-61a03a8e-9ee8-11e8-94fb-d3ab81eac589.png)

GiteaMirror added the type/question issue/stale labels 2025-11-02 04:26:26 -06:00

GiteaMirror closed this issue

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

GiteaMirror commented

2025-11-02 04:26:27 -06:00

@stale[bot] commented on GitHub (Jan 14, 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 (Jan 14, 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 commented

2025-11-02 04:26:27 -06:00

@markshep commented on GitHub (Feb 2, 2019):

Closing as this seems to be fixed now. I think the fix happened somewhere between 1.6.4 and 1.7.0.

(Dunno why this issue was marked as a question - it isn't!)

@markshep commented on GitHub (Feb 2, 2019): Closing as this seems to be fixed now. I think the fix happened somewhere between 1.6.4 and 1.7.0. (Dunno why this issue was marked as a question - it isn't!)

GiteaMirror referenced this issue

2025-11-02 12:06:32 -06:00

[PR #2184] [MERGED] Only allow token authentication with 2FA enabled #16276

GiteaMirror referenced this issue

2025-11-02 12:13:06 -06:00

[PR #2700] [MERGED] fix .netrc authentication #16544

Sign in to join this conversation.