Repo owner annotations #1545
Merged
Repo owner annotations #1545
+36
−22
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
colleenmcginnis
approved these changes
Jul 9, 2025
There was a problem hiding this comment.
I made one change related to integrations in 60e701e. The rest looks good from the ingest docs perspective.
Mpdreamz
requested changes
Jul 10, 2025
Co-authored-by: Martijn Laarman <Mpdreamz@gmail.com>
szabosteve
approved these changes
Jul 10, 2025
Mpdreamz
approved these changes
Jul 10, 2025
bmorelli25
reviewed
Jul 10, 2025
bmorelli25
approved these changes
Jul 10, 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.
As docs teams, we often need to work in repositories owned by other teams at Elastic to maintain the docs and docs-related actions and pipelines.
This PR adds annotations to the repositories that feed into elastic.co/docs (as listed in
assembler.yml) to help our team to understand who should be on point for maintenance activities for each repo. We don't have to always follow this approach, but it will help us to find task owners when changes are not straightforward or require interfacing with other teams.as a side effect, this reorders the items in
assembler.ymlso I'll wait on a green light from eng to make sure it's safe to merge.