public
Description: A set of Sake tasks to make developing with Git easier.
Clone URL: git://github.com/eventualbuddha/sake-git.git
Search Repo:
Wed Apr 16 13:27:14 -0700 2008
commit  15879e86954d89d97eb9437f4d1f2751b6677ff1
tree    e93703513f403e6c59e001422d7609426f1fd16f
parent  835bd93a838792771973e06c9554efea0a8f1999
sake-git / README.textile
100644 58 lines (40 sloc) 1.587 kb
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
h1. Sake-Git
 
Here are a few Sake tasks to make developing with Git easier (and some corresponding Git aliases to
make invoking them easier). Install them with:
 
<pre>
$ rake install
</pre>
 
Or, if you don't want to actually download this stuff, just use Sake:
 
<pre>
$ sake -i "http://github.com/eventualbuddha/sake-git/tree/master/git.rake?raw=true"
</pre>
 
h2. Common Commands
 
<pre>
$ sake git:update
</pre>
 
Updates your current git repository, autodetecting whether you have a regular ol' git project or a
git-svn project. I recommend aliasing it @git up@.
 
<pre>
$ sake git:push
</pre>
 
Commits any changes in your current branch not yet pushed upstream _and_ ports 'em over to master. I use @git ci@ for this one.
 
<pre>
$ sake git:open [NAME=mynewbranch]
</pre>
 
Creates a new branch off master. Think of this as opening an issue, or a new path of development. I use @git open@ for this one, allowing you to call it like so:
 
<pre>
$ git open mynewbranch
</pre>
 
You can even call it without the branch name and it'll ask you for it:
 
<pre>
$ git open
* Name your branch: mynewbranch
</pre>
 
<pre>
$ sake git:close [NAME=mynewbranch]
</pre>
 
This is open's brother, and should be used when you finish something and have already moved it to
master or upstream. If you haven't yet, don't worry - this won't eat your data. Like open, this one I alias to @git close@.
 
h2. Credits
 
Thanks to Coda Hale and everyone else at Wesabe for trying these out when I first wrote them and
contributing tasks of their own, and to the Rubinius folks for giving me the idea in the first place.