Skip to main content
Frecuentemente publicamos actualizaciones de nuestra documentación. Es posible que la traducción de esta página esté en curso. Para conocer la información más actual, visita la documentación en inglés. Si existe un problema con las traducciones en esta página, por favor infórmanos.
GitHub AE está actualmente en un lanzamiento limitado. Por favor, contacta a nuestro equipo de ventas para conocer más sobre esto.

Enabling automatic access to GitHub.com actions using GitHub Connect

To allow GitHub Actions in your enterprise to use actions from GitHub.com, you can connect your enterprise instance to Nube de GitHub Enterprise.

Enterprise owners can enable access to all GitHub.com actions.

About automatic access to GitHub.com actions

By default, GitHub Actions workflows on GitHub AE cannot use actions directly from GitHub.com or GitHub Marketplace. To make all actions from GitHub.com available on your enterprise instance, you can use GitHub Connect to integrate GitHub AE with Nube de GitHub Enterprise.

To use actions from GitHub.com, your self-hosted runners must be able to make outbound connections to GitHub.com. No inbound connections from GitHub.com are required. Para obtener más información Para obtener más información, consulta la sección "Acerca de los ejecutores auto-hospedados".

Alternatively, if you want stricter control over which actions are allowed in your enterprise, you can manually download and sync actions onto your enterprise instance using the actions-sync tool. For more information, see "Manually syncing actions from GitHub.com."

About resolution for actions using GitHub Connect

When a workflow uses an action by referencing the repository where the action is stored, GitHub Actions will first try to find the repository on tu empresa. If the repository does not exist on tu empresa, and if you have automatic access to GitHub.com enabled, GitHub Actions will try to find the repository on GitHub.com.

If a user has already created an organization and repository in your enterprise that matches an organization and repository name on GitHub.com, the repository on your enterprise will be used instead of the GitHub.com repository. A malicious user could take advantage of this behavior to run code as part of a workflow

Enabling automatic access to all GitHub.com actions

Before enabling access to all actions from GitHub.com for your enterprise, you must enable GitHub Connect. For more information, see "Managing GitHub Connect."

  1. En la esquina superior derecha de GitHub AE, da clic en tu foto de perfil y luego en Configuración de empresa. "Configuración de empresa" en el menú desplegable de la foto de perfil en GitHub AE

  2. En la barra lateral de la cuenta empresarial, haz clic en GitHub Connect. La pestaña de GitHub Connect en la barra lateral de la cuenta empresarial

  3. Under "Users can utilize actions from GitHub.com in workflow runs", use the drop-down menu and select Enabled. Drop-down menu to actions from GitHub.com in workflows runs

  4. Después de que habilitas GitHub Connect, puedes utilizar políticas para restringir qué acciones públicas se pueden utilizar en los repositorios de tu empresa. Para obtener más información, consulta la sección "Requerir las políticas de GitHub Actions para tu empresa".

Automatic retirement of namespaces for actions accessed on GitHub.com

When you enable GitHub Connect, users see no change in behavior for existing workflows because GitHub Actions searches tu empresa for each action before falling back to GitHub.com. This ensures that any custom versions of actions your enterprise has created are used in preference to their counterparts on GitHub.com.

Automatic retirement of namespaces for actions accessed on GitHub.com blocks the potential for a man-in-the-middle attack by a malicious user with access to tu empresa. When an action on GitHub.com is used for the first time, that namespace is retired in tu empresa. This blocks any user creating an organization and repository in your enterprise that matches that organization and repository name on GitHub.com. This ensures that when a workflow runs, the intended action is always run.

After using an action from GitHub.com, if you want to create an action in tu empresa with the same name, first you need to make the namespace for that organization and repository available.

  1. Desde una cuenta administrativa de GitHub AE, en la esquina superior derecha de cualquier página, haz clic en .

    Captura de pantalla del icono de cohete para acceder a los ajustes administrativos

  2. Si aún no estás en la página de "Administrador de sitio", en la esquina inferior izquierda, haz clic en Administrador de sitio.

    Captura de pantalla del enlace de "Administrador de sitio"

  3. In the left sidebar, under Site admin click Retired namespaces.

  4. Locate the namespace that you want use in tu empresa and click Unretire. Unretire namespace

  5. Go to the relevant organization and create a new repository.

    Tip: When you unretire a namespace, always create the new repository with that name as soon as possible. If a workflow calls the associated action on GitHub.com before you create the local repository, the namespace will be retired again. For actions used in workflows that run frequently, you may find that a namespace is retired again before you have time to create the local repository. In this case, you can temporarily disable the relevant workflows until you have created the new repository.