git-runner 0.1.2 → 0.1.3

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA1:
+  metadata.gz: 7a10e80ae51b76c698b01112d4ce9e83fb682b26
+  data.tar.gz: 612fd10eebabaa569632d4828c86b91b9402e202
+SHA512:
+  metadata.gz: 034cee972df2a9f27ddde4c60662d41918ac7b761d51752a77f9865a440a217cfe767c4a61d732217ccd1a9b573375f5eac4ec252f34e22ac329a83d6142d26a
+  data.tar.gz: 022bad902f351438f1119091e265f76a0a43ce1e8cdf90c687b8dfab84684efef2bc1ccb22d6834d66e35c4af3451a73909133878f61684652f86af7f87ac478

data/README.md

@@ -9,14 +9,14 @@ It works by having the git server-side post-update hook (`hooks/post-update`) in
 
 Git Runner instructions are distrubuted as separate gems, see **Available Instructions** below for what instructions are currently available for use.
 
-Have a look at this short [demonistration video](http://ascii.io/a/1349) for what it looks like for a user pushing to a Git Runner enabled repository (using `git-runner-deploy`).
+Have a look at this short [demonstration video](http://ascii.io/a/1349) for what it looks like for a user pushing to a Git Runner enabled repository (using `git-runner-deploy`).
 
 
 ## Why?
 
 #### Origins
 
-Git Runner originated from a need to simply the deployment process (capistrano) within my organisation for people who don't have their environments setup with ruby and the required gems. I wanted to make the process work for even those who are using GUI git clients.
+Git Runner originated from a need to simplify the deployment process (capistrano) within my organisation for people who don't have their environments setup with ruby and the required gems. I wanted to make the process work for even those who are using GUI git clients.
 
 
 #### Wouldn't a simple script do the job?

data/lib/git-runner/branch.rb

@@ -24,6 +24,9 @@ module GitRunner
 
   private
     def extract_instructions
+      # Check if the instructions file exists
+      return unless File.exist?(File.join(repository_path, Configuration.instruction_file))
+
       # Use git to grep the current branch for instruction lines within the specific instruction file
       output = Command.execute(
         "cd #{repository_path}",

data/lib/git-runner/version.rb

@@ -1,3 +1,3 @@
 module GitRunner
-  VERSION = '0.1.2'
+  VERSION = '0.1.3'
 end

metadata

@@ -1,30 +1,27 @@
 --- !ruby/object:Gem::Specification
 name: git-runner
 version: !ruby/object:Gem::Version
-  version: 0.1.2
-  prerelease: 
+  version: 0.1.3
 platform: ruby
 authors:
 - James Brooks
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2012-10-26 00:00:00.000000000 Z
+date: 2013-02-26 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: session
   requirement: !ruby/object:Gem::Requirement
-    none: false
     requirements:
-    - - ! '>='
+    - - '>='
       - !ruby/object:Gem::Version
         version: 3.1.0
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
-    none: false
     requirements:
-    - - ! '>='
+    - - '>='
       - !ruby/object:Gem::Version
         version: 3.1.0
 description: GitRunner is a ruby framework to implement and run tasks after code has
@@ -58,26 +55,25 @@ files:
 - lib/git-runner/version.rb
 homepage: https://github.com/JamesBrooks/git-runner
 licenses: []
+metadata: {}
 post_install_message: 
 rdoc_options: []
 require_paths:
 - lib
 required_ruby_version: !ruby/object:Gem::Requirement
-  none: false
   requirements:
-  - - ! '>='
+  - - '>='
     - !ruby/object:Gem::Version
       version: '0'
 required_rubygems_version: !ruby/object:Gem::Requirement
-  none: false
   requirements:
-  - - ! '>='
+  - - '>='
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
 rubyforge_project: 
-rubygems_version: 1.8.24
+rubygems_version: 2.0.0
 signing_key: 
-specification_version: 3
+specification_version: 4
 summary: Ruby framework to run tasks after code has been pushed to a Git repository.
 test_files: []