Multiple patch listing files #667
Open
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Description
No issue... maybe I should've written an issue before a PR? (but .github/CONTRIBUTING.md is empty so unsure).
Upgrading a pile of Drupal sites to PHP 8.5. Almost all of them need the same 4-8 patches. Most of them still have some PHP 8.4 related patches. Having to merge JSON manually for each site is more work than I think needed. Instead, I want to have multiple patches files...
patches.json (or whatever name) with site specific patches
php84.patches.json with PHP 8.4 related patches for components that most of my sites have
php85.patches.json with PHP 8.5 related patches for common components.
Because packages in the patch file that don't exist on the project are silently ignored that is really convenient and reduces work on similar projects.
Example output:
Related tasks
Everything here needs to be done if the idea is approved - happy to do so, but wanted to get a POC out for my own personal use/testing
patches-fileconfig key is deprecated. But that should probably be discussed.