Because we use a devOps system that installs packages on the server via Composer, my core drupal installation and contrib modules are not in version control (Git).
I used to patch modules as follows:
- Commit everything, so my branch is up-to-date.
- Make my changes to the module (= write the fixes in the module).
- Inside my code editor go to Code -> Create patch and follow the steps there (because of Git, my editor knows what has changed).
- My patch gets saved where I prefer to do it.
Since we started working with keeping modules and core out of Git I do not have a clue on how to create my patches anymore.
Curious about the solutions you might have!
diff
on them when required to. But it would be painful. Thing is, everything you’re talking about (Drupal and its contrib modules) lives in git already. So, arguably, you should create your patches using git, and make them available to your Composer workflow separately for installation