Post-merge badge step can fail twice: (1) transient Gitea connectivity during push leaves an existing badges branch, so the retry's git checkout --orphan badges fails (seen in infra run 6173). The step should fetch/reset the existing branch instead of always orphaning. (2) steps.release-tag.outputs.tag rendered as %!t(string=v0.75.0) in logs — act expression formatting bug in the workflow, worth checking if the output name is wrong.
Post-merge badge step can fail twice: (1) transient Gitea connectivity during push leaves an existing `badges` branch, so the retry's `git checkout --orphan badges` fails (seen in infra run 6173). The step should fetch/reset the existing branch instead of always orphaning. (2) `steps.release-tag.outputs.tag` rendered as `%!t(string=v0.75.0)` in logs — act expression formatting bug in the workflow, worth checking if the output name is wrong.
kireto
added the feedback label 2026-09-19 15:53:29 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Post-merge badge step can fail twice: (1) transient Gitea connectivity during push leaves an existing
badgesbranch, so the retry'sgit checkout --orphan badgesfails (seen in infra run 6173). The step should fetch/reset the existing branch instead of always orphaning. (2)steps.release-tag.outputs.tagrendered as%!t(string=v0.75.0)in logs — act expression formatting bug in the workflow, worth checking if the output name is wrong.