public this repo is viewable by everyone
Description: A set of Sake tasks to make developing with Git easier.
Clone URL: git://github.com/eventualbuddha/sake-git.git
Oh wait, Github wants Textile.
28 days ago
commit  835bd93a838792771973e06c9554efea0a8f1999
tree    4741a50ef1e123ee5101f0c8bc0a22ff4952f2da
parent  b30c5237c925db31c03a4dda1d479fdb27910925
...
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
...
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
0
@@ -1,45 +0,0 @@
0
-Sake-Git
0
-========
0
-
0
-Here are a few Sake tasks to make developing with Git easier (and some corresponding Git aliases to
0
-make invoking them easier). Install them with:
0
-
0
- $ rake install
0
-
0
-Or, if you don't want to actually download this stuff, just use Sake:
0
-
0
- $ sake -i "http://github.com/eventualbuddha/sake-git/tree/master/git.rake?raw=true"
0
-
0
-Common Commands
0
----------------
0
-
0
- $ sake git:update
0
-
0
-Updates your current git repository, autodetecting whether you have a regular ol' git project or a
0
-git-svn project. I recommend aliasing it `git up'.
0
-
0
- $ sake git:push
0
-
0
-Commits any changes in your current branch not yet pushed upstream AND ports 'em over to master. I use `git ci' for this one.
0
-
0
- $ sake git:open [NAME=mynewbranch]
0
-
0
-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:
0
-
0
- $ git open mynewbranch
0
-
0
-You can even call it without the branch name and it'll ask you for it:
0
-
0
- $ git open
0
- * Name your branch: mynewbranch
0
-
0
- $ sake git:close [NAME=mynewbranch]
0
-
0
-This is open's brother, and should be used when you finish something and have already moved it to
0
-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'.
0
-
0
-Credits
0
--------
0
-
0
-Thanks to Coda Hale and everyone else at Wesabe for trying these out when I first wrote them and
0
-contributing tasks of their own, and to the Rubinius folks for giving me the idea in the first place.
...
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
...
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
0
@@ -0,0 +1,58 @@
0
+h1. Sake-Git
0
+
0
+Here are a few Sake tasks to make developing with Git easier (and some corresponding Git aliases to
0
+make invoking them easier). Install them with:
0
+
0
+<pre>
0
+$ rake install
0
+</pre>
0
+
0
+Or, if you don't want to actually download this stuff, just use Sake:
0
+
0
+<pre>
0
+$ sake -i "http://github.com/eventualbuddha/sake-git/tree/master/git.rake?raw=true"
0
+</pre>
0
+
0
+h2. Common Commands
0
+
0
+<pre>
0
+$ sake git:update
0
+</pre>
0
+
0
+Updates your current git repository, autodetecting whether you have a regular ol' git project or a
0
+git-svn project. I recommend aliasing it `git up'.
0
+
0
+<pre>
0
+$ sake git:push
0
+</pre>
0
+
0
+Commits any changes in your current branch not yet pushed upstream AND ports 'em over to master. I use `git ci' for this one.
0
+
0
+<pre>
0
+$ sake git:open [NAME=mynewbranch]
0
+</pre>
0
+
0
+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:
0
+
0
+<pre>
0
+$ git open mynewbranch
0
+</pre>
0
+
0
+You can even call it without the branch name and it'll ask you for it:
0
+
0
+<pre>
0
+$ git open
0
+* Name your branch: mynewbranch
0
+</pre>
0
+
0
+<pre>
0
+$ sake git:close [NAME=mynewbranch]
0
+</pre>
0
+
0
+This is open's brother, and should be used when you finish something and have already moved it to
0
+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'.
0
+
0
+h2. Credits
0
+
0
+Thanks to Coda Hale and everyone else at Wesabe for trying these out when I first wrote them and
0
+contributing tasks of their own, and to the Rubinius folks for giving me the idea in the first place.

Comments

    No one has commented yet.