remove outdated info

Author: skywinder

CONTRIBUTING.md

@@ -11,6 +11,34 @@ Bug reports and pull requests from users are what keep this project working.
 5. Publish the branch (`git push origin my-new-feature`)
 6. Create a new Pull Request
 
+## Running for development
+
+Make sure you have `ruby`, `gem` and `bundle` installed locally.
+
+If you don't: `gem install bundler`
+
+#### Step 1: Install requirements
+
+```
+bundle install
+```
+
+#### Step 2: Install linters: overcommit, rubocop
+
+```
+overcommit --install
+```
+
+#### Step 3: Run & debug
+
+TBD 
+
+#### Step 4: Test it
+
+```
+bundle exec rake
+```
+
 ## Checking your work
 
 You can test your workflow with changelog generator with

README.md

@@ -5,11 +5,6 @@
 
 # github-changelog-generator ![GitHub Logo](../master/images/logo.jpg)
 
-#### Update:
-
-🖖 Keep it alive: We need more Collaborators to github-changelog-generator [#727](https://github.com/github-changelog-generator/github-changelog-generator/issues/727)
-
----
 <!--
 To update TOC, please run:
 > doctoc ./README.md --github
@@ -289,27 +284,6 @@ I'm not trying to compare the quality of handwritten and auto-generated logs. Th
 
 An auto-generated changelog really helps, even if you manually fill in the release notes!
 
-For example:
-
-When you find a closed bug, it is very useful to know which release fixed it.
-So that you can easily find the issue by \# in `CHANGELOG.md`.
-
-- It's not quite as easy to find this in handwritten releases notes.
-- A generated file saves you the trouble of remembering everything;
-  sometimes people forget to add things to a handwritten file.
-
-Ultimately, I think GitHub Releases are ideal for end-users.
-Meanwhile, `CHANGELOG.md` lives right in the repository, with its detailed list of changes, which is handy for developers.
-Finally, there's nothing wrong with using GitHub Releases alongside `CHANGELOG.md` in this combination.
-
-- ***I got an "API rate limit exceeded" error message. What does this mean?***
-
-GitHub [limits the number of API requests](https://developer.github.com/v3/#rate-limiting) you can make in an hour. You can make up to 5,000 requests per hour. For unauthenticated requests, the rate limit is only up to 60 requests per hour. Unauthenticated requests are associated with your IP address (not the user making requests).
-
-If you're seeing this warning, please do the following:
-
-1. Make sure you're providing an OAuth token, so you're not making requests anonymously. Using an OAuth token increases your hourly request maximum from 60 to 5000.
-2. If you have a large repo with lots of issues/PRs, you can use `--max-issues NUM` to limit the number of issues that are pulled back. For example: `--max-issues 1000`
 
 - ***My Ruby version is very old, can I use this?***
 
@@ -349,7 +323,7 @@ We have collected notes on how to contribute to this project in [CONTRIBUTING.md
 [CONTRIBUTING.md]: CONTRIBUTING.md
 
 ## Contact us
-Feel free to ask your questions [gitter.im chat])https://gitter.im/github-changelog-generator)
+[Join the chat at gitter : github-changelog-generator](https://gitter.im/github-changelog-generator/chat?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge)
 
 ## License