README.md in knife-spork-1.4.1 vs README.md in knife-spork-1.4.2

@@ -1,9 +1,10 @@
 KnifeSpork
 ===========
 KnifeSpork is a workflow plugin for `Chef::Knife` which helps multiple developers work on the same Chef Server and repository without treading on each other's toes. This plugin was designed around the workflow we have here at Etsy, where several people are working on the Chef repository and Chef Server simultaneously. It contains several functions, documented below:
 
+[![Build Status](https://travis-ci.org/jonlives/knife-spork.svg)](https://travis-ci.org/jonlives/knife-spork)
 [![Gem Version](https://badge.fury.io/rb/knife-spork.png)](http://badge.fury.io/rb/knife-spork)
 
 Installation
 ------------
 
@@ -77,10 +78,12 @@
     rooms:
       - [e-mail]/spork
       - [e-mail]/spork
   git:
     enabled: true
+    auto_push: true
+    branch: some_branch
   irccat:
     server: irccat.mydomain.com
     port: 12345
     gist: "/usr/bin/gist"
     channel: ["chef-annoucements"]
@@ -92,10 +95,11 @@
   slack:
     api_token: abc123
     channel: "#sysops"
     teamname: myteam
     username: knife
+    icon_url: http://example.com/image.jpg
   rubocop:
     epic_fail: true
     show_name: false
     autocorrect: false
     out_file: <file>
@@ -151,11 +155,11 @@
 #### Example
 
 ```text
 $ knife spork info
 Config Hash:
-{"plugins"=>{"git"=>{"enabled"=>true}, "irccat"=>{"server"=>"irccat.mydomain.com", "port"=>12345, "gist"=>"usr/bin/gist", "channel"=>["#chef-announce"]}, "graphite"=>{"server"=>"graphite.mydomain.com", "port"=>2003}, "slack"=>{"api_token"=>"abc123", "channel"=>"random", "teamname"=>"myteam"}, "eventinator"=>{"url"=>"http://eventinator.mydomain.com/events/oneshot"}}, "default_environments"=>["development", "production"], "version_change_threshold"=>2, "pplugins"=>{"foodcritic"=>{"fail_tags"=>["style,correctness,test"], "tags"=>["~portability"], "include_rules"=>["config/rules.rb"]}}}
+{"plugins"=>{"git"=>{"enabled"=>true}, "irccat"=>{"server"=>"irccat.mydomain.com", "port"=>12345, "gist"=>"usr/bin/gist", "channel"=>["#chef-announce"]}, "graphite"=>{"server"=>"graphite.mydomain.com", "port"=>2003}, "slack"=>{"api_token"=>"abc123", "channel"=>"random", "teamname"=>"myteam", "icon_url"=>"http://example.com/image.jpg"}, "eventinator"=>{"url"=>"http://eventinator.mydomain.com/events/oneshot"}}, "default_environments"=>["development", "production"], "version_change_threshold"=>2, "pplugins"=>{"foodcritic"=>{"fail_tags"=>["style,correctness,test"], "tags"=>["~portability"], "include_rules"=>["config/rules.rb"]}}}
 
 Plugins:
 KnifeSpork::Plugins::Campfire: disabled
 KnifeSpork::Plugins::Eventinator: enabled
 KnifeSpork::Plugins::Foodcritic: disabled
@@ -276,10 +280,10 @@
 Successfully uploaded apache2@1.0.13!
 ```
 
 Spork Promote
 -------------
-This function lets you easily set a version constraint in an environment or group of environments for a particular cookbook. By default it will set the version constraint to whatever the local version of the specified cookbook is. Optionally, you can include a `--version` option which will set the version constraint for the specified cookbook to whatever version number you provide. You might want to use this if, for example, you pushed a version constraint for a cookbook version you don't want your nodes to use anymore, so you want to "roll back" the environment to a previous version. You can also specify the `--remote` option if you'd like to automatically upload your changed local environment file to the server.
+This function lets you easily set a version constraint in an environment or group of environments for a particular cookbook. By default it will set the version constraint to whatever the local version of the specified cookbook is. Optionally, you can include a `--version` option which will set the version constraint for the specified cookbook to whatever version number you provide. You might want to use this if, for example, you pushed a version constraint for a cookbook version you don't want your nodes to use anymore, so you want to "roll back" the environment to a previous version. You can also specify the `--remote` option if you'd like to automatically upload your changed local environment file to the server. To promote to multiple environments, simply pass a list of them delimited with a comma.  
 
 If you don't specify an environment or environment group, the default_environments config directive will be used if set.
 
 #### Usage