Collect Github Forks

[A-Guldborg]

Additionally, in your GitInsight back-end applications implement a new analysis. It should be able to list all forks of a repository on GitHub. To do so, it should call the GitHub REST API and collect a list of all forks from a given repository. That is, when your GitInsight REST API receives a GET request with a GitHub repository identifier of the form <github_user>/<repository_name> or <github_organization>/<repository_name>, then besides the two already existing analyses of cloned Git repositories your application contacts the GitHub REST API to collect the number of forks of that repository.

To connect to the GitHub REST API, you need an Access Token. Read this documentation on how to receive an Access Token for the GitHub REST API. Remember and double check on how Rasmus demonstrated to handle secrets like access tokens in .Net projects. That is, do not store the access token directly in your source code. It should never end up in your source code repository that is publicly shared with the world.

[OliFryser]

#100
#99