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.

Wer kann dieses Feature verwenden?

Organisationsbesitzerinnen, Sicherheitsmanagerinnen und Organisationsmitglieder mit der Administratorrolle

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. Wählen Sie in der oberen rechten Ecke von GitHub Ihr Profilfoto aus, und klicken Sie dann auf Ihre Organisationen.

  2. Klicke unter deinem Organisationsnamen auf die Option Einstellungen. Wenn die Registerkarte „Einstellungen“ nicht angezeigt wird, wähle im Dropdownmenü die Option Einstellungen aus.

    Screenshot der Registerkarten im Profil einer Organisation. Die Registerkarte „Einstellungen“ ist dunkelorange umrandet.

  3. Wählen Sie im Abschnitt „Sicherheit“ der Randleiste das Dropdownmenü Codesicherheit aus, und klicken Sie dann auf Konfigurationen.

  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