Skip to content

ci(docs-dispatch): mint the dispatchbot token with client-id #33

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
vdavez merged 1 commit into from
Oct 19, 2026
Merged

ci(docs-dispatch): mint the dispatchbot token with client-id #33

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions .github/workflows/docs-dispatch.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,9 +8,9 @@ name: Docs dispatch
# tango-node is a `coloc-source` repo: its docs/ folder is the authoritative
# source for the Node SDK pages on docs.makegov.com (see makegov/docs#15).
#
# Required secrets — both are ORG secrets with `visibility: selected`, so this repo has to be on their selected list or every dispatch fails auth:
# DISPATCHBOT_APP_ID — the makegov-dispatchbot App.
# DISPATCHBOT_PRIVATE_KEY — its private key.
# Required org settings for the makegov-dispatchbot App:
# DISPATCHBOT_CLIENT_ID — org variable: the App's Client ID, visible to all repos.
# DISPATCHBOT_PRIVATE_KEY — org secret: its private key. The secret has `visibility: selected`, so this repo has to be on its selected list or every dispatch fails auth.
#
# The App mints a short-lived installation token scoped to the one repo this dispatches to (makegov/docs unless DOCS_TARGET_REPO overrides it).
#
Expand Down Expand Up @@ -93,7 +93,7 @@ jobs:
id: docs_composer
uses: actions/create-github-app-token@v3
with:
app-id: ${{ secrets.DISPATCHBOT_APP_ID }}
client-id: ${{ vars.DISPATCHBOT_CLIENT_ID }}
private-key: ${{ secrets.DISPATCHBOT_PRIVATE_KEY }}
owner: ${{ steps.docs_target.outputs.owner }}
# Scoped to the single repo this step dispatches to, so a leaked token can't reach the rest of the org. A repository_dispatch needs Contents:write on the receiving repo.
Expand Down
Loading