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.
-
In the upper-right corner of GitHub, select your profile photo, then click Your organizations**.
-
Under your organization name, click Settings. If you cannot see the "Settings" tab, select the dropdown menu, then click Settings.
-
In the "Security" section of the sidebar, select the Code security dropdown menu, then click Configurations.
-
In the "Apply configurations" section, filter by
config-status:failed. -
From the results list, for the repository you're interested in, click Failed REASON.
-
In the dialog box, review the information and follow the remediation guidance.
