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...

Changing git push from passphrase?  There are several ways to tackle this step.  I'm going to focus one of these steps. From your web directory root, look for your .git directory.  Then open the .git... cd .gitNext using your shell prompt (iTerm2), view the contents of the config file vim configPresently the config file looks like the following [core] repositoryformatversion = 0 filemode = true bare = false logallrefupdates = true ...