chore: exclude benchmark repos from safe-settings - #21
Merged
Merged
Conversation
hacktron-bench, bench-dataset-* and llm-router are benchmark/research repos whose owner needs to manage their own branch protection; the org default was reverting manual edits within seconds. bench-dataset-* is a glob so each new per-dataset repo is covered without another change. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01A6rDqmzwhbo5u5WmMm5YYc
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
1 participant
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.
Why
jikun's new benchmark repos picked up the org-default branch protection from
.github/settings.yml. Any manual edit to it was reverted byhacktron-safe-settings[bot]within ~2s (see the org audit log forhacktron-bench, 2026-09-24). These are research/benchmark repos, not customer-facing, and he needs to manage protection himself.Change
Adds to
deploymentConfig.restrictedRepos.exclude(minimatch globs, full-name match):hacktron-bench(harness; pins datasets as submodules)bench-dataset-*(one repo per dataset; covers current 10 + future ones)llm-routerExisting branch protection on these repos is left in place; the bot just stops enforcing it, so the owner can edit/remove it.
Unit test extended to assert the new exclusions and that
web/hacktronstay managed.Deploy
Touches
helm/safe-settings/**, so merging tomain-enterprisetriggers Deploy safe-settings (tests → image → Helm upgrade onsafe-settings-cluster).🤖 Generated with Claude Code
https://claude.ai/code/session_01A6rDqmzwhbo5u5WmMm5YYc