-
-
Notifications
You must be signed in to change notification settings - Fork 6k
Description
Description
Since upgrading from 1.23.4 to 1.24.4, some users are unable to make file changes through the web interface. This issue is both repository and user-specific, affecting only certain users in one particular repository.
Steps to reproduce:
- User navigates to a file in the web interface
- User makes changes to the file
- User clicks "Propose file change"
Expected behavior:
The file changes should be committed to a new branch and the user should be able to proceed with creating a pull request.
Actual behavior:
The error "The push appears to be out of date" appears, preventing the user from proceeding.
Instance log error:
2025年08月26日 08:57:18 .../repository/files/update.go:291:ChangeRepoFiles() [E] *git.ErrPushOutOfDate PushOutOfDate Error: exit status 1 - To /var/lib/gitea/data/gitea-repositories/<org>/repo.git
! [rejected] 3306cd11f859ea2f4e50b86ddfe293fbd45e1ee4 -> christian-patch-1 (non-fast-forward)
error: failed to push some refs to '/var/lib/gitea/data/gitea-repositories/<org>/repo.git'
hint: Updates were rejected because a pushed branch tip is behind its remote
hint: counterpart. If you want to integrate the remote changes, use 'git pull'
hint: before pushing again.
hint: See the 'Note about fast-forwards' in 'git push --help' for details.
- To /var/lib/gitea/data/gitea-repositories/<org>/repo.git
! [rejected] 3306cd11f859ea2f4e50b86ddfe293fbd45e1ee4 -> christian-patch-1 (non-fast-forward)
error: failed to push some refs to '/var/lib/gitea/data/gitea-repositories/<org>/repo.git'
hint: Updates were rejected because a pushed branch tip is behind its remote
hint: counterpart. If you want to integrate the remote changes, use 'git pull'
hint: before pushing again.
hint: See the 'Note about fast-forwards' in 'git push --help' for details.
: To /var/lib/gitea/data/gitea-repositories/<org>/repo.git
! [rejected] 3306cd11f859ea2f4e50b86ddfe293fbd45e1ee4 -> christian-patch-1 (non-fast-forward)
error: failed to push some refs to '/var/lib/gitea/data/gitea-repositories/<org>/repo.git'
hint: Updates were rejected because a pushed branch tip is behind its remote
hint: counterpart. If you want to integrate the remote changes, use 'git pull'
hint: before pushing again.
hint: See the 'Note about fast-forwards' in 'git push --help' for details.
This behavior is strange because the branch christian-patch-1 does not exist prior to the user attempting to create the file proposal. Since the branch is created at the moment the user clicks the button, there shouldn't be any "outdated" content causing a non-fast-forward rejection.
The Gitea Site-Administration page does also show no problems on the "Self check" section.
Gitea Version
1.24.5
Can you reproduce the bug on the Gitea demo site?
No
Log Gist
No response
Screenshots
Image
Git Version
2.48.1
Operating System
Ubuntu Server 20.04.6 LTS
How are you running Gitea?
Gitea runs via the binary which gets executed from a systemd service.
Database
MySQL/MariaDB