Andrew Fletcher published: 13 April 2022 1 minute read
If you edit a Drupal contrib module, the next time the module is updated those edits will be wiped. So they are not lost there are a couple of options for you to consider:
- Are the edits worth the contributing to the community? Yes, you can fork the repo and add the changes for the developer(s) to review; or
- Create a patch file
Creating a patch file
The process:
Add the files you want to see in the diff. Remembering to only add untracked files.
git stash && git add . && git stash pop Now diff the staged:
git diff --stagedReset the staged files if needed
git resetCan you run all of the steps in one chained command?
git stash && git add . && git stash pop && git diff --staged && git reset
Related articles
Andrew Fletcher
•
09 Jan 2026
Upgrading Drupal from 10.6.x to 11.3.2: a practical, dependency-driven walkthrough
Upgrading from Drupal 10.6.x to 11.3.x is officially supported, but in real projects it’s rarely a single command. The friction usually comes from **Composer constraints**, not Drupal itself.This article documents a real-world upgrade path from Drupal 10.6.1 → 11.3.2, including the specific blockers...
Andrew Fletcher
•
04 Apr 2025
Managing .gitignore changes
When working with Git, the .gitignore file plays a critical role in controlling which files and folders are tracked by version control. Yet, many developers are unsure when changes to .gitignore take effect and how to manage files that are already being tracked. This uncertainty can lead to...
Andrew Fletcher
•
26 Mar 2025
How to fix the ‘Undefined function t’ error in Drupal 10 or 11 code
Upgrading to Drupal 10.4+ you might have noticed a warning in their code editor stating “Undefined function ‘t’”. While Drupal’s `t()` function remains valid in procedural code, some language analysis tools — such as Intelephense — do not automatically recognise Drupal’s global functions. This...