Aeion Forge + GitHub / GitLab / Bitbucket
PR tracking is table-stakes for engineering PM — every PR should be linked to an issue, and merging it should move the issue forward automatically. Aeion Forge auto-links GitHub pull requests via a signed webhook: issue keys are matched against the PR title and branch name, the PR is attached to the issue, and merging transitions the issue to done. For GitLab, Bitbucket, Azure DevOps, or self-hosted Git, the same linking happens on demand through Forge's MCP tool actions — called by your AI coding agent or a CI step, not automatic webhook detection.
Supported Git Platforms
`
Per-PR Lifecycle Sync
```typescript
Per-Commit Attribution
`
GitHub Webhook Setup Walkthrough
```bash
What's Not Automatic
`
FAQ
A shared secret (`FORGE_GITHUB_WEBHOOK_SECRET`) used to verify each delivery's HMAC-SHA256 signature. No GitHub App or OAuth token is required for the webhook path itself.
Yes — every delivery must include a valid `X-Hub-Signature-256` header, checked with a timing-safe comparison. Deliveries without a valid signature are rejected.
No. Issue linking is done by matching the KEY-123 pattern in the PR title/branch against issue identifiers tenant-wide — it isn't scoped by repository. Projects have an optional `githubRepo` reference field for your own bookkeeping, but it isn't enforced by the webhook handler.
Not currently — it's a fixed uppercase-prefix/number match (`KEY-123`), not a configurable regex.
On the GitHub webhook path, no — merging a linked PR always transitions the issue's status to done if it isn't already; there's no override flag. The agent/CI path is different: the `update_pr_status` MCP action takes an optional `autoClose` flag, so you decide per call whether a `merged` update also marks the issue done.
The webhook shape is the same (GitHub's `pull_request` event), so a GHE instance pointing at the same webhook URL should work, but there's no GHE-specific configuration in Forge.
No — the integration is one-way (GitHub → Forge) and only listens for `pull_request` events. There's no check-run or status sync in either direction.
Use Forge's `link_pr` / `update_pr_status` / `attach_commit` MCP actions from your AI agent or a CI job. There's no dedicated webhook receiver for these platforms yet.
Not automatically from the webhook path. Forge does add an internal comment on the issue when a PR is opened — that's visible in Forge's UI, not pushed out as a notification.