Repository navigation
#229 issue - added merge config feature - #279
Open
jakubfrieb wants to merge 1 commit into
Open
jakubfrieb wants to merge 1 commit into
jakubfrieb wants to merge 1 commit into
Conversation
swolley
approved these changes
Mar 13, 2026
swolley
left a comment
There was a problem hiding this comment.
Thanks for this PR, the merge-config feature is very useful.
I’m using composer-merge-plugin in a modular Laravel project to merge multiple composer.*.json files, including config.platform. I’ve applied this patch locally and it works well for my use case.
It would be great to have this merged and released.
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.
Add feature to merge config part form composer.json. You can merge all keys, or you can create only allowed keys, or exclude. Fixes issue #229