Enterprise Server 3.15 est actuellement disponible en tant que version finale (RC).

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.

Qui peut utiliser cette fonctionnalité ?

PropriĂ©taires de l’organisation, gestionnaires de sĂ©curitĂ© et membres de l’organisation avec le rĂŽle d’administrateur

Dans cet article

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. Dans le coin supérieur droit de GitHub, sélectionnez votre photo de profil, puis cliquez sur Vos organisations.

  2. Sous le nom de votre organisation, cliquez sur ParamĂštres. Si vous ne voyez pas l’onglet « ParamĂštres », sĂ©lectionnez le menu dĂ©roulant , puis cliquez sur ParamĂštres.

    Capture d’écran des onglets dans le profil d’une organisation. L’onglet « ParamĂštres » est prĂ©sentĂ© en orange foncĂ©.

  3. Dans la section Sécurité de la barre latérale, sélectionnez le menu déroulant Sécurité du code, puis cliquez sur Configurations.

  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