Repository navigation
ci: run the ruleset drift check on a schedule - #231
Merged
Merged
Conversation
Refs #166 Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Refs #166 Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
The read-only drifter App gets rulesets back without bypass_actors, so normalise() spread undefined and crashed the drift check. Co-Authored-By: Claude Sonnet 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.
Adds
.github/workflows/rulesets-drift.yml, which runsbun scripts/apply-rulesets.ts --checkand writes the plan to the job summary.workflow_dispatch, and PRs touchingrulesets/**, the script, its config lib, or the workflow itself (same-repo PRs only, since forks get no secrets).--checkis ever run, never--applyor--prune.actions/create-github-app-tokenwithpermission-administration: read, scoped to the five managed repos.Needs a manual step before it can go green
I reused the release-bot App (
RELEASE_BOT_CLIENT_ID/RELEASE_BOT_APP_PRIVATE_KEY) rather than creating a second App. I could not check its permissions from here. Its settings must grant Administration: Read and the installation must cover queeromaha, soundry, synthomaha, taraxvoid.net and voidflow, otherwise the token step fails. If you would rather keep release-bot narrow, a separate read-only App is a swap of the two secret names.A PR that changes
rulesets/will show drift in its run until it is merged and applied, so read the summary rather than the colour there.Not yet verified in Actions: the workflow has not run. After the App permission is in place, run it via
workflow_dispatchon this branch. Done criterion from the issue (a hand edit turns the run red with the diff in the summary) can be checked by editing a ruleset by hand and re-dispatching.Closes #166
🤖 Generated with Claude Code