docs(template-sync): document APP_CLIENT_ID and external ci.yaml ownership#182
Conversation
…rship The external opt-in was under-documented: the reusable workflow mints its App token from the APP_CLIENT_ID variable + APP_PRIVATE_KEY secret, but only the secret was named — an external adopter following the README would enable the schedule and fail token creation. Also scope the ci.yaml template-ownership claim to devantler-tech instances and document how external instances take ownership. Mirrors the wording shipped in dotnet-template#292. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@codex review |
|
Codex Review: Didn't find any major issues. Chef's kiss. Reviewed commit: ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
Self-promotion readiness record (head |
1 participant
Why
An adopter outside devantler-tech following the current opt-in doc would enable the weekly sync and have token creation fail: the reusable workflow needs the App's client ID as well as its key, but only the key was documented. The synced
ci.yamlis also an empty aggregator outside the org's rulesets, which the docs didn't say.What
Documents the full external opt-in triple (
APP_CLIENT_IDvariable +APP_PRIVATE_KEYsecret +TEMPLATE_SYNC_ENABLED=true) and how external instances take ownership ofci.yaml. Doc-only; mirrors dotnet-template#292's merged wording.