penchant 0.2.17 → 0.2.18

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.
data/README.md CHANGED
@@ -189,6 +189,17 @@ of `bundle exec rake` *after* I've already committed code. Since we have compute
189
189
  you can add `ensure_git_hooks!` anywhere in your `Gemfile.penchant` to make sure the git hooks are symlinked to the ones
190
190
  in the `script/hooks` directory with every processing of `Gemfile.penchant`.
191
191
 
192
+ ### Performing pre-`bundle exec rake` tasks.
193
+
194
+ Example: I use a style of Cucumber testing where I co-opt the `@wip` tag and then tell Guard to only run scenarios with `@wip` tags.
195
+ I don't want `@wip` tasks to be committed to the repo, since committing a half-completed scenario seems silly.
196
+ So I use `bundle exec rake preflight_check` to check all feature files for `@wip` tasks, and to fail if I hit one. Yes, Cucumber
197
+ already does this, but in order to get to `bundle exec rake`, I need to go through two `Gemfile` creations, one for `remote --deployment`
198
+ and one for `remote` to make sure my tests work on remote gems only.
199
+
200
+ If `bundle exec rake -T preflight_check` returns a task, that task will be run before all the `Gemfile` switcheroo. *Don't use it
201
+ as a place to run your tests!*
202
+
192
203
  ### Skipping all that Rake falderal?
193
204
 
194
205
  Do it Travis CI style: stick `[ci skip]` in your commit message. That's why the meat of the git hooks resides in
@@ -1,3 +1,3 @@
1
1
  module Penchant
2
- VERSION = "0.2.17"
2
+ VERSION = "0.2.18"
3
3
  end
@@ -1,5 +1,11 @@
1
1
  #!/bin/bash
2
2
 
3
+ if [ $(bundle exec rake -T preflight_check | wc -l) -eq 1 ]; then
4
+ bundle exec rake preflight_check
5
+ R=$?
6
+ if [ $R -ne 0 ]; then exit $R; fi
7
+ fi
8
+
3
9
  unset GIT_DIR
4
10
  penchant gemfile remote --deployment
5
11
  GIT_DIR=$OLD_GIT_DIR
metadata CHANGED
@@ -1,7 +1,7 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: penchant
3
3
  version: !ruby/object:Gem::Version
4
- version: 0.2.17
4
+ version: 0.2.18
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: 2012-08-13 00:00:00.000000000 Z
12
+ date: 2012-08-15 00:00:00.000000000 Z
13
13
  dependencies:
14
14
  - !ruby/object:Gem::Dependency
15
15
  name: bundler
@@ -199,7 +199,7 @@ required_ruby_version: !ruby/object:Gem::Requirement
199
199
  version: '0'
200
200
  segments:
201
201
  - 0
202
- hash: -2365201167288047
202
+ hash: 1954295842592246039
203
203
  required_rubygems_version: !ruby/object:Gem::Requirement
204
204
  none: false
205
205
  requirements:
@@ -208,7 +208,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
208
208
  version: '0'
209
209
  segments:
210
210
  - 0
211
- hash: -2365201167288047
211
+ hash: 1954295842592246039
212
212
  requirements: []
213
213
  rubyforge_project: penchant
214
214
  rubygems_version: 1.8.23