checkcheckit 0.3.0 → 0.3.1

Sign up to get free protection for your applications and to get access to all the features.
data/README.md CHANGED
@@ -16,14 +16,6 @@ Everything beneath a step is that step's body or description.
16
16
 
17
17
  ## Usage
18
18
 
19
- # list your checklists
20
- $ check list
21
- # Checklists
22
- personal
23
- groceries
24
- work
25
- deploy
26
-
27
19
  # it's all text
28
20
  $ cat ~/checkcheckit/personal/groceries.md
29
21
  - bacon
@@ -33,7 +25,7 @@ Everything beneath a step is that step's body or description.
33
25
  - avocados
34
26
 
35
27
  # start a list at the command line and keep it there
36
- $ check start groceries
28
+ $ check start ~/checkcheckit/personal/groceries.md
37
29
  |.......| Step 1: bacon
38
30
  Check: <enter>
39
31
 
@@ -46,57 +38,47 @@ Everything beneath a step is that step's body or description.
46
38
  $ check start groceries --live --no-cli -O
47
39
  Live at URL: http://checkcheckit.herokuapp.com/4f24b9d933d5467ec913461b8da3f952dbe724cb
48
40
 
49
- ### `list` the checklists
50
-
51
- `checkcheckit` assumes a home directory of ~/checkcheckit
41
+ # Use it with any text file
42
+ $ check start /Users/csquared/checkcheckit/groceries.md
52
43
 
53
- In that directory are folders for your organizations, groups, etc.
54
-
55
- In those folders are your checklists.
44
+ # When files are in `~/checkcheckit`
56
45
 
46
+ # list your checklists
57
47
  $ check list
58
48
  # Checklists
59
- heroku
60
- todo
61
49
  personal
62
- todo
63
- vault
50
+ groceries
51
+ work
64
52
  deploy
65
53
 
66
- ### `start` a checklist
54
+ # Start with shortcut names
55
+ $ check start groceries
67
56
 
68
- You can go through a checklist by running `check start ` and then the checklist name.
57
+ # Run commands from the checklist
58
+ $ cat ./hello.txt
59
+ - say hello
60
+ `echo hello`
69
61
 
70
- If there are multiple checklists with the same name use the format `folder/checklist`.
62
+ $ check start ./hello.txt
63
+ |.| Step 1: say hello
64
+ `echo hello`
71
65
 
72
- When you iterate through a checklist you can just type "enter", "y", or "+" to confirm a step and "no" or "-" to
73
- fail one.
74
-
75
- You can use the `--notes` flag to enter optional notes.
66
+ Run command `echo hello`?
67
+ <enter>,y,n:
68
+ running `echo hello`
69
+ hello
70
+ Check:
76
71
 
77
- For example:
72
+ |+| Done
78
73
 
79
- $ check start deploy --notes
80
- |.......| Step 1: Pull everything from git
81
- > git pull origin
82
- Check: <enter>
83
- Notes: <enter>
74
+ ### `start` a checklist
84
75
 
85
- |+......| Step 2: Make sure there are no uncommitted changes
86
- > `git status`
87
- Check: <n>
88
- Notes: <enter>
76
+ You can go through a checklist by running `check start ` and then the checklist name.
89
77
 
90
- |+-.....| Step 3: Diff master with heroku/master
91
- Make sure the change you want to push are what you're pushing
92
- > git fetch heroku
93
- > git diff heroku/master | $EDITOR
94
- Check: <y>
95
- Notes: <enter>
78
+ If there are multiple checklists with the same name use the format `folder/checklist`.
96
79
 
97
- |+-+....| Step 4: Run the test suite
98
- Check: failures!
99
- Notes: <enter>
80
+ When you iterate through a checklist you can just type "enter", "y", or "+" to confirm a step and "no" or "-" to
81
+ fail one.
100
82
 
101
83
  ### `--live` mode
102
84
 
@@ -123,7 +105,38 @@ disconnect the command line and continue finishing it (with others).
123
105
  During that console session the web UI would be interactively crossing items off the list:
124
106
  <img height="400px" src="http://f.cl.ly/items/1h3V0L1a1p1a062I2X3f/Screen%20Shot%202012-12-16%20at%209.37.56%20PM.png" />
125
107
 
126
- ### Email
108
+ ### shell out to commands
109
+
110
+ This is useful.
111
+
112
+ `check` will recognize any text that is surrouned with backticks: \`command with args\` as a command to potentially run.
113
+ It will prompt you if you'd like it to run the command. You will then have the option to check it off.
114
+
115
+ For example:
116
+
117
+ $ cat ./hello.txt
118
+ - say hello
119
+ `echo hello`
120
+
121
+ $ check start ./hello.txt
122
+ |.| Step 1: say hello
123
+ `echo hello`
124
+
125
+ Run command `echo hello`?
126
+ <enter>,y,n:
127
+ running `echo hello`
128
+ hello
129
+ Check:
130
+
131
+ |+| Done
132
+
133
+
134
+
135
+ #### `--open/-O`
136
+
137
+ `check start <listname> --live -O/--open` will open the url in your browser by shelling out to `open`
138
+
139
+ #### `--email <address(es)>`
127
140
  Specify an email (or a comma-separated list) on the command line via the `--email` flag and
128
141
  the address(es) will receive an email with a link to a web version of the checklist.
129
142
 
@@ -136,6 +149,27 @@ the address(es) will receive an email with a link to a web version of the checkl
136
149
  Check: ^C
137
150
  bye
138
151
 
152
+ ### `list` the checklists
153
+
154
+ `checkcheckit` works with a normal filename.
155
+
156
+ However, it also assumes a home directory of ~/checkcheckit
157
+
158
+ In that directory are folders for your organizations, groups, etc so you can start
159
+ them by name.
160
+
161
+ In those folders are your checklists.
162
+
163
+ $ check list
164
+ # Checklists
165
+ heroku
166
+ todo
167
+ personal
168
+ todo
169
+ vault
170
+ deploy
171
+
172
+
139
173
  ## TODO
140
174
 
141
175
  - resume a run locally from URL
@@ -0,0 +1,2 @@
1
+ - say hello
2
+ `echo hello`
@@ -116,7 +116,7 @@ class CheckCheckIt::Console
116
116
  puts input.inspect if debug?
117
117
  case input
118
118
  when /^(y|)$/
119
- puts "running `#{command}`"
119
+ puts "running..."
120
120
  system(command)
121
121
  else
122
122
  puts "skipping"
@@ -1,3 +1,3 @@
1
1
  module CheckCheckIt
2
- VERSION = "0.3.0"
2
+ VERSION = "0.3.1"
3
3
  end
@@ -55,7 +55,7 @@ class ConsoleTest < CheckCheckIt::TestCase
55
55
  console.out_stream.expect :puts, true, ["\nRun command `git pull`?"]
56
56
  console.out_stream.expect :print, true, ["<enter>,y,n: "]
57
57
  console.in_stream.expect :gets, ""
58
- console.out_stream.expect :puts, true, ["running `git pull`"]
58
+ console.out_stream.expect :puts, true, ["running..."]
59
59
  mock(console).system("git pull") { true }
60
60
  console.out_stream.expect :print, true, ["Check: "]
61
61
  console.in_stream.expect :gets, ""
metadata CHANGED
@@ -1,7 +1,7 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: checkcheckit
3
3
  version: !ruby/object:Gem::Version
4
- version: 0.3.0
4
+ version: 0.3.1
5
5
  prerelease:
6
6
  platform: ruby
7
7
  authors:
@@ -9,7 +9,7 @@ authors:
9
9
  autorequire:
10
10
  bindir: bin
11
11
  cert_chain: []
12
- date: 2013-02-12 00:00:00.000000000 Z
12
+ date: 2013-07-23 00:00:00.000000000 Z
13
13
  dependencies:
14
14
  - !ruby/object:Gem::Dependency
15
15
  name: lucy-goosey
@@ -92,6 +92,7 @@ files:
92
92
  - bin/check
93
93
  - bin/t
94
94
  - checkcheckit.gemspec
95
+ - examples/hello.txt
95
96
  - lib/checkcheckit.rb
96
97
  - lib/checkcheckit/console.rb
97
98
  - lib/checkcheckit/list.rb
@@ -116,7 +117,7 @@ required_ruby_version: !ruby/object:Gem::Requirement
116
117
  version: '0'
117
118
  segments:
118
119
  - 0
119
- hash: -1655738984959365236
120
+ hash: 3147570249937767500
120
121
  required_rubygems_version: !ruby/object:Gem::Requirement
121
122
  none: false
122
123
  requirements:
@@ -125,7 +126,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
125
126
  version: '0'
126
127
  segments:
127
128
  - 0
128
- hash: -1655738984959365236
129
+ hash: 3147570249937767500
129
130
  requirements: []
130
131
  rubyforge_project:
131
132
  rubygems_version: 1.8.23