mirror of
https://github.com/different-ai/openwork
synced 2026-04-25 17:15:34 +02:00
* feat(plugin-system): add GitHub connector, discovery, marketplaces, and access UX End-to-end GitHub App connector flow and UI: - GitHub App connect: install start/callback/complete endpoints, connector account upsert from installation, selection state, and a dedicated Den Web setup page. - Repo discovery: GitHub tree + manifest inspection, Claude-compatible classification (marketplace/plugin-manifest), marketplace plugin metadata/component path parsing, discovery API + snapshot. - Apply pipeline: materialize plugins, connector mappings, config objects (with frontmatter-aware skill/agent parsing), memberships, and source bindings; create marketplaces with name/description from marketplace.json. - Auto-import on push: persist flag on connector instance, webhook-driven re-apply for new discoveries. - Cleanup: cascading disconnect on connector account removal and remove on connector instance. - Integrations UI: cleaner connected-account card, GitHub avatar, hover trash + confirm dialog, inline "Add new repo" action, per-account repo picker, manifest badges, configured/unconfigured sorting. - Discovery UI: cleaner loader, plugin cards with component chips, inline apply action, auto-import toggle default on. - Manage UI: instance configuration endpoint, auto-import toggle, remove repo danger zone with cascade confirmation. - Plugins & Marketplaces pages: dashboard nav entries, list + detail screens, per-plugin component counts, marketplace resolved endpoint with source + plugins, marketplace access section (org-wide/team/member grants). - Bitbucket card marked "Coming soon". - PRDs, GitHub setup instructions, and learnings docs added. * chore(docs): move GitHub-instructions.md into prds/new-plugin-arch/github-connection * fix(den-web): wrap github integration page in Suspense for useSearchParams * refactor(den-web): redirect GitHub post-install flow into the clean account selection phase After completing the GitHub App install, previously we rendered a separate GithubRepositorySelectionPhase with different styling. Now we call the install completion endpoint, then router.replace to ?connectorAccountId=... so the existing GithubConnectedAccountSelectionPhase renders the repo list. Removes the duplicate selection phase and its unused helpers/imports. * fix(den-web): drop Requires-scopes body and show GitHub description in integrations card Removes the empty-state Requires scopes: <code>… block from both provider cards and restores the provider description on the GitHub card so the empty state is consistent with Bitbucket. Drops the header's bottom border when no body follows. * fix(den-web): only show integration provider description in empty state Once a provider has connections, hide the description in the header so the card focuses on the connected accounts + repos list. --------- Co-authored-by: src-opn <src-opn@users.noreply.github.com>
3.6 KiB
3.6 KiB
New Plugin Arch Webhooks API
This document covers public webhook ingress and internal async sync trigger shapes.
Normal authenticated admin APIs are documented in prds/new-plugin-arch/admin-api.md.
Principles
- public webhooks are separate from authenticated admin APIs;
- signature verification happens before parsing or processing;
- ingress should be fast and queue-driven;
- connector-specific reconciliation happens asynchronously.
Public webhook endpoints
GitHub webhook ingress
POST /v1/webhooks/connectors/github
Purpose:
- receive GitHub App webhook deliveries for connector sync and connector lifecycle events.
Expected request inputs:
- raw request body
X-Hub-Signature-256X-GitHub-EventX-GitHub-Delivery
Behavior:
- verify signature against raw body
- reject invalid/missing signatures with
401 - normalize the webhook envelope
- dispatch by event type
- enqueue sync jobs for relevant branch updates
- return quickly
Recommended responses:
401 Unauthorizedfor invalid signature202 Acceptedfor relevant accepted events200 OKfor valid but ignored events
Internal webhook dispatch
Recommended normalized envelope:
type GithubWebhookEnvelope = {
deliveryId: string
event: string
installationId?: number
repositoryId?: number
repositoryFullName?: string
ref?: string
headSha?: string
payload: unknown
}
Recommended internal handlers:
githubWebhookIngress()handleGithubPushEvent()handleGithubInstallationEvent()handleGithubInstallationRepositoriesEvent()handleGithubRepositoryEvent()optional later
Signature verification shape
Requirements:
- use the GitHub App webhook secret;
- compute HMAC SHA-256 from the raw body;
- compare using constant-time comparison;
- do not parse JSON before verification;
- do not process if signature fails.
Practical rule:
- no signature match, no webhook processing.
Example pseudocode:
async function githubWebhookIngress(req: Request) {
const rawBody = await req.text()
const signature = req.headers.get("x-hub-signature-256")
if (!signature) return new Response("missing signature", { status: 401 })
const expected = signGithubBody(rawBody, env.GITHUB_CONNECTOR_APP_WEBHOOK_SECRET)
if (!timingSafeEqual(signature, expected)) {
return new Response("invalid signature", { status: 401 })
}
const event = req.headers.get("x-github-event")
const deliveryId = req.headers.get("x-github-delivery")
const payload = JSON.parse(rawBody)
return dispatchGithubWebhook({ event, deliveryId, payload })
}
Internal sync enqueue contract
For relevant push events on tracked branches, enqueue an async sync job.
Recommended payload shape:
type GithubConnectorSyncJob = {
connectorType: "github"
connectorInstanceId: string
connectorTargetId: string
connectorSyncEventId: string
deliveryId: string
installationId: number
repositoryId: number
repositoryFullName: string
ref: string
headSha: string
}
Recommendations:
- dedupe on
connectorTargetId + headSha - preserve
deliveryIdfor observability - allow internal retries without requiring webhook redelivery
- installation lifecycle events may update connector-account health/state without enqueuing a content reconciliation job
Worker result contract
The worker should update connector_sync_event with:
- final status (
completed,failed,partial) - target id
- head SHA
- created / updated / deleted / skipped counts
- per-file failures if any
- completed timestamp
Related docs
prds/new-plugin-arch/GitHub-connector.mdprds/new-plugin-arch/admin-api.md