git_commands 3.0.3 → 3.0.4

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 1ae2bbf9cdd38b13af1e132df51c7ff7a39e2481
-  data.tar.gz: 42897c46f486c0dbcb101e27c897df5adfddbc62
+  metadata.gz: 8c5ee655beae7fa80652b9f87b2eadb5f9071490
+  data.tar.gz: aa39a9867606d3bc95ae6a85c2ade4dd0e33c5b9
 SHA512:
-  metadata.gz: 849f09efd4b6c6053b047d27d4556ec970a60bdac01d6107ae602611c0d7ad25a958294b07a90fe2379f233c7825156f02e8510ecc86b8b52435299760178df1
-  data.tar.gz: 23f208d27d078d2db105cd35a631c4e310842a5cfe006e0ff36a3f40afab9ae1d1b8e0b84afe4ba74159f702dc58109c0cc07ee1611a29d6f1e44f715bf58080
+  metadata.gz: 078b02de2b4afed47f954be07badb0ddf1a337ad063ad3e6c58f8545208b61683225341ee7a9bbaddedd2e76f7e13992dbe0cea23de20bd51fe7018eeef17e63
+  data.tar.gz: c9ad03c652bad9e7bfeea2c0abfc9b5ba5a74cbdde424a6fb686a5709a5df1ddec1f7624fc0db96f62f81f5107dc80db3879ab898074b8046851a5b25fca4457

data/README.md

@@ -16,7 +16,7 @@ This script will facilitate adopting a subset of the branch-featuring workflow c
 * **release** branches are created **aggregating multiple branches** into a new one
 
 ## Scope
-The scope of this is helping out in the following cases:
+The scope of this gem is helping out in the following cases:
 * you have multiple feature branches waiting for release due to some reason (i.e. long QA time...), and need to keep them aligned with master
 * you need to quickly aggregate branches for a release
 
@@ -24,14 +24,14 @@ The scope of this is helping out in the following cases:
 I assume you have GIT installed ;)  
 Just install the gem to use the binaries commands.
 ```
-gem isntall git_commands
+gem install git_commands
 ```
 
 ## Usage
 Here are the main commands:
 
 ### Help
-Each command has an help option that can be displayed:
+Each command come with a help option that can be displayed:
 
 ```
 rebase --help
@@ -43,13 +43,20 @@ Usage: rebase --repo=./Sites/oro --branches=feature/add_bin,fetaure/remove_rake_
 
 ### rebase
 This is probably the most useful command in case you have several branches to rebase with _origin/master_ frequently.
-A confirmation is asked to continue.  
+A confirmation is asked to before rebasing.  
 
 ```
 rebase --repo=~/Sites/greatest_hits --branches=feature/love_me_tender,feature/teddybear,feature/return_to_sender
 ```
 
-You can also specify as the *branches* the path to a file containing multiple branches on each line:
+You can also specify as the *branches* argument a path to a file containing the branches names on each line, like this:
+
+```txt
+feature/love_me_tender
+feature/teddybear
+feature/return_to_sender
+feature/in_the_ghetto
+```
 
 ```
 rebase --repo=~/Sites/greatest_hits --branches=~/greatest_hits/.branches
@@ -57,7 +64,7 @@ rebase --repo=~/Sites/greatest_hits --branches=~/greatest_hits/.branches
 
 ### purge
 This command remove the specified branches locally and remotely.  
-A confirmation is asked before each removal.  
+A confirmation is asked before removal.  
 
 ```
 purge --repo=~/temp/top_20 --branches=release/in_the_ghetto
@@ -66,7 +73,7 @@ purge --repo=~/temp/top_20 --branches=release/in_the_ghetto
 ### aggregate
 It should be useful to aggregate your branches into a single one in case you want to create a release branch.  
 It uses the following naming convention: *release/yyyy_mm_dd*  
-A confirmation is asked to continue.  
+A confirmation is asked before aggregating.  
 
 ```
 aggregate --repo=~/Sites/greatest_hits --branches=~/greatest_hits/.branches

data/lib/git_commands/version.rb

@@ -1,3 +1,3 @@
 module GitCommands
-  VERSION = "3.0.3"
+  VERSION = "3.0.4"
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: git_commands
 version: !ruby/object:Gem::Version
-  version: 3.0.3
+  version: 3.0.4
 platform: ruby
 authors:
 - costajob
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2016-10-13 00:00:00.000000000 Z
+date: 2016-10-17 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: bundler