RFC: A repository topic as an ownership proof - #38
Merged
Conversation
Maximilian-Nesslauer
added
rfc
Maximilian-Nesslauer
added
area:index
Maximilian-Nesslauer
requested review from
KlaasWhite,
MrJeranimo,
PlazmaBoltz and
averageksp
August 9, 2026 20:16
MrJeranimo
previously approved these changes
Aug 9, 2026
Maximilian-Nesslauer
added
stage:accepted
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
2 participants
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.
A third proof for RFC 0033's ownership check: the topic
ksa-index-<login>on the target repository, accepted exactly like the marker file. Nothing else in RFC 0033 changes.It closes the organization-owned case, where the owner-id fast path never fires, so listing your own content starts with committing a file into your own repository.
StarMapLoader/StarMapis in that group.The ownership half of #37. The number and
discussion:follow in a second commit.