Skip to main content

Finding and fixing configuration attachment failures

You can identify any repositories where the security configuration could not be attached, and follow guidance to remediate the problem.

누가 이 기능을 사용할 수 있나요?

관리자 역할이 있는 조직 소유자, 보안 관리자 및 조직 구성원

Finding and remediating attachment failures

When you apply a configuration to a group of repositories, you may see a banner reporting that there was an attachment failure for some repositories. This happens when there is a conflict between the existing repository settings and the configuration that you applied.

When an attachment failure happens:

  • Only some of the settings in the security configuration are applied to affected repositories.
  • Any changes you later make to the security configuration will not be inherited by the affected repositories.

On the security configuration settings page, under "Apply configurations", you will see a banner advising how many repositories in your organization have an attachment failure, and an overview of the reason(s) for the failure.

Click the link in the banner display, or alternatively, filter the list of repositories by config-status:failed, to see the list of affected repositories and to source additional guidance on how to remediate the attachment failure for a specific repository.

  1. GitHub의 오른쪽 위 모서리에서 프로필 사진을 선택하고 조직을 클릭합니다.

  2. 조직 이름에서 설정을 클릭합니다. "설정" 탭이 표시되지 않으면 드롭다운 메뉴를 선택한 다음 설정을 클릭합니다.

    조직 프로필에 있는 여러 탭의 스크린샷. "설정" 탭이 진한 주황색으로 표시됩니다.

  3. 사이드바의 "보안" 섹션에서 코드 보안 드롭다운 메뉴를 선택한 다음 성을 클릭합니다.

  4. In the "Apply configurations" section, filter by config-status:failed.

  5. From the results list, for the repository you're interested in, click Failed REASON.

  6. In the dialog box, review the information and follow the remediation guidance.

Further reading