Octomerger Bot
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Niveles de permisos para un repositorio de una cuenta personal
|
||||
intro: 'Un repositorio que pertenece a una cuenta personal tiene dos niveles de permiso: propietario del repositorio y colaboradores.'
|
||||
title: Permission levels for a personal account repository
|
||||
intro: 'A repository owned by a personal account has two permission levels: the repository owner and collaborators.'
|
||||
redirect_from:
|
||||
- /articles/permission-levels-for-a-user-account-repository
|
||||
- /github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository
|
||||
@@ -14,84 +14,79 @@ versions:
|
||||
topics:
|
||||
- Accounts
|
||||
shortTitle: Repository permissions
|
||||
ms.openlocfilehash: e7c7a542204c7b1ce69bc19ac326fb248bbbff12
|
||||
ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: es-ES
|
||||
ms.lasthandoff: 09/05/2022
|
||||
ms.locfileid: '147066310'
|
||||
---
|
||||
## Acerca de los niveles de permisos para un repositorio de una cuenta personal
|
||||
## About permissions levels for a personal account repository
|
||||
|
||||
Los repositorios propiedad de las cuentas personales tienen un propietario. Los permisos de propiedad no se pueden compartir con otra cuenta personal.
|
||||
Repositories owned by personal accounts have one owner. Ownership permissions can't be shared with another personal account.
|
||||
|
||||
También puede {% ifversion fpt or ghec %}invitar{% else %}agregar{% endif %} usuarios de {% data variables.product.product_name %} al repositorio como colaboradores. Para más información, vea "[Invitación de colaboradores a un repositorio personal](/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository)".
|
||||
You can also {% ifversion fpt or ghec %}invite{% else %}add{% endif %} users on {% data variables.product.product_name %} to your repository as collaborators. For more information, see "[Inviting collaborators to a personal repository](/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository)."
|
||||
|
||||
{% tip %}
|
||||
|
||||
**Sugerencia:** si necesitas un acceso más pormenorizado a un repositorio propiedad de tu cuenta personal, considera la posibilidad de transferir el repositorio a una organización. Para más información, vea "[Transferencia de un repositorio](/github/administering-a-repository/transferring-a-repository#transferring-a-repository-owned-by-your-personal-account)".
|
||||
**Tip:** If you require more granular access to a repository owned by your personal account, consider transferring the repository to an organization. For more information, see "[Transferring a repository](/github/administering-a-repository/transferring-a-repository#transferring-a-repository-owned-by-your-personal-account)."
|
||||
|
||||
{% endtip %}
|
||||
|
||||
## Acceso de propietarios a un repositorio propiedad de una cuenta personal
|
||||
## Owner access for a repository owned by a personal account
|
||||
|
||||
El propietario del repositorio tiene control completo del repositorio. Adicionalmente a las acciones que pudiera realizar cualquier colaborador, el propietario del repositorio puede realizar las siguientes.
|
||||
The repository owner has full control of the repository. In addition to the actions that any collaborator can perform, the repository owner can perform the following actions.
|
||||
|
||||
| Acción | Más información |
|
||||
| Action | More information |
|
||||
| :- | :- |
|
||||
| {% ifversion fpt or ghec %}Invitación a colaboradores{% else %}Adición de colaboradores{% endif %} | "[Invitación a colaboradores a un repositorio personal](/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository)" |
|
||||
| Cambiar la visibilidad del repositorio | "[Configuración de la visibilidad de un repositorio](/github/administering-a-repository/setting-repository-visibility)" |{% ifversion fpt or ghec %}
|
||||
| Limitar las interacciones con el repositorio | "[Limitación de las interacciones en el repositorio](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository)" |{% endif %}
|
||||
| Renombrar una rama, incluyendo la rama predeterminada | "[Cambio del nombre de una rama](/github/administering-a-repository/renaming-a-branch)" |
|
||||
| Fusionar una solicitud de extracción sobre una rama protegida, incluso si no hay revisiones de aprobación | "[Acerca de las ramas protegidas](/github/administering-a-repository/about-protected-branches)" |
|
||||
| Eliminar el repositorio | "[Eliminación de un repositorio](/repositories/creating-and-managing-repositories/deleting-a-repository)" |
|
||||
| Administrar los temas del repositorio | "[Clasificación del repositorio con temas](/github/administering-a-repository/classifying-your-repository-with-topics)" |{% ifversion fpt or ghec %}
|
||||
| Administrar la seguridad y la configuración de análisis del repositorio | "[Administración de la configuración de seguridad y análisis para el repositorio](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)" |{% endif %}{% ifversion fpt or ghec %}
|
||||
| Habilitar la gráfica de dependencias para un repositorio privado | "[Exploración de las dependencias de un repositorio](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository#enabling-and-disabling-the-dependency-graph-for-a-private-repository)" |{% endif %}
|
||||
| Borrar y restaurar paquetes | "[Eliminación y restauración de un paquete](/packages/learn-github-packages/deleting-and-restoring-a-package)" |
|
||||
| Personalizar la vista previa de las redes sociales de un repositorio | "[Personalización de la vista previa de las redes sociales del repositorio ](/github/administering-a-repository/customizing-your-repositorys-social-media-preview)" |
|
||||
| Crear una plantilla del repositorio | "[Creación de un repositorio de plantillas](/github/creating-cloning-and-archiving-repositories/creating-a-template-repository)" |
|
||||
| Controlar el acceso a las {% data variables.product.prodname_dependabot_alerts %}| "[Administración de la configuración de seguridad y análisis para el repositorio](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)" |{% ifversion fpt or ghec %}
|
||||
| Descartar las {% data variables.product.prodname_dependabot_alerts %} en el repositorio | "[Visualización y actualización de {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts)" |
|
||||
| Administrar el uso de datos para un repositorio privado | "[Administración de la configuración de uso de datos para el repositorio privado](/get-started/privacy-on-github/managing-data-use-settings-for-your-private-repository)"|{% endif %}
|
||||
| Definir propietarios del código para un repositorio | "[Acerca de los propietarios de código](/github/creating-cloning-and-archiving-repositories/about-code-owners)" |
|
||||
| Archivar el repositorio | "[Archivado de repositorios](/repositories/archiving-a-github-repository/archiving-repositories)" |{% ifversion fpt or ghec %}
|
||||
| Creación de avisos de seguridad | "[Acerca de {% data variables.product.prodname_security_advisories %}](/github/managing-security-vulnerabilities/about-github-security-advisories)" |
|
||||
| Representación de un botón de patrocinador | "[Representación de un botón de patrocinador en el repositorio](/github/administering-a-repository/displaying-a-sponsor-button-in-your-repository)" |{% endif %}
|
||||
| Permitir o dejar de permitir la fusión automática para las solicitudes de cambios | "[Administración de la combinación automática para las solicitudes de incorporación de cambios en el repositorio](/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository)" |
|
||||
| {% ifversion fpt or ghec %}Invite collaborators{% else %}Add collaborators{% endif %} | "[Inviting collaborators to a personal repository](/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository)" |
|
||||
| Change the visibility of the repository | "[Setting repository visibility](/github/administering-a-repository/setting-repository-visibility)" |{% ifversion fpt or ghec %}
|
||||
| Limit interactions with the repository | "[Limiting interactions in your repository](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository)" |{% endif %}
|
||||
| Rename a branch, including the default branch | "[Renaming a branch](/github/administering-a-repository/renaming-a-branch)" |
|
||||
| Merge a pull request on a protected branch, even if there are no approving reviews | "[About protected branches](/github/administering-a-repository/about-protected-branches)" |
|
||||
| Delete the repository | "[Deleting a repository](/repositories/creating-and-managing-repositories/deleting-a-repository)" |
|
||||
| Manage the repository's topics | "[Classifying your repository with topics](/github/administering-a-repository/classifying-your-repository-with-topics)" |{% ifversion fpt or ghec %}
|
||||
| Manage security and analysis settings for the repository | "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)" |{% endif %}{% ifversion fpt or ghec %}
|
||||
| Enable the dependency graph for a private repository | "[Exploring the dependencies of a repository](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository#enabling-and-disabling-the-dependency-graph-for-a-private-repository)" |{% endif %}
|
||||
| Delete and restore packages | "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)" |
|
||||
| Customize the repository's social media preview | "[Customizing your repository's social media preview](/github/administering-a-repository/customizing-your-repositorys-social-media-preview)" |
|
||||
| Create a template from the repository | "[Creating a template repository](/github/creating-cloning-and-archiving-repositories/creating-a-template-repository)" |
|
||||
| Control access to {% data variables.product.prodname_dependabot_alerts %}| "[Managing security and analysis settings for your repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)" |{% ifversion fpt or ghec %}
|
||||
| Dismiss {% data variables.product.prodname_dependabot_alerts %} in the repository | "[Viewing and updating {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts)" |
|
||||
| Manage data use for a private repository | "[Managing data use settings for your private repository](/get-started/privacy-on-github/managing-data-use-settings-for-your-private-repository)"|{% endif %}
|
||||
| Define code owners for the repository | "[About code owners](/github/creating-cloning-and-archiving-repositories/about-code-owners)" |
|
||||
| Archive the repository | "[Archiving repositories](/repositories/archiving-a-github-repository/archiving-repositories)" |{% ifversion fpt or ghec %}
|
||||
| Create security advisories | "[About repository security advisories](/github/managing-security-vulnerabilities/about-github-security-advisories)" |
|
||||
| Display a sponsor button | "[Displaying a sponsor button in your repository](/github/administering-a-repository/displaying-a-sponsor-button-in-your-repository)" |{% endif %}
|
||||
| Allow or disallow auto-merge for pull requests | "[Managing auto-merge for pull requests in your repository](/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository)" |
|
||||
| Manage webhooks and deploy keys | "[Managing deploy keys](/developers/overview/managing-deploy-keys#deploy-keys)" |
|
||||
|
||||
## Acceso de colaboradores a un repositorio propiedad de una cuenta personal
|
||||
## Collaborator access for a repository owned by a personal account
|
||||
|
||||
Los colaboradores de un repositorio personal pueden extraer (leer) el contienido del mismo y subir (escribir) los cambios al repositorio.
|
||||
Collaborators on a personal repository can pull (read) the contents of the repository and push (write) changes to the repository.
|
||||
|
||||
{% note %}
|
||||
|
||||
**Nota:** En un repositorio privado, los propietarios del repositorio solo pueden conceder acceso de escritura a los colaboradores. Los colaboradores no pueden tener acceso de solo lectura a los repositorios propiedad de una cuenta personal.
|
||||
**Note:** In a private repository, repository owners can only grant write access to collaborators. Collaborators can't have read-only access to repositories owned by a personal account.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
Los colaboradores también pueden realizar las siguientes acciones.
|
||||
Collaborators can also perform the following actions.
|
||||
|
||||
| Acción | Más información |
|
||||
| Action | More information |
|
||||
| :- | :- |
|
||||
| Bifurcar el repositorio | "[Acerca de las bifurcaciones](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks)" |
|
||||
| Renombrar una rama diferente a la predeterminada | "[Cambio del nombre de una rama](/github/administering-a-repository/renaming-a-branch)" |
|
||||
| Crear, editar, y borrar comentarios en las confirmaciones, solicitudes de cambios y propuestas del repositorio | <ul><li>"[Acerca de las incidencias](/github/managing-your-work-on-github/about-issues)"</li><li>"[Comentario de una solicitud de incorporación de cambios](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request)"</li><li>"[Administración de comentarios negativos](/communities/moderating-comments-and-conversations/managing-disruptive-comments)"</li></ul> |
|
||||
| Crear, asignar, cerrar y volver a abrir las propuestas en el repositorio | "[Administración del trabajo con incidencias](/github/managing-your-work-on-github/managing-your-work-with-issues)" |
|
||||
| Administrar las etiquetas para las propuestas y solicitudes de cambios en el repositorio | "[Etiquetado de incidencias y solicitudes de incorporación de cambios](/github/managing-your-work-on-github/labeling-issues-and-pull-requests)" |
|
||||
| Administrar hitos para las propuestas y solicitudes de cambios en el repositorio | "[Creación y edición de hitos para incidencias y solicitudes de incorporación de cambios](/github/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests)" |
|
||||
| Marcar una propuesta o solicitud de cambios en el repositorio como duplicada | "[Acerca de incidencias duplicadas y solicitudes de incorporación de cambios](/github/managing-your-work-on-github/about-duplicate-issues-and-pull-requests)" |
|
||||
| Crear, fusionar y cerrar las solicitudes de cambios en el repositorio | "[Propuesta de cambios en el trabajo con solicitudes de incorporación de cambios](/github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests)" |
|
||||
| Habilitar e inhabilitar la fusión automática para una solicitud de cambios | "[Combinación automática de una solicitud de incorporación de cambios](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request)"
|
||||
| Aplicar los cambios sugeridos a las solicitudes de cambios en el repositorio |"[Incorporación de comentarios en la solicitud de incorporación de cambios](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/incorporating-feedback-in-your-pull-request)" |
|
||||
| Crear una solicitud de cambios desde una bifurcación del repositorio | "[Creación de una solicitud de incorporación de cambios desde una bifurcación](/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork)" |
|
||||
| Emitir una revisión de una solicitud de cambios que afecte la capacidad de fusión de una solicitud de cambios | "[Revisión de los cambios propuestos en una solicitud de incorporación de cambios](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request)" |
|
||||
| Crear y editar un wiki para el repositorio | "[Acerca de las wikis](/communities/documenting-your-project-with-wikis/about-wikis)" |
|
||||
| Crear y editar los lanzamientos del repositorio | "[Administración de versiones en un repositorio](/github/administering-a-repository/managing-releases-in-a-repository)" |
|
||||
| Actuar como propietario del código del repositorio | "[Acerca de los propietarios de código](/articles/about-code-owners)" |{% ifversion fpt or ghae or ghec %}
|
||||
| Publicar, ver o instalar paquetes | "[Publicación y administración de paquetes](/github/managing-packages-with-github-packages/publishing-and-managing-packages)" |{% endif %}
|
||||
| Eliminarse como colaboradores del repositorio | "[Eliminarse del repositorio de un colaborador](/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-a-collaborators-repository)" |
|
||||
| Fork the repository | "[About forks](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks)" |
|
||||
| Rename a branch other than the default branch | "[Renaming a branch](/github/administering-a-repository/renaming-a-branch)" |
|
||||
| Create, edit, and delete comments on commits, pull requests, and issues in the repository | <ul><li>"[About issues](/github/managing-your-work-on-github/about-issues)"</li><li>"[Commenting on a pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request)"</li><li>"[Managing disruptive comments](/communities/moderating-comments-and-conversations/managing-disruptive-comments)"</li></ul> |
|
||||
| Create, assign, close, and re-open issues in the repository | "[Managing your work with issues](/github/managing-your-work-on-github/managing-your-work-with-issues)" |
|
||||
| Manage labels for issues and pull requests in the repository | "[Labeling issues and pull requests](/github/managing-your-work-on-github/labeling-issues-and-pull-requests)" |
|
||||
| Manage milestones for issues and pull requests in the repository | "[Creating and editing milestones for issues and pull requests](/github/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests)" |
|
||||
| Mark an issue or pull request in the repository as a duplicate | "[About duplicate issues and pull requests](/github/managing-your-work-on-github/about-duplicate-issues-and-pull-requests)" |
|
||||
| Create, merge, and close pull requests in the repository | "[Proposing changes to your work with pull requests](/github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests)" |
|
||||
| Enable and disable auto-merge for a pull request | "[Automatically merging a pull request](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request)"
|
||||
| Apply suggested changes to pull requests in the repository |"[Incorporating feedback in your pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/incorporating-feedback-in-your-pull-request)" |
|
||||
| Create a pull request from a fork of the repository | "[Creating a pull request from a fork](/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork)" |
|
||||
| Submit a review on a pull request that affects the mergeability of the pull request | "[Reviewing proposed changes in a pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request)" |
|
||||
| Create and edit a wiki for the repository | "[About wikis](/communities/documenting-your-project-with-wikis/about-wikis)" |
|
||||
| Create and edit releases for the repository | "[Managing releases in a repository](/github/administering-a-repository/managing-releases-in-a-repository)" |
|
||||
| Act as a code owner for the repository | "[About code owners](/articles/about-code-owners)" |{% ifversion fpt or ghae or ghec %}
|
||||
| Publish, view, or install packages | "[Publishing and managing packages](/github/managing-packages-with-github-packages/publishing-and-managing-packages)" |{% endif %}
|
||||
| Remove themselves as collaborators on the repository | "[Removing yourself from a collaborator's repository](/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-a-collaborators-repository)" |
|
||||
|
||||
## Información adicional
|
||||
## Further reading
|
||||
|
||||
- "[Roles de repositorio para una organización](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)"
|
||||
- "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)"
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Using the GitHub CLI on a runner
|
||||
title: Uso de la CLI de GitHub en un ejecutor
|
||||
shortTitle: Use the GitHub CLI on a runner
|
||||
intro: 'How to use advanced {% data variables.product.prodname_actions %} features for continuous integration (CI).'
|
||||
intro: 'Cómo usar características avanzadas de {% data variables.product.prodname_actions %} para la integración continua (CI).'
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '> 3.1'
|
||||
@@ -10,40 +10,34 @@ versions:
|
||||
type: how_to
|
||||
topics:
|
||||
- Workflows
|
||||
ms.openlocfilehash: e0787d09cd194de0038d259c1aff777cc91a4a6a
|
||||
ms.sourcegitcommit: bf11c3e08cbb5eab6320e0de35b32ade6d863c03
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: es-ES
|
||||
ms.lasthandoff: 10/27/2022
|
||||
ms.locfileid: '148111589'
|
||||
---
|
||||
|
||||
{% data reusables.actions.enterprise-github-hosted-runners %}
|
||||
|
||||
## Example overview
|
||||
## Información general de ejemplo
|
||||
|
||||
{% data reusables.actions.example-workflow-intro-ci %} When this workflow is triggered, it automatically runs a script that checks whether the {% data variables.product.prodname_dotcom %} Docs site has any broken links. If any broken links are found, the workflow uses the {% data variables.product.prodname_dotcom %} CLI to create a {% data variables.product.prodname_dotcom %} issue with the details.
|
||||
{% data reusables.actions.example-workflow-intro-ci %} Cuando se desencadena este flujo de trabajo, ejecuta automáticamente un script que comprueba si el sitio de {% data variables.product.prodname_dotcom %} Docs tienen vínculos rotos. Si se encuentran vínculos rotos, el flujo de trabajo usa la CLI de {% data variables.product.prodname_dotcom %} para crear una incidencia de {% data variables.product.prodname_dotcom %} con los detalles.
|
||||
|
||||
{% data reusables.actions.example-diagram-intro %}
|
||||
|
||||
|
||||
|
||||
|
||||
## Features used in this example
|
||||
## Características que se usan en este ejemplo
|
||||
|
||||
{% data reusables.actions.example-table-intro %}
|
||||
|
||||
| **Feature** | **Implementation** |
|
||||
| **Característica** | **Implementación** |
|
||||
| --- | --- |
|
||||
{% data reusables.actions.cron-table-entry %}
|
||||
{% data reusables.actions.permissions-table-entry %}
|
||||
{% data reusables.actions.if-conditions-table-entry %}
|
||||
{% data reusables.actions.secrets-table-entry %}
|
||||
{% data reusables.actions.checkout-action-table-entry %}
|
||||
{% data reusables.actions.setup-node-table-entry %}
|
||||
| Using a third-party action: | [`peter-evans/create-issue-from-file`](https://github.com/peter-evans/create-issue-from-file)|
|
||||
| Running shell commands on the runner: | [`run`](/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idstepsrun) |
|
||||
| Running a script on the runner: | Using `script/check-english-links.js` |
|
||||
| Generating an output file: | Piping the output using the `>` operator |
|
||||
| Checking for existing issues using {% data variables.product.prodname_cli %}: | [`gh issue list`](https://cli.github.com/manual/gh_issue_list) |
|
||||
| Commenting on an issue using {% data variables.product.prodname_cli %}: | [`gh issue comment`](https://cli.github.com/manual/gh_issue_comment) |
|
||||
{% data reusables.actions.cron-table-entry %} {% data reusables.actions.permissions-table-entry %} {% data reusables.actions.if-conditions-table-entry %} {% data reusables.actions.secrets-table-entry %} {% data reusables.actions.checkout-action-table-entry %} {% data reusables.actions.setup-node-table-entry %} | Uso de una acción de terceros: | [`peter-evans/create-issue-from-file`](https://github.com/peter-evans/create-issue-from-file)| | Ejecución de comandos de shell en el ejecutor: | [`run`](/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idstepsrun) | | Ejecución de un script en el ejecutor: | Uso de `script/check-english-links.js` | | Generación de un archivo de salida: | Canalización de la salida mediante el operador `>` | | Comprobación de incidencias existentes mediante la {% data variables.product.prodname_cli %}: | [`gh issue list`](https://cli.github.com/manual/gh_issue_list) | | Realización de comentarios sobre una incidencia mediante la {% data variables.product.prodname_cli %}: | [`gh issue comment`](https://cli.github.com/manual/gh_issue_comment) |
|
||||
|
||||
## Example workflow
|
||||
## Flujo de trabajo de ejemplo
|
||||
|
||||
{% data reusables.actions.example-docs-engineering-intro %} [`check-all-english-links.yml`](https://github.com/github/docs/blob/main/.github/workflows/check-all-english-links.yml).
|
||||
{% data reusables.actions.example-docs-engineering-intro %} [`check-all-english-links.yml`](https://github.com/github/docs/blob/6e01c0653836c10d7e092a17566a2c88b10504ce/.github/workflows/check-all-english-links.yml).
|
||||
|
||||
{% data reusables.actions.note-understanding-example %}
|
||||
|
||||
@@ -178,15 +172,15 @@ jobs:
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
## Understanding the example
|
||||
## Descripción del ejemplo
|
||||
|
||||
{% data reusables.actions.example-explanation-table-intro %}
|
||||
|
||||
<table style="table-layout: fixed;">
|
||||
<thead>
|
||||
<tr>
|
||||
<th style="width:60%"><b>Code</b></th>
|
||||
<th style="width:40%"><b>Explanation</b></th>
|
||||
<th style="width:60%"><b>Código</b></th>
|
||||
<th style="width:40%"><b>Explicación</b></th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
@@ -214,10 +208,10 @@ on:
|
||||
</td>
|
||||
<td>
|
||||
|
||||
Defines the `workflow_dispatch` and `scheduled` as triggers for the workflow:
|
||||
Define `workflow_dispatch` y `scheduled` como desencadenadores para el flujo de trabajo:
|
||||
|
||||
* The `workflow_dispatch` lets you manually run this workflow from the UI. For more information, see [`workflow_dispatch`](/actions/using-workflows/events-that-trigger-workflows#workflow_dispatch).
|
||||
* The `schedule` event lets you use `cron` syntax to define a regular interval for automatically triggering the workflow. For more information, see [`schedule`](/actions/reference/events-that-trigger-workflows#schedule).
|
||||
* `workflow_dispatch` permite ejecutar manualmente este flujo de trabajo desde la interfaz de usuario. Para más información, vea [`workflow_dispatch`](/actions/using-workflows/events-that-trigger-workflows#workflow_dispatch).
|
||||
* El evento `schedule` permite usar la sintaxis `cron` para definir un intervalo regular para desencadenar automáticamente el flujo de trabajo. Para más información, vea [`schedule`](/actions/reference/events-that-trigger-workflows#schedule).
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
@@ -231,7 +225,7 @@ permissions:
|
||||
</td>
|
||||
<td>
|
||||
|
||||
Modifies the default permissions granted to `GITHUB_TOKEN`. This will vary depending on the needs of your workflow. For more information, see "[Assigning permissions to jobs](/actions/using-jobs/assigning-permissions-to-jobs)."
|
||||
Modifica los permisos predeterminados concedidos a `GITHUB_TOKEN`. Esto variará en función de las necesidades del flujo de trabajo. Para obtener más información, consulta "[Asignación de permisos a trabajos](/actions/using-jobs/assigning-permissions-to-jobs)".
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
@@ -243,7 +237,7 @@ jobs:
|
||||
</td>
|
||||
<td>
|
||||
|
||||
Groups together all the jobs that run in the workflow file.
|
||||
Agrupa todos los trabajos que se ejecutan en el archivo de flujo de trabajo.
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
@@ -256,7 +250,7 @@ Groups together all the jobs that run in the workflow file.
|
||||
</td>
|
||||
<td>
|
||||
|
||||
Defines a job with the ID `check_all_english_links`, and the name `Check all links`, that is stored within the `jobs` key.
|
||||
Define un trabajo con el identificador `check_all_english_links` y el nombre `Check all links`, que se almacena en la clave `jobs`.
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
@@ -268,7 +262,7 @@ if: github.repository == 'github/docs-internal'
|
||||
</td>
|
||||
<td>
|
||||
|
||||
Only run the `check_all_english_links` job if the repository is named `docs-internal` and is within the `github` organization. Otherwise, the job is marked as _skipped_.
|
||||
El trabajo `check_all_english_links` solo se ejecuta si el repositorio se denomina `docs-internal` y está dentro de la organización `github`. De lo contrario, el trabajo se marca como _omitido_.
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
@@ -280,7 +274,7 @@ runs-on: ubuntu-latest
|
||||
</td>
|
||||
<td>
|
||||
|
||||
Configures the job to run on an Ubuntu Linux runner. This means that the job will execute on a fresh virtual machine hosted by {% data variables.product.prodname_dotcom %}. For syntax examples using other runners, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idruns-on)."
|
||||
Configura el job para ejecutarse en un ejecutor Ubuntu Linux. Esto significa que el trabajo se ejecutará en una máquina virtual nueva que se hospede en {% data variables.product.prodname_dotcom %}. Para obtener ejemplos de sintaxis con otros ejecutores, consulta «[Sintaxis de flujo de trabajo para {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idruns-on)».
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
@@ -296,7 +290,7 @@ Configures the job to run on an Ubuntu Linux runner. This means that the job wil
|
||||
</td>
|
||||
<td>
|
||||
|
||||
Creates custom environment variables, and redefines the built-in `GITHUB_TOKEN` variable to use a custom [secret](/actions/security-guides/encrypted-secrets). These variables will be referenced later in the workflow.
|
||||
Crea variables de entorno personalizadas y vuelve a definir la variable `GITHUB_TOKEN` integrada para usar un [secreto](/actions/security-guides/encrypted-secrets) personalizado. Se hará referencia a estas variables más adelante en el flujo de trabajo.
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
@@ -308,7 +302,7 @@ Creates custom environment variables, and redefines the built-in `GITHUB_TOKEN`
|
||||
</td>
|
||||
<td>
|
||||
|
||||
Groups together all the steps that will run as part of the `check_all_english_links` job. Each job in the workflow has its own `steps` section.
|
||||
Agrupa todos los pasos que se ejecutarán como parte del trabajo `check_all_english_links`. Cada trabajo del flujo de trabajo tiene su propia sección `steps`.
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
@@ -321,7 +315,7 @@ Groups together all the steps that will run as part of the `check_all_english_li
|
||||
</td>
|
||||
<td>
|
||||
|
||||
The `uses` keyword tells the job to retrieve the action named `actions/checkout`. This is an action that checks out your repository and downloads it to the runner, allowing you to run actions against your code (such as testing tools). You must use the checkout action any time your workflow will run against the repository's code or you are using an action defined in the repository.
|
||||
La palabra clave `uses` le indica al trabajo que recupere la acción denominada `actions/checkout`. Esta es una acción que revisa tu repositorio y lo descarga al ejecutor, lo que te permite ejecutar acciones contra tu código (tales como las herramientas de prueba). Debes utilizar la acción de verificación cada que tu flujo de trabajo se ejecute contra el código del repositorio o cada que estés utilizando una acción definida en el repositorio.
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
@@ -337,7 +331,7 @@ The `uses` keyword tells the job to retrieve the action named `actions/checkout`
|
||||
</td>
|
||||
<td>
|
||||
|
||||
This step uses the `actions/setup-node` action to install the specified version of the `node` software package on the runner, which gives you access to the `npm` command.
|
||||
En este paso, se usa la acción `actions/setup-node` para instalar la versión especificada del paquete de software `node` en el ejecutor, lo que te da acceso al comando `npm`.
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
@@ -352,7 +346,7 @@ This step uses the `actions/setup-node` action to install the specified version
|
||||
</td>
|
||||
<td>
|
||||
|
||||
The `run` keyword tells the job to execute a command on the runner. In this case, the `npm ci` and `npm run build` commands are run as separate steps to install and build the Node.js application in the repository.
|
||||
La palabra clave `run` indica al trabajo que ejecute un comando en el ejecutor. En este caso, los comandos `npm ci` y `npm run build` se ejecutan como pasos independientes para instalar y compilar la aplicación Node.js en el repositorio.
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
@@ -366,7 +360,7 @@ The `run` keyword tells the job to execute a command on the runner. In this case
|
||||
</td>
|
||||
<td>
|
||||
|
||||
This `run` command executes a script that is stored in the repository at `script/check-english-links.js`, and pipes the output to a file called `broken_links.md`.
|
||||
Este comando `run` ejecuta un script que se almacena en el repositorio en `script/check-english-links.js` y canaliza la salida a un archivo denominado `broken_links.md`.
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
@@ -385,7 +379,7 @@ This `run` command executes a script that is stored in the repository at `script
|
||||
</td>
|
||||
<td>
|
||||
|
||||
If the `check-english-links.js` script detects broken links and returns a non-zero (failure) exit status, then use a [workflow command](/actions/using-workflows/workflow-commands-for-github-actions#setting-an-output-parameter) to set an output that has the value of the first line of the `broken_links.md` file (this is used the next step).
|
||||
Si el script `check-english-links.js` detecta vínculos rotos y devuelve un estado de salida distinto de cero (error), usa un [comando de flujo de trabajo](/actions/using-workflows/workflow-commands-for-github-actions#setting-an-output-parameter) para establecer una salida que tenga el valor de la primera línea del archivo `broken_links.md` (se usa el paso siguiente).
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
@@ -407,7 +401,7 @@ If the `check-english-links.js` script detects broken links and returns a non-ze
|
||||
</td>
|
||||
<td>
|
||||
|
||||
Uses the `peter-evans/create-issue-from-file` action to create a new {% data variables.product.prodname_dotcom %} issue. This example is pinned to a specific version of the action, using the `b4f9ee0a9d4abbfc6986601d9b1a4f8f8e74c77e` SHA.
|
||||
Usa la acción `peter-evans/create-issue-from-file` para crear una incidencia de {% data variables.product.prodname_dotcom %}. Este ejemplo se ancla a una versión específica de la acción mediante el SHA `b4f9ee0a9d4abbfc6986601d9b1a4f8f8e74c77e`.
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
@@ -435,9 +429,9 @@ Uses the `peter-evans/create-issue-from-file` action to create a new {% data var
|
||||
</td>
|
||||
<td>
|
||||
|
||||
Uses [`gh issue list`](https://cli.github.com/manual/gh_issue_list) to locate the previously created issue from earlier runs. This is [aliased](https://cli.github.com/manual/gh_alias_set) to `gh list-reports` for simpler processing in later steps. To get the issue URL, the `jq` expression processes the resulting JSON output.
|
||||
Usa [`gh issue list`](https://cli.github.com/manual/gh_issue_list) para buscar la incidencia creada previamente a partir de ejecuciones anteriores. Se le asigna el [alias](https://cli.github.com/manual/gh_alias_set) `gh list-reports` para facilitar el procesamiento en pasos posteriores. Para obtener la dirección URL de la incidencia, la expresión `jq` procesa la salida JSON resultante.
|
||||
|
||||
[`gh issue comment`](https://cli.github.com/manual/gh_issue_comment) is then used to add a comment to the new issue that links to the previous one.
|
||||
Después, se usa [`gh issue comment`](https://cli.github.com/manual/gh_issue_comment) para agregar un comentario a la nueva incidencia que vincula a la anterior.
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
@@ -455,7 +449,7 @@ Uses [`gh issue list`](https://cli.github.com/manual/gh_issue_list) to locate th
|
||||
</td>
|
||||
<td>
|
||||
|
||||
If an issue from a previous run is open and assigned to someone, then use [`gh issue comment`](https://cli.github.com/manual/gh_issue_comment) to add a comment with a link to the new issue.
|
||||
Si una incidencia de una ejecución anterior está abierta y asignada a alguien, usa [`gh issue comment`](https://cli.github.com/manual/gh_issue_comment) para agregar un comentario con un vínculo a la nueva incidencia.
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
@@ -476,16 +470,16 @@ If an issue from a previous run is open and assigned to someone, then use [`gh i
|
||||
</td>
|
||||
<td>
|
||||
|
||||
If an issue from a previous run is open and is not assigned to anyone, then:
|
||||
Si una incidencia de una ejecución anterior está abierta y no está asignada a nadie, haz lo siguiente:
|
||||
|
||||
* Use [`gh issue comment`](https://cli.github.com/manual/gh_issue_comment) to add a comment with a link to the new issue.
|
||||
* Use [`gh issue close`](https://cli.github.com/manual/gh_issue_close) to close the old issue.
|
||||
* Use [`gh issue edit`](https://cli.github.com/manual/gh_issue_edit) to edit the old issue to remove it from a specific {% data variables.product.prodname_dotcom %} project board.
|
||||
* Usa [`gh issue comment`](https://cli.github.com/manual/gh_issue_comment) para agregar un comentario con un vínculo a la nueva incidencia.
|
||||
* Usa [`gh issue close`](https://cli.github.com/manual/gh_issue_close) para cerrar la incidencia antigua.
|
||||
* Usa [`gh issue edit`](https://cli.github.com/manual/gh_issue_edit) para editar la incidencia antigua y quitarla de un panel de proyecto específico de {% data variables.product.prodname_dotcom %}.
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
## Next steps
|
||||
## Pasos siguientes
|
||||
|
||||
{% data reusables.actions.learning-actions %}
|
||||
|
||||
@@ -581,6 +581,8 @@ console.log("The running PID from the main action is: " + process.env.STATE_pro
|
||||
|
||||
During the execution of a workflow, the runner generates temporary files that can be used to perform certain actions. The path to these files are exposed via environment variables. You will need to use UTF-8 encoding when writing to these files to ensure proper processing of the commands. Multiple commands can be written to the same file, separated by newlines.
|
||||
|
||||
Most commands in the following examples use double quotes for echoing strings, which will attempt to interpolate characters like `$` for shell variable names. To always use literal values in quoted strings, you can use single quotes instead.
|
||||
|
||||
{% powershell %}
|
||||
|
||||
{% note %}
|
||||
|
||||
@@ -125,11 +125,11 @@ children:
|
||||
- /guides
|
||||
- /release-notes
|
||||
- /all-releases
|
||||
ms.openlocfilehash: ebd1473538d42928ff3d9abb3c0e2bd9f12767f5
|
||||
ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
|
||||
ms.openlocfilehash: 3980ad01e56bf1e38dd6473c5e5246c6d45350eb
|
||||
ms.sourcegitcommit: 3268914369fb29540e4d88ee5e56bc7a41f2a60e
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: es-ES
|
||||
ms.lasthandoff: 09/11/2022
|
||||
ms.locfileid: '147881159'
|
||||
ms.lasthandoff: 10/26/2022
|
||||
ms.locfileid: '148111316'
|
||||
---
|
||||
|
||||
|
||||
@@ -125,8 +125,8 @@ After removing the `autobuild` step, uncomment the `run` step and add build comm
|
||||
|
||||
``` yaml
|
||||
- run: |
|
||||
make bootstrap
|
||||
make release
|
||||
make bootstrap
|
||||
make release
|
||||
```
|
||||
|
||||
For more information about the `run` keyword, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsrun)."
|
||||
|
||||
@@ -1,188 +0,0 @@
|
||||
---
|
||||
title: Browsing security advisories in the GitHub Advisory Database
|
||||
intro: 'You can browse the {% data variables.product.prodname_advisory_database %} to find advisories for security risks in open source projects that are hosted on {% data variables.product.company_short %}.'
|
||||
shortTitle: Browse Advisory Database
|
||||
miniTocMaxHeadingLevel: 3
|
||||
redirect_from:
|
||||
- /github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database
|
||||
- /code-security/supply-chain-security/browsing-security-vulnerabilities-in-the-github-advisory-database
|
||||
- /code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/browsing-security-vulnerabilities-in-the-github-advisory-database
|
||||
- /code-security/dependabot/dependabot-alerts/browsing-security-vulnerabilities-in-the-github-advisory-database
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
type: how_to
|
||||
topics:
|
||||
- Security advisories
|
||||
- Alerts
|
||||
- Dependabot
|
||||
- Vulnerabilities
|
||||
- CVEs
|
||||
---
|
||||
<!--Marketing-LINK: From /features/security/software-supply-chain page "Browsing security vulnerabilities in the GitHub Advisory Database".-->
|
||||
|
||||
## About the {% data variables.product.prodname_advisory_database %}
|
||||
|
||||
The {% data variables.product.prodname_advisory_database %} contains a list of known security vulnerabilities {% ifversion GH-advisory-db-supports-malware %}and malware, {% endif %}grouped in two categories: {% data variables.product.company_short %}-reviewed advisories and unreviewed advisories.
|
||||
|
||||
{% data reusables.repositories.tracks-vulnerabilities %}
|
||||
|
||||
## About types of security advisories
|
||||
|
||||
{% data reusables.advisory-database.beta-malware-advisories %}
|
||||
|
||||
Each advisory in the {% data variables.product.prodname_advisory_database %} is for a vulnerability in open source projects{% ifversion GH-advisory-db-supports-malware %} or for malicious open source software{% endif %}.
|
||||
|
||||
{% data reusables.repositories.a-vulnerability-is %} Vulnerabilities in code are usually introduced by accident and fixed soon after they are discovered. You should update your code to use the fixed version of the dependency as soon as it is available.
|
||||
|
||||
{% ifversion GH-advisory-db-supports-malware %}
|
||||
|
||||
In contrast, malicious software, or malware, is code that is intentionally designed to perform unwanted or harmful functions. The malware may target hardware, software, confidential data, or users of any application that uses the malware. You need to remove the malware from your project and find an alternative, more secure replacement for the dependency.
|
||||
|
||||
{% endif %}
|
||||
|
||||
### {% data variables.product.company_short %}-reviewed advisories
|
||||
|
||||
{% data variables.product.company_short %}-reviewed advisories are security vulnerabilities{% ifversion GH-advisory-db-supports-malware %} or malware{% endif %} that have been mapped to packages in ecosystems we support. We carefully review each advisory for validity and ensure that they have a full description, and contain both ecosystem and package information.
|
||||
|
||||
Generally, we name our supported ecosystems after the software programming language's associated package registry. We review advisories if they are for a vulnerability in a package that comes from a supported registry.
|
||||
|
||||
- Composer (registry: https://packagist.org/){% ifversion GH-advisory-db-erlang-support %}
|
||||
- Erlang (registry: https://hex.pm/){% endif %}
|
||||
- Go (registry: https://pkg.go.dev/)
|
||||
{%- ifversion fpt or ghec or ghes > 3.6 or ghae > 3.6 %}
|
||||
- GitHub Actions (https://github.com/marketplace?type=actions/) {% endif %}
|
||||
- Maven (registry: https://repo.maven.apache.org/maven2)
|
||||
- npm (registry: https://www.npmjs.com/)
|
||||
- NuGet (registry: https://www.nuget.org/)
|
||||
- pip (registry: https://pypi.org/){% ifversion dependency-graph-dart-support %}
|
||||
- pub (registry: https://pub.dev/packages/registry){% endif %}
|
||||
- RubyGems (registry: https://rubygems.org/)
|
||||
- Rust (registry: https://crates.io/)
|
||||
|
||||
If you have a suggestion for a new ecosystem we should support, please open an [issue](https://github.com/github/advisory-database/issues) for discussion.
|
||||
|
||||
If you enable {% data variables.product.prodname_dependabot_alerts %} for your repositories, you are automatically notified when a new {% data variables.product.company_short %}-reviewed advisory reports a vulnerability {% ifversion GH-advisory-db-supports-malware %}or malware{% endif %} for a package you depend on. For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)."
|
||||
|
||||
### Unreviewed advisories
|
||||
|
||||
Unreviewed advisories are security vulnerabilites that we publish automatically into the {% data variables.product.prodname_advisory_database %}, directly from the National Vulnerability Database feed.
|
||||
|
||||
{% data variables.product.prodname_dependabot %} doesn't create {% data variables.product.prodname_dependabot_alerts %} for unreviewed advisories as this type of advisory isn't checked for validity or completion.
|
||||
|
||||
## About information in security advisories
|
||||
|
||||
Each security advisory contains information about the vulnerability{% ifversion GH-advisory-db-supports-malware %} or malware,{% endif %} which may include the description, severity, affected package, package ecosystem, affected versions and patched versions, impact, and optional information such as references, workarounds, and credits. In addition, advisories from the National Vulnerability Database list contain a link to the CVE record, where you can read more details about the vulnerability, its CVSS scores, and its qualitative severity level. For more information, see the "[National Vulnerability Database](https://nvd.nist.gov/)" from the National Institute of Standards and Technology.
|
||||
|
||||
The severity level is one of four possible levels defined in the "[Common Vulnerability Scoring System (CVSS), Section 5](https://www.first.org/cvss/specification-document)."
|
||||
- Low
|
||||
- Medium/Moderate
|
||||
- High
|
||||
- Critical
|
||||
|
||||
The {% data variables.product.prodname_advisory_database %} uses the CVSS levels described above. If {% data variables.product.company_short %} obtains a CVE, the {% data variables.product.prodname_advisory_database %} uses CVSS version 3.1. If the CVE is imported, the {% data variables.product.prodname_advisory_database %} supports both CVSS versions 3.0 and 3.1.
|
||||
|
||||
{% data reusables.repositories.github-security-lab %}
|
||||
|
||||
## Accessing an advisory in the {% data variables.product.prodname_advisory_database %}
|
||||
|
||||
1. Navigate to https://github.com/advisories.
|
||||
2. Optionally, to filter the list, use any of the drop-down menus.
|
||||
|
||||
{% tip %}
|
||||
|
||||
**Tip:** You can use the sidebar on the left to explore {% data variables.product.company_short %}-reviewed and unreviewed advisories separately.
|
||||
|
||||
{% endtip %}
|
||||
3. Click an advisory to view details. By default, you will see {% data variables.product.company_short %}-reviewed advisories for security vulnerabilities. {% ifversion GH-advisory-db-supports-malware %}To show malware advisories, use `type:malware` in the search bar.{% endif %}
|
||||
|
||||
|
||||
{% note %}
|
||||
|
||||
The database is also accessible using the GraphQL API. {% ifversion GH-advisory-db-supports-malware %}By default, queries will return {% data variables.product.company_short %}-reviewed advisories for security vulnerabilities unless you specify `type:malware`.{% endif %} For more information, see the "[`security_advisory` webhook event](/webhooks/event-payloads/#security_advisory)."
|
||||
|
||||
{% endnote %}
|
||||
|
||||
## Editing an advisory in the {% data variables.product.prodname_advisory_database %}
|
||||
You can suggest improvements to any advisory in the {% data variables.product.prodname_advisory_database %}. For more information, see "[Editing security advisories in the {% data variables.product.prodname_advisory_database %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/editing-security-advisories-in-the-github-advisory-database)."
|
||||
|
||||
## Searching the {% data variables.product.prodname_advisory_database %}
|
||||
|
||||
You can search the database, and use qualifiers to narrow your search. For example, you can search for advisories created on a certain date, in a specific ecosystem, or in a particular library.
|
||||
|
||||
{% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %}
|
||||
|
||||
{% data reusables.search.date_gt_lt %}
|
||||
|
||||
| Qualifier | Example |
|
||||
| ------------- | ------------- |
|
||||
| `type:reviewed`| [**type:reviewed**](https://github.com/advisories?query=type%3Areviewed) will show {% data variables.product.company_short %}-reviewed advisories for security vulnerabilities. |
|
||||
{% ifversion GH-advisory-db-supports-malware %}| `type:malware` | [**type:malware**](https://github.com/advisories?query=type%3Amalware) will show {% data variables.product.company_short %}-reviewed advisories for malware. |
|
||||
{% endif %}| `type:unreviewed`| [**type:unreviewed**](https://github.com/advisories?query=type%3Aunreviewed) will show unreviewed advisories. |
|
||||
| `GHSA-ID`| [**GHSA-49wp-qq6x-g2rf**](https://github.com/advisories?query=GHSA-49wp-qq6x-g2rf) will show the advisory with this {% data variables.product.prodname_advisory_database %} ID. |
|
||||
| `CVE-ID`| [**CVE-2020-28482**](https://github.com/advisories?query=CVE-2020-28482) will show the advisory with this CVE ID number. |
|
||||
| `ecosystem:ECOSYSTEM`| [**ecosystem:npm**](https://github.com/advisories?utf8=%E2%9C%93&query=ecosystem%3Anpm) will show only advisories affecting NPM packages. |
|
||||
| `severity:LEVEL`| [**severity:high**](https://github.com/advisories?utf8=%E2%9C%93&query=severity%3Ahigh) will show only advisories with a high severity level. |
|
||||
| `affects:LIBRARY`| [**affects:lodash**](https://github.com/advisories?utf8=%E2%9C%93&query=affects%3Alodash) will show only advisories affecting the lodash library. |
|
||||
| `cwe:ID`| [**cwe:352**](https://github.com/advisories?query=cwe%3A352) will show only advisories with this CWE number. |
|
||||
| `credit:USERNAME`| [**credit:octocat**](https://github.com/advisories?query=credit%3Aoctocat) will show only advisories credited to the "octocat" user account. |
|
||||
| `sort:created-asc`| [**sort:created-asc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Acreated-asc) will sort by the oldest advisories first. |
|
||||
| `sort:created-desc`| [**sort:created-desc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Acreated-desc) will sort by the newest advisories first. |
|
||||
| `sort:updated-asc`| [**sort:updated-asc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Aupdated-asc) will sort by the least recently updated first. |
|
||||
| `sort:updated-desc`| [**sort:updated-desc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Aupdated-desc) will sort by the most recently updated first. |
|
||||
| `is:withdrawn`| [**is:withdrawn**](https://github.com/advisories?utf8=%E2%9C%93&query=is%3Awithdrawn) will show only advisories that have been withdrawn. |
|
||||
| `created:YYYY-MM-DD`| [**created:2021-01-13**](https://github.com/advisories?utf8=%E2%9C%93&query=created%3A2021-01-13) will show only advisories created on this date. |
|
||||
| `updated:YYYY-MM-DD`| [**updated:2021-01-13**](https://github.com/advisories?utf8=%E2%9C%93&query=updated%3A2021-01-13) will show only advisories updated on this date. |
|
||||
|
||||
## Viewing your vulnerable repositories
|
||||
|
||||
For any {% data variables.product.company_short %}-reviewed advisory in the {% data variables.product.prodname_advisory_database %}, you can see which of your repositories are affected by that security vulnerability{% ifversion GH-advisory-db-supports-malware %} or malware{% endif %}. To see a vulnerable repository, you must have access to {% data variables.product.prodname_dependabot_alerts %} for that repository. For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies#access-to-dependabot-alerts)."
|
||||
|
||||
1. Navigate to https://github.com/advisories.
|
||||
2. Click an advisory.
|
||||
3. At the top of the advisory page, click **Dependabot alerts**.
|
||||
|
||||
4. Optionally, to filter the list, use the search bar or the drop-down menus. The "Organization" drop-down menu allows you to filter the {% data variables.product.prodname_dependabot_alerts %} per owner (organization or user).
|
||||
|
||||
5. For more details about the advisory, and for advice on how to fix the vulnerable repository, click the repository name.
|
||||
|
||||
{% ifversion security-advisories-ghes-ghae %}
|
||||
## Accessing the local advisory database on {% data variables.location.product_location %}
|
||||
|
||||
If your site administrator has enabled {% data variables.product.prodname_github_connect %} for {% data variables.location.product_location %}, you can also browse reviewed advisories locally. For more information, see "[About {% data variables.product.prodname_github_connect %}](/admin/configuration/configuring-github-connect/about-github-connect)".
|
||||
|
||||
You can use your local advisory database to check whether a specific security vulnerability is included, and therefore whether you'd get alerts for vulnerable dependencies. You can also view any vulnerable repositories.
|
||||
|
||||
1. Navigate to `https://HOSTNAME/advisories`.
|
||||
2. Optionally, to filter the list, use any of the drop-down menus.
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** Only reviewed advisories will be listed. Unreviewed advisories can be viewed in the {% data variables.product.prodname_advisory_database %} on {% data variables.product.prodname_dotcom_the_website %}. For more information, see "[Accessing an advisory in the GitHub Advisory Database](#accessing-an-advisory-in-the-github-advisory-database)".
|
||||
|
||||
{% endnote %}
|
||||
3. Click an advisory to view details.{% ifversion GH-advisory-db-supports-malware %} By default, you will see {% data variables.product.company_short %}-reviewed advisories for security vulnerabilities. To show malware advisories, use `type:malware` in the search bar.{% endif %}
|
||||
|
||||
You can also suggest improvements to any advisory directly from your local advisory database. For more information, see "[Editing advisories from {% data variables.location.product_location %}](/code-security/dependabot/dependabot-alerts/editing-security-advisories-in-the-github-advisory-database#editing-advisories-from-your-github-enterprise-server-instance)".
|
||||
|
||||
### Viewing vulnerable repositories for {% data variables.location.product_location %}
|
||||
|
||||
{% data reusables.repositories.enable-security-alerts %}
|
||||
|
||||
In the local advisory database, you can see which repositories are affected by each security vulnerability{% ifversion GH-advisory-db-supports-malware %} or malware{% endif %}. To see a vulnerable repository, you must have access to {% data variables.product.prodname_dependabot_alerts %} for that repository. For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies#access-to-dependabot-alerts)."
|
||||
|
||||
1. Navigate to `https://HOSTNAME/advisories`.
|
||||
2. Click an advisory.
|
||||
3. At the top of the advisory page, click **Dependabot alerts**.
|
||||
|
||||
4. Optionally, to filter the list, use the search bar or the drop-down menus. The "Organization" drop-down menu allows you to filter the {% data variables.product.prodname_dependabot_alerts %} per owner (organization or user).
|
||||
|
||||
5. For more details about the advisory, and for advice on how to fix the vulnerable repository, click the repository name.
|
||||
|
||||
{% endif %}
|
||||
|
||||
## Further reading
|
||||
|
||||
- MITRE's [definition of "vulnerability"](https://www.cve.org/ResourcesSupport/Glossary#vulnerability)
|
||||
@@ -1,55 +0,0 @@
|
||||
---
|
||||
title: Editing security advisories in the GitHub Advisory Database
|
||||
intro: 'You can submit improvements to any advisory published in the {% data variables.product.prodname_advisory_database %}.'
|
||||
redirect_from:
|
||||
- /code-security/security-advisories/editing-security-advisories-in-the-github-advisory-database
|
||||
- /code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/editing-security-advisories-in-the-github-advisory-database
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
type: how_to
|
||||
topics:
|
||||
- Security advisories
|
||||
- Alerts
|
||||
- Dependabot
|
||||
- Vulnerabilities
|
||||
- CVEs
|
||||
shortTitle: Edit Advisory Database
|
||||
---
|
||||
|
||||
## About editing advisories in the {% data variables.product.prodname_advisory_database %}
|
||||
Security advisories in the {% data variables.product.prodname_advisory_database %} at [github.com/advisories](https://github.com/advisories) are considered global advisories. Anyone can suggest improvements on any global security advisory in the {% data variables.product.prodname_advisory_database %}. You can edit or add any detail, including additionally affected ecosystems, severity level or description of who is impacted. The {% data variables.product.prodname_security %} curation team will review the submitted improvements and publish them onto the {% data variables.product.prodname_advisory_database %} if accepted.
|
||||
{% ifversion fpt or ghec %}
|
||||
Only repository owners and administrators can edit repository-level security advisories. For more information, see "[Editing a repository security advisory](/code-security/security-advisories/editing-a-security-advisory)."{% endif %}
|
||||
|
||||
## Editing advisories in the GitHub Advisory Database
|
||||
|
||||
1. Navigate to https://github.com/advisories.
|
||||
1. Select the security advisory you would like to contribute to.
|
||||
1. On the right-hand side of the page, click the **Suggest improvements for this vulnerability** link.
|
||||
|
||||
|
||||
|
||||
1. In the "Improve security advisory" form, make the desired improvements. You can edit or add any detail.{% ifversion fpt or ghec %} For information about correctly specifying information on the form, including affected versions, see "[Best practices for writing repository security advisories](/code-security/repository-security-advisories/best-practices-for-writing-repository-security-advisories)."{% endif %}{% ifversion security-advisories-reason-for-change %}
|
||||
1. Under **Reason for change**, explain why you want to make this improvement. If you include links to supporting material this will help our reviewers.
|
||||
|
||||
{% endif %}
|
||||
|
||||
1. When you finish editing the advisory, click **Submit improvements**.
|
||||
1. Once you submit your improvements, a pull request containing your changes will be created for review in [github/advisory-database](https://github.com/github/advisory-database) by the {% data variables.product.prodname_security %} curation team. If the advisory originated from a {% data variables.product.prodname_dotcom %} repository, we will also tag the original publisher for optional commentary. You can view the pull request and get notifications when it is updated or closed.
|
||||
|
||||
You can also open a pull request directly on an advisory file in the [github/advisory-database](https://github.com/github/advisory-database) repository. For more information, see the [contribution guidelines](https://github.com/github/advisory-database/blob/main/CONTRIBUTING.md).
|
||||
|
||||
{% ifversion security-advisories-ghes-ghae %}
|
||||
## Editing advisories from {% data variables.location.product_location %}
|
||||
|
||||
If you have {% data variables.product.prodname_github_connect %} enabled for {% data variables.location.product_location %}, you will be able to see advisories by adding `/advisories` to the instance url.
|
||||
|
||||
1. Navigate to `https://HOSTNAME/advisories`.
|
||||
2. Select the security advisory you would like to contribute to.
|
||||
3. On the right-hand side of the page, click the **Suggest improvements for this vulnerability on {% data variables.product.prodname_dotcom_the_website %}.** link. A new tab opens with the same security advisory on {% data variables.product.prodname_dotcom_the_website %}.
|
||||
|
||||
4. Edit the advisory, following steps four through six in "[Editing advisories in the GitHub Advisory Database](#editing-advisories-in-the-github-advisory-database)" above.
|
||||
{% endif %}
|
||||
@@ -15,8 +15,6 @@ topics:
|
||||
- Repositories
|
||||
- Dependencies
|
||||
children:
|
||||
- /browsing-security-advisories-in-the-github-advisory-database
|
||||
- /editing-security-advisories-in-the-github-advisory-database
|
||||
- /about-dependabot-alerts
|
||||
- /configuring-dependabot-alerts
|
||||
- /viewing-and-updating-dependabot-alerts
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Agregar una política de seguridad a tu repositorio
|
||||
intro: Puedes dar instrucciones de cómo reportar una vulnerabilidad de seguridad en tu proyecto si agregas una política de seguridad a tu repositorio.
|
||||
title: Adding a security policy to your repository
|
||||
intro: You can give instructions for how to report a security vulnerability in your project by adding a security policy to your repository.
|
||||
redirect_from:
|
||||
- /articles/adding-a-security-policy-to-your-repository
|
||||
- /github/managing-security-vulnerabilities/adding-a-security-policy-to-your-repository
|
||||
@@ -17,47 +17,49 @@ topics:
|
||||
- Repositories
|
||||
- Health
|
||||
shortTitle: Add a security policy
|
||||
ms.openlocfilehash: f081d6e6bd99f604e7e86bc094f76de9041adf4b
|
||||
ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: es-ES
|
||||
ms.lasthandoff: 09/10/2022
|
||||
ms.locfileid: '145091550'
|
||||
---
|
||||
## Acerca de las políticas de seguridad
|
||||
|
||||
Para proporcionar instrucciones sobre cómo notificar vulnerabilidades de seguridad en el proyecto,{% ifversion fpt or ghes or ghec %} puede agregar un archivo _SECURITY.md_ a la raíz, `docs`, o a la carpeta `.github` del repositorio.{% else %} puede agregar un archivo _SECURITY.md_ a la raíz o a la carpeta `docs` del repositorio.{% endif %} Cuando alguien cree una incidencia en el repositorio, verá un vínculo a la directiva de seguridad del proyecto.
|
||||
## About security policies
|
||||
|
||||
To give people instructions for reporting security vulnerabilities in your project,{% ifversion fpt or ghes or ghec %} you can add a _SECURITY.md_ file to your repository's root, `docs`, or `.github` folder.{% else %} you can add a _SECURITY.md_ file to your repository's root, or `docs` folder.{% endif %} When someone creates an issue in your repository, they will see a link to your project's security policy.
|
||||
|
||||
{% ifversion not ghae %}
|
||||
<!-- no public repos in GHAE -->
|
||||
Puedes crear una política de seguridad predeterminada para tu organización o cuenta personal. Para más información, vea "[Creación de un archivo de estado de la comunidad predeterminado](/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file)".
|
||||
You can create a default security policy for your organization or personal account. For more information, see "[Creating a default community health file](/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file)."
|
||||
{% endif %}
|
||||
|
||||
{% tip %}
|
||||
|
||||
**Sugerencia:** Para ayudar a los usuarios a encontrar su directiva de seguridad, puede vincular a su archivo _SECURITY.md_ desde otros lugares del repositorio, como un archivo Léame. Para más información, vea "[Acerca de los archivos Léame](/articles/about-readmes)".
|
||||
**Tip:** To help people find your security policy, you can link to your _SECURITY.md_ file from other places in your repository, such as your README file. For more information, see "[About READMEs](/articles/about-readmes)."
|
||||
|
||||
{% endtip %}
|
||||
|
||||
{% ifversion fpt or ghec %} Cuando alguien informa de una vulnerabilidad de seguridad en el proyecto, puede usar {% data variables.product.prodname_security_advisories %} para divulgar, corregir y publicar información sobre esta. Para obtener más información sobre el proceso de generación de informes y la divulgación de vulnerabilidades en {% data variables.product.prodname_dotcom %}, vea "[Acerca de la divulgación coordinada de vulnerabilidades de seguridad](/code-security/security-advisories/about-coordinated-disclosure-of-security-vulnerabilities#about-reporting-and-disclosing-vulnerabilities-in-projects-on-github)". Para más información sobre {% data variables.product.prodname_security_advisories %}, vea "[Acerca de {% data variables.product.prodname_security_advisories %}](/github/managing-security-vulnerabilities/about-github-security-advisories)".
|
||||
{% ifversion fpt or ghec %}
|
||||
After someone reports a security vulnerability in your project, you can use {% data variables.product.prodname_security_advisories %} to disclose, fix, and publish information about the vulnerability. For more information about the process of reporting and disclosing vulnerabilities in {% data variables.product.prodname_dotcom %}, see "[About coordinated disclosure of security vulnerabilities](/code-security/security-advisories/about-coordinated-disclosure-of-security-vulnerabilities#about-reporting-and-disclosing-vulnerabilities-in-projects-on-github)." For more information about repository security advisories, see "[About repository security advisories](/github/managing-security-vulnerabilities/about-github-security-advisories)."
|
||||
|
||||
{% data reusables.repositories.github-security-lab %} {% endif %} {% ifversion ghes or ghae %}
|
||||
{% data reusables.repositories.github-security-lab %}
|
||||
{% endif %}
|
||||
{% ifversion ghes or ghae %}
|
||||
<!-- alternative to the content about GitHub Security Advisories in the dotcom article -->
|
||||
Cuando pones las instrucciones de reporte de seguridad claramente disponibles, facilitas a tus usurios el reportar cualquier vulnerabilidad de seguridad que encuentren en tu repositorio utilizando tu canal de comunicación preferido.
|
||||
By making security reporting instructions clearly available, you make it easy for your users to report any security vulnerabilities they find in your repository using your preferred communication channel.
|
||||
{% endif %}
|
||||
|
||||
## Agregar una política de seguridad a tu repositorio
|
||||
## Adding a security policy to your repository
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %}
|
||||
3. En la barra lateral izquierda, haga clic en **Security policy** (Directiva de seguridad).
|
||||
|
||||
4. Haga clic en **Iniciar configuración**.
|
||||
|
||||
5. En el nuevo archivo _SECURITY.md_, agregue información sobre las versiones admitidas del proyecto y cómo notificar una vulnerabilidad.
|
||||
{% data reusables.files.write_commit_message %} {% data reusables.files.choose-commit-email %} {% data reusables.files.choose_commit_branch %} {% data reusables.files.propose_file_change %}
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
{% data reusables.repositories.sidebar-security %}
|
||||
3. In the left sidebar, click **Security policy**.
|
||||
|
||||
4. Click **Start setup**.
|
||||
|
||||
5. In the new _SECURITY.md_ file, add information about supported versions of your project and how to report a vulnerability.
|
||||
{% data reusables.files.write_commit_message %}
|
||||
{% data reusables.files.choose-commit-email %}
|
||||
{% data reusables.files.choose_commit_branch %}
|
||||
{% data reusables.files.propose_file_change %}
|
||||
|
||||
## Información adicional
|
||||
## Further reading
|
||||
|
||||
- "[Protección del repositorio](/code-security/getting-started/securing-your-repository)"{% ifversion not ghae %}
|
||||
- "[Configuración del proyecto para contribuciones correctas](/communities/setting-up-your-project-for-healthy-contributions)"{% endif %}{% ifversion fpt or ghec %}
|
||||
- "[Securing your repository](/code-security/getting-started/securing-your-repository)"{% ifversion not ghae %}
|
||||
- "[Setting up your project for healthy contributions](/communities/setting-up-your-project-for-healthy-contributions)"{% endif %}{% ifversion fpt or ghec %}
|
||||
- [{% data variables.product.prodname_security %}]({% data variables.product.prodname_security_link %}){% endif %}
|
||||
|
||||
@@ -28,7 +28,7 @@ Make it easy for your users to confidentially report security vulnerabilities th
|
||||
{% ifversion fpt or ghec %}
|
||||
### Security advisories
|
||||
|
||||
Privately discuss and fix security vulnerabilities in your repository's code. You can then publish a security advisory to alert your community to the vulnerability and encourage community members to upgrade. For more information, see "[About {% data variables.product.prodname_security_advisories %}](/github/managing-security-vulnerabilities/about-github-security-advisories)."
|
||||
Privately discuss and fix security vulnerabilities in your repository's code. You can then publish a security advisory to alert your community to the vulnerability and encourage community members to upgrade. For more information, see "[About repository security advisories](/github/managing-security-vulnerabilities/about-github-security-advisories)."
|
||||
|
||||
{% endif %}
|
||||
{% ifversion fpt or ghec or ghes %}
|
||||
|
||||
@@ -125,7 +125,7 @@ For more information, see "[Managing security and analysis settings for your org
|
||||
## Next steps
|
||||
You can view and manage alerts from security features to address dependencies and vulnerabilities in your code. For more information, see {% ifversion fpt or ghes or ghec %} "[Viewing and updating {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts),"{% endif %} {% ifversion fpt or ghec or ghes %}"[Managing pull requests for dependency updates](/code-security/supply-chain-security/managing-pull-requests-for-dependency-updates)," {% endif %}"[Managing {% data variables.product.prodname_code_scanning %} for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)," and "[Managing alerts from {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/managing-alerts-from-secret-scanning)."
|
||||
|
||||
{% ifversion fpt or ghec %}If you have a security vulnerability, you can create a security advisory to privately discuss and fix the vulnerability. For more information, see "[About {% data variables.product.prodname_security_advisories %}](/code-security/security-advisories/about-github-security-advisories)" and "[Creating a security advisory](/code-security/security-advisories/creating-a-security-advisory)."
|
||||
{% ifversion fpt or ghec %}If you have a security vulnerability, you can create a security advisory to privately discuss and fix the vulnerability. For more information, see "[About repository security advisories](/code-security/security-advisories/about-github-security-advisories)" and "[Creating a security advisory](/code-security/security-advisories/creating-a-security-advisory)."
|
||||
{% endif %}
|
||||
|
||||
{% ifversion ghes or ghec or ghae %}You{% elsif fpt %}Organizations that use {% data variables.product.prodname_ghe_cloud %}{% endif %} can view, filter, and sort security alerts for repositories owned by {% ifversion ghes or ghec or ghae %}your{% elsif fpt %}their{% endif %} organization in the security overview. For more information, see{% ifversion ghes or ghec or ghae %} "[About the security overview](/code-security/security-overview/about-the-security-overview)."{% elsif fpt %} "[About the security overview](/enterprise-cloud@latest/code-security/security-overview/about-the-security-overview)" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% endif %}
|
||||
|
||||
@@ -133,5 +133,5 @@ You can set up {% data variables.product.prodname_code_scanning %} to automatica
|
||||
## Next steps
|
||||
You can view and manage alerts from security features to address dependencies and vulnerabilities in your code. For more information, see {% ifversion fpt or ghes or ghec %} "[Viewing and updating {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts),"{% endif %} {% ifversion fpt or ghec or ghes %}"[Managing pull requests for dependency updates](/code-security/supply-chain-security/managing-pull-requests-for-dependency-updates)," {% endif %}"[Managing {% data variables.product.prodname_code_scanning %} for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)," and "[Managing alerts from {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/managing-alerts-from-secret-scanning)."
|
||||
|
||||
{% ifversion fpt or ghec %}If you have a security vulnerability, you can create a security advisory to privately discuss and fix the vulnerability. For more information, see "[About {% data variables.product.prodname_security_advisories %}](/code-security/security-advisories/about-github-security-advisories)" and "[Creating a security advisory](/code-security/security-advisories/creating-a-security-advisory)."
|
||||
{% ifversion fpt or ghec %}If you have a security vulnerability, you can create a security advisory to privately discuss and fix the vulnerability. For more information, see "[About repository security advisories](/code-security/security-advisories/about-github-security-advisories)" and "[Creating a security advisory](/code-security/security-advisories/creating-a-security-advisory)."
|
||||
{% endif %}
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Seguridad de código
|
||||
title: Code security
|
||||
shortTitle: Code security
|
||||
intro: 'Crea la seguridad de tu flujo de trabajo de {% data variables.product.prodname_dotcom %} con características para mantener tus secretos y vulnerabilidades fuera de tu codebase {% ifversion not ghae %}, y para mantener la cadena de suministro de tu software{% endif %}.'
|
||||
intro: 'Build security into your {% data variables.product.prodname_dotcom %} workflow with features to keep secrets and vulnerabilities out of your codebase{% ifversion not ghae %}, and to maintain your software supply chain{% endif %}.'
|
||||
introLinks:
|
||||
overview: /code-security/getting-started/github-security-features
|
||||
featuredLinks:
|
||||
@@ -53,16 +53,10 @@ children:
|
||||
- /adopting-github-advanced-security-at-scale
|
||||
- /secret-scanning
|
||||
- /code-scanning
|
||||
- /repository-security-advisories
|
||||
- /security-advisories
|
||||
- /supply-chain-security
|
||||
- /dependabot
|
||||
- /security-overview
|
||||
- /guides
|
||||
ms.openlocfilehash: 90d3ad046a6531849edd8e783db265866f118d90
|
||||
ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: es-ES
|
||||
ms.lasthandoff: 09/05/2022
|
||||
ms.locfileid: '147145243'
|
||||
---
|
||||
|
||||
|
||||
@@ -1,71 +0,0 @@
|
||||
---
|
||||
title: About coordinated disclosure of security vulnerabilities
|
||||
intro: Vulnerability disclosure is a coordinated effort between security reporters and repository maintainers.
|
||||
redirect_from:
|
||||
- /code-security/security-advisories/about-coordinated-disclosure-of-security-vulnerabilities
|
||||
miniTocMaxHeadingLevel: 3
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
type: overview
|
||||
topics:
|
||||
- Security advisories
|
||||
- Vulnerabilities
|
||||
shortTitle: Coordinated disclosure
|
||||
---
|
||||
|
||||
## About disclosing vulnerabilities in the industry
|
||||
|
||||
{% data reusables.security-advisory.disclosing-vulnerabilities %}
|
||||
|
||||
The initial report of a vulnerability is made privately, and the full details are only published once the maintainer has acknowledged the issue, and ideally made remediations or a patch available, sometimes with a delay to allow more time for the patches to be installed. For more information, see the "[OWASP Cheat Sheet Series about vulnerability disclosure](https://cheatsheetseries.owasp.org/cheatsheets/Vulnerability_Disclosure_Cheat_Sheet.html#commercial-and-open-source-software)" on the OWASP Cheat Sheet Series website.
|
||||
|
||||
### Best practices for vulnerability reporters
|
||||
|
||||
It's good practice to report vulnerabilities privately to maintainers. When possible, as a vulnerability reporter, we recommend you avoid:
|
||||
- Disclosing the vulnerability publicly without giving maintainers a chance to remediate.
|
||||
- Bypassing the maintainers.
|
||||
- Disclosing the vulnerability before a fixed version of the code is available.
|
||||
- Expecting to be compensated for reporting an issue, where no public bounty program exists.
|
||||
|
||||
It's acceptable for vulnerability reporters to disclose a vulnerability publicly after a period of time, if they have tried to contact the maintainers and not received a response, or contacted them and been asked to wait too long to disclose it.
|
||||
|
||||
We recommend vulnerability reporters clearly state the terms of their disclosure policy as part of their reporting process. Even if the vulnerability reporter does not adhere to a strict policy, it's a good idea to set clear expectations for maintainers in terms of timelines on intended vulnerability disclosures. For an example of disclosure policy, see the "[Security Lab's disclosure policy](https://securitylab.github.com/advisories#policy)" on the GitHub Security Lab website.
|
||||
|
||||
### Best practices for maintainers
|
||||
|
||||
As a maintainer, it's good practice to clearly indicate how and where you want to receive reports for vulnerabilities. If this information is not clearly available, vulnerability reporters don't know how to contact you, and may resort to extracting developer email addresses from git commit histories to try to find an appropriate security contact. This can lead to friction, lost reports, or the publication of unresolved reports.
|
||||
|
||||
Maintainers should disclose vulnerabilities in a timely manner. If there is a security vulnerability in your repository, we recommend you:
|
||||
- Treat the vulnerability as a security issue rather than a simple bug, both in your response and your disclosure. For example, you'll need to explicitly mention that the issue is a security vulnerability in the release notes.
|
||||
- Acknowledge receipt of the vulnerability report as quickly as possible, even if no immediate resources are available for investigation. This sends the message that you are quick to respond and act, and it sets a positive tone for the rest of the interaction between you and the vulnerability reporter.
|
||||
- Involve the vulnerability reporter when you verify the impact and veracity of the report. It's likely the vulnerability reporter has already spent time considering the vulnerability in a variety of scenarios, some of which you may have not considered yourself.
|
||||
- Remediate the issue in a way that you see fit, taking any concerns and advice provided by the vulnerability reporter into careful consideration. Often the vulnerability reporter will have knowledge of certain corner cases and remediation bypasses that are easy to miss without a security research background.
|
||||
- Always acknowledge the vulnerability reporter when you credit the discovery.
|
||||
- Aim to publish a fix as soon as you can.
|
||||
- Ensure that you make the wider ecosystem aware of the issue and its remediation when you disclose the vulnerability. It is not uncommon to see cases where a recognized security issue is fixed in the current development branch of a project, but the commit or subsequent release is not explicitly marked as a security fix or release. This can cause problems with downstream consumers.
|
||||
|
||||
Publishing the details of a security vulnerability doesn't make maintainers look bad. Security vulnerabilities are present everywhere in software, and users will trust maintainers who have a clear and established process for disclosing security vulnerabilities in their code.
|
||||
|
||||
## About reporting and disclosing vulnerabilities in projects on {% data variables.product.prodname_dotcom %}
|
||||
|
||||
The process for reporting and disclosing vulnerabilities for projects on {% data variables.product.prodname_dotcom_the_website %} is as follows:
|
||||
|
||||
If you are a vulnerability reporter (for example, a security researcher) who would like report a vulnerability, first check if there is a security policy for the related repository. For more information, see "[About security policies](/code-security/getting-started/adding-a-security-policy-to-your-repository#about-security-policies)." If there is one, follow it to understand the process before contacting the security team for that repository.
|
||||
|
||||
If there isn't a security policy in place, the most efficient way to establish a private means of communication with maintainers is to create an issue asking for a preferred security contact. It's worth noting that the issue will be immediately publicly visible, so it should not include any information about the bug. Once communication is established, you can suggest the maintainers define a security policy for future use.
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note**: _For npm only_ - If we receive a report of malware in an npm package, we try to contact you privately. If you don't address the issue in a timely manner, we will disclose it. For more information, see "[Reporting malware in an npm package](https://docs.npmjs.com/reporting-malware-in-an-npm-package)" on the npm Docs website.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
If you've found a security vulnerability in {% data variables.product.prodname_dotcom_the_website %}, please report the vulnerability through our coordinated disclosure process. For more information, see the [{% data variables.product.prodname_dotcom %} Security Bug Bounty](https://bounty.github.com/) website.
|
||||
|
||||
If you are a maintainer, you can take ownership of the process at the very beginning of the pipeline by setting up a security policy for your repository, or otherwise making security reporting instructions clearly available, for example in your project’s README file. For information about adding a security policy, see "[About security policies](/code-security/getting-started/adding-a-security-policy-to-your-repository#about-security-policies)." If there is no security policy, it's likely that a vulnerability reporter will try to email you or otherwise privately contact you. Alternatively, someone may open a (public) issue with details of a security issue.
|
||||
|
||||
As a maintainer, to disclose a vulnerability in your code, you first create a draft security advisory in the package's repository in {% data variables.product.prodname_dotcom %}. {% data reusables.security-advisory.security-advisory-overview %} For more information, see "[About {% data variables.product.prodname_security_advisories %} for repositories](/code-security/repository-security-advisories/about-github-security-advisories-for-repositories)."
|
||||
|
||||
|
||||
To get started, see "[Creating a repository security advisory](/code-security/repository-security-advisories/creating-a-repository-security-advisory)."
|
||||
@@ -1,66 +0,0 @@
|
||||
---
|
||||
title: Acerca de los avisos de seguridad de GitHub para repositorios
|
||||
intro: 'Puedes usar {% data variables.product.prodname_security_advisories %} para discutir, corregir y publicar información sobre vulnerabilidades de seguridad en tu repositorio.'
|
||||
redirect_from:
|
||||
- /articles/about-maintainer-security-advisories
|
||||
- /github/managing-security-vulnerabilities/about-maintainer-security-advisories
|
||||
- /github/managing-security-vulnerabilities/about-github-security-advisories
|
||||
- /code-security/security-advisories/about-github-security-advisories
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
type: overview
|
||||
topics:
|
||||
- Security advisories
|
||||
- Vulnerabilities
|
||||
- CVEs
|
||||
shortTitle: Repository security advisories
|
||||
ms.openlocfilehash: 5c8ad99a2bee30f52a185fa15421bc6b23429fbf
|
||||
ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: es-ES
|
||||
ms.lasthandoff: 09/10/2022
|
||||
ms.locfileid: '145091532'
|
||||
---
|
||||
{% data reusables.repositories.security-advisory-admin-permissions %}
|
||||
|
||||
{% data reusables.security-advisory.security-researcher-cannot-create-advisory %}
|
||||
|
||||
## About {% data variables.product.prodname_security_advisories %}
|
||||
|
||||
{% data reusables.security-advisory.disclosing-vulnerabilities %} Para más información, vea "[Acerca de la divulgación coordinada de vulnerabilidades de seguridad](/code-security/repository-security-advisories/about-coordinated-disclosure-of-security-vulnerabilities)".
|
||||
|
||||
{% data reusables.security-advisory.security-advisory-overview %}
|
||||
|
||||
Con {% data variables.product.prodname_security_advisories %}, puedes:
|
||||
|
||||
1. Crear un borrador de asesoría de seguridad y utilizarlo para debatir de manera privada sobre el impacto de la vulnerabilidad en tu proyecto. Para más información, vea "[Creación de un aviso de seguridad de repositorio](/code-security/repository-security-advisories/creating-a-repository-security-advisory)".
|
||||
2. Colaborar en privado para solucionar la vulnerabilidad en una bifurcación privada temporaria.
|
||||
3. Publica la asesoría de seguridad para alertar a tu comunidad sobre la vulnerabilidad una vez que se lance el parche. Para más información, vea "[Publicación de un aviso de seguridad de repositorio](/code-security/repository-security-advisories/publishing-a-repository-security-advisory)".
|
||||
|
||||
{% data reusables.repositories.security-advisories-republishing %}
|
||||
|
||||
Puedes dar crédito a los individuos que contribuyeron con una asesoría de seguridad. Para más información, vea "[Edición de un aviso de seguridad de repositorio](/code-security/repository-security-advisories/editing-a-repository-security-advisory#about-credits-for-security-advisories)".
|
||||
|
||||
{% data reusables.repositories.security-guidelines %}
|
||||
|
||||
Si creaste una asesoría de seguridad en tu repositorio, esta permanecerá en tu repositorio. Publicamos avisos de seguridad para todos los ecosistemas compatibles con el gráfico de dependencias en la {% data variables.product.prodname_advisory_database %} en [github.com/advisories](https://github.com/advisories). Cualquiera puede enviar un cambio de un aviso publicado en {% data variables.product.prodname_advisory_database %}. Para más información, vea "[Edición de avisos de seguridad en {% data variables.product.prodname_advisory_database %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/editing-security-advisories-in-the-github-advisory-database)".
|
||||
|
||||
Si una asesoría de seguridad es específicamente para npm, también la publicamos en las asesorías de seguridad de npm. Para más información, vea [npmjs.com/advisories](https://www.npmjs.com/advisories).
|
||||
|
||||
{% data reusables.repositories.github-security-lab %}
|
||||
|
||||
## Números de identificación CVE
|
||||
|
||||
Las {% data variables.product.prodname_security_advisories %} se construyen sobre las bases de la lista de Vulnerabilidades y Exposiciones Comunes (CVE, por sus siglas en inglés). El formato de asesoría de seguridad en {% data variables.product.prodname_dotcom %} es un formato estandarizado que coincide con el formato de descripción de CVE.
|
||||
|
||||
{% data variables.product.prodname_dotcom %} es una Autoridad de Numeración de CVE (CNA, por sus siglas en inglés) y está autorizado para asignar números de identificación de CVE. Para más información, vea "[Acerca de CVE](https://www.cve.org/About/Overview)" y "[Entidades de numeración de CVE](https://www.cve.org/ProgramOrganization/CNAs)" en el sitio web de CVE.
|
||||
|
||||
Cuando creas una asesoría de seguridad para un repositorio público en {% data variables.product.prodname_dotcom %}, tienes la opción de proporcionar un número de identificación de CVE para la vulnerabilidad de seguridad. {% data reusables.repositories.request-security-advisory-cve-id %}
|
||||
|
||||
Una vez que hayas publicado la asesoría de seguridad y que {% data variables.product.prodname_dotcom %} haya asignado un número de identificación CVE a la vulnerabilidad, {% data variables.product.prodname_dotcom %} publicará el CVE a la base de datos de MITRE.
|
||||
Para más información, vea "[Publicación de un aviso de seguridad de repositorio](/code-security/repository-security-advisories/publishing-a-repository-security-advisory)".
|
||||
|
||||
## {% data variables.product.prodname_dependabot_alerts %} para las asesorías de seguridad publicadas
|
||||
|
||||
{% data reusables.repositories.github-reviews-security-advisories %}
|
||||
@@ -1,50 +0,0 @@
|
||||
---
|
||||
title: Incorporación de un colaborador a un aviso de seguridad de repositorio
|
||||
intro: Puedes agregar otros usuarios o equipos para que colaboren contigo en un aviso de seguridad.
|
||||
redirect_from:
|
||||
- /articles/adding-a-collaborator-to-a-maintainer-security-advisory
|
||||
- /github/managing-security-vulnerabilities/adding-a-collaborator-to-a-maintainer-security-advisory
|
||||
- /github/managing-security-vulnerabilities/adding-a-collaborator-to-a-security-advisory
|
||||
- /code-security/security-advisories/adding-a-collaborator-to-a-security-advisory
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
type: how_to
|
||||
topics:
|
||||
- Security advisories
|
||||
- Vulnerabilities
|
||||
- Collaboration
|
||||
shortTitle: Add collaborators
|
||||
ms.openlocfilehash: 6fa4062fab8e4ffc59724ceb0ba3b6b536871df9
|
||||
ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: es-ES
|
||||
ms.lasthandoff: 09/10/2022
|
||||
ms.locfileid: '147879428'
|
||||
---
|
||||
Las personas con permisos de administrador en una asesoría de seguridad pueden añadir colaboradores a la misma.
|
||||
|
||||
{% data reusables.security-advisory.repository-level-advisory-note %}
|
||||
|
||||
## Añadir un colaborador a una asesoría de seguridad
|
||||
|
||||
Los colaboradores tienen permisos de escritura para el aviso de seguridad. Para obtener más información, vea "[Niveles de permisos para avisos de seguridad del repositorio](/code-security/repository-security-advisories/permission-levels-for-repository-security-advisories)".
|
||||
|
||||
{% note %}
|
||||
|
||||
{% data reusables.repositories.security-advisory-collaborators-public-repositories %} Para obtener más información sobre cómo quitar un colaborador en un aviso de seguridad, vea "[Eliminación de un colaborador de un aviso de seguridad del repositorio](/code-security/repository-security-advisories/removing-a-collaborator-from-a-repository-security-advisory)".
|
||||
|
||||
{% endnote %}
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} {% data reusables.repositories.sidebar-advisories %}
|
||||
4. En la lista de "Asesorías de Seguridad", da clic en la asesoría a la cual quieras añadir un colaborador.
|
||||
5. En la parte derecha de la página, debajo de "Colaboradores", teclea el nombre de usuario o equipo que quieras añadir a la asesoría de seguridad.
|
||||
|
||||
6. Haga clic en **Agregar**.
|
||||
|
||||
|
||||
## Información adicional
|
||||
|
||||
- "[Niveles de permiso para avisos de seguridad de repositorios](/code-security/repository-security-advisories/permission-levels-for-repository-security-advisories)"
|
||||
- "[Colaboración en una bifurcación privada temporal para resolver una vulnerabilidad de seguridad del repositorio](/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability)"
|
||||
- "[Eliminación de un colaborador de un aviso de seguridad del repositorio](/code-security/repository-security-advisories/removing-a-collaborator-from-a-repository-security-advisory)".
|
||||
@@ -1,90 +0,0 @@
|
||||
---
|
||||
title: Colaboración en una bifurcación privada temporal para resolver una vulnerabilidad de seguridad del repositorio
|
||||
intro: Puedes crear una bifurcación privada temporal para colaborar de manera privada en la resolución de una vulnerabilidad de seguridad en tu repositorio.
|
||||
redirect_from:
|
||||
- /articles/collaborating-in-a-temporary-private-fork-to-resolve-a-security-vulnerability
|
||||
- /github/managing-security-vulnerabilities/collaborating-in-a-temporary-private-fork-to-resolve-a-security-vulnerability
|
||||
- /code-security/security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-security-vulnerability
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
type: how_to
|
||||
topics:
|
||||
- Security advisories
|
||||
- Vulnerabilities
|
||||
- Collaboration
|
||||
- Forks
|
||||
shortTitle: Temporary private forks
|
||||
ms.openlocfilehash: c03892c3ad1bd7345a7a066c9a9564858db4b84d
|
||||
ms.sourcegitcommit: ac00e2afa6160341c5b258d73539869720b395a4
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: es-ES
|
||||
ms.lasthandoff: 09/09/2022
|
||||
ms.locfileid: '147878540'
|
||||
---
|
||||
{% data reusables.security-advisory.repository-level-advisory-note %}
|
||||
|
||||
## Prerrequisitos
|
||||
|
||||
Antes de que puedas colaborar en una bifurcación privada temporal, debes crear un borrador de asesoría de seguridad. Para más información, vea "[Creación de un aviso de seguridad de repositorio](/code-security/repository-security-advisories/creating-a-repository-security-advisory)".
|
||||
|
||||
## Crear una bifurcación privada temporal
|
||||
|
||||
Cualquier persona con permisos de administración para un aviso de seguridad puede crear una bifurcación privada temporal.
|
||||
|
||||
Para garantizar la seguridad de la información sobre vulnerabilidades, las integraciones, entre las que se incluye CI, no pueden acceder a las bifurcaciones privadas temporales.
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} {% data reusables.repositories.sidebar-advisories %}
|
||||
4. En la lista de "Asesorías de Seguridad", da clic en aquella en la cual desees crear una bifurcación privada temporal.
|
||||
|
||||
5. Haga clic en **Nueva bifurcación privada temporal**.
|
||||
|
||||
|
||||
## Añadir colaboradores a una bifurcación privada temporal
|
||||
|
||||
Cualquiera con permisos de administrador en una asesoría de seguridad puede añadir colaboradores adicionales a la misma, y estos pueden acceder a la bifurcación privada temporal. Para más información, vea "[Adición de un colaborador a un aviso de seguridad de repositorio](/code-security/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory)".
|
||||
|
||||
## Agregar cambios a una bifurcación privada temporal
|
||||
|
||||
Cualquier persona con permisos de escritura para un aviso de seguridad puede agregar cambios a una bifurcación privada temporal.
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} {% data reusables.repositories.sidebar-advisories %}
|
||||
4. En la lista de "Asesorías de Seguridad", da clic sobre aquella en la que quieras añadir cambios.
|
||||
|
||||
5. Agrega tus cambios en {% data variables.product.product_name %} o localmente:
|
||||
- Para añadir cambios en {% data variables.product.product_name %}, debajo de "Añadir cambios a este aviso", haga clic en **la bifurcación privada temporal**. Luego, crea una nueva rama y edita los archivos. Para más información, vea "[Creación y eliminación de ramas dentro del repositorio](/articles/creating-and-deleting-branches-within-your-repository)" y "[Edición de archivos](/repositories/working-with-files/managing-files/editing-files)".
|
||||
- Para añadir cambios localmente, sigue las instrucciones descritas en "Clonar y crear una nueva rama" y "Haz tus cambios, posteriormente, súbelos".
|
||||
|
||||
|
||||
## Crear una solicitud de extracción desde una bifurcación privada temporal
|
||||
|
||||
Cualquier persona con permisos de escritura para un aviso de seguridad puede crear una solicitud de extracción desde una bifurcación privada temporal.
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} {% data reusables.repositories.sidebar-advisories %}
|
||||
4. En la lista de "Asesorías de Seguridad", da clic sobre aquella en la que desees crear una solicitud de extracción.
|
||||
|
||||
5. A la derecha del nombre de la rama, haga clic en **Comparar y solicitud de incorporación de cambios**.
|
||||
 {% data reusables.repositories.pr-title-description %} {% data reusables.repositories.create-pull-request %}
|
||||
|
||||
{% data reusables.repositories.merge-all-pulls-together %} Para más información, vea "[Combinación de cambios en un aviso de seguridad](#merging-changes-in-a-security-advisory)".
|
||||
|
||||
## Fusionar cambios en una asesoría de seguridad
|
||||
|
||||
Cualquiera con permisos de administrador en una asesoría de seguridad puede fusionar los cambios en la misma.
|
||||
|
||||
{% data reusables.repositories.merge-all-pulls-together %}
|
||||
|
||||
Antes de que puedas fusionar cambios en una asesoría de seguridad, cada solicitud de extracción abierta en la bifurcación privada temporal debe ser fusionable. No puede haber conflictos de fusión, y se deben cumplir los requisitos de protección de la rama. Para garantizar la seguridad de la información sobre las vulnerabilidades, las verificaciones de estado no ejecutan solicitudes de extracción en bifurcaciones privadas temporales. Para más información, vea "[Acerca de las ramas protegidas](/articles/about-protected-branches)".
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} {% data reusables.repositories.sidebar-advisories %}
|
||||
4. En el listado de "Asesorías de Seguridad", da clic sobre aquella que tiene los cambios que quieras fusionar.
|
||||
|
||||
5. Para combinar todas las solicitudes de incorporación de cambios abiertas en la bifurcación privada temporal, haga clic en **Combinar solicitudes de incorporación de cambios**.
|
||||
|
||||
|
||||
Después de que fusiones cambios en una asesoría de seguridad, puedes publicarla para alertar a tu comunidad sobre las vulnerabilidades de seguridad en versiones previas de tu proyecto. Para más información, vea "[Publicación de un aviso de seguridad de repositorio](/code-security/repository-security-advisories/publishing-a-repository-security-advisory)".
|
||||
|
||||
## Información adicional
|
||||
|
||||
- "[Niveles de permiso para avisos de seguridad de repositorios](/code-security/repository-security-advisories/permission-levels-for-repository-security-advisories)"
|
||||
- "[Publicación de un aviso de seguridad de repositorio](/code-security/repository-security-advisories/publishing-a-repository-security-advisory)"
|
||||
@@ -1,44 +0,0 @@
|
||||
---
|
||||
title: Creación de un aviso de seguridad de repositorio
|
||||
intro: Puedes crear un borrador de asesoría de seguridad para debatir en privado y arreglar una vulnerabilidad de seguridad en tu proyecto de código abierto.
|
||||
redirect_from:
|
||||
- /articles/creating-a-maintainer-security-advisory
|
||||
- /github/managing-security-vulnerabilities/creating-a-maintainer-security-advisory
|
||||
- /github/managing-security-vulnerabilities/creating-a-security-advisory
|
||||
- /code-security/security-advisories/creating-a-security-advisory
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
type: how_to
|
||||
topics:
|
||||
- Security advisories
|
||||
- Vulnerabilities
|
||||
shortTitle: Create repository advisories
|
||||
ms.openlocfilehash: d4b47f84b20873e97b18106448b768288fff3039
|
||||
ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: es-ES
|
||||
ms.lasthandoff: 09/10/2022
|
||||
ms.locfileid: '145119394'
|
||||
---
|
||||
Cualquier usuario con permisos de administrador puede crear un aviso de seguridad.
|
||||
|
||||
{% data reusables.security-advisory.security-researcher-cannot-create-advisory %}
|
||||
|
||||
## Creación de un aviso de seguridad
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} {% data reusables.repositories.sidebar-advisories %}
|
||||
4. Haga clic en **New draft security advisory**.
|
||||
|
||||
5. Escribe un título para tu aviso de seguridad.
|
||||
{% data reusables.repositories.security-advisory-edit-details %} {% data reusables.repositories.security-advisory-edit-severity %} {% data reusables.repositories.security-advisory-edit-cwe-cve %} {% data reusables.repositories.security-advisory-edit-description %}
|
||||
11. Haga clic en **Create draft security advisory**.
|
||||
|
||||
|
||||
## Pasos siguientes
|
||||
|
||||
- Comentar en el borrador de asesoría de seguridad para debatir sobre la vulnerabilidad con tu equipo.
|
||||
- Añadir colaboradores a la asesoría de seguridad. Para obtener más información, consulte "[Adición de un colaborador a un aviso de seguridad de repositorio](/code-security/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory)".
|
||||
- Colaborar en privado para solucionar la vulnerabilidad en una bifurcación privada temporaria. Para más información, vea "[Colaboración en una bifurcación privada temporal para resolver una vulnerabilidad de seguridad del repositorio](/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability)".
|
||||
- Agregar individuos que deberían recibir crédito por contribuir con la asesoría de seguridad. Para más información, vea "[Edición de un aviso de seguridad de repositorio](/code-security/repository-security-advisories/editing-a-repository-security-advisory#about-credits-for-security-advisories)".
|
||||
- Publicar la asesoría de seguridad para notificar a tu comunidad sobre la vulnerabilidad de seguridad en cuestión. Para más información, vea "[Publicación de un aviso de seguridad de repositorio](/code-security/repository-security-advisories/publishing-a-repository-security-advisory)".
|
||||
@@ -1,48 +0,0 @@
|
||||
---
|
||||
title: Edición de un aviso de seguridad de repositorio
|
||||
intro: Puedes editar los metadatos y la descripción de una asesoría de seguridad de repositorio si necesitas actualizar los detalles o corregir los errores en esta.
|
||||
redirect_from:
|
||||
- /github/managing-security-vulnerabilities/editing-a-security-advisory
|
||||
- /code-security/security-advisories/editing-a-security-advisory
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
type: how_to
|
||||
topics:
|
||||
- Security advisories
|
||||
- Vulnerabilities
|
||||
shortTitle: Edit repository advisories
|
||||
ms.openlocfilehash: 2ea2f588374d83be677589b4f3bf4e74a7fc6e91
|
||||
ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: es-ES
|
||||
ms.lasthandoff: 09/05/2022
|
||||
ms.locfileid: '145119386'
|
||||
---
|
||||
Los usuarios con permisos de administrador para aviso de seguridad pueden editarlo.
|
||||
|
||||
{% data reusables.security-advisory.repository-level-advisory-note %}
|
||||
|
||||
## Acerca de los créditos para las asesorías de seguridad
|
||||
|
||||
Puedes dar crédito a las personas que ayudaron a descubrir, reportar, o arreglar una vulnerabilidad de seguridad. Si le das crédito a alguien, ellos pueden elegir aceptarlo o declinarlo.
|
||||
|
||||
Si alguien acepta el crédito, el nombre de usuario de la persona aparecerá en la sección "Créditos" de la asesoría de seguridad. Cualquiera con acceso de lectura al repositorio puede ver la asesoría y las personas que aceptaron el crédito por ella.
|
||||
|
||||
Si crees que se te debería dar crédito por alguna asesoría de seguridad, por favor, contacta a la persona que la creó y pídele que edite la asesoría para incluir tu crédito. Solo el creador de la asesoría te puede dar crédito, asi que, por favor, no contactes al Soporte de GitHub pidiendo crédito para alguna asesoría de seguridad.
|
||||
|
||||
## Editar una asesoría de seguridad
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} {% data reusables.repositories.sidebar-advisories %}
|
||||
4. En el listado de "Asesorías de Seguridad", da clic en aquella que quieras editar.
|
||||
5. En la esquina superior derecha de los detalles del aviso de seguridad, haga clic en {% octicon "pencil" aria-label="The edit icon" %}.
|
||||
 {% data reusables.repositories.security-advisory-edit-details %} {% data reusables.repositories.security-advisory-edit-severity %} {% data reusables.repositories.security-advisory-edit-cwe-cve %} {% data reusables.repositories.security-advisory-edit-description %}
|
||||
11. Opcionalmente, puedes editar los "Créditos" para la asesoría de seguridad.
|
||||
|
||||
12. Haga clic en **Actualizar aviso de seguridad**.
|
||||
|
||||
13. Las personas listadas en la sección de "Créditos" recibirán una notificación web o por correo electrónico que los invita a aceptar el crédito. Si la persona acepta, su nombre de usuario estará visible al público una vez que la asesoría de seguridad se publique.
|
||||
|
||||
## Información adicional
|
||||
|
||||
- "[Retirada de un aviso de seguridad de repositorio](/code-security/repository-security-advisories/withdrawing-a-repository-security-advisory)"
|
||||
@@ -1,36 +0,0 @@
|
||||
---
|
||||
title: Administrar las advertencias de seguridad de vulnerabilidades en tu proyecto
|
||||
shortTitle: Repository security advisories
|
||||
intro: 'Debate, arregla y divulga las vulnerabilidades de seguridad en tus repositorios utilizando asesorías de seguridad de repositorios.'
|
||||
redirect_from:
|
||||
- /articles/managing-security-vulnerabilities-in-your-project
|
||||
- /github/managing-security-vulnerabilities/managing-security-vulnerabilities-in-your-project
|
||||
- /code-security/security-advisories
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
topics:
|
||||
- Security advisories
|
||||
- Vulnerabilities
|
||||
- Repositories
|
||||
- CVEs
|
||||
children:
|
||||
- /about-coordinated-disclosure-of-security-vulnerabilities
|
||||
- /about-github-security-advisories-for-repositories
|
||||
- /permission-levels-for-repository-security-advisories
|
||||
- /creating-a-repository-security-advisory
|
||||
- /adding-a-collaborator-to-a-repository-security-advisory
|
||||
- /removing-a-collaborator-from-a-repository-security-advisory
|
||||
- /collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability
|
||||
- /publishing-a-repository-security-advisory
|
||||
- /editing-a-repository-security-advisory
|
||||
- /withdrawing-a-repository-security-advisory
|
||||
- /best-practices-for-writing-repository-security-advisories
|
||||
ms.openlocfilehash: 43efe7ceaf307da4a8a7c02c45f744a4967b05b0
|
||||
ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: es-ES
|
||||
ms.lasthandoff: 09/10/2022
|
||||
ms.locfileid: '145119385'
|
||||
---
|
||||
|
||||
@@ -1,50 +0,0 @@
|
||||
---
|
||||
title: Niveles de permiso para avisos de seguridad de repositorios
|
||||
intro: Las acciones que puedes tomar en una asesoría de seguridad de repositorio dependen de si tienes permisos de administrador o de escritura en esta.
|
||||
redirect_from:
|
||||
- /articles/permission-levels-for-maintainer-security-advisories
|
||||
- /github/managing-security-vulnerabilities/permission-levels-for-maintainer-security-advisories
|
||||
- /github/managing-security-vulnerabilities/permission-levels-for-security-advisories
|
||||
- /code-security/security-advisories/permission-levels-for-security-advisories
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
type: reference
|
||||
topics:
|
||||
- Security advisories
|
||||
- Vulnerabilities
|
||||
- Permissions
|
||||
shortTitle: Permission levels
|
||||
ms.openlocfilehash: 9c2ad0d30b98b79786df09a224766bd826cb84f6
|
||||
ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: es-ES
|
||||
ms.lasthandoff: 09/05/2022
|
||||
ms.locfileid: '145119393'
|
||||
---
|
||||
Este artículo solo se aplica a los avisos de seguridad de nivel de repositorio. Cualquiera puede contribuir a los avisos de seguridad globales en {% data variables.product.prodname_advisory_database %} en [github.com/advisories](https://github.com/advisories). Las ediciones a las asesorías globales no cambiarán ni afectarán la forma en la que se muestra la asesoría en el repositorio. Para más información, vea "[Edición de avisos de seguridad en {% data variables.product.prodname_advisory_database %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/editing-security-advisories-in-the-github-advisory-database)".
|
||||
|
||||
## Introducción sobre los permisos
|
||||
|
||||
{% data reusables.repositories.security-advisory-admin-permissions %} Para más información sobre cómo agregar un colaborador a un aviso de seguridad, vea "[Adición de un colaborador a un aviso de seguridad de repositorio](/code-security/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory)".
|
||||
|
||||
Acción | Permisos de escritura | Permisos de administrador |
|
||||
------ | ----------------- | ----------------- |
|
||||
Ver un borrador de asesoría de seguridad | x | x |
|
||||
Agregar colaboradores al aviso de seguridad (vea "[Adición de un colaborador a un aviso de seguridad de repositorio](/code-security/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory)") | | x |
|
||||
Editar y borrar cualquier comentario en la asesoría de seguridad | x | x |
|
||||
Crear una bifurcación privada temporal en el aviso de seguridad (vea "[Colaboración en una bifurcación privada temporal para resolver una vulnerabilidad de seguridad del repositorio](/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability)") | | x |
|
||||
Agregar cambios a una bifurcación privada temporal en el aviso de seguridad (vea "[Colaboración en una bifurcación privada temporal para resolver una vulnerabilidad de seguridad del repositorio](/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability)") | x | x |
|
||||
Crear solicitudes de incorporación de cambios en una bifurcación privada temporal (vea "[Colaboración en una bifurcación privada temporal para resolver una vulnerabilidad de seguridad del repositorio](/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability)") | x | x |
|
||||
Combinar cambios en el aviso de seguridad (vea "[Colaboración en una bifurcación privada temporal para resolver una vulnerabilidad de seguridad del repositorio](/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability)") | | x |
|
||||
Agregar y editar metadatos en el aviso de seguridad (vea "[Publicación de un aviso de seguridad de repositorio](/code-security/repository-security-advisories/publishing-a-repository-security-advisory)") | x | x |
|
||||
Agregar y quitar créditos en el aviso de seguridad (vea "[Edición de un aviso de seguridad de repositorio](/code-security/repository-security-advisories/editing-a-repository-security-advisory)") | x | x |
|
||||
Cerrar el borrador de la asesoría de seguridad | | x |
|
||||
Publicar el aviso de seguridad (vea "[Publicación de un aviso de seguridad de repositorio](/code-security/repository-security-advisories/publishing-a-repository-security-advisory)") | | x |
|
||||
|
||||
## Información adicional
|
||||
|
||||
- "[Adición de un colaborador a un aviso de seguridad de repositorio](/code-security/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory)"
|
||||
- "[Colaboración en una bifurcación privada temporal para resolver una vulnerabilidad de seguridad del repositorio](/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability)"
|
||||
- "[Eliminación de un colaborador de un aviso de seguridad del repositorio](/code-security/repository-security-advisories/removing-a-collaborator-from-a-repository-security-advisory)"
|
||||
- "[Retirada de un aviso de seguridad de repositorio](/code-security/repository-security-advisories/withdrawing-a-repository-security-advisory)"
|
||||
@@ -1,101 +0,0 @@
|
||||
---
|
||||
title: Publicación de un aviso de seguridad de repositorio
|
||||
intro: Puedes publicar una asesoría de seguridad para alertar a tu comunidad sobre la vulnerabilidad de seguridad en tu proyecto.
|
||||
redirect_from:
|
||||
- /articles/publishing-a-maintainer-security-advisory
|
||||
- /github/managing-security-vulnerabilities/publishing-a-maintainer-security-advisory
|
||||
- /github/managing-security-vulnerabilities/publishing-a-security-advisory
|
||||
- /code-security/security-advisories/publishing-a-security-advisory
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
type: how_to
|
||||
topics:
|
||||
- Security advisories
|
||||
- Vulnerabilities
|
||||
- CVEs
|
||||
- Repositories
|
||||
shortTitle: Publish repository advisories
|
||||
ms.openlocfilehash: f3e3bfdb6b44ec1c86bb903c66271b854f4fb041
|
||||
ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: es-ES
|
||||
ms.lasthandoff: 09/05/2022
|
||||
ms.locfileid: '145119378'
|
||||
---
|
||||
<!--Marketing-LINK: From /features/security/software-supply-chain page "Publishing a security advisory".-->
|
||||
|
||||
Cualquiera con permisos de administrador en una asesoría de seguridad puede publicarla.
|
||||
|
||||
{% data reusables.security-advisory.repository-level-advisory-note %}
|
||||
|
||||
## Prerrequisitos
|
||||
|
||||
Antes de que puedas publicar una asesoría de seguridad o solicitar un número de identificación de CVE, debes crear un borrador de asesoría de seguridad y proporcionar información acerca de las versiones de tu proyecto que se vieron afectadas por la vulnerabilidad de seguridad. Para más información, vea "[Creación de un aviso de seguridad de repositorio](/code-security/repository-security-advisories/creating-a-repository-security-advisory)".
|
||||
|
||||
Si creaste una asesoría de seguridad pero no has proporcionado detalles sobre las versiones de tu proyecto que afectó la vulnerabilidad, puedes editarla. Para más información, vea "[Edición de un aviso de seguridad de repositorio](/code-security/repository-security-advisories/editing-a-repository-security-advisory)".
|
||||
|
||||
## Acerca de publicar una asesoría de seguridad
|
||||
|
||||
Cuando publicas una asesoría de seguridad, notificas a tu comunidad acerca de la vulnerabilidad de seguridad que se dirige en dicha asesoría. El publicar una asesoría de seguridad facilita a tu comunidad el actualizar las dependencias de los paquetes y el investigar el impacto de la vulnerabilidad de seguridad.
|
||||
|
||||
{% data reusables.repositories.security-advisories-republishing %}
|
||||
|
||||
Antes de que publiques una asesoría de seguridad, puedes hacer una colaboración privada para arreglar la vulnerabilidad en una bifurcación privada. Para más información, vea "[Colaboración en una bifurcación privada temporal para resolver una vulnerabilidad de seguridad del repositorio](/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability)".
|
||||
|
||||
{% warning %}
|
||||
|
||||
**Advertencia**: Siempre que sea posible, debe agregar una versión de corrección a un aviso de seguridad antes de publicar el aviso. Si no lo haces, la asesoría se publicará sin una versión corregida y el {% data variables.product.prodname_dependabot %} alertará a tus usuarios sobre este problema sin ofrecer una versión segura para actualizarse.
|
||||
|
||||
Te recomendamos seguir estos pasos en estas situaciones:
|
||||
|
||||
- Si una versión corregida está disponible inminentemente y puedes hacerlo, espera para divulgar el problema cuando la corrección ya esté lista.
|
||||
- Si aún se está desarrollando una versión corregida y no se encuentra disponible, menciónalo en la asesoría y edítala después de publicarla.
|
||||
- Si no planeas corregir el problema, aclara esto en la asesoría para que tus usuarios no te contacten para preguntar cuándo crearás la corrección. En este caso, es útil incluir pasos que puedan seguir los usuarios para mitigar el problema.
|
||||
|
||||
{% endwarning %}
|
||||
|
||||
Cuando publicas un borrador de asesoría desde un repositorio público, todos pueden ver:
|
||||
|
||||
- La versión actual de los datos de la asesoría.
|
||||
- Cualquier asesoría atribuye que los usuarios acreditados han aceptado.
|
||||
|
||||
{% note %}
|
||||
|
||||
**Nota**: El público general nunca tendrá acceso al historial de edición del aviso y solo verá la versión publicada.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
Después de que publicas una asesoría de seguridad, la URL de la misa permanecerá tal como antes de publicarla. Cualquiera con acceso de lectura al repositorio puede verla. Los colaboradores de la asesoría de seguridad pueden seguir viendo las conversaciones pasadas, incluyendo el flujo completo de comentarios, en la asesoría de seguridad a menos de que alguien con permisos administrativos elimine al colaborador de la asesoría de seguridad.
|
||||
|
||||
Si necesitas actualizar o corregir información en una asesoría de seguridad que hayas publicado, puedes editarla. Para más información, vea "[Edición de un aviso de seguridad de repositorio](/code-security/repository-security-advisories/editing-a-repository-security-advisory)".
|
||||
|
||||
## Publicar una asesoría de seguridad
|
||||
|
||||
El publicar una asesoría de seguridad borra la bifurcación temporal privada para la misma.
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} {% data reusables.repositories.sidebar-advisories %}
|
||||
4. En el listado de "Asesorías de Seguridad", da clic sobre la que quieras publicar.
|
||||
|
||||
5. En la parte inferior de la página, haga clic en **Publish advisory**.
|
||||
|
||||
|
||||
## {% data variables.product.prodname_dependabot_alerts %} para las asesorías de seguridad publicadas
|
||||
|
||||
{% data reusables.repositories.github-reviews-security-advisories %}
|
||||
|
||||
## Solicitar un número de identificación de CVE (Opcional)
|
||||
|
||||
{% data reusables.repositories.request-security-advisory-cve-id %} Para más información, vea "[Acerca de {% data variables.product.prodname_security_advisories %} para repositorios](/code-security/repository-security-advisories/about-github-security-advisories-for-repositories#cve-identification-numbers)".
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} {% data reusables.repositories.sidebar-advisories %}
|
||||
4. En el listado de "Asesorías de Seguridad", da clic en aquella para la cual quieras solicitar un número de identificación de CVE.
|
||||
|
||||
5. Use el menú desplegable **Publish advisory** y haga clic en **Request CVE**.
|
||||
|
||||
6. Haga clic en **Request CVE**.
|
||||
|
||||
|
||||
## Información adicional
|
||||
|
||||
- "[Retirada de un aviso de seguridad de repositorio](/code-security/repository-security-advisories/withdrawing-a-repository-security-advisory)"
|
||||
@@ -1,42 +0,0 @@
|
||||
---
|
||||
title: Eliminación de un colaborador de un aviso de seguridad del repositorio
|
||||
intro: 'Cuando eliminas a un colaborador de una asesoría de seguridad de repositorio, este pierde el acceso de lectura y escritura en el debate y los metadatos de aquella.'
|
||||
redirect_from:
|
||||
- /github/managing-security-vulnerabilities/removing-a-collaborator-from-a-security-advisory
|
||||
- /code-security/security-advisories/removing-a-collaborator-from-a-security-advisory
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
type: how_to
|
||||
topics:
|
||||
- Security advisories
|
||||
- Vulnerabilities
|
||||
- Collaboration
|
||||
shortTitle: Remove collaborators
|
||||
ms.openlocfilehash: ced0edd0614304c0d33ddd40dce3c6a24a9ffcfd
|
||||
ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: es-ES
|
||||
ms.lasthandoff: 09/10/2022
|
||||
ms.locfileid: '145119361'
|
||||
---
|
||||
Las personas con permisos administrativos en una asesoría de seguridad pueden eliminar a los colaboradores de la misma.
|
||||
|
||||
{% data reusables.security-advisory.repository-level-advisory-note %}
|
||||
|
||||
## Eliminar un colaborador de una asesoría de seguridad
|
||||
|
||||
{% data reusables.repositories.security-advisory-collaborators-public-repositories %}
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} {% data reusables.repositories.sidebar-advisories %}
|
||||
4. En el listado de "Asesorías de Seguridad", da clic sobre aquella en la que quieras eliminar a algún colaborador.
|
||||
|
||||
5. En el lado derecho de la página, debajo de "Colaboradores", encuentra el nombre del usuario o equipo al que quieres eliminar de la asesoría de seguridad.
|
||||
|
||||
6. Junto al colaborador que quiera quitar, haga clic en el icono **X**.
|
||||
|
||||
|
||||
## Información adicional
|
||||
|
||||
- "[Niveles de permiso para avisos de seguridad de repositorios](/code-security/repository-security-advisories/permission-levels-for-repository-security-advisories)"
|
||||
- "[Adición de un colaborador a un aviso de seguridad de repositorio](/code-security/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory)"
|
||||
@@ -1,28 +0,0 @@
|
||||
---
|
||||
title: Retirada de un aviso de seguridad de repositorio
|
||||
intro: Puedes retirar una asesoría de seguridad de repositorio que hayas publicado.
|
||||
redirect_from:
|
||||
- /github/managing-security-vulnerabilities/withdrawing-a-security-advisory
|
||||
- /code-security/security-advisories/withdrawing-a-security-advisory
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
type: how_to
|
||||
topics:
|
||||
- Security advisories
|
||||
- Vulnerabilities
|
||||
shortTitle: Withdraw repository advisories
|
||||
ms.openlocfilehash: 1d85afddaadbd25c5b24ab945dac998b7842ae23
|
||||
ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: es-ES
|
||||
ms.lasthandoff: 09/10/2022
|
||||
ms.locfileid: '145119329'
|
||||
---
|
||||
{% data reusables.security-advisory.repository-level-advisory-note %}
|
||||
|
||||
Si publicas una asesoría de seguridad por error, puedes retirarla contactando a {% data variables.contact.contact_support %}.
|
||||
|
||||
## Información adicional
|
||||
|
||||
- "[Edición de un aviso de seguridad de repositorio](/code-security/repository-security-advisories/editing-a-repository-security-advisory)"
|
||||
@@ -67,17 +67,23 @@ The security overview displays active alerts raised by security features. If the
|
||||
|
||||
At the organization-level, the security overview displays aggregate and repository-specific security information for repositories owned by your organization. You can filter information by security features at the organization-level.
|
||||
|
||||
Organization owners and security managers for organizations have access to the organization-level security overview. {% ifversion ghec or ghes > 3.6 or ghae > 3.6 %}Organization members can access the organization-level security overview to view results for repositories where they have admin privileges or have been granted access to security alerts. For more information on managing security alert access, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)".{% endif %}
|
||||
|
||||
{% ifversion ghec or ghes > 3.4 or ghae > 3.4 %}
|
||||
### About the enterprise-level security overview
|
||||
At the enterprise-level, the security overview displays aggregate and repository-specific security information for your enterprise. You can view repositories owned by your enterprise that have security alerts, view all security alerts, or security feature-specific alerts from across your enterprise.
|
||||
|
||||
Organization owners and security managers for organizations in your enterprise also have limited access to the enterprise-level security overview. They can only view repositories and alerts for the organizations that they have full access to.
|
||||
Organization owners and security managers for organizations in your enterprise have access to the enterprise-level security overview. They can view repositories and alerts for the organizations that they have full access to.
|
||||
|
||||
Enterprise owners can only see alerts for organizations that they are an owner or a security manager of.{% ifversion ghec or ghes > 3.5 or ghae > 3.5 %} Enterprise owners can join an organization as an organization owner to see all of its alerts in the enterprise-level security overview. For more information, see "[Managing your role in an organization owned by your enterprise](/admin/user-management/managing-organizations-in-your-enterprise/managing-your-role-in-an-organization-owned-by-your-enterprise)."{% endif %}
|
||||
|
||||
{% elsif fpt %}
|
||||
### About the enterprise-level security overview
|
||||
At the enterprise-level, the security overview displays aggregate and repository-specific information for an enterprise. For more information, see "[About the enterprise-level security overview](/enterprise-cloud@latest/code-security/security-overview/about-the-security-overview#about-the-enterprise-level-security-overview)" in the {% data variables.product.prodname_ghe_cloud %} documentation.
|
||||
{% endif %}
|
||||
|
||||
{% ifversion ghes < 3.7 or ghae < 3.7 %}
|
||||
### About the team-level security overview
|
||||
At the team-level, the security overview displays repository-specific security information for repositories that the team has admin privileges for. For more information, see "[Managing team access to an organization repository](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository)."
|
||||
{% endif %}
|
||||
{% endif %}
|
||||
|
||||
@@ -30,7 +30,7 @@ If you publish a container image to {% data variables.packages.prodname_ghcr_or_
|
||||
|
||||
By default, when you publish a container image to {% data variables.packages.prodname_ghcr_or_npm_registry %}, the image inherits the access setting of the repository from which the image was published. For example, if the repository is public, the image is also public. If the repository is private, the image is also private, but is accessible from the repository.
|
||||
|
||||
This behavior is controlled by the **Inherit access from repo** option. **Inherit access from repo** is selected by default when publishing via {% data variables.product.prodname_actions %}, but not when publishing directly to {% data variables.packages.prodname_ghcr_or_npm_registry %} using a % data variables.product.pat_generic %}.
|
||||
This behavior is controlled by the **Inherit access from repo** option. **Inherit access from repo** is selected by default when publishing via {% data variables.product.prodname_actions %}, but not when publishing directly to {% data variables.packages.prodname_ghcr_or_npm_registry %} using a {% data variables.product.pat_generic %}.
|
||||
|
||||
If the **Inherit access from repo** option was not selected when the image was published, you can manually add the repository to the published container image's access controls. For more information, see "[Configuring a package's access control and visibility](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility#inheriting-access-for-a-container-image-from-a-repository)."
|
||||
|
||||
|
||||
@@ -15,6 +15,8 @@ includeGuides:
|
||||
- /codespaces/setting-up-your-project-for-codespaces/setting-up-your-python-project-for-codespaces
|
||||
- /codespaces/setting-up-your-project-for-codespaces/setting-up-your-dotnet-project-for-codespaces
|
||||
- /codespaces/setting-up-your-project-for-codespaces/setting-up-your-java-project-for-codespaces
|
||||
- /codespaces/setting-up-your-project-for-codespaces/setting-a-minimum-specification-for-codespace-machines
|
||||
- /codespaces/setting-up-your-project-for-codespaces/automatically-opening-files-in-the-codespaces-for-a-repository
|
||||
- /codespaces/setting-up-your-project-for-codespaces/adding-a-codespaces-badge
|
||||
- /codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project
|
||||
- /codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account
|
||||
|
||||
@@ -17,6 +17,7 @@ children:
|
||||
- /setting-up-your-java-project-for-codespaces
|
||||
- /setting-up-your-python-project-for-codespaces
|
||||
- /setting-a-minimum-specification-for-codespace-machines
|
||||
- /automatically-opening-files-in-the-codespaces-for-a-repository
|
||||
- /adding-a-codespaces-badge
|
||||
ms.openlocfilehash: 1e172243dc351f0a173c8624b66914e1c3795495
|
||||
ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Configurar una especificación mínima para las máquinas de los codespaces
|
||||
title: Setting a minimum specification for codespace machines
|
||||
shortTitle: Set a minimum machine spec
|
||||
intro: 'Puedes evitar que los tipos de máquina con recursos insuficientes se usen en los {% data variables.product.prodname_github_codespaces %} de tu repositorio.'
|
||||
intro: 'You can avoid under-resourced machine types being used for {% data variables.product.prodname_github_codespaces %} for your repository.'
|
||||
permissions: People with write permissions to a repository can create or edit the codespace configuration.
|
||||
versions:
|
||||
fpt: '*'
|
||||
@@ -11,29 +11,24 @@ topics:
|
||||
- Codespaces
|
||||
- Set up
|
||||
product: '{% data reusables.gated-features.codespaces %}'
|
||||
ms.openlocfilehash: 368b7c73d13bb0624c9d838ac2d7bb18a2b050e3
|
||||
ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: es-ES
|
||||
ms.lasthandoff: 09/10/2022
|
||||
ms.locfileid: '147880810'
|
||||
---
|
||||
## Información general
|
||||
|
||||
Cada codespace que crees se hospeda en una máquina virtual independiente, y normalmente puedes elegir entre diferentes tipos de máquinas virtuales. Cada tipo de máquina tiene recursos diferentes (CPU, memoria, almacenamiento) y, de forma predeterminada, se usa el tipo de máquina con los recursos mínimos. Para obtener más información, consulte "[Cambio del tipo de máquina para el codespace](/codespaces/customizing-your-codespace/changing-the-machine-type-for-your-codespace#about-machine-types)".
|
||||
## Overview
|
||||
|
||||
Si tu proyecto necesita cierto nivel de potencia de cómputo, puedes configurar {% data variables.product.prodname_github_codespaces %} para que solo los tipos de máquina que cumplan con estos requisitos se puedan usar de forma predeterminada o los puedan seleccionar los usuarios. Esta configuración se realiza en un archivo `devcontainer.json`.
|
||||
Each codespace that you create is hosted on a separate virtual machine, and you can usually choose from different types of virtual machines. Each machine type has different resources (processor cores, memory, storage) and, by default, the machine type with the least resources is used. For more information, see "[Changing the machine type for your codespace](/codespaces/customizing-your-codespace/changing-the-machine-type-for-your-codespace#about-machine-types)."
|
||||
|
||||
If your project needs a certain level of compute power, you can configure {% data variables.product.prodname_github_codespaces %} so that only machine types that meet these requirements can be used by default, or selected by users. You configure this in a `devcontainer.json` file.
|
||||
|
||||
{% note %}
|
||||
|
||||
**Importante:** El acceso a algunos tipos de máquina puede estar restringido en el nivel de organización. Habitualmente, esto se hace para prevenir que las personas elijan máquinas con recursos superiores, las cuales se cobran en tazas más altas. Si tu repositorio se ve afectado por la política de tipos de máquina a nivel organizacional, debes asegurarte de que no configures una especificación mínima que impida que las personas seleccionen los tipos de máquina disponibles que necesitan. Para obtener más información, consulte "[Restringir el acceso a los tipos de máquina](/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types)".
|
||||
**Important:** Access to some machine types may be restricted at the organization level. Typically this is done to prevent people choosing higher resourced machines that are billed at a higher rate. If your repository is affected by an organization-level policy for machine types you should make sure you don't set a minimum specification that would leave no available machine types for people to choose. For more information, see "[Restricting access to machine types](/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types)."
|
||||
|
||||
{% endnote %}
|
||||
|
||||
## Configurar una especificación de máquina mínima
|
||||
## Setting a minimum machine specification
|
||||
|
||||
1. Los {% data variables.product.prodname_github_codespaces %} del repositorio se configuran en un archivo `devcontainer.json`. Si el repositorio aún no contiene un archivo `devcontainer.json`, agregue uno ahora. Consulta "[Adición de una configuración de contenedor de desarrollo al repositorio](/free-pro-team@latest/codespaces/setting-up-your-project-for-codespaces/setting-up-your-project-for-codespaces)".
|
||||
1. Edite el archivo `devcontainer.json` y agregue una propiedad `hostRequirements` como esta:
|
||||
{% data reusables.codespaces.edit-devcontainer-json %}
|
||||
1. Edit the `devcontainer.json` file, adding the `hostRequirements` property at the top level of the file, within the enclosing JSON object. For example:
|
||||
|
||||
```json{:copy}
|
||||
"hostRequirements": {
|
||||
@@ -43,16 +38,16 @@ Si tu proyecto necesita cierto nivel de potencia de cómputo, puedes configurar
|
||||
}
|
||||
```
|
||||
|
||||
Puede especificar una de las opciones o todas: `cpus`, `memory` y `storage`.
|
||||
You can specify any or all of the options: `cpus`, `memory`, and `storage`.
|
||||
|
||||
Para verificar las especificaciones de los tipos de máquina de {% data variables.product.prodname_github_codespaces %} que actualmente están disponibles para tu repositorio, realiza el proceso de crear un codespace hasta que veas la elección de tipos de máquina. Para obtener más información, consulte "[Crear un codespace](/codespaces/developing-in-codespaces/creating-a-codespace#creating-a-codespace)".
|
||||
To check the specifications of the {% data variables.product.prodname_github_codespaces %} machine types that are currently available for your repository, step through the process of creating a codespace until you see the choice of machine types. For more information, see "[Creating a codespace](/codespaces/developing-in-codespaces/creating-a-codespace#creating-a-codespace)."
|
||||
|
||||
1. Guarda el archivo y confirma tus cambios a la rama requerida del repositorio.
|
||||
1. Save the file and commit your changes to the required branch of the repository.
|
||||
|
||||
Ahora, cuando crees un codespace para esta rama del repositorio y vayas a las opciones de configuración de creación, solo podrás seleccionar tipos de máquina que coincidan con los recursos que especificaste o los excedan.
|
||||
Now when you create a codespace for that branch of the repository, and you go to the creation configuration options, you will only be able to select machine types that match or exceed the resources you've specified.
|
||||
|
||||
|
||||
|
||||
|
||||
## Información adicional
|
||||
## Further reading
|
||||
|
||||
- "[Introducción a los contenedores de desarrollo](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers)"
|
||||
- "[Introduction to dev containers](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers)"
|
||||
|
||||
@@ -142,14 +142,14 @@ You can use `publishConfig` element in the *package.json* file to specify the re
|
||||
{% endif %}
|
||||
```shell
|
||||
"publishConfig": {
|
||||
"registry":"https://{% ifversion fpt or ghec %}npm.pkg.github.com{% else %}npm.HOSTNAME/{% endif %}"
|
||||
"registry": "https://{% ifversion fpt or ghec %}npm.pkg.github.com{% else %}npm.HOSTNAME/{% endif %}"
|
||||
},
|
||||
```
|
||||
{% ifversion ghes %}
|
||||
If your instance has subdomain isolation disabled:
|
||||
```shell
|
||||
"publishConfig": {
|
||||
"registry":"https://HOSTNAME/_registry/npm/"
|
||||
"registry": "https://HOSTNAME/_registry/npm/"
|
||||
},
|
||||
```
|
||||
{% endif %}
|
||||
|
||||
@@ -187,7 +187,7 @@ When you enable branch restrictions, only users, teams, or apps that have been g
|
||||
Optionally, you can apply the same restrictions to the creation of branches that match the rule. For example, if you create a rule that only allows a certain team to push to any branches that contain the word `release`, only members of that team would be able to create a new branch that contains the word `release`.
|
||||
{% endif %}
|
||||
|
||||
You can only give push access to a protected branch, or give permission to create a matching branch, to users, teams, or installed {% data variables.product.prodname_github_apps %} with write access to a repository. People and apps with admin permissions to a repository are always able to push to a protected branch or create a matching branch.
|
||||
You can only give push access to a protected branch, or give permission to create a matching branch, to users, teams, or installed {% data variables.product.prodname_github_apps %} with write access to a repository. People and apps with admin permissions to a repository are always able to push to a protected branch{% ifversion restrict-pushes-create-branch %} or create a matching branch{% endif %}.
|
||||
|
||||
### Allow force pushes
|
||||
|
||||
|
||||
@@ -51,6 +51,12 @@ When you transfer a repository, its issues, pull requests, wiki, stars, and watc
|
||||
$ git remote set-url origin NEW_URL
|
||||
```
|
||||
|
||||
{% warning %}
|
||||
|
||||
**Warning**: If you create a new repository under your account in the future, do not reuse the original name of the transferred repository. If you do, redirects to the transferred repository will no longer work.
|
||||
|
||||
{% endwarning %}
|
||||
|
||||
- When you transfer a repository from an organization to a personal account, the repository's read-only collaborators will not be transferred. This is because collaborators can't have read-only access to repositories owned by a personal account. For more information about repository permission levels, see "[Permission levels for a personal account repository](/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository)" and "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)."{% ifversion fpt or ghec %}
|
||||
- Sponsors who have access to the repository through a sponsorship tier may be affected. For more information, see "[Adding a repository to a sponsorship tier](/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers#adding-a-repository-to-a-sponsorship-tier)".{% endif %}
|
||||
|
||||
|
||||
@@ -4,15 +4,18 @@ security_advisories:
|
||||
description: 'Using repository security advisories to privately fix a reported vulnerability and get a CVE.'
|
||||
featured_track: '{% ifversion fpt or ghec %}true{% else %}false{% endif %}'
|
||||
guides:
|
||||
- /code-security/repository-security-advisories/about-coordinated-disclosure-of-security-vulnerabilities
|
||||
- /code-security/repository-security-advisories/creating-a-repository-security-advisory
|
||||
- /code-security/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory
|
||||
- /code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability
|
||||
- /code-security/repository-security-advisories/publishing-a-repository-security-advisory
|
||||
- /code-security/repository-security-advisories/editing-a-repository-security-advisory
|
||||
- /code-security/repository-security-advisories/withdrawing-a-repository-security-advisory
|
||||
- /code-security/repository-security-advisories/removing-a-collaborator-from-a-repository-security-advisory
|
||||
- /code-security/repository-security-advisories/best-practices-for-writing-repository-security-advisories
|
||||
- /code-security/security-advisories/repository-security-advisories/about-coordinated-disclosure-of-security-vulnerabilities
|
||||
- /code-security/security-advisories/global-security-advisories/about-the-github-advisory-database
|
||||
- /code-security/security-advisories/global-security-advisories/about-global-security-advisories
|
||||
- /code-security/security-advisories/repository-security-advisories/about-repository-security-advisories
|
||||
- /code-security/security-advisories/repository-security-advisories/creating-a-repository-security-advisory
|
||||
- /code-security/security-advisories/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory
|
||||
- /code-security/security-advisories/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability
|
||||
- /code-security/security-advisories/repository-security-advisories/publishing-a-repository-security-advisory
|
||||
- /code-security/security-advisories/repository-security-advisories/editing-a-repository-security-advisory
|
||||
- /code-security/security-advisories/repository-security-advisories/withdrawing-a-repository-security-advisory
|
||||
- /code-security/security-advisories/repository-security-advisories/removing-a-collaborator-from-a-repository-security-advisory
|
||||
- /code-security/security-advisories/guidance-on-reporting-and-writing/best-practices-for-writing-repository-security-advisories
|
||||
|
||||
# Feature available on dotcom and GHES 3.3+, so articles available on GHAE and earlier GHES hidden to hide the learning track
|
||||
dependabot_alerts:
|
||||
|
||||
@@ -1,9 +1 @@
|
||||
---
|
||||
ms.openlocfilehash: 0ac903914a15eacb9f6db488c4c1cac01a6411e6
|
||||
ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: es-ES
|
||||
ms.lasthandoff: 09/11/2022
|
||||
ms.locfileid: "145092576"
|
||||
---
|
||||
También puedes utilizar {% data variables.product.prodname_security_advisories %} para volver a publicar los detalles de una vulnerabilidad de seguridad que ya has divulgado en otro lugar si copias y pegas los detalles de la vulnerabilidad en una asesoría de seguridad nueva.
|
||||
You can also use repository security advisories to republish the details of a security vulnerability that you have already disclosed elsewhere by copying and pasting the details of the vulnerability into a new security advisory.
|
||||
|
||||
@@ -90,6 +90,8 @@ Google | Google OAuth Refresh Token | google_oauth_refresh_token{% endif %}
|
||||
Grafana | Grafana API Key | grafana_api_key
|
||||
HashiCorp | Terraform Cloud / Enterprise API Token | terraform_api_token
|
||||
HashiCorp | HashiCorp Vault Batch Token | hashicorp_vault_batch_token
|
||||
{%- ifversion fpt or ghec or ghes > 3.8 or ghae > 3.8 %}
|
||||
HashiCorp | HashiCorp Vault Root Service Token | hashicorp_vault_root_service_token{% endif %}
|
||||
HashiCorp | HashiCorp Vault Service Token | hashicorp_vault_service_token
|
||||
Hubspot | Hubspot API Key | hubspot_api_key
|
||||
Intercom | Intercom Access Token | intercom_access_token
|
||||
|
||||
@@ -1,9 +1 @@
|
||||
---
|
||||
ms.openlocfilehash: aa9f7cd0b911ddfc6e144c7c91cecd0374286b13
|
||||
ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: es-ES
|
||||
ms.lasthandoff: 09/10/2022
|
||||
ms.locfileid: "145137530"
|
||||
---
|
||||
Las {% data variables.product.prodname_security_advisories %} permiten a los manenedores de repositorios debatir en privado y corregir vulnerabilidades de seguridad en los proyectos. Después de colaborar en una corrección, los mantenedores de repositorios pueden publicar el aviso de seguridad para revelar públicamente la vulnerabilidad de seguridad a la comunidad del proyecto. Al publicar avisos de seguridad, los mantenedores de repositorios facilitan a su comunidad la actualización de las dependencias de paquetes y la investigación del impacto de las vulnerabilidades de seguridad.
|
||||
Repository security advisories allow repository maintainers to privately discuss and fix a security vulnerability in a project. After collaborating on a fix, repository maintainers can publish the security advisory to publicly disclose the security vulnerability to the project's community. By publishing security advisories, repository maintainers make it easier for their community to update package dependencies and research the impact of the security vulnerabilities.
|
||||
|
||||
@@ -1 +1 @@
|
||||
Organization owners and security managers can access the security overview for organizations{% ifversion ghec or ghes > 3.4 or ghae > 3.4 %} and view their organization's repositories via the enterprise-level security overview. Enterprise owners can use the enterprise-level security overview to view all repositories in their enterprise's organizations{% endif %}. Members of a team can see the security overview for repositories that the team has admin privileges for.
|
||||
{% ifversion not fpt %}Organization owners and security managers can access the organization-level security overview{% ifversion ghec or ghes > 3.4 or ghae > 3.4 %} and view alerts across multiple organizations via the enterprise-level security overview. Enterprise owners can only view repositories and alerts for organizations where they are added as an organization owner or security manager{% endif %}. {% ifversion ghec or ghes > 3.6 or ghae > 3.6 %}Organization members can access the organization-level security overview to view results for repositories where they have admin privileges or have been granted access to security alerts.{% else %}Members of a team can see the security overview for repositories that the team has admin privileges for.{% endif %}{% endif %}
|
||||
|
||||
@@ -161,7 +161,7 @@ For example, to see notifications from the octo-org organization, use `org:octo-
|
||||
|
||||
## {% data variables.product.prodname_dependabot %} custom filters
|
||||
|
||||
{% ifversion fpt or ghec or ghes > 3.2 %}
|
||||
{% ifversion fpt or ghec or ghes %}
|
||||
If you use {% data variables.product.prodname_dependabot %} to keep your dependencies up-to-date, you can use and save these custom filters:
|
||||
- `is:repository_vulnerability_alert` to show notifications for {% data variables.product.prodname_dependabot_alerts %}.
|
||||
- `reason:security_alert` to show notifications for {% data variables.product.prodname_dependabot_alerts %} and security update pull requests.
|
||||
@@ -170,7 +170,7 @@ If you use {% data variables.product.prodname_dependabot %} to keep your depende
|
||||
For more information about {% data variables.product.prodname_dependabot %}, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)."
|
||||
{% endif %}
|
||||
|
||||
{% ifversion ghes < 3.3 or ghae %}
|
||||
{% ifversion ghae %}
|
||||
|
||||
If you use {% data variables.product.prodname_dependabot %} to tell you about insecure dependencies, you can use and save these custom filters to show notifications for {% data variables.product.prodname_dependabot_alerts %}:
|
||||
- `is:repository_vulnerability_alert`
|
||||
|
||||
@@ -24,7 +24,7 @@ Organizations that use {% data variables.product.prodname_ghe_cloud %} can confi
|
||||
To confirm your organization's identity and display a "Verified" badge on your organization profile page, you can verify your organization's domains with {% data variables.product.prodname_dotcom %}. For more information, see "[Verifying or approving a domain for your organization](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization)."
|
||||
{% endif %}
|
||||
|
||||
{% ifversion fpt or ghes > 3.2 or ghec %}
|
||||
{% ifversion fpt or ghes or ghec %}
|
||||
|
||||
{% else %}
|
||||
|
||||
|
||||
@@ -1,56 +1,62 @@
|
||||
---
|
||||
title: Setting your profile to private
|
||||
intro: 'A private profile displays only limited information, and hides some activity.'
|
||||
title: プロファイルをプライベートに設定する
|
||||
intro: プライベート プロファイルには限られた情報のみが表示され、一部のアクティビティは表示されません。
|
||||
versions:
|
||||
fpt: '*'
|
||||
topics:
|
||||
- Profiles
|
||||
shortTitle: Set profile to private
|
||||
ms.openlocfilehash: c00718c84d99de95a9ca1352f32954279906451d
|
||||
ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: ja-JP
|
||||
ms.lasthandoff: 10/25/2022
|
||||
ms.locfileid: '148008670'
|
||||
---
|
||||
## About private profiles
|
||||
## プライベート プロファイルについて
|
||||
|
||||
To hide parts of your profile page, you can make your profile private. This also hides your activity in various social features on {% data variables.product.prodname_dotcom_the_website %}. A private profile hides information from all users, and there is currently no option to allow specified users to see your activity.
|
||||
プロファイル ページの一部を非表示にするには、プロファイルをプライベートにします。 これにより、{% data variables.product.prodname_dotcom_the_website %} のさまざまなソーシャル機能のアクティビティも非表示になります。 プライベート プロファイルでは、すべてのユーザーに対し情報が非表示になります。現在、指定したユーザーにアクティビティを表示するオプションはありません。
|
||||
|
||||
After making your profile private, you can still view all your information when you visit your own profile.
|
||||
プロファイルをプライベートにした後も、自分のプロファイルにアクセスした場合、すべての情報が表示されます。
|
||||
|
||||
Private profiles cannot receive sponsorships under [{% data variables.product.prodname_sponsors %}](/sponsors/getting-started-with-github-sponsors/about-github-sponsors). To be eligible for {% data variables.product.prodname_sponsors %}, your profile cannot be private.
|
||||
プライベート プロファイルでは、[{% data variables.product.prodname_sponsors %}](/sponsors/getting-started-with-github-sponsors/about-github-sponsors) のスポンサーシップを受けることができません。 {% data variables.product.prodname_sponsors %} の対象になるには、プロファイルをプライベートにしないでください。
|
||||
|
||||
## Differences between private and public profiles
|
||||
## プライベートおよびパブリック プロファイルの違い
|
||||
|
||||
When your profile is private, the following content is hidden from your profile page:
|
||||
プロファイルがプライベートの場合、プロファイル ページで次のコンテンツが非表示になります。
|
||||
|
||||
- Achievements and highlights.
|
||||
- Activity overview and activity feed.
|
||||
- Contribution graph.
|
||||
- Follower and following counts.
|
||||
- Follow and Sponsor buttons.
|
||||
- Organization memberships.
|
||||
- Stars, projects, packages, and sponsoring tabs.
|
||||
- 実績とハイライト。
|
||||
- アクティビティの概要とアクティビティ フィード。
|
||||
- コントリビューション グラフ。
|
||||
- フォロワーと次の数。
|
||||
- フォローとスポンサーのボタン。
|
||||
- Organization メンバーシップ。
|
||||
- スター、プロジェクト、パッケージ、スポンサー タブ。
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note**: When your profile is private, some optional fields are still publicly visible, such as the README, biography, and profile photo.
|
||||
**注**: プロファイルがプライベートの場合、README、経歴、プロフィール写真などの一部のオプション フィールドは引き続きパブリックに表示されます。
|
||||
|
||||
{% endnote %}
|
||||
|
||||
## Changes to reporting on your activities
|
||||
## アクティビティに対する通知の変更
|
||||
|
||||
By making your profile private, you will not remove or hide past activity; this setting only applies to your activity while the private setting is enabled.
|
||||
プロフィールをプライベートにしても、過去のアクティビティは削除または非表示になりません。この設定は、プライベート設定が有効になっている間のアクティビティにのみ適用されます。
|
||||
|
||||
When your profile is private, your {% data variables.product.prodname_dotcom_the_website %} activity will not appear in the following locations:
|
||||
プロファイルがプライベートの場合、{% data variables.product.prodname_dotcom_the_website %} アクティビティは次の場所に表示されません。
|
||||
|
||||
- Activity feeds for other users.
|
||||
- Discussions leaderboards.
|
||||
- The [Trending](https://github.com/trending) page.
|
||||
- 他のユーザーのアクティビティ フィード。
|
||||
- ディスカッション ランキング。
|
||||
- [[トレンド]](https://github.com/trending) ページ。
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note**: Your activity on public repositories will still be publicly visible to anyone viewing those repositories, and some activity data may still be available through the {% data variables.product.prodname_dotcom %} API.
|
||||
**注**: パブリック リポジトリ上のアクティビティは、それらのリポジトリを表示しているユーザーには引き続きパブリックに表示され、一部のアクティビティ データは {% data variables.product.prodname_dotcom %} API を通じて引き続き使用できます。
|
||||
|
||||
{% endnote %}
|
||||
|
||||
## Changing your profile's privacy settings
|
||||
## プロファイルのプライバシー設定を変更する
|
||||
|
||||
{% data reusables.user-settings.access_settings %}
|
||||
1. Under "Contributions & Activity", select the checkbox next to **Make profile private and hide activity**.
|
||||
1. [コントリビューションとアクティビティ] で、 **[プロファイルを非公開にしてアクティビティを非表示にする]** の横にあるチェックボックスをオンにします。
|
||||
{% data reusables.user-settings.update-preferences %}
|
||||
|
||||
@@ -69,11 +69,15 @@ The email address in the `From:` field is the address that was set in the [local
|
||||
|
||||
If the email address used for the commit is not connected to your account on {% data variables.location.product_location %}, {% ifversion ghae %}change the email address used to author commits in Git. For more information, see "[Setting your commit email address](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address#setting-your-commit-email-address-in-git)."{% else %}you must [add the email address](/articles/adding-an-email-address-to-your-github-account) to your account on {% data variables.location.product_location %}. Your contributions graph will be rebuilt automatically when you add the new address.{% endif %}
|
||||
|
||||
{% warning %}
|
||||
{% ifversion fpt or ghec %}
|
||||
{% note %}
|
||||
|
||||
**Warning**: Generic email addresses, such as `jane@computer.local`, cannot be added to {% data variables.product.prodname_dotcom %} accounts. If you use such an email for your commits, the commits will not be linked to your {% data variables.product.prodname_dotcom %} profile and will not show up in your contribution graph.
|
||||
**Note**: If you use a {% data variables.enterprise.prodname_managed_user %}, you cannot add additional email addresses to the account, even if multiple email addresses are registered with your identity provider (IdP). Therefore, only commits that are authored by the primary email address registered with your IdP can be associated with your {% data variables.enterprise.prodname_managed_user %}.
|
||||
|
||||
{% endwarning %}
|
||||
{% endnote %}
|
||||
{% endif %}
|
||||
|
||||
Generic email addresses, such as `jane@computer.local`, cannot be added to {% data variables.product.prodname_dotcom %} accounts and linked to commits. If you've authored any commits using a generic email address, the commits will not be linked to your {% data variables.product.prodname_dotcom %} profile and will not show up in your contribution graph.
|
||||
|
||||
### Commit was not made in the default or `gh-pages` branch
|
||||
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Setting up and managing your personal account on GitHub
|
||||
intro: You can manage settings for your personal account on {% ifversion fpt or ghec or ghes %}{% data variables.location.product_location %}{% elsif ghae %}{% data variables.product.product_name %}{% endif %}, including email preferences, access to personal repositories, and organization memberships. You can also manage the account itself.
|
||||
intro: 'You can manage settings for your personal account on {% ifversion fpt or ghec or ghes %}{% data variables.location.product_location %}{% elsif ghae %}{% data variables.product.product_name %}{% endif %}, including email preferences, access to personal repositories, and organization memberships. You can also manage the account itself.'
|
||||
shortTitle: Personal accounts
|
||||
redirect_from:
|
||||
- /categories/setting-up-and-managing-your-github-user-account
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Managing accessibility settings
|
||||
shortTitle: Manage accessibility settings
|
||||
intro: "{% data variables.product.product_name %}'s user interface can adapt to your vision, hearing, motor, cognitive, or learning needs."
|
||||
intro: '{% data variables.product.product_name %}''s user interface can adapt to your vision, hearing, motor, cognitive, or learning needs.'
|
||||
versions:
|
||||
feature: keyboard-shortcut-accessibility-setting
|
||||
redirect_from:
|
||||
|
||||
@@ -1,10 +1,10 @@
|
||||
---
|
||||
title: 個人アカウントのセキュリティと分析設定を管理する
|
||||
intro: '{% data variables.product.prodname_dotcom %} 上のプロジェクトのコードをセキュリティ保護し分析する機能を管理できます。'
|
||||
title: Managing security and analysis settings for your personal account
|
||||
intro: 'You can control features that secure and analyze the code in your projects on {% data variables.product.prodname_dotcom %}.'
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
ghes: '>3.2'
|
||||
ghes: '*'
|
||||
topics:
|
||||
- Accounts
|
||||
redirect_from:
|
||||
@@ -12,47 +12,43 @@ redirect_from:
|
||||
- /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-security-and-analysis-settings-for-your-user-account
|
||||
- /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-security-and-analysis-settings-for-your-user-account
|
||||
shortTitle: Manage security & analysis
|
||||
ms.openlocfilehash: 61d1944219fd1b75f476c7aef8305018c85735c5
|
||||
ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: ja-JP
|
||||
ms.lasthandoff: 09/05/2022
|
||||
ms.locfileid: '145165351'
|
||||
---
|
||||
## セキュリティおよび分析設定の管理について
|
||||
## About management of security and analysis settings
|
||||
|
||||
{% data variables.product.prodname_dotcom %} を使用してリポジトリを保護できます。 このトピックでは、既存または新規のすべてのリポジトリのセキュリティおよび分析機能を管理する方法について説明します。
|
||||
{% data variables.product.prodname_dotcom %} can help secure your repositories. This topic tells you how you can manage the security and analysis features for all your existing or new repositories.
|
||||
|
||||
個々のリポジトリのセキュリティおよび分析機能は引き続き管理できます。 詳細については、「[リポジトリのセキュリティと分析の設定を管理する](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)」を参照してください。
|
||||
You can still manage the security and analysis features for individual repositories. For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)."
|
||||
|
||||
自分の個人アカウントに対するすべてのアクティビティのセキュリティ ログを確認することもできます。 詳細については、「[セキュリティ ログの確認](/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log)」を参照してください。
|
||||
You can also review the security log for all activity on your personal account. For more information, see "[Reviewing your security log](/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log)."
|
||||
|
||||
{% data reusables.security.some-security-and-analysis-features-are-enabled-by-default %}
|
||||
|
||||
{% data reusables.security.security-and-analysis-features-enable-read-only %}
|
||||
|
||||
リポジトリレベル セキュリティの概要については、「[リポジトリをセキュリティで保護する](/code-security/getting-started/securing-your-repository)」を参照してください。
|
||||
For an overview of repository-level security, see "[Securing your repository](/code-security/getting-started/securing-your-repository)."
|
||||
|
||||
## 既存のリポジトリに対して機能を有効または無効にする
|
||||
## Enabling or disabling features for existing repositories
|
||||
|
||||
{% data reusables.user-settings.access_settings %} {% data reusables.user-settings.security-analysis %}
|
||||
3. [Code security and analysis] の下で機能の右にある **[Disable all]** または **[Enable all]** をクリックします。
|
||||
{% ifversion ghes > 3.2 %}{% else %}{% endif %}
|
||||
6. オプションで、自分が所有する新しいリポジトリに対して機能を既定で有効にできます。
|
||||
{% ifversion ghes > 3.2 %}{% else %}{% endif %}
|
||||
7. **[Disable FEATURE]** または **[Enable FEATURE]** をクリックし、所有するすべてのリポジトリに対してこの機能を無効または有効にします。
|
||||
{% ifversion ghes > 3.2 %}{% else %}{% endif %}
|
||||
{% data reusables.user-settings.access_settings %}
|
||||
{% data reusables.user-settings.security-analysis %}
|
||||
3. Under "Code security and analysis", to the right of the feature, click **Disable all** or **Enable all**.
|
||||
{% ifversion ghes %}{% else %}{% endif %}
|
||||
6. Optionally, enable the feature by default for new repositories that you own.
|
||||
{% ifversion ghes %}{% else %}{% endif %}
|
||||
7. Click **Disable FEATURE** or **Enable FEATURE** to disable or enable the feature for all the repositories you own.
|
||||
{% ifversion ghes %}{% else %}{% endif %}
|
||||
|
||||
{% data reusables.security.displayed-information %}
|
||||
|
||||
## 既存のリポジトリに対して機能を有効または無効にする
|
||||
## Enabling or disabling features for new repositories
|
||||
|
||||
{% data reusables.user-settings.access_settings %} {% data reusables.user-settings.security-analysis %}
|
||||
3. 機能の右側にある [Code security and analysis] で、所有する新しいリポジトリに対して既定で機能を有効または無効にします
|
||||
{% ifversion ghes > 3.2 %}{% else %}{% endif %}
|
||||
{% data reusables.user-settings.access_settings %}
|
||||
{% data reusables.user-settings.security-analysis %}
|
||||
3. Under "Code security and analysis", to the right of the feature, enable or disable the feature by default for new repositories that you own.
|
||||
{% ifversion ghes %}{% else %}{% endif %}
|
||||
|
||||
## 参考資料
|
||||
## Further reading
|
||||
|
||||
- "[依存関係グラフについて](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)"
|
||||
- "[{% data variables.product.prodname_dependabot_alerts %} について](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)"
|
||||
- "[依存関係を自動的に更新する](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically)"
|
||||
- "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)"
|
||||
- "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)"
|
||||
- "[Keeping your dependencies updated automatically](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically)"
|
||||
|
||||
@@ -9,12 +9,12 @@ versions:
|
||||
topics:
|
||||
- Accounts
|
||||
shortTitle: Manage cookie preferences
|
||||
ms.openlocfilehash: f2fdbcf8bd552902e7db491aa1b3c6622c5673ab
|
||||
ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
|
||||
ms.openlocfilehash: 44f0324a91f8447a10947d5f5c7be111241ad091
|
||||
ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: ja-JP
|
||||
ms.lasthandoff: 09/09/2022
|
||||
ms.locfileid: '147760923'
|
||||
ms.lasthandoff: 10/25/2022
|
||||
ms.locfileid: '148108809'
|
||||
---
|
||||
## エンタープライズ マーケティング ページでの Cookie の基本設定について
|
||||
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: テーマ設定を管理する
|
||||
intro: 'システム設定に従うか、ライトまたはダーク モードを常に使用するようにテーマを設定することで、{% data variables.product.product_name %} の外観を管理できます。'
|
||||
title: Managing your theme settings
|
||||
intro: 'You can manage how {% data variables.product.product_name %} looks to you by setting a theme preference that either follows your system settings or always uses a light or dark mode.'
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghae: '*'
|
||||
@@ -13,52 +13,51 @@ redirect_from:
|
||||
- /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings
|
||||
- /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings
|
||||
shortTitle: Manage theme settings
|
||||
ms.openlocfilehash: 6251b265d99271f58a4ad02d2f6cb7fdf722cb6b
|
||||
ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: ja-JP
|
||||
ms.lasthandoff: 09/05/2022
|
||||
ms.locfileid: '147580448'
|
||||
---
|
||||
{% data variables.product.product_name %} を使用時期と使用方法を選択して柔軟性を高めるために、テーマ設定をして {% data variables.product.product_name %} の外観を変更できます。 ライトとダークの 2 つのテーマから選択するか、システム設定に従うかを {% data variables.product.product_name %} で設定できます。
|
||||
|
||||
ダーク テーマを使用して、特定のデバイスの電力消費量を削減したり、暗い場所で目の負担を減らしたり、テーマの外観を優先したりすることができます。
|
||||
For choice and flexibility in how and when you use {% data variables.product.product_name %}, you can configure theme settings to change how {% data variables.product.product_name %} looks to you. You can choose from themes that are light or dark, or you can configure {% data variables.product.product_name %} to follow your system settings.
|
||||
|
||||
{% ifversion fpt or ghes > 3.2 or ghae or ghec %}弱視の方は、前景と背景の要素のコントラストが強いハイ コントラスト テーマの使用をお勧めします。{% endif %}{% ifversion fpt or ghae or ghec %}色覚障碍がある方には、ライトとダークの色覚障碍向けテーマをお勧めします。
|
||||
You may want to use a dark theme to reduce power consumption on certain devices, to reduce eye strain in low-light conditions, or because you prefer how the theme looks.
|
||||
|
||||
If you have low vision, you may benefit from a high contrast theme, with greater contrast between foreground and background elements.{% ifversion fpt or ghae or ghec %} If you have colorblindness, you may benefit from our light and dark colorblind themes.
|
||||
|
||||
{% endif %}
|
||||
|
||||
{% data reusables.user-settings.access_settings %} {% data reusables.user-settings.appearance-settings %}
|
||||
{% data reusables.user-settings.access_settings %}
|
||||
{% data reusables.user-settings.appearance-settings %}
|
||||
|
||||
1. [テーマ モード] で、ドロップダウン メニューを選択し、テーマの設定をクリックします。
|
||||
1. Under "Theme mode", select the drop-down menu, then click a theme preference.
|
||||
|
||||
![テーマの設定を選択するための [テーマ モード] のドロップダウン メニュー](/assets/images/help/settings/theme-mode-drop-down-menu.png)
|
||||
1. 使いたいテーマをクリックしてください。
|
||||
- 1 つのテーマを選択する場合は、そのテーマをクリックします。
|
||||
|
||||
1. Click the theme you'd like to use.
|
||||
- If you chose a single theme, click a theme.
|
||||
|
||||
{%- ifversion ghes = 3.5 %} {% note %}
|
||||
{%- ifversion ghes = 3.5 %}
|
||||
{% note %}
|
||||
|
||||
**注**: 明るいハイ コントラスト テーマは、{% data variables.product.product_name %} 3.5.0、3.5.1、3.5.2、および 3.5.3 では使用できませんでした。 このテーマは 3.5.4 以降で使用できます。 アップグレードの詳しい情報については、サイト管理者にお問い合わせください。
|
||||
**Note**: The light high contrast theme was unavailable in {% data variables.product.product_name %} 3.5.0, 3.5.1, 3.5.2, and 3.5.3. The theme is available in 3.5.4 and later. For more information about upgrades, contact your site administrator.
|
||||
|
||||
使用する {% data variables.product.product_name %} のバージョンの決定について詳しくは、「[{% data variables.product.prodname_docs %} のバージョンについて](/get-started/learning-about-github/about-versions-of-github-docs#github-enterprise-server)」を参照してください。
|
||||
{% endnote %} {%- endif %}
|
||||
For more information about determining the version of {% data variables.product.product_name %} you're using, see "[About versions of {% data variables.product.prodname_docs %}](/get-started/learning-about-github/about-versions-of-github-docs#github-enterprise-server)."
|
||||
{% endnote %}
|
||||
{%- endif %}
|
||||
|
||||
{% ifversion fpt or ghes > 3.2 or ghae or ghec %}{% else %}{% endif %}
|
||||
- システム設定に従うことを選択した場合は、昼のテーマと夜のテーマをクリックします。
|
||||
|
||||
- If you chose to follow your system settings, click a day theme and a night theme.
|
||||
|
||||
{% ifversion fpt or ghes > 3.2 or ghae or ghec %}{% else %}{% endif %} {% ifversion fpt or ghec %}
|
||||
- 現在パブリック ベータ版のテーマを選択する場合は、まず機能プレビューでそれを有効にする必要があります。 詳細については、「[機能プレビューを使用した早期アクセス リリースを探索する](/get-started/using-github/exploring-early-access-releases-with-feature-preview)」を参照してください。{% endif %}
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
- If you would like to choose a theme which is currently in public beta, you will first need to enable it with feature preview. For more information, see "[Exploring early access releases with feature preview](/get-started/using-github/exploring-early-access-releases-with-feature-preview)."{% endif %}
|
||||
|
||||
{% ifversion command-palette %}
|
||||
|
||||
{% note %}
|
||||
|
||||
**注:** コマンド パレットを使用してテーマの設定を変更することもできます。 詳細については、「[{% data variables.product.prodname_command_palette %}](/get-started/using-github/github-command-palette)」を参照してください。
|
||||
**Note:** You can also change your theme settings with the command palette. For more information, see "[{% data variables.product.prodname_command_palette %}](/get-started/using-github/github-command-palette)".
|
||||
|
||||
{% endnote %}
|
||||
|
||||
{% endif %}
|
||||
|
||||
## 参考資料
|
||||
## Further reading
|
||||
|
||||
- [{% data variables.product.prodname_desktop %}](/desktop/installing-and-configuring-github-desktop/setting-a-theme-for-github-desktop) の設定方法
|
||||
- "[Setting a theme for {% data variables.product.prodname_desktop %}](/desktop/installing-and-configuring-github-desktop/setting-a-theme-for-github-desktop)"
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: 個人アカウントのリポジトリの権限レベル
|
||||
intro: 個人アカウントが所有するリポジトリには、リポジトリ所有者とコラボレーターという 2 つのアクセス許可レベルがあります。
|
||||
title: Permission levels for a personal account repository
|
||||
intro: 'A repository owned by a personal account has two permission levels: the repository owner and collaborators.'
|
||||
redirect_from:
|
||||
- /articles/permission-levels-for-a-user-account-repository
|
||||
- /github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository
|
||||
@@ -14,84 +14,79 @@ versions:
|
||||
topics:
|
||||
- Accounts
|
||||
shortTitle: Repository permissions
|
||||
ms.openlocfilehash: e7c7a542204c7b1ce69bc19ac326fb248bbbff12
|
||||
ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: ja-JP
|
||||
ms.lasthandoff: 09/05/2022
|
||||
ms.locfileid: '147066307'
|
||||
---
|
||||
## 個人アカウント リポジトリのアクセス許可レベルについて
|
||||
## About permissions levels for a personal account repository
|
||||
|
||||
個人アカウントが所有するリポジトリの所有者は 1 人です。 所有権のアクセス許可を別の個人アカウントと共有することはできません。
|
||||
Repositories owned by personal accounts have one owner. Ownership permissions can't be shared with another personal account.
|
||||
|
||||
{% data variables.product.product_name %} のユーザーをコラボレーターとしてリポジトリに{% ifversion fpt or ghec %}招待{% else %}追加{% endif %}することもできます。 詳細については、「[コラボレーターを個人リポジトリに招待する](/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository)」を参照してください。
|
||||
You can also {% ifversion fpt or ghec %}invite{% else %}add{% endif %} users on {% data variables.product.product_name %} to your repository as collaborators. For more information, see "[Inviting collaborators to a personal repository](/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository)."
|
||||
|
||||
{% tip %}
|
||||
|
||||
**ヒント:** 個人アカウントが所有しているリポジトリに対して、より詳細なアクセス権が必要な場合には、リポジトリを Organization に移譲することを検討してください。 詳細については、「[リポジトリを移譲する](/github/administering-a-repository/transferring-a-repository#transferring-a-repository-owned-by-your-personal-account)」を参照してください。
|
||||
**Tip:** If you require more granular access to a repository owned by your personal account, consider transferring the repository to an organization. For more information, see "[Transferring a repository](/github/administering-a-repository/transferring-a-repository#transferring-a-repository-owned-by-your-personal-account)."
|
||||
|
||||
{% endtip %}
|
||||
|
||||
## 個人アカウントが所有しているリポジトリに対する所有者アクセス権
|
||||
## Owner access for a repository owned by a personal account
|
||||
|
||||
リポジトリオーナーは、リポジトリを完全に制御することができます。 コラボレータが実行できるアクションに加えて、リポジトリオーナーは次のアクションを実行できます。
|
||||
The repository owner has full control of the repository. In addition to the actions that any collaborator can perform, the repository owner can perform the following actions.
|
||||
|
||||
| アクション | 説明を見る |
|
||||
| Action | More information |
|
||||
| :- | :- |
|
||||
| {% ifversion fpt or ghec %}コラボレーターの招待{% else %}コラボレーターの追加{% endif %} | 「[コラボレーターを個人リポジトリに招待する](/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository)」 |
|
||||
| リポジトリの表示変更 | 「[リポジトリの可視性を設定する](/github/administering-a-repository/setting-repository-visibility)」 |{% ifversion fpt or ghec %}
|
||||
| リポジトリとのインタラクションの制限 | 「[リポジトリでのインタラクションを制限する](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository)」 |{% endif %}
|
||||
| デフォルトブランチを含むブランチ名の変更 | 「[ブランチの名前を変更する](/github/administering-a-repository/renaming-a-branch)」 |
|
||||
| 保護されたブランチで、レビューの承認がなくてもプルリクエストをマージする | 「[保護されたブランチについて](/github/administering-a-repository/about-protected-branches)」 |
|
||||
| リポジトリを削除する | 「[リポジトリの削除](/repositories/creating-and-managing-repositories/deleting-a-repository)」 |
|
||||
| リポジトリのトピックの管理 | 「[トピックでリポジトリを分類する](/github/administering-a-repository/classifying-your-repository-with-topics)」 |{% ifversion fpt or ghec %}
|
||||
| リポジトリのセキュリティおよび分析設定の管理 | 「[リポジトリのセキュリティと分析設定を管理する](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)」 |{% endif %}{% ifversion fpt or ghec %}
|
||||
| プライベートリポジトリの依存関係グラフの有効化 | 「[リポジトリの依存関係を調べる](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository#enabling-and-disabling-the-dependency-graph-for-a-private-repository)」 |{% endif %}
|
||||
| パッケージの削除および復元 | 「[パッケージを削除および復元する](/packages/learn-github-packages/deleting-and-restoring-a-package)」 |
|
||||
| リポジトリのソーシャルメディア向けプレビューのカスタマイズ | 「[リポジトリのソーシャルメディア向けプレビューをカスタマイズする](/github/administering-a-repository/customizing-your-repositorys-social-media-preview)」 |
|
||||
| リポジトリからのテンプレートの作成 | 「[テンプレートリポジトリを作成する](/github/creating-cloning-and-archiving-repositories/creating-a-template-repository)」 |
|
||||
| Control access to {% data variables.product.prodname_dependabot_alerts %} へのアクセスを制御する| 「[リポジトリのセキュリティと分析設定を管理する](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)」 |{% ifversion fpt or ghec %}
|
||||
| リポジトリで {% data variables.product.prodname_dependabot_alerts %} を閉じる | "[{% data variables.product.prodname_dependabot_alerts %} の表示と更新](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts)" |
|
||||
| プライベートリポジトリのデータ利用の管理 | 「[プライベート リポジトリ用のデータ利用設定の管理](/get-started/privacy-on-github/managing-data-use-settings-for-your-private-repository)」|{% endif %}
|
||||
| リポジトリのコードオーナーを定義する | 「[コード オーナーについて](/github/creating-cloning-and-archiving-repositories/about-code-owners)」 |
|
||||
| リポジトリのアーカイブ | 「[リポジトリのアーカイブ](/repositories/archiving-a-github-repository/archiving-repositories)」 |{% ifversion fpt or ghec %}
|
||||
| セキュリティアドバイザリの作成 | 「[{% data variables.product.prodname_security_advisories %}について](/github/managing-security-vulnerabilities/about-github-security-advisories)」 |
|
||||
| スポンサーボタンの表示 | 「[リポジトリにスポンサーボタンを表示する](/github/administering-a-repository/displaying-a-sponsor-button-in-your-repository)」 |{% endif %}
|
||||
| プルリクエストの自動マージを許可または禁止 | 「[リポジトリ内のプル リクエストの自動マージを管理する](/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository)」 |
|
||||
| {% ifversion fpt or ghec %}Invite collaborators{% else %}Add collaborators{% endif %} | "[Inviting collaborators to a personal repository](/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository)" |
|
||||
| Change the visibility of the repository | "[Setting repository visibility](/github/administering-a-repository/setting-repository-visibility)" |{% ifversion fpt or ghec %}
|
||||
| Limit interactions with the repository | "[Limiting interactions in your repository](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository)" |{% endif %}
|
||||
| Rename a branch, including the default branch | "[Renaming a branch](/github/administering-a-repository/renaming-a-branch)" |
|
||||
| Merge a pull request on a protected branch, even if there are no approving reviews | "[About protected branches](/github/administering-a-repository/about-protected-branches)" |
|
||||
| Delete the repository | "[Deleting a repository](/repositories/creating-and-managing-repositories/deleting-a-repository)" |
|
||||
| Manage the repository's topics | "[Classifying your repository with topics](/github/administering-a-repository/classifying-your-repository-with-topics)" |{% ifversion fpt or ghec %}
|
||||
| Manage security and analysis settings for the repository | "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)" |{% endif %}{% ifversion fpt or ghec %}
|
||||
| Enable the dependency graph for a private repository | "[Exploring the dependencies of a repository](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository#enabling-and-disabling-the-dependency-graph-for-a-private-repository)" |{% endif %}
|
||||
| Delete and restore packages | "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)" |
|
||||
| Customize the repository's social media preview | "[Customizing your repository's social media preview](/github/administering-a-repository/customizing-your-repositorys-social-media-preview)" |
|
||||
| Create a template from the repository | "[Creating a template repository](/github/creating-cloning-and-archiving-repositories/creating-a-template-repository)" |
|
||||
| Control access to {% data variables.product.prodname_dependabot_alerts %}| "[Managing security and analysis settings for your repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)" |{% ifversion fpt or ghec %}
|
||||
| Dismiss {% data variables.product.prodname_dependabot_alerts %} in the repository | "[Viewing and updating {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts)" |
|
||||
| Manage data use for a private repository | "[Managing data use settings for your private repository](/get-started/privacy-on-github/managing-data-use-settings-for-your-private-repository)"|{% endif %}
|
||||
| Define code owners for the repository | "[About code owners](/github/creating-cloning-and-archiving-repositories/about-code-owners)" |
|
||||
| Archive the repository | "[Archiving repositories](/repositories/archiving-a-github-repository/archiving-repositories)" |{% ifversion fpt or ghec %}
|
||||
| Create security advisories | "[About repository security advisories](/github/managing-security-vulnerabilities/about-github-security-advisories)" |
|
||||
| Display a sponsor button | "[Displaying a sponsor button in your repository](/github/administering-a-repository/displaying-a-sponsor-button-in-your-repository)" |{% endif %}
|
||||
| Allow or disallow auto-merge for pull requests | "[Managing auto-merge for pull requests in your repository](/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository)" |
|
||||
| Manage webhooks and deploy keys | "[Managing deploy keys](/developers/overview/managing-deploy-keys#deploy-keys)" |
|
||||
|
||||
## 個人アカウントが所有しているリポジトリに対するコラボレーター アクセス権
|
||||
## Collaborator access for a repository owned by a personal account
|
||||
|
||||
個人リポジトリのコラボレータは、リポジトリのコンテンツをプル（読み取り）したり、リポジトリに変更をプッシュ（書き込み）したりすることができます。
|
||||
Collaborators on a personal repository can pull (read) the contents of the repository and push (write) changes to the repository.
|
||||
|
||||
{% note %}
|
||||
|
||||
**注:** プライベート リポジトリでは、リポジトリ オーナーはコラボレーターに書き込みアクセスしか付与できません。 個人アカウントが所有するリポジトリに対して、コラボレーターが読み取り専用アクセス権を持つことはできません。
|
||||
**Note:** In a private repository, repository owners can only grant write access to collaborators. Collaborators can't have read-only access to repositories owned by a personal account.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
コラボレータは、次のアクションを実行することもできます。
|
||||
Collaborators can also perform the following actions.
|
||||
|
||||
| アクション | 説明を見る |
|
||||
| Action | More information |
|
||||
| :- | :- |
|
||||
| リポジトリのフォーク | 「[フォークについて](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks)」 |
|
||||
| デフォルトブランチ以外のブランチ名の変更 | 「[ブランチの名前を変更する](/github/administering-a-repository/renaming-a-branch)」 |
|
||||
| リポジトリ内のコミット、プルリクエスト、Issue に関するコメントの作成、編集、削除 | <ul><li>「[Issue について](/github/managing-your-work-on-github/about-issues)」</li><li>「[プル リクエストへコメントする](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request)」</li><li>「[混乱を生むコメントを管理する](/communities/moderating-comments-and-conversations/managing-disruptive-comments)」</li></ul> |
|
||||
| リポジトリ内の Issue の作成、割り当て、クローズ、再オープン | 「[Issue で作業を管理する](/github/managing-your-work-on-github/managing-your-work-with-issues)」 |
|
||||
| リポジトリ内の Issue とプルリクエストのラベル管理 | 「[Issue と Pull Request のラベル付け](/github/managing-your-work-on-github/labeling-issues-and-pull-requests)」 |
|
||||
| リポジトリ内の Issue とプルリクエストのマイルストーン管理 | 「[Issue と Pull Request のマイルストーンの作成と削除](/github/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests)」 |
|
||||
| リポジトリ内の Issue またはプルリクエストを重複としてマーク | 「[Issue と Pull Request の重複について](/github/managing-your-work-on-github/about-duplicate-issues-and-pull-requests)」 |
|
||||
| リポジトリ内のプルリクエストの作成、マージ、クローズ | 「[プル リクエストで、作業に対する変更を提案する](/github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests)」 |
|
||||
| プルリクエストの自動マージの有効化または無効化 | 「[プル リクエストを自動的にマージする](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request)」
|
||||
| リポジトリ内のプルリクエストに提案された変更を適用 |「[プル リクエストでのフィードバックを取り込む](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/incorporating-feedback-in-your-pull-request)」 |
|
||||
| リポジトリのフォークからプルリクエストを作成 | 「[フォークからプル リクエストを作成する](/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork)」 |
|
||||
| プルリクエストのマージ可能性に影響するプルリクエストについてレビューを送信 | 「[プル リクエストで提案された変更をレビューする](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request)」 |
|
||||
| リポジトリ用のウィキの作成と編集 | 「[ウィキについて](/communities/documenting-your-project-with-wikis/about-wikis)」 |
|
||||
| リポジトリ用のリリースの作成と編集 | 「[リポジトリのリリースを管理する](/github/administering-a-repository/managing-releases-in-a-repository)」 |
|
||||
| リポジトリのコードオーナーの定義 | 「[コード オーナーについて](/articles/about-code-owners)」 |{% ifversion fpt or ghae or ghec %}
|
||||
| パッケージの公開、表示、インストール | 「[パッケージの公開と管理](/github/managing-packages-with-github-packages/publishing-and-managing-packages)」 |{% endif %}
|
||||
| リポジトリでコラボレーターである自身を削除する | 「[コラボレーターのリポジトリから自分を削除する](/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-a-collaborators-repository)」 |
|
||||
| Fork the repository | "[About forks](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks)" |
|
||||
| Rename a branch other than the default branch | "[Renaming a branch](/github/administering-a-repository/renaming-a-branch)" |
|
||||
| Create, edit, and delete comments on commits, pull requests, and issues in the repository | <ul><li>"[About issues](/github/managing-your-work-on-github/about-issues)"</li><li>"[Commenting on a pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request)"</li><li>"[Managing disruptive comments](/communities/moderating-comments-and-conversations/managing-disruptive-comments)"</li></ul> |
|
||||
| Create, assign, close, and re-open issues in the repository | "[Managing your work with issues](/github/managing-your-work-on-github/managing-your-work-with-issues)" |
|
||||
| Manage labels for issues and pull requests in the repository | "[Labeling issues and pull requests](/github/managing-your-work-on-github/labeling-issues-and-pull-requests)" |
|
||||
| Manage milestones for issues and pull requests in the repository | "[Creating and editing milestones for issues and pull requests](/github/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests)" |
|
||||
| Mark an issue or pull request in the repository as a duplicate | "[About duplicate issues and pull requests](/github/managing-your-work-on-github/about-duplicate-issues-and-pull-requests)" |
|
||||
| Create, merge, and close pull requests in the repository | "[Proposing changes to your work with pull requests](/github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests)" |
|
||||
| Enable and disable auto-merge for a pull request | "[Automatically merging a pull request](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request)"
|
||||
| Apply suggested changes to pull requests in the repository |"[Incorporating feedback in your pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/incorporating-feedback-in-your-pull-request)" |
|
||||
| Create a pull request from a fork of the repository | "[Creating a pull request from a fork](/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork)" |
|
||||
| Submit a review on a pull request that affects the mergeability of the pull request | "[Reviewing proposed changes in a pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request)" |
|
||||
| Create and edit a wiki for the repository | "[About wikis](/communities/documenting-your-project-with-wikis/about-wikis)" |
|
||||
| Create and edit releases for the repository | "[Managing releases in a repository](/github/administering-a-repository/managing-releases-in-a-repository)" |
|
||||
| Act as a code owner for the repository | "[About code owners](/articles/about-code-owners)" |{% ifversion fpt or ghae or ghec %}
|
||||
| Publish, view, or install packages | "[Publishing and managing packages](/github/managing-packages-with-github-packages/publishing-and-managing-packages)" |{% endif %}
|
||||
| Remove themselves as collaborators on the repository | "[Removing yourself from a collaborator's repository](/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-a-collaborators-repository)" |
|
||||
|
||||
## 参考資料
|
||||
## Further reading
|
||||
|
||||
- 「[Organization のリポジトリ ロール](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)」
|
||||
- "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)"
|
||||
|
||||
@@ -231,19 +231,11 @@ For example, this `cleanup.js` will only run on Linux-based runners:
|
||||
|
||||
### `runs.steps`
|
||||
|
||||
{% ifversion fpt or ghes > 3.2 or ghae or ghec %}
|
||||
**Required** The steps that you plan to run in this action. These can be either `run` steps or `uses` steps.
|
||||
{% else %}
|
||||
**Required** The steps that you plan to run in this action.
|
||||
{% endif %}
|
||||
|
||||
#### `runs.steps[*].run`
|
||||
|
||||
{% ifversion fpt or ghes > 3.2 or ghae or ghec %}
|
||||
**Optional** The command you want to run. This can be inline or a script in your action repository:
|
||||
{% else %}
|
||||
**Required** The command you want to run. This can be inline or a script in your action repository:
|
||||
{% endif %}
|
||||
|
||||
{% raw %}
|
||||
```yaml
|
||||
@@ -269,11 +261,7 @@ For more information, see "[`github context`](/actions/reference/context-and-exp
|
||||
|
||||
#### `runs.steps[*].shell`
|
||||
|
||||
{% ifversion fpt or ghes > 3.2 or ghae or ghec %}
|
||||
**Optional** The shell where you want to run the command. You can use any of the shells listed [here](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsshell). Required if `run` is set.
|
||||
{% else %}
|
||||
**Required** The shell where you want to run the command. You can use any of the shells listed [here](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsshell). Required if `run` is set.
|
||||
{% endif %}
|
||||
|
||||
{% ifversion fpt or ghes > 3.3 or ghae > 3.3 or ghec %}
|
||||
#### `runs.steps[*].if`
|
||||
@@ -322,7 +310,6 @@ steps:
|
||||
|
||||
**Optional** Specifies the working directory where the command is run.
|
||||
|
||||
{% ifversion fpt or ghes > 3.2 or ghae or ghec %}
|
||||
#### `runs.steps[*].uses`
|
||||
|
||||
**Optional** Selects an action to run as part of a step in your job. An action is a reusable unit of code. You can use an action defined in the same repository as the workflow, a public repository, or in a [published Docker container image](https://hub.docker.com/).
|
||||
@@ -371,7 +358,6 @@ runs:
|
||||
middle_name: The
|
||||
last_name: Octocat
|
||||
```
|
||||
{% endif %}
|
||||
|
||||
{% ifversion ghes > 3.5 or ghae > 3.5 %}
|
||||
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Configuring OpenID Connect in HashiCorp Vault
|
||||
title: HashiCorp Vault での OpenID Connect の構成
|
||||
shortTitle: OpenID Connect in HashiCorp Vault
|
||||
intro: Use OpenID Connect within your workflows to authenticate with HashiCorp Vault.
|
||||
intro: ワークフロー内で OpenID Connect を使用して HashiCorp Vault で認証します。
|
||||
miniTocMaxHeadingLevel: 3
|
||||
versions:
|
||||
fpt: '*'
|
||||
@@ -10,31 +10,35 @@ versions:
|
||||
type: tutorial
|
||||
topics:
|
||||
- Security
|
||||
ms.openlocfilehash: 174243818443709ee6ffe3b22aa668cff254266f
|
||||
ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: ja-JP
|
||||
ms.lasthandoff: 10/25/2022
|
||||
ms.locfileid: '148106630'
|
||||
---
|
||||
{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %}
|
||||
|
||||
{% data reusables.actions.enterprise-beta %}
|
||||
{% data reusables.actions.enterprise-github-hosted-runners %}
|
||||
## 概要
|
||||
|
||||
## Overview
|
||||
OpenID Connect (OIDC) を使うと、{% data variables.product.prodname_actions %} ワークフローが HashiCorp Vault で認証し、シークレットを取得できます。
|
||||
|
||||
OpenID Connect (OIDC) allows your {% data variables.product.prodname_actions %} workflows to authenticate with a HashiCorp Vault to retrieve secrets.
|
||||
このガイドでは、HashiCorp Vault が {% data variables.product.prodname_dotcom %} の OIDC をフェデレーション ID として信頼するように構成する方法の概要について説明します。また、この構成を [hashicorp/vault-action](https://github.com/hashicorp/vault-action) アクションで使って HashiCorp Vault からシークレットを取得する方法を示します。
|
||||
|
||||
This guide gives an overview of how to configure HashiCorp Vault to trust {% data variables.product.prodname_dotcom %}'s OIDC as a federated identity, and demonstrates how to use this configuration in the [hashicorp/vault-action](https://github.com/hashicorp/vault-action) action to retrieve secrets from HashiCorp Vault.
|
||||
|
||||
## Prerequisites
|
||||
## 前提条件
|
||||
|
||||
{% data reusables.actions.oidc-link-to-intro %}
|
||||
|
||||
{% data reusables.actions.oidc-security-notice %}
|
||||
|
||||
## Adding the identity provider to HashiCorp Vault
|
||||
## HashiCorp Vault への ID プロバイダーの追加
|
||||
|
||||
To use OIDC with HashiCorp Vault, you will need to add a trust configuration for the {% data variables.product.prodname_dotcom %} OIDC provider. For more information, see the HashiCorp Vault [documentation](https://www.vaultproject.io/docs/auth/jwt).
|
||||
HashiCorp Vault と共に OIDC を使うには、{% data variables.product.prodname_dotcom %} OIDC プロバイダーの信頼構成を追加する必要があります。 詳細については、HashiCorp Vault の[ドキュメント](https://www.vaultproject.io/docs/auth/jwt)を参照してください。
|
||||
|
||||
To configure your Vault server to accept JSON Web Tokens (JWT) for authentication:
|
||||
認証に JSON Web トークン (JWT) を受け入れるように Vault サーバーを構成します。
|
||||
|
||||
1. Enable the JWT `auth` method, and use `write` to apply the configuration to your Vault.
|
||||
For `oidc_discovery_url` and `bound_issuer` parameters, use {% ifversion ghes %}`https://HOSTNAME/_services/token`{% else %}`https://token.actions.githubusercontent.com`{% endif %}. These parameters allow the Vault server to verify the received JSON Web Tokens (JWT) during the authentication process.
|
||||
1. JWT `auth` メソッドを有効にし、`write` を使用して Vault に構成を適用します。
|
||||
`oidc_discovery_url` および `bound_issuer` パラメーターの場合は、{% ifversion ghes %}`https://HOSTNAME/_services/token`{% else %}`https://token.actions.githubusercontent.com`{% endif %} を使います。 これらのパラメーターを使用すると、Vault サーバーは認証プロセス中に受信した JSON Web トークン (JWT) を確認できます。
|
||||
|
||||
```sh{:copy}
|
||||
vault auth enable jwt
|
||||
@@ -45,7 +49,7 @@ To configure your Vault server to accept JSON Web Tokens (JWT) for authenticatio
|
||||
bound_issuer="{% ifversion ghes %}https://HOSTNAME/_services/token{% else %}https://token.actions.githubusercontent.com{% endif %}" \
|
||||
oidc_discovery_url="{% ifversion ghes %}https://HOSTNAME/_services/token{% else %}https://token.actions.githubusercontent.com{% endif %}"
|
||||
```
|
||||
2. Configure a policy that only grants access to the specific paths your workflows will use to retrieve secrets. For more advanced policies, see the HashiCorp Vault [Policies documentation](https://www.vaultproject.io/docs/concepts/policies).
|
||||
2. ワークフローがシークレットの取得に使用する特定のパスへのアクセスのみを許可するポリシーを構成します。 詳細なポリシーについては、HashiCorp Vault の [「ポリシー」のドキュメント](https://www.vaultproject.io/docs/concepts/policies)を参照してください。
|
||||
|
||||
```sh{:copy}
|
||||
vault policy write myproject-production - <<EOF
|
||||
@@ -56,7 +60,7 @@ To configure your Vault server to accept JSON Web Tokens (JWT) for authenticatio
|
||||
}
|
||||
EOF
|
||||
```
|
||||
3. Configure roles to group different policies together. If the authentication is successful, these policies are attached to the resulting Vault access token.
|
||||
3. 異なるポリシーをグループ化するようにロールを構成します。 認証が成功した場合、これらのポリシーは結果の Vault アクセス トークンにアタッチされます。
|
||||
|
||||
```sh{:copy}
|
||||
vault write auth/jwt/role/myproject-production -<<EOF
|
||||
@@ -72,51 +76,51 @@ To configure your Vault server to accept JSON Web Tokens (JWT) for authenticatio
|
||||
EOF
|
||||
```
|
||||
|
||||
- `ttl` defines the validity of the resulting access token.
|
||||
- Ensure that the `bound_claims` parameter is defined for your security requirements, and has at least one condition. Optionally, you can also set the `bound_subject` as well as the `bound_audiences` parameter.
|
||||
- To check arbitrary claims in the received JWT payload, the `bound_claims` parameter contains a set of claims and their required values. In the above example, the role will accept any incoming authentication requests from the `repo-name` repository owned by the `user-or-org-name` account.
|
||||
- To see all the available claims supported by {% data variables.product.prodname_dotcom %}'s OIDC provider, see ["Configuring the OIDC trust with the cloud"](/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect#configuring-the-oidc-trust-with-the-cloud).
|
||||
- `ttl` によって、結果のアクセス トークンの有効性が定義されます。
|
||||
- `bound_claims` パラメーターがセキュリティ要件に対して定義されており、少なくとも 1 つの条件があることを確認します。 必要に応じて、`bound_subject` だけでなく、`bound_audiences` パラメーターも設定できます。
|
||||
- 受信した JWT ペイロード内の任意の要求を確認するために、`bound_claims` パラメーターには一連の要求とその必須の値が含まれています。 上記の例では、ロールは、`user-or-org-name` アカウントによって所有される `repo-name` リポジトリからの受信認証要求を受け取ります。
|
||||
- {% data variables.product.prodname_dotcom %} の OIDC プロバイダーでサポートされている使用可能なすべての要求を確認するには、「[クラウドを使った OIDC 信頼の構成](/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect#configuring-the-oidc-trust-with-the-cloud)」を参照してください。
|
||||
|
||||
For more information, see the HashiCorp Vault [documentation](https://www.vaultproject.io/docs/auth/jwt).
|
||||
詳細については、HashiCorp Vault の[ドキュメント](https://www.vaultproject.io/docs/auth/jwt)を参照してください。
|
||||
|
||||
## Updating your {% data variables.product.prodname_actions %} workflow
|
||||
## {% data variables.product.prodname_actions %} ワークフローを更新する
|
||||
|
||||
To update your workflows for OIDC, you will need to make two changes to your YAML:
|
||||
1. Add permissions settings for the token.
|
||||
2. Use the [`hashicorp/vault-action`](https://github.com/hashicorp/vault-action) action to exchange the OIDC token (JWT) for a cloud access token.
|
||||
OIDC のワークフローを更新するには、YAML に 2 つの変更を行う必要があります。
|
||||
1. トークンのアクセス許可設定を追加します。
|
||||
2. この [`hashicorp/vault-action`](https://github.com/hashicorp/vault-action) アクションを使って、OIDC トークン (JWT) をクラウド アクセス トークンと交換します。
|
||||
|
||||
|
||||
To add OIDC integration to your workflows that allow them to access secrets in Vault, you will need to add the following code changes:
|
||||
Vault のシークレットにアクセスできるようにワークフローに OIDC 統合を追加するには、次のコード変更を追加する必要があります。
|
||||
|
||||
- Grant permission to fetch the token from the {% data variables.product.prodname_dotcom %} OIDC provider:
|
||||
- The workflow needs `permissions:` settings with the `id-token` value set to `write`. This lets you fetch the OIDC token from every job in the workflow.
|
||||
- Request the JWT from the {% data variables.product.prodname_dotcom %} OIDC provider, and present it to HashiCorp Vault to receive an access token:
|
||||
- You can use the [`hashicorp/vault-action`](https://github.com/hashicorp/vault-action) action to fetch the JWT and receive the access token from Vault, or you could use the [Actions toolkit](https://github.com/actions/toolkit/) to fetch the tokens for your job.
|
||||
- {% data variables.product.prodname_dotcom %} OIDC プロバイダーからトークンをフェッチするアクセス許可を付与します。
|
||||
- ワークフローには、`id-token` の値が `write` に設定された `permissions:` 設定が必要です。 これにより、ワークフロー内のすべてのジョブから OIDC トークンをフェッチすることができます。
|
||||
- {% data variables.product.prodname_dotcom %} OIDC プロバイダーに JWT を要求し、それを HashiCorp Vault に提示してアクセス トークンを受け取ります。
|
||||
- [`hashicorp/vault-action`](https://github.com/hashicorp/vault-action) アクションを使って、JWT をフェッチし、Vault からアクセス トークンを受け取ることができます。または、[Actions ツールキット](https://github.com/actions/toolkit/)を使ってジョブのトークンをフェッチすることもできます。
|
||||
|
||||
This example demonstrates how to use OIDC with the official action to request a secret from HashiCorp Vault.
|
||||
この例は、HashiCorp Vault からシークレットを要求するために、公式のアクションと共に OIDC を使う方法を示しています。
|
||||
|
||||
### Adding permissions settings
|
||||
### アクセス許可設定の追加
|
||||
|
||||
{% data reusables.actions.oidc-permissions-token %}
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note**:
|
||||
**注**:
|
||||
|
||||
When the `permissions` key is used, all unspecified permissions are set to _no access_, with the exception of the metadata scope, which always gets _read_ access. As a result, you may need to add other permissions, such as `contents: read`. See [Automatic token authentication](/actions/security-guides/automatic-token-authentication) for more information.
|
||||
`permissions` キーを使用すると、すべての未指定のアクセス許可が "アクセスなし" に設定されます。ただし、メタデータ スコープは例外であり、常に "読み取り" アクセス権を取得します。 その結果、`contents: read` のような他のアクセス許可を追加することが必要になる場合があります。 詳しくは、「[自動トークン認証](/actions/security-guides/automatic-token-authentication)」を参照してください。
|
||||
|
||||
{% endnote %}
|
||||
|
||||
### Requesting the access token
|
||||
### アクセス トークンの要求
|
||||
|
||||
The `hashicorp/vault-action` action receives a JWT from the {% data variables.product.prodname_dotcom %} OIDC provider, and then requests an access token from your HashiCorp Vault instance to retrieve secrets. For more information, see the HashiCorp Vault GitHub Action [documentation](https://github.com/hashicorp/vault-action).
|
||||
`hashicorp/vault-action` アクションは、{% data variables.product.prodname_dotcom %} OIDC プロバイダーから JWT を受け取り、HashiCorp Vault インスタンスにアクセス トークンを要求し、シークレットを取得します。 詳しくは、HashiCorp Vault の GitHub Action の[ドキュメント](https://github.com/hashicorp/vault-action)を参照してください。
|
||||
|
||||
This example demonstrates how to create a job that requests a secret from HashiCorp Vault.
|
||||
この例では、HashiCorp Vault にシークレットを要求するジョブを作成する方法を示しています。
|
||||
|
||||
- `<Vault URL>`: Replace this with the URL of your HashiCorp Vault.
|
||||
- `<Vault Namespace>`: Replace this with the Namespace you've set in HashiCorp Vault. For example: `admin`.
|
||||
- `<Role name>`: Replace this with the role you've set in the HashiCorp Vault trust relationship.
|
||||
- `<Secret-Path>`: Replace this with the path to the secret you're retrieving from HashiCorp Vault. For example: `secret/data/production/ci npmToken`.
|
||||
- `<Vault URL>`: これを HashiCorp Vault の URL に置き換えます。
|
||||
- `<Vault Namespace>`: これを HashiCorp Vault で設定した名前空間に置き換えます。 (例: `admin`)。
|
||||
- `<Role name>`: これを HashiCorp Vault の信頼関係で設定したロールに置き換えます。
|
||||
- `<Secret-Path>`: これを HashiCorp Vault から取得するシークレットのパスに置き換えます。 たとえば、「`secret/data/production/ci npmToken`」のように入力します。
|
||||
|
||||
```yaml{:copy}
|
||||
jobs:
|
||||
@@ -142,19 +146,19 @@ jobs:
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note**:
|
||||
**注**:
|
||||
|
||||
- If your Vault server is not accessible from the public network, consider using a self-hosted runner with other available Vault [auth methods](https://www.vaultproject.io/docs/auth). For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners)."
|
||||
- `<Vault Namespace>` must be set for a Vault Enterprise (including HCP Vault) deployment. For more information, see [Vault namespace](https://www.vaultproject.io/docs/enterprise/namespaces).
|
||||
- Vault サーバーにパブリック ネットワークからアクセスできない場合は、他の使用可能な Vault の[認証方法](https://www.vaultproject.io/docs/auth)でセルフホステッド ランナーを使用することを検討してください。 詳細については、[セルフホステッド ランナー](/actions/hosting-your-own-runners/about-self-hosted-runners)に関する記述をご覧ください。
|
||||
- `<Vault Namespace>` は、Vault Enterprise (HCP Vault を含む) デプロイに対して設定する必要があります。 詳しくは、[Vault 名前空間](https://www.vaultproject.io/docs/enterprise/namespaces)に関するページを参照してください。
|
||||
|
||||
{% endnote %}
|
||||
|
||||
### Revoking the access token
|
||||
### アクセス トークンの取り消し
|
||||
|
||||
By default, the Vault server will automatically revoke access tokens when their TTL is expired, so you don't have to manually revoke the access tokens. However, if you do want to revoke access tokens immediately after your job has completed or failed, you can manually revoke the issued token using the [Vault API](https://www.vaultproject.io/api/auth/token#revoke-a-token-self).
|
||||
既定で、Vault サーバーでは TTL の有効期限が切れたときにアクセス トークンを自動的に取り消します。そのため、アクセス トークンを手動で取り消す必要はありません。 ただし、ジョブが完了または失敗した直後にアクセス トークンを取り消す場合は、[Vault API](https://www.vaultproject.io/api/auth/token#revoke-a-token-self) を使用して発行されたトークンを手動で取り消すことができます。
|
||||
|
||||
1. Set the `exportToken` option to `true` (default: `false`). This exports the issued Vault access token as an environment variable: `VAULT_TOKEN`.
|
||||
2. Add a step to call the [Revoke a Token (Self)](https://www.vaultproject.io/api/auth/token#revoke-a-token-self) Vault API to revoke the access token.
|
||||
1. `exportToken` オプションを `true` (既定値: `false`) に設定します。 これにより、発行された Vault アクセス トークンが環境変数としてエクスポートされます: `VAULT_TOKEN`。
|
||||
2. [トークンの取り消し (自己)](https://www.vaultproject.io/api/auth/token#revoke-a-token-self) Vault API を呼び出してアクセス トークンを取り消すステップを追加します。
|
||||
|
||||
```yaml{:copy}
|
||||
jobs:
|
||||
@@ -183,4 +187,4 @@ jobs:
|
||||
run: |
|
||||
curl -X POST -sv -H "X-Vault-Token: {% raw %}${{ env.VAULT_TOKEN }}{% endraw %}" \
|
||||
<Vault URL>/v1/auth/token/revoke-self
|
||||
```
|
||||
```
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Using the GitHub CLI on a runner
|
||||
title: ランナーでの GitHub CLI の使用
|
||||
shortTitle: Use the GitHub CLI on a runner
|
||||
intro: 'How to use advanced {% data variables.product.prodname_actions %} features for continuous integration (CI).'
|
||||
intro: '継続的インテグレーション (CI) のために高度な {% data variables.product.prodname_actions %} 機能を使用する方法。'
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '> 3.1'
|
||||
@@ -10,40 +10,34 @@ versions:
|
||||
type: how_to
|
||||
topics:
|
||||
- Workflows
|
||||
ms.openlocfilehash: e0787d09cd194de0038d259c1aff777cc91a4a6a
|
||||
ms.sourcegitcommit: bf11c3e08cbb5eab6320e0de35b32ade6d863c03
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: ja-JP
|
||||
ms.lasthandoff: 10/27/2022
|
||||
ms.locfileid: '148111586'
|
||||
---
|
||||
|
||||
{% data reusables.actions.enterprise-github-hosted-runners %}
|
||||
|
||||
## Example overview
|
||||
## サンプルの概要
|
||||
|
||||
{% data reusables.actions.example-workflow-intro-ci %} When this workflow is triggered, it automatically runs a script that checks whether the {% data variables.product.prodname_dotcom %} Docs site has any broken links. If any broken links are found, the workflow uses the {% data variables.product.prodname_dotcom %} CLI to create a {% data variables.product.prodname_dotcom %} issue with the details.
|
||||
{% data reusables.actions.example-workflow-intro-ci %}このワークフローがトリガーされると、{% data variables.product.prodname_dotcom %} Docs サイトに壊れたリンクがあるかどうかを確認するスクリプトが自動的に実行されます。 壊れたリンクが見つかった場合、ワークフローで詳しい情報を含む {% data variables.product.prodname_dotcom %} のイシューが {% data variables.product.prodname_dotcom %} CLI を使用して作成されます。
|
||||
|
||||
{% data reusables.actions.example-diagram-intro %}
|
||||
|
||||
|
||||
|
||||
|
||||
## Features used in this example
|
||||
## この例で使用されている機能
|
||||
|
||||
{% data reusables.actions.example-table-intro %}
|
||||
|
||||
| **Feature** | **Implementation** |
|
||||
| **機能** | **実装** |
|
||||
| --- | --- |
|
||||
{% data reusables.actions.cron-table-entry %}
|
||||
{% data reusables.actions.permissions-table-entry %}
|
||||
{% data reusables.actions.if-conditions-table-entry %}
|
||||
{% data reusables.actions.secrets-table-entry %}
|
||||
{% data reusables.actions.checkout-action-table-entry %}
|
||||
{% data reusables.actions.setup-node-table-entry %}
|
||||
| Using a third-party action: | [`peter-evans/create-issue-from-file`](https://github.com/peter-evans/create-issue-from-file)|
|
||||
| Running shell commands on the runner: | [`run`](/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idstepsrun) |
|
||||
| Running a script on the runner: | Using `script/check-english-links.js` |
|
||||
| Generating an output file: | Piping the output using the `>` operator |
|
||||
| Checking for existing issues using {% data variables.product.prodname_cli %}: | [`gh issue list`](https://cli.github.com/manual/gh_issue_list) |
|
||||
| Commenting on an issue using {% data variables.product.prodname_cli %}: | [`gh issue comment`](https://cli.github.com/manual/gh_issue_comment) |
|
||||
{% data reusables.actions.cron-table-entry %} {% data reusables.actions.permissions-table-entry %} {% data reusables.actions.if-conditions-table-entry %} {% data reusables.actions.secrets-table-entry %} {% data reusables.actions.checkout-action-table-entry %} {% data reusables.actions.setup-node-table-entry %} | サード パーティのアクションの使用: | [`peter-evans/create-issue-from-file`](https://github.com/peter-evans/create-issue-from-file)| | ランナーでのシェル コマンドの実行: | [`run`](/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idstepsrun) | | ランナーでのスクリプトの実行: | `script/check-english-links.js` の使用 | | 出力ファイルの生成: | `>` 演算子を使用した出力のパイプ処理 | | {% data variables.product.prodname_cli %} を使用した既存のイシューの確認: | [`gh issue list`](https://cli.github.com/manual/gh_issue_list) | | {% data variables.product.prodname_cli %} を使用したイシューへのコメント: | [`gh issue comment`](https://cli.github.com/manual/gh_issue_comment) |
|
||||
|
||||
## Example workflow
|
||||
## ワークフローの例
|
||||
|
||||
{% data reusables.actions.example-docs-engineering-intro %} [`check-all-english-links.yml`](https://github.com/github/docs/blob/main/.github/workflows/check-all-english-links.yml).
|
||||
{% data reusables.actions.example-docs-engineering-intro %} [`check-all-english-links.yml`](https://github.com/github/docs/blob/6e01c0653836c10d7e092a17566a2c88b10504ce/.github/workflows/check-all-english-links.yml)。
|
||||
|
||||
{% data reusables.actions.note-understanding-example %}
|
||||
|
||||
@@ -178,15 +172,15 @@ jobs:
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
## Understanding the example
|
||||
## 例の説明
|
||||
|
||||
{% data reusables.actions.example-explanation-table-intro %}
|
||||
|
||||
<table style="table-layout: fixed;">
|
||||
<thead>
|
||||
<tr>
|
||||
<th style="width:60%"><b>Code</b></th>
|
||||
<th style="width:40%"><b>Explanation</b></th>
|
||||
<th style="width:60%">"<b>コード</b>"</th>
|
||||
<th style="width:40%"><b>説明</b></th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
@@ -214,10 +208,10 @@ on:
|
||||
</td>
|
||||
<td>
|
||||
|
||||
Defines the `workflow_dispatch` and `scheduled` as triggers for the workflow:
|
||||
ワークフローのトリガーとして `workflow_dispatch` と `scheduled` を定義します。
|
||||
|
||||
* The `workflow_dispatch` lets you manually run this workflow from the UI. For more information, see [`workflow_dispatch`](/actions/using-workflows/events-that-trigger-workflows#workflow_dispatch).
|
||||
* The `schedule` event lets you use `cron` syntax to define a regular interval for automatically triggering the workflow. For more information, see [`schedule`](/actions/reference/events-that-trigger-workflows#schedule).
|
||||
* `workflow_dispatch` を使用すると、UI からこのワークフローを手動で実行できます。 詳細については、「[`workflow_dispatch`](/actions/using-workflows/events-that-trigger-workflows#workflow_dispatch)」を参照してください。
|
||||
* `schedule` イベントにより、`cron` 構文を使用して、ワークフローを自動的にトリガーするための一定の間隔を定義できます。 詳細については、「[`schedule`](/actions/reference/events-that-trigger-workflows#schedule)」を参照してください。
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
@@ -231,7 +225,7 @@ permissions:
|
||||
</td>
|
||||
<td>
|
||||
|
||||
Modifies the default permissions granted to `GITHUB_TOKEN`. This will vary depending on the needs of your workflow. For more information, see "[Assigning permissions to jobs](/actions/using-jobs/assigning-permissions-to-jobs)."
|
||||
`GITHUB_TOKEN` に付与される既定のアクセス許可を変更します。 これはワークフローのニーズによって異なります。 詳しい情報については、「[ジョブへのアクセス許可の割り当て](/actions/using-jobs/assigning-permissions-to-jobs)」を参照してください。
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
@@ -243,7 +237,7 @@ jobs:
|
||||
</td>
|
||||
<td>
|
||||
|
||||
Groups together all the jobs that run in the workflow file.
|
||||
ワークフロー ファイルで実行されるすべてのジョブをグループ化します。
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
@@ -256,7 +250,7 @@ Groups together all the jobs that run in the workflow file.
|
||||
</td>
|
||||
<td>
|
||||
|
||||
Defines a job with the ID `check_all_english_links`, and the name `Check all links`, that is stored within the `jobs` key.
|
||||
ID `check_all_english_links` と名前 `Check all links` を持つジョブを定義します。これは `jobs` キー内に格納されます。
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
@@ -268,7 +262,7 @@ if: github.repository == 'github/docs-internal'
|
||||
</td>
|
||||
<td>
|
||||
|
||||
Only run the `check_all_english_links` job if the repository is named `docs-internal` and is within the `github` organization. Otherwise, the job is marked as _skipped_.
|
||||
リポジトリが `docs-internal` という名前で、`github` という Organization 内にある場合のみ、`check_all_english_links` ジョブを実行します。 それ以外の場合、ジョブは _"スキップ済み"_ としてマークされます。
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
@@ -280,7 +274,7 @@ runs-on: ubuntu-latest
|
||||
</td>
|
||||
<td>
|
||||
|
||||
Configures the job to run on an Ubuntu Linux runner. This means that the job will execute on a fresh virtual machine hosted by {% data variables.product.prodname_dotcom %}. For syntax examples using other runners, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idruns-on)."
|
||||
Ubuntu Linux ランナーで実行するようにジョブを設定します。 これは、ジョブが {% data variables.product.prodname_dotcom %} によってホストされている新しい仮想マシンで実行されるということです。 他のランナーを使う構文例については、「[{% data variables.product.prodname_actions %} のワークフロー構文](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idruns-on)」を参照してください。
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
@@ -296,7 +290,7 @@ Configures the job to run on an Ubuntu Linux runner. This means that the job wil
|
||||
</td>
|
||||
<td>
|
||||
|
||||
Creates custom environment variables, and redefines the built-in `GITHUB_TOKEN` variable to use a custom [secret](/actions/security-guides/encrypted-secrets). These variables will be referenced later in the workflow.
|
||||
カスタム環境変数を作成し、組み込み `GITHUB_TOKEN` 変数を再定義してカスタム [シークレット](/actions/security-guides/encrypted-secrets)を使用します。 これらの変数は、ワークフローで後から参照されます。
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
@@ -308,7 +302,7 @@ Creates custom environment variables, and redefines the built-in `GITHUB_TOKEN`
|
||||
</td>
|
||||
<td>
|
||||
|
||||
Groups together all the steps that will run as part of the `check_all_english_links` job. Each job in the workflow has its own `steps` section.
|
||||
`check_all_english_links` ジョブの一部として実行されるすべてのステップをグループ化します。 ワークフロー内の各ジョブには、独自の `steps` セクションがあります。
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
@@ -321,7 +315,7 @@ Groups together all the steps that will run as part of the `check_all_english_li
|
||||
</td>
|
||||
<td>
|
||||
|
||||
The `uses` keyword tells the job to retrieve the action named `actions/checkout`. This is an action that checks out your repository and downloads it to the runner, allowing you to run actions against your code (such as testing tools). You must use the checkout action any time your workflow will run against the repository's code or you are using an action defined in the repository.
|
||||
`uses` キーワードは、`actions/checkout` という名前のアクションを取得するようにジョブに指示します。 これは、リポジトリをチェックアウトしてランナーにダウンロードし、コードに対してアクション（テストツールなど）を実行できるようにします。 ワークフローがリポジトリのコードに対して実行されるとき、またはリポジトリで定義されたアクションを使用しているときはいつでも、チェックアウトアクションを使用する必要があります。
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
@@ -337,7 +331,7 @@ The `uses` keyword tells the job to retrieve the action named `actions/checkout`
|
||||
</td>
|
||||
<td>
|
||||
|
||||
This step uses the `actions/setup-node` action to install the specified version of the `node` software package on the runner, which gives you access to the `npm` command.
|
||||
このステップでは、`actions/setup-node` アクションを使用して、指定したバージョンの `node` ソフトウェア パッケージをランナーにインストールします。これにより、`npm` コマンドにアクセスできるようになります。
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
@@ -352,7 +346,7 @@ This step uses the `actions/setup-node` action to install the specified version
|
||||
</td>
|
||||
<td>
|
||||
|
||||
The `run` keyword tells the job to execute a command on the runner. In this case, the `npm ci` and `npm run build` commands are run as separate steps to install and build the Node.js application in the repository.
|
||||
`run` キーワードは、ランナーでコマンドを実行するようにジョブに指示します。 この場合、Node.js アプリケーションをリポジトリにインストールしてビルドするための個別のステップとして、`npm ci` コマンドと `npm run build` コマンドが実行されます。
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
@@ -366,7 +360,7 @@ The `run` keyword tells the job to execute a command on the runner. In this case
|
||||
</td>
|
||||
<td>
|
||||
|
||||
This `run` command executes a script that is stored in the repository at `script/check-english-links.js`, and pipes the output to a file called `broken_links.md`.
|
||||
この `run` コマンドは、リポジトリの `script/check-english-links.js` に保存されているスクリプトを実行し、出力を `broken_links.md` というファイルにパイプで渡します。
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
@@ -385,7 +379,7 @@ This `run` command executes a script that is stored in the repository at `script
|
||||
</td>
|
||||
<td>
|
||||
|
||||
If the `check-english-links.js` script detects broken links and returns a non-zero (failure) exit status, then use a [workflow command](/actions/using-workflows/workflow-commands-for-github-actions#setting-an-output-parameter) to set an output that has the value of the first line of the `broken_links.md` file (this is used the next step).
|
||||
`check-english-links.js` スクリプトで壊れたリンクが検出され、0 以外 (失敗) の終了状態が返された場合は、[ワークフロー コマンド](/actions/using-workflows/workflow-commands-for-github-actions#setting-an-output-parameter)を使用して、`broken_links.md` ファイルの先頭行の値を持つ出力を設定します (これは次のステップで使用されます)。
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
@@ -407,7 +401,7 @@ If the `check-english-links.js` script detects broken links and returns a non-ze
|
||||
</td>
|
||||
<td>
|
||||
|
||||
Uses the `peter-evans/create-issue-from-file` action to create a new {% data variables.product.prodname_dotcom %} issue. This example is pinned to a specific version of the action, using the `b4f9ee0a9d4abbfc6986601d9b1a4f8f8e74c77e` SHA.
|
||||
`peter-evans/create-issue-from-file` アクションを使用して、新しい {% data variables.product.prodname_dotcom %} のイシューを作成します。 この例は、`b4f9ee0a9d4abbfc6986601d9b1a4f8f8e74c77e` SHA を使用して、特定のバージョンのアクションに合わせて固定されています。
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
@@ -435,9 +429,9 @@ Uses the `peter-evans/create-issue-from-file` action to create a new {% data var
|
||||
</td>
|
||||
<td>
|
||||
|
||||
Uses [`gh issue list`](https://cli.github.com/manual/gh_issue_list) to locate the previously created issue from earlier runs. This is [aliased](https://cli.github.com/manual/gh_alias_set) to `gh list-reports` for simpler processing in later steps. To get the issue URL, the `jq` expression processes the resulting JSON output.
|
||||
[`gh issue list`](https://cli.github.com/manual/gh_issue_list) を使用して、以前の実行から以前に作成したイシューを見つけます。 これには、後のステップでの処理を簡単にするために、`gh list-reports` という[別名](https://cli.github.com/manual/gh_alias_set)が付けられます。 イシューの URL を取得するために、`jq` 式で結果の JSON 出力を処理します。
|
||||
|
||||
[`gh issue comment`](https://cli.github.com/manual/gh_issue_comment) is then used to add a comment to the new issue that links to the previous one.
|
||||
次に [`gh issue comment`](https://cli.github.com/manual/gh_issue_comment) を使用して、以前のイシューにリンクするコメントを新しいイシューに追加します。
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
@@ -455,7 +449,7 @@ Uses [`gh issue list`](https://cli.github.com/manual/gh_issue_list) to locate th
|
||||
</td>
|
||||
<td>
|
||||
|
||||
If an issue from a previous run is open and assigned to someone, then use [`gh issue comment`](https://cli.github.com/manual/gh_issue_comment) to add a comment with a link to the new issue.
|
||||
以前の実行でのイシューが未解決であり誰かに割り当てられている場合は、[`gh issue comment`](https://cli.github.com/manual/gh_issue_comment) を使用して、新しいイシューへのリンクを含むコメントを追加します。
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
@@ -476,16 +470,16 @@ If an issue from a previous run is open and assigned to someone, then use [`gh i
|
||||
</td>
|
||||
<td>
|
||||
|
||||
If an issue from a previous run is open and is not assigned to anyone, then:
|
||||
以前の実行でのイシューが未解決であり誰にも割り当てられない場合は、次のようになります。
|
||||
|
||||
* Use [`gh issue comment`](https://cli.github.com/manual/gh_issue_comment) to add a comment with a link to the new issue.
|
||||
* Use [`gh issue close`](https://cli.github.com/manual/gh_issue_close) to close the old issue.
|
||||
* Use [`gh issue edit`](https://cli.github.com/manual/gh_issue_edit) to edit the old issue to remove it from a specific {% data variables.product.prodname_dotcom %} project board.
|
||||
* [`gh issue comment`](https://cli.github.com/manual/gh_issue_comment) を使用して、新しいイシューへのリンクを含むコメントを追加します。
|
||||
* [`gh issue close`](https://cli.github.com/manual/gh_issue_close) を使用して以前のイシューを閉じます。
|
||||
* [`gh issue edit`](https://cli.github.com/manual/gh_issue_edit) を使用して以前のイシューを編集し、特定の {% data variables.product.prodname_dotcom %} プロジェクト ボードから削除します。
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
## Next steps
|
||||
## 次の手順
|
||||
|
||||
{% data reusables.actions.learning-actions %}
|
||||
|
||||
@@ -69,13 +69,10 @@ You can use any machine as a self-hosted runner as long at it meets these requir
|
||||
* The machine has enough hardware resources for the type of workflows you plan to run. The self-hosted runner application itself only requires minimal resources.
|
||||
* If you want to run workflows that use Docker container actions or service containers, you must use a Linux machine and Docker must be installed.
|
||||
|
||||
{% ifversion fpt or ghes > 3.2 or ghec or ghae %}
|
||||
## Autoscaling your self-hosted runners
|
||||
|
||||
You can automatically increase or decrease the number of self-hosted runners in your environment in response to the webhook events you receive. For more information, see "[Autoscaling with self-hosted runners](/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners)."
|
||||
|
||||
{% endif %}
|
||||
|
||||
## Usage limits
|
||||
|
||||
There are some limits on {% data variables.product.prodname_actions %} usage when using self-hosted runners. These limits are subject to change.
|
||||
@@ -249,7 +246,6 @@ codeload.github.com
|
||||
|
||||
{% endnote %}
|
||||
|
||||
|
||||
{% endif %}
|
||||
|
||||
## Self-hosted runner security
|
||||
|
||||
@@ -32,7 +32,7 @@ For more information, see "[About self-hosted runners](/github/automating-your-w
|
||||
{% endwarning %}
|
||||
{% endif %}
|
||||
|
||||
{% ifversion fpt or ghec or ghes > 3.2 %}
|
||||
{% ifversion fpt or ghec or ghes %}
|
||||
|
||||
You can set up automation to scale the number of self-hosted runners. For more information, see "[Autoscaling with self-hosted runners](/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners)."
|
||||
|
||||
|
||||
@@ -5,7 +5,7 @@ intro: You can automatically scale your self-hosted runners in response to webho
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
ghes: '>3.2'
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
type: overview
|
||||
---
|
||||
|
||||
@@ -608,7 +608,7 @@ jobs:
|
||||
|
||||
## `secrets` context
|
||||
|
||||
The `secrets` context contains the names and values of secrets that are available to a workflow run. The `secrets` context is not available for composite actions. For more information about secrets, see "[Encrypted secrets](/actions/security-guides/encrypted-secrets)."
|
||||
The `secrets` context contains the names and values of secrets that are available to a workflow run. The `secrets` context is not available for composite actions due to security reasons. If you want to pass a secret to a composite action, you need to do it explicitly as an input. For more information about secrets, see "[Encrypted secrets](/actions/security-guides/encrypted-secrets)."
|
||||
|
||||
`GITHUB_TOKEN` is a secret that is automatically created for every workflow run, and is always included in the `secrets` context. For more information, see "[Automatic token authentication](/actions/security-guides/automatic-token-authentication)."
|
||||
|
||||
|
||||
@@ -87,9 +87,7 @@ The following table shows the permissions granted to the `GITHUB_TOKEN` by defau
|
||||
| issues | read/write | none | read |
|
||||
| metadata | read | read | read |
|
||||
| packages | read/write | none | read |
|
||||
{%- ifversion fpt or ghec or ghes > 3.2 or ghae %}
|
||||
| pages | read/write | none | read |
|
||||
{%- endif %}
|
||||
| pull-requests | read/write | none | read |
|
||||
| repository-projects | read/write | none | read |
|
||||
| security-events | read/write | none | read |
|
||||
|
||||
@@ -7,6 +7,8 @@ redirect_from:
|
||||
- /actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets
|
||||
- /actions/configuring-and-managing-workflows/using-variables-and-secrets-in-a-workflow
|
||||
- /actions/reference/encrypted-secrets
|
||||
- /actions/managing-workflows/storing-secrets
|
||||
|
||||
miniTocMaxHeadingLevel: 3
|
||||
versions:
|
||||
fpt: '*'
|
||||
|
||||
@@ -1,50 +1,49 @@
|
||||
---
|
||||
title: より大きなランナーへのアクセスの制御
|
||||
intro: 'Organization または Enterprise に追加された {% data variables.actions.hosted_runner %} へのアクセスを、ポリシーを使って制限できます。'
|
||||
title: Controlling access to larger runners
|
||||
shortTitle: 'Control access to {% data variables.actions.hosted_runner %}s'
|
||||
intro: 'You can use policies to limit access to {% data variables.actions.hosted_runner %}s that have been added to an organization or enterprise.'
|
||||
product: '{% data reusables.gated-features.hosted-runners %}'
|
||||
versions:
|
||||
feature: actions-hosted-runners
|
||||
type: tutorial
|
||||
shortTitle: 'Controlling access to {% data variables.actions.hosted_runner %}s'
|
||||
ms.openlocfilehash: 6761f05ef04d18ebba7b9ef8a2894d7effd2622b
|
||||
ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: ja-JP
|
||||
ms.lasthandoff: 09/09/2022
|
||||
ms.locfileid: '147764022'
|
||||
---
|
||||
{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %}
|
||||
|
||||
## ランナー グループについて
|
||||
{% data reusables.actions.enterprise-beta %}
|
||||
{% data reusables.actions.enterprise-github-hosted-runners %}
|
||||
|
||||
{% data reusables.actions.about-runner-groups %} {% ifversion fpt %}詳しくは、[{% data variables.product.prodname_ghe_cloud %} のドキュメント](/enterprise-cloud@latest/actions/using-github-hosted-runners/controlling-access-to-larger-runners)をご覧ください。{% endif %}
|
||||
## About runner groups
|
||||
|
||||
{% data reusables.actions.about-runner-groups %} {% ifversion fpt %}For more information, see the [{% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/actions/using-github-hosted-runners/controlling-access-to-larger-runners).{% endif %}
|
||||
|
||||
{% ifversion ghec or ghes or ghae %}
|
||||
|
||||
## Organization のランナー グループを作成する
|
||||
## Creating a runner group for an organization
|
||||
|
||||
{% data reusables.actions.hosted-runner-security-admonition %} {% data reusables.actions.creating-a-runner-group-for-an-organization %}
|
||||
{% data reusables.actions.hosted-runner-security-admonition %}
|
||||
{% data reusables.actions.creating-a-runner-group-for-an-organization %}
|
||||
|
||||
## Enterprise のランナー グループを作成する
|
||||
## Creating a runner group for an enterprise
|
||||
|
||||
{% data reusables.actions.hosted-runner-security-admonition %} {% data reusables.actions.creating-a-runner-group-for-an-enterprise %}
|
||||
{% data reusables.actions.hosted-runner-security-admonition %}
|
||||
{% data reusables.actions.creating-a-runner-group-for-an-enterprise %}
|
||||
|
||||
{% endif %}
|
||||
|
||||
## ランナー グループのアクセス ポリシーを変更する
|
||||
## Changing the access policy of a runner group
|
||||
|
||||
{% data reusables.actions.hosted-runner-security-admonition %} {% data reusables.actions.changing-the-access-policy-of-a-runner-group %}
|
||||
{% data reusables.actions.hosted-runner-security-admonition %}
|
||||
{% data reusables.actions.changing-the-access-policy-of-a-runner-group %}
|
||||
|
||||
## ランナー グループの名前を変更する
|
||||
## Changing the name of a runner group
|
||||
|
||||
{% data reusables.actions.changing-the-name-of-a-runner-group %}
|
||||
|
||||
{% ifversion ghec or ghes or ghae %}
|
||||
## ランナーをグループに移動する
|
||||
## Moving a runner to a group
|
||||
|
||||
{% data reusables.actions.moving-a-runner-to-a-group %}
|
||||
|
||||
## ランナー グループを削除する
|
||||
## Removing a runner group
|
||||
|
||||
{% data reusables.actions.removing-a-runner-group %}
|
||||
|
||||
|
||||
@@ -1,11 +1,11 @@
|
||||
---
|
||||
title: Using larger runners
|
||||
shortTitle: 'Larger runners'
|
||||
shortTitle: Larger runners
|
||||
intro: '{% data variables.product.prodname_dotcom %} offers larger runners with more RAM and CPU.'
|
||||
miniTocMaxHeadingLevel: 3
|
||||
product: '{% data reusables.gated-features.hosted-runners %}'
|
||||
versions:
|
||||
feature: 'actions-hosted-runners'
|
||||
feature: actions-hosted-runners
|
||||
---
|
||||
|
||||
## Overview of {% data variables.actions.hosted_runner %}s
|
||||
|
||||
@@ -139,8 +139,8 @@ The following table shows which toolkit functions are available within a workflo
|
||||
| Toolkit function | Equivalent workflow command |
|
||||
| ----------------- | ------------- |
|
||||
| `core.addPath` | Accessible using environment file `GITHUB_PATH` |
|
||||
| `core.debug` | `debug` |{% ifversion fpt or ghes > 3.2 or ghae or ghec %}
|
||||
| `core.notice` | `notice` |{% endif %}
|
||||
| `core.debug` | `debug` |
|
||||
| `core.notice` | `notice` |
|
||||
| `core.error` | `error` |
|
||||
| `core.endGroup` | `endgroup` |
|
||||
| `core.exportVariable` | Accessible using environment file `GITHUB_ENV` |
|
||||
@@ -216,8 +216,6 @@ Write-Output "::debug::Set the Octocat variable"
|
||||
|
||||
{% endpowershell %}
|
||||
|
||||
{% ifversion fpt or ghes > 3.2 or ghae or ghec %}
|
||||
|
||||
## Setting a notice message
|
||||
|
||||
Creates a notice message and prints the message to the log. {% data reusables.actions.message-annotation-explanation %}
|
||||
@@ -245,7 +243,6 @@ Write-Output "::notice file=app.js,line=1,col=5,endColumn=7::Missing semicolon"
|
||||
```
|
||||
|
||||
{% endpowershell %}
|
||||
{% endif %}
|
||||
|
||||
## Setting a warning message
|
||||
|
||||
@@ -584,6 +581,8 @@ console.log("The running PID from the main action is: " + process.env.STATE_pro
|
||||
|
||||
During the execution of a workflow, the runner generates temporary files that can be used to perform certain actions. The path to these files are exposed via environment variables. You will need to use UTF-8 encoding when writing to these files to ensure proper processing of the commands. Multiple commands can be written to the same file, separated by newlines.
|
||||
|
||||
Most commands in the following examples use double quotes for echoing strings, which will attempt to interpolate characters like `$` for shell variable names. To always use literal values in quoted strings, you can use single quotes instead.
|
||||
|
||||
{% powershell %}
|
||||
|
||||
{% note %}
|
||||
|
||||
@@ -32,7 +32,7 @@ The name of your workflow. {% data variables.product.prodname_dotcom %} displays
|
||||
{% ifversion actions-run-name %}
|
||||
## `run-name`
|
||||
|
||||
The name for workflow runs generated from the workflow. {% data variables.product.prodname_dotcom %} displays the workflow run name in the list of workflow runs on your repository's "Actions" tab. If you omit `run-name`, the run name is set to event-specific information for the workflow run. For example, for a workflow triggered by a `push` or `pull_request` event, it is set as the commit message.
|
||||
The name for workflow runs generated from the workflow. {% data variables.product.prodname_dotcom %} displays the workflow run name in the list of workflow runs on your repository's "Actions" tab. If `run-name` is omitted or is only whitespace, then the run name is set to event-specific information for the workflow run. For example, for a workflow triggered by a `push` or `pull_request` event, it is set as the commit message.
|
||||
|
||||
This value can include expressions and can reference the [`github`](/actions/learn-github-actions/contexts#github-context) and [`inputs`](/actions/learn-github-actions/contexts#inputs-context) contexts.
|
||||
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Configuring dependency review for your appliance
|
||||
shortTitle: Configuring dependency review
|
||||
intro: 'To helps users understand dependency changes when reviewing pull requests, you can enable, configure, and disable dependency review for {% data variables.location.product_location %}.'
|
||||
intro: 'To helps users understand dependency changes when reviewing pull requests, you can enable, configure, and disable dependency review for {% data variables.location.product_location %}.'
|
||||
product: '{% data reusables.gated-features.dependency-review %}'
|
||||
miniTocMaxHeadingLevel: 3
|
||||
versions:
|
||||
@@ -14,8 +14,6 @@ topics:
|
||||
- Security
|
||||
---
|
||||
|
||||
{% data reusables.dependency-review.beta %}
|
||||
|
||||
## About dependency review
|
||||
|
||||
{% data reusables.dependency-review.feature-overview %}
|
||||
|
||||
@@ -15,6 +15,6 @@ topics:
|
||||
|
||||
You can allow users to identify their projects' dependencies by {% ifversion ghes %}enabling{% elsif ghae %}using{% endif %} the dependency graph for {% data variables.location.product_location %}. For more information, see "{% ifversion ghes %}[Enabling the dependency graph for your enterprise](/admin/code-security/managing-supply-chain-security-for-your-enterprise/enabling-the-dependency-graph-for-your-enterprise){% elsif ghae %}[About the dependency graph](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph){% endif %}."
|
||||
|
||||
You can also allow users on {% data variables.location.product_location %} to find and fix vulnerabilities in their code dependencies by enabling {% data variables.product.prodname_dependabot_alerts %}{% ifversion ghes > 3.2 %} and {% data variables.product.prodname_dependabot_updates %}{% endif %}. For more information, see "[Enabling {% data variables.product.prodname_dependabot %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)."
|
||||
You can also allow users on {% data variables.location.product_location %} to find and fix vulnerabilities in their code dependencies by enabling {% data variables.product.prodname_dependabot_alerts %}{% ifversion ghes %} and {% data variables.product.prodname_dependabot_updates %}{% endif %}. For more information, see "[Enabling {% data variables.product.prodname_dependabot %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)."
|
||||
|
||||
After you enable {% data variables.product.prodname_dependabot_alerts %}, you can view vulnerability data from the {% data variables.product.prodname_advisory_database %} on {% data variables.location.product_location %} and manually sync the data. For more information, see "[Viewing the vulnerability data for your enterprise](/admin/code-security/managing-supply-chain-security-for-your-enterprise/viewing-the-vulnerability-data-for-your-enterprise)."
|
||||
|
||||
@@ -16,7 +16,7 @@ topics:
|
||||
|
||||
{% data reusables.dependabot.about-the-dependency-graph %} For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)"
|
||||
|
||||
After you enable the dependency graph for your enterprise, you can enable {% data variables.product.prodname_dependabot %} to detect insecure dependencies in your repository{% ifversion ghes > 3.2 %} and automatically fix the vulnerabilities{% endif %}. For more information, see "[Enabling {% data variables.product.prodname_dependabot %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)."
|
||||
After you enable the dependency graph for your enterprise, you can enable {% data variables.product.prodname_dependabot %} to detect insecure dependencies in your repository{% ifversion ghes %} and automatically fix the vulnerabilities{% endif %}. For more information, see "[Enabling {% data variables.product.prodname_dependabot %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)."
|
||||
|
||||
{% ifversion ghes %}
|
||||
You can enable the dependency graph via the {% data variables.enterprise.management_console %} or the administrative shell. We recommend using the {% data variables.enterprise.management_console %} unless {% data variables.location.product_location %} uses clustering.
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Enabling Dependabot for your enterprise
|
||||
intro: 'You can allow users of {% data variables.location.product_location %} to find and fix vulnerabilities in code dependencies by enabling {% data variables.product.prodname_dependabot_alerts %}{% ifversion ghes > 3.2 %} and {% data variables.product.prodname_dependabot_updates %}{% endif %}.'
|
||||
intro: 'You can allow users of {% data variables.location.product_location %} to find and fix vulnerabilities in code dependencies by enabling {% data variables.product.prodname_dependabot_alerts %}{% ifversion ghes %} and {% data variables.product.prodname_dependabot_updates %}{% endif %}.'
|
||||
miniTocMaxHeadingLevel: 3
|
||||
shortTitle: Dependabot
|
||||
redirect_from:
|
||||
@@ -26,7 +26,7 @@ topics:
|
||||
|
||||
## About {% data variables.product.prodname_dependabot %} for {% data variables.product.product_name %}
|
||||
|
||||
{% data variables.product.prodname_dependabot %} helps users of {% data variables.location.product_location %} find and fix vulnerabilities in their dependencies.{% ifversion ghes > 3.2 %} You can enable {% data variables.product.prodname_dependabot_alerts %} to notify users about vulnerable dependencies and {% data variables.product.prodname_dependabot_updates %} to fix the vulnerabilities and keep dependencies updated to the latest version.
|
||||
{% data variables.product.prodname_dependabot %} helps users of {% data variables.location.product_location %} find and fix vulnerabilities in their dependencies.{% ifversion ghes %} You can enable {% data variables.product.prodname_dependabot_alerts %} to notify users about vulnerable dependencies and {% data variables.product.prodname_dependabot_updates %} to fix the vulnerabilities and keep dependencies updated to the latest version.
|
||||
|
||||
### About {% data variables.product.prodname_dependabot_alerts %}
|
||||
{% endif %}
|
||||
@@ -51,7 +51,7 @@ When {% data variables.location.product_location %} receives information about a
|
||||
|
||||
For repositories with {% data variables.product.prodname_dependabot_alerts %} enabled, scanning is triggered on any push to the default branch that contains a manifest file or lock file. Additionally, when a new vulnerability record is added to {% data variables.location.product_location %}, {% data variables.product.product_name %} scans all existing repositories on {% data variables.location.product_location %} and generates alerts for any repository that is vulnerable. For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)."
|
||||
|
||||
{% ifversion ghes > 3.2 %}
|
||||
{% ifversion ghes %}
|
||||
### About {% data variables.product.prodname_dependabot_updates %}
|
||||
|
||||
{% data reusables.dependabot.beta-security-and-version-updates %}
|
||||
@@ -124,7 +124,7 @@ After you enable {% data variables.product.prodname_dependabot_alerts %} for you
|
||||
|
||||
|
||||
{% endif %}
|
||||
{% ifversion ghes > 3.2 %}
|
||||
{% ifversion ghes %}
|
||||
|
||||
When you enable {% data variables.product.prodname_dependabot_alerts %}, you should consider also setting up {% data variables.product.prodname_actions %} for {% data variables.product.prodname_dependabot_security_updates %}. This feature allows developers to fix vulnerabilities in their dependencies. For more information, see "[Managing self-hosted runners for {% data variables.product.prodname_dependabot_updates %} on your enterprise](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/managing-self-hosted-runners-for-dependabot-updates)."
|
||||
|
||||
|
||||
@@ -2,7 +2,7 @@
|
||||
title: Configuring host keys for your instance
|
||||
shortTitle: Configure host keys
|
||||
intro: 'You can increase the security of {% data variables.location.product_location %} by configuring the algorithms that your instance uses to generate and advertise host keys for incoming SSH connections.'
|
||||
permissions: "Site administrators can configure the host keys for a {% data variables.product.product_name %} instance."
|
||||
permissions: 'Site administrators can configure the host keys for a {% data variables.product.product_name %} instance.'
|
||||
versions:
|
||||
ghes: '>= 3.6'
|
||||
type: how_to
|
||||
|
||||
@@ -2,7 +2,7 @@
|
||||
title: Configuring SSH connections to your instance
|
||||
shortTitle: Configure SSH connections
|
||||
intro: 'You can increase the security of {% data variables.location.product_location %} by configuring the SSH algorithms that clients can use to establish a connection.'
|
||||
permissions: "Site administrators can configure SSH connections to a {% data variables.product.product_name %} instance."
|
||||
permissions: 'Site administrators can configure SSH connections to a {% data variables.product.product_name %} instance.'
|
||||
versions:
|
||||
ghes: '>= 3.6'
|
||||
type: how_to
|
||||
|
||||
@@ -1,26 +1,21 @@
|
||||
---
|
||||
title: リポジトリのキャッシュについて
|
||||
intro: リポジトリのキャッシュを使用して、分散チームと CI ファームでの Git 読み取り操作のパフォーマンスを向上させることができます。
|
||||
title: About repository caching
|
||||
intro: You can increase the performance of Git read operations for distributed teams and CI farms with repository caching.
|
||||
versions:
|
||||
ghes: '>=3.3'
|
||||
ghes: '*'
|
||||
type: overview
|
||||
topics:
|
||||
- Enterprise
|
||||
ms.openlocfilehash: 06a0dd3ba202c73f1ee035d61f7865fadd13b415
|
||||
ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: ja-JP
|
||||
ms.lasthandoff: 09/11/2022
|
||||
ms.locfileid: '145120645'
|
||||
---
|
||||
|
||||
{% data reusables.enterprise.repository-caching-release-phase %}
|
||||
|
||||
世界中にチームと CI ファームがある場合、{% data variables.product.prodname_ghe_server %} のプライマリ インスタンスのパフォーマンスが低下する可能性があります。 アクティブ geo レプリカを使うと読み取り要求のパフォーマンスが向上しますが、書き込みスループットが制限されます。 プライマリ インスタンスの負荷を軽減し、書き込みスループットのパフォーマンスを向上させるには、これらの地理的に分散したクライアントの近くに配置されたリポジトリの非同期読み取り専用ミラーであるリポジトリ キャッシュを構成できます。
|
||||
If you have teams and CI farms located around the world, you may experience reduced performance on your primary {% data variables.product.prodname_ghe_server %} instance. While active geo-replicas can improve the performance of read requests, this comes at the cost of limiting write throughput. To reduce load on your primary instance and improve write throughput performance, you can configure a repository cache, an asynchronous read-only mirror of repositories located near these geographically-distributed clients.
|
||||
|
||||
リポジトリ キャッシュを使うと、CI ファームや分散チームの近くにリポジトリ データが提供されるため、{% data variables.product.product_name %} は、複数のクライアントにサービスを提供するために、同じ Git データを長距離ネットワーク リンク経由で何回も送信する必要がなくなります。 たとえば、プライマリ インスタンスが北米にあり、アジアの多くの場所でもそれを利用している場合は、アジアの CI ランナーが使用するためのリポジトリ キャッシュをアジアに設けるとメリットがあります。
|
||||
A repository cache eliminates the need for {% data variables.product.product_name %} to transmit the same Git data over a long-haul network link multiple times to serve multiple clients, by serving your repository data close to CI farms and distributed teams. For instance, if your primary instance is in North America and you also have a large presence in Asia, you will benefit from setting up the repository cache in Asia for use by CI runners there.
|
||||
|
||||
リポジトリ キャッシュは、プライマリ インスタンス (単一インスタンスでも、geo レプリケートされたインスタンスのセットでも) で、Git データの変更をリッスンします。 CI ファームや他の読み取り負荷の高いコンシューマーは、プライマリ インスタンスの代わりにリポジトリ キャッシュからクローンしてフェッチします。 変更は、クライアントごとに 1 回ではなく、キャッシュ インスタンスごとに 1 回ずつ、定期的にネットワーク全体に反映されます。 通常、Git データは、データがプライマリ インスタンスにプッシュされてから数分以内に、リポジトリ キャッシュで使用できるようになります。 {% ifversion ghes > 3.3 %}CI システムは、[`cache_sync` Webhook](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#cache_sync) を使うことで、キャッシュで使用可能になったデータに対応できます。{% endif %}
|
||||
The repository cache listens to the primary instance, whether that's a single instance or a geo-replicated set of instances, for changes to Git data. CI farms and other read-heavy consumers clone and fetch from the repository cache instead of the primary instance. Changes are propagated across the network, at periodic intervals, once per cache instance rather than once per client. Git data will typically be visible on the repository cache within several minutes after the data is pushed to the primary instance. {% ifversion ghes > 3.3 %}The [`cache_sync` webhook](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#cache_sync) can be used by CI systems to react to data being available in the cache.{% endif %}
|
||||
|
||||
リポジトリ キャッシュと同期できるようにするリポジトリを、きめ細かく制御できます。 Git データは、ユーザーが指定した場所にのみレプリケートされます。
|
||||
You have fine-grained control over which repositories are allowed to sync to the repository cache. Git data will only be replicated to the locations you specify.
|
||||
|
||||
{% data reusables.enterprise.repository-caching-config-summary %}詳しくは、「[リポジトリ キャッシュを構成する](/admin/enterprise-management/caching-repositories/configuring-a-repository-cache)」をご覧ください。
|
||||
{% data reusables.enterprise.repository-caching-config-summary %} For more information, see "[Configuring a repository cache](/admin/enterprise-management/caching-repositories/configuring-a-repository-cache)."
|
||||
|
||||
@@ -1,107 +1,105 @@
|
||||
---
|
||||
title: リポジトリ キャッシュの構成
|
||||
intro: リポジトリ キャッシュを構成するには、新しいアプライアンスを作成し、リポジトリ キャッシュをプライマリ アプライアンスに接続し、リポジトリ キャッシュに対するリポジトリ ネットワークのレプリケーションを構成します。
|
||||
title: Configuring a repository cache
|
||||
intro: 'You can configure a repository cache by creating a new appliance, connecting the repository cache to your primary appliance, and configuring replication of repository networks to the repository cache.'
|
||||
versions:
|
||||
ghes: '>=3.3'
|
||||
ghes: '*'
|
||||
type: how_to
|
||||
topics:
|
||||
- Enterprise
|
||||
ms.openlocfilehash: dced49e1e6795407e2e41f12275a310c3a98aaf1
|
||||
ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: ja-JP
|
||||
ms.lasthandoff: 09/10/2022
|
||||
ms.locfileid: '146332011'
|
||||
---
|
||||
|
||||
{% data reusables.enterprise.repository-caching-release-phase %}
|
||||
|
||||
## リポジトリ キャッシュの構成について
|
||||
## About configuration for repository caching
|
||||
|
||||
{% data reusables.enterprise.repository-caching-config-summary %}次に、リポジトリ キャッシュにレプリケートされるリポジトリ ネットワークを管理するデータの場所ポリシーを設定できます。
|
||||
{% data reusables.enterprise.repository-caching-config-summary %} Then, you can set data location policies that govern which repository networks are replicated to the repository cache.
|
||||
|
||||
クラスタリングでは、リポジトリ キャッシュはサポートされていません。
|
||||
Repository caching is not supported with clustering.
|
||||
|
||||
## リポジトリ キャッシュの DNS
|
||||
## DNS for repository caches
|
||||
|
||||
プライマリ インスタンスとリポジトリ キャッシュの DNS 名は異なっている必要があります。 たとえば、プライマリ インスタンスが `github.example.com` にある場合は、キャッシュ名は `europe-ci.github.example.com` や `github.asia.example.com` に決定できます。
|
||||
The primary instance and repository cache should have different DNS names. For example, if your primary instance is at `github.example.com`, you might decide to name a cache `europe-ci.github.example.com` or `github.asia.example.com`.
|
||||
|
||||
CI マシンで、プライマリ インスタンスではなくリポジトリ キャッシュからフェッチするには、Git の `url.<base>.insteadOf` 構成設定を使用できます。 詳細については、Git ドキュメントにある「[`git-config`](https://git-scm.com/docs/git-config#Documentation/git-config.txt-urlltbasegtinsteadOf)」を参照してください。
|
||||
To have your CI machines fetch from the repository cache instead of the primary instance, you can use Git's `url.<base>.insteadOf` configuration setting. For more information, see [`git-config`](https://git-scm.com/docs/git-config#Documentation/git-config.txt-urlltbasegtinsteadOf) in the Git documentation.
|
||||
|
||||
たとえば、CI マシンのグローバル `.gitconfig` には、次の行が含まれます。
|
||||
For example, the global `.gitconfig` for the CI machine would include these lines.
|
||||
|
||||
```
|
||||
[url "https://europe-ci.github.example.com/"]
|
||||
insteadOf = https://github.example.com/
|
||||
insteadOf = https://github.example.com/
|
||||
```
|
||||
|
||||
次に、`https://github.example.com/myorg/myrepo` をフェッチするように Git に要求すると、代わりに `https://europe-ci.github.example.com/myorg/myrepo` からフェッチされます。
|
||||
Then, when told to fetch `https://github.example.com/myorg/myrepo`, Git will instead fetch from `https://europe-ci.github.example.com/myorg/myrepo`.
|
||||
|
||||
## リポジトリ キャッシュの構成
|
||||
## Configuring a repository cache
|
||||
|
||||
{% ifversion ghes = 3.3 %}
|
||||
1. プライマリ {% data variables.product.prodname_ghe_server %} アプライアンスで、リポジトリ キャッシュの機能フラグを有効にします。
|
||||
1. On your primary {% data variables.product.prodname_ghe_server %} appliance, enable the feature flag for repository caching.
|
||||
|
||||
```
|
||||
$ ghe-config cluster.cache-enabled true
|
||||
```
|
||||
{%- endif %}
|
||||
1. 新しい {% data variables.product.prodname_ghe_server %} アプライアンスを希望するプラットフォームにセットアップします。 このアプライアンスがリポジトリ キャッシュになります。 詳細については、「[{% data variables.product.prodname_ghe_server %} インスタンスをセットアップする](/admin/guides/installation/setting-up-a-github-enterprise-server-instance)」を参照してください。
|
||||
1. Set up a new {% data variables.product.prodname_ghe_server %} appliance on your desired platform. This appliance will be your repository cache. For more information, see "[Setting up a {% data variables.product.prodname_ghe_server %} instance](/admin/guides/installation/setting-up-a-github-enterprise-server-instance)."
|
||||
{% data reusables.enterprise_installation.replica-steps %}
|
||||
1. SSH を使用して、リポジトリ キャッシュの IP アドレスに接続します。
|
||||
1. Connect to the repository cache's IP address using SSH.
|
||||
|
||||
```shell
|
||||
$ ssh -p 122 admin@<em>REPLICA IP</em>
|
||||
$ ssh -p 122 admin@REPLICA-IP
|
||||
```
|
||||
{%- ifversion ghes = 3.3 %}
|
||||
1. キャッシュ レプリカで、リポジトリ キャッシュの機能フラグを有効にします。
|
||||
1. On your cache replica, enable the feature flag for repository caching.
|
||||
|
||||
```
|
||||
$ ghe-config cluster.cache-enabled true
|
||||
```
|
||||
{%- endif %} {% data reusables.enterprise_installation.generate-replication-key-pair %} {% data reusables.enterprise_installation.add-ssh-key-to-primary %}
|
||||
1. プライマリへの接続を確認し、リポジトリ キャッシュに対してレプリカ モードを有効にするには、`ghe-repl-setup` をもう一度実行します。
|
||||
{%- endif %}
|
||||
{% data reusables.enterprise_installation.generate-replication-key-pair %}
|
||||
{% data reusables.enterprise_installation.add-ssh-key-to-primary %}
|
||||
1. To verify the connection to the primary and enable replica mode for the repository cache, run `ghe-repl-setup` again.
|
||||
|
||||
```shell
|
||||
$ ghe-repl-setup <em>PRIMARY IP</em>
|
||||
$ ghe-repl-setup PRIMARY-IP
|
||||
```
|
||||
|
||||
1. *CACHE-LOCATION* を、キャッシュがデプロイされているリージョンなどの英数字識別子に置き換えて、リポジトリ キャッシュに対して `cache_location` を設定します。 また、このキャッシュのデータセンター名も設定します。新しいキャッシュでは、同じデータセンター内の別のキャッシュからシード処理を試みます。
|
||||
1. Set a `cache_location` for the repository cache, replacing *CACHE-LOCATION* with an alphanumeric identifier, such as the region where the cache is deployed. Also set a datacenter name for this cache; new caches will attempt to seed from another cache in the same datacenter.
|
||||
|
||||
```shell
|
||||
$ ghe-repl-node --cache <em>CACHE-LOCATION</em> --datacenter <em>REPLICA-DC-NAME</em>
|
||||
$ ghe-repl-node --cache CACHE-LOCATION --datacenter REPLICA-DC-NAME
|
||||
```
|
||||
|
||||
{% data reusables.enterprise_installation.replication-command %} {% data reusables.enterprise_installation.verify-replication-channel %}
|
||||
1. リポジトリ キャッシュへのリポジトリ ネットワークのレプリケーションを有効にするには、データの場所ポリシーを設定します。 詳細については、「[データの場所ポリシー](#data-location-policies)」を参照してください。
|
||||
{% data reusables.enterprise_installation.replication-command %}
|
||||
{% data reusables.enterprise_installation.verify-replication-channel %}
|
||||
1. To enable replication of repository networks to the repository cache, set a data location policy. For more information, see "[Data location policies](#data-location-policies)."
|
||||
|
||||
## データの場所ポリシー
|
||||
## Data location policies
|
||||
|
||||
`spokesctl cache-policy` コマンドでリポジトリのデータの場所ポリシーを構成して、データの局所性を制御できます。 データの場所ポリシーによって、どのリポジトリ ネットワークがどのリポジトリ キャッシュにレプリケートされているかが決まります。 既定では、データの場所ポリシーが構成されるまで、どのリポジトリ キャッシュにもリポジトリ ネットワークはレプリケートされません。
|
||||
You can control data locality by configuring data location policies for your repositories with the `spokesctl cache-policy` command. Data location policies determine which repository networks are replicated on which repository caches. By default, no repository networks will be replicated on any repository caches until a data location policy is configured.
|
||||
|
||||
データの場所ポリシーは、Git コンテンツにのみ影響します。 Issue や pull request コメントなどのデータベース内のコンテンツは、ポリシーに関係なくすべてのノードにレプリケートされます。
|
||||
Data location policies affect only Git content. Content in the database, such as issues and pull request comments, will be replicated to all nodes regardless of policy.
|
||||
|
||||
{% note %}
|
||||
|
||||
**注:** データの場所ポリシーは、アクセス制御と同じではありません。 リポジトリにアクセスできるユーザーを制御するには、リポジトリ ロールを使用する必要があります。 リポジトリ ロールの詳細については、「[Organization のリポジトリ ロール](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)」を参照してください。
|
||||
**Note:** Data location policies are not the same as access control. You must use repository roles to control which users may access a repository. For more information about repository roles, see "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)."
|
||||
|
||||
{% endnote %}
|
||||
|
||||
`--default` フラグを使用して、すべてのネットワークをレプリケートするようにポリシーを構成できます。 たとえば、次のコマンドでは、すべてのリポジトリ ネットワークの 1 つのコピーを、`cache_location` が "kansas" であるリポジトリ キャッシュのセットにレプリケートするポリシーが作成されます。
|
||||
You can configure a policy to replicate all networks with the `--default` flag. For example, this command will create a policy to replicate a single copy of every repository network to the set of repository caches whose `cache_location` is "kansas".
|
||||
|
||||
```
|
||||
$ ghe-spokesctl cache-policy set --default 1 kansas
|
||||
```
|
||||
|
||||
リポジトリ ネットワークのレプリケーションを構成するには、ネットワークのルートであるリポジトリを指定します。 リポジトリ ネットワークには、リポジトリとリポジトリのすべてのフォークが含まれます。 ネットワーク全体をレプリケートしないと、ネットワークの一部をレプリケートすることはできません。
|
||||
To configure replication for a repository network, specify the repository that is the root of the network. A repository network includes a repository and all of the repository's forks. You cannot replicate part of a network without replicating the whole network.
|
||||
|
||||
```
|
||||
$ ghe-spokesctl cache-policy set <owner/repository> 1 kansas
|
||||
```
|
||||
|
||||
ネットワークのレプリカ数を 0 に指定すると、すべてのネットワークをレプリケートし、特定のネットワークを除外するポリシーをオーバーライドできます。 たとえば、次のコマンドでは、場所 "kansas" 内のリポジトリ キャッシュに、そのネットワークのコピーを含めることができないことが指定されます。
|
||||
You can override a policy that replicates all networks and exclude specific networks by specifying a replica count of zero for the network. For example, this command specifies that any repository cache in location "kansas" cannot contain any copies of that network.
|
||||
|
||||
```
|
||||
$ ghe-spokesctl cache-policy set <owner/repository> 0 kansas
|
||||
```
|
||||
|
||||
特定のキャッシュの場所で、1 より大きいレプリカ数はサポートされていません。
|
||||
Replica counts greater than one in a given cache location are not supported.
|
||||
|
||||
@@ -1,18 +1,13 @@
|
||||
---
|
||||
title: リポジトリのキャッシュ
|
||||
intro: ユーザーと CI クライアントに近い読み取り専用ミラーを提供するリポジトリ キャッシュを使用して、地理的に分散した Team のパフォーマンスを向上させることができます。
|
||||
title: Caching repositories
|
||||
intro: 'You can improve performance for your geographically-distributed team with repository caching, which provides read-only mirrors close to your users and CI clients.'
|
||||
versions:
|
||||
ghes: '>=3.3'
|
||||
ghes: '*'
|
||||
topics:
|
||||
- Enterprise
|
||||
children:
|
||||
- /about-repository-caching
|
||||
- /configuring-a-repository-cache
|
||||
ms.openlocfilehash: 4c019db4ea99bc2383c4496fb9632e8723a7a02b
|
||||
ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: ja-JP
|
||||
ms.lasthandoff: 09/11/2022
|
||||
ms.locfileid: '145112798'
|
||||
---
|
||||
|
||||
{% data reusables.enterprise.repository-caching-release-phase %}
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Geo-replicationについて
|
||||
intro: '{% data variables.product.prodname_ghe_server %} 上の Geo-replication は、地理的に分散したデータセンターからの要求を満たすために、複数のアクティブなレプリカを使用します。'
|
||||
title: About geo-replication
|
||||
intro: 'Geo-replication on {% data variables.product.prodname_ghe_server %} uses multiple active replicas to fulfill requests from geographically distributed data centers.'
|
||||
redirect_from:
|
||||
- /enterprise/admin/installation/about-geo-replication
|
||||
- /enterprise/admin/enterprise-management/about-geo-replication
|
||||
@@ -11,32 +11,26 @@ type: overview
|
||||
topics:
|
||||
- Enterprise
|
||||
- High availability
|
||||
ms.openlocfilehash: 0e4e2feb161dd897172385bf25cf997268527fd3
|
||||
ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: ja-JP
|
||||
ms.lasthandoff: 09/05/2022
|
||||
ms.locfileid: '146332809'
|
||||
---
|
||||
アクティブなレプリカが複数あれば、最も近いレプリカへの距離を短くできます。 たとえばサンフランシスコ、ニューヨーク、ロンドンにオフィスを持つ組織は、プライマリのアプライアンスをニューヨークの近くのデータセンター内で動作させ、2つのレプリカをサンフランシスコとロンドンの近くのデータセンターで動作させることができます。 地理的な場所を認識するDNSを利用すれば、ユーザーは利用可能な最も近いサーバへ振り分けられ、リポジトリのデータに高速にアクセスできます。 ニューヨークの近くにあるアプライアンスをプライマリにすれば、ロンドンへのレイテンシが大きいサンフランシスコ近くのアプライアンスをプライマリにする場合に比べ、ホスト間のレイテンシの削減に役立ちます。
|
||||
Multiple active replicas can provide a shorter distance to the nearest replica. For example, an organization with offices in San Francisco, New York, and London could run the primary appliance in a datacenter near New York and two replicas in datacenters near San Francisco and London. Using geolocation-aware DNS, users can be directed to the closest server available and access repository data faster. Designating the appliance near New York as the primary helps reduce the latency between the hosts, compared to the appliance near San Francisco being the primary which has a higher latency to London.
|
||||
|
||||
アクティブなレプリカは、自身では処理できないリクエストをプライマリインスタンスに中継します。 レプリカは、すべてのSSL接続をターミネートする接続点として機能します。 ホスト間のトラフィックは、暗号化されたVPN接続を通じて送信されます。これは、Geo-replicationなしの2ノードのHigh Availability構成に似ています。
|
||||
The active replica proxies requests that it can't process itself to the primary instance. The replicas function as a point of presence terminating all SSL connections. Traffic between hosts is sent through an encrypted VPN connection, similar to a two-node high availability configuration without geo-replication.
|
||||
|
||||
Git リクエストと、LFS やファイルアップロードなどの特定のファイルサーバーリクエストは、プライマリからデータをロードせずにレプリカから直接処理できます。 Webリクエストは常にプライマリにルーティングされますが、レプリカがユーザに近ければ、近くでSSLのターミネーションが行われることからリクエストは高速に処理されます。
|
||||
Git requests and specific file server requests, such as LFS and file uploads, can be served directly from the replica without loading any data from the primary. Web requests are always routed to the primary, but if the replica is closer to the user the requests are faster due to the closer SSL termination.
|
||||
|
||||
[Amazon の Route 53 サービス](http://docs.aws.amazon.com/Route53/latest/DeveloperGuide/routing-policy.html#routing-policy-geo)など、Geo DNS は、geo レプリケーションがシームレスに機能するために必要です。 インスタンスのホスト名は、ユーザの場所に最も近いレプリカに解決されるべきです。
|
||||
Geo DNS, such as [Amazon's Route 53 service](http://docs.aws.amazon.com/Route53/latest/DeveloperGuide/routing-policy.html#routing-policy-geo), is required for geo-replication to work seamlessly. The hostname for the instance should resolve to the replica that is closest to the user's location.
|
||||
|
||||
## 制限事項
|
||||
## Limitations
|
||||
|
||||
レプリカへの書き込みリクエストには、データをプライマリとすべてのレプリカへ送信することが必要です。 これは、すべての書き込みのパフォーマンスが最も遅いレプリカによって制限されることを意味しますが、新しい Geo-replication レプリカは、プライマリからではなく、既存の同じ場所に配置された Geo-replication レプリカからデータの大部分をシードできます。 {% ifversion ghes > 3.2 %}書き込みスループットに影響を与えず、分散チームと大規模 CI ファームによって引き起こされる待機時間と帯域幅を減らすには、代わりにリポジトリ キャッシュを構成できます。 詳細については、「[About repository caching](/admin/enterprise-management/caching-repositories/about-repository-caching)」(リポジトリのキャッシュについて) を参照してください。{% endif %}
|
||||
Writing requests to the replica requires sending the data to the primary and all replicas. This means that the performance of all writes is limited by the slowest replica, although new geo-replicas can seed the majority of their data from existing co-located geo-replicas, rather than from the primary. To reduce the latency and bandwidth caused by distributed teams and large CI farms without impacting write throughput, you can configure repository caching instead. For more information, see "[About repository caching](/admin/enterprise-management/caching-repositories/about-repository-caching)."
|
||||
|
||||
Geo-replication は、{% data variables.product.prodname_ghe_server %} インスタンスに容量を追加したり、不十分な CPU やメモリリソースに関連するパフォーマンスの問題を解決したりしません。 プライマリのアプライアンスがオフラインである場合、アクティブなレプリカはいかなる読み込みや書き込みのリクエストも処理できません。
|
||||
Geo-replication will not add capacity to a {% data variables.product.prodname_ghe_server %} instance or solve performance issues related to insufficient CPU or memory resources. If the primary appliance is offline, active replicas will be unable to serve any read or write requests.
|
||||
|
||||
{% data reusables.enterprise_installation.replica-limit %}
|
||||
|
||||
## Geo-replication設定のモニタリング
|
||||
## Monitoring a geo-replication configuration
|
||||
|
||||
{% data reusables.enterprise_installation.monitoring-replicas %}
|
||||
|
||||
## 参考資料
|
||||
- 「[geo レプリケーションレプリカの作成](/enterprise/admin/guides/installation/creating-a-high-availability-replica/#creating-geo-replication-replicas)」
|
||||
## Further reading
|
||||
- "[Creating geo-replication replicas](/enterprise/admin/guides/installation/creating-a-high-availability-replica/#creating-geo-replication-replicas)"
|
||||
|
||||
@@ -13,12 +13,12 @@ topics:
|
||||
- High availability
|
||||
- Infrastructure
|
||||
shortTitle: About HA configuration
|
||||
ms.openlocfilehash: 921a1a935bbfa930c77e2c72d7856f00d54d6016
|
||||
ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
|
||||
ms.openlocfilehash: b54ca60c6cf1d79b9435ca8deedebec09ed39396
|
||||
ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: ja-JP
|
||||
ms.lasthandoff: 09/05/2022
|
||||
ms.locfileid: '146332746'
|
||||
ms.lasthandoff: 10/25/2022
|
||||
ms.locfileid: '148109001'
|
||||
---
|
||||
High Availability設定をする際には、プライマリからレプリカアプライアンスへのすべてのデータストア（Gitリポジトリ、MySQL、Redis、Elasticsearch）の一方方向の非同期レプリケーションが、自動的にセットアップされます。 ほとんどの {% data variables.product.prodname_ghe_server %} 構成設定も、{% data variables.enterprise.management_console %} パスワードを含めてレプリケートされます。 詳細については、「[Accessing the management console](/admin/configuration/configuring-your-enterprise/accessing-the-management-console)」 (管理コンソールへのアクセス) を参照してください。
|
||||
|
||||
@@ -35,8 +35,8 @@ High Availability設定をする際には、プライマリからレプリカア
|
||||
|
||||
High Availability設定は、以下に対するソリューションとしては適切ではありません。
|
||||
|
||||
- **スケールアウト**: geo レプリケーションを使えば地理的にトラフィックを分散させることができるものの、書き込みのパフォーマンスはプライマリ アプライアンスの速度と可用性によって制限されます。 詳細については、「[geo レプリケーションについて](/enterprise/admin/guides/installation/about-geo-replication/)」を参照してください。{% ifversion ghes > 3.2 %}
|
||||
- **CI/CD の読み込み**: プライマリ インスタンスから地理的に離れている多数の CI クライアントがある場合は、リポジトリ キャッシュを構成するとメリットが得られる場合があります。 詳細については、「[About repository caching](/admin/enterprise-management/caching-repositories/about-repository-caching)」(リポジトリのキャッシュについて) を参照してください。{% endif %}
|
||||
- **スケールアウト**: geo レプリケーションを使えば地理的にトラフィックを分散させることができるものの、書き込みのパフォーマンスはプライマリ アプライアンスの速度と可用性によって制限されます。 詳細については、「[geo レプリケーションについて](/enterprise/admin/guides/installation/about-geo-replication/)」を参照してください。
|
||||
- **CI/CD の読み込み**: プライマリ インスタンスから地理的に離れている多数の CI クライアントがある場合は、リポジトリ キャッシュを構成するとメリットが得られる場合があります。 詳細については、「[About repository caching](/admin/enterprise-management/caching-repositories/about-repository-caching)」(リポジトリのキャッシュについて) を参照してください。
|
||||
- **プライマリ アプライアンスのバックアップ**: High Availabilityレプリカは、システム災害復旧計画のオフサイトバックアップを置き換えるものではありません。 データ破壊や損失の中には、プライマリからレプリカへ即座にレプリケーションされてしまうものもあります。 安定した過去の状態への安全なロールバックを保証するには、履歴スナップショットでの定期的なバックアップを行う必要があります。
|
||||
- **ダウンタイムなしのアップグレード**: コントロールされた昇格のシナリオにおけるデータ損失やスプリットブレインの状況を避けるには、プライマリアプライアンスをメンテナンスモードにして、すべての書き込みが完了するのを待ってからレプリカを昇格させてください。
|
||||
|
||||
|
||||
@@ -39,7 +39,7 @@ shortTitle: Create HA replica
|
||||
|
||||
This example configuration uses a primary and two replicas, which are located in three different geographic regions. While the three nodes can be in different networks, all nodes are required to be reachable from all the other nodes. At the minimum, the required administrative ports should be open to all the other nodes. For more information about the port requirements, see "[Network Ports](/enterprise/admin/guides/installation/network-ports/#administrative-ports)."
|
||||
|
||||
{% data reusables.enterprise_clustering.network-latency %}{% ifversion ghes > 3.2 %} If latency is more than 70 milliseconds, we recommend cache replica nodes instead. For more information, see "[Configuring a repository cache](/admin/enterprise-management/caching-repositories/configuring-a-repository-cache)."{% endif %}
|
||||
{% data reusables.enterprise_clustering.network-latency %} If latency is more than 70 milliseconds, we recommend cache replica nodes instead. For more information, see "[Configuring a repository cache](/admin/enterprise-management/caching-repositories/configuring-a-repository-cache)."
|
||||
|
||||
1. Create the first replica the same way you would for a standard two node configuration by running `ghe-repl-setup` on the first replica.
|
||||
```shell
|
||||
|
||||
@@ -17,7 +17,6 @@ topics:
|
||||
{% note %}
|
||||
|
||||
**Notes:**
|
||||
{% ifversion ghes < 3.3 %}- Features such as {% data variables.product.prodname_actions %}, {% data variables.product.prodname_registry %}, {% data variables.product.prodname_mobile %} and {% data variables.product.prodname_GH_advanced_security %} are available on {% data variables.product.prodname_ghe_server %} 3.0 or higher. We highly recommend upgrading to 3.0 or later releases to take advantage of critical security updates, bug fixes and feature enhancements.{% endif %}
|
||||
- Upgrade packages are available at [enterprise.github.com](https://enterprise.github.com/releases) for supported versions. Verify the availability of the upgrade packages you will need to complete the upgrade. If a package is not available, contact {% data variables.contact.contact_ent_support %} for assistance.
|
||||
- If you're using {% data variables.product.prodname_ghe_server %} Clustering, see "[Upgrading a cluster](/enterprise/admin/guides/clustering/upgrading-a-cluster/)" in the {% data variables.product.prodname_ghe_server %} Clustering Guide for specific instructions unique to clustering.
|
||||
- The release notes for {% data variables.product.prodname_ghe_server %} provide a comprehensive list of new features for every version of {% data variables.product.prodname_ghe_server %}. For more information, see the [releases page](https://enterprise.github.com/releases).
|
||||
|
||||
@@ -23,7 +23,6 @@ topics:
|
||||
shortTitle: Upgrading GHES
|
||||
---
|
||||
|
||||
{% ifversion ghes < 3.3 %}{% data reusables.enterprise.upgrade-ghes-for-features %}{% endif %}
|
||||
|
||||
## Preparing to upgrade
|
||||
|
||||
@@ -70,8 +69,7 @@ There are two types of snapshots:
|
||||
| Azure | VM | <https://docs.microsoft.com/azure/backup/backup-azure-vms-first-look-arm>
|
||||
| Hyper-V | VM | <https://docs.microsoft.com/windows-server/virtualization/hyper-v/manage/enable-or-disable-checkpoints-in-hyper-v>
|
||||
| Google Compute Engine | Disk | <https://cloud.google.com/compute/docs/disks/create-snapshots>
|
||||
| VMware | VM | <https://pubs.vmware.com/vsphere-50/topic/com.vmware.wssdk.pg.doc_50/PG_Ch11_VM_Manage.13.3.html>{% ifversion ghes < 3.3 %}
|
||||
| XenServer | VM | <https://docs.citrix.com/en-us/xencenter/current-release/vms-snapshots.html>{% endif %}
|
||||
| VMware | VM | <https://pubs.vmware.com/vsphere-50/topic/com.vmware.wssdk.pg.doc_50/PG_Ch11_VM_Manage.13.3.html>
|
||||
|
||||
## Upgrading with a hotpatch
|
||||
|
||||
|
||||
@@ -41,4 +41,4 @@ To restore a backup of {% data variables.location.product_location %} with {% da
|
||||
```
|
||||
{% data reusables.actions.apply-configuration-and-enable %}
|
||||
1. After {% data variables.product.prodname_actions %} is configured and enabled, to restore the rest of the data from the backup, use the `ghe-restore` command. For more information, see "[Restoring a backup](/admin/configuration/configuring-backups-on-your-appliance#restoring-a-backup)."
|
||||
1. Re-register your self-hosted runners on the destination instance. For more information, see "[Adding self-hosted runners](/actions/hosting-your-own-runners/adding-self-hosted-runners)."
|
||||
1. Re-register your self-hosted runners on the destination instance. For more information, see "[Adding self-hosted runners](/actions/hosting-your-own-runners/adding-self-hosted-runners)."
|
||||
|
||||
@@ -156,7 +156,7 @@ If any of these services are at or near 100% CPU utilization, or the memory is n
|
||||
When running `ghe-config-apply`, if you see output like `Failed to run nomad job '/etc/nomad-jobs/<name>.hcl'`, then the change has likely over-allocated CPU or memory resources. If this happens, edit the configuration files again and lower the allocated CPU or memory, then re-run `ghe-config-apply`.
|
||||
1. After the configuration is applied, run `ghe-actions-check` to verify that the {% data variables.product.prodname_actions %} services are operational.
|
||||
|
||||
{% ifversion fpt or ghec or ghes > 3.2 %}
|
||||
{% ifversion fpt or ghec or ghes %}
|
||||
## Troubleshooting failures when {% data variables.product.prodname_dependabot %} triggers existing workflows
|
||||
|
||||
{% data reusables.dependabot.beta-security-and-version-updates %}
|
||||
|
||||
@@ -12,11 +12,11 @@ children:
|
||||
- /enabling-github-actions-with-minio-gateway-for-nas-storage
|
||||
- /managing-self-hosted-runners-for-dependabot-updates
|
||||
shortTitle: Enable GitHub Actions
|
||||
ms.openlocfilehash: 675bbbe0ccbb68d676602b0553c8534f1601bcf6
|
||||
ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d
|
||||
ms.openlocfilehash: 273e03407dd8c3c0a125e2c215a973c88aaf884b
|
||||
ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: ja-JP
|
||||
ms.lasthandoff: 09/11/2022
|
||||
ms.locfileid: '145120446'
|
||||
ms.lasthandoff: 10/25/2022
|
||||
ms.locfileid: '148109060'
|
||||
---
|
||||
|
||||
|
||||
@@ -12,13 +12,6 @@ topics:
|
||||
- Enterprise
|
||||
---
|
||||
|
||||
{% ifversion ghes < 3.3 %}
|
||||
{% note %}
|
||||
|
||||
**Note:** {% data reusables.enterprise.upgrade-ghes-for-actions %}
|
||||
|
||||
{% endnote %}
|
||||
{% endif %}
|
||||
|
||||
## About {% data variables.product.prodname_actions %} for enterprises
|
||||
|
||||
@@ -56,7 +49,6 @@ You can create your own unique automations, or you can use and adapt workflows f
|
||||
After you finish planning, you can follow the instructions for getting started with {% data variables.product.prodname_actions %}. For more information, see {% ifversion ghec %}"[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_cloud %}](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-cloud)."{% elsif ghae %}"[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_managed %}](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-ae)."{% endif %}
|
||||
{% endif %}
|
||||
|
||||
|
||||
## Further reading
|
||||
|
||||
- "[Understanding {% data variables.product.prodname_actions %}](/actions/learn-github-actions/understanding-github-actions)"{% ifversion ghec %}
|
||||
|
||||
@@ -23,8 +23,6 @@ topics:
|
||||
|
||||
This article explains how site administrators can configure {% data variables.product.prodname_ghe_server %} to use {% data variables.product.prodname_actions %}.
|
||||
|
||||
{% data reusables.enterprise.upgrade-ghes-for-actions %}
|
||||
|
||||
{% data reusables.actions.ghes-actions-not-enabled-by-default %} You'll need to determine whether your instance has adequate CPU and memory resources to handle the load from {% data variables.product.prodname_actions %} without causing performance loss, and possibly increase those resources. You'll also need to decide which storage provider you'll use for the blob storage required to store artifacts{% ifversion actions-caching %} and caches{% endif %} generated by workflow runs. Then, you'll enable {% data variables.product.prodname_actions %} for your enterprise, manage access permissions, and add self-hosted runners to run workflows.
|
||||
|
||||
{% data reusables.actions.introducing-enterprise %}
|
||||
@@ -33,7 +31,6 @@ This article explains how site administrators can configure {% data variables.pr
|
||||
|
||||
## Review hardware requirements
|
||||
|
||||
|
||||
{%- ifversion ghes < 3.6 %}
|
||||
|
||||
The CPU and memory resources available to {% data variables.location.product_location %} determine the number of jobs that can be run concurrently without performance loss. {% data reusables.actions.minimum-hardware %}
|
||||
@@ -50,14 +47,6 @@ The peak quantity of connected runners without performance loss depends on such
|
||||
|
||||
{% endif %}
|
||||
|
||||
{%- ifversion ghes = 3.2 %}
|
||||
|
||||
{% data reusables.actions.hardware-requirements-3.2 %}
|
||||
|
||||
Maximum concurrency was measured using multiple repositories, job duration of approximately 10 minutes, and 10 MB artifact uploads. You may experience different performance depending on the overall levels of activity on your instance.
|
||||
|
||||
{%- endif %}
|
||||
|
||||
{%- ifversion ghes = 3.3 %}
|
||||
|
||||
{% data reusables.actions.hardware-requirements-3.3 %}
|
||||
@@ -88,7 +77,6 @@ Maximum concurrency was measured using multiple repositories, job duration of ap
|
||||
|
||||
{%- endif %}
|
||||
|
||||
|
||||
{%- ifversion ghes = 3.6 %}
|
||||
|
||||
{% data reusables.actions.hardware-requirements-3.6 %}
|
||||
@@ -114,8 +102,7 @@ For more information about minimum hardware requirements for {% data variables.l
|
||||
- [Google Cloud Platform](/admin/installation/installing-github-enterprise-server-on-google-cloud-platform#hardware-considerations)
|
||||
- [Hyper-V](/admin/installation/installing-github-enterprise-server-on-hyper-v#hardware-considerations)
|
||||
- [OpenStack KVM](/admin/installation/installing-github-enterprise-server-on-openstack-kvm#hardware-considerations)
|
||||
- [VMware](/admin/installation/installing-github-enterprise-server-on-vmware#hardware-considerations){% ifversion ghes < 3.3 %}
|
||||
- [XenServer](/admin/installation/installing-github-enterprise-server-on-xenserver#hardware-considerations){% endif %}
|
||||
- [VMware](/admin/installation/installing-github-enterprise-server-on-vmware#hardware-considerations)
|
||||
|
||||
{% data reusables.enterprise_installation.about-adjusting-resources %}
|
||||
|
||||
|
||||
@@ -32,9 +32,7 @@ This guide shows you how to apply a centralized management approach to self-host
|
||||
1. Deploy a self-hosted runner for your enterprise
|
||||
1. Create a group to manage access to the runners available to your enterprise
|
||||
1. Optionally, further restrict the repositories that can use the runner
|
||||
{%- ifversion ghec or ghae or ghes > 3.2 %}
|
||||
1. Optionally, build custom tooling to automatically scale your self-hosted runners
|
||||
{% endif %}
|
||||
|
||||
You'll also find additional information about how to monitor and secure your self-hosted runners,{% ifversion ghes or ghae %} how to access actions from {% data variables.product.prodname_dotcom_the_website %},{% endif %} and how to customize the software on your runner machines.
|
||||
|
||||
@@ -122,14 +120,10 @@ Optionally, organization owners can further restrict the access policy of the ru
|
||||
|
||||
For more information, see "[Managing access to self-hosted runners using groups](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#changing-the-access-policy-of-a-self-hosted-runner-group)."
|
||||
|
||||
{% ifversion ghec or ghae or ghes > 3.2 %}
|
||||
|
||||
## 5. Automatically scale your self-hosted runners
|
||||
|
||||
Optionally, you can build custom tooling to automatically scale the self-hosted runners for {% ifversion ghec or ghae %}your enterprise{% elsif ghes %}{% data variables.location.product_location %}{% endif %}. For example, your tooling can respond to webhook events from {% data variables.location.product_location %} to automatically scale a cluster of runner machines. For more information, see "[Autoscaling with self-hosted runners](/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners)."
|
||||
|
||||
{% endif %}
|
||||
|
||||
## Next steps
|
||||
|
||||
- You can monitor self-hosted runners and troubleshoot common issues. For more information, see "[Monitoring and troubleshooting self-hosted runners](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners)."
|
||||
|
||||
@@ -18,8 +18,6 @@ topics:
|
||||
|
||||
|
||||
|
||||
{% data reusables.enterprise.upgrade-ghes-for-actions %}
|
||||
|
||||
Before you introduce {% data variables.product.prodname_actions %} to a large enterprise, you first need to plan your adoption and make decisions about how your enterprise will use {% data variables.product.prodname_actions %} to best support your unique needs.
|
||||
|
||||
## Governance and compliance
|
||||
@@ -102,7 +100,7 @@ You may need to upgrade the CPU and memory resources for {% data variables.locat
|
||||
|
||||
You also have to decide where to add each runner. You can add a self-hosted runner to an individual repository, or you can make the runner available to an entire organization or your entire enterprise. Adding runners at the organization or enterprise levels allows sharing of runners, which might reduce the size of your runner infrastructure. You can use policies to limit access to self-hosted runners at the organization and enterprise levels by assigning groups of runners to specific repositories or organizations. For more information, see "[Adding self-hosted runners](/actions/hosting-your-own-runners/adding-self-hosted-runners)" and "[Managing access to self-hosted runners using groups](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups)."
|
||||
|
||||
{% ifversion ghec or ghes > 3.2 %}
|
||||
{% ifversion ghec or ghes %}
|
||||
You should consider using autoscaling to automatically increase or decrease the number of available self-hosted runners. For more information, see "[Autoscaling with self-hosted runners](/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners)."
|
||||
{% endif %}
|
||||
|
||||
|
||||
@@ -31,7 +31,7 @@ Alternatively, if you want stricter control over which actions are allowed in yo
|
||||
|
||||
{% data reusables.actions.github-connect-resolution %}
|
||||
|
||||
If a user has already created an organization and repository in your enterprise that matches an organization and repository name on {% data variables.product.prodname_dotcom_the_website %}, the repository on your enterprise will be used instead of the {% data variables.product.prodname_dotcom_the_website %} repository. {% ifversion ghes < 3.3 or ghae %}A malicious user could take advantage of this behavior to run code as part of a workflow{% else %}For more information, see "[Automatic retirement of namespaces for actions accessed on {% data variables.product.prodname_dotcom_the_website%}](#automatic-retirement-of-namespaces-for-actions-accessed-on-githubcom)."
|
||||
If a user has already created an organization and repository in your enterprise that matches an organization and repository name on {% data variables.product.prodname_dotcom_the_website %}, the repository on your enterprise will be used instead of the {% data variables.product.prodname_dotcom_the_website %} repository. {% ifversion ghae %}A malicious user could take advantage of this behavior to run code as part of a workflow.{% else %}For more information, see "[Automatic retirement of namespaces for actions accessed on {% data variables.product.prodname_dotcom_the_website%}](#automatic-retirement-of-namespaces-for-actions-accessed-on-githubcom)."
|
||||
{% endif %}
|
||||
|
||||
## Enabling automatic access to all {% data variables.product.prodname_dotcom_the_website %} actions
|
||||
@@ -46,8 +46,6 @@ Before enabling access to all actions from {% data variables.product.prodname_do
|
||||
|
||||
1. {% data reusables.actions.enterprise-limit-actions-use %}
|
||||
|
||||
{% ifversion ghes > 3.2 or ghae %}
|
||||
|
||||
## Automatic retirement of namespaces for actions accessed on {% data variables.product.prodname_dotcom_the_website %}
|
||||
|
||||
When you enable {% data variables.product.prodname_github_connect %}, users see no change in behavior for existing workflows because {% data variables.product.prodname_actions %} searches {% data variables.location.product_location %} for each action before falling back to {% data variables.product.prodname_dotcom_the_website%}. This ensures that any custom versions of actions your enterprise has created are used in preference to their counterparts on {% data variables.product.prodname_dotcom_the_website%}.
|
||||
@@ -67,5 +65,3 @@ After using an action from {% data variables.product.prodname_dotcom_the_website
|
||||
**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 {% data variables.product.prodname_dotcom_the_website %} 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.
|
||||
|
||||
{% endtip %}
|
||||
|
||||
{% endif %}
|
||||
|
||||
@@ -33,13 +33,11 @@ If your machine has access to both systems at the same time, you can do the sync
|
||||
|
||||
The `actions-sync` tool can only download actions from {% data variables.product.prodname_dotcom_the_website %} that are stored in public repositories.
|
||||
|
||||
{% ifversion ghes > 3.2 or ghae %}
|
||||
{% note %}
|
||||
|
||||
**Note:** The `actions-sync` tool is intended for use in systems where {% data variables.product.prodname_github_connect %} is not enabled. If you run the tool on a system with {% data variables.product.prodname_github_connect %} enabled, you may see the error `The repository <repo_name> has been retired and cannot be reused`. This indicates that a workflow has used that action directly on {% data variables.product.prodname_dotcom_the_website %} and the namespace is retired on {% data variables.location.product_location %}. For more information, see "[Automatic retirement of namespaces for actions accessed on {% data variables.product.prodname_dotcom_the_website%}](/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect#automatic-retirement-of-namespaces-for-actions-accessed-on-githubcom)."
|
||||
|
||||
{% endnote %}
|
||||
{% endif %}
|
||||
|
||||
## Prerequisites
|
||||
|
||||
|
||||
@@ -47,10 +47,8 @@ Once {% data variables.product.prodname_github_connect %} is configured, you can
|
||||
1. Configure your workflow's YAML to use `{% data reusables.actions.action-checkout %}`.
|
||||
1. Each time your workflow runs, the runner will use the specified version of `actions/checkout` from {% data variables.product.prodname_dotcom_the_website %}.
|
||||
|
||||
{% ifversion ghes > 3.2 or ghae %}
|
||||
{% note %}
|
||||
|
||||
**Note:** The first time the `checkout` action is used from {% data variables.product.prodname_dotcom_the_website %}, the `actions/checkout` namespace is automatically retired on {% data variables.location.product_location %}. If you ever want to revert to using a local copy of the action, you first need to remove the namespace from retirement. For more information, see "[Automatic retirement of namespaces for actions accessed on {% data variables.product.prodname_dotcom_the_website%}](/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect#automatic-retirement-of-namespaces-for-actions-accessed-on-githubcom)."
|
||||
|
||||
{% endnote %}
|
||||
{% endif %}
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
title: About Enterprise Managed Users
|
||||
title: About {% data variables.product.prodname_emus %}
|
||||
shortTitle: About managed users
|
||||
intro: 'You can centrally manage identity and access for your enterprise members on {% data variables.product.prodname_dotcom %} from your identity provider.'
|
||||
redirect_from:
|
||||
@@ -16,6 +16,7 @@ topics:
|
||||
- Authentication
|
||||
- Enterprise
|
||||
- SSO
|
||||
allowTitleToDifferFromFilename: true
|
||||
---
|
||||
|
||||
## About {% data variables.product.prodname_emus %}
|
||||
@@ -24,8 +25,6 @@ With {% data variables.product.prodname_emus %}, you can control the user accoun
|
||||
|
||||
In your IdP, you can give each {% data variables.enterprise.prodname_managed_user %} the role of user, enterprise owner, or billing manager. {% data variables.enterprise.prodname_managed_users_caps %} can own organizations within your enterprise and can add other {% data variables.enterprise.prodname_managed_users %} to the organizations and teams within. For more information, see "[Roles in an enterprise](/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/roles-in-an-enterprise)" and "[About organizations](/organizations/collaborating-with-groups-in-organizations/about-organizations)."
|
||||
|
||||
Organization membership can be managed manually, or you can update membership automatically as {% data variables.enterprise.prodname_managed_users %} are added to IdP groups that are connected to teams within the organization. When a {% data variables.enterprise.prodname_managed_user %} is manually added to an organization, unassigning them from the {% data variables.product.prodname_emu_idp_application %} application on your IdP will suspend the user but not remove them from the organization. For more information about managing organization and team membership automatically, see "[Managing team memberships with identity provider groups](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/managing-team-memberships-with-identity-provider-groups)."
|
||||
|
||||
{% ifversion oidc-for-emu %}
|
||||
|
||||
{% data reusables.enterprise-accounts.emu-cap-validates %} For more information, see "[About support for your IdP's Conditional Access Policy](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-support-for-your-idps-conditional-access-policy)."
|
||||
@@ -46,6 +45,17 @@ To use {% data variables.product.prodname_emus %}, you need a separate type of e
|
||||
|
||||
{% endnote %}
|
||||
|
||||
## About organization membership management
|
||||
|
||||
Organization memberships can be managed manually, or you can update memberships automatically using IdP groups. To manage organization memberships through your IdP, the members must be added to an IdP group, and the IdP group must be connected to a team within the organization. For more information about managing organization and team memberships automatically, see "[Managing team memberships with identity provider groups](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/managing-team-memberships-with-identity-provider-groups)."
|
||||
|
||||
The way a member is added to an organization owned by your enterprise (through IdP groups or manually) determines how they must be removed from an organization.
|
||||
|
||||
- If a member was added to an organization manually, you must remove them manually. Unassigning them from the {% data variables.product.prodname_emu_idp_application %} application on your IdP will suspend the user but not remove them from the organization.
|
||||
- If a user became a member of an organization because they were added to IdP groups mapped to one or more teams in the organization, removing them from _all_ of the mapped IdP groups associated with the organization will remove them from the organization.
|
||||
|
||||
To discover how a member was added to an organization, you can filter the member list by type. For more information, see "[Viewing people in your enterprise](/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise#filtering-by-member-type-in-an-enterprise-with-managed-users)."
|
||||
|
||||
## Identity provider support
|
||||
|
||||
{% data variables.product.prodname_emus %} supports the following IdPs{% ifversion oidc-for-emu %} and authentication methods:
|
||||
|
||||
@@ -145,7 +145,13 @@ After you enable LDAP sync, a synchronization job will run at the specified time
|
||||
A synchronization job will also run at the specified time interval to perform the following operations on each team that has been mapped to an LDAP group:
|
||||
|
||||
- If a team's corresponding LDAP group has been removed, remove all members from the team.
|
||||
- If LDAP member entries have been removed from the LDAP group, remove the corresponding users from the team. If the user is no longer a member of any team in the organization, remove the user from the organization. If the user loses access to any repositories as a result, delete any private forks the user has of those repositories.
|
||||
- If LDAP member entries have been removed from the LDAP group, remove the corresponding users from the team. If the user is no longer a member of any team in the organization and is not an owner of the organization, remove the user from the organization. If the user loses access to any repositories as a result, delete any private forks the user has of those repositories.
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** LDAP Sync will not remove a user from an organization if the user is an owner of that organization. Another organization owner will need to manually remove the user instead.
|
||||
|
||||
{% endnote %}
|
||||
- If LDAP member entries have been added to the LDAP group, add the corresponding users to the team. If the user regains access to any repositories as a result, restore any private forks of the repositories that were deleted because the user lost access in the past 90 days.
|
||||
|
||||
{% data reusables.enterprise_user_management.ldap-sync-nested-teams %}
|
||||
|
||||
@@ -15,12 +15,12 @@ topics:
|
||||
- Enterprise
|
||||
type: how_to
|
||||
shortTitle: Configure SAML SSO with Okta
|
||||
ms.openlocfilehash: 2772285f266a2593e8fc0900b39602325d30c46d
|
||||
ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
|
||||
ms.openlocfilehash: e9cbf6e70fb5e07f9cd2c5e27d9b952921e18fdc
|
||||
ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: ja-JP
|
||||
ms.lasthandoff: 09/05/2022
|
||||
ms.locfileid: '147094807'
|
||||
ms.lasthandoff: 10/25/2022
|
||||
ms.locfileid: '148109667'
|
||||
---
|
||||
{% data reusables.enterprise-accounts.emu-saml-note %}
|
||||
|
||||
|
||||
@@ -108,4 +108,4 @@ Ensure that you set the value for `Audience` on your IdP to the `EntityId` for {
|
||||
|
||||
{% ifversion ghec %}
|
||||
{% data reusables.saml.authentication-loop %}
|
||||
{% endif %}
|
||||
{% endif %}
|
||||
|
||||
@@ -105,14 +105,6 @@ featuredLinks:
|
||||
- '{% ifversion ghec %}/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/managing-global-webhooks{% endif %}'
|
||||
- /billing/managing-your-license-for-github-enterprise/using-visual-studio-subscription-with-github-enterprise/setting-up-visual-studio-subscription-with-github-enterprise
|
||||
- /admin/enterprise-support/about-github-enterprise-support
|
||||
videos:
|
||||
- title: GitHub in the Enterprise – Maya Ross
|
||||
href: 'https://www.youtube-nocookie.com/embed/1-i39RqaxRs'
|
||||
- title: What's new for GitHub Enterprise – Jarryd McCree
|
||||
href: 'https://www.youtube-nocookie.com/embed/ZZviWZgrqhM'
|
||||
- title: Enforcing information security policy through GitHub Enterprise – Thomas Worley
|
||||
href: 'https://www.youtube-nocookie.com/embed/DCu-ZTT7WTI'
|
||||
videosHeading: GitHub Universe 2021 videos
|
||||
layout: product-landing
|
||||
versions:
|
||||
ghec: '*'
|
||||
@@ -133,11 +125,11 @@ children:
|
||||
- /guides
|
||||
- /release-notes
|
||||
- /all-releases
|
||||
ms.openlocfilehash: ebd1473538d42928ff3d9abb3c0e2bd9f12767f5
|
||||
ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
|
||||
ms.openlocfilehash: 3980ad01e56bf1e38dd6473c5e5246c6d45350eb
|
||||
ms.sourcegitcommit: 3268914369fb29540e4d88ee5e56bc7a41f2a60e
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: ja-JP
|
||||
ms.lasthandoff: 09/11/2022
|
||||
ms.locfileid: '147881156'
|
||||
ms.lasthandoff: 10/26/2022
|
||||
ms.locfileid: '148111313'
|
||||
---
|
||||
|
||||
|
||||
@@ -18,14 +18,13 @@ children:
|
||||
- /installing-github-enterprise-server-on-hyper-v
|
||||
- /installing-github-enterprise-server-on-openstack-kvm
|
||||
- /installing-github-enterprise-server-on-vmware
|
||||
- /installing-github-enterprise-server-on-xenserver
|
||||
- /setting-up-a-staging-instance
|
||||
shortTitle: Set up an instance
|
||||
ms.openlocfilehash: 23fe586f2c4baa87a2e2b388685bf8e42d5e10a4
|
||||
ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
|
||||
ms.openlocfilehash: 7c23ae31e8e976f2acc664f87fbff82ffe025a0e
|
||||
ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: ja-JP
|
||||
ms.lasthandoff: 09/11/2022
|
||||
ms.locfileid: '147881462'
|
||||
ms.lasthandoff: 10/25/2022
|
||||
ms.locfileid: '148109000'
|
||||
---
|
||||
|
||||
|
||||
@@ -5,7 +5,7 @@ redirect_from:
|
||||
- /enterprise/admin/installation/setting-up-a-staging-instance
|
||||
- /admin/installation/setting-up-a-staging-instance
|
||||
versions:
|
||||
ghes: "*"
|
||||
ghes: '*'
|
||||
type: how_to
|
||||
topics:
|
||||
- Enterprise
|
||||
|
||||
@@ -46,9 +46,7 @@ As an enterprise owner{% ifversion ghes %} or site administrator{% endif %}, you
|
||||
{%- ifversion ghes %}
|
||||
- You can forward audit and system logs, from your enterprise to an third-party hosted monitoring system. For more information, see "[Log forwarding](/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/log-forwarding)."
|
||||
{%- endif %}
|
||||
{%- ifversion ghec or ghes > 3.2 or ghae %}
|
||||
- You can use the Audit log API to view actions performed in your enterprise. For more information, see "[Using the audit log API for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/using-the-audit-log-api-for-your-enterprise)."
|
||||
{%- endif %}
|
||||
|
||||
For a full list of audit log actions that may appear in your enterprise audit log, see "[Audit log actions for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise)."
|
||||
|
||||
|
||||
@@ -265,7 +265,6 @@ Action | Description
|
||||
| `config_entry.update` | A configuration setting was edited. These events are only visible in the site admin audit log. The type of events recorded relate to:</br>- Enterprise settings and policies</br>- Organization and repository permissions and settings</br>- Git, Git LFS, {% data variables.product.prodname_github_connect %}, {% data variables.product.prodname_registry %}, project, and code security settings.
|
||||
{%- endif %}
|
||||
|
||||
{%- ifversion fpt or ghec or ghes > 3.2 or ghae %}
|
||||
## `dependabot_alerts` category actions
|
||||
|
||||
| Action | Description
|
||||
@@ -285,9 +284,8 @@ Action | Description
|
||||
| Action | Description
|
||||
|--------|-------------
|
||||
| `dependabot_repository_access.repositories_updated` | The repositories that {% data variables.product.prodname_dependabot %} can access were updated.
|
||||
{%- endif %}
|
||||
|
||||
{%- ifversion fpt or ghec or ghes > 3.2 %}
|
||||
{%- ifversion fpt or ghec or ghes %}
|
||||
## `dependabot_security_updates` category actions
|
||||
|
||||
| Action | Description
|
||||
@@ -1341,7 +1339,7 @@ Before you'll see `git` category actions, you must enable Git events in the audi
|
||||
|--------|-------------
|
||||
| `staff.disable_repo` | An organization{% ifversion ghes %}, repository or site{% else %} or repository{% endif %} administrator disabled access to a repository and all of its forks.
|
||||
| `staff.enable_repo` | An organization{% ifversion ghes %}, repository or site{% else %} or repository{% endif %} administrator re-enabled access to a repository and all of its forks.
|
||||
{%- ifversion ghes > 3.2 or ghae %}
|
||||
{%- ifversion ghes or ghae %}
|
||||
| `staff.exit_fake_login` | An enterprise owner{% ifversion ghes %} or site administrator{% endif %} ended an impersonation session on {% data variables.product.product_name %}.
|
||||
| `staff.fake_login` | An enterprise owner{% ifversion ghes %} or site administrator{% endif %} signed into {% data variables.product.product_name %} as another user.
|
||||
{%- endif %}
|
||||
|
||||
@@ -1,8 +1,8 @@
|
||||
---
|
||||
title: Configuring the audit log for your enterprise
|
||||
intro: "You can configure settings for your enterprise's audit log."
|
||||
intro: You can configure settings for your enterprise's audit log.
|
||||
shortTitle: Configure audit logs
|
||||
permissions: 'Enterprise owners can configure the audit log.'
|
||||
permissions: Enterprise owners can configure the audit log.
|
||||
versions:
|
||||
feature: audit-data-retention-tab
|
||||
type: how_to
|
||||
@@ -53,4 +53,4 @@ Before you can enable Git events in the audit log, you must configure a retentio
|
||||
|
||||
1. Click **Save**.
|
||||
|
||||
{% endif %}
|
||||
{% endif %}
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Using the audit log API for your enterprise
|
||||
intro: 'You can programmatically retrieve enterprise events with the{% ifversion ghec or ghes > 3.2 %} REST or{% endif %} GraphQL API.'
|
||||
intro: 'You can programmatically retrieve enterprise events with the REST or GraphQL API.'
|
||||
shortTitle: Audit log API
|
||||
permissions: 'Enterprise owners {% ifversion ghes %}and site administrators {% endif %}can use the audit log API.'
|
||||
miniTocMaxHeadingLevel: 3
|
||||
@@ -18,7 +18,7 @@ topics:
|
||||
|
||||
## Using the audit log API
|
||||
|
||||
You can interact with the audit log using the GraphQL API{% ifversion ghec or ghes > 3.2 or ghae %} or the REST API{% endif %}.
|
||||
You can interact with the audit log using the GraphQL API or the REST API.
|
||||
|
||||
Timestamps and date fields in the API response are measured in [UTC epoch milliseconds](http://en.wikipedia.org/wiki/Unix_time).
|
||||
|
||||
@@ -106,7 +106,6 @@ This query uses the [AuditEntry](/graphql/reference/interfaces#auditentry) inter
|
||||
|
||||
For more query examples, see the [platform-samples repository](https://github.com/github/platform-samples/blob/master/graphql/queries).
|
||||
|
||||
{% ifversion ghec or ghes > 3.2 or ghae %}
|
||||
## Querying the audit log REST API
|
||||
|
||||
To ensure your intellectual property is secure, and you maintain compliance for your enterprise, you can use the audit log REST API to keep copies of your audit log data and monitor:
|
||||
@@ -137,5 +136,3 @@ curl -H "Authorization: Bearer TOKEN" \
|
||||
--request GET \
|
||||
"https://api.github.com/enterprises/avocado-corp/audit-log?phrase=action:pull_request+created:>=2022-01-01+actor:octocat"
|
||||
```
|
||||
|
||||
{% endif %}
|
||||
|
||||
@@ -9,15 +9,13 @@ type: overview
|
||||
topics:
|
||||
- Enterprise
|
||||
- Upgrades
|
||||
ms.openlocfilehash: 196745ee4ededaf78bd5afe876e4afa09141e930
|
||||
ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
|
||||
ms.openlocfilehash: b3a2d340ef73ffe92f2117caf38a84e76ba0c8d1
|
||||
ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: ja-JP
|
||||
ms.lasthandoff: 09/11/2022
|
||||
ms.locfileid: '145120205'
|
||||
ms.lasthandoff: 10/25/2022
|
||||
ms.locfileid: '148108851'
|
||||
---
|
||||
{% ifversion ghes < 3.3 %}{% data reusables.enterprise.upgrade-ghes-for-features %}{% endif %}
|
||||
|
||||
{% data reusables.enterprise.constantly-improving %}{% ifversion ghae %}{% data variables.product.prodname_ghe_managed %} はフルマネージドサービスであるため、{% data variables.product.company_short %} が Enterprise のアップグレードプロセスを完了します。{% endif %}
|
||||
|
||||
通常、機能リリースは四半期ごとに行われ、新機能と機能のアップグレードが含まれます。 {% ifversion ghae %}{% data variables.product.company_short %} は、エンタープライズを最新の機能リリースにアップグレードします。 Enterprise で予定されているダウンタイムについては、事前に通知されます。{% endif %}
|
||||
|
||||
@@ -2,9 +2,9 @@
|
||||
title: Migrating your enterprise to the Container registry from the Docker registry
|
||||
intro: 'You can migrate Docker images previously stored in the Docker registry on {% data variables.location.product_location %} to the {% data variables.product.prodname_container_registry %}.'
|
||||
product: '{% data reusables.gated-features.packages %}'
|
||||
permissions: "Enterprise owners can migrate Docker images to the {% data variables.product.prodname_container_registry %}."
|
||||
permissions: 'Enterprise owners can migrate Docker images to the {% data variables.product.prodname_container_registry %}.'
|
||||
versions:
|
||||
feature: 'docker-ghcr-enterprise-migration'
|
||||
feature: docker-ghcr-enterprise-migration
|
||||
shortTitle: Migrate to Container registry
|
||||
topics:
|
||||
- Containers
|
||||
|
||||
@@ -20,12 +20,12 @@ topics:
|
||||
- Policies
|
||||
- Projects
|
||||
shortTitle: Project board policies
|
||||
ms.openlocfilehash: 2066ab3fd36814150ff79457930d05909027513e
|
||||
ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
|
||||
ms.openlocfilehash: 2bb72b21094fadea8f584eb4749ed0cea69619ee
|
||||
ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: ja-JP
|
||||
ms.lasthandoff: 09/09/2022
|
||||
ms.locfileid: '147854136'
|
||||
ms.lasthandoff: 10/25/2022
|
||||
ms.locfileid: '148108797'
|
||||
---
|
||||
## エンタープライズ内のプロジェクトのポリシーについて
|
||||
|
||||
|
||||
@@ -14,11 +14,11 @@ children:
|
||||
- /enforcing-policies-for-your-enterprise
|
||||
- /enforcing-policy-with-pre-receive-hooks
|
||||
shortTitle: Set policies
|
||||
ms.openlocfilehash: 075d4f949435539c9c45ae651aedb0878f3317db
|
||||
ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d
|
||||
ms.openlocfilehash: 6fae4d9a9aa9c137be114b51eb90d79eb16d71df
|
||||
ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: ja-JP
|
||||
ms.lasthandoff: 09/11/2022
|
||||
ms.locfileid: '147400371'
|
||||
ms.lasthandoff: 10/25/2022
|
||||
ms.locfileid: '148109115'
|
||||
---
|
||||
|
||||
|
||||
@@ -33,11 +33,11 @@ children:
|
||||
- /managing-projects-using-jira
|
||||
- /continuous-integration-using-jenkins
|
||||
shortTitle: Manage organizations
|
||||
ms.openlocfilehash: 5d1430bc4efff03e6cddfe81f3c018d4f2064155
|
||||
ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d
|
||||
ms.openlocfilehash: 333d9b8d50bcdb86f709a447fee5a4078353dfe2
|
||||
ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: ja-JP
|
||||
ms.lasthandoff: 09/11/2022
|
||||
ms.locfileid: '147884246'
|
||||
ms.lasthandoff: 10/25/2022
|
||||
ms.locfileid: '148109114'
|
||||
---
|
||||
|
||||
|
||||
Some files were not shown because too many files have changed in this diff Show More
Reference in New Issue
Block a user