Repository navigation
Add internal GitHub token broker for SEO Monitor - #150
Merged
Merged
Conversation
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
appfactory-api | 68fde00 | Commit Preview URL Branch Preview URL |
Oct 14 2026, 12:51 PM |
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.
Adds an internal named Worker RPC entrypoint so SEO Monitor can reuse AppFactory's GitHub identity without copying its private key. The target repository and permission sets are fixed, with bounded fallback after definite scope rejection. Capability diagnostics return installation metadata without secrets.
The database lease allowlist also accepts repository dispatch for the original SEO collector workflow on main. Tests cover scoped token requests, bounded fallback and workflow-pinned lease authorization; Workers RPC types are included. Default HTTP routes remain unchanged.
Validated in production: the broker uses existing Contents write permission, the MCP → API → broker path dispatched SEO workflow run 38568211173 successfully, and Neon saved the matching snapshot with no failures. No additional GitHub permission grant was needed. Typecheck, service, web and Android checks pass; desktop blueprint validation runs independently.