Gitea broke CI/Actions for mirrored repos

[dboreham]

This happened between 1.19.1 and 1.19.2 I suspect and broke our gitea-hosted CI jobs.

Previously jobs would be run on "push" events when commits were synced over from the origin Github repo.
Then, when the Gitea update was deployed, those jobs never ran again.

[dboreham]

Some debugging reveals the problem to be related to changes made in the naming of the "ref" on a push event.
When the push originates locally it has the form "refs/heads/" however when it originates in a synced push the ref string is just the branch name (e.g. "main"). Gitea's matching code now fails to match the job branch spec (e.g. "main") with what it expects ("refs/heads/main") and so does not run the job.

[dboreham]

Tested a possible fix and reported the bug in the gitea project: go-gitea/gitea#24926
There was an existing bug open: go-gitea/gitea#24824

[dboreham]

This issue is fixed with merge of this PR today: go-gitea/gitea#24634
Once we deploy a release with the fix, we can close this issue.

[dboreham]

Fix was backported to the 1.19 branch: go-gitea/gitea#23070 and the docker image 1.19-nightly was built 30min later, so I assume has the fix. I will test that image with a view to deploying it in production.

[dboreham]

The backported fix does not seem to work.

[dboreham]

Fixed in the 1.19 branch with go-gitea/gitea#24994 so we can deploy the 1.19-nightly image, or any subsequent 1.19 point release.

[dboreham]

Resolved now that the 1.19 nightly image has been deployed.