ci: Trigger seam-mcp redeploy on docs changes#1103
Merged
Conversation
Adds a workflow that fires on push to main and dispatches the seam-mcp deploy workflow via the SEAM_CI_BOT GitHub App. This keeps the public MCP's embedding index in sync with docs changes without requiring a separate nightly rebuild. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
.github/workflows/trigger-mcp-redeploy.ymlmain(and on manual dispatch), mints a scoped GitHub App token and callsgh workflow run deploy.yml --repo seamapi/seam-mcp --ref maindeploy.ymlalready rebuilds the OpenAI embedding index from this repo's docs and deploys the MCP server to Fly — so this closes the gap where docs-only changes never reached production search resultsWhy this design
deploy.ymlalready exposesworkflow_dispatch:, so we can trigger it directly without defining arepository_dispatchevent type on both sidesrepositories: seam-mcp) instead of an org-wide token — minimal blast radiuscancel-in-progress: trueon this workflow is safe because it only sends a dispatch; the receivingdeploy.ymlhas its owncancel-in-progress: falseconcurrency group to keep Fly deploys serializedPre-merge check
The
SEAM_CI_BOTGitHub App needsactions: writeonseamapi/seam-mcpfor thegh workflow runcall to succeed. It already hascontents: readthere (used in the other direction by seam-mcp's deploy). If the first run 403s, broaden the App's permissions on seam-mcp and re-run.Test plan
Trigger MCP Redeployworkflow runs on the merge commit to main and succeeds🤖 Generated with Claude Code