Repository navigation
Check repository settings for drift every week - #8
Merged
Merged
Conversation
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.
Repository settings must not drift from
settings/baseline.jsonunnoticed. A scheduled workflow runsscripts/apply-settings.mjs --dry-runevery Monday and fails on any difference.It reads the repositories with a short-lived token from the "BSStudio settings check" GitHub App, which has only Administration: read, is installed only on the repositories in
settings/repos.json, and gets its token scoped to that list. The App cannot change anything; fixing drift stays a local run of the script.