Break up explore-analyze code ownership #3629
Open
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
shainaraskas
commented
Oct 23, 2025
| /explore-analyze/visualize/ @elastic/experience-docs | ||
|
|
||
| /extend/ @elastic/core-docs | ||
| /get-started/ @elastic/core-docs @elastic/project-docs |
There was a problem hiding this comment.
@elastic/project-docs looks like we have a missing link here (see the error at the top of this file)
I think we need to add your team as a subteam of docs, but we should do whatever we did for core/exp/dev/admin/ingest - I can't see how they were added, but they weren't given direct permissions to this repo
until we do that, your team won't be notified on the files you've marked as co-owned
cc: @georgewallace we will probably need your help here
florent-leborgne
approved these changes
Oct 23, 2025
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.
... for more targeted review requests and reduced noise
right now, we can't get away from global notifications for the top-level topics in each of these sections because they're not handled as index files in their respective folders. we could move to that model if we want to cut down on noise further.
Also looked at the other folders where I was familiar with the content, and didn't see any clear wins for breaking down ownership further.