patchy 1.0.0b1 → 1.0.0b2

data/README.md

@@ -21,7 +21,8 @@ specify it as the second argument:
     patchy 1234 2-3-stable
 
 What this will do is to to check out the base branch (`master` or what you
-specify) and then create a `1234` branch in this case.
+specify), do a `git pull` to make sure it's up to date, and then create a
+`1234` branch in this case.
 
 ### Finishing
 
@@ -44,7 +45,7 @@ commit message. Patchy shows you which commands it runs and asks you to approve
 the output of certain critical commands before moving on.
 
 I encourage you to take a look at the source code (in `bin/patchy`). It's only
-54 lines "long" and helps you understand what exactly Patchy does for you.
+55 lines "long" and helps you understand what exactly Patchy does for you.
 
 ## Copyright
 

data/bin/patchy

@@ -32,6 +32,7 @@ if ARGV[0] =~ /^\d+$/
   unless base_branch == current_branch
     run("git checkout #{base_branch}")
   end
+  run("git pull")
   run("git checkout -b #{ticket}")
 else
   message = ARGV[0]

data/lib/patchy/version.rb

@@ -1,3 +1,3 @@
 module Patchy
-  VERSION = '1.0.0b1'
+  VERSION = '1.0.0b2'
 end

metadata

@@ -1,13 +1,12 @@
 --- !ruby/object:Gem::Specification 
 name: patchy
 version: !ruby/object:Gem::Version 
-  hash: 415574164
   prerelease: true
   segments: 
   - 1
   - 0
-  - 0b1
-  version: 1.0.0b1
+  - 0b2
+  version: 1.0.0b2
 platform: ruby
 authors: 
 - David Trasbo
@@ -15,7 +14,7 @@ autorequire:
 bindir: bin
 cert_chain: []
 
-date: 2010-06-28 00:00:00 +02:00
+date: 2010-06-29 00:00:00 +02:00
 default_executable: 
 dependencies: []
 
@@ -46,7 +45,6 @@ required_ruby_version: !ruby/object:Gem::Requirement
   requirements: 
   - - ">="
     - !ruby/object:Gem::Version 
-      hash: 3
       segments: 
       - 0
       version: "0"
@@ -55,7 +53,6 @@ required_rubygems_version: !ruby/object:Gem::Requirement
   requirements: 
   - - ">"
     - !ruby/object:Gem::Version 
-      hash: 25
       segments: 
       - 1
       - 3