Skip to content

Fix webhook event name + note provisioner token UI - #1

Open
ThierryAbalea wants to merge 2 commits into
mainfrom
fix/webhook-received-and-provisioner-token
Open

Fix webhook event name + note provisioner token UI#1
ThierryAbalea wants to merge 2 commits into
mainfrom
fix/webhook-received-and-provisioner-token

Conversation

@ThierryAbalea

@ThierryAbalea ThierryAbalea commented Jul 2, 2026

Copy link
Copy Markdown
Contributor

Two doc corrections from recent backend changes:

  • Webhook event is received, not webhook.received. shipfox#463 locked the generic webhook trigger contract to source = connection slug + the fixed received event (confirmed in libs/api/triggers/.../received-event.ts and the dispatch/inbound tests). Updated every mention across webhooks, trigger-sources, overview, linear, slack, triggers, and the authoring prompt.
  • Provisioner token UI. shipfox#479 added a Settings → Runner Provisioners page to create/reveal-once/revoke the provisioner registration token. Noted where SHIPFOX_PROVISIONER_TOKEN comes from on the runner-provisioners page.

Summary by cubic

Updated docs to use the correct webhook event name received and noted where to create/manage the provisioner token in Settings → Runner Provisioners. Aligns with backend changes from Linear 463 and 479.

  • Bug Fixes
    • Webhooks: replaced webhook.received with received across pages; source remains the webhook connection slug (Linear 463).
    • Runner provisioners: added how to create/reveal-once/revoke the SHIPFOX_PROVISIONER_TOKEN in Settings → Runner Provisioners (Linear 479).

Written for commit 37b2767. Summary will update on new commits.

Review in cubic

@cubic-dev-ai cubic-dev-ai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No issues found across 8 files

Heads up: you’re close to your included review allowance. Set a flex budget so reviews don’t pause.

Re-trigger cubic

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant