Nota: Los ejecutores hospedados en GitHub no son compatibles con GitHub Enterprise Server actualmente. Puedes encontrar más información sobre el soporte que se tiene planeado en el futuro en el Itinerario público de GitHub.
About automatic access to GitHub.com actions
By default, GitHub Actions workflows on GitHub Enterprise Server 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 Enterprise Server with Nube de GitHub Enterprise. For other ways of accessing actions from GitHub.com, see "About using actions in your enterprise."
To use actions from GitHub.com, your self-hosted runners must be able to download public actions from api.github.com.
Enabling automatic access to all GitHub.com actions
Nota: Con GitHub Connect habilitado, las GitHub Actions intentarán encontrar el repositorio en tu instancia de GitHub Enterprise Server antes de revertirse a GitHub.com. Si un usuario ya creó una organización y repositorio en tu empresa, el cual empate con un nombre de organización y repositorio en GitHub, el repositorio de tu empresa se utilizará en vez del de GitHub. Para obtener más información, consulta la sección "Jubilación automática de designadores de espacio para las acciones a las cuales se accede en GitHub.com".
Before enabling access to all actions from GitHub.com on your enterprise instance, you must connect your enterprise to GitHub.com. For more information, see "Connecting your enterprise to Nube de GitHub Enterprise."
-
En la esquina superior derecha de GitHub Enterprise Server, da clic en tu foto de perfil y luego en Configuración de empresa.
-
En la barra lateral de la cuenta empresarial, haz clic en GitHub Connect.
-
Under "Users can utilize actions from GitHub.com in workflow runs", use the drop-down menu and select Enabled.
-
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 instancia de GitHub Enterprise Server 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 instancia de GitHub Enterprise Server. When an action on GitHub.com is used for the first time, that namespace is retired in tu instancia de GitHub Enterprise Server. 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 instancia de GitHub Enterprise Server with the same name, first you need to make the namespace for that organization and repository available.
-
Desde una cuenta administrativa de GitHub Enterprise Server, en la esquina superior derecha de cualquier página, haz clic en .
-
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.
-
In the left sidebar, under Site admin click Retired namespaces.
-
Locate the namespace that you want use in tu instancia de GitHub Enterprise Server and click Unretire.
-
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.