fix(oauth-scopes): reduce required scopes to the minimum

[Anthony-Jhoiro]

Currently, the Outstatic documentation says to create an Oauth application to manage user authentication.
This is great but GitHub recommends the usage of GitHub application instead which provides Fine Grained access to resources and can limit Outstatic accesses to a single repository (if needed).

Changes :

• Documentation about GitHub Application added
• Reduce OAuth scopes to only "read:user" and "repo"

Bug

• Related issues linked using fixes #number
• Integration tests added
• Errors have a helpful link attached, see contributing.md

[vercel]

Someone is attempting to deploy a commit to a Personal Account owned by @avitorio on Vercel.

@avitorio first needs to authorize it.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
outstatic-canary	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Sep 23, 2023 11:29pm
outstatic-dev-blog	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Sep 23, 2023 11:29pm
outstatic-web	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Sep 23, 2023 11:29pm

[avitorio]

Hey @Anthony-Jhoiro,

Thank you for this. I noticed that when I follow the steps it seems we are missing something.
When I log into outstatic, I get asked to authorize the app, and then I'm redirected back to the Dashboard.
But none of the collections/documents are available. Only after I go back to Github and click on Install App:

I get this:

And then I'm able to see the contents of the repository on the Dashboard.
Is there a simpler way to achieve this? I was hoping to get that last screenshot when logging in to Outstatic.

[Anthony-Jhoiro]

Thank's for your answer, @avitorio !

Yes, I forgot this part in the documentation; I can add it tomorrow.
You are right, and it would be better! I can try that during the week!

[changeset-bot]

⚠️ No Changeset found

Latest commit: dd2fa79

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[avitorio]

Hey @Anthony-Jhoiro,
Sorry for the delay in reviewing this. The structure of the project changed to support Next.js 13's app directory and I've updated your PR with the necessary changes.

I've also updated the docs. I believe this is ready to merge. Thank you for your help!