public
Description: Don't use this. It's slow and requires ruby and sake. Use this: http://gist.github.com/12718
Homepage: http://gist.github.com/12718
Clone URL: git://github.com/eventualbuddha/sake-git.git
commit  2f6ed83408b032d68e2387d3e7b445909503cb7b
tree    fe4c62e314ddd7a025ee9d3f27c6be832884659f
parent  53acbc6559aa5e88b69c5543d423d81866c7a791
sake-git / README
100644 66 lines (38 sloc) 1.491 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
59
60
61
62
63
64
65
66
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:
 
$ rake install
 
 
Common Commands
---------------
 
$ sake git:update
 
Updates your current git repository, autodetecting whether you have a regular ol' git project or a
git-svn project. Alias it to `git up' with this alias:
 
[alias]
  up = !sake git:update
 
 
$ sake git:push
 
Commits any changes in your current branch not yet pushed upstream AND ports 'em over to master.
Another alias for ya:
 
[alias]
  ci = !sake git:push
 
 
$ sake git:open [NAME=mynewbranch]
 
Creates a new branch off master. Think of this as opening an issue, or a new path of development.
Because of the way Rake handles (or _doesn't_ handle) arguments, the alias for this one is a little
weird:
 
[alias]
  open = !sake git:open NAME= -- $1
 
Allowing you to call it like so:
 
$ git open mynewbranch
 
You can even call it without the branch name and it'll ask you for it:
 
$ git open
* Name your branch: mynewbranch
 
 
$ sake git:close [NAME=mynewbranch]
 
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. Aliases for
everyone:
 
[alias]
  close = !sake git:close NAME= -- $1
 
 
 
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.