Adding to README instructions for creating and loading a GitHub token

Author: llavarello

README.md

@@ -37,6 +37,19 @@ Please refer to the Documentation for additional use-cases and introductory info
 - [https://kulkansecurity.github.io/gitxray/](https://kulkansecurity.github.io/gitxray/)
 - [https://www.gitxray.com/](https://www.gitxray.com/)
 
+# Rate Limits and the GitHub API
+
+Gitxray gracefully handles Rate Limits and can work out of the box without a GitHub API key, but you'll likely hit RateLimits pretty fast (A small to medium-size repository with 10+ Contributors could take hours to complete while it waits for RateLimits to reset) This is detailed by GitHub in their [documentation here](https://docs.github.com/en/rest/using-the-rest-api/rate-limits-for-the-rest-api?apiVersion=2022-11-28#primary-rate-limit-for-unauthenticated-users). 
+
+[Creating a simple read-only token scoped to PUBLIC repositories](https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/managing-your-personal-access-tokens#creating-a-fine-grained-personal-access-token) will however help you increase those restrictions considerably. If you're not in a hurry or can leave gitxray running you'll be able to use its full capacity, as it pauses execution while waiting for the limits to lift.
+
+You may then load the token safely by using (prevents the token from being displayed on screen or getting logged in your shell history):
+
+```bash
+read -rs GH_ACCESS_TOKEN
+export
+```
+
 # Installing, Updating, and running Gitxray
 
 gitxray was written with no use of external package dependencies other than the `requests` library.