-
Menu
Linked
Meta
Archive
- February 2012
- January 2012
- November 2011
- August 2011
- July 2011
- June 2011
- September 2010
- August 2010
- March 2010
- November 2009
- October 2009
- September 2009
- August 2009
- July 2009
- June 2009
- May 2009
- April 2009
- March 2009
- February 2009
- November 2008
- October 2008
- September 2008
- August 2008
- July 2008
- June 2008
- May 2008
- April 2008
- March 2008
- February 2008
- January 2008
- December 2007
- November 2007
- October 2007
- August 2007
- July 2007
- June 2007
- May 2007
- March 2006
- July 2005
- June 2005
- April 2005
- January 2003
Search
Tag Archives: git
Commit Messages
When reviewing a commit I’m not interested in what you did. A commit is a codebase transformation. I’m interested in what will happen to my codebase when I apply your commit. Bad “I did this” form: I had a cup of coffee, went for a walk, and changed some code. Better “This commit does this” form: Adds unmap() to the command map API. A commit message should describe the commit, not the process you went through to create it … Continue reading
Linking to your GitHub code
It’s pretty easy to link directly to a line of code in your GitHub repo: robotlegs/robotlegs-framework/blob/master/src/org/robotlegs/core/IContextProvider.as#L16 Don’t do that you naughty sausage! Your codebase will evolve (if all goes well), and line 16 will be replaced by a newer, shinier string of characters. Or, in this case, it’ll point to something that no longer exists. This, on the other hand, is more likely to stick around to haunt its author (me): robotlegs/robotlegs-framework/blob/v1.1.2/src/org/robotlegs/core/IContextProvider.as#L16 Select a tag before you link to your … Continue reading
OS X Git Prompt
I’m currently using a modified version of git-prompt that looks something like this:
Getting Started with Git on Mac OS X
Some Background I’ve recently switched from using SVN to using Git as my source control management tool of choice. It took a little while to get to grips with, but it rocks! Git is not an evolution of SVN. It is entirely different. Git is a distributed revision control system – everybody working on a project has their own full copy of the repository and its entire history.