📖 [Docs]: Repository Type Property standard + memory-repo ruleset fix#76
Merged
Merged
Conversation
Documents the Type custom property as the concrete mechanism for Organization Standard's repository-type and custom-property requirements, including the exclude-only ruleset condition pattern, a migration/verification playbook, and the ruleset PATCH quirk discovered while implementing it. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
4 tasks
Marius Storhaug (MariusStorhaug)
marked this pull request as ready for review
July 25, 2026 15:32
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.
Adds Repository Type Property documenting the Type custom-property pattern used to classify repositories and drive which org-wide rulesets/controls apply to them.
Why
Standing up
MSXOrg/memoryper the Memory Repository Template surfaced a real gap: the org-wide "GitHub Flow" ruleset requires PRs on every push to main, which conflicts with the memory repo's designed no-PR, direct-commit workflow. Tracked in #71.This PR documents and implements the fix in both current MSX initiative organizations:
Both migrations used an exclude-only condition (Type != Memory is covered, not an include allow-list) specifically so future Type values are covered by default and nothing falls out of branch protection silently — the verification playbook for this is written into the new page.
Also documents a real API quirk hit during implementation: PATCH on orgs/{org}/rulesets/{id} returned 404 for an otherwise fully-authorized token, including on a disposable ruleset created solely to isolate the bug. Ruleset edits were done via delete-old + create-new instead.
Related: #71 (this PR resolves it for both organizations)
📖 [Docs]