Repository navigation
docs(affirmation): affirm Roadmap Sync runs on a GitHub App token, no PAT - #910
Merged
Merged
Conversation
… PAT Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_011qEporYjgWy2Kw6WDQismf
Contributor
|
Note Currently processing new changes in this PR. This may take a few minutes, please wait... ⚙️ Run configuration
📒 Files selected for processing (1)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds one dated claim to
AFFIRMATION.adocunder We affirm: Roadmap Sync runs on a ≤1 h GitHub App installation token (Apphyperpolymath-roadmap-sync), with no personal access token. It writes to the org projectmetadatastician/projects/2. The legacy secretADD_TO_PROJECT_PATis no longer read by any workflow and will be deleted once the #35 → #2 item migration completes.Why: #903 (
fabe659) changed the credential, and the affirmation did not say so. The owner asked on 2026-10-07 for the affirmation of every repo touched by that work to be brought current.Closes: no tracking issue (follow-up to #903).
Type of change
📌 New pins
654ef0c40a6f4cb56a7ac54c979e0ee2441c4f25actions.lockentry, lockfile record or container digest.How has this been verified?
Each sentence of the new bullet was checked against
mainat1f30497:grep -n -E 'create-github-app-token|ROADMAP_SYNC|PROJECT_OWNER:|PROJECT_NUMBER:' .github/workflows/roadmap-sync.yml→ the mint step usesactions/create-github-app-token@v3.2.0withvars.ROADMAP_SYNC_APP_CLIENT_IDandsecrets.ROADMAP_SYNC_APP_PRIVATE_KEY;PROJECT_OWNER: metadatastician,PROJECT_NUMBER: '2'.grep -rn ADD_TO_PROJECT_PAT .github→ no match (rc 1). Positive control:grep -rln 'secrets\.' .github/workflows→ 14 files, so the grep does reach workflow files.gh api repos/hyperpolymath/hypatia/actions/secretslistsADD_TO_PROJECT_PATandROADMAP_SYNC_APP_PRIVATE_KEY.gh run list -w roadmap-sync.ymlshowedevent=schedulesuccessonfabe659(6 runs, 10-06 14:04Z→16:38Z) and on1f30497through 2026-10-07T09:05Z.git log -1 --format=%G?→G.Checklist
git commit -S).654ef0cverifiesG.AFFIRMATION.adoc. No code, test or workflow is touched, and the required checks run in CI.SPDX-License-Identifier. No new files;AFFIRMATION.adockeeps itsCC-BY-SA-4.0header.1f30497, and it states that the old secret is still stored.Notes for reviewers
:affirmed-at:is deliberately unchanged. Only this bullet is re-affirmed, inline-dated as the 2026-09-26 trusted-base re-measurement is. Moving the header date would assert that every other claim was re-verified.ADD_TO_PROJECT_PATis deleted (Phase 5 of the migration), the last sentence of the bullet should be shortened accordingly.🤖 Generated with Claude Code
https://claude.ai/code/session_011qEporYjgWy2Kw6WDQismf