You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The issue is reproducible with the following git commands (adapt the clone URL and cd accordingly):
git clone [email protected]:matrss/broken-hooks-demo.git
cd broken-hooks-demo
git commit --allow-empty -m "Initial commit"
git push
git switch -c a
git commit --allow-empty -m "commit on a"
sleep 1
git push origin a
git commit --allow-empty -m "another commit on a"
git switch main
git commit --allow-empty -m "commit on main"
sleep 1
git push origin main a
i.e. this warning appears when pushing more than one branch with a single git push.
If I remove the git push origin a in the middle from the above commands then the warning does not appear, but instead the "a" branch will not be shown in the web UI, even though git reports it as pushed and up-to-date. That is probably a related issue.
Backport #31151 by @lunnyFix#31140
The previous logic is wrong when pushing multiple branches. After first
branch updated, it will ignore left other branches sync operations.
As a workaround for the repositories, just push a new commit after the
patch applied will fix the repositories status.
Co-authored-by: Lunny Xiao <[email protected]>
go-gitea
locked as resolved and limited conversation to collaborators
Aug 28, 2024
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Description
See the warning at the top of the screenshot included below.
Link to demo repository: https://demo.gitea.com/matrss/broken-hooks-demo
The issue is reproducible with the following git commands (adapt the clone URL and cd accordingly):
i.e. this warning appears when pushing more than one branch with a single
git push
.If I remove the
git push origin a
in the middle from the above commands then the warning does not appear, but instead the "a" branch will not be shown in the web UI, even though git reports it as pushed and up-to-date. That is probably a related issue.This issue was also reported to Forgejo here: https://codeberg.org/forgejo/forgejo/issues/3518 where I bisected the cause to be the changes made in #29493.
Gitea Version
1.23.0+dev-128-g14f6105ce0
Can you reproduce the bug on the Gitea demo site?
Yes
Log Gist
No response
Screenshots
Git Version
No response
Operating System
No response
How are you running Gitea?
https://demo.gitea.com/
Database
None
The text was updated successfully, but these errors were encountered: