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

워크플로의 필수 검토 정보

작업이 승인을 기다리는 동안 “대기 중” 상태가 됩니다.

환경, 환경 비밀, 환경 보호 규칙은 모든 제품의 퍼블릭 리포지토리에서 사용할 수 있습니다. 프라이빗 또는 내부 리포지토리의 환경, 환경 비밀 및 배포 분기에 액세스하려면 GitHub Pro, GitHub Team, GitHub Enterprise를 사용해야 합니다. 프라이빗 또는 내부 리포지토리의 기타 환경 보호 규칙에 액세스하려면 GitHub Enterprise를 사용해야 합니다. 자세한 내용은 "AUTOTITLE"을 참조하세요.

About required reviews in workflows

Jobs that reference an environment configured with required reviewers will wait for an approval before starting. While a job is awaiting approval, it has a status of "Waiting". If a job is not approved within 30 days, it will automatically fail.

For more information about environments and required approvals, see "Using environments for deployment." For information about how to review deployments with the REST API, see "Actions."

Approving or rejecting a job

  1. Navigate to the workflow run that requires review. For more information about navigating to a workflow run, see "Viewing workflow run history."
  2. If the run requires review, you will see a notification for the review request. On the notification, click Review deployments.
  3. Select the job environment(s) to approve or reject. Optionally, leave a comment.
  4. Approve or reject:
    • To approve the job, click Approve and deploy. Once a job is approved (and any other environment protection rules have passed), the job will proceed. At this point, the job can access any secrets stored in the environment.
    • To reject the job, click Reject. If a job is rejected, the workflow will fail.

Bypassing environment protection rules

If you have configured environment protection rules that control whether software can be deployed to an environment, you can bypass these rules and force all pending jobs referencing the environment to proceed.


  • You cannot bypass environment protection rules if the environment has been configured to prevent admins from bypassing configured protection rules. For more information, see "Using environments for deployment."
  • You can only bypass environment protection rules during workflow execution when a job referencing the environment is in a "Pending" state.
  1. Navigate to the workflow run. For more information about navigating to a workflow run, see "Viewing workflow run history."
  2. To the right of Deployment protection rules, click Start all waiting jobs. Screenshot of the "Deployment protection rules" section with the "Start all waiting jobs" button outlined in orange
  3. In the pop-up window, select the environments for which you want to bypass environment protection rules.
  4. Under Leave a comment, enter a description for bypassing the environment protection rules.
  5. Click I understand the consequences, start deploying.