Scaffold the elasticgraph-proto_ingestion gem#1297
Merged
Conversation
myronmarston
requested changes
Jul 7, 2026
bbcb52f to
27fe0fc
Compare
a4d28b4 to
e3a237b
Compare
27fe0fc to
7ae8271
Compare
Creates the new `elasticgraph-proto_ingestion` extension gem and wires it into the repo (bundle, RBS collection, docker demo, doctest helper, docs diagrams), without any of the Protocol Buffers generation logic yet. The gem currently just defines its artifact file name constants and an `APIExtension` entry point that does not customize anything. Splitting the gem creation out this way keeps the follow-up PR that adds the actual generation logic contained to the gem's own directory.
7ae8271 to
cc66e8b
Compare
myronmarston
approved these changes
Jul 7, 2026
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.
Creates the new
elasticgraph-proto_ingestionextension gem and wires it into the repo — bundle/lockfile, RBS collection, docker demo image, doctest helper, dependency diagrams, and therun_gem_specsflatware list — without any of the Protocol Buffers generation logic yet. The gem currently just defines its artifact file name constants and anAPIExtensionentry point that does not customize anything.Splitting the gem creation out this way keeps the follow-up PR that adds the actual generation logic (#1080) contained entirely to the gem's own directory.
Second of a three-PR sequence: #1296 (artifact comment prefixes), this scaffold, then #1080 (the generation logic).