Repository navigation
Document the environment-scoped GitHub secrets and the smoke-test token. - #323
Conversation
Bugbot couldn't run - usage limit reachedBugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit. A user or team admin can review and increase usage limits in the Cursor dashboard. (requestId: serverGenReqId_1480eeb8-bf07-4a45-9007-7cf53879669d) |
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 8369805036
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
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".
8369805 to
3be8dbe
Compare
Bugbot couldn't run - usage limit reachedBugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit. A user or team admin can review and increase usage limits in the Cursor dashboard. (requestId: serverGenReqId_0f35a5e0-cfb7-4d53-acdb-02b6fc34b58d) |
![graphite-app[bot]](https://avatars.githubusercontent.com/in/158384?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 3be8dbed29
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
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".
`CF_API_TOKEN`, `CF_ACCOUNT_ID`, and `VOID_TOKEN_STAGING` moved from repo-level secrets into the `Prod` and `Staging` environments. The table now names the 1Password item each value comes from, and explains how `VOID_TOKEN_STAGING` is signed and rotated. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01WNXbwieSdsSErZwQ7HWRwG
3be8dbe to
0ec5ae2
Compare
Bugbot couldn't run - usage limit reachedBugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit. A user or team admin can review and increase usage limits in the Cursor dashboard. (requestId: serverGenReqId_04dfb70a-b022-44ce-89b5-d29803f93f39) |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 0ec5ae2cbb
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
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".
What
Docs only.
CF_API_TOKEN,CF_ACCOUNT_ID, andVOID_TOKEN_STAGINGare no longer repo-level secrets. They live in theProdandStagingGitHub environments now. The secrets table inplatform/meta/operations.mdsays so, names the 1Password item behind each value, and explains howVOID_TOKEN_STAGINGis signed and rotated.No workflow changed. Every job that reads these secrets already declares
environment: Prodorenvironment: Staging.🤖 Generated with Claude Code
https://claude.ai/code/session_01WNXbwieSdsSErZwQ7HWRwG
Note
Low Risk
Documentation-only; no workflow or runtime behavior changes.
Overview
Updates
platform/meta/operations.mdto reflect that platform deploy/smoke secrets are only in GitHubProd/Stagingenvironments (no repo-level platform secrets), and adds a table tying each secret to its environment, purpose, and 1Password item in theVOIDvault.The doc now spells out
VOID_TOKEN_STAGING: long-lived stagingaud: apiJWT for the kitchen-sink smoke test (manualsignJwt()+ 2-year TTL), rotation viagh secret set … --env Staging, and invalidation when stagingJWT_SECRETrotates.Reviewed by Cursor Bugbot for commit 0ec5ae2. Bugbot is set up for automated code reviews on this repo. Configure here.