
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.

Then, to the right of the organization, click Settings. For a GitHub App owned by an organization, in the upper-right corner of any page, click your profile photo, then click Your organizations.


