release-and-maintain: badge push retry leaves orphan 'badges' branch; tag output shows %!t(string=...) #333

Open
opened 2026-09-19 15:53:29 +00:00 by kireto · 0 comments
Member

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
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: oblachno-oss/devx#333