Forge webhook intake (forge.intake=webhook, webhook_secret, webhook_addr) runs its own receiver on its own port and is set only by editing config.toml on the server, which breaks the rule that settings are edited through the control plane. Capture sources already give a per-source URL, secret and X-Hub-Signature-256 check in the dashboard. Done when a GitHub repo webhook pointed at a capture source can drive issue/PR work and the separate forge receiver and its config fields are deleted.
Imported from beads archie-core-vqci · GitHub #1507 · type task · priority P2 · created 2026-10-05
Forge webhook intake (forge.intake=webhook, webhook_secret, webhook_addr) runs its own receiver on its own port and is set only by editing config.toml on the server, which breaks the rule that settings are edited through the control plane. Capture sources already give a per-source URL, secret and X-Hub-Signature-256 check in the dashboard. Done when a GitHub repo webhook pointed at a capture source can drive issue/PR work and the separate forge receiver and its config fields are deleted.
---
_Imported from beads `archie-core-vqci` · GitHub #1507 · type task · priority P2 · created 2026-10-05_
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Forge webhook intake (forge.intake=webhook, webhook_secret, webhook_addr) runs its own receiver on its own port and is set only by editing config.toml on the server, which breaks the rule that settings are edited through the control plane. Capture sources already give a per-source URL, secret and X-Hub-Signature-256 check in the dashboard. Done when a GitHub repo webhook pointed at a capture source can drive issue/PR work and the separate forge receiver and its config fields are deleted.
Imported from beads
archie-core-vqci· GitHub #1507 · type task · priority P2 · created 2026-10-05