slurper 0.1.0 → 0.2.0

data/README.rdoc

@@ -14,7 +14,7 @@ Slurper allows you to quickly compose your stories in a text file and import the
 
 == Setup
 
-gem install hashrocket-slurper
+  $gem install slurper
 
 == Config
 
@@ -33,13 +33,15 @@ The project_id tells tracker which project to add your stories to. It can be fou
 
 The token can be found on your personal profile page in Pivotal Tracker.
 
-The name, labels and description fields provide slurper with default values for story titles and descriptoins if you don't provide them in your stories.txt file.
+The name, labels and description fields provide slurper with default values for story titles and descriptoins if you don't provide them in your stories.slurper file.
 
 The requested_by field should be the name of your project stakeholder exactly as it appears in tracker.
 
 == Usage
 
-Create a stories.txt file and compose your stories in the slurper story format.
+Create a stories.slurper file and compose your stories in the slurper story format. In your working directory use the slurp command to import your stories from the stories.slurper file into Pivotal Tracker. If you have multiple story files for a project, stories.slurper and stories2.slurperfor example you can explicitly provide which file to slurp.
+
+  $slurp stories2.slurper
 
 === Example
 

data/bin/slurp

@@ -21,7 +21,7 @@ OptionParser.new do |opts|
   end
 end.parse!
 
-story_file = ARGV.empty? ? "stories.txt" : ARGV[0]
+story_file = ARGV.empty? ? "stories.slurper" : ARGV[0]
 
 story_lines = Array.new
 stories = Array.new

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification 
 name: slurper
 version: !ruby/object:Gem::Version 
-  version: 0.1.0
+  version: 0.2.0
 platform: ruby
 authors: 
 - Wes Gibbs
@@ -12,7 +12,7 @@ autorequire:
 bindir: bin
 cert_chain: []
 
-date: 2009-12-16 00:00:00 -05:00
+date: 2009-12-18 00:00:00 -05:00
 default_executable: slurp
 dependencies: 
 - !ruby/object:Gem::Dependency