ops: connect maity.team to GitHub for the ticker (forge token, ticker on for 'maity', webhook)
tsk-3mffs18cstnw done Maity OPS Team (maity-ops-team)
Oliver wants to dogfood the change ticker (chat seq 7047). Today it is empty: project 'maity' has no settings.ticker, the hub has no MAITY_FORGE_GITHUB_TOKEN (probe_configured: false), no webhook. Steps: (1) Oliver creates a fine-grained read-only GitHub token for oliver-zehentleitner/maity (contents, pull requests, deployments: read) and gives it to you privately; set it as the hub secret MAITY_FORGE_GITHUB_TOKEN in the k8s secret (never print it), roll the pod; check probe_configured: true. (2) Oliver (human project:admin) turns the ticker on in settings (or via PATCH until the web settings card lands). (3) Oliver creates the webhook secret (POST …/forge/webhook/secret) and enters URL + secret in GitHub (events: pull_request, deployment_status). (4) Verify a merge shows up as a ticker item. Do this after the main deploy.
Notes
Maity Review Team Grok (maity-review-team-grok) ·
Review (grok-bot-review): pass. I checked this live on the hub.
- Step 1: the probe is configured. The project probe for an open PR returns fresh data (forge github, repository oliver-zehentleitner/maity, fresh: true). The token is wired through the chart's own forge.github.existingSecret, so it survives the next helm upgrade.
- Steps 2 and 4: settings.ticker.enabled is now true for this project, and the ticker shows merge items from this morning, so a merge does show up as a ticker item.
- Step 3, the webhook, is optional. Per the report it only makes the hub look sooner, and it is left to a human admin. It doesn't block this card.
- Keep the Why: OK. The hub-wide instance token is the documented fallback in context/integrations.md ("a GitHub App installation first, the owner's token second, the instance token for public repositories only"). Per-user keys or a GitHub App, named in the report as the follow-up, already match that entry's order. Nothing missing.
Moving the card to done.