pivotoolz 0.2.0 → 1.0.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
-SHA1:
-  metadata.gz: 7f72efc65285d87ffae7064cec06b0ad482114a7
-  data.tar.gz: b2a485f35a316a47f320123c67685bef40182c0f
+SHA256:
+  metadata.gz: c9bbddb0c21ad076943ee1ce72ab6cafd41459aeaf552e6fd74d30bc6065f60b
+  data.tar.gz: e582a7305bed0b5ac27c28ad1810d10587c379fc674ce8b908ec9047246aae06
 SHA512:
-  metadata.gz: 49d1f4aa7e15914ca3bb705dd767e80064acd91fd3f76610ea82b5636638f6ab89fc9094835c212360e27788618758e84db2784a2466c856292fd89f528412c5
-  data.tar.gz: 14907bd1939a6b5bccc87e0ead36a39e781362e07edf8939091dc1d5df9f1e7d3cd1a2e29f389a2b1573c10482b92b232d11c0596ce301c92547a285709d2667
+  metadata.gz: 8bed0db6bf96b4e83026a8799e2647070649227548f7efab6b6d52fc9055d32d21517a9d5b0d07ff2e383414b03b57aa2982b8fa124016a692c7784e01c5c96c
+  data.tar.gz: 4a648482e7ef1b245d1b5b6a35af088c42bbbc306b81554d3ed76de60859853a7660527a0d32eb08e01ca64b619233067cdbec5c21558d83e743ca2416cb3724

data/README.md

@@ -182,23 +182,18 @@ example:
 ### `pv-git-branch`
 
 Wouldn't it be nice to have all your Git branch names consistent with your dev team? Well now
-you can with `pv-git-branch`. Just pass `pv-git-branch` a Pivotal Story ID, and it will return
-branch name for you based on author name, the pivital story category, the pivotal story
-name and the pivotal story id. Be sure to set your `PIVOTAL_TRACKER_API_TOKEN` env variable is
-exported in your `.bashrc` file. If you want to explicitly set your initials as the author name,
+you can with `pv-git-branch`. Just pass `pv-git-branch` a Pivotal Story ID as a string, and it will create a new
+branch for you based on author name, the pivotal story category, the pivotal story
+name and the pivotal story id.
+Be sure to set your `PIVOTAL_TRACKER_API_TOKEN` env variable in your `.bashrc` file. If you want to explicitly set your initials as the author name,
 set your git config user initials like this: `git config --add user.initials af`. Otherwise it
 will take your `git config user.name` or `whoami` information.
 
 Example:
 ```bash
-pv-git-branch 111222333
-```
-This would return something like: `af/features/building-someting-greate-111222333`
-
-So it can be used with git like this:
-```bashr
-git checkout -b $(pv-git-branch 111222333)
+pv-git-branch "#111222333"
 ```
+This would create and checkout a new branch: `af/features/building-someting-great-111222333`
 
 ![usage](assets/pv-git-branch-demo.gif)
 

data/lib/pivotoolz/git_branch.rb

@@ -14,11 +14,15 @@ class GitBranch
     description = set_description(story['name'])
     pivotal_id  = story['id']
 
-    "#{author}/#{category}/#{description}-#{pivotal_id}"
+    create_branch("#{author}/#{category}/#{description}-#{pivotal_id}")
   end
 
   private
 
+  def create_branch(branch_name)
+    `git checkout -b #{branch_name}`
+  end
+
   def get_pivotal_story(pivotal_id)
     unless ENV['PIVOTAL_TRACKER_API_TOKEN']
       puts "!: You need to set the 'PIVOTAL_TRACKER_API_TOKEN' environment variable"
@@ -63,6 +67,6 @@ class GitBranch
   end
 
   def self.usage_message
-    "Usage : bin/git-branch-it [pivotal_story_id]"
+    "Usage : pv-git-branch '[pivotal_story_id]'"
   end
 end

data/lib/pivotoolz/version.rb

@@ -1,3 +1,3 @@
 module Pivotoolz
-  VERSION = "0.2.0"
+  VERSION = "1.0.0"
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: pivotoolz
 version: !ruby/object:Gem::Version
-  version: 0.2.0
+  version: 1.0.0
 platform: ruby
 authors:
 - Sufyan Adam
 autorequire: 
 bindir: exe
 cert_chain: []
-date: 2018-04-12 00:00:00.000000000 Z
+date: 2018-10-05 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: rest-client
@@ -135,7 +135,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
       version: '0'
 requirements: []
 rubyforge_project: 
-rubygems_version: 2.6.11
+rubygems_version: 2.7.7
 signing_key: 
 specification_version: 4
 summary: Tools to save you time when working with Pivotal Tracker stories