Document JSON ingestion in repository guidance#1202
Draft
jwils wants to merge 1 commit into
Draft
Conversation
d52e77c to
b967a4d
Compare
8ea9e97 to
3ea2a40
Compare
b967a4d to
be69edf
Compare
3ea2a40 to
7eea290
Compare
be69edf to
d3393aa
Compare
7eea290 to
461ba24
Compare
d3393aa to
60ef9c4
Compare
edc42c3 to
62013f0
Compare
60ef9c4 to
2fdd0ae
Compare
2fdd0ae to
514f27e
Compare
62013f0 to
1eec3a6
Compare
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
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.
Why
Keep repository guidance accurate after adding the JSON ingestion extension gem.
What
elasticgraph-json_ingestionto the extension gem category in the repository guidanceRisk Assessment
Low - documentation-only follow-up on top of the extraction stack.
References