Jonathan Broquist jbro-io

If anyone is interested in setting up their system to automatically (or manually) sign their git commits with their GPG key, here are the steps:

Generate and add your key to GitHub
$ git config --global commit.gpgsign true ([OPTIONAL] every commit will now be signed)
$ git config --global user.signingkey ABCDEF01 (where ABCDEF01 is the fingerprint of the key to use)
$ git config --global alias.logs "log --show-signature" (now available as $ git logs)
$ git config --global alias.cis "commit -S" (optional if global signing is false)
$ echo "Some content" >> example.txt
$ git add example.txt
$ git cis -m "This commit is signed by a GPG key." (regular commit will work if global signing is enabled)

	/*
	* Hard coding your Salesforce URL in places like Email Tempaltes and Apex Classes is a worst practice, but some people do it.
	* These URLs will break when you turn on my domain, since your URL changes.
	* More on this here: https://help.salesforce.com/apex/HTViewSolution?urlname=Updating-Hard-Coded-References-FAQ
	* Here are some quick and dirty checks for your Salesforce URL being hard coded in:
	* EmailTemplates, WebLinks, ApexClasses, Visualforce Pages, and Triggers.
	* Ideally you would retrieve all metadata and search it, but this will find some of the low hanging problems easily.
	*
	* Usage:
	* - Copy / Paste this into Salesforce Execute Anonymous window.

	// "Cols" and "Rows" specify the coordinates in x and y.
	// Cells create cells by indexing the rows and cols array in the order [startx, starty, endx, endy].
	// Edit your Main.Sublime-menu file
	// Mac: /Users/yourMacName/Library/Application Support/Sublime Text 2/Packages/Default
	// PC: C:\Users\yourPCName\AppData\Roaming\Sublime Text 2\Packages\Default
	// Example Below:

	{
	"caption": "Grid: 6",
	"command": "set_layout",