CONTRIBUTING.md in hoe-reek-1.0.11 vs CONTRIBUTING.md in hoe-reek-1.1.0

@@ -1,25 +1,33 @@
-# IDEAS:
-
-* Add ideas on: https://github.com/saigkill/hoe-rubocop/issues
-
-## COOL HACKS:
-
-* Open a bugreport on https://github.com/saigkill/hoe-rubocop/issues.
-* Please use the -u flag when generating the patch as it makes the patch
-  more readable.
-* Write a good explanation of what the patch does.
-* It is better to use git format-patch command: git format-patch HEAD^
-
-# STRUCTURE:
-
-## BRANCHES:
-
-### `master` BRANCH:
-The master branch is the last stable version.
-
-### `develop` BRANCH:
-The develop branch is the current edge of development.
-
-### PULL REQUESTS:
-Please base all Pullrequests off the `develop` branch. Merges to
-`X.X` only occur through the `develop` branch.
\ No newline at end of file
+# Contributing
+
+## Branches
+
+### `master` branch
+
+The master branch is the current stable released version.
+
+### `develop` branch
+
+The develop branch is the current edge of development.
+
+## Forking
+
+1. Fork it
+2. Create your feature branch (`git checkout -b my-new-feature`)
+3. Commit your changes (`git commit -am 'Add some feature'`)
+4. Push to the branch (`git push origin my-new-feature`)
+5. Create new Pull Request
+
+## Pull requests
+
+* https://gitlab.com/saigkill/hoe-reek/merge_requests
+
+Please base all pull requests off the `develop` branch. Merges to
+`master` only occur through the `develop` branch. Pull requests
+based on `master` will likely be cherry picked.
+
+## Issues
+
+Need to report an issue? Use that issue tracker:
+
+* https://gitlab.com/saigkill/hoe-reek/issues