Revert #59: restore flat Neo4j manifest (re-sequencing — land #54 first)#60
Merged
Conversation
…ne manifest" This reverts commit b278bfd.
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.
Undo the structured two-client Neo4j manifest change from #59 so PR #54 can merge cleanly.
Why
PR #54 edits
amplifier-online.yamlbased on the pre-#59 flat manifest form. With #59 currently merged, #54's base conflicts. This revert restores the manifest to the form #54 expects, enabling a conflict-free merge.What's happening next
This re-sequencing preserves #54's integrity and lets the new structured work land cleanly on top.