This website requires JavaScript.
Explore
Help
Sign In
pub-solar
/
forgejo
Watch
5
Star
0
Fork
You've already forked forgejo
0
Code
Issues
Pull requests
Packages
Projects
Releases
Wiki
Activity
e18429aeb0
forgejo
/
routers
/
private
/
tests
/
repos
/
repo1_hook_verification
/
HEAD
2 lines
21 B
Plaintext
Raw
Normal View
History
Unescape
Escape
Fix verifyCommits error when push a new branch (#26664) > ### 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>
2023-08-30 02:27:53 +00:00
ref: refs/heads/main
Reference in a new issue
Copy permalink