apps VS go-github-mock

Access token is the simple way to authenticate to the Rest API. You simply need to go to your GitHub account settings then Developer Settings (or simply go to this URI), and then create an access token. You can either choose the classic tokens (no restriction) or the fine-grained token where you can use fine-tuned permissions.

Go to the GitHub Apps and select to create a new GitHub App

GitHub has tucked the personal access tokens admin in a slightly hard-to-find location. From anywhere in GitHub, you can click on your profile image → Settings → Developer Settings → Personal Access Tokens.

When you're on https://github.com/settings/apps (GitHub Apps) there will be an action list button called "Personal access tokens".

In your Github Settings, go to Developer settings. Then, in Personal access tokens, Generate a new classic token with scope: write:packages

To create your GithubProvider ID and SECRET, navigate to your GitHub account developer settings and click on the OAuth Apps tab to register a new application.

Github project is needed to authenticate users. You may do so by visiting https://github.com/settings/apps. Note the Client ID and Client secret. Also, set two Callback URLs for project and contributor authentication.

In my previous post, I developed a GitHub App. I found the app at this location:https://github.com/settings/apps to edit it. In the Permissions and Events tab, I updated the user permissions and the events I wanted my app to subscribe to. In this case, I wanted my app to listen to and have access to when a user starred the repository.

Next we need to go to https://github.com/settings/apps/new to configure the integration. Fill the fields as follows:

So far we've been testing the app with localtunnel, which is nice for quick ad-hoc tests against live API, but it doesn't replace proper unit tests. To write unit tests for this app, we need to mock-out the API to avoid being dependent on the external service. To do so, we can use go-github-mock: