Skip to main content
Publicamos actualizaciones para la documentación con frecuencia y es posible que aún se esté traduciendo esta página. Para obtener la información más reciente, visite la documentación en inglés.
� 

� 

Esta versión de GitHub Enterprise se discontinuó el 2022-10-12. No se realizarán lanzamientos de patch, ni siquiera para problemas de seguridad críticos. Para obtener rendimiento mejorado, seguridad mejorada y nuevas características, actualice a la versión más reciente de GitHub Enterprise. Para obtener ayuda con la actualización, póngase en contacto con el soporte técnico de GitHub Enterprise.

Managing security and analysis settings for your repository

En este artículo

You can control features that secure and analyze the code in your project on GitHub.

Who can use this feature

People with admin permissions to a repository can manage security and analysis settings for the repository.

Enabling or disabling security and analysis features

You can manage the security and analysis features for your repository. If your organization belongs to an enterprise with a license for GitHub Advanced Security then extra options are available. Para más información, consulte "Acerca de GitHub Advanced Security".

  1. En your GitHub Enterprise Server instance, vaya a la página principal del repositorio.

  2. Debajo del nombre del repositorio, haz clic en Configuración. Botón de configuración del repositorio

  3. In the left sidebar, click Security & analysis. "Security & analysis" tab in repository settings

  4. Under "Code security and analysis", to the right of the feature, click Disable or Enable. The control for "GitHub Advanced Security" is disabled if your enterprise has no available licenses for Advanced Security. Screenshot of "Enable" or "Disable" button for "Configure security and analysis" features

    Note: If you disable GitHub Advanced Security, secret scanning and code scanning are disabled. Any workflows, SARIF uploads, or API calls for code scanning will fail.

Granting access to security alerts

Security alerts for a repository are visible to people with admin access to the repository and, when the repository is owned by an organization, organization owners. You can give additional teams and people access to the alerts.

Organization owners and repository administrators can only grant access to view security alerts, such as secret scanning alerts, to people or teams who have write access to the repo.

  1. En your GitHub Enterprise Server instance, vaya a la página principal del repositorio.

  2. Debajo del nombre del repositorio, haz clic en Configuración. Botón de configuración del repositorio

  3. In the left sidebar, click Security & analysis. "Security & analysis" tab in repository settings

  4. Under "Access to alerts", in the search field, start typing the name of the person or team you'd like to find, then click a name in the list of matches.

    Search field for granting people or teams access to security alerts

  5. Click Save changes.

    "Save changes" button for changes to security alert settings

Removing access to security alerts

  1. En your GitHub Enterprise Server instance, vaya a la página principal del repositorio.

  2. Debajo del nombre del repositorio, haz clic en Configuración. Botón de configuración del repositorio

  3. In the left sidebar, click Security & analysis. "Security & analysis" tab in repository settings

  4. Under "Access to alerts", to the right of the person or team whose access you'd like to remove, click .

    "x" button to remove someone's access to security alerts for your repository

  5. Click Save changes.

Further reading