gitcycle 0.2.1 → 0.2.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (4) hide show
  1. data/README.md +23 -5
  2. data/gitcycle.gemspec +1 -1
  3. data/lib/gitcycle.rb +2 -2
  4. metadata +3 -3
data/README.md CHANGED
@@ -3,6 +3,8 @@ Gitcycle
3
3
 
4
4
  Tame your development cycle.
5
5
 
6
+ Gitcycle is a drop-in replacement for git that makes pull request dev cycles super easy.
7
+
6
8
  Get Started
7
9
  -----------
8
10
 
@@ -19,7 +21,6 @@ Type `gitc` + your ticket URL to create a new branch:
19
21
 
20
22
  gitc https://xxx.lighthouseapp.com/projects/0000/tickets/0000-my-ticket
21
23
 
22
-
23
24
  Pull Changes from Upstream
24
25
  --------------------------
25
26
 
@@ -27,6 +28,11 @@ When you're developing, you may need to pull new changes from an upstream branch
27
28
 
28
29
  gitc pull
29
30
 
31
+ Push Changes
32
+ ------------
33
+
34
+ gitc push
35
+
30
36
  Discuss Code
31
37
  ------------
32
38
 
@@ -98,11 +104,23 @@ More
98
104
 
99
105
  If you are working in a fork, it is easy to checkout upstream branches:
100
106
 
101
- gitc checkout [BRANCH] [...]
107
+ gitc checkout [BRANCH]
108
+
109
+ ### Collaborate
110
+
111
+ Its easy to checkout branches from other forks:
112
+
113
+ gitc checkout [USER] [BRANCH]
114
+
115
+ ### QA Status
116
+
117
+ See who is QA'ing what:
118
+
119
+ gitc qa
102
120
 
103
- ### Reset Branch
121
+ ### Redo Branch
104
122
 
105
- If you associate the wrong branch with a ticket, use `gitc reset` to fix it.
123
+ If you associate the wrong branch with a ticket, use `gitc redo` to fix it.
106
124
 
107
125
  Checkout the branch that you will eventually merge your feature into:
108
126
 
@@ -110,7 +128,7 @@ Checkout the branch that you will eventually merge your feature into:
110
128
 
111
129
  Type `gitc reset` + your ticket URL to reset the branch:
112
130
 
113
- gitc reset https://xxx.lighthouseapp.com/projects/0000/tickets/0000-my-ticket
131
+ gitc redo https://xxx.lighthouseapp.com/projects/0000/tickets/0000-my-ticket
114
132
 
115
133
  Todo
116
134
  ----
data/gitcycle.gemspec CHANGED
@@ -6,7 +6,7 @@ $:.unshift lib unless $:.include?(lib)
6
6
 
7
7
  Gem::Specification.new do |s|
8
8
  s.name = "gitcycle"
9
- s.version = '0.2.1'
9
+ s.version = '0.2.2'
10
10
  s.platform = Gem::Platform::RUBY
11
11
  s.authors = [ 'Winton Welsh' ]
12
12
  s.email = [ 'mail@wintoni.us' ]
data/lib/gitcycle.rb CHANGED
@@ -213,7 +213,7 @@ class Gitcycle
213
213
 
214
214
  def push
215
215
  branch = pull
216
- remote = branch ? branch['home'] : 'origin'
216
+ remote = branch && branch['collab'] == '1' ? branch['home'] : 'origin'
217
217
 
218
218
  puts "\nPushing branch '#{remote}/#{branch}'.\n".green
219
219
  run("git push #{remote} #{branch}")
@@ -355,7 +355,7 @@ class Gitcycle
355
355
  end
356
356
  end
357
357
 
358
- def reset(ticket_or_url)
358
+ def redo(ticket_or_url)
359
359
  create_branch(ticket_or_url, true)
360
360
  end
361
361
 
metadata CHANGED
@@ -1,13 +1,13 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: gitcycle
3
3
  version: !ruby/object:Gem::Version
4
- hash: 21
4
+ hash: 19
5
5
  prerelease:
6
6
  segments:
7
7
  - 0
8
8
  - 2
9
- - 1
10
- version: 0.2.1
9
+ - 2
10
+ version: 0.2.2
11
11
  platform: ruby
12
12
  authors:
13
13
  - Winton Welsh