Skip to main content
설명서에 자주 업데이트를 게시하며 이 페이지의 번역이 계속 진행 중일 수 있습니다. 최신 정보는 영어 설명서를 참조하세요.
All products
앱

이 버전의 GitHub Enterprise는 다음 날짜에 중단되었습니다. 2023-03-15. 중요한 보안 문제에 대해서도 패치 릴리스가 이루어지지 않습니다. 성능 향상, 향상된 보안, 새로운 기능을 위해 최신 버전의 GitHub Enterprise로 업그레이드합니다. 업그레이드에 대한 도움말은 GitHub Enterprise 지원에 문의하세요.

Modifying a GitHub App registration

이 문서의 내용

GitHub 앱을 만든 후 변경할 수 있습니다.

About GitHub App modifications

You can modify your GitHub App registration to change any of the settings that were selected when the app was initially registered. For more information about the settings you can select while registering a GitHub App, see "Registering a GitHub App."

For example, you can change the name and description of your app, the permissions granted to your app, the webhooks your app subscribes to, or the visibility of your app.

You can also choose to test new optional features for your GitHub App. For more information, see "GitHub 앱에 대한 선택적 기능 활성화."

To modify a GitHub App, first navigate to the app settings page.

  1. 계정 설정으로 이동합니다.

    • 개인 계정이 소유하는 GitHub App의 경우 페이지 오른쪽 위 모서리에서 프로필 사진을 클릭한 다음, 설정을 클릭합니다.
    • 조직이 소유하는 GitHub App의 경우 페이지 오른쪽 위 모서리에서 프로필 사진을 클릭한 다음, 조직을 클릭합니다. 그런 다음, 조직 오른쪽에서 설정을 클릭합니다.

  2. 왼쪽 사이드바에서 개발자 설정을 클릭합니다.

  3. 왼쪽 사이드바에서 GitHub Apps를 클릭합니다. GitHub의 "개발자 설정" 페이지 스크린샷 "GitHub Apps"라는 레이블이 지정된 옵션은 진한 주황색으로 표시됩니다.

  4. 수정하려는 GitHub App의 오른쪽에서 Edit(편집)을 클릭합니다.

Changing the basic information of a GitHub App

You can change the basic information of your GitHub App, like the name of the app, the description of the app, and the homepage URL of the app.

  1. Navigate to the settings page for the app you'd like to modify. For more information, see "Navigating to your GitHub App settings" in this article.
  2. Under "Basic information," modify the GitHub App information that you'd like to change.
  3. Click Save changes.

Requesting user authorization (OAuth) during installation

You can prompt users to authorize your GitHub App when they install it and generate a user access token. When you request user authorization (OAuth) during installation, you must also provide a callback URL where the user will be redirected after they authorize the installation. For more information, see "GitHub 앱 대한 사용자 액세스 토큰 생성."

  1. Navigate to the settings page for the app you'd like to modify. For more information, see "Navigating to your GitHub App settings" in this article.
  2. Under "Identifying and authorizing users," select or deselect Request user authorization (OAuth) during installation.
  3. Under "Callback URL," enter the full URL to redirect to after a user authorizes the installation.

Enabling or disabling the device flow

You can use the device flow to authorize users for a headless app like a CLI tool or Git credential manager. For more information about using the device flow with GitHub Apps, see "GitHub 앱 대한 사용자 액세스 토큰 생성."

  1. Navigate to the settings page for the app you'd like to modify. For more information, see "Navigating to your GitHub App settings" in this article.
  2. Under "Identifying and authorizing users," select or deselect Enable Device Flow.

Adding or updating a setup URL

You can redirect people to a specific URL after they install your app. For more information, see "Registering a GitHub App."

If you select Request user authorization (OAuth) during installation, you will not be able to enter a setup URL. Users will instead be redirected to the Callback URL as part of the authorization flow, where you can describe additional setup. For more information, see "About the user authorization callback URL."

  1. Navigate to the settings page for the app you'd like to modify. For more information, see "Navigating to your GitHub App settings" in this article.
  2. Under "Post installation," in the "Setup URL" field, enter the URL where you'd like to redirect users after they install your app.
  3. Optionally, if you want to redirect users to the setup URL after they update an installation, select Redirect on update. An update includes adding or removing a repository for an installation. If "Setup URL" is blank, this will be ignored.

Changing the permissions of a GitHub App

You can change the access permissions that are granted to your GitHub App using the following steps.

When you change the repository or organization permissions of an app, each account where the app is installed will need to approve the new permissions. When you change the account permissions of an app, each user that has authorized the app will need to approve the permission changes. Updated permissions won't take effect on an installation or user authorization until the new permissions are approved. You can use the installation webhook to find out when people accept new permissions for your app.

Changing the permissions of an app may also change the webhooks that your app can subscribe to and the actions that your app can take with the API. For more information, see "Choosing permissions for a GitHub App."

  1. Navigate to the settings page for the app you'd like to modify. For more information, see "Navigating to your GitHub App settings" in this article.
  2. In the GitHub Apps settings sidebar, click Permissions & events.
  3. Under the sections "Repository permissions," "Organization permissions," and "Account permissions," modify the permissions you'd like to change. For each type of permission, select either "Read-only," "Read and write," or "No access" from the dropdown. For more information, see "Choosing permissions for a GitHub App."
  4. Optionally, under "Add a note to users," add a note telling your users why you are changing the permissions that your GitHub App requests.
  5. Click Save changes.

Activating or deactivating the GitHub App webhook

You can configure your GitHub App to receive webhooks for specific events on GitHub and automatically take action on them. For more information, see "Using webhooks with GitHub Apps."

  1. Navigate to the settings page for the app you'd like to modify. For more information, see "Navigating to your GitHub App settings" in this article.
  2. Under "Webhook," to enable or disable the webhook, select or deselect Active.
  3. If you selected Active in the previous step, under "Webhook URL," enter the URL that GitHub should send webhook events to.
  4. Optionally, if you selected Active in the previous step, under "Webhook secret," enter a secret token to secure your webhooks. GitHub highly recommends that you set a webhook secret.

Changing the webhook event subscriptions of a GitHub App

You can change the webhook events that a GitHub App subscribes to using the following steps.

앱 설정에서 선택할 수 있는 특정 웹후크 이벤트는 앱에 대해 선택한 사용 권한 유형에 따라 결정됩니다. 먼저 앱에 부여할 권한을 선택한 다음, 해당 권한 집합과 관련된 웹후크 이벤트에 앱을 구독할 수 있습니다. For more information, see "Using webhooks with GitHub Apps."

  1. Navigate to the settings page for the app you'd like to modify. For more information, see "Navigating to your GitHub App settings" in this article.
  2. Activate the GitHub App webhook. For more information, see "Activating or deactivating the GitHub App webhook" in this article.
  3. In the GitHub Apps settings sidebar, click Permissions & events.
  4. Under the sections "Repository permissions," "Organization permissions," and "Account permissions," select the permissions that are required for the events your app will subscribe to. For more information, see "Changing the permissions of a GitHub App."
  5. Under "Subscribe to Events," select the webhook events you would like your GitHub App to receive.
  6. Click Save changes.

Changing the visibility of a GitHub App

You can change the visibility settings of your GitHub App to control who can install it. Public apps cannot be made private if they're installed on other accounts. For more information, see "Making a GitHub App public or private."

  1. Navigate to the settings page for the app you'd like to modify. For more information, see "Navigating to your GitHub App settings" in this article.
  2. 왼쪽 사이드바에서 고급을 클릭합니다.
  3. Under "Danger zone," depending on the current visibility of your GitHub App, click either Make public or Make private.