Include encoding in signature payload (#30174)

[GiteaBot]

Backport #30174 by @KN4CK3R

Fixes #30119

Include the encoding in the signature payload.

before

after

[silverwind]

@KN4CK3R lint failing:

Error: modules/git/commit_test.go:152:10: undefined: Sha1Hash (typecheck)

[silverwind]

@lunny v1.21 branch still has mysql5 and mysql8. Can this be changed per-branch?

[lunny]

@lunny v1.21 branch still has mysql5 and mysql8. Can this be changed per-branch?

This PR is unrelated to database charset. It's about git signature's text encoding. So I don't know what did you mean.

[KN4CK3R]

The pipeline did not run for MySQL.

[silverwind]

@lunny v1.21 branch still has mysql5 and mysql8. Can this be changed per-branch?

This PR is unrelated to database charset. It's about git signature's text encoding. So I don't know what did you mean.

I mean this:

1.22 and 1.23 have test-mysql
1.21 has test-mysql5 and test-mysql8

Please adapt the github protected branches config accordingly.

[lunny]

@lunny v1.21 branch still has mysql5 and mysql8. Can this be changed per-branch?

This PR is unrelated to database charset. It's about git signature's text encoding. So I don't know what did you mean.

I mean this:

1.22 and 1.23 have test-mysql 1.21 has test-mysql5 and test-mysql8

Please adapt the github protected branches config accordingly.

All release branches shared the same rules. I think this PR just need a new push to trigger a new CI to resolve the problem.

[silverwind]

All release branches shared the same rules

You need to make a separate rule for the 1.21 branch. A push won't solve it. Alternatively just remove these "required checks" that target workflows by name, I don't think they provide anything useful.