Repository navigation
ci(archive): keep a human as the only approver; the bot only opens an issue - #21
Merged
Merged
Conversation
… issue The weekly archive job pushed a bot branch and opened a PR. That required the repo setting "Allow GitHub Actions to create and approve pull requests", which would also let any workflow token approve PRs. Bot-opened PRs would not run CI either, since events from the built-in token start no workflows. The job now runs with contents: read and issues: write only. It runs the archiver in report mode, which still triggers Wayback's Save Page Now, so the slow snapshotting happens in CI. It then opens or updates one archive-labelled issue listing the snapshots found and the failures, with the local commands to add them; the issue closes itself once every source has a snapshot. A maintainer runs npm run archive -- --write, reviews, commits, opens the PR and merges. CONTRIBUTING and CHANGELOG [Unreleased] are updated. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
The weekly archive job pushed a bot branch and opened a PR. That required the repo setting "Allow GitHub Actions to create and approve pull requests", which would also let any workflow token approve PRs. Bot-opened PRs would not run CI either, since events from the built-in token start no workflows. The job now runs with contents: read and issues: write only. It runs the archiver in report mode, which still triggers Wayback's Save Page Now, so the slow snapshotting happens in CI. It then opens or updates one archive-labelled issue listing the snapshots found and the failures, with the local commands to add them; the issue closes itself once every source has a snapshot. A maintainer runs npm run archive -- --write, reviews, commits, opens the PR and merges. CONTRIBUTING and CHANGELOG [Unreleased] are updated.
What
Checklist (Definition of done)
npm testpasses locally (validate + build,dist/rebuilt and committed)npm run linkcheck)status/confidencehonestly reflect the sourcing (no upgrade beyond sources)mappingsIDs exist exactly as published — nothing inventedidis new and permanent (no rename/recycle of existing ids)