Skip to content

Conversation

@M-arcus
Copy link
Contributor

@M-arcus M-arcus commented Jan 8, 2026

No description provided.

```

<br>

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please keep these

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Re-added them, I thought they were leftover HTML tags in a markdown file

@M-arcus M-arcus requested a review from TomasVotruba January 8, 2026 18:02
```bash
# generate patches
vendor/bin/vendor-patches generate
# (if using cweagans/composer-patches v2)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm thinking, what is the added value of v2 here? It seems more and more work.

Instead, we should handle this for a user. Any chance we can include this complexity into our generate command to keep it working as before?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I updated the README instructions because without executing the 2 additional commands, nothing happens to files in vendor/. This might lead to people just installing and assuming that files in vendor/ are patched.

I can add another PR that checks if v2 is installed and triggers the relock and repatch commands after generating the patch.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants