\n \n \n clientId\n | \n \n Required. The client ID you received from GitHub when you registered.\n | \n
\n \n \n clientType\n | \n \n\nMust be set to either `\"oauth-app\"` or `\"github-app\"`. Defaults to `\"oauth-app\"`.\n\n | \n
\n \n \n redirectUrl\n | \n \n The URL in your application where users will be sent after authorization. See Redirect URLs in GitHub’s Developer Guide.\n | \n
\n \n \n login\n | \n \n Suggests a specific account to use for signing in and authorizing the app.\n | \n
\n \n \n scopes\n | \n \n\nOnly relevant when `clientType` is set to `\"oauth-app\"`.\n\nAn array of scope names (or: space-delimited list of scopes). If not provided, scope defaults to an empty list for users that have not authorized any scopes for the application. For users who have authorized scopes for the application, the user won't be shown the OAuth authorization page with the list of scopes. Instead, this step of the flow will automatically complete with the set of scopes the user has authorized for the application. For example, if a user has already performed the web flow twice and has authorized one token with user scope and another token with repo scope, a third web flow that does not provide a scope will receive a token with user and repo scope.\n\nDefaults to `[]` if `clientType` is set to `\"oauth-app\"`.\n\n | \n
\n \n \n state\n | \n \n An unguessable random string. It is used to protect against cross-site request forgery attacks.\n Defaults to Math.random().toString(36).substr(2).\n | \n
\n \n \n allowSignup\n | \n \n Whether or not unauthenticated users will be offered an option to sign up for GitHub during the OAuth flow. Use false in the case that a policy prohibits signups. Defaults to true.\n | \n
\n \n \n baseUrl\n | \n \n When using GitHub Enterprise Server, set the baseUrl to the origin, e.g. https://github.my-enterprise.com.\n | \n
\n \n