![]() Optionally, if you want to redirect users to the setup URL after they update an installation, select Redirect on update. Users will instead be redirected to the Callback URL as part of the authorization flow, where you can describe additional setup. If you selected Request user authorization (OAuth) during installation in an earlier step, you will not be able to enter a URL here. For more information, see " About the setup URL." If additional setup is required after installation, you can use this URL to tell users what steps to take after installation. ![]() Optionally, under "Setup URL", enter the URL to redirect users to after they install your app. For more information, see " Generating a user access token for a GitHub App." Optionally, if you want to use device flow to generate a user access token, select Enable Device Flow. ![]() For more information, see " Authenticating with a GitHub App on behalf of a user" and " Generating a user access token for a GitHub App." If a user authorizes your app, your app can generate a user access token to make API requests on the user's behalf and attribute app activity to the user. Optionally, to prompt users to authorize your app when they install it, select Request user authorization (OAuth) during installation. For more information about refreshing expired tokens and the benefits of user access tokens that expire, see " Refreshing user access tokens." If your app does not need to generate a user access token, this field will be ignored. GitHub strongly recommends that you leave this option selected. Optionally, to prevent user access tokens from expiring, deselect Expire user authorization tokens. If your app uses device flow instead of web application flow to generate a user access token, this field will be ignored.įor more information about the callback URL, see " About the user authorization callback URL." For more information about generating a user access token to act on behalf of a user, see " Authenticating with a GitHub App on behalf of a user" and " Generating a user access token for a GitHub App." If your app does not need to act on behalf of a user (does not need to generate a user access token), this field will be ignored. To add additional callback URLs, click Add callback URL. Optionally, under "Callback URL", enter the full URL to redirect to after a user authorizes the installation. Or, you can use the URL of the organization or user that owns the app. If you don’t have a dedicated URL and your app's code is stored in a public repository, you can use that repository URL. Under "Homepage URL", type the full URL to your app's website. Users and organizations will see this description when they install your app. Optionally, under "Description", type a description of your app. You cannot use same name as an existing GitHub account, unless it is your own user or organization name. For example, My APp Näme would display as my-app-name. Your app's name (converted to lowercase, with spaces replaced by -, and with special characters replaced) will be shown in the user interface when your app takes an action. You should choose a clear and short name. Under "GitHub App name", enter a name for your app. In the left sidebar, click Developer settings. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |