Remove ownership.yaml (moved to central directory) #171
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
brrygrdn
previously approved these changes
Nov 24, 2025
brrygrdn
force-pushed
the
remove-ownership-yaml
branch
from
86771c7 to
b4cb42c
Compare
brrygrdn
approved these changes
Nov 24, 2025
brrygrdn
force-pushed
the
remove-ownership-yaml
branch
from
b4cb42c to
dcd1c17
Compare
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.
Remove legacy ownership.yaml (moved to central repository)
This PR removes the legacy
ownership.yamlfrom the repository root. The relocated ownership file can now be found here:Why is this changing?
See the centralization plan and discussion here: Durable Ownership Centralization.
Key points:
ownership.yamlfiles are centralized ingithub/ownership.github/github,github/github-ui) are exceptions.What do I need to do?
ownership.yamlis auto-generated, please coordinate with the Service Catalog team.If you have questions, please reply on the discussion above or reach out to the maintainers of the service catalog.