Use the bot identity for tap release pushes #1508

Closed
opened 2026-07-22 16:28:23 +00:00 by coilyco-ops · 0 comments
Owner

Ward release run 2353 failed to push the tap after infrastructure's token contract moved to the coilyco-ops bot. The workflow still places the TAP_WRITE_TOKEN behind the personal coilysiren username in its HTTPS remote. Make the push identity explicit and match the bot-owned token provisioned by infrastructure#580. This is the locally grounded workflow half of the credential repair.

Ward release run 2353 failed to push the tap after infrastructure's token contract moved to the coilyco-ops bot. The workflow still places the TAP_WRITE_TOKEN behind the personal coilysiren username in its HTTPS remote. Make the push identity explicit and match the bot-owned token provisioned by infrastructure#580. This is the locally grounded workflow half of the credential repair.
Commenting is not possible because the repository is archived.
No milestone
No project
No assignees
1 participant
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
coilyco-flight-deck/ward#1508
No description provided.