Skip to content

chore: notify Teable on Mintlify deploy#121

Merged
HynLcc merged 2 commits intomainfrom
chore/notify-teable-on-mintlify-deploy
Apr 30, 2026
Merged

chore: notify Teable on Mintlify deploy#121
HynLcc merged 2 commits intomainfrom
chore/notify-teable-on-mintlify-deploy

Conversation

@HynLcc
Copy link
Copy Markdown
Collaborator

@HynLcc HynLcc commented Apr 30, 2026

What

Adds a GitHub Actions workflow that fires when a PR is merged into main, waits for Mintlify's staging deployment to reach success, then POSTs the docs branch name to a Teable webhook. Teable then updates the matching Docs Sync Runs record (Status → launch) and sends a Feishu notification.

How it works

  1. Triggered by pull_request: closed on main (only runs if merged == true).
  2. Polls GitHub Deployments API for a deployment matching the merge SHA, environment staging, creator mintlify[bot].
  3. On success → POST {docs_branch, docs_url} to the Teable webhook.
  4. Fails on failure/error or after 12 minutes timeout.

Requires

Repo secret TEABLE_WEBHOOK_TOKEN (configured separately).

Why a new workflow

pages-build-deployment is GitHub-managed (legacy Pages) — not a workflow file. Mintlify's deployment is created by the Mintlify GitHub App. Neither is editable. This is a single-file, single-purpose workflow that does not touch any existing deploy path.

@HynLcc HynLcc merged commit d5cc1de into main Apr 30, 2026
2 checks passed
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