wiggleverse/wiggleverse-ecomm
2
0
Fork 0
Code Issues 5 Pull Requests Actions Packages Projects Releases Wiki Activity

Bind a GITEA_BOT_TOKEN on the ecomm deployment for patchwatch label provisioning #19

New Issue
Open
opened 2026-06-11 07:56:55 +00:00 by ben.stull · 1 comment
ben.stull commented 2026-06-11 07:56:55 +00:00
Owner
Copy Link
Copy Source

The first flotilla-core deploy ecomm (v0.4.0, deploys.id=40, session 0024) ended green with one warning: patchwatch labels not provisioned — deployment 'ecomm' has no GITEA_BOT_TOKEN secret bound (the webhook/labels verbs need it). Non-blocking; deploys work without it. Resume context: bind via flotilla-core secret set ecomm GITEA_BOT_TOKEN <project>/<secret> once a bot token exists for this repo (cf. ohm-rfc-app's wiggleverse-ohm/ohm-rfc-app-gitea-bot-token); the wgl-gitea-admin TOKENS.md card maps the scopes.

The first `flotilla-core deploy ecomm` (v0.4.0, deploys.id=40, session 0024) ended green with one warning: *patchwatch labels not provisioned — deployment 'ecomm' has no GITEA_BOT_TOKEN secret bound* (the webhook/labels verbs need it). Non-blocking; deploys work without it. Resume context: bind via `flotilla-core secret set ecomm GITEA_BOT_TOKEN <project>/<secret>` once a bot token exists for this repo (cf. ohm-rfc-app's `wiggleverse-ohm/ohm-rfc-app-gitea-bot-token`); the wgl-gitea-admin TOKENS.md card maps the scopes.
ben.stull added the type/taskpriority/P3 labels 2026-06-11 07:56:55 +00:00
ben.stull commented 2026-06-12 16:16:46 +00:00
Author
Owner
Copy Link
Copy Source

Survives the pivot (session 0036). Patchwatch deploy-security tooling is direction-agnostic; the network service still needs dependency-advisory provisioning.

**Survives the pivot** (session 0036). Patchwatch deploy-security tooling is direction-agnostic; the network service still needs dependency-advisory provisioning.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
priority/P0
Priority: highest — drop everything
 priority/P1
Priority: high
 priority/P2
Priority: medium
 priority/P3
Priority: low / someday
 type/bug
Type: a defect in shipped behaviour — small leaf work, straight to a plan
 type/epic
Type: a large body of work spanning many features
 type/feature
Type: a deliverable capability under an epic
 type/story
Type: a user story — the smallest valuable increment
 type/task
Type: a concrete unit of work under a story
No Label priority/P3 type/task
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
ben.stull (Ben Stull) ohm-bot
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: wiggleverse/wiggleverse-ecomm#19
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?