mirror of
https://codeberg.org/forgejo/forgejo.git
synced 2024-08-20 19:47:55 +02:00
> ### Description > If a new branch is pushed, and the repository has a rule that would require signed commits for the new branch, the commit is rejected with a 500 error regardless of whether it's signed. > > When pushing a new branch, the "old" commit is the empty ID (0000000000000000000000000000000000000000). verifyCommits has no provision for this and passes an invalid commit range to git rev-list. Prior to 1.19 this wasn't an issue because only pre-existing individual branches could be protected. > > I was able to reproduce with [try.gitea.io/CraigTest/test](https://try.gitea.io/CraigTest/test), which is set up with a blanket rule to require commits on all branches. Fix #25565 Very thanks to @Craig-Holmquist-NTI for reporting the bug and suggesting an valid solution! --------- Co-authored-by: wxiaoguang <wxiaoguang@gmail.com> Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com> |
||
---|---|---|
.. | ||
0b | ||
2b | ||
08 | ||
8b | ||
9c | ||
13 | ||
23 | ||
65 | ||
72 | ||
93 | ||
97 | ||
a9 | ||
ba | ||
bb | ||
cb | ||
d7 | ||
e3 | ||
e6 | ||
e8 | ||
info | ||
tmp_objdir-incoming-a21648 |