Skip to content

docs: authenticate the docs dispatch with the org automation App - #19

Open
emmanuel-defreitas wants to merge 1 commit into
release/v0.2.0from
docs/dispatch-app-token
Open

docs: authenticate the docs dispatch with the org automation App#19
emmanuel-defreitas wants to merge 1 commit into
release/v0.2.0from
docs/dispatch-app-token

Conversation

@emmanuel-defreitas

Copy link
Copy Markdown
Member

Pairs with exegia/corpora-auth#78.

Why

The documented notify-docs.yml needed a CORPORA_DOCS_DISPATCH_TOKEN PAT with contents: write on this repo. That secret was never created, so the dispatch has been dormant since it shipped — every source repo would have been blocked on provisioning a long-lived credential.

The org already exposes AUTOMATION_APP_ID and AUTOMATION_APP_PRIVATE_KEY to every repo (visibility=all), and corpora-auth already mints short-lived App tokens this way in pr-merged.yml. Reusing that pattern is strictly better:

  • no secret to provision — a new source repo can add the workflow and it works
  • no long-lived credential, nothing to rotate
  • token scoped to corpora-docs alone via owner + repositories, expires within the hour

Change

  • Snippet rewritten to mint via actions/create-github-app-token@v3 — verified line-for-line identical to what shipped in corpora-auth#78.
  • New Authentication section explaining the scoping and the one prerequisite (the App needs access to this repo with contents: write).
  • The <Note> now explains why continue-on-error on the minting step is load-bearing rather than boilerplate.
  • No remaining references to CORPORA_DOCS_DISPATCH_TOKEN anywhere in the repo.

scripts/mirror_sections.py --check passes.

The documented workflow required a CORPORA_DOCS_DISPATCH_TOKEN PAT that was
never created, so every source repo had to wait on a long-lived credential
before the dispatch could work at all.

The org already exposes AUTOMATION_APP_ID and AUTOMATION_APP_PRIVATE_KEY to
every repo (visibility=all), and corpora-auth already mints short-lived App
tokens this way in pr-merged.yml. Reusing that means a new source repo needs
no secret provisioned, nothing to rotate, and a token scoped to corpora-docs
that expires within the hour.

Snippet is line-for-line identical to exegia/corpora-auth#78.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@mintlify

mintlify Bot commented Aug 10, 2026

Copy link
Copy Markdown

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated (UTC)
exegia 🟢 Ready View Preview Aug 10, 2026, 7:48 PM

💡 Tip: Enable Workflows to automatically generate PRs for you.

@claude

claude Bot commented Aug 10, 2026

Copy link
Copy Markdown

Code review

No issues found. Checked for bugs and CLAUDE.md compliance.

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