Post Reply 
Author Useful stuff: Git
jakub-g
AT core team member

Find all posts by this user
Quote this message in a reply
Information  15 November 2013 13:33
Let's put useful tools, blog articles etc. regarding Git here.

I'll start with http://www.sourcetreeapp.com/
Basically a gitk-like thing with a nicer UI. Freeware, Windows 7+ required.
[Image: sourcetree_hero_win_full_interface_windows.png]

http://jakub-g.github.io/
(This post was last modified: 15 November 2013 13:33 by jakub-g.)
benoit.charbonnier
AT core team member

Find all posts by this user
Quote this message in a reply
Default  21 November 2013 14:23
all crafted by Altassian, the guys behind Stash / Bitbucket / Jira / Confluence (BTW all rockstar/killer apps !)
Olaf
Administrator

Find all posts by this user
Quote this message in a reply
18 February 2014 11:02
A little trick I learned yesterday is a functionality called sparse checkout that allow to only partially retrieve a Git repo. I needed to do that to only get the guides from our documentation-code repo to at.com, leaving the snippets and samples aside.

It's nicely explained here: http://briancoyner.github.io/blog/2013/0...-checkout/
jakub-g
AT core team member

Find all posts by this user
Quote this message in a reply
Default  18 February 2014 16:00
Cool, thx for sharing Olaf!

Another related trick is shallow clone: `git clone --depth 1`

This will not fetch all the history since the beginning of the time (in case you wanted to clone a Linux kernel or sth like that), but just the last N commits (N being the depth here).

http://jakub-g.github.io/
(This post was last modified: 18 February 2014 16:01 by jakub-g.)
jakub-g
AT core team member

Find all posts by this user
Quote this message in a reply
Default  10 March 2014 13:42
Two new things I've learnt lately:

- Git 1.9.0 for Windows is out. Among other features and fixes, it adds "@" to be an alias for "HEAD" to save some characters when typing things in command line.

- git describe <commit> can tell you where the certain commit is located in history with respect to the tags.

$ git describe HEAD
v1.4.16-16-g5ac3b86 # HEAD is "5ac3b86" and it is 16 commits after v1.4.16

$ git describe 5c6d
v1.4.12-10-g5c6d68c # 5c6d is 10 commits after v1.4.12

It's useful to infer in which release certain commit was included, i.e. the number reported + 1 (you can check it on Github, but this doesn't require you to go to the browser).

http://jakub-g.github.io/
(This post was last modified: 10 March 2014 13:43 by jakub-g.)
Post Reply