Skip to content

docs(NO-TASK): Match the secret names the product repos actually use - #5

Merged
aaronware merged 1 commit into
mainfrom
docs/secret-names
Aug 10, 2026
Merged

aaronware merged 1 commit into
mainfrom
docs/secret-names

Conversation

@aaronware

Copy link
Copy Markdown
Contributor

The README invented RELEASE_POST_* secret names. The names actually configured on
linchpin-blocks are shorter, so the docs now match reality rather than the other way round.

README said actually used
RELEASE_POST_WP_USER WP_USER
RELEASE_POST_WP_APP_PASSWORD WP_PASS
RELEASE_POST_CF_ACCESS_CLIENT_ID CF_ACCESS_CLIENT_ID
RELEASE_POST_CF_ACCESS_CLIENT_SECRET CF_ACCESS_CLIENT_SECRET

The Cloudflare pair also matches the env-var convention already used by linchpin.com's
client-sync tooling, so this is the more consistent naming regardless.

Also drops the claim that these have to be org secrets — they are repo-level on
linchpin-blocks today, and the action only reads its inputs, so it does not care either way.

linchpin-blocks#923 and
mantle#832 already use these names.

Docs only.

@aaronware
aaronware merged commit 2027172 into main Aug 10, 2026
2 checks passed
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