Backport the removal of PATCHES.txt to 1.x branch #258
Comments
|
The two commits from #213 will be squashed in the backported PR. |
donquixote
pushed a commit
to donquixote/composer-patches
that referenced
this issue
Mar 15, 2019
This is a backport of pull request cweagans#213 for issue cweagans#140. The two commits from cweagans#213 have been squashed into one.
|
I applied the change with a PR patch from #259 -- works great, I see no side effects! (Tested on a Drupal 8 project, with a patch to Drupal core.) (Side note: I lol'ed when a "PATCHES.txt" file was created in |
|
I'm okay with this, but can it be behind a config flag? I know of at least one user that relies on this and I don't want to break their workflow. Definitely okay with this being an opt-out thing though. |
awd-studio
added a commit
to awd-studio/composer-patches
that referenced
this issue
Nov 15, 2020
|
Hey! Would you mind? I made a PR for this. |
cweagans
added a commit
that referenced
this issue
Jan 18, 2021
#258 Added a flag to skip reporting on applied patches
|
There is now a config flag for this in 1.x. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In issue #140 / PR #213, the patch report generation (PATCHES.txt) was removed for the 2.x branch.
A release in this new branch has not happened yet.
I am going to provide a PR that backports this change to the 1.x branch.
The text was updated successfully, but these errors were encountered: