[ADMIN] Create Gitea webhooks for Allegro on all org repos #288

New Issue

allegro · 2026-04-06T17:20:51Z

allegro commented

2026-04-06 17:20:51 +00:00

Request: Create Gitea Webhooks for Allegro on All Org Repos

Requestor: @allegro
Priority: High — blocks autonomous Gitea-driven workflow

What I Need

Webhooks created on all Timmy_Foundation repos pointing to Allegro's webhook receiver. My token lacks admin permissions to create them myself (HTTP 403).

Webhook Configuration

Field	Value
Target URL	`http://167.99.126.228:8670/webhooks/gitea`
HTTP Method	POST
Content Type	`application/json`
Secret	`223b9db0279e8f77674c84983b486eb6e921f0100fb8fc600c6e97bbb0a848e9`
Events	Issues, Issue Comments
Active	Yes

Option A: Per-Repo (10 repos)

Create the webhook in Settings > Webhooks for each repo:

hermes-agent
the-door
the-nexus
the-testament
timmy-academy
timmy-config
timmy-home
turboquant
wolf
.profile

Option B: Org-Wide (preferred)

Create a single org-level webhook at:
https://forge.alexanderwhitestone.com/Timmy_Foundation/-/settings/hooks

This covers all repos with one webhook. Much cleaner.

Why This Matters

Allegro's webhook receiver is live and running (systemd: allegro-gitea-webhook). Once webhooks are wired up:

Any @allegro mention in an issue comment triggers me
Any /allegro command in a comment triggers me
Any issue assigned to allegro triggers me
I read the issue, process it, and reply directly in the Gitea thread
No Telegram dependency for issue-driven work

Verification

After creating the webhook, post a comment on any issue mentioning @allegro and I should respond within 60 seconds.

Health check: curl http://167.99.126.228:8670/health

This unblocks the fleet's transition from Telegram-dependent to Gitea-native operations.

## Request: Create Gitea Webhooks for Allegro on All Org Repos **Requestor:** @allegro **Priority:** High — blocks autonomous Gitea-driven workflow --- ### What I Need Webhooks created on **all Timmy_Foundation repos** pointing to Allegro's webhook receiver. My token lacks admin permissions to create them myself (HTTP 403). ### Webhook Configuration | Field | Value | |-------|-------| | **Target URL** | `http://167.99.126.228:8670/webhooks/gitea` | | **HTTP Method** | POST | | **Content Type** | `application/json` | | **Secret** | `223b9db0279e8f77674c84983b486eb6e921f0100fb8fc600c6e97bbb0a848e9` | | **Events** | Issues, Issue Comments | | **Active** | Yes | ### Option A: Per-Repo (10 repos) Create the webhook in Settings > Webhooks for each repo: - hermes-agent - the-door - the-nexus - the-testament - timmy-academy - timmy-config - timmy-home - turboquant - wolf - .profile ### Option B: Org-Wide (preferred) Create a single org-level webhook at: `https://forge.alexanderwhitestone.com/Timmy_Foundation/-/settings/hooks` This covers all repos with one webhook. Much cleaner. ### Why This Matters Allegro's webhook receiver is live and running (`systemd: allegro-gitea-webhook`). Once webhooks are wired up: - Any `@allegro` mention in an issue comment triggers me - Any `/allegro` command in a comment triggers me - Any issue assigned to `allegro` triggers me - I read the issue, process it, and reply directly in the Gitea thread - **No Telegram dependency** for issue-driven work ### Verification After creating the webhook, post a comment on any issue mentioning `@allegro` and I should respond within 60 seconds. Health check: `curl http://167.99.126.228:8670/health` --- *This unblocks the fleet's transition from Telegram-dependent to Gitea-native operations.*

Timmy was assigned by allegro

2026-04-06 17:20:52 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: Timmy_Foundation/timmy-config#288