GIT

Sometimes there are files that I want to remain executable even though for the most part I don't have git track file mode changes.  There is a single command that I end up searching for every time I need it.  

git update-index --chmod=+x <filename>

I use git commit hooks to run my code through code sniffer prior to commit.  If the code is not up to code style standards, the commit fails and you have to go fix it before it will commit.  In some rare instances (kept to a minimum of course) there is code that will just not pass code style review.  In those cases it is best to wrap the code to make it exclude review.

There are a lot of steps I end up doing with git repeatedly, especially when using a pull request workflow, so I make shell aliases out of them (either bash or zsh).   Some could be just as easily done as git aliases if you prefer.

There are times when it is handy to export a subdirectory in repo into a new repo where you want to maintain the original git history of the files.  Example: During the course of building a drupal site, a custom module is ready to become a contrib module, so it needs to be in a separate repository.

There are two methods

Method 1: Strip everything from a copy of the repo

1. mkdir NewExport

2. cd NewExport

3. git clone <repo>

4. cd into the cloned repo

I have used git submodules and they are more trouble and pain than they are worth.

I find this approach to be nicer and an easier way to handle a git repo inside a git repo.
http://debuggable.com/posts/git-fake-submodules:4b563ee4-f3cc-4061-967e-...

A nice feature for protecting a repository from badly formatted code that violates Drupal coding standards is to install Coder at the global drush level (not in a specific website) and then use Drupal Code Quality (dcq) to run that code review as a git commit hook that runs as you attempt to commit your code.

Installation instructions are here.

Do review you Drupal code for style:
Install coder and enable enable it
drush dl coder
drush en coder

Then to run code style review on any module, cd into the module

Or on a specific file:

This is the very basic idea behind a pull request based workflow.

1. Pull from a prime remote repositiory. (never push to this repo)
2. Commit your work locally and push to your remote fork
3. Use github to create a pull request to the prime repo.

Simple commands needed for working with multiple remotes in git.

List of remotes

Add a remote

Rename a remote

Checkout a remote branch

Delete a remote

install zshell
then extend it with oh-my-zshell

https://github.com/robbyrussell/oh-my-zsh

Very helpful using it with the git plugin