Preparation for v0.0.6 release

Updated docs and metadata info.

CHANGELOG.md

@@ -0,0 +1,14 @@
+##2015-02-24 - Release 0.0.6
+###Summary
+
+This release has many new parameters enabling the ability to set different triggers for webhooks on GitLab and disabling ssl checks on GitHub.  Minor cleanup as well.
+
+The [README](https://github.com/abrader/abrader-gms/blob/master/README.md) has been updated to include the usage notes for these parameters.
+
+####Features
+- New parameters - `GitLab`
+  - `merge_request_events`
+  - `tag_push_events`
+  - `issue_events`
+- New parameters - `GitHub`
+  - `disable_ssl_verify`

README.md

@@ -212,4 +212,24 @@ git_webhook { 'web_post_receive_webhook' :
 }
 ```
 
---
+## Limited use access tokens (GitHub only)
+
+By heading over the following link:
+
+[Create a GitHub Access Token](https://github.com/settings/tokens/new)
+
+You should see a screen that resembles something like the following image:
+
+![alt text](https://github.com/abrader/abrader-gms/raw/master/github_new_token.png "GitHub Access Token")
+
+By highlighting **only** the following options:
+
+* write:repo_hook
+* read:repo_hook
+* admin:repo_hook
+
+You are limiting this token to only be able to manage webhooks.  This may be very beneficial to you if the current tokens available to you entitle too much access. Ultimately, you are puppetizing webhook creation, limiting scope of the token capability only makes sense.
+
+
+
+--

metadata.json

@@ -1,6 +1,6 @@
 {
   "name": "abrader-gms",
-  "version": "0.0.5",
+  "version": "0.0.6",
   "author": "Andrew Brader",
   "summary": "Git Management Systems API Types & Providers",
   "license": "Apache-2.0",