Using deploy key with write access, commits not counted #2394

New Issue

GiteaMirror · 2025-11-02T04:34:41-06:00

GiteaMirror commented

2025-11-02 04:34:41 -06:00

Originally created by @Exagone313 on GitHub (Oct 9, 2018).

Gitea version (or commit ref): 1.5.2
Git version: 2.19.1
Operating system: Arch Linux
Database (use [x]):
- PostgreSQL
- MySQL
- MSSQL
- SQLite
Can you reproduce the bug at https://try.gitea.io: don't want to register :/
- Yes (provide example URL)
- No
- Not relevant
Log gist: irrelevant, nothing special?

Steps to reproduce

Set up a new SSH key as deploy key with write access to a repo (try with both an empty and non empty repo)
Make one (or more) commit and push

Expected result

Nothing abnormal, it counts all the commits

Actual result

Commit count is off by one (or more)
Files may not be shown (!) if there is no commit made by a real user, it'll show the initial Quick Guide

Screenshots

Originally created by @Exagone313 on GitHub (Oct 9, 2018). - Gitea version (or commit ref): 1.5.2 - Git version: 2.19.1 - Operating system: Arch Linux - Database (use `[x]`): - [x] PostgreSQL - [ ] MySQL - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: don't want to register :/ - [ ] Yes (provide example URL) - [ ] No - [ ] Not relevant - Log gist: irrelevant, nothing special? ## Steps to reproduce * Set up a new SSH key as deploy key with write access to a repo (try with both an empty and non empty repo) * Make one (or more) commit and push ## Expected result * Nothing abnormal, it counts all the commits ## Actual result * Commit count is off by one (or more) * Files may **not** be shown (!) if there is no commit made by a real user, it'll show the initial *Quick Guide* ## Screenshots ![screen shot 2018-10-09 at 21 19 57-fullpage](https://user-images.githubusercontent.com/11819703/46699390-2c9c1a80-cc09-11e8-8845-cf4ad255c195.png)

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

GiteaMirror closed this issue

2025-11-02 04:34:41 -06:00

GiteaMirror commented

2025-11-02 04:34:42 -06:00

@techknowlogick commented on GitHub (Oct 9, 2018):

Closing as duplicate of #4424

@techknowlogick commented on GitHub (Oct 9, 2018): Closing as duplicate of #4424

GiteaMirror commented

2025-11-02 04:34:42 -06:00

@Exagone313 commented on GitHub (Oct 9, 2018):

Ok, sorry, I didn't find this issue although I searched, but too many open issues.

@Exagone313 commented on GitHub (Oct 9, 2018): Ok, sorry, I didn't find this issue although I searched, but too many open issues.

GiteaMirror commented

2025-11-02 04:34:42 -06:00

@techknowlogick commented on GitHub (Oct 9, 2018):

@Exagone313 that's ok, the important thing is at least you searched.

@techknowlogick commented on GitHub (Oct 9, 2018): @Exagone313 that's ok, the important thing is at least you searched.

GiteaMirror commented

2025-11-02 04:34:43 -06:00

@zeripath commented on GitHub (Feb 4, 2019):

This should be fixed by #5935 and its backport to v1.7 #5944

@zeripath commented on GitHub (Feb 4, 2019): This should be fixed by #5935 and its backport to v1.7 #5944

GiteaMirror commented

2025-11-02 04:34:43 -06:00

@Exagone313 commented on GitHub (Feb 4, 2019):

I just had a quick look at the PR and I don't think it's going to fix actual repos. But maybe it just requires a new push or a new commit.

@Exagone313 commented on GitHub (Feb 4, 2019): I just had a quick look at the PR and I don't think it's going to fix actual repos. But maybe it just requires a new push or a new commit.

GiteaMirror commented

2025-11-02 04:34:43 -06:00

@zeripath commented on GitHub (Feb 4, 2019):

Those commits should prevent any further problems. In terms of fixing these repos - try pushing another commit and see if that solves it - if not I wonder if we should make an admin task that does an extreme cleanup.

@zeripath commented on GitHub (Feb 4, 2019): Those commits should prevent any further problems. In terms of fixing these repos - try pushing another commit and see if that solves it - if not I wonder if we should make an admin task that does an extreme cleanup.

GiteaMirror referenced this issue

2025-11-02 12:09:25 -06:00

[PR #2394] [MERGED] Update CONTRIBUTING following #2329 discussion #16386

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#2394