As it states on the OAuth website:
OAuth is a simple way to publish and interact with protected data.
One way to use GitHub OAuth in a non-GitHub website or application is as an identity mechanism. You give your application's users the ability to use GitHub to authenticate who they are. This saves you from having to deal with passwords and all the mess that goes along with them. It also gives you an avatar for them as well, so you don't have to store and police potentially abusive avatar images. If you've seen a "Sign in with GitHub" button on a website such as https://travis-ci.org or https://exercism.io, then that's what they're using GitHub OAuth for. Additionally, we have information on how to do this in our developer documentation.
But how to use OAuth depends on what your website or application does. Does your website or application need to see its user's GitHub data? Then GitHub OAuth might be the right solution. Does your website or application need to calculate spaceship transfer orbits between Venus and Mars? Then GitHub OAuth is less likely to be the right solution.
I hope that helps!
... View more
I'm confused. There's a step-by-step guide to building GitHub Apps in our documentation. And even a guide to using Smee to create a development environment for GitHub Apps. And the REST guide has some helpful information on learning about the GitHub API. So I'm not sure what it is you're looking for when you say you want a "tutorial"? Can you be a bit more specific as to what it is you need?
... View more