Repository navigation
[DX-660] Rulesets for main and branch names as files - #14
Merged
Merged
Conversation
- main.json: one code-owner review, no force-push or deletion, both CI jobs required. - branch-names.json: only type-prefixed branches may be created, Dependabot exempt. A creation rule with exclusions, since branch-name patterns need GitHub Enterprise. 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.
Why
DX-660, CI/CD standard §4.1 (atlas
handbook/engineering/cicd-standard.md):mainis protected by a ruleset committed to the repository. sample-data has no ruleset today, so nothing stops a direct push or a red merge.What
.github/rulesets/main.json:@revenexx/developer-experience).shell (run lock)andtui (install · format · lint · types · test), both jobs ofci.yml.bypass_actors: []..github/rulesets/branch-names.json:feature,fix,chore,doc,docs(each followed by/or-), plus Dependabot.branch_name_pattern) is stored on GitHub Team and enforces nothing: on 2026-10-30probe-dx660was pushed to pick-the-place past one. The creation rule is enforced: skills-catalog's live rule turned away afix/…push the same day (GH013).ownership/adr-0104,sample-data-media) stay. Only creating new ones is refused.After merge: an admin applies the rulesets
🤖 Generated with Claude Code