ownership.yaml: Surface inactive data for replacement #3
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.
Hello.
There exists inactive data in this repo's
ownership.yamlfile, which gets pulled into the Service Catalog.What do we mean by inactive?
What should you do?
Please replace the lines containing
FIXMEwith appropriate new, active data. For Slack channels, a public channel is preferred so that people can find your team and ask you questions if needed. For additional recommendations and examples, check out the "service ownership" page on the Hub.If you need help, please ask questions in #service-catalog on Slack. Thank you for helping us to keep Service Catalog data accurate! 🙇
/cc @johanrosenkilde @github/next for 👀 on stale github-copilot-cli data