Merge branch 'main' into codewithdev-ui-changes
This commit is contained in:
Steve Ward
5
.gitignore
vendored
5
.gitignore
vendored
@@ -19,10 +19,9 @@ coverage/
|
||||
blc_output.log
|
||||
blc_output_internal.log
|
||||
broken_links.md
|
||||
lib/redirects/.redirects-cache.json
|
||||
# This one is purely for historical reasons because so many people might
|
||||
# still have thes files on their disk.
|
||||
lib/redirects/.redirects-cache_*.json
|
||||
# still have these files on their disk.
|
||||
lib/redirects/.redirects-cache*.json
|
||||
|
||||
# During the preview deploy untrusted user code may be cloned into this directory
|
||||
# We ignore it from git to keep things deterministic
|
||||
|
||||
BIN
assets/images/help/codespaces/disable-prebuild-optimization.png
Normal file
BIN
assets/images/help/codespaces/disable-prebuild-optimization.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 56 KiB |
BIN
assets/images/help/codespaces/edit-prebuild-configuration.png
Normal file
BIN
assets/images/help/codespaces/edit-prebuild-configuration.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 74 KiB |
BIN
assets/images/help/codespaces/show-advanced-options.png
Normal file
BIN
assets/images/help/codespaces/show-advanced-options.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 61 KiB |
@@ -63,7 +63,7 @@ When you enable {% data variables.product.prodname_dependabot_alerts %} for exis
|
||||
|
||||
{% ifversion fpt or ghec %}You can manage {% data variables.product.prodname_dependabot_alerts %} for your public, private or internal repository.
|
||||
|
||||
By default, we notify people with admin permissions in the affected repositories about new {% data variables.product.prodname_dependabot_alerts %}. {% data variables.product.product_name %} never publicly discloses insecure dependencies for any repository. You can also make {% data variables.product.prodname_dependabot_alerts %} visible to additional people or teams working repositories that you own or have admin permissions for.
|
||||
By default, we notify people with admin permissions in the affected repositories about new {% data variables.product.prodname_dependabot_alerts %}. {% data variables.product.product_name %} never publicly discloses insecure dependencies for any repository. You can also make {% data variables.product.prodname_dependabot_alerts %} visible to additional people or teams working on repositories that you own or have admin permissions for.
|
||||
|
||||
{% data reusables.security.security-and-analysis-features-enable-read-only %}
|
||||
|
||||
|
||||
@@ -27,9 +27,7 @@ Before you can configure prebuilds for your project the following must be true:
|
||||
|
||||
## Configuring a prebuild
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
{% data reusables.repositories.sidebar-settings %}
|
||||
1. In the "Code & automation" section of the sidebar, click **{% octicon "codespaces" aria-label="The Codespaces icon" %} {% data variables.product.prodname_codespaces %}**.
|
||||
{% data reusables.codespaces.accessing-prebuild-configuration %}
|
||||
1. In the "Prebuild configuration" section of the page, click **Set up prebuild**.
|
||||
|
||||
|
||||
@@ -80,6 +78,12 @@ Before you can configure prebuilds for your project the following must be true:
|
||||
|
||||
|
||||
|
||||
1. Optionally, at the bottom of the page, click **Show advanced options**.
|
||||
|
||||
|
||||
|
||||
In the "Advanced options" section, if you select **Disable prebuild optimization**, codespaces will be created without a prebuild if the latest prebuild workflow has failed or is currently running. For more information, see "[Troubleshooting prebuilds](/codespaces/troubleshooting/troubleshooting-prebuilds#preventing-out-of-date-prebuilds-being-used)."
|
||||
|
||||
1. Click **Create**.
|
||||
|
||||
{% data reusables.codespaces.prebuilds-permission-authorization %}
|
||||
|
||||
@@ -65,6 +65,24 @@ If the `devcontainer.json` configuration file for a prebuild configuration is up
|
||||
|
||||
If the workflow runs for a prebuild configuration are failing, you can temporarily disable the prebuild configuration while you investigate. For more information, see "[Managing prebuilds](/codespaces/prebuilding-your-codespaces/managing-prebuilds#disabling-a-prebuild-configuration)."
|
||||
|
||||
### Preventing out-of-date prebuilds being used
|
||||
|
||||
By default, if the latest prebuild workflow has failed, then a previous prebuild for the same combination of repository, branch, and `devcontainer.json` configuration file will be used to create new codespaces. This behavior is called prebuild optimization.
|
||||
|
||||
We recommend keeping prebuild optimization enabled, because it helps ensure that codespaces can still be created quickly if an up-to-date prebuild is not available. However, as a repository administrator, you can disable prebuild optimization if you run into problems with prebuilt codespaces being behind the current state of the branch. If you disable prebuild optimization, codespaces for the relevant combination of repository, branch, and `devcontainer.json` file will be created without a prebuild if the latest prebuild workflow has failed or is currently running.
|
||||
|
||||
{% data reusables.codespaces.accessing-prebuild-configuration %}
|
||||
1. To the right of the affected prebuild configuration, select the ellipsis (**...**), then click **Edit**.
|
||||
|
||||
|
||||
1. Scroll to the bottom of the "Edit configuration" page and click **Show advanced options**.
|
||||
|
||||
|
||||
1. If you're sure you want to disable the default setting, select **Disable prebuild optimization**.
|
||||
|
||||
|
||||
1. To save your change, click **Update**.
|
||||
|
||||
## Further reading
|
||||
|
||||
- "[Configuring prebuilds](/codespaces/prebuilding-your-codespaces/configuring-prebuilds)"
|
||||
|
||||
@@ -0,0 +1,3 @@
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
{% data reusables.repositories.sidebar-settings %}
|
||||
1. In the "Code & automation" section of the sidebar, click **{% octicon "codespaces" aria-label="The Codespaces icon" %} {% data variables.product.prodname_codespaces %}**.
|
||||
@@ -1,8 +1,3 @@
|
||||
# Redirects are cached in 'lib/redirects/.redirects-cache.json'. If changes made here are not being reflected
|
||||
# on your local server, delete the cache file by running the following command, then restart your server.
|
||||
#
|
||||
# rm lib/redirects/.redirects-cache.json
|
||||
|
||||
# These urls are exceptions to the versionless redirect fallbacks (described in lib/all-versions.js).
|
||||
# See the comment in lib/redirects/precompile.js for an explanation of these exceptions.
|
||||
# Originally shipped in pull #20947 on 10/15/21
|
||||
|
||||
@@ -88,10 +88,8 @@ router.get(
|
||||
)}-${language}`
|
||||
|
||||
const hits = []
|
||||
const timed = statsd.asyncTimer(getSearchResults, 'api.search', [
|
||||
'version:legacy',
|
||||
`indexName:${indexName}`,
|
||||
])
|
||||
const tags = ['version:legacy', `indexName:${indexName}`]
|
||||
const timed = statsd.asyncTimer(getSearchResults, 'api.search', tags)
|
||||
const options = {
|
||||
indexName,
|
||||
query,
|
||||
@@ -108,8 +106,10 @@ router.get(
|
||||
usePrefixSearch: true,
|
||||
}
|
||||
try {
|
||||
const searchResults = await timed(options)
|
||||
hits.push(...searchResults.hits)
|
||||
const { hits: hits_, meta } = await timed(options)
|
||||
hits.push(...hits_)
|
||||
statsd.timing('api.search.total', meta.took.total_msec, tags)
|
||||
statsd.timing('api.search.query', meta.took.query_msec, tags)
|
||||
} catch (error) {
|
||||
// If we don't catch here, the `catchMiddlewareError()` wrapper
|
||||
// will take any thrown error and pass it to `next()`.
|
||||
@@ -227,15 +227,16 @@ router.get(
|
||||
// This measurement then combines both the Node-work and the total
|
||||
// network-work but we know that roughly 99.5% of the total time is
|
||||
// spent in the network-work time so this primarily measures that.
|
||||
const timed = statsd.asyncTimer(getSearchResults, 'api.search', [
|
||||
'version:v1',
|
||||
`indexName:${indexName}`,
|
||||
])
|
||||
const tags = ['version:v1', `indexName:${indexName}`]
|
||||
const timed = statsd.asyncTimer(getSearchResults, 'api.search', tags)
|
||||
|
||||
const options = { indexName, query, page, size, debug, sort }
|
||||
try {
|
||||
const { meta, hits } = await timed(options)
|
||||
|
||||
statsd.timing('api.search.total', meta.took.total_msec, tags)
|
||||
statsd.timing('api.search.query', meta.took.query_msec, tags)
|
||||
|
||||
if (process.env.NODE_ENV !== 'development') {
|
||||
// The assumption, at the moment is that searches are never distinguished
|
||||
// differently depending on a cookie or a request header.
|
||||
|
||||
@@ -155,18 +155,6 @@ async function main(opts, nameTuple) {
|
||||
)
|
||||
}
|
||||
}
|
||||
|
||||
const redirectsCachingFile = 'lib/redirects/.redirects-cache.json'
|
||||
if (fs.existsSync(redirectsCachingFile)) {
|
||||
fs.unlinkSync(redirectsCachingFile)
|
||||
if (verbose) {
|
||||
console.log(
|
||||
chalk.yellow(
|
||||
`Deleted the redirects caching file ${redirectsCachingFile} to stale cache in local server testing.`
|
||||
)
|
||||
)
|
||||
}
|
||||
}
|
||||
}
|
||||
|
||||
function validateFileInputs(oldPath, newPath, isFolder) {
|
||||
|
||||
9
tests/fixtures/versionless-redirects.txt
vendored
9
tests/fixtures/versionless-redirects.txt
vendored
@@ -1,8 +1,3 @@
|
||||
# Redirects are cached in 'lib/redirects/.redirects-cache.json'. If changes made here are not being reflected
|
||||
# on your local server, delete the cache file by running the following command, then restart your server.
|
||||
#
|
||||
# rm lib/redirects/.redirects-cache.json
|
||||
|
||||
# These urls went from being free-pro-team, but are now versioned for more than one enterprise version and enterprise-cloud
|
||||
# Shipped in pull #20947 on 10/15/21
|
||||
|
||||
@@ -145,7 +140,7 @@
|
||||
- /github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account
|
||||
- /admin/authentication/managing-identity-and-access-for-your-enterprise
|
||||
|
||||
# These URLs went from being in free-pro-team to ONLY to being in enterprise-cloud only.
|
||||
# These URLs went from being in free-pro-team to ONLY to being in enterprise-cloud only.
|
||||
# Shipped in pull #20947 on 10/15/21
|
||||
|
||||
/enterprise-cloud@latest/admin/identity-and-access-management/using-saml-for-enterprise-iam/managing-team-synchronization-for-organizations-in-your-enterprise
|
||||
@@ -278,7 +273,7 @@
|
||||
# - lib/github/private_instance_bootstrapper/internal_support_contact.rb
|
||||
# - lib/github/private_instance_bootstrapper/saml_idp_configuration.rb
|
||||
# - lib/github/private_instance_bootstrapper/policies_configuration.rb
|
||||
# This redirect ensures that the links don't resolve to the non-GHAE version
|
||||
# This redirect ensures that the links don't resolve to the non-GHAE version
|
||||
# of the docs as this article only exists in the GHAE docs.
|
||||
|
||||
/github-ae@latest/admin/configuration/configuring-your-enterprise/initializing-github-ae
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Visualizar tus suscripciones
|
||||
intro: 'Para entender de dónde están llegando las notificaciones y la cantidad de las mismas, te recomendamos revisarlas frecuentemente, así como los repositorios que sigues de cerca.'
|
||||
title: Viewing your subscriptions
|
||||
intro: 'To understand where your notifications are coming from and your notifications volume, we recommend reviewing your subscriptions and watched repositories regularly.'
|
||||
redirect_from:
|
||||
- /articles/subscribing-to-conversations
|
||||
- /articles/unsubscribing-from-conversations
|
||||
@@ -24,63 +24,61 @@ versions:
|
||||
topics:
|
||||
- Notifications
|
||||
shortTitle: View subscriptions
|
||||
ms.openlocfilehash: 34faad79004d34f5beb14e8992b9aff4e6a3ab39
|
||||
ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: es-ES
|
||||
ms.lasthandoff: 09/10/2022
|
||||
ms.locfileid: '145117241'
|
||||
---
|
||||
Recibe notificaciones para sus suscripciones de la actividad reciente en {% data variables.product.product_name %}. Hay muchas razones por las cuales puedes estar suscrito a una conversación. Para obtener más información, consulte "[Acerca de las notificaciones](/github/managing-subscriptions-and-notifications-on-github/about-notifications#notifications-and-subscriptions)".
|
||||
You receive notifications for your subscriptions of ongoing activity on {% data variables.product.product_name %}. There are many reasons you can be subscribed to a conversation. For more information, see "[About notifications](/github/managing-subscriptions-and-notifications-on-github/about-notifications#notifications-and-subscriptions)."
|
||||
|
||||
Te recomendamos auditar tus suscripciones y desuscribirte de las que no sean necesarias como parte de un flujo de trabajo de notificaciones saludable. Para obtener más información sobre las opciones para cancelar la suscripción, consulte "[Administración de suscripciones](/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions)".
|
||||
We recommend auditing and unsubscribing from your subscriptions as a part of a healthy notifications workflow. For more information about your options for unsubscribing, see "[Managing subscriptions](/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions)."
|
||||
|
||||
## Diagnosticar el por qué recibes tantas notificaciones
|
||||
## Diagnosing why you receive too many notifications
|
||||
|
||||
Cuando tu bandeja de entrada tiene demasiadas notificaciones como para administrarlas, considera si estás suscrito a más de las que puedas manejar, o cómo puedes cambiar tu configuración de notificaciones para reducir aquellas que ya tienes y ver los tipos de notificaciones que estás recibiendo. Por ejemplo, puedes considerar inhabilitar la configuración para que observes automáticamente todos los repositorios y discusiones de equipo cada que te unas a un equipo o repositorio.
|
||||
When your inbox has too many notifications to manage, consider whether you have oversubscribed or how you can change your notification settings to reduce the subscriptions you have and the types of notifications you're receiving. For example, you may consider disabling the settings to automatically watch all repositories and all team discussions whenever you've joined a team or repository.
|
||||
|
||||
|
||||
{% ifversion update-notification-settings-22 %}
|
||||
|
||||
{% else %}
|
||||
{% endif %}
|
||||
|
||||
Para más información, consulte "[Configuración de notificaciones](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#automatic-watching)".
|
||||
For more information, see "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#automatic-watching)."
|
||||
|
||||
Para ver la información general de sus suscripciones a repositorios, consulte "[Revisión de los repositorios que sigue](#reviewing-repositories-that-youre-watching)". {% tip %}
|
||||
To see an overview of your repository subscriptions, see "[Reviewing repositories that you're watching](#reviewing-repositories-that-youre-watching)."
|
||||
{% tip %}
|
||||
|
||||
**Sugerencia:** Puede seleccionar los tipos de eventos para los que quiere recibir notificaciones mediante la opción **Custom** (Personalizar) de la lista desplegable **Watch/Unwatch** (Seguir/Dejar de seguir) en la [página de seguimiento](https://github.com/watching) o en cualquier página de repositorio de {% data variables.product.product_name %}. Para más información, consulte "[Configuración de notificaciones](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#configuring-your-watch-settings-for-an-individual-repository)".
|
||||
**Tip:** You can select the types of event to be notified of by using the **Custom** option of the **Watch/Unwatch** dropdown list in your [watching page](https://github.com/watching) or on any repository page on {% data variables.product.product_name %}. For more information, see "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#configuring-your-watch-settings-for-an-individual-repository)."
|
||||
|
||||
{% endtip %}
|
||||
|
||||
Muchas personas se olvidan de los repositorios que han marcado para observar. Desde la página de "Repositorios observados" puedes dejar de observar los repositorios rápidamente. Para obtener más información sobre las formas de cancelar la suscripción, consulte "[Recomendaciones para desuscribirse](https://github.blog/changelog/2020-11-10-unwatch-recommendations/)" en {% data variables.product.prodname_blog %} y "[Administración de las suscripciones](/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions)". También puedes crear un flujo de trabajo de clasificación para que te ayude con las notificaciones que recibes. Para obtener instrucciones sobre los flujos de trabajo de evaluación de prioridades, consulte "[Personalización de un flujo de trabajo para clasificar las notificaciones](/github/managing-subscriptions-and-notifications-on-github/customizing-a-workflow-for-triaging-your-notifications)".
|
||||
Many people forget about repositories that they've chosen to watch in the past. From the "Watched repositories" page you can quickly unwatch repositories. For more information on ways to unsubscribe, see "[Unwatch recommendations](https://github.blog/changelog/2020-11-10-unwatch-recommendations/)" on {% data variables.product.prodname_blog %} and "[Managing your subscriptions](/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions)." You can also create a triage workflow to help with the notifications you receive. For guidance on triage workflows, see "[Customizing a workflow for triaging your notifications](/github/managing-subscriptions-and-notifications-on-github/customizing-a-workflow-for-triaging-your-notifications)."
|
||||
|
||||
## Revisar todas tus suscripciones
|
||||
## Reviewing all of your subscriptions
|
||||
|
||||
{% data reusables.notifications.access_notifications %}
|
||||
1. En la barra lateral izquierda, en la lista de repositorios de los cuales recibe notificaciones, abra el menú desplegable "Manage notifications" (Administrar notificaciones) y haga clic en **Subscriptions** (Suscripciones).
|
||||
|
||||
1. In the left sidebar, under the list of repositories that you have notifications from, use the "Manage notifications" drop-down to click **Subscriptions**.
|
||||
|
||||
|
||||
2. Utiliza los filtros y organiza para reducir la lista de suscripciones y comenzar a darte de baja de las conversaciones de las cuales ya no quieres recibir notificaciones.
|
||||
2. Use the filters and sort to narrow the list of subscriptions and begin unsubscribing to conversations you no longer want to receive notifications for.
|
||||
|
||||
|
||||
|
||||
|
||||
{% tip %}
|
||||
|
||||
**Sugerencias:**
|
||||
- Para revisar las suscripciones que pudiste haber olvidado, organiza por "suscripciones menos recientes"
|
||||
**Tips:**
|
||||
- To review subscriptions you may have forgotten about, sort by "least recently subscribed."
|
||||
|
||||
- Para revisar una lista de repositorios de los cuales aún puedes recibir notificaciones, despliega el menú "filtrar por repositorio" para ver el listado.
|
||||
- To review a list of repositories that you can still receive notifications for, see the repository list in the "filter by repository" drop-down menu.
|
||||
|
||||
{% endtip %}
|
||||
|
||||
## Revisar los repositorios que estás siguiendo de cerca
|
||||
## Reviewing repositories that you're watching
|
||||
|
||||
1. En la barra lateral izquierda, en la lista de repositorios, use el menú desplegable "Manage notifications" (Administrar notificaciones) y haga clic en **Watched repositories** (Repositorios que sigue).
|
||||
|
||||
2. Evalúa si los repositorios que estás siguiendo de cerca tienen actualizaciones que aún sean útiles y relevantes. Cuando sigues de cerca un repositorio, se te notificará de todas las conversaciones en el mismo.
|
||||
|
||||
1. In the left sidebar, under the list of repositories, use the "Manage notifications" drop-down menu and click **Watched repositories**.
|
||||
|
||||
2. Evaluate the repositories that you are watching and decide if their updates are still relevant and helpful. When you watch a repository, you will be notified of all conversations for that repository.
|
||||
|
||||
|
||||
{% tip %}
|
||||
|
||||
**Sugerencia:** En lugar de seguir un repositorio, considere la posibilidad de recibir solo notificaciones cuando haya actualizaciones en {% data reusables.notifications-v2.custom-notification-types %} (si se han habilitado para el repositorio), o en cualquier combinación de estas opciones, o bien deje de seguir un repositorio por completo.
|
||||
**Tip:** Instead of watching a repository, consider only receiving notifications when there are updates to {% data reusables.notifications-v2.custom-notification-types %} (if enabled for the repository), or any combination of these options, or completely unwatching a repository.
|
||||
|
||||
Al dejar de seguir un repositorio, todavía recibirá notificaciones cuando le mencionen (@mentioned) o cuando participe en una conversación. Si configura las opciones para recibir notificaciones de ciertos tipos de eventos, solo se le notificará cuando haya actualizaciones en dichos eventos en el repositorio, cuando participe en una conversación o cuando usted o un equipo al que pertenece sean @mentioned.
|
||||
When you unwatch a repository, you can still be notified when you're @mentioned or participating in a thread. When you configure to receive notifications for certain event types, you're only notified when there are updates to these event types in the repository, you're participating in a thread, or you or a team you're on is @mentioned.
|
||||
|
||||
{% endtip %}
|
||||
|
||||
@@ -79,15 +79,27 @@ You can customize notifications for a repository. For example, you can choose to
|
||||
### Participating in conversations
|
||||
Anytime you comment in a conversation or when someone @mentions your username, you are _participating_ in a conversation. By default, you are automatically subscribed to a conversation when you participate in it. You can unsubscribe from a conversation you've participated in manually by clicking **Unsubscribe** on the issue or pull request or through the **Unsubscribe** option in the notifications inbox.
|
||||
|
||||
For conversations you're watching or participating in, you can choose whether you want to receive notifications by email or through the notifications inbox on {% data variables.product.product_location %}{% ifversion fpt or ghes or ghec %} and {% data variables.product.prodname_mobile %}{% endif %}.
|
||||
{% ifversion update-notification-settings-22 %}For conversations you're watching or participating in, you can choose whether you want to receive notifications on {% data variables.product.company_short %} or by email in your notification settings. For more information, see "[Choosing your notification settings](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications#choosing-your-notification-settings)."
|
||||
|
||||
|
||||
|
||||
{% else %}
|
||||
|
||||
For conversations you're watching or participating in, you can choose whether you want to receive notifications by email or through the notifications inbox on {% data variables.product.product_location %}{% ifversion ghes %} and {% data variables.product.prodname_mobile %}{% endif %}. For more information, see "[Choosing your notification settings](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications#choosing-your-notification-settings)."
|
||||
|
||||
{% endif %}
|
||||
|
||||
|
||||
|
||||
|
||||
For example:
|
||||
- If you don't want notifications to be sent to your email, unselect **email** for participating and watching notifications.
|
||||
- If you want to receive notifications by email when you've participated in a conversation, then you can select **email** under "Participating".
|
||||
|
||||
If you do not enable watching or participating notifications for web{% ifversion fpt or ghes or ghec %} and mobile{% endif %}, then your notifications inbox will not have any updates.
|
||||
{% ifversion update-notification-settings-22 %}If you do not enable "Notify me: On GitHub" for watching or participating notifications, then your notifications inbox will not have any updates.
|
||||
|
||||
{% else %}
|
||||
|
||||
If you do not enable watching or participating notifications for web{% ifversion ghes %} and mobile{% endif %}, then your notifications inbox will not have any updates.{% endif %}
|
||||
|
||||
## Customizing your email notifications
|
||||
|
||||
@@ -146,11 +158,16 @@ Email notifications from {% data variables.product.product_location %} contain t
|
||||
|
||||
## Automatic watching
|
||||
|
||||
By default, anytime you gain access to a new repository, you will automatically begin watching that repository. Anytime you join a new team, you will automatically be subscribed to updates and receive notifications when that team is @mentioned. If you don't want to automatically be subscribed, you can unselect the automatic watching options.
|
||||
By default, anytime you gain access to a new repository, you will automatically begin watching that repository. Anytime you join a new team, you will automatically be subscribed to updates and receive notifications when that team is @mentioned. If you don't want to automatically be subscribed, you can unselect the automatic watching options in your notification settings.
|
||||
|
||||
|
||||
{% ifversion update-notification-settings-22 %}
|
||||
|
||||
{% else %}
|
||||
{% endif %}
|
||||
|
||||
If "Automatically watch repositories" is disabled, then you will not automatically watch your own repositories. You must navigate to your repository page and choose the watch option.
|
||||
If "Automatically watch repositories" is disabled, then you will not automatically watch your own repositories. You must navigate to your repository page and choose the watch option.
|
||||
|
||||
For more information, see "[Choosing your notification settings](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications#choosing-your-notification-settings)."
|
||||
|
||||
## Configuring your watch settings for an individual repository
|
||||
|
||||
@@ -172,9 +189,17 @@ If you belong to an organization, you can choose the email account you want noti
|
||||
|
||||
{% data reusables.notifications.access_notifications %}
|
||||
{% data reusables.notifications-v2.manage-notifications %}
|
||||
|
||||
3. Under "Default notification email", select the email address you'd like notifications sent to.
|
||||
|
||||
4. Click **Save**.
|
||||
{% ifversion update-notification-settings-22 %}
|
||||
|
||||
|
||||
|
||||
{% else %}
|
||||
|
||||
{% endif %}
|
||||
{% ifversion ghes or ghae %}
|
||||
4. Click **Save**.{% endif %}
|
||||
|
||||
### Customizing email routes per organization
|
||||
|
||||
@@ -182,12 +207,35 @@ If you are a member of more than one organization, you can configure each one to
|
||||
|
||||
{% data reusables.notifications.access_notifications %}
|
||||
{% data reusables.notifications-v2.manage-notifications %}
|
||||
3. Under "Custom routing," find your organization's name in the list.
|
||||
|
||||
{% ifversion update-notification-settings-22 %}
|
||||
3. Under "Default notifications email", click **Custom routing**.
|
||||
|
||||
|
||||
|
||||
4. Click **Add new route**.
|
||||
|
||||
|
||||
|
||||
5. Click **Pick organization**, then select the organization you want to customize from the dropdown.
|
||||
|
||||
|
||||
|
||||
6. Select one of your verified email addresses, then click **Save**.
|
||||
|
||||
|
||||
|
||||
{% else %}
|
||||
3. Under "Custom routing," find your organization's name in the list.
|
||||
|
||||
|
||||
|
||||
4. Click **Edit** next to the email address you want to change.
|
||||
|
||||
|
||||
|
||||
|
||||
5. Select one of your verified email addresses, then click **Save**.
|
||||
|
||||
|
||||
{% endif %}
|
||||
|
||||
## {% data variables.product.prodname_dependabot_alerts %} notification options
|
||||
|
||||
@@ -197,14 +245,17 @@ If you are a member of more than one organization, you can configure each one to
|
||||
|
||||
For more information about the notification delivery methods available to you, and advice on optimizing your notifications for {% data variables.product.prodname_dependabot_alerts %}, see "[Configuring notifications for {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/configuring-notifications-for-dependabot-alerts)."
|
||||
|
||||
{% ifversion fpt or ghes or ghec %}
|
||||
{% ifversion update-notification-settings-22 or ghes %}
|
||||
## {% data variables.product.prodname_actions %} notification options
|
||||
|
||||
Choose how you want to receive workflow run updates for repositories that you are watching that are set up with {% data variables.product.prodname_actions %}. You can also choose to only receive notifications for failed workflow runs.
|
||||
Choose how you want to receive workflow run updates for repositories that you are watching that are set up with {% data variables.product.prodname_actions %}. You can also choose to only receive notifications for failed workflow runs.{% endif %}
|
||||
|
||||
|
||||
{% ifversion update-notification-settings-22 %}
|
||||
{% endif %}
|
||||
|
||||
{% ifversion ghes %}
|
||||
{% endif %}
|
||||
|
||||
{% endif %}
|
||||
|
||||
{% ifversion fpt or ghec or ghes > 3.3 or ghae > 3.3 %}
|
||||
## Organization alerts notification options
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Administrar el README de tu perfil
|
||||
intro: 'Puedes agregar un README a tu perfil de {% data variables.product.prodname_dotcom %} para que otras personas sepan sobre ti.'
|
||||
title: Managing your profile README
|
||||
intro: 'You can add a README to your {% data variables.product.prodname_dotcom %} profile to tell other people about yourself.'
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
@@ -11,71 +11,67 @@ redirect_from:
|
||||
- /github/setting-up-and-managing-your-github-profile/managing-your-profile-readme
|
||||
- /github/setting-up-and-managing-your-github-profile/customizing-your-profile/managing-your-profile-readme
|
||||
shortTitle: Your profile README
|
||||
ms.openlocfilehash: 587bcea1e1a0f96aad8882b41196afcc6e433363
|
||||
ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: es-ES
|
||||
ms.lasthandoff: 09/05/2022
|
||||
ms.locfileid: '147578904'
|
||||
---
|
||||
## Acerca del README de tu perfil
|
||||
## About your profile README
|
||||
|
||||
Puede compartir información acerca de usted mismo con la comunidad en {% data variables.product.product_location %} si crea un README del perfil. {% data variables.product.prodname_dotcom %} muestra el README de tu perfil al inicio de tu página de perfil.
|
||||
You can share information about yourself with the community on {% data variables.product.product_location %} by creating a profile README. {% data variables.product.prodname_dotcom %} shows your profile README at the top of your profile page.
|
||||
|
||||
Tú decides qué información incluir en el README de tu perfil, así que tienes todo el contro sobre cómo te presentas con los demás en {% data variables.product.prodname_dotcom %}. Aquí tienes algunos ejemplos de información que puede ser interesante, divertida o útil para los visitantes que lean el README en tu perfil.
|
||||
You decide what information to include in your profile README, so you have full control over how you present yourself on {% data variables.product.prodname_dotcom %}. Here are some examples of information that visitors may find interesting, fun, or useful in your profile README.
|
||||
|
||||
- Una sección de "sobre mí" que describa tu trabajo y tus intereses
|
||||
- Las contribuciones de las cuales estás orgulloso y el contexto de las mismas
|
||||
- Orientación para obtener ayuda en las comunidades en las que estás involucrado
|
||||
- An "About me" section that describes your work and interests
|
||||
- Contributions you're proud of, and context about those contributions
|
||||
- Guidance for getting help in communities where you're involved
|
||||
|
||||
|
||||
|
||||
|
||||
Puedes formatear el texto e incluir emojis, imágenes y GIFs en el README de tu perfil si utilizas el Marcado Enriquecido de {% data variables.product.company_short %}. Para obtener más información, consulte "[Introducción a la escritura y el formato en {% data variables.product.prodname_dotcom %}](/github/writing-on-github/getting-started-with-writing-and-formatting-on-github)".
|
||||
You can format text and include emoji, images, and GIFs in your profile README by using {% data variables.product.company_short %} Flavored Markdown. For more information, see "[Getting started with writing and formatting on {% data variables.product.prodname_dotcom %}](/github/writing-on-github/getting-started-with-writing-and-formatting-on-github)." For a hands-on guide to customizing your profile README, see "[Quickstart for writing on {% data variables.product.prodname_dotcom %}](/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/quickstart-for-writing-on-github)."
|
||||
|
||||
## Prerrequisitos
|
||||
## Prerequisites
|
||||
|
||||
GitHub mostrará el README de tu perfil en tu página de perfil si cuentas con todo lo siguiente.
|
||||
GitHub will display your profile README on your profile page if all of the following are true.
|
||||
|
||||
- Has creado un repositorio con un nombre que empate con tu nombre de usuario de {% data variables.product.prodname_dotcom %}.
|
||||
- Este repositorio es público.
|
||||
- Este repositorio contiene un archivo de nombre README.md en su raíz.
|
||||
- El archivo README.md contiene cualquier tipo de contenido.
|
||||
- You've created a repository with a name that matches your {% data variables.product.prodname_dotcom %} username.
|
||||
- The repository is public.
|
||||
- The repository contains a file named README.md in its root.
|
||||
- The README.md file contains any content.
|
||||
|
||||
{% note %}
|
||||
|
||||
**Nota**: Si creó un repositorio público con el mismo nombre que su nombre de usuario antes de julio del 2020, {% data variables.product.prodname_dotcom %} no mostrará automáticamente el README del repositorio en su perfil. Puede compartir manualmente el README del repositorio en su perfil. Para ello, vaya al repositorio en {% data variables.product.prodname_dotcom_the_website %} y haga clic en **Share to profile**.
|
||||
**Note**: If you created a public repository with the same name as your username before July 2020, {% data variables.product.prodname_dotcom %} won't automatically show the repository's README on your profile. You can manually share the repository's README to your profile by going to the repository on {% data variables.product.prodname_dotcom_the_website %} and clicking **Share to profile**.
|
||||
|
||||
|
||||
|
||||
|
||||
{% endnote %}
|
||||
|
||||
## Agregar un README de perfil
|
||||
## Adding a profile README
|
||||
|
||||
{% data reusables.repositories.create_new %}
|
||||
2. Debajo de "Nombre de repositorio", teclea un nombre de repositorio que empate con tu nombre de usuario de {% data variables.product.prodname_dotcom %}. Por ejemplo, si tu nombre de usuario es "octocat", el nombre de repositorio debe ser "octocat".
|
||||
|
||||
3. Opcionalmente, puede agregar una descripción del repositorio. Por ejemplo, "Mi repositorio personal".
|
||||
|
||||
4. Seleccione **Público**.
|
||||
 {% data reusables.repositories.initialize-with-readme %} {% data reusables.repositories.create-repo %}
|
||||
7. Encima de la barra lateral derecha, haga clic en **Edit README**.
|
||||
|
||||
2. Under "Repository name", type a repository name that matches your {% data variables.product.prodname_dotcom %} username. For example, if your username is "octocat", the repository name must be "octocat".
|
||||
|
||||
3. Optionally, add a description of your repository. For example, "My personal repository."
|
||||
|
||||
4. Select **Public**.
|
||||
|
||||
{% data reusables.repositories.initialize-with-readme %}
|
||||
{% data reusables.repositories.create-repo %}
|
||||
7. Above the right sidebar, click **Edit README**.
|
||||
|
||||
|
||||
El archivo de README que se ha generado está pre-llenado con una plantilla para que te inspires en completarlo.
|
||||
|
||||
The generated README file is pre-populated with a template to give you some inspiration for your profile README.
|
||||
|
||||
|
||||
Para obtener un resumen de todos los emojis disponibles y sus códigos, consulte "[Hoja de referencia rápida de emoji](https://www.webfx.com/tools/emoji-cheat-sheet/)".
|
||||
For a summary of all the available emojis and their codes, see "[Emoji cheat sheet](https://www.webfx.com/tools/emoji-cheat-sheet/)."
|
||||
|
||||
## Eliminar un README de perfil
|
||||
## Removing a profile README
|
||||
|
||||
El README de tu perfil se eliminará de tu perfil de {% data variables.product.prodname_dotcom %} si sucede cualquiera de los siguientes escenarios:
|
||||
The profile README is removed from your {% data variables.product.prodname_dotcom %} profile if any of the following apply:
|
||||
|
||||
- El archivo README está vacío o no existe.
|
||||
- El repositorio es privado.
|
||||
- El nombre del repositorio no empata con tu nombre de usuario.
|
||||
- The README file is empty or doesn't exist.
|
||||
- The repository is private.
|
||||
- The repository name no longer matches your username.
|
||||
|
||||
The method you choose is dependant upon your needs, but if you're unsure, we recommend making your repository private. Para ver los pasos para hacer un repositorio privado, consulta "[Cambiar la visibilidad de un repositorio](/github/administering-a-repository/setting-repository-visibility#changing-a-repositorys-visibility)".
|
||||
The method you choose depends upon your needs, but if you're unsure, we recommend making your repository private. For steps on how to make your repository private, see "[Changing a repository's visibility](/github/administering-a-repository/setting-repository-visibility#changing-a-repositorys-visibility)."
|
||||
|
||||
## Información adicional
|
||||
## Further reading
|
||||
|
||||
- "[Acerca de los archivos README](/github/creating-cloning-and-archiving-repositories/about-readmes)"
|
||||
- [About READMEs](/github/creating-cloning-and-archiving-repositories/about-readmes)
|
||||
|
||||
@@ -1,5 +1,6 @@
|
||||
---
|
||||
title: Creating a JavaScript action
|
||||
shortTitle: Create a JavaScript action
|
||||
intro: 'In this guide, you''ll learn how to build a JavaScript action using the actions toolkit.'
|
||||
redirect_from:
|
||||
- /articles/creating-a-javascript-action
|
||||
@@ -15,7 +16,6 @@ type: tutorial
|
||||
topics:
|
||||
- Action development
|
||||
- JavaScript
|
||||
shortTitle: JavaScript action
|
||||
---
|
||||
|
||||
{% data reusables.actions.enterprise-beta %}
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: About security hardening with OpenID Connect
|
||||
shortTitle: About security hardening with OpenID Connect
|
||||
shortTitle: Security hardening with OpenID Connect
|
||||
intro: OpenID Connect allows your workflows to exchange short-lived tokens directly from your cloud provider.
|
||||
miniTocMaxHeadingLevel: 4
|
||||
versions:
|
||||
|
||||
@@ -1,5 +1,6 @@
|
||||
---
|
||||
title: Autoscaling with self-hosted runners
|
||||
shortTitle: Autoscale self-hosted runners
|
||||
intro: You can automatically scale your self-hosted runners in response to webhook events.
|
||||
versions:
|
||||
fpt: '*'
|
||||
@@ -63,7 +64,7 @@ By default, self-hosted runners will automatically perform a software update whe
|
||||
To turn off automatic software updates and install software updates yourself, specify the `--disableupdate` flag when registering your runner using `config.sh`. For example:
|
||||
|
||||
```shell
|
||||
./config.sh --url <em>https://github.com/octo-org</em> --token <em>example-token</em> --disableupdate
|
||||
./config.sh --url https://github.com/YOUR-ORGANIZATION --token EXAMPLE-TOKEN --disableupdate
|
||||
```
|
||||
|
||||
If you disable automatic updates, you must still update your runner version regularly. New functionality in {% data variables.product.prodname_actions %} requires changes in both the {% data variables.product.prodname_actions %} service _and_ the runner software. The runner may not be able to correctly process jobs that take advantage of new features in {% data variables.product.prodname_actions %} without a software update.
|
||||
|
||||
@@ -201,7 +201,7 @@ The `github` context contains information about the workflow run and the event t
|
||||
| `github.ref` | `string` | {% data reusables.actions.ref-description %} |
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 or ghae > 3.3 %}
|
||||
| `github.ref_name` | `string` | {% data reusables.actions.ref_name-description %} |
|
||||
| `github.ref_protected` | `string` | {% data reusables.actions.ref_protected-description %} |
|
||||
| `github.ref_protected` | `boolean` | {% data reusables.actions.ref_protected-description %} |
|
||||
| `github.ref_type` | `string` | {% data reusables.actions.ref_type-description %} |
|
||||
{%- endif %}
|
||||
| `github.path` | `string` | Path on the runner to the file that sets system `PATH` variables from workflow commands. This file is unique to the current step and is a different file for each step in a job. For more information, see "[Workflow commands for {% data variables.product.prodname_actions %}](/actions/learn-github-actions/workflow-commands-for-github-actions#adding-a-system-path)." |
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Finding and customizing actions
|
||||
shortTitle: Finding and customizing actions
|
||||
shortTitle: Find and customize actions
|
||||
intro: 'Actions are the building blocks that power your workflow. A workflow can contain actions created by the community, or you can create your own actions directly within your application''s repository. This guide will show you how to discover, use, and customize actions.'
|
||||
redirect_from:
|
||||
- /actions/automating-your-workflow-with-github-actions/using-github-marketplace-actions
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Understanding GitHub Actions
|
||||
shortTitle: Understanding GitHub Actions
|
||||
shortTitle: Understand GitHub Actions
|
||||
intro: 'Learn the basics of {% data variables.product.prodname_actions %}, including core concepts and essential terminology.'
|
||||
miniTocMaxHeadingLevel: 3
|
||||
redirect_from:
|
||||
@@ -87,15 +87,9 @@ For more information, see "[Creating actions](/actions/creating-actions)."
|
||||
|
||||
{% data reusables.actions.workflow-basic-example-and-explanation %}
|
||||
|
||||
## More complex examples
|
||||
{% data reusables.actions.link-to-example-library %}
|
||||
|
||||
## Next steps
|
||||
|
||||
- To continue learning about {% data variables.product.prodname_actions %}, see "[Finding and customizing actions](/actions/learn-github-actions/finding-and-customizing-actions)."
|
||||
{% ifversion fpt or ghec or ghes %}
|
||||
- To understand how billing works for {% data variables.product.prodname_actions %}, see "[About billing for {% data variables.product.prodname_actions %}](/actions/reference/usage-limits-billing-and-administration#about-billing-for-github-actions)."
|
||||
{% endif %}
|
||||
{% data reusables.actions.onboarding-next-steps %}
|
||||
|
||||
## Contacting support
|
||||
|
||||
|
||||
@@ -1,5 +1,6 @@
|
||||
---
|
||||
title: Re-running workflows and jobs
|
||||
shortTitle: Re-run workflows and jobs
|
||||
intro: 'You can re-run a workflow run{% ifversion re-run-jobs %}, all failed jobs in a workflow run, or specific jobs in a workflow run{% endif %} up to 30 days after its initial run.'
|
||||
permissions: People with write permissions to a repository can re-run workflows in the repository.
|
||||
miniTocMaxHeadingLevel: 3
|
||||
@@ -48,14 +49,14 @@ Re-running a workflow{% ifversion re-run-jobs %} or jobs in a workflow{% endif %
|
||||
To re-run a failed workflow run, use the `run rerun` subcommand. Replace `run-id` with the ID of the failed run that you want to re-run. If you don't specify a `run-id`, {% data variables.product.prodname_cli %} returns an interactive menu for you to choose a recent failed run.
|
||||
|
||||
```shell
|
||||
gh run rerun <em>run-id</em>
|
||||
gh run rerun RUN_ID
|
||||
```
|
||||
|
||||
{% ifversion debug-reruns %}
|
||||
{% data reusables.actions.enable-debug-logging-cli %}
|
||||
|
||||
```shell
|
||||
gh run rerun <em>run-id</em> --debug
|
||||
gh run rerun RUN_ID --debug
|
||||
```
|
||||
|
||||
{% endif %}
|
||||
@@ -90,14 +91,14 @@ If any jobs in a workflow run failed, you can re-run just the jobs that failed.
|
||||
To re-run failed jobs in a workflow run, use the `run rerun` subcommand with the `--failed` flag. Replace `run-id` with the ID of the run for which you want to re-run failed jobs. If you don't specify a `run-id`, {% data variables.product.prodname_cli %} returns an interactive menu for you to choose a recent failed run.
|
||||
|
||||
```shell
|
||||
gh run rerun <em>run-id</em> --failed
|
||||
gh run rerun RUN_ID --failed
|
||||
```
|
||||
|
||||
{% ifversion debug-reruns %}
|
||||
{% data reusables.actions.enable-debug-logging-cli %}
|
||||
|
||||
```shell
|
||||
gh run rerun <em>run-id</em> --failed --debug
|
||||
gh run rerun RUN_ID --failed --debug
|
||||
```
|
||||
|
||||
{% endif %}
|
||||
@@ -127,14 +128,14 @@ When you re-run a specific job in a workflow, a new workflow run will start for
|
||||
To re-run a specific job in a workflow run, use the `run rerun` subcommand with the `--job` flag. Replace `job-id` with the ID of the job that you want to re-run.
|
||||
|
||||
```shell
|
||||
gh run rerun --job <em>job-id</em>
|
||||
gh run rerun --job JOB_ID
|
||||
```
|
||||
|
||||
{% ifversion debug-reruns %}
|
||||
{% data reusables.actions.enable-debug-logging-cli %}
|
||||
|
||||
```shell
|
||||
gh run rerun --job <em>job-id</em> --debug
|
||||
gh run rerun --job JOB_ID --debug
|
||||
```
|
||||
|
||||
{% endif %}
|
||||
|
||||
@@ -1,5 +1,6 @@
|
||||
---
|
||||
title: Publishing Docker images
|
||||
shortTitle: Publish Docker images
|
||||
intro: 'You can publish Docker images to a registry, such as Docker Hub or {% data variables.product.prodname_registry %}, as part of your continuous integration (CI) workflow.'
|
||||
redirect_from:
|
||||
- /actions/language-and-framework-guides/publishing-docker-images
|
||||
|
||||
@@ -1,5 +1,6 @@
|
||||
---
|
||||
title: Publishing Node.js packages
|
||||
shortTitle: Publish Node.js packages
|
||||
intro: You can publish Node.js packages to a registry as part of your continuous integration (CI) workflow.
|
||||
redirect_from:
|
||||
- /actions/automating-your-workflow-with-github-actions/publishing-nodejs-packages
|
||||
@@ -16,7 +17,6 @@ topics:
|
||||
- Publishing
|
||||
- Node
|
||||
- JavaScript
|
||||
shortTitle: Node.js packages
|
||||
---
|
||||
|
||||
{% data reusables.actions.enterprise-beta %}
|
||||
|
||||
@@ -77,21 +77,13 @@ Committing the workflow file to a branch in your repository triggers the `push`
|
||||
|
||||
For example, you can see the list of files in your repository:
|
||||
|
||||
|
||||
|
||||
The example workflow you just added is triggered each time code is pushed to the branch, and shows you how {% data variables.product.prodname_actions %} can work with the contents of your repository. For an in-depth tutorial, see "[Understanding {% data variables.product.prodname_actions %}](/actions/learn-github-actions/understanding-github-actions)."
|
||||
|
||||
## More starter workflows
|
||||
|
||||
{% data reusables.actions.workflow-template-overview %}
|
||||
|
||||
## More complex examples
|
||||
{% data reusables.actions.link-to-example-library %}
|
||||
|
||||
## Next steps
|
||||
|
||||
The example workflow you just added runs each time code is pushed to the branch, and shows you how {% data variables.product.prodname_actions %} can work with the contents of your repository. But this is only the beginning of what you can do with {% data variables.product.prodname_actions %}:
|
||||
|
||||
- Your repository can contain multiple workflows that trigger different jobs based on different events.
|
||||
- You can use a workflow to install software testing apps and have them automatically test your code on {% data variables.product.prodname_dotcom %}'s runners.
|
||||
|
||||
{% data variables.product.prodname_actions %} can help you automate nearly every aspect of your application development processes. Ready to get started? Here are some helpful resources for taking your next steps with {% data variables.product.prodname_actions %}:
|
||||
|
||||
- "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)" for an in-depth tutorial.
|
||||
{% data reusables.actions.onboarding-next-steps %}
|
||||
|
||||
@@ -93,13 +93,13 @@ If your repository has environment secrets or can access secrets from the parent
|
||||
To add a repository secret, use the `gh secret set` subcommand. Replace `secret-name` with the name of your secret.
|
||||
|
||||
```shell
|
||||
gh secret set <em>secret-name</em>
|
||||
gh secret set SECRET_NAME
|
||||
```
|
||||
|
||||
The CLI will prompt you to enter a secret value. Alternatively, you can read the value of the secret from a file.
|
||||
|
||||
```shell
|
||||
gh secret set <em>secret-name</em> < secret.txt
|
||||
gh secret set SECRET_NAME < secret.txt
|
||||
```
|
||||
|
||||
To list all secrets for the repository, use the `gh secret list` subcommand.
|
||||
@@ -128,13 +128,13 @@ To list all secrets for the repository, use the `gh secret list` subcommand.
|
||||
To add a secret for an environment, use the `gh secret set` subcommand with the `--env` or `-e` flag followed by the environment name.
|
||||
|
||||
```shell
|
||||
gh secret set --env <em>environment-name</em> <em>secret-name</em>
|
||||
gh secret set --env ENV_NAME SECRET_NAME
|
||||
```
|
||||
|
||||
To list all secrets for an environment, use the `gh secret list` subcommand with the `--env` or `-e` flag followed by the environment name.
|
||||
|
||||
```shell
|
||||
gh secret list --env <em>environment-name</em>
|
||||
gh secret list --env ENV_NAME
|
||||
```
|
||||
|
||||
{% endcli %}
|
||||
@@ -173,25 +173,25 @@ gh auth login --scopes "admin:org"
|
||||
To add a secret for an organization, use the `gh secret set` subcommand with the `--org` or `-o` flag followed by the organization name.
|
||||
|
||||
```shell
|
||||
gh secret set --org <em>organization-name</em> <em>secret-name</em>
|
||||
gh secret set --org ORG_NAME SECRET_NAME
|
||||
```
|
||||
|
||||
By default, the secret is only available to private repositories. To specify that the secret should be available to all repositories within the organization, use the `--visibility` or `-v` flag.
|
||||
|
||||
```shell
|
||||
gh secret set --org <em>organization-name</em> <em>secret-name</em> --visibility all
|
||||
gh secret set --org ORG_NAME SECRET_NAME --visibility all
|
||||
```
|
||||
|
||||
To specify that the secret should be available to selected repositories within the organization, use the `--repos` or `-r` flag.
|
||||
|
||||
```shell
|
||||
gh secret set --org <em>organization-name</em> <em>secret-name</em> --repos <em>repo-name-1</em>,<em>repo-name-2</em>"
|
||||
gh secret set --org ORG_NAME SECRET_NAME --repos REPO-NAME-1, REPO-NAME-2"
|
||||
```
|
||||
|
||||
To list all secrets for an organization, use the `gh secret list` subcommand with the `--org` or `-o` flag followed by the organization name.
|
||||
|
||||
```shell
|
||||
gh secret list --org <em>organization-name</em>
|
||||
gh secret list --org ORG_NAME
|
||||
```
|
||||
|
||||
{% endcli %}
|
||||
|
||||
@@ -1,11 +1,11 @@
|
||||
---
|
||||
title: Using 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'
|
||||
shortTitle: Using {% data variables.actions.hosted_runner %}s
|
||||
---
|
||||
|
||||
## Overview of {% data variables.actions.hosted_runner %}s
|
||||
@@ -87,7 +87,7 @@ You can add a {% data variables.actions.hosted_runner %} to an organization, whe
|
||||
|
||||
## Running jobs on your runner
|
||||
|
||||
Once your runner type has been been defined, you can update your workflows to send jobs to the runner instances for processing. In this example, a runner group is populated with Ubuntu 16-core runners, which have been assigned the label `ubuntu-20.04-16core`. If you have a runner matching this label, the `check-bats-version` job then uses the `runs-on` key to target that runner whenever the job is run:
|
||||
Once your runner type has been defined, you can update your workflow YAML files to send jobs to your newly created runner instances for processing. In this example, a runner group is populated with Ubuntu 16-core runners, which have been assigned the label `ubuntu-20.04-16core`. If you have a runner matching this label, the `check-bats-version` job then uses the `runs-on` key to target that runner whenever the job is run:
|
||||
|
||||
```yaml
|
||||
name: learn-github-actions
|
||||
@@ -104,6 +104,8 @@ jobs:
|
||||
- run: bats -v
|
||||
```
|
||||
|
||||
To find out which runners are enabled for your repository and organization, you must contact your organization admin. Your organization admin can create new runners and runner groups, as well as configure permissions to specify which repositories can access a runner group.
|
||||
|
||||
## Managing access to your runners
|
||||
|
||||
{% note %}
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Creating starter workflows for your organization
|
||||
shortTitle: Creating starter workflows
|
||||
shortTitle: Create starter workflows
|
||||
intro: Learn how you can create starter workflows to help people in your team add new workflows more easily.
|
||||
redirect_from:
|
||||
- /actions/configuring-and-managing-workflows/sharing-workflow-templates-within-your-organization
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Reusing workflows
|
||||
shortTitle: Reusing workflows
|
||||
shortTitle: Reuse workflows
|
||||
intro: Learn how to avoid duplication when creating a workflow by reusing existing workflows.
|
||||
redirect_from:
|
||||
- /actions/learn-github-actions/reusing-workflows
|
||||
@@ -105,7 +105,7 @@ You can define inputs and secrets, which can be passed from the caller workflow
|
||||
on:
|
||||
workflow_call:
|
||||
inputs:
|
||||
username:
|
||||
config-path:
|
||||
required: true
|
||||
type: string
|
||||
secrets:
|
||||
@@ -133,10 +133,10 @@ You can define inputs and secrets, which can be passed from the caller workflow
|
||||
runs-on: ubuntu-latest
|
||||
environment: production
|
||||
steps:
|
||||
- uses: octo-org/my-action@v1
|
||||
with:
|
||||
username: ${{ inputs.username }}
|
||||
token: ${{ secrets.envPAT }}
|
||||
- uses: actions/labeler@v4
|
||||
with:
|
||||
repo-token: ${{ secrets.envPAT }}
|
||||
configuration-path: ${{ inputs.config-path }}
|
||||
```
|
||||
{% endraw %}
|
||||
In the example above, `envPAT` is an environment secret that's been added to the `production` environment. This environment is therefore referenced within the job.
|
||||
@@ -162,7 +162,7 @@ name: Reusable workflow example
|
||||
on:
|
||||
workflow_call:
|
||||
inputs:
|
||||
username:
|
||||
config-path:
|
||||
required: true
|
||||
type: string
|
||||
secrets:
|
||||
@@ -170,14 +170,13 @@ on:
|
||||
required: true
|
||||
|
||||
jobs:
|
||||
example_job:
|
||||
name: Pass input and secrets to my-action
|
||||
triage:
|
||||
runs-on: ubuntu-latest
|
||||
steps:
|
||||
- uses: octo-org/my-action@v1
|
||||
with:
|
||||
username: ${{ inputs.username }}
|
||||
token: ${{ secrets.token }}
|
||||
- uses: actions/labeler@v4
|
||||
with:
|
||||
repo-token: ${{ secrets.token }}
|
||||
configuration-path: ${{ inputs.config-path }}
|
||||
```
|
||||
{% endraw %}
|
||||
|
||||
@@ -256,7 +255,7 @@ When you call a reusable workflow, you can only use the following keywords in th
|
||||
|
||||
### Example caller workflow
|
||||
|
||||
This workflow file calls two workflow files. The second of these, `workflow-B.yml` (shown in the [example reusable workflow](#example-reusable-workflow)), is passed an input (`username`) and a secret (`token`).
|
||||
This workflow file calls two workflow files. The second of these, `workflow-B.yml` (shown in the [example reusable workflow](#example-reusable-workflow)), is passed an input (`config-path`) and a secret (`token`).
|
||||
|
||||
{% raw %}
|
||||
```yaml{:copy}
|
||||
@@ -272,11 +271,14 @@ jobs:
|
||||
uses: octo-org/example-repo/.github/workflows/workflow-A.yml@v1
|
||||
|
||||
call-workflow-passing-data:
|
||||
permissions:
|
||||
contents: read
|
||||
pull-requests: write
|
||||
uses: octo-org/example-repo/.github/workflows/workflow-B.yml@main
|
||||
with:
|
||||
username: mona
|
||||
config-path: .github/labeler.yml
|
||||
secrets:
|
||||
token: ${{ secrets.TOKEN }}
|
||||
token: ${{ secrets.GITHUB_TOKEN }}
|
||||
```
|
||||
{% endraw %}
|
||||
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: 'Sharing workflows, secrets, and runners with your organization'
|
||||
shortTitle: Sharing workflows with your organization
|
||||
shortTitle: Share workflows with your organization
|
||||
intro: 'Learn how you can use organization features to collaborate with your team, by sharing starter workflows, secrets, and self-hosted runners.'
|
||||
redirect_from:
|
||||
- /actions/learn-github-actions/sharing-workflows-with-your-organization
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Triggering a workflow
|
||||
shortTitle: Triggering a workflow
|
||||
shortTitle: Trigger a workflow
|
||||
intro: 'How to automatically trigger {% data variables.product.prodname_actions %} workflows'
|
||||
versions:
|
||||
fpt: '*'
|
||||
|
||||
@@ -93,7 +93,7 @@ By default, the rate limit for {% data variables.product.prodname_actions %} is
|
||||
|
||||
```shell
|
||||
ghe-config actions-rate-limiting.enabled true
|
||||
ghe-config actions-rate-limiting.queue-runs-per-minute <em>RUNS-PER-MINUTE</em>
|
||||
ghe-config actions-rate-limiting.queue-runs-per-minute RUNS-PER-MINUTE
|
||||
```
|
||||
1. To disable the rate limit after it's been enabled, run the following command.
|
||||
|
||||
|
||||
@@ -118,7 +118,7 @@ If the upgrade target you're presented with is a feature release instead of a pa
|
||||
{% data reusables.enterprise_installation.download-package %}
|
||||
4. Run the `ghe-upgrade` command using the package file name:
|
||||
```shell
|
||||
admin@<em>HOSTNAME</em>:~$ ghe-upgrade <em>GITHUB-UPGRADE.hpkg</em>
|
||||
admin@HOSTNAME:~$ ghe-upgrade GITHUB-UPGRADE.hpkg
|
||||
*** verifying upgrade package signature...
|
||||
```
|
||||
5. If a reboot is required for updates for kernel, MySQL, Elasticsearch or other programs, the hotpatch upgrade script notifies you.
|
||||
@@ -170,14 +170,14 @@ While you can use a hotpatch to upgrade to the latest patch release within a fea
|
||||
|
||||
5. Run the `ghe-upgrade` command using the package file name:
|
||||
```shell
|
||||
admin@<em>HOSTNAME</em>:~$ ghe-upgrade <em>GITHUB-UPGRADE.pkg</em>
|
||||
admin@HOSTNAME:~$ ghe-upgrade GITHUB-UPGRADE.pkg
|
||||
*** verifying upgrade package signature...
|
||||
```
|
||||
6. Confirm that you'd like to continue with the upgrade and restart after the package signature verifies. The new root filesystem writes to the secondary partition and the instance automatically restarts in maintenance mode:
|
||||
```shell
|
||||
*** applying update...
|
||||
This package will upgrade your installation to version <em>version-number</em>
|
||||
Current root partition: /dev/xvda1 [<em>version-number</em>]
|
||||
This package will upgrade your installation to version VERSION-NUMBER
|
||||
Current root partition: /dev/xvda1 [VERSION-NUMBER]
|
||||
Target root partition: /dev/xvda2
|
||||
Proceed with installation? [y/N]
|
||||
```
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Streaming del registro de auditoría de su empresa
|
||||
intro: 'Puedes trasmitir datos de eventos de Git y de auditorías desde {% data variables.product.prodname_dotcom %} hacia un sistema externo de administración de datos.'
|
||||
title: Streaming the audit log for your enterprise
|
||||
intro: 'You can stream audit and Git events data from {% data variables.product.prodname_dotcom %} to an external data management system.'
|
||||
miniTocMaxHeadingLevel: 3
|
||||
versions:
|
||||
feature: audit-log-streaming
|
||||
@@ -15,34 +15,32 @@ redirect_from:
|
||||
- /github/setting-up-and-managing-your-enterprise/managing-organizations-in-your-enterprise-account/streaming-the-audit-logs-for-organizations-in-your-enterprise-account
|
||||
- /admin/user-management/managing-organizations-in-your-enterprise/streaming-the-audit-logs-for-organizations-in-your-enterprise-account
|
||||
permissions: Enterprise owners can configure audit log streaming.
|
||||
ms.openlocfilehash: 81eb88f760016390a321798589e7994542c9f312
|
||||
ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: es-ES
|
||||
ms.lasthandoff: 09/05/2022
|
||||
ms.locfileid: '147710343'
|
||||
---
|
||||
{% ifversion ghes %} {% note %}
|
||||
|
||||
**Nota:** La transmisión de registros de auditoría se encuentra actualmente en beta para {% data variables.product.product_name %} y está sujeta a cambios.
|
||||
{% ifversion ghes %}
|
||||
{% note %}
|
||||
|
||||
{% endnote %} {% endif %}
|
||||
**Note:** Audit log streaming is currently in beta for {% data variables.product.product_name %} and is subject to change.
|
||||
|
||||
## Acerca de la transmisión de bitácoras de auditoría
|
||||
{% endnote %}
|
||||
{% endif %}
|
||||
|
||||
Para ayudar a proteger la propiedad intelectual y mantener el cumplimiento de su organización, puede usar streaming para conservar copias de los datos del registro de auditoría y supervisar: {% data reusables.audit_log.audited-data-list %}
|
||||
## About audit log streaming
|
||||
|
||||
Los beneficios de transmitir datos de auditoría incluyen:
|
||||
To help protect your intellectual property and maintain compliance for your organization, you can use streaming to keep copies of your audit log data and monitor:
|
||||
{% data reusables.audit_log.audited-data-list %}
|
||||
|
||||
* **Exploración de datos**. Puedes examinar los eventos transmitidos utilizando tu herramienta preferida para consultar cantidades grandes de datos. La transmisión contiene tanto los eventos de auditoría como los de Git a lo largo de toda la cuenta empresarial.{% ifversion pause-audit-log-stream %}
|
||||
* **Continuidad de los datos**. Puedes poner en pausa la transmisión un máximo de siete días sin perder datos de auditoría.{% endif %}
|
||||
* **Retención de datos**. Puede mantener los registros de auditoría exportados y los datos de eventos de Git siempre que sea necesario.
|
||||
The benefits of streaming audit data include:
|
||||
|
||||
Los propietarios de la empresa pueden configurar{% ifversion pause-audit-log-stream %}, poner en pausa{% endif %} o eliminar una secuencia en cualquier momento. La transmisión exporta los datos de eventos de Git y auditoría de todas las organizaciones en tu empresa.
|
||||
* **Data exploration**. You can examine streamed events using your preferred tool for querying large quantities of data. The stream contains both audit events and Git events across the entire enterprise account.{% ifversion pause-audit-log-stream %}
|
||||
* **Data continuity**. You can pause the stream for up to seven days without losing any audit data.{% endif %}
|
||||
* **Data retention**. You can keep your exported audit logs and Git events data as long as you need to.
|
||||
|
||||
## Configurar la transmisión de bitácoras de auditoría
|
||||
Enterprise owners can set up{% ifversion pause-audit-log-stream %}, pause,{% endif %} or delete a stream at any time. The stream exports the audit and Git events data for all of the organizations in your enterprise.
|
||||
|
||||
Puedes configurar la transmisión de bitácoras de auditoría en {% data variables.product.product_name %} si sigues las instrucciones para tu proveedor.
|
||||
## Setting up audit log streaming
|
||||
|
||||
You set up the audit log stream on {% data variables.product.product_name %} by following the instructions for your provider.
|
||||
|
||||
- [Amazon S3](#setting-up-streaming-to-amazon-s3)
|
||||
- [Azure Blob Storage](#setting-up-streaming-to-azure-blob-storage)
|
||||
@@ -51,52 +49,49 @@ Puedes configurar la transmisión de bitácoras de auditoría en {% data variabl
|
||||
- [Google Cloud Storage](#setting-up-streaming-to-google-cloud-storage)
|
||||
- [Splunk](#setting-up-streaming-to-splunk)
|
||||
|
||||
### Configurar la transmisión para Amazon S3
|
||||
|
||||
{% ifversion streaming-oidc-s3 %} Puedes configurar la transmisión a S3 con claves de acceso o bien, para evitar almacenar secretos de larga duración en {% data variables.product.product_name %}, con OpenID Connect (OIDC).
|
||||
|
||||
- [Configuración de la transmisión a S3 con claves de acceso](#setting-up-streaming-to-s3-with-access-keys)
|
||||
- [Configuración de la transmisión a S3 con OpenID Connect](#setting-up-streaming-to-s3-with-openid-connect)
|
||||
- [Deshabilitación de la transmisión a S3 con OpenID Connect](#disabling-streaming-to-s3-with-openid-connect)
|
||||
|
||||
#### Configuración de la transmisión a S3 con claves de acceso
|
||||
{% endif %}
|
||||
|
||||
Para transmitir bitácoras de auditoría a la terminal de Amazon S3, debes tener un bucket y llaves de acceso. Para obtener más información, consulta [Creación, configuración y trabajo con buckets de Amazon S3](https://docs.aws.amazon.com/AmazonS3/latest/userguide/creating-buckets-s3.html) en la documentación de AWS. Asegúrate de bloquear el acceso público al bucket para proteger la información de tu bitácora de auditoría.
|
||||
|
||||
Para configurar la transmisión de bitácora de auditoría desde {% data variables.product.prodname_dotcom %}, necesitarás:
|
||||
* El nombrede tu bucket de Amazon S3
|
||||
* Tu ID de llave de acceso de AWS
|
||||
* Tu llave de secreto de AWS
|
||||
|
||||
Para obtener información sobre cómo crear o acceder al id. clave de acceso y la clave secreta, vea [Comprender y obtener las credenciales de AWS](https://docs.aws.amazon.com/general/latest/gr/aws-sec-cred-types.html) en la documentación de AWS.
|
||||
|
||||
{% data reusables.enterprise.navigate-to-log-streaming-tab %} {% data reusables.audit_log.streaming-choose-s3 %}{% ifversion streaming-oidc-s3 %}
|
||||
1. En "Autenticación", haz clic en **Claves de acceso**.
|
||||
|
||||
{% endif %}
|
||||
1. Configura los valores de transmisión.
|
||||
|
||||
- En "Cubo", escribe el nombre del cubo al que quieres transmitir. Por ejemplo, `auditlog-streaming-test`.
|
||||
- En "Id. de clave de acceso", escribe el identificador de la clave de acceso. Por ejemplo, `ABCAIOSFODNN7EXAMPLE1`.
|
||||
- En "Clave secreta", escribe la clave secreta. Por ejemplo, `aBcJalrXUtnWXYZ/A1MDENG/zPxRfiCYEXAMPLEKEY`.
|
||||
{% data reusables.audit_log.streaming-check-s3-endpoint %} {% data reusables.enterprise.verify-audit-log-streaming-endpoint %}
|
||||
### Setting up streaming to Amazon S3
|
||||
|
||||
{% ifversion streaming-oidc-s3 %}
|
||||
#### Configuración de la transmisión a S3 con OpenID Connect
|
||||
You can set up streaming to S3 with access keys or, to avoid storing long-lived secrets in {% data variables.product.product_name %}, with OpenID Connect (OIDC).
|
||||
|
||||
{% note %}
|
||||
- [Setting up streaming to S3 with access keys](#setting-up-streaming-to-s3-with-access-keys)
|
||||
- [Setting up streaming to S3 with OpenID Connect](#setting-up-streaming-to-s3-with-openid-connect)
|
||||
- [Disabling streaming to S3 with OpenID Connect](#disabling-streaming-to-s3-with-openid-connect)
|
||||
|
||||
**Nota:** El streaming a Amazon S3 con OpenID Connect está actualmente en versión beta y está sujeto a cambios.
|
||||
#### Setting up streaming to S3 with access keys
|
||||
{% endif %}
|
||||
|
||||
{% endnote %}
|
||||
To stream audit logs to Amazon's S3 endpoint, you must have a bucket and access keys. For more information, see [Creating, configuring, and working with Amazon S3 buckets](https://docs.aws.amazon.com/AmazonS3/latest/userguide/creating-buckets-s3.html) in the AWS documentation. Make sure to block public access to the bucket to protect your audit log information.
|
||||
|
||||
1. En AWS, agrega el proveedor de OIDC de {% data variables.product.prodname_dotcom %} a IAM. Para obtener más información, consulta [Creación de proveedores de identidades de OpenID Connect (OIDC)](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_providers_create_oidc.html) en la documentación de AWS.
|
||||
To set up audit log streaming from {% data variables.product.prodname_dotcom %} you will need:
|
||||
* The name of your Amazon S3 bucket
|
||||
* Your AWS access key ID
|
||||
* Your AWS secret key
|
||||
|
||||
- Para la dirección URL del proveedor, usa `https://oidc-configuration.audit-log.githubusercontent.com`.
|
||||
- Para "Audiencia", usa `sts.amazonaws.com`.
|
||||
1. Crea un cubo y bloquea el acceso público a él. Para obtener más información, consulta [Creación, configuración y trabajo con buckets de Amazon S3](https://docs.aws.amazon.com/AmazonS3/latest/userguide/creating-buckets-s3.html) en la documentación de AWS.
|
||||
1. Crea una directiva que permita que {% data variables.product.company_short %} escriba en el cubo. {% data variables.product.prodname_dotcom %} solo requiere los permisos siguientes.
|
||||
For information on creating or accessing your access key ID and secret key, see [Understanding and getting your AWS credentials](https://docs.aws.amazon.com/general/latest/gr/aws-sec-cred-types.html) in the AWS documentation.
|
||||
|
||||
{% data reusables.enterprise.navigate-to-log-streaming-tab %}
|
||||
{% data reusables.audit_log.streaming-choose-s3 %}{% ifversion streaming-oidc-s3 %}
|
||||
1. Under "Authentication", click **Access keys**.
|
||||
|
||||
{% endif %}
|
||||
1. Configure the stream settings.
|
||||
|
||||
- Under "Bucket", type the name of the bucket you want to stream to. For example, `auditlog-streaming-test`.
|
||||
- Under "Access Key ID", type your access key ID. For example, `ABCAIOSFODNN7EXAMPLE1`.
|
||||
- Under "Secret Key", type your secret key. For example, `aBcJalrXUtnWXYZ/A1MDENG/zPxRfiCYEXAMPLEKEY`.
|
||||
{% data reusables.audit_log.streaming-check-s3-endpoint %}
|
||||
{% data reusables.enterprise.verify-audit-log-streaming-endpoint %}
|
||||
|
||||
{% ifversion streaming-oidc-s3 %}
|
||||
#### Setting up streaming to S3 with OpenID Connect
|
||||
|
||||
1. In AWS, add the {% data variables.product.prodname_dotcom %} OIDC provider to IAM. For more information, see [Creating OpenID Connect (OIDC) identity providers](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_providers_create_oidc.html) in the AWS documentation.
|
||||
|
||||
- For the provider URL, use `https://oidc-configuration.audit-log.githubusercontent.com`.
|
||||
- For "Audience", use `sts.amazonaws.com`.
|
||||
1. Create a bucket, and block public access to the bucket. For more information, see [Creating, configuring, and working with Amazon S3 buckets](https://docs.aws.amazon.com/AmazonS3/latest/userguide/creating-buckets-s3.html) in the AWS documentation.
|
||||
1. Create a policy that allows {% data variables.product.company_short %} to write to the bucket. {% data variables.product.prodname_dotcom %} requires only the following permissions.
|
||||
|
||||
```
|
||||
{
|
||||
@@ -113,11 +108,11 @@ Para obtener información sobre cómo crear o acceder al id. clave de acceso y l
|
||||
]
|
||||
}
|
||||
```
|
||||
Para obtener más información, consulta [Crear políticas de IAM](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_create.html) en la documentación de AWS.
|
||||
1. Configura el rol y la directiva de confianza para el IdP de {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta [Creación de un rol para identidades federadas web u OpenID Connect (consola)](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_create_for-idp_oidc.html) en la documentación de AWS.
|
||||
For more information, see [Creating IAM policies](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_create.html) in the AWS documentation.
|
||||
1. Configure the role and trust policy for the {% data variables.product.prodname_dotcom %} IdP. For more information, see [Creating a role for web identity or OpenID Connect Federation (console)](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_create_for-idp_oidc.html) in the AWS documentation.
|
||||
|
||||
- Agrega la directiva de permisos que creaste anteriormente para permitir operaciones de escritura en el cubo.
|
||||
- Edita la relación de confianza para agregar el campo `sub` a las condiciones de validación. Reemplaza `ENTERPRISE` por el nombre de la empresa.
|
||||
- Add the permissions policy you created above to allow writes to the bucket.
|
||||
- Edit the trust relationship to add the `sub` field to the validation conditions, replacing `ENTERPRISE` with the name of your enterprise.
|
||||
```
|
||||
"Condition": {
|
||||
"StringEquals": {
|
||||
@@ -126,209 +121,217 @@ Para obtener información sobre cómo crear o acceder al id. clave de acceso y l
|
||||
}
|
||||
}
|
||||
```
|
||||
- Anota el nombre de recurso de Amazon (ARN) del rol creado.
|
||||
{% data reusables.enterprise.navigate-to-log-streaming-tab %} {% data reusables.audit_log.streaming-choose-s3 %}
|
||||
1. En "Autenticación", haz clic en **OpenID Connect**.
|
||||
- Make note of the Amazon Resource Name (ARN) of the created role.
|
||||
{% data reusables.enterprise.navigate-to-log-streaming-tab %}
|
||||
{% data reusables.audit_log.streaming-choose-s3 %}
|
||||
1. Under "Authentication", click **OpenID Connect**.
|
||||
|
||||
|
||||
1. Configura los valores de transmisión.
|
||||
|
||||
1. Configure the stream settings.
|
||||
|
||||
- En "Cubo", escribe el nombre del cubo al que quieres transmitir. Por ejemplo, `auditlog-streaming-test`.
|
||||
- En "Rol de ARN", escribe el rol de ARN que anotaste anteriormente. Por ejemplo, `arn:aws::iam::1234567890:role/github-audit-log-streaming-role`.
|
||||
{% data reusables.audit_log.streaming-check-s3-endpoint %} {% data reusables.enterprise.verify-audit-log-streaming-endpoint %}
|
||||
- Under "Bucket", type the name of the bucket you want to stream to. For example, `auditlog-streaming-test`.
|
||||
- Under "ARN Role" type the ARN role you noted earlier. For example, `arn:aws::iam::1234567890:role/github-audit-log-streaming-role`.
|
||||
{% data reusables.audit_log.streaming-check-s3-endpoint %}
|
||||
{% data reusables.enterprise.verify-audit-log-streaming-endpoint %}
|
||||
|
||||
#### Deshabilitación de la transmisión a S3 con OpenID Connect
|
||||
#### Disabling streaming to S3 with OpenID Connect
|
||||
|
||||
Si deseas deshabilitar la transmisión a S3 con OIDC por cualquier motivo, como la detección de una vulnerabilidad de seguridad en OIDC, elimina el proveedor de OIDC {% data variables.product.prodname_dotcom %} que creaste en AWS al configurar la transmisión. Para obtener más información, consulta [Creación de proveedores de identidades de OpenID Connect (OIDC)](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_providers_create_oidc.html) en la documentación de AWS.
|
||||
If you want to disable streaming to S3 with OIDC for any reason, such as the discovery of a security vulnerability in OIDC, delete the {% data variables.product.prodname_dotcom %} OIDC provider you created in AWS when you set up streaming. For more information, see [Creating OpenID Connect (OIDC) identity providers](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_providers_create_oidc.html) in the AWS documentation.
|
||||
|
||||
A continuación, configura la transmisión con claves de acceso hasta que se resuelva la vulnerabilidad. Para obtener más información, consulta "[Configuración de la transmisión a S3 con claves de acceso](#setting-up-streaming-to-s3-with-access-keys)".
|
||||
Then, set up streaming with access keys until the vulnerability is resolved. For more information, see "[Setting up streaming to S3 with access keys](#setting-up-streaming-to-s3-with-access-keys)."
|
||||
|
||||
{% endif %}
|
||||
|
||||
### Configurar la transmisión hacia Azure Blob Storage
|
||||
### Setting up streaming to Azure Blob Storage
|
||||
|
||||
Antes de configurar una transmisión en {% data variables.product.prodname_dotcom %}, primero debes haber creado una cuenta de almacenamiento y un contenedor en Microsoft Azure. Para obtener más información, vea la documentación de Microsoft "[Introducción a Azure Blob Storage](https://docs.microsoft.com/en-us/azure/storage/blobs/storage-blobs-introduction)".
|
||||
Before setting up a stream in {% data variables.product.prodname_dotcom %}, you must first have created a storage account and a container in Microsoft Azure. For details, see the Microsoft documentation, "[Introduction to Azure Blob Storage](https://docs.microsoft.com/en-us/azure/storage/blobs/storage-blobs-introduction)."
|
||||
|
||||
Para configurar la transmisión en {% data variables.product.prodname_dotcom %}, necesitarás la URL de un token SAS.
|
||||
To configure the stream in {% data variables.product.prodname_dotcom %} you need the URL of a SAS token.
|
||||
|
||||
**En Microsoft Azure Portal**:
|
||||
1. En la página principal, haga clic en **Cuentas de almacenamiento**.
|
||||
2. Haga clic en el nombre de la cuenta de almacenamiento que quiere usar y, después, haga clic en **Contenedores**.
|
||||
**On Microsoft Azure portal**:
|
||||
1. On the Home page, click **Storage Accounts**.
|
||||
2. Click the name of the storage account you want to use, then click **Containers**.
|
||||
|
||||
|
||||
|
||||
|
||||
1. Haz clic en el nombre del contenedor que quieres utilizar.
|
||||
1. Haga clic en **Shared access tokens** (Tokens de acceso compartido).
|
||||
1. Click the name of the container you want to use.
|
||||
1. Click **Shared access tokens**.
|
||||
|
||||
|
||||
|
||||
|
||||
1. En el menú desplegable **Permisos**, cambie los permisos para permitir únicamente `Create` y `Write`.
|
||||
1. In the **Permissions** drop-down menu, change the permissions to only allow `Create` and `Write`.
|
||||
|
||||
|
||||
|
||||
|
||||
1. Configura una fecha de vencimiento que cumpla con tu política de rotación de secretos.
|
||||
1. Haga clic en **Generar URL y token de SAS**.
|
||||
1. Copie el valor del campo **URL de SAS de blob** que se muestra. Utilizarás esta URL en {% data variables.product.prodname_dotcom %}.
|
||||
1. Set an expiry date that complies with your secret rotation policy.
|
||||
1. Click **Generate SAS token and URL**.
|
||||
1. Copy the value of the **Blob SAS URL** field that's displayed. You will use this URL in {% data variables.product.prodname_dotcom %}.
|
||||
|
||||
**En {% data variables.product.prodname_dotcom %}** : {% data reusables.enterprise.navigate-to-log-streaming-tab %}
|
||||
1. Haga clic en **Configurar secuencia** y seleccione **Azure Blob Storage**.
|
||||
**On {% data variables.product.prodname_dotcom %}**:
|
||||
{% data reusables.enterprise.navigate-to-log-streaming-tab %}
|
||||
1. Click **Configure stream** and select **Azure Blob Storage**.
|
||||
|
||||
|
||||
|
||||
|
||||
1. En la página de configuración, ingresa la URL de SAS del blob que copiaste en Azure. El campo **Contenedor** se rellena automáticamente en función de la dirección URL.
|
||||
1. On the configuration page, enter the blob SAS URL that you copied in Azure. The **Container** field is auto-filled based on the URL.
|
||||
|
||||
|
||||
|
||||
|
||||
1. Haga clic en **Check endpoint** (Comprobar punto de conexión) para comprobar que {% data variables.product.prodname_dotcom %} puede conectarse y escribir en el punto de conexión de Azure Blob Storage.
|
||||
1. Click **Check endpoint** to verify that {% data variables.product.prodname_dotcom %} can connect and write to the Azure Blob Storage endpoint.
|
||||
|
||||
|
||||
|
||||
|
||||
{% data reusables.enterprise.verify-audit-log-streaming-endpoint %}
|
||||
|
||||
### Configurar la transmisión hacia Azure Event Hubs
|
||||
### Setting up streaming to Azure Event Hubs
|
||||
|
||||
Antes de configurar una transmisión en {% data variables.product.prodname_dotcom %}, primero debes tener un espacio designador de nombre para concentradores de eventos en Microsoft Azure. Posteriormente, debes crear una instancia de concentrador de eventos dentro del designador de nombre. Necesitarás los detalles de esta instancia de concentrador de eventos cuando configures la transmisión. Para obtener más información, vea la documentación de Microsoft "[Inicio rápido: Creación de un centro de eventos mediante Azure Portal](https://docs.microsoft.com/en-us/azure/event-hubs/event-hubs-create)".
|
||||
Before setting up a stream in {% data variables.product.prodname_dotcom %}, you must first have an event hub namespace in Microsoft Azure. Next, you must create an event hub instance within the namespace. You'll need the details of this event hub instance when you set up the stream. For details, see the Microsoft documentation, "[Quickstart: Create an event hub using Azure portal](https://docs.microsoft.com/en-us/azure/event-hubs/event-hubs-create)."
|
||||
|
||||
Necesitas dos partes de información sobre tu concentrador de eventos: su nombre de instancia y la secuencia de conexión.
|
||||
You need two pieces of information about your event hub: its instance name and the connection string.
|
||||
|
||||
**En Microsoft Azure Portal**:
|
||||
1. Busque "Event Hubs".
|
||||
**On Microsoft Azure portal**:
|
||||
1. Search for "Event Hubs".
|
||||
|
||||
|
||||
|
||||
|
||||
1. Seleccione **Centro de eventos**. Se listarán los nombres de tus concentradores de eventos.
|
||||
1. Select **Event Hubs**. The names of your event hubs are listed.
|
||||
|
||||
|
||||
|
||||
|
||||
1. Haz una nota del nombre del concentrador de eventos al cual quieras transmitir.
|
||||
1. Haz clic en el concentrador de eventos requerido. En el menú de la izquierda, seleccione **Directivas de acceso compartido**.
|
||||
1. Selecciona las políticas de acceso compartido de la lista de políticas o crea una nueva.
|
||||
1. Make a note of the name of the event hub you want to stream to.
|
||||
1. Click the required event hub. Then, in the left menu, select **Shared Access Policies**.
|
||||
1. Select a shared access policy in the list of policies, or create a new policy.
|
||||
|
||||
|
||||
|
||||
|
||||
1. Haga clic en el botón situado a la derecha del campo **Connection string-primary key** (Clave principal de cadena de conexión) para copiar la cadena de conexión.
|
||||
1. Click the button to the right of the **Connection string-primary key** field to copy the connection string.
|
||||
|
||||
|
||||
|
||||
|
||||
**En {% data variables.product.prodname_dotcom %}** : {% data reusables.enterprise.navigate-to-log-streaming-tab %}
|
||||
1. Haga clic en **Configurar secuencia** y seleccione **Azure Event Hubs**.
|
||||
**On {% data variables.product.prodname_dotcom %}**:
|
||||
{% data reusables.enterprise.navigate-to-log-streaming-tab %}
|
||||
1. Click **Configure stream** and select **Azure Event Hubs**.
|
||||
|
||||
|
||||
|
||||
|
||||
1. En la página de configuración, ingresa:
|
||||
* El nombre de la instancia de Azure Event Hubs.
|
||||
* La cadena de conexión.
|
||||
1. On the configuration page, enter:
|
||||
* The name of the Azure Event Hubs instance.
|
||||
* The connection string.
|
||||
|
||||
|
||||
|
||||
|
||||
1. Haga clic en **Check endpoint** (Comprobar punto de conexión) para comprobar que {% data variables.product.prodname_dotcom %} puede conectarse y escribir en el punto de conexión de Azure Event Hubs.
|
||||
1. Click **Check endpoint** to verify that {% data variables.product.prodname_dotcom %} can connect and write to the Azure Events Hub endpoint.
|
||||
|
||||
|
||||
|
||||
|
||||
{% data reusables.enterprise.verify-audit-log-streaming-endpoint %}
|
||||
|
||||
{% ifversion streaming-datadog %}
|
||||
### Configuración de la transmisión a Datadog
|
||||
### Setting up streaming to Datadog
|
||||
|
||||
Para configurar la transmisión a Datadog, debes crear un token de cliente o una clave de API en Datadog y, a continuación, configurar la transmisión de registros de auditoría en {% data variables.product.product_name %} mediante el token para la autenticación. No es necesario crear un cubo u otro contenedor de almacenamiento en Datadog.
|
||||
To set up streaming to Datadog, you must create a client token or an API key in Datadog, then configure audit log streaming in {% data variables.product.product_name %} using the token for authentication. You do not need to create a bucket or other storage container in Datadog.
|
||||
|
||||
Después de configurar el streaming en Datadog, puedes ver los datos del registro de auditoría filtrando por "github.audit.streaming". Para más información, consulta [Administración de registros](https://docs.datadoghq.com/logs/).
|
||||
After you set up streaming to Datadog, you can see your audit log data by filtering by "github.audit.streaming." For more information, see [Log Management](https://docs.datadoghq.com/logs/).
|
||||
|
||||
1. Si aún no tienes una cuenta de Datadog, crea una.
|
||||
1. En Datadog, genera un token de cliente o una clave de API y, a continuación, haz clic en **Copiar clave**. Para obtener más información, consulta [API y claves de aplicación](https://docs.datadoghq.com/account_management/api-app-keys/) en Datadog Docs. {% data reusables.enterprise.navigate-to-log-streaming-tab %}
|
||||
1. Selecciona la lista desplegable **Configurar secuencia** y haz clic en **Datadog**.
|
||||
1. If you don't already have a Datadog account, create one.
|
||||
1. In Datadog, generate a client token or an API key, then click **Copy key**. For more information, see [API and Application Keys](https://docs.datadoghq.com/account_management/api-app-keys/) in Datadog Docs.
|
||||
{% data reusables.enterprise.navigate-to-log-streaming-tab %}
|
||||
1. Select the **Configure stream** dropdown menu and click **Datadog**.
|
||||
|
||||
|
||||
1. En "Token", pega el token que copiaste anteriormente.
|
||||
|
||||
1. Under "Token", paste the token you copied earlier.
|
||||
|
||||
|
||||
1. Selecciona el menú desplegable "Sitio" y haz clic en el sitio de Datadog. Para determinar el sitio de Datadog, compara la dirección URL de Datadog con la tabla de [sitios de Datadog](https://docs.datadoghq.com/getting_started/site/) en Datadog Docs.
|
||||
|
||||
1. Select the "Site" dropdown menu and click your Datadog site. To determine your Datadog site, compare your Datadog URL to the table in [Datadog sites](https://docs.datadoghq.com/getting_started/site/) in Datadog Docs.
|
||||
|
||||
|
||||
1. Para comprobar que {% data variables.product.prodname_dotcom %} se puede conectar al punto de conexión de Datadog y puedes escribir en él, haz clic en **Comprobar punto de conexión**.
|
||||
|
||||
1. To verify that {% data variables.product.prodname_dotcom %} can connect and write to the Datadog endpoint, click **Check endpoint**.
|
||||
|
||||
 {% data reusables.enterprise.verify-audit-log-streaming-endpoint %}
|
||||
1. Después de unos minutos, confirma que los datos del registro de auditoría aparecen en la pestaña **Registros** de Datadog. Si los datos del registro de auditoría no aparecen, confirma que el token y el sitio son correctos en {% data variables.product.prodname_dotcom %}.
|
||||
|
||||
{% data reusables.enterprise.verify-audit-log-streaming-endpoint %}
|
||||
1. After a few minutes, confirm that audit log data is appearing on the **Logs** tab in Datadog. If audit log data is not appearing, confirm that your token and site are correct in {% data variables.product.prodname_dotcom %}.
|
||||
{% endif %}
|
||||
|
||||
### Configurar la transmisión para Google Cloud Storage
|
||||
### Setting up streaming to Google Cloud Storage
|
||||
|
||||
Para configurar la transmisión al Almacenamiento de Google Cloud, debes crear una cuenta de servicio en Google Cloud con las credenciales y permisos adecuados y luego configurar la transmisión de bitácoras de auditoría en {% data variables.product.product_name %} utilizando las credenciales de la cuenta de servicio para la autenticación.
|
||||
To set up streaming to Google Cloud Storage, you must create a service account in Google Cloud with the appropriate credentials and permissions, then configure audit log streaming in {% data variables.product.product_name %} using the service account's credentials for authentication.
|
||||
|
||||
1. Crea una cuenta de servicio de Google Cloud. No necesitas configurar controles de acceso o roles de IAM para la cuenta de servicio. Para obtener más información, vea [Crear y administrar cuentas de servicio](https://cloud.google.com/iam/docs/creating-managing-service-accounts#creating) en la documentación de Google Cloud.
|
||||
1. Crear una llave de JSON para la cuenta de servicio y almacenarla de forma segura. Para obtener más información, vea [Crear y administrar claves de cuentas de servicio](https://cloud.google.com/iam/docs/creating-managing-service-account-keys#creating) en la documentación de Google Cloud.
|
||||
1. Si aún no has creado un bucket, házlo ahora. Para obtener más información, vea [Crear cubos de almacenamiento](https://cloud.google.com/storage/docs/creating-buckets) en la documentación de Google Cloud.
|
||||
1. Dale a la cuenta de servicio el el rol de Credor de Objetos de Almacenamiento para el bucket. Para obtener más información, vea [Usar permisos de Cloud IAM](https://cloud.google.com/storage/docs/access-control/using-iam-permissions#bucket-add) en la documentación de Google Cloud.
|
||||
1. Create a service account for Google Cloud. You do not need to set access controls or IAM roles for the service account. For more information, see [Creating and managing service accounts](https://cloud.google.com/iam/docs/creating-managing-service-accounts#creating) in the Google Cloud documentation.
|
||||
1. Create a JSON key for the service account, and store the key securely. For more information, see [Creating and managing service account keys](https://cloud.google.com/iam/docs/creating-managing-service-account-keys#creating) in the Google Cloud documentation.
|
||||
1. If you haven't created a bucket yet, create the bucket. For more information, see [Creating storage buckets](https://cloud.google.com/storage/docs/creating-buckets) in the Google Cloud documentation.
|
||||
1. Give the service account the Storage Object Creator role for the bucket. For more information, see [Using Cloud IAM permissions](https://cloud.google.com/storage/docs/access-control/using-iam-permissions#bucket-add) in the Google Cloud documentation.
|
||||
{% data reusables.enterprise.navigate-to-log-streaming-tab %}
|
||||
1. Seleccione el menú desplegable Configurar secuencia y haga clic en **Google Cloud Storage**.
|
||||
1. Select the Configure stream drop-down menu and click **Google Cloud Storage**.
|
||||
|
||||
|
||||
|
||||
|
||||
1. Debajo de "Bucket", teclea el nombre de tu bucket de Google Cloud Storage.
|
||||
1. Under "Bucket", type the name of your Google Cloud Storage bucket.
|
||||
|
||||
|
||||
|
||||
|
||||
1. Debajo de "Credenciales de JSON", pega todo el contenido del archivo para tu llave JSON de la cuenta de servicio.
|
||||
1. Under "JSON Credentials", paste the entire contents of the file for your service account's JSON key.
|
||||
|
||||
|
||||
|
||||
|
||||
1. Para comprobar que {% data variables.product.prodname_dotcom %} puede conectarse y escribir en el cubo de Google Cloud Storage, haga clic en **Check endpoint** (Comprobar punto de conexión).
|
||||
1. To verify that {% data variables.product.prodname_dotcom %} can connect and write to the Google Cloud Storage bucket, click **Check endpoint**.
|
||||
|
||||
|
||||
|
||||
|
||||
{% data reusables.enterprise.verify-audit-log-streaming-endpoint %}
|
||||
|
||||
### Configurar la transmisión a Splunk
|
||||
### Setting up streaming to Splunk
|
||||
|
||||
Para transmitir bitácoras de auditoría a la terminal del Recolector de Eventos HTTP (HEC) de Splunk, debes asegurarte de que la terminal se configure para aceptar conexiones HTTPS. Para obtener más información, vea [Configuración y uso del recopilador de eventos HTTP en Splunk Web](https://docs.splunk.com/Documentation/Splunk/latest/Data/UsetheHTTPEventCollector) en la documentación de Splunk.
|
||||
To stream audit logs to Splunk's HTTP Event Collector (HEC) endpoint you must make sure that the endpoint is configured to accept HTTPS connections. For more information, see [Set up and use HTTP Event Collector in Splunk Web](https://docs.splunk.com/Documentation/Splunk/latest/Data/UsetheHTTPEventCollector) in the Splunk documentation.
|
||||
|
||||
{% data reusables.enterprise.navigate-to-log-streaming-tab %}
|
||||
1. Haga clic en **Configurar secuencia** y seleccione **Splunk**.
|
||||
1. Click **Configure stream** and select **Splunk**.
|
||||
|
||||
|
||||
|
||||
|
||||
1. En la página de configuración, ingresa:
|
||||
* El dominio en el cual se hospeda la aplicación que quieres transmitir.
|
||||
1. On the configuration page, enter:
|
||||
* The domain on which the application you want to stream to is hosted.
|
||||
|
||||
Si usa Splunk Cloud, `Domain` debe ser `http-inputs-<host>`, donde `host` es el dominio que usa en Splunk Cloud. Por ejemplo: `http-inputs-mycompany.splunkcloud.com`.
|
||||
If you are using Splunk Cloud, `Domain` should be `http-inputs-<host>`, where `host` is the domain you use in Splunk Cloud. For example: `http-inputs-mycompany.splunkcloud.com`.
|
||||
|
||||
* El puerto mediante el cual la aplicación acepta datos.<br>
|
||||
* The port on which the application accepts data.<br>
|
||||
|
||||
Si usa Splunk Cloud, `Port` debe ser `443` si no ha cambiado la configuración del puerto. Si usa la versión de evaluación gratuita de Splunk Cloud, `Port` debe ser `8088`.
|
||||
If you are using Splunk Cloud, `Port` should be `443` if you haven't changed the port configuration. If you are using the free trial version of Splunk Cloud, `Port` should be `8088`.
|
||||
|
||||
* Un token que pueda utilizar {% data variables.product.prodname_dotcom %} para autenticarse a la aplicación de terceros.
|
||||
* A token that {% data variables.product.prodname_dotcom %} can use to authenticate to the third-party application.
|
||||
|
||||
|
||||
|
||||
|
||||
1. Deje activada la casilla **Enable SSL verification** (Habilitar comprobación SSL).
|
||||
1. Leave the **Enable SSL verification** check box selected.
|
||||
|
||||
Las bitácoras de auditoría siempre se transmiten como datos cifrados, sin embargo, si seleccionas esta opción, {% data variables.product.prodname_dotcom %} verificará el certificado SSL de tu instancia de Splunk cuando entregue eventos. La verificación por SSL te ayuda a garantizar que los eventos se entreguen a tu terminal URL con seguridad. Puedes limpiar la selección de esta opción, pero te recomendamos que dejes habilitada la verificación por SSL.
|
||||
1. Haga clic en **Check endpoint** (Comprobar punto de conexión) para comprobar que {% data variables.product.prodname_dotcom %} puede conectarse y escribir en el punto de conexión de Splunk.
|
||||
 {% data reusables.enterprise.verify-audit-log-streaming-endpoint %}
|
||||
Audit logs are always streamed as encrypted data, however, with this option selected, {% data variables.product.prodname_dotcom %} verifies the SSL certificate of your Splunk instance when delivering events. SSL verification helps ensure that events are delivered to your URL endpoint securely. You can clear the selection of this option, but we recommend you leave SSL verification enabled.
|
||||
1. Click **Check endpoint** to verify that {% data variables.product.prodname_dotcom %} can connect and write to the Splunk endpoint.
|
||||
|
||||
{% data reusables.enterprise.verify-audit-log-streaming-endpoint %}
|
||||
|
||||
{% ifversion pause-audit-log-stream %}
|
||||
## Pausar la transmisión de bitácoras de auditoría
|
||||
## Pausing audit log streaming
|
||||
|
||||
El pausar la transmisión te permite realizar el mantenimiento de la aplicación receptora sin perder datos de auditoría. Las bitácoras de auditoría se almacenan por hasta siete días en {% data variables.product.product_location %} y luego se exportan cuando dejas de pausar la transmisión.
|
||||
Pausing the stream allows you to perform maintenance on the receiving application without losing audit data. Audit logs are stored for up to seven days on {% data variables.product.product_location %} and are then exported when you unpause the stream.
|
||||
|
||||
{% ifversion streaming-datadog %} Datadog solo acepta registros de hasta 18 horas en el pasado. Si pausas una secuencia en un punto de conexión de Datadog durante más de 18 horas, corres el riesgo de perder los registros que Datadog no aceptará después de reanudar la transmisión.
|
||||
{% ifversion streaming-datadog %}
|
||||
Datadog only accepts logs from up to 18 hours in the past. If you pause a stream to a Datadog endpoint for more than 18 hours, you risk losing logs that Datadog won't accept after you resume streaming.
|
||||
{% endif %}
|
||||
|
||||
{% data reusables.enterprise.navigate-to-log-streaming-tab %}
|
||||
1. Haga clic en **Pause stream** (Pausar secuencia).
|
||||
1. Click **Pause stream**.
|
||||
|
||||
|
||||
|
||||
|
||||
1. Se muestra un mensaje de confirmación. Haga clic en **Pause stream** (Pausar secuencia) para confirmar.
|
||||
1. A confirmation message is displayed. Click **Pause stream** to confirm.
|
||||
|
||||
Cuando la aplicación esté lista para recibir registros de auditoría de nuevo, haga clic en **Resume stream** (Reanudar secuencia) para reiniciar los registros de auditoría de streaming.
|
||||
When the application is ready to receive audit logs again, click **Resume stream** to restart streaming audit logs.
|
||||
{% endif %}
|
||||
|
||||
## Borrar la transmisión de bitácoras de auditoría
|
||||
## Deleting the audit log stream
|
||||
|
||||
{% data reusables.enterprise.navigate-to-log-streaming-tab %}
|
||||
1. Haga clic en **Delete stream** (Eliminar secuencia).
|
||||
1. Click **Delete stream**.
|
||||
|
||||
|
||||
|
||||
|
||||
1. Se muestra un mensaje de confirmación. Haga clic en **Delete stream** (Eliminar secuencia) para confirmar.
|
||||
1. A confirmation message is displayed. Click **Delete stream** to confirm.
|
||||
|
||||
@@ -121,7 +121,7 @@ For more information about the audit log REST API, see "[Enterprise administrati
|
||||
The query below searches for audit log events created on Jan 1st, 2022 in the `avocado-corp` enterprise, and return the first page with a maximum of 100 items per page using [REST API pagination](/rest/overview/resources-in-the-rest-api#pagination):
|
||||
|
||||
```shell
|
||||
curl -H "Authorization: Bearer <em>TOKEN</em>" \
|
||||
curl -H "Authorization: Bearer TOKEN" \
|
||||
--request GET \
|
||||
"https://api.github.com/enterprises/avocado-corp/audit-log?phrase=created:2022-01-01&page=1&per_page=100"
|
||||
```
|
||||
@@ -133,7 +133,7 @@ You can specify multiple search phrases, such as `created` and `actor`, by separ
|
||||
The query below searches for audit log events for pull requests, where the event occurred on or after Jan 1st, 2022 in the `avocado-corp` enterprise, and the action was performed by the `octocat` user:
|
||||
|
||||
```shell
|
||||
curl -H "Authorization: Bearer <em>TOKEN</em>" \
|
||||
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"
|
||||
```
|
||||
|
||||
@@ -74,13 +74,13 @@ Before you can use the {% data variables.product.prodname_cli %} to add an SSH k
|
||||
To add an SSH authentication key to your GitHub account, use the `ssh-key add` subcommand, specifying your public key.
|
||||
|
||||
```shell
|
||||
gh ssh-key add <em>key-file</em>
|
||||
gh ssh-key add KEY-FILE
|
||||
```
|
||||
|
||||
To include a title for the new key, use the `-t` or `--title` flag.
|
||||
|
||||
```shell
|
||||
gh ssh-key add <em>key-file</em> --title "personal laptop"
|
||||
gh ssh-key add KEY-FILE --title "personal laptop"
|
||||
```
|
||||
|
||||
If you generated your SSH key by following the instructions in "[Generating a new SSH key](/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)", you can add the key to your account with this command.
|
||||
|
||||
@@ -44,17 +44,19 @@ If you are a site administrator for {% data variables.product.product_location %
|
||||
{%- ifversion ghae %}
|
||||
<!-- GitHub AE is FIPS 140-2 compliant. FIPS does not yet permit keys that use the ed25519 algorithm. -->
|
||||
```shell
|
||||
$ ssh-keygen -t rsa -b 4096 -C "<em>your_email@example.com</em>"
|
||||
$ ssh-keygen -t rsa -b 4096 -C "your_email@example.com"
|
||||
$ ssh-keygen -t rsa -b 4096 -C "your_email@example.com"
|
||||
|
||||
```
|
||||
{%- else %}
|
||||
```shell
|
||||
$ ssh-keygen -t ed25519 -C "<em>your_email@example.com</em>"
|
||||
$ ssh-keygen -t ed25519 -C "your_email@example.com"
|
||||
```
|
||||
{% note %}
|
||||
|
||||
**Note:** If you are using a legacy system that doesn't support the Ed25519 algorithm, use:
|
||||
```shell
|
||||
$ ssh-keygen -t rsa -b 4096 -C "<em>your_email@example.com</em>"
|
||||
$ ssh-keygen -t rsa -b 4096 -C "your_email@example.com"
|
||||
```
|
||||
|
||||
{% endnote %}
|
||||
@@ -62,14 +64,14 @@ If you are a site administrator for {% data variables.product.product_location %
|
||||
|
||||
This creates a new SSH key, using the provided email as a label.
|
||||
```shell
|
||||
> Generating public/private <em>algorithm</em> key pair.
|
||||
> Generating public/private ALGORITHM key pair.
|
||||
```
|
||||
3. When you're prompted to "Enter a file in which to save the key," press Enter. This accepts the default file location.
|
||||
|
||||
{% mac %}
|
||||
|
||||
```shell
|
||||
> Enter a file in which to save the key (/Users/<em>you</em>/.ssh/id_<em>algorithm</em>): <em>[Press enter]</em>
|
||||
> Enter a file in which to save the key (/Users/YOU/.ssh/id_ALGORITHM: [Press enter]
|
||||
```
|
||||
|
||||
{% endmac %}
|
||||
@@ -77,7 +79,7 @@ If you are a site administrator for {% data variables.product.product_location %
|
||||
{% windows %}
|
||||
|
||||
```shell
|
||||
> Enter a file in which to save the key (/c/Users/<em>you</em>/.ssh/id_<em>algorithm</em>):<em>[Press enter]</em>
|
||||
> Enter a file in which to save the key (/c/Users/YOU/.ssh/id_ALGORITHM):[Press enter]
|
||||
```
|
||||
|
||||
{% endwindows %}
|
||||
@@ -85,15 +87,15 @@ If you are a site administrator for {% data variables.product.product_location %
|
||||
{% linux %}
|
||||
|
||||
```shell
|
||||
> Enter a file in which to save the key (/home/<em>you</em>/.ssh/<em>algorithm</em>): <em>[Press enter]</em>
|
||||
> Enter a file in which to save the key (/home/YOU/.ssh/ALGORITHM):[Press enter]
|
||||
```
|
||||
|
||||
{% endlinux %}
|
||||
|
||||
4. At the prompt, type a secure passphrase. For more information, see ["Working with SSH key passphrases](/articles/working-with-ssh-key-passphrases)."
|
||||
```shell
|
||||
> Enter passphrase (empty for no passphrase): <em>[Type a passphrase]</em>
|
||||
> Enter same passphrase again: <em>[Type passphrase again]</em>
|
||||
> Enter passphrase (empty for no passphrase): [Type a passphrase]
|
||||
> Enter same passphrase again: [Type passphrase again]
|
||||
```
|
||||
|
||||
## Adding your SSH key to the ssh-agent
|
||||
@@ -110,7 +112,7 @@ Before adding a new SSH key to the ssh-agent to manage your keys, you should hav
|
||||
|
||||
```shell
|
||||
$ open ~/.ssh/config
|
||||
> The file /Users/<em>you</em>/.ssh/config does not exist.
|
||||
> The file /Users/YOU/.ssh/config does not exist.
|
||||
```
|
||||
|
||||
* If the file doesn't exist, create the file.
|
||||
@@ -198,7 +200,7 @@ If you are using macOS or Linux, you may need to update your SSH client or insta
|
||||
{% data reusables.command_line.open_the_multi_os_terminal %}
|
||||
3. Paste the text below, substituting in the email address for your account on {% data variables.product.product_name %}.
|
||||
```shell
|
||||
$ ssh-keygen -t {% ifversion ghae %}ecdsa{% else %}ed25519{% endif %}-sk -C "<em>your_email@example.com</em>"
|
||||
$ ssh-keygen -t {% ifversion ghae %}ecdsa{% else %}ed25519{% endif %}-sk -C "YOUR_EMAIL"
|
||||
```
|
||||
|
||||
{%- ifversion not ghae %}
|
||||
@@ -217,7 +219,7 @@ If you are using macOS or Linux, you may need to update your SSH client or insta
|
||||
{% mac %}
|
||||
|
||||
```shell
|
||||
> Enter a file in which to save the key (/Users/<em>you</em>/.ssh/id_{% ifversion ghae %}ecdsa{% else %}ed25519{% endif %}_sk): <em>[Press enter]</em>
|
||||
> Enter a file in which to save the key (/Users/YOU/.ssh/id_{% ifversion ghae %}ecdsa{% else %}ed25519{% endif %}_sk): [Press enter]
|
||||
```
|
||||
|
||||
{% endmac %}
|
||||
@@ -225,7 +227,7 @@ If you are using macOS or Linux, you may need to update your SSH client or insta
|
||||
{% windows %}
|
||||
|
||||
```shell
|
||||
> Enter a file in which to save the key (/c/Users/<em>you</em>/.ssh/id_{% ifversion ghae %}ecdsa{% else %}ed25519{% endif %}_sk):<em>[Press enter]</em>
|
||||
> Enter a file in which to save the key (/c/Users/YOU/.ssh/id_{% ifversion ghae %}ecdsa{% else %}ed25519{% endif %}_sk):[Press enter]
|
||||
```
|
||||
|
||||
{% endwindows %}
|
||||
@@ -233,14 +235,14 @@ If you are using macOS or Linux, you may need to update your SSH client or insta
|
||||
{% linux %}
|
||||
|
||||
```shell
|
||||
> Enter a file in which to save the key (/home/<em>you</em>/.ssh/id_{% ifversion ghae %}ecdsa{% else %}ed25519{% endif %}_sk): <em>[Press enter]</em>
|
||||
> Enter a file in which to save the key (/home/YOU/.ssh/id_{% ifversion ghae %}ecdsa{% else %}ed25519{% endif %}_sk):[Press enter]
|
||||
```
|
||||
|
||||
{% endlinux %}
|
||||
|
||||
6. When you are prompted to type a passphrase, press **Enter**.
|
||||
```shell
|
||||
> Enter passphrase (empty for no passphrase): <em>[Type a passphrase]</em>
|
||||
> Enter same passphrase again: <em>[Type passphrase again]</em>
|
||||
> Enter passphrase (empty for no passphrase): [Type a passphrase]
|
||||
> Enter same passphrase again: [Type passphrase again]
|
||||
```
|
||||
7. Add the SSH key to your account on {% data variables.product.prodname_dotcom %}. For more information, see "[Adding a new SSH key to your {% data variables.product.prodname_dotcom %} account](/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account)."
|
||||
|
||||
@@ -36,7 +36,7 @@ If you have multiple keys or are attempting to sign commits or tags with a key t
|
||||
|
||||
1. When committing changes in your local branch, add the -S flag to the git commit command:
|
||||
```shell
|
||||
$ git commit -S -m <em>"your commit message"</em>
|
||||
$ git commit -S -m "YOUR_COMMIT_MESSAGE"
|
||||
# Creates a signed commit
|
||||
```
|
||||
2. If you're using GPG, after you create your commit, provide the passphrase you set up when you [generated your GPG key](/articles/generating-a-new-gpg-key).
|
||||
|
||||
@@ -19,12 +19,12 @@ topics:
|
||||
|
||||
1. To sign a tag, add `-s` to your `git tag` command.
|
||||
```shell
|
||||
$ git tag -s <em>mytag</em>
|
||||
$ git tag -s MYTAG
|
||||
# Creates a signed tag
|
||||
```
|
||||
2. Verify your signed tag by running `git tag -v [tag-name]`.
|
||||
```shell
|
||||
$ git tag -v <em>mytag</em>
|
||||
$ git tag -v MYTAG
|
||||
# Verifies the signed tag
|
||||
```
|
||||
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Configuración de notificaciones para alertas de Dependabot
|
||||
title: Configuring notifications for Dependabot alerts
|
||||
shortTitle: Configure notifications
|
||||
intro: 'Optimiza la forma en la que recibes notificaciones de {% data variables.product.prodname_dependabot_alerts %}.'
|
||||
intro: 'Optimize how you receive notifications about {% data variables.product.prodname_dependabot_alerts %}.'
|
||||
redirect_from:
|
||||
- /github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies
|
||||
- /code-security/supply-chain-security/configuring-notifications-for-vulnerable-dependencies
|
||||
@@ -19,50 +19,51 @@ topics:
|
||||
- Vulnerabilities
|
||||
- Dependencies
|
||||
- Repositories
|
||||
ms.openlocfilehash: b8810c27a10302a7873fc61a32189f33855140bb
|
||||
ms.sourcegitcommit: ac00e2afa6160341c5b258d73539869720b395a4
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: es-ES
|
||||
ms.lasthandoff: 09/09/2022
|
||||
ms.locfileid: '147878563'
|
||||
---
|
||||
## Acerca de las notificaciones de {% data variables.product.prodname_dependabot_alerts %}
|
||||
|
||||
Cuando {% data variables.product.prodname_dependabot %} detecta las dependencias vulnerables{% ifversion GH-advisory-db-supports-malware %} o el malware{% endif %} en tus repositorios, generamos una alerta del {% data variables.product.prodname_dependabot %} y la mostramos en la pestaña Seguridad del repositorio. {% data variables.product.product_name %} notifica a los mantenedores de los repositorios afectados sobre la alerta nueva de acuerdo con sus preferencias de notificaciones.{% ifversion fpt or ghec %} {% data variables.product.prodname_dependabot %} está habilitado de forma predeterminada en todos los repositorios públicos. En el caso de las {% data variables.product.prodname_dependabot_alerts %}, predeterminadamente, recibirás {% data variables.product.prodname_dependabot_alerts %} por correo electrónico, agrupadas por la vulnerabilidad específica.
|
||||
## About notifications for {% data variables.product.prodname_dependabot_alerts %}
|
||||
|
||||
When {% data variables.product.prodname_dependabot %} detects vulnerable dependencies{% ifversion GH-advisory-db-supports-malware %} or malware{% endif %} in your repositories, we generate a {% data variables.product.prodname_dependabot %} alert and display it on the Security tab for the repository. {% data variables.product.product_name %} notifies the maintainers of affected repositories about the new alert according to their notification preferences.{% ifversion fpt or ghec %} {% data variables.product.prodname_dependabot %} is enabled by default on all public repositories. For {% data variables.product.prodname_dependabot_alerts %}, by default, you will receive {% data variables.product.prodname_dependabot_alerts %} by email, grouped by the specific vulnerability.
|
||||
{% endif %}
|
||||
|
||||
{% ifversion fpt or ghec %} Si eres propietario de la organización, puedes habilitar o deshabilitar {% data variables.product.prodname_dependabot_alerts %} para todos los repositorios de la organización con un solo clic. También puedes establecer si {% data variables.product.prodname_dependabot_alerts %} se habilitarán o deshabilitarán para los repositorios recién creados. Para más información, vea "[Administración de la configuración de seguridad y análisis para la organización](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization#enabling-or-disabling-a-feature-for-all-new-repositories-when-they-are-added)".
|
||||
{% ifversion fpt or ghec %}If you're an organization owner, you can enable or disable {% data variables.product.prodname_dependabot_alerts %} for all repositories in your organization with one click. You can also set whether {% data variables.product.prodname_dependabot_alerts %} will be enabled or disabled for newly-created repositories. For more information, see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization#enabling-or-disabling-a-feature-for-all-new-repositories-when-they-are-added)."
|
||||
{% endif %}
|
||||
|
||||
{% ifversion ghes or ghae %} De forma predeterminada, si el propietario de tu empresa configuró las notificaciones por correo electrónico en ella, recibirás {% data variables.product.prodname_dependabot_alerts %} por este medio.
|
||||
{% ifversion ghes or ghae %}
|
||||
By default, if your enterprise owner has configured email for notifications on your enterprise, you will receive {% data variables.product.prodname_dependabot_alerts %} by email.
|
||||
|
||||
Los propietarios de empresas también pueden habilitar las {% data variables.product.prodname_dependabot_alerts %} sin notificaciones. Para obtener más información, consulte "[Habilitación de {% data variables.product.prodname_dependabot %} para la empresa](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)".
|
||||
Enterprise owners can also enable {% data variables.product.prodname_dependabot_alerts %} without notifications. For more information, see "[Enabling {% data variables.product.prodname_dependabot %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)."
|
||||
{% endif %}
|
||||
|
||||
## Configurar las notificaciones para las {% data variables.product.prodname_dependabot_alerts %}
|
||||
## Configuring notifications for {% data variables.product.prodname_dependabot_alerts %}
|
||||
|
||||
{% ifversion fpt or ghes or ghec %} Cuando se detecta una alerta nueva de {% data variables.product.prodname_dependabot %}, {% data variables.product.product_name %} notifica a todos los usuarios del repositorio con acceso a las {% data variables.product.prodname_dependabot_alerts %} de acuerdo con sus preferencias de notificación. Recibirás las alertas si estás observando el repositorio, si habilitas las notificaciones para las alertas de seguridad para toda la actividad del repositorio y si es que no lo estás ignorando. Para más información, vea "[Configuración de notificaciones](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#configuring-your-watch-settings-for-an-individual-repository)".
|
||||
{% ifversion fpt or ghes or ghec %}
|
||||
When a new {% data variables.product.prodname_dependabot %} alert is detected, {% data variables.product.product_name %} notifies all users with access to {% data variables.product.prodname_dependabot_alerts %} for the repository according to their notification preferences. You will receive alerts if you are watching the repository, have enabled notifications for security alerts or for all the activity on the repository, and are not ignoring the repository. For more information, see "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#configuring-your-watch-settings-for-an-individual-repository)."
|
||||
{% endif %}
|
||||
|
||||
Puedes configurar los ajustes de notificaciones para ti mismo o para tu organización desde el menú desplegable de administrar notificaciones {% octicon "bell" aria-label="The notifications bell" %} que se muestra en la parte superior de cada página. Para más información, vea "[Configuración de notificaciones](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#choosing-your-notification-settings)".
|
||||
You can configure notification settings for yourself or your organization from the Manage notifications drop-down {% octicon "bell" aria-label="The notifications bell" %} shown at the top of each page. For more information, see "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#choosing-your-notification-settings)."
|
||||
|
||||
{% data reusables.notifications.vulnerable-dependency-notification-delivery-method-customization2 %} {% data reusables.notifications.vulnerable-dependency-notification-options %}
|
||||
{% data reusables.notifications.vulnerable-dependency-notification-delivery-method-customization2 %}
|
||||
{% data reusables.notifications.vulnerable-dependency-notification-options %}
|
||||
|
||||
{% ifversion update-notification-settings-22 %}
|
||||
{% else %}
|
||||
{% endif %}
|
||||
|
||||
|
||||
|
||||
{% note %}
|
||||
|
||||
**Nota**: Puedes filtrar tus notificaciones en {% data variables.product.company_short %} para mostrar {% data variables.product.prodname_dependabot_alerts %}. Para más información, vea "[Administración de notificaciones de la Bandeja de entrada](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#dependabot-custom-filters)".
|
||||
**Note:** You can filter your notifications on {% data variables.product.company_short %} to show {% data variables.product.prodname_dependabot_alerts %}. For more information, see "[Managing notifications from your inbox](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#dependabot-custom-filters)."
|
||||
|
||||
{% endnote %}
|
||||
|
||||
{% data reusables.repositories.security-alerts-x-github-severity %} Para obtener más información, consulta "[Configuración de notificaciones](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#filtering-email-notifications)".
|
||||
{% data reusables.repositories.security-alerts-x-github-severity %} For more information, see "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#filtering-email-notifications)."
|
||||
|
||||
## Cómo reducir el ruido de las notificaciones de {% data variables.product.prodname_dependabot_alerts %}
|
||||
## How to reduce the noise from notifications for {% data variables.product.prodname_dependabot_alerts %}
|
||||
|
||||
Si te preocupa recibir demasiadas notificaciones para las {% data variables.product.prodname_dependabot_alerts %}, te recomendamos que te unas al resumen semanal por correo electrónico o que apagues las notificaciones mientras mantienes habilitadas las {% data variables.product.prodname_dependabot_alerts %}. Todavía puedes navegar para ver los {% data variables.product.prodname_dependabot_alerts %} en la pestaña Seguridad del repositorio. Para obtener más información, consulta "[Visualización y actualización de {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts)".
|
||||
If you are concerned about receiving too many notifications for {% data variables.product.prodname_dependabot_alerts %}, we recommend you opt into the weekly email digest, or turn off notifications while keeping {% data variables.product.prodname_dependabot_alerts %} enabled. You can still navigate to see your {% data variables.product.prodname_dependabot_alerts %} in your repository's Security tab. For more information, see "[Viewing and updating {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts)."
|
||||
|
||||
## Información adicional
|
||||
## Further reading
|
||||
|
||||
- "[Configuración de notificaciones](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications)"
|
||||
- "[Administración de notificaciones desde la bandeja de entrada](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#supported-is-queries)"
|
||||
- "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications)"
|
||||
- "[Managing notifications from your inbox](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#supported-is-queries)"
|
||||
|
||||
@@ -33,6 +33,12 @@ You must store this file in the `.github` directory of your repository. When you
|
||||
|
||||
Any options that also affect security updates are used the next time a security alert triggers a pull request for a security update. For more information, see "[Configuring {% data variables.product.prodname_dependabot_security_updates %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-dependabot-security-updates)."
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** You cannot configure {% data variables.product.prodname_dependabot_alerts %} using the *dependabot.yml* file.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
The *dependabot.yml* file has two mandatory top-level keys: `version`, and `updates`. You can, optionally, include a top-level `registries` key{% ifversion ghes = 3.5 %} and/or a `enable-beta-ecosystems` key{% endif %}. The file must start with `version: 2`.
|
||||
|
||||
## Configuration options for the *dependabot.yml* file
|
||||
|
||||
@@ -42,9 +42,9 @@ While {% data variables.product.prodname_github_codespaces %} provides the benef
|
||||
|
||||
While this option does not configure a development environment for you, it will allow you to make changes to your source code as needed while you wait for the service disruption to resolve.
|
||||
|
||||
## Option 4: Use Remote-Containers and Docker for a local containerized environment
|
||||
## Option 4: Use the Dev Containers extension and Docker for a local containerized environment
|
||||
|
||||
If your repository has a `devcontainer.json`, consider using the [Remote-Containers extension](https://code.visualstudio.com/docs/remote/containers#_quick-start-open-a-git-repository-or-github-pr-in-an-isolated-container-volume) in {% data variables.product.prodname_vscode %} to build and attach to a local development container for your repository. The setup time for this option will vary depending on your local specifications and the complexity of your dev container setup.
|
||||
If your repository has a `devcontainer.json`, consider using the [Dev Containers extension](https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.remote-containers) in {% data variables.product.prodname_vscode %} to build and attach to a local development container for your repository. The setup time for this option will vary depending on your local specifications and the complexity of your dev container setup. For more information, see "[Developing inside a container](https://code.visualstudio.com/docs/remote/containers#_quick-start-open-a-git-repository-or-github-pr-in-an-isolated-container-volume)" in the {% data variables.product.prodname_vscode_shortname %} documentation.
|
||||
|
||||
{% note %}
|
||||
|
||||
|
||||
@@ -79,4 +79,4 @@ For more information on deleting a codespace, see "[Deleting a codespace](/codes
|
||||
|
||||
{% data variables.product.prodname_github_codespaces %} is a cloud-based development environment and requires an internet connection. If you lose connection to the internet while working in a codespace, you will not be able to access your codespace. However, any uncommitted changes will be saved. When you have access to an internet connection again, you can connect to your codespace in the exact same state that it was left in. If you have an unstable internet connection, you should commit and push your changes often.
|
||||
|
||||
If you know that you will often be working offline, you can use your `devcontainer.json` file with the ["{% data variables.product.prodname_vscode %} Remote - Containers" extension](https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.remote-containers) to build and attach to a local development container for your repository. For more information, see [Developing inside a container](https://code.visualstudio.com/docs/remote/containers) in the {% data variables.product.prodname_vscode %} documentation.
|
||||
If you know that you will often be working offline, you can use your `devcontainer.json` file with the ["Dev Containers" extension](https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.remote-containers) for {% data variables.product.prodname_vscode_shortname %} to build and attach to a local development container for your repository. For more information, see [Developing inside a container](https://code.visualstudio.com/docs/remote/containers) in the {% data variables.product.prodname_vscode %} documentation.
|
||||
|
||||
@@ -73,6 +73,8 @@ Organization owners can specify who can create and use codespaces at the organiz
|
||||
|
||||
|
||||
|
||||
If codespaces for this repository are billable, a message is displayed below the **Create codespace on BRANCH** button telling you who will pay for the codespace.
|
||||
|
||||
1. Create your codespace, either using the default options, or after configuring advanced options:
|
||||
|
||||
* **Use the default options**
|
||||
@@ -131,12 +133,12 @@ To create a new codespace, use the `gh codespace create` subcommand.
|
||||
gh codespace create
|
||||
```
|
||||
|
||||
You are prompted to choose a repository, a branch, a dev container configuration file (if more than one is available), and a machine type (if more than one is available).
|
||||
You are prompted to choose a repository. If codespaces for this repository are billable, a message is displayed telling you who will pay for the codespace. You are then prompted to choose a branch, a dev container configuration file (if more than one is available), and a machine type (if more than one is available).
|
||||
|
||||
Alternatively, you can use flags to specify some or all of the options:
|
||||
|
||||
```shell
|
||||
gh codespace create -r <em>owner</em>/<em>repo</em> -b <em>branch</em> --devcontainer-path <em>path</em> -m <em>machine-type</em>
|
||||
gh codespace create -r OWNER/REPO -b BRANCH --devcontainer-path PATH -m MACHINE-TYPE
|
||||
```
|
||||
|
||||
In this example, replace `owner/repo` with the repository identifier. Replace `branch` with the name of the branch, or the full SHA hash of the commit, that you want to be initially checked out in the codespace. If you use the `-r` flag without the `b` flag, the codespace is created from the default branch.
|
||||
|
||||
@@ -78,7 +78,7 @@ By default, {% data variables.product.prodname_github_codespaces %} forwards por
|
||||
To forward a port use the `gh codespace ports forward` subcommand. Replace `codespace-port:local-port` with the remote and local ports that you want to connect. After entering the command choose from the list of codespaces that's displayed.
|
||||
|
||||
```shell
|
||||
gh codespace ports forward <em>codespace-port</em>:<em>local-port</em>
|
||||
gh codespace ports forward CODESPACE-PORT:LOCAL-PORT
|
||||
```
|
||||
|
||||
For more information about this command, see [the {% data variables.product.prodname_cli %} manual](https://cli.github.com/manual/gh_codespace_ports_forward).
|
||||
@@ -132,7 +132,7 @@ To change the visibility of a forwarded port, use the `gh codespace ports visibi
|
||||
Replace `codespace-port` with the forwarded port number. Replace `setting` with `private`, `org`, or `public`. After entering the command choose from the list of codespaces that's displayed.
|
||||
|
||||
```shell
|
||||
gh codespace ports visibility <em>codespace-port</em>:<em>setting</em>
|
||||
gh codespace ports visibility CODESPACE-PORT:SETTINGS
|
||||
```
|
||||
|
||||
You can set the visibility for multiple ports with one command. For example:
|
||||
|
||||
@@ -62,7 +62,7 @@ For a complete reference of `gh` commands for {% data variables.product.prodname
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note**: The `-c <em>codespace-name</em>` flag, used with many commands, is optional. If you omit it a list of codespaces is displayed for you to choose from.
|
||||
**Note**: The `-c CODESPACE_NAME` flag, used with many commands, is optional. If you omit it a list of codespaces is displayed for you to choose from.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
@@ -77,7 +77,7 @@ The list includes the unique name of each codespace, which you can use in other
|
||||
### Create a new codespace
|
||||
|
||||
```shell
|
||||
gh codespace create -r <em>owner/repository</em> [-b <em>branch</em>]
|
||||
gh codespace create -r OWNER/REPO_NAME [-b BRANCH]
|
||||
```
|
||||
|
||||
For more information, see "[Creating a codespace](/codespaces/developing-in-codespaces/creating-a-codespace)."
|
||||
@@ -85,7 +85,7 @@ For more information, see "[Creating a codespace](/codespaces/developing-in-code
|
||||
### Stop a codespace
|
||||
|
||||
```shell
|
||||
gh codespace stop -c <em>codespace-name</em>
|
||||
gh codespace stop -c CODESPACE-NAME
|
||||
```
|
||||
|
||||
For more information, see "[Deep dive into {% data variables.product.prodname_github_codespaces %}](/codespaces/getting-started/deep-dive#closing-or-stopping-your-codespace)."
|
||||
@@ -93,7 +93,7 @@ For more information, see "[Deep dive into {% data variables.product.prodname_gi
|
||||
### Delete a codespace
|
||||
|
||||
```shell
|
||||
gh codespace delete -c <em>codespace-name</em>
|
||||
gh codespace delete -c CODESPACE-NAME
|
||||
```
|
||||
|
||||
For more information, see "[Deleting a codespace](/codespaces/developing-in-codespaces/deleting-a-codespace)."
|
||||
@@ -103,7 +103,7 @@ For more information, see "[Deleting a codespace](/codespaces/developing-in-code
|
||||
To run commands on the remote codespace machine, from your terminal, you can SSH into the codespace.
|
||||
|
||||
```shell
|
||||
gh codespace ssh -c <em>codespace-name</em>
|
||||
gh codespace ssh -c CODESPACE-NAME
|
||||
```
|
||||
|
||||
{% data variables.product.prodname_github_codespaces %} copies your GitHub SSH keys into the codespace on creation for a seamless authentication experience. You may be asked to enter the passphrase for your SSH key, after which you will get a command prompt from the remote codespace machine.
|
||||
@@ -113,7 +113,7 @@ If you don't have any SSH keys, follow the instructions in "[Generating a new SS
|
||||
### Open a codespace in {% data variables.product.prodname_vscode %}
|
||||
|
||||
```shell
|
||||
gh codespace code -c <em>codespace-name</em>
|
||||
gh codespace code -c CODESPACE-NAME
|
||||
```
|
||||
|
||||
For more information, see "[Using {% data variables.product.prodname_github_codespaces %} in {% data variables.product.prodname_vscode %}](/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code)."
|
||||
@@ -121,13 +121,13 @@ For more information, see "[Using {% data variables.product.prodname_github_code
|
||||
### Open a codespace in JupyterLab
|
||||
|
||||
```shell
|
||||
gh codespace jupyter -c <em>codespace-name</em>
|
||||
gh codespace jupyter -c CODESPACE-NAME
|
||||
```
|
||||
|
||||
### Copy a file to/from a codespace
|
||||
|
||||
```shell
|
||||
gh codespace cp [-r] <em>source(s)</em> <em>destination</em>
|
||||
gh codespace cp [-r] SOURCE(S) DESTINATION
|
||||
```
|
||||
|
||||
Use the prefix `remote:` on a file or directory name to indicate that it's on the codespace. As with the UNIX `cp` command, the first argument specifies the source and the last specifies the destination. If the destination is a directory, you can specify multiple sources. Use the `-r` (recursive) flag if any of the sources is a directory.
|
||||
@@ -171,7 +171,7 @@ For more information about the `gh codespace cp` command, including additional f
|
||||
You can forward a port on a codespace to a local port. The port remains forwarded as long as the process is running. To stop forwarding the port, press <kbd>Control</kbd>+<kbd>C</kbd>.
|
||||
|
||||
```shell
|
||||
gh codespace ports forward <em>codespace-port-number</em>:<em>local-port-number</em> -c <em>codespace-name</em>
|
||||
gh codespace ports forward CODESPACE-PORT_NAME:LOCAL-PORT-NAME -c CODESPACE-NAME
|
||||
```
|
||||
|
||||
To see details of forwarded ports enter `gh codespace ports` and then choose a codespace.
|
||||
@@ -179,13 +179,13 @@ To see details of forwarded ports enter `gh codespace ports` and then choose a c
|
||||
You can set the visibility of a forwarded port. {% data reusables.codespaces.port-visibility-settings %}
|
||||
|
||||
```shell
|
||||
gh codespace ports visibility <em>codespace-port</em>:<em>private|org|public</em> -c <em>codespace-name</em>
|
||||
gh codespace ports visibility CODESPACE-PORT:private|org|public -c CODESPACE-NAME
|
||||
```
|
||||
|
||||
You can set the visibility for multiple ports with one command. For example:
|
||||
|
||||
```shell
|
||||
gh codespace ports visibility 80:private 3000:public 3306:org -c <em>codespace-name</em>
|
||||
gh codespace ports visibility 80:private 3000:public 3306:org -c CODESPACE-NAME
|
||||
```
|
||||
|
||||
For more information, see "[Forwarding ports in your codespace](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace)."
|
||||
@@ -195,7 +195,7 @@ For more information, see "[Forwarding ports in your codespace](/codespaces/deve
|
||||
You can see the creation log for a codespace. After entering this command you will be asked to enter the passphrase for your SSH key.
|
||||
|
||||
```shell
|
||||
gh codespace logs -c <em>codespace-name</em>
|
||||
gh codespace logs -c CODESPACE-NAME
|
||||
```
|
||||
|
||||
For more information about the creation log, see "[{% data variables.product.prodname_github_codespaces %} logs](/codespaces/troubleshooting/github-codespaces-logs#creation-logs)."
|
||||
|
||||
@@ -41,3 +41,5 @@ You can also personalize aspects of your codespace environment by using a public
|
||||
For information on pricing, storage, and usage for {% data variables.product.prodname_github_codespaces %}, see "[About billing for {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces)."
|
||||
|
||||
{% data reusables.codespaces.codespaces-spending-limit-requirement %} For information on how organizations owners and billing managers can manage the spending limit for {% data variables.product.prodname_github_codespaces %} for an organization, see "[Managing spending limits for {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-github-codespaces)."
|
||||
|
||||
You can see who will pay for a codespace before you create it. For more information, see "[Creating a codespace](/codespaces/developing-in-codespaces/creating-a-codespace#creating-a-codespace)."
|
||||
@@ -27,9 +27,7 @@ Before you can configure prebuilds for your project the following must be true:
|
||||
|
||||
## Configuring a prebuild
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
{% data reusables.repositories.sidebar-settings %}
|
||||
1. In the "Code & automation" section of the sidebar, click **{% octicon "codespaces" aria-label="The Codespaces icon" %} {% data variables.product.prodname_codespaces %}**.
|
||||
{% data reusables.codespaces.accessing-prebuild-configuration %}
|
||||
1. In the "Prebuild configuration" section of the page, click **Set up prebuild**.
|
||||
|
||||
|
||||
@@ -80,6 +78,12 @@ Before you can configure prebuilds for your project the following must be true:
|
||||
|
||||
|
||||
|
||||
1. Optionally, at the bottom of the page, click **Show advanced options**.
|
||||
|
||||
|
||||
|
||||
In the "Advanced options" section, if you select **Disable prebuild optimization**, codespaces will be created without a prebuild if the latest prebuild workflow has failed or is currently running. For more information, see "[Troubleshooting prebuilds](/codespaces/troubleshooting/troubleshooting-prebuilds#preventing-out-of-date-prebuilds-being-used)."
|
||||
|
||||
1. Click **Create**.
|
||||
|
||||
{% data reusables.codespaces.prebuilds-permission-authorization %}
|
||||
|
||||
@@ -126,7 +126,7 @@ You can choose from a list of predefined configurations to create a dev containe
|
||||
|
||||
Using a predefined configuration is a great idea if you need some additional extensibility. You can also start with a predefined configuration and amend it as needed for your project. For more information about the definitions of predefined dev containers, see the [`devcontainers/images`](https://github.com/devcontainers/images/tree/main/src) repository.
|
||||
|
||||
You can add a predefined dev container configuration either while working in a codespace, or while working on a repository locally. To do this in {% data variables.product.prodname_vscode_shortname %} while you are working locally, and not connected to a codespace, you must have the "Remote - Containers" extension installed and enabled. For more information about this extension, see the [{% data variables.product.prodname_vs_marketplace_shortname %}](https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.remote-containers). The following procedure describes the process when you are using a codespace. The steps in {% data variables.product.prodname_vscode_shortname %} when you are not connected to a codespace are very similar.
|
||||
You can add a predefined dev container configuration either while working in a codespace, or while working on a repository locally. To do this in {% data variables.product.prodname_vscode_shortname %} while you are working locally, and not connected to a codespace, you must have the "Dev Containers" extension installed and enabled. For more information about this extension, see the [{% data variables.product.prodname_vs_marketplace_shortname %}](https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.remote-containers). The following procedure describes the process when you are using a codespace. The steps in {% data variables.product.prodname_vscode_shortname %} when you are not connected to a codespace are very similar.
|
||||
|
||||
{% data reusables.codespaces.command-palette-container %}
|
||||
1. Click the definition you want to use.
|
||||
|
||||
@@ -30,6 +30,38 @@ If you create a codespace and it does not open:
|
||||
|
||||
If you still cannot create a codespace for a repository where {% data variables.product.prodname_github_codespaces %} is available, {% data reusables.codespaces.contact-support %}
|
||||
|
||||
### Codespace creation fails
|
||||
|
||||
If the creation of a codespace fails, it's likely to be due to a temporary infrastructure issue in the cloud - for example, a problem provisioning a virtual machine for the codespace. A less common reason for failure is if it takes longer than an hour to build the container. In this case, the build is cancelled and codespace creation will fail.
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** A codespace that was not successfully created is never going to be usable and should be deleted. For more information, see "[Deleting a codespace](/codespaces/developing-in-codespaces/deleting-a-codespace)."
|
||||
|
||||
{% endnote %}
|
||||
|
||||
If you create a codespace and the creation fails:
|
||||
|
||||
1. Check {% data variables.product.prodname_dotcom %}'s [Status page](https://githubstatus.com) for any active incidents.
|
||||
1. Go to [your {% data variables.product.prodname_github_codespaces %} page](https://github.com/codespaces), delete the codespace, and create a new codespace.
|
||||
1. If the container is building, look at the logs that are streaming and make sure the build is not stuck. A container build that takes longer than one hour will be canceled, resulting in a failed creation.
|
||||
|
||||
One common scenario where this could happen is if you have a script running that is prompting for user input and waiting for an answer. If this is the case, remove the interactive prompt so that the build can complete non-interactively.
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note**: To view the logs during a build:
|
||||
* In the browser, click **View logs.**
|
||||
|
||||
|
||||
|
||||
* In the VS Code desktop application, click **Building codespace** in the "Setting up remote connection" that's displayed.
|
||||
|
||||
|
||||
|
||||
{% endnote %}
|
||||
2. If you have a container that takes a long time to build, consider using prebuilds to speed up codespace creations. For more information, see "[Configuring prebuilds](/codespaces/prebuilding-your-codespaces/configuring-prebuilds#configuring-a-prebuild)."
|
||||
|
||||
## Deleting codespaces
|
||||
|
||||
The owner of a codespace has full control over it and only they can delete their codespaces. You cannot delete a codespace created by another user.
|
||||
|
||||
@@ -65,6 +65,24 @@ If the `devcontainer.json` configuration file for a prebuild configuration is up
|
||||
|
||||
If the workflow runs for a prebuild configuration are failing, you can temporarily disable the prebuild configuration while you investigate. For more information, see "[Managing prebuilds](/codespaces/prebuilding-your-codespaces/managing-prebuilds#disabling-a-prebuild-configuration)."
|
||||
|
||||
### Preventing out-of-date prebuilds being used
|
||||
|
||||
By default, if the latest prebuild workflow has failed, then a previous prebuild for the same combination of repository, branch, and `devcontainer.json` configuration file will be used to create new codespaces. This behavior is called prebuild optimization.
|
||||
|
||||
We recommend keeping prebuild optimization enabled, because it helps ensure that codespaces can still be created quickly if an up-to-date prebuild is not available. However, as a repository administrator, you can disable prebuild optimization if you run into problems with prebuilt codespaces being behind the current state of the branch. If you disable prebuild optimization, codespaces for the relevant combination of repository, branch, and `devcontainer.json` file will be created without a prebuild if the latest prebuild workflow has failed or is currently running.
|
||||
|
||||
{% data reusables.codespaces.accessing-prebuild-configuration %}
|
||||
1. To the right of the affected prebuild configuration, select the ellipsis (**...**), then click **Edit**.
|
||||
|
||||
|
||||
1. Scroll to the bottom of the "Edit configuration" page and click **Show advanced options**.
|
||||
|
||||
|
||||
1. If you're sure you want to disable the default setting, select **Disable prebuild optimization**.
|
||||
|
||||
|
||||
1. To save your change, click **Update**.
|
||||
|
||||
## Further reading
|
||||
|
||||
- "[Configuring prebuilds](/codespaces/prebuilding-your-codespaces/configuring-prebuilds)"
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Configurar pautas para los colaboradores de repositorios
|
||||
intro: Puedes crear pautas para comunicar cómo pueden contribuir las personas a tu proyecto.
|
||||
title: Setting guidelines for repository contributors
|
||||
intro: You can create guidelines to communicate how people should contribute to your project.
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
@@ -13,59 +13,56 @@ redirect_from:
|
||||
topics:
|
||||
- Community
|
||||
shortTitle: Contributor guidelines
|
||||
ms.openlocfilehash: b418c5a3d10f8b8f7572f33b17a9ebfbb3de27d3
|
||||
ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: es-ES
|
||||
ms.lasthandoff: 09/05/2022
|
||||
ms.locfileid: '147578792'
|
||||
---
|
||||
## Acerca de los lineamientos de contribución
|
||||
Para ayudar a los colaboradores de su proyecto a realizar un buen trabajo, puede agregar un archivo con las pautas de contribución a la raíz del repositorio del proyecto, `docs` o la carpeta `.github`. Cuando alguien abre una solicitud de extracción o crea una propuesta, verán un enlace a ese archivo. El vínculo a las pautas de contribución también aparece en la página `contribute` del repositorio. Para obtener un ejemplo de una página `contribute`, vea [github/docs/contribute](https://github.com/github/docs/contribute).
|
||||
## About contributing guidelines
|
||||
To help your project contributors do good work, you can add a file with contribution guidelines to your project repository's root, `docs`, or `.github` folder. When someone opens a pull request or creates an issue, they will see a link to that file. The link to the contributing guidelines also appears on your repository's `contribute` page. For an example of a `contribute` page, see [github/docs/contribute](https://github.com/github/docs/contribute).
|
||||
|
||||
|
||||
|
||||
Para el propietario del repositorio, las pautas de contribución son una manera de comunicar cómo deben contribuir las personas.
|
||||
For the repository owner, contribution guidelines are a way to communicate how people should contribute.
|
||||
|
||||
Para los colaboradores, las pautas los ayudan a verificar que están presentando solicitudes de extracción conformadas correctamente y abriendo propuestas útiles.
|
||||
For contributors, the guidelines help them verify that they're submitting well-formed pull requests and opening useful issues.
|
||||
|
||||
Tanto para los propietarios como para los colaboradores, las pautas de contribución ahorran tiempo y evitan inconvenientes generados por solicitudes de extracción o propuestas creadas de manera incorrecta que deben ser rechazadas o se deben volver a presentar.
|
||||
For both owners and contributors, contribution guidelines save time and hassle caused by improperly created pull requests or issues that have to be rejected and re-submitted.
|
||||
|
||||
{% ifversion fpt or ghes or ghec %}
|
||||
|
||||
Puedes crear pautas de contribución predeterminadas para tu organización{% ifversion fpt or ghes or ghec %} o cuenta personal{% endif %}. 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 default contribution guidelines for your organization{% ifversion fpt or ghes or ghec %} or personal account{% endif %}. 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**: los mantenedores de repositorios pueden establecer pautas específicas para las incidencias creando una plantilla de incidencia o de solicitud de incorporación de cambios para el repositorio. Para más información, vea "[Acerca de las plantillas de incidencias y solicitudes de incorporación de cambios](/articles/about-issue-and-pull-request-templates)".
|
||||
**Tip:** Repository maintainers can set specific guidelines for issues by creating an issue or pull request template for the repository. For more information, see "[About issue and pull request templates](/articles/about-issue-and-pull-request-templates)."
|
||||
|
||||
{% endtip %}
|
||||
|
||||
## Agregar un archivo *CONTRIBUTING*
|
||||
## Adding a *CONTRIBUTING* file
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %} {% data reusables.files.add-file %}
|
||||
3. Decida si quiere almacenar las pautas de contribución en la raíz del repositorio, en `docs` o en el directorio `.github`. Después, en el campo nombre de archivo, escribe el nombre y la extensión del archivo. Los nombres de archivo de los lineamientos de contribución no distinguen entre mayúsculas y minúsculas. Los archivos se interpretan en formato de texto rico si la extensión de archivo se encuentra en un formato compatible. Para obtener más información, vea "[Trabajar con archivos que no son de código](/repositories/working-with-files/using-files/working-with-non-code-files#rendering-differences-in-prose-documents)".
|
||||
|
||||
- Para hacer visibles sus pautas de contribución en el directorio raíz del repositorio, escriba *CONTRIBUTING*.
|
||||
- Para hacer visible sus pautas de contribución en el directorio `docs` del repositorio, escriba *docs/* para crear el directorio y luego *CONTRIBUTING*.
|
||||
- Si un repositorio contiene más de un archivo *CONTRIBUTING*, el archivo que se muestra en los vínculos se elige de las ubicaciones en el siguiente orden: el directorio `.github`, luego el directorio raíz del repositorio y finalmente el directorio `docs`.
|
||||
4. En el nuevo archivo, agrega las pautas de contribución. Pueden incluir:
|
||||
- Pasos para crear buenas propuestas o solicitudes de extracción.
|
||||
- Enlaces a la documentación externa, listas de correos o un código de conducta.
|
||||
- Expectativas de comportamiento y de la comunidad.
|
||||
{% data reusables.files.write_commit_message %} {% data reusables.files.choose_commit_branch %} {% data reusables.files.propose_new_file %}
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
{% data reusables.files.add-file %}
|
||||
3. Decide whether to store your contributing guidelines in your repository's root, `docs`, or `.github` directory. Then, in the filename field, type the name and extension for the file. Contributing guidelines filenames are not case sensitive. Files are rendered in rich text format if the file extension is in a supported format. For more information, see "[Working with non-code files](/repositories/working-with-files/using-files/working-with-non-code-files#rendering-differences-in-prose-documents)."
|
||||
|
||||
- To make your contributing guidelines visible in the repository's root directory, type *CONTRIBUTING*.
|
||||
- To make your contributing guidelines visible in the repository's `docs` directory, type *docs/* to create the new directory, then *CONTRIBUTING*.
|
||||
- If a repository contains more than one *CONTRIBUTING* file, then the file shown in links is chosen from locations in the following order: the `.github` directory, then the repository's root directory, and finally the `docs` directory.
|
||||
4. In the new file, add contribution guidelines. These could include:
|
||||
- Steps for creating good issues or pull requests.
|
||||
- Links to external documentation, mailing lists, or a code of conduct.
|
||||
- Community and behavioral expectations.
|
||||
{% data reusables.files.write_commit_message %}
|
||||
{% data reusables.files.choose_commit_branch %}
|
||||
{% data reusables.files.propose_new_file %}
|
||||
|
||||
## Ejemplos de pautas de contribución
|
||||
## Examples of contribution guidelines
|
||||
|
||||
Si estás confundido, aquí hay algunos buenos ejemplos de pautas de contribución:
|
||||
If you're stumped, here are some good examples of contribution guidelines:
|
||||
|
||||
- [Pautas de contribución](https://github.com/atom/atom/blob/master/CONTRIBUTING.md) del editor Atom.
|
||||
- [Pautas de contribución](https://github.com/rails/rails/blob/main/CONTRIBUTING.md) de Ruby on Rails.
|
||||
- [Pautas de contribución](https://github.com/opengovernment/opengovernment/blob/master/CONTRIBUTING.md) de Open Government.
|
||||
- The {% data variables.product.prodname_docs %} [contribution guidelines](https://github.com/github/docs/blob/main/CONTRIBUTING.md).
|
||||
- The Ruby on Rails [contribution guidelines](https://github.com/rails/rails/blob/main/CONTRIBUTING.md).
|
||||
- The Open Government [contribution guidelines](https://github.com/opengovernment/opengovernment/blob/master/CONTRIBUTING.md).
|
||||
|
||||
## Información adicional
|
||||
- La sección de Guías de código abierto "[Iniciar un proyecto de código abierto](https://opensource.guide/starting-a-project/)"{% ifversion fpt or ghec %}
|
||||
## Further reading
|
||||
- The Open Source Guides' section "[Starting an Open Source Project](https://opensource.guide/starting-a-project/)"{% ifversion fpt or ghec %}
|
||||
- [{% data variables.product.prodname_learning %}]({% data variables.product.prodname_learning_link %}){% endif %}{% ifversion fpt or ghes or ghec %}
|
||||
- "[Agregar una licencia a un repositorio](/articles/adding-a-license-to-a-repository)"{% endif %}
|
||||
- "[Adding a license to a repository](/articles/adding-a-license-to-a-repository)"{% endif %}
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Realizar cambios en una rama
|
||||
intro: 'Usa tu editor de texto favorito, como [Atom](https://atom.io/), para realizar cambios en el proyecto y, a continuación, utiliza {% data variables.product.prodname_desktop %} para visualizar confirmaciones útiles.'
|
||||
title: Making changes in a branch
|
||||
intro: 'Use your favorite text editor, such as [{% data variables.product.prodname_vscode %}](https://code.visualstudio.com/), to make changes to your project, then use {% data variables.product.prodname_desktop %} to visualize useful commits.'
|
||||
redirect_from:
|
||||
- /desktop/contributing-to-projects/making-changes-in-a-branch
|
||||
versions:
|
||||
@@ -12,11 +12,5 @@ children:
|
||||
- /viewing-the-branch-history
|
||||
- /pushing-changes-to-github
|
||||
shortTitle: Make changes in a branch
|
||||
ms.openlocfilehash: 3ff1729cdf050f3604c383d965dda117b5a18e42
|
||||
ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: es-ES
|
||||
ms.lasthandoff: 09/11/2022
|
||||
ms.locfileid: '145092312'
|
||||
---
|
||||
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Administrar las llaves de despliegue
|
||||
intro: Aprende las diversas formas de administrar llaves SSH en tus servidores cuando automatizas los scripts de desplegue y averigua qué es lo mejor para ti.
|
||||
title: Managing deploy keys
|
||||
intro: Learn different ways to manage SSH keys on your servers when you automate deployment scripts and which way is best for you.
|
||||
redirect_from:
|
||||
- /guides/managing-deploy-keys
|
||||
- /v3/guides/managing-deploy-keys
|
||||
@@ -14,91 +14,90 @@ versions:
|
||||
ghec: '*'
|
||||
topics:
|
||||
- API
|
||||
ms.openlocfilehash: 425535eb582c84801d79f00df751bb48d4a5b05e
|
||||
ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: es-ES
|
||||
ms.lasthandoff: 09/05/2022
|
||||
ms.locfileid: '146058472'
|
||||
---
|
||||
Puedes administrar llaves SSH en tus servidores cuando automatices tus scripts de despliegue utilizando el reenvío del agente de SSH, HTTPS con tokens de OAuth, o usuarios máquina.
|
||||
|
||||
## Reenvío del agente SSH
|
||||
|
||||
En muchos casos, especialmente al inicio de un proyecto, el reenvío del agente SSH es el método más fácil y rápido a utilizar. El reenvío de agentes utiliza las mismas llaves SSH que utiliza tu ordenador de desarrollo local.
|
||||
You can manage SSH keys on your servers when automating deployment scripts using SSH agent forwarding, HTTPS with OAuth tokens, deploy keys, or machine users.
|
||||
|
||||
#### Ventajas
|
||||
## SSH agent forwarding
|
||||
|
||||
* No tienes que generar o llevar registros de las llaves nuevas.
|
||||
* No hay administración de llaves; los usuarios tienen los mismos permisos en el servidor y localmente.
|
||||
* No se almacenan las llaves en el servidor, así que, en caso de que el servidor se ponga en riesgo, no necesitas buscar y eliminar las llaves con este problema.
|
||||
In many cases, especially in the beginning of a project, SSH agent forwarding is the quickest and simplest method to use. Agent forwarding uses the same SSH keys that your local development computer uses.
|
||||
|
||||
#### Desventajas
|
||||
#### Pros
|
||||
|
||||
* Los usuarios **deben** utilizar SSH para la implementación; no se pueden usar procesos de implementación automatizados.
|
||||
* El reenvío del agente SSH puede ser difícil de ejecutar para usuarios de Windows.
|
||||
* You do not have to generate or keep track of any new keys.
|
||||
* There is no key management; users have the same permissions on the server that they do locally.
|
||||
* No keys are stored on the server, so in case the server is compromised, you don't need to hunt down and remove the compromised keys.
|
||||
|
||||
#### Configurar
|
||||
#### Cons
|
||||
|
||||
1. Habilita el reenvío de agente localmente. Vea [nuestra guía sobre el reenvío de agentes SSH][ssh-agent-forwarding] para más información.
|
||||
2. Configura tus scripts de despliegue para utilizar el reenvío de agente. Por ejemplo, en un script de Bash, la habilitación del reenvío de agentes tendría un aspecto similar al siguiente: `ssh -A serverA 'bash -s' < deploy.sh`
|
||||
* Users **must** SSH in to deploy; automated deploy processes can't be used.
|
||||
* SSH agent forwarding can be troublesome to run for Windows users.
|
||||
|
||||
## Clonado de HTTPS con tokens de OAuth
|
||||
#### Setup
|
||||
|
||||
Si no quieres utilizar llaves SSH, puedes utilizar HTTPS con tokens de OAuth.
|
||||
1. Turn on agent forwarding locally. See [our guide on SSH agent forwarding][ssh-agent-forwarding] for more information.
|
||||
2. Set your deploy scripts to use agent forwarding. For example, on a bash script, enabling agent forwarding would look something like this:
|
||||
`ssh -A serverA 'bash -s' < deploy.sh`
|
||||
|
||||
#### Ventajas
|
||||
## HTTPS cloning with OAuth tokens
|
||||
|
||||
* Cualquiera que tenga acceso al servidor puede desplegar el repositorio.
|
||||
* Los usuarios no tienen que implementar la configuración local de SSH.
|
||||
* No se necesitan tokens múltiples (uno por usuario); un token por servidor es suficiente.
|
||||
* Los tokens se pueden revocar en cualquier momento, convirtiéndolos esencialmente en una contraseña de un solo uso.
|
||||
If you don't want to use SSH keys, you can use HTTPS with OAuth tokens.
|
||||
|
||||
#### Pros
|
||||
|
||||
* Anyone with access to the server can deploy the repository.
|
||||
* Users don't have to change their local SSH settings.
|
||||
* Multiple tokens (one for each user) are not needed; one token per server is enough.
|
||||
* A token can be revoked at any time, turning it essentially into a one-use password.
|
||||
{% ifversion ghes %}
|
||||
* La generación de nuevos tokens se puede incluir fácilmente en un script mediante [la API de OAuth](/rest/reference/oauth-authorizations#create-a-new-authorization).
|
||||
* Generating new tokens can be easily scripted using [the OAuth API](/rest/reference/oauth-authorizations#create-a-new-authorization).
|
||||
{% endif %}
|
||||
|
||||
#### Desventajas
|
||||
#### Cons
|
||||
|
||||
* Debes asegurarte de que configuras tu token con los alcances de acceso correctos.
|
||||
* Los tokens son prácticamente contraseñas, y deben protegerse de la misma manera.
|
||||
* You must make sure that you configure your token with the correct access scopes.
|
||||
* Tokens are essentially passwords, and must be protected the same way.
|
||||
|
||||
#### Configurar
|
||||
#### Setup
|
||||
|
||||
Vea [nuestra guía sobre cómo crear un token de acceso personal](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token).
|
||||
See [our guide on creating a personal access token](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token).
|
||||
|
||||
## Claves de implementación
|
||||
## Deploy keys
|
||||
|
||||
{% data reusables.repositories.deploy-keys %}
|
||||
|
||||
{% data reusables.repositories.deploy-keys-write-access %}
|
||||
|
||||
#### Ventajas
|
||||
#### Pros
|
||||
|
||||
* Cualquiera que tenga acceso al repositorio y al servidor tiene la capacidad de desplegar el proyecto.
|
||||
* Los usuarios no tienen que implementar la configuración local de SSH.
|
||||
* Las claves de implementación son de solo lectura de forma predeterminada, pero puede darles acceso de escritura al agregarlas a un repositorio.
|
||||
* Anyone with access to the repository and server has the ability to deploy the project.
|
||||
* Users don't have to change their local SSH settings.
|
||||
* Deploy keys are read-only by default, but you can give them write access when adding them to a repository.
|
||||
|
||||
#### Desventajas
|
||||
#### Cons
|
||||
|
||||
* Las llaves de despliegue solo otorgan acceso a un solo repositorio. Los proyectos más complejos pueden tener muchos repositorios que extraer del mismo servidor.
|
||||
* Las llaves de lanzamiento habitualmente no están protegidas con una frase de acceso, lo cual hace que se pueda acceder fácilmente a ellas si el servidor estuvo en riesgo.
|
||||
* Deploy keys only grant access to a single repository. More complex projects may have many repositories to pull to the same server.
|
||||
* Deploy keys are usually not protected by a passphrase, making the key easily accessible if the server is compromised.
|
||||
|
||||
#### Configurar
|
||||
#### Setup
|
||||
|
||||
1. [Ejecuta el procedimiento`ssh-keygen` ][generating-ssh-keys] en el servidor y recuerda dónde guardas el par de claves RSA públicas y privadas generado.
|
||||
2. En la esquina superior derecha de cualquier página de {% data variables.product.product_name %}, haga clic en la fotografía de perfil y luego en **Your profile**. 
|
||||
3. En la página del perfil, haga clic en **Repositories** y después en el nombre del repositorio. 
|
||||
4. Desde el repositorio, haga clic en **Settings**. 
|
||||
5. En la barra lateral, haga clic en **Deploy Keys** y después en **Add deploy key**. 
|
||||
6. Proporciona un título, pégalo en tu llave pública. 
|
||||
7. Seleccione **Allow write access** si quiere que esta clave tenga acceso de escritura en el repositorio. Una llave de despliegue con acceso de escritura permite que un despliegue cargue información al repositorio.
|
||||
8. Haga clic en **Add key**.
|
||||
1. [Run the `ssh-keygen` procedure][generating-ssh-keys] on your server, and remember where you save the generated public and private rsa key pair.
|
||||
{% data reusables.profile.navigating-to-profile %}
|
||||
|
||||
#### Utilizar repositorios múltiples en un servidor
|
||||
|
||||
1. On your profile page, click **Repositories**, then click the name of your repository. 
|
||||
2. From your repository, click **Settings**. 
|
||||
3. In the sidebar, click **Deploy Keys**, then click **Add deploy key**. 
|
||||
4. Provide a title, paste in your public key. 
|
||||
5. Select **Allow write access** if you want this key to have write access to the repository. A deploy key with write access lets a deployment push to the repository.
|
||||
6. Click **Add key**.
|
||||
|
||||
Si utilizas repositorios múltiples en un servidor, necesitarás generar un par de llaves dedicados para cada uno. No puedes reutilizar una llave de despliegue para repositorios múltiples.
|
||||
#### Using multiple repositories on one server
|
||||
|
||||
En el archivo de configuración SSH del servidor (habitualmente `~/.ssh/config`), agregue una entrada de alias para cada repositorio. Por ejemplo:
|
||||
If you use multiple repositories on one server, you will need to generate a dedicated key pair for each one. You can't reuse a deploy key for multiple repositories.
|
||||
|
||||
In the server's SSH configuration file (usually `~/.ssh/config`), add an alias entry for each repository. For example:
|
||||
|
||||
```bash
|
||||
Host {% ifversion fpt or ghec %}github.com{% else %}my-GHE-hostname.com{% endif %}-repo-0
|
||||
@@ -110,79 +109,79 @@ Host {% ifversion fpt or ghec %}github.com{% else %}my-GHE-hostname.com{% endif
|
||||
IdentityFile=/home/user/.ssh/repo-1_deploy_key
|
||||
```
|
||||
|
||||
* `Host {% ifversion fpt or ghec %}github.com{% else %}my-GHE-hostname.com{% endif %}-repo-0`: alias del repositorio.
|
||||
* `Hostname {% ifversion fpt or ghec %}github.com{% else %}my-GHE-hostname.com{% endif %}`: configura el nombre de host que se va a usar con el alias.
|
||||
* `IdentityFile=/home/user/.ssh/repo-0_deploy_key`: asigna una clave privada al alias.
|
||||
* `Host {% ifversion fpt or ghec %}github.com{% else %}my-GHE-hostname.com{% endif %}-repo-0` - The repository's alias.
|
||||
* `Hostname {% ifversion fpt or ghec %}github.com{% else %}my-GHE-hostname.com{% endif %}` - Configures the hostname to use with the alias.
|
||||
* `IdentityFile=/home/user/.ssh/repo-0_deploy_key` - Assigns a private key to the alias.
|
||||
|
||||
Entonces podrás utilizar el alias del nombre de host para que interactúe con el repositorio utilizando SSH, lo cual utilizará la llave de despliegue única que se asignó a dicho alias. Por ejemplo:
|
||||
You can then use the hostname's alias to interact with the repository using SSH, which will use the unique deploy key assigned to that alias. For example:
|
||||
|
||||
```bash
|
||||
$ git clone git@{% ifversion fpt or ghec %}github.com{% else %}my-GHE-hostname.com{% endif %}-repo-1:OWNER/repo-1.git
|
||||
```
|
||||
|
||||
## Tokens de servidor a servidor
|
||||
## Server-to-server tokens
|
||||
|
||||
Si el servidor tiene que acceder a repositorios en una o más organizaciones, puede usar una aplicación de GitHub para definir el acceso necesario y, luego, generar tokens de _ámbito limitado_ y de _servidor a servidor_ desde esa aplicación de GitHub. Se puede ajustar el alcance de los tokens de servidor a servidor para repositorios múltiples y pueden tener permisos específicos. Por ejemplo, puedes generar un token con acceso de solo lectura al contenido de un repositorio.
|
||||
If your server needs to access repositories across one or more organizations, you can use a GitHub App to define the access you need, and then generate _tightly-scoped_, _server-to-server_ tokens from that GitHub App. The server-to-server tokens can be scoped to single or multiple repositories, and can have fine-grained permissions. For example, you can generate a token with read-only access to a repository's contents.
|
||||
|
||||
Ya que las GitHub Apps son un actor de primera clase en {% data variables.product.product_name %}, los tokens de servidor a servidor se desacoplan de cualquier usuario de GitHub, lo cual los hace comparables con los "tokens de servicio". Adicionalmente, los tokens de servidor a servidor. tienen límites de tasa dedicados que se escalan de acuerdo con el tamaño de las organizaciones sobre las cuales actúan. Para más información, vea [Límites de frecuencia para {% data variables.product.prodname_github_apps %}](/developers/apps/rate-limits-for-github-apps).
|
||||
Since GitHub Apps are a first class actor on {% data variables.product.product_name %}, the server-to-server tokens are decoupled from any GitHub user, which makes them comparable to "service tokens". Additionally, server-to-server tokens have dedicated rate limits that scale with the size of the organizations that they act upon. For more information, see [Rate limits for {% data variables.product.prodname_github_apps %}](/developers/apps/rate-limits-for-github-apps).
|
||||
|
||||
#### Ventajas
|
||||
#### Pros
|
||||
|
||||
- Tokens de alcance muy específico con conjuntos de permisos bien definidos y tiempos de vencimiento (1 hora o menos si se revocan manualmente utilizando la API).
|
||||
- Límites de tasa dedicados que crecen con tu organización.
|
||||
- Desacoplados de las identidades de los usuariso de GitHub para que no consuman plazas de la licencia.
|
||||
- Nunca se les otorga una contraseña, así que no se puede iniciar sesión directamente en ellos.
|
||||
- Tightly-scoped tokens with well-defined permission sets and expiration times (1 hour, or less if revoked manually using the API).
|
||||
- Dedicated rate limits that grow with your organization.
|
||||
- Decoupled from GitHub user identities, so they do not consume any licensed seats.
|
||||
- Never granted a password, so cannot be directly signed in to.
|
||||
|
||||
#### Desventajas
|
||||
#### Cons
|
||||
|
||||
- Se necesita de una configuración adicional para crear la GitHub App.
|
||||
- Los tokens de servidor a servidor vencen después de 1 hora, entonces necesitan volver a generarse habitualmente cuando se necesite, utilizando código.
|
||||
- Additional setup is needed to create the GitHub App.
|
||||
- Server-to-server tokens expire after 1 hour, and so need to be re-generated, typically on-demand using code.
|
||||
|
||||
#### Configurar
|
||||
#### Setup
|
||||
|
||||
1. Determina si tu GitHub App debería ser pública o privada. Si tu GitHub App solo actúa en los repositorios dentro de tu organización, probablemente la quieras como privada.
|
||||
1. Determina los permisos que necesita tu GitHub App, tales como el acceso de solo lectura al contenido del repositorio.
|
||||
1. Crea tu GitHub App a través de la página de configuración de tu organización. Para más información, vea [Creación de una aplicación de GitHub](/developers/apps/creating-a-github-app).
|
||||
1. Anote la aplicación de GitHub `id`.
|
||||
1. Genera y descarga la llave privada de tu GitHub App y almacénala de forma segura. Para más información, vea [Generación de una clave privada](/developers/apps/authenticating-with-github-apps#generating-a-private-key).
|
||||
1. Instala tu GitHub App en los repositorios sobre los que necesita actuar, opcionalmente, puedes instalarla en todos los repositorios de tu organización.
|
||||
1. Identifica el valor `installation_id` que representa la conexión entre la aplicación de GitHub y los repositorios de la organización a los que puede acceder. Cada par de aplicación de GitHub y organización tiene como máximo un único valor `installation_id`. Puede identificar este valor `installation_id` mediante la [Obtención de una instalación de la organización para la aplicación autenticada](/rest/reference/apps#get-an-organization-installation-for-the-authenticated-app). Para esto es necesario autenticase como una aplicación de GitHub mediante un JWT. Para más información, vea [Autenticación como una aplicación de GitHub](/developers/apps/authenticating-with-github-apps#authenticating-as-a-github-app).
|
||||
1. Genere un token de servidor a servidor mediante el punto de conexión de la API REST correspondiente, [Crear un token de acceso de instalación para una aplicación](/rest/reference/apps#create-an-installation-access-token-for-an-app). Para esto es necesario autenticase como una aplicación de GitHub mediante un JWT. Para más información, vea [Autenticación como una aplicación de GitHub](/developers/apps/authenticating-with-github-apps#authenticating-as-a-github-app) y [Autenticación como una instalación](/developers/apps/authenticating-with-github-apps#authenticating-as-an-installation).
|
||||
1. Esto requiere que un token de servidor a servidor interactúe con tus repositorios, ya sea a través de la API de REST o de GraphQL, o mediante el cliente de Git.
|
||||
1. Determine if your GitHub App should be public or private. If your GitHub App will only act on repositories within your organization, you likely want it private.
|
||||
1. Determine the permissions your GitHub App requires, such as read-only access to repository contents.
|
||||
1. Create your GitHub App via your organization's settings page. For more information, see [Creating a GitHub App](/developers/apps/creating-a-github-app).
|
||||
1. Note your GitHub App `id`.
|
||||
1. Generate and download your GitHub App's private key, and store this safely. For more information, see [Generating a private key](/developers/apps/authenticating-with-github-apps#generating-a-private-key).
|
||||
1. Install your GitHub App on the repositories it needs to act upon, optionally you may install the GitHub App on all repositories in your organization.
|
||||
1. Identify the `installation_id` that represents the connection between your GitHub App and the organization repositories it can access. Each GitHub App and organization pair have at most a single `installation_id`. You can identify this `installation_id` via [Get an organization installation for the authenticated app](/rest/reference/apps#get-an-organization-installation-for-the-authenticated-app). This requires authenticating as a GitHub App using a JWT, for more information see [Authenticating as a GitHub App](/developers/apps/authenticating-with-github-apps#authenticating-as-a-github-app).
|
||||
1. Generate a server-to-server token using the corresponding REST API endpoint, [Create an installation access token for an app](/rest/reference/apps#create-an-installation-access-token-for-an-app). This requires authenticating as a GitHub App using a JWT, for more information see [Authenticating as a GitHub App](/developers/apps/authenticating-with-github-apps#authenticating-as-a-github-app), and [Authenticating as an installation](/developers/apps/authenticating-with-github-apps#authenticating-as-an-installation).
|
||||
1. Use this server-to-server token to interact with your repositories, either via the REST or GraphQL APIs, or via a Git client.
|
||||
|
||||
## Usuarios máquina
|
||||
## Machine users
|
||||
|
||||
Si tu servidor necesita acceso a varios repositorios, puedes crear una cuenta nueva en {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} y adjuntar la llave SSH que se utilizará exclusivamente para la automatización. Ya que ningún humano usará esta cuenta en {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}, se denomina _usuario de máquina_. Puede agregar el usuario de máquina como [colaborador][collaborator] en un repositorio personal (y conceder acceso de lectura y escritura), como [colaborador externo][outside-collaborator] en un repositorio de la organización (y conceder acceso de lectura, escritura o administrador), o bien a un [equipo][team] con acceso a los repositorios que necesita automatizar (y conceder los permisos del equipo).
|
||||
If your server needs to access multiple repositories, you can create a new account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} and attach an SSH key that will be used exclusively for automation. Since this account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} won't be used by a human, it's called a _machine user_. You can add the machine user as a [collaborator][collaborator] on a personal repository (granting read and write access), as an [outside collaborator][outside-collaborator] on an organization repository (granting read, write, or admin access), or to a [team][team] with access to the repositories it needs to automate (granting the permissions of the team).
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
|
||||
{% tip %}
|
||||
|
||||
**Sugerencia:** Nuestros [términos del servicio][tos] establecen que:
|
||||
**Tip:** Our [terms of service][tos] state:
|
||||
|
||||
> *No se permiten cuentas registradas mediante "bots", ni otros métodos automatizados.*
|
||||
> *Accounts registered by "bots" or other automated methods are not permitted.*
|
||||
|
||||
Esto significa que no puedes automatizar la creación de las cuentas. Pero si quieres crear un solo usuario máquina para automatizar las tareas como el despliegue de scripts en tu proyecto u organización, eso está perfecto.
|
||||
This means that you cannot automate the creation of accounts. But if you want to create a single machine user for automating tasks such as deploy scripts in your project or organization, that is totally cool.
|
||||
|
||||
{% endtip %}
|
||||
|
||||
{% endif %}
|
||||
|
||||
#### Ventajas
|
||||
#### Pros
|
||||
|
||||
* Cualquiera que tenga acceso al repositorio y al servidor tiene la capacidad de desplegar el proyecto.
|
||||
* No se necesitan usuarios (humanos) para cambiar su configuración local de SSH.
|
||||
* No se necesitan llaves múltiples; una por servidor está bien.
|
||||
* Anyone with access to the repository and server has the ability to deploy the project.
|
||||
* No (human) users need to change their local SSH settings.
|
||||
* Multiple keys are not needed; one per server is adequate.
|
||||
|
||||
#### Desventajas
|
||||
#### Cons
|
||||
|
||||
* Únicamente las organizaciones pueden restringir a los usuarios máquina para que tengan acceso de solo lectura. Los repositorios personales siempre otorgan a los colaboradores acceso de lectura/escritura.
|
||||
* Las llaves de los usuarios máquina, tal como las llaves de despliegue, a menudo no se encuentran protegidas con una frase de acceso.
|
||||
* Only organizations can restrict machine users to read-only access. Personal repositories always grant collaborators read/write access.
|
||||
* Machine user keys, like deploy keys, are usually not protected by a passphrase.
|
||||
|
||||
#### Configurar
|
||||
#### Setup
|
||||
|
||||
1. [Ejecute el procedimiento `ssh-keygen`][generating-ssh-keys] en el servidor y adjunte la clave pública a la cuenta de usuario de máquina.
|
||||
2. Otorga a la cuenta del usuario máquina el acceso a los repositorios que quieras automatizar. Para ello, agregue la cuenta como [colaborador][collaborator], como [colaborador externo][outside-collaborator] o a un [equipo][team] de una organización.
|
||||
1. [Run the `ssh-keygen` procedure][generating-ssh-keys] on your server and attach the public key to the machine user account.
|
||||
2. Give the machine user account access to the repositories you want to automate. You can do this by adding the account as a [collaborator][collaborator], as an [outside collaborator][outside-collaborator], or to a [team][team] in an organization.
|
||||
|
||||
[ssh-agent-forwarding]: /guides/using-ssh-agent-forwarding/
|
||||
[generating-ssh-keys]: /articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent/#generating-a-new-ssh-key
|
||||
@@ -192,5 +191,5 @@ Esto significa que no puedes automatizar la creación de las cuentas. Pero si qu
|
||||
[outside-collaborator]: /articles/adding-outside-collaborators-to-repositories-in-your-organization
|
||||
[team]: /articles/adding-organization-members-to-a-team
|
||||
|
||||
## Información adicional
|
||||
- [Configuración de notificaciones](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications#organization-alerts-notification-options)
|
||||
## Further reading
|
||||
- [Configuring notifications](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications#organization-alerts-notification-options)
|
||||
|
||||
@@ -106,7 +106,7 @@ Activity related to a branch protection rule. For more information, see "[About
|
||||
|
||||
- Repository webhooks
|
||||
- Organization webhooks
|
||||
- {% data variables.product.prodname_github_apps %} with at least `read-only` access on repositories administration
|
||||
- {% data variables.product.prodname_github_apps %} with **Administration** repository permission
|
||||
|
||||
### Webhook payload object
|
||||
|
||||
@@ -161,7 +161,7 @@ Key | Type | Description
|
||||
|
||||
- Repository webhooks only receive payloads for the `created` and `completed` event types in a repository
|
||||
- Organization webhooks only receive payloads for the `created` and `completed` event types in repositories
|
||||
- {% data variables.product.prodname_github_apps %} with the `checks:read` permission receive payloads for the `created` and `completed` events that occur in the repository where the app is installed. The app must have the `checks:write` permission to receive the `rerequested` and `requested_action` event types. The `rerequested` and `requested_action` event type payloads are only sent to the {% data variables.product.prodname_github_app %} being requested. {% data variables.product.prodname_github_apps %} with the `checks:write` are automatically subscribed to this webhook event.
|
||||
- {% data variables.product.prodname_github_apps %} with **Checks** read permission receive payloads for the `created` and `completed` events that occur in the repository where the app is installed. The app must have **Checks** write permission to receive the `rerequested` and `requested_action` event types. The `rerequested` and `requested_action` event type payloads are only sent to the {% data variables.product.prodname_github_app %} being requested. {% data variables.product.prodname_github_apps %} with **Checks** write permission are automatically subscribed to this webhook event.
|
||||
|
||||
### Webhook payload object
|
||||
|
||||
@@ -185,7 +185,7 @@ Key | Type | Description
|
||||
|
||||
- Repository webhooks only receive payloads for the `completed` event types in a repository
|
||||
- Organization webhooks only receive payloads for the `completed` event types in repositories
|
||||
- {% data variables.product.prodname_github_apps %} with the `checks:read` permission receive payloads for the `created` and `completed` events that occur in the repository where the app is installed. The app must have the `checks:write` permission to receive the `requested` and `rerequested` event types. The `requested` and `rerequested` event type payloads are only sent to the {% data variables.product.prodname_github_app %} being requested. {% data variables.product.prodname_github_apps %} with the `checks:write` are automatically subscribed to this webhook event.
|
||||
- {% data variables.product.prodname_github_apps %} with **Checks** read permission receive payloads for the `created` and `completed` events that occur in the repository where the app is installed. The app must have **Checks** write permission to receive the `requested` and `rerequested` event types. The `requested` and `rerequested` event type payloads are only sent to the {% data variables.product.prodname_github_app %} being requested. {% data variables.product.prodname_github_apps %} with **Checks** write permission are automatically subscribed to this webhook event.
|
||||
|
||||
### Webhook payload object
|
||||
|
||||
@@ -207,7 +207,7 @@ Key | Type | Description
|
||||
|
||||
- Repository webhooks
|
||||
- Organization webhooks
|
||||
- {% data variables.product.prodname_github_apps %} with the `security_events :read` permission
|
||||
- {% data variables.product.prodname_github_apps %} with **Code scanning alerts** permission
|
||||
|
||||
### Webhook payload object
|
||||
|
||||
@@ -229,7 +229,7 @@ Key | Type | Description
|
||||
|
||||
- Repository webhooks
|
||||
- Organization webhooks
|
||||
- {% data variables.product.prodname_github_apps %} with the `contents` permission
|
||||
- {% data variables.product.prodname_github_apps %} with **Contents** permission
|
||||
|
||||
### Webhook payload object
|
||||
|
||||
@@ -273,7 +273,7 @@ Webhook events are triggered based on the specificity of the domain you register
|
||||
|
||||
- Repository webhooks
|
||||
- Organization webhooks
|
||||
- {% data variables.product.prodname_github_apps %} with the `contents` permission
|
||||
- {% data variables.product.prodname_github_apps %} with **Contents** permission
|
||||
|
||||
### Webhook payload object
|
||||
|
||||
@@ -302,7 +302,7 @@ Webhook events are triggered based on the specificity of the domain you register
|
||||
|
||||
- Repository webhooks
|
||||
- Organization webhooks
|
||||
- {% data variables.product.prodname_github_apps %} with the `contents` permission
|
||||
- {% data variables.product.prodname_github_apps %} with **Contents** permission
|
||||
|
||||
### Webhook payload object
|
||||
|
||||
@@ -345,7 +345,7 @@ Webhook events are triggered based on the specificity of the domain you register
|
||||
|
||||
- Repository webhooks
|
||||
- Organization webhooks
|
||||
- {% data variables.product.prodname_github_apps %} with the `deployments` permission
|
||||
- {% data variables.product.prodname_github_apps %} with **Deployments** permission
|
||||
|
||||
### Webhook payload object
|
||||
|
||||
@@ -370,7 +370,7 @@ Key | Type | Description
|
||||
|
||||
- Repository webhooks
|
||||
- Organization webhooks
|
||||
- {% data variables.product.prodname_github_apps %} with the `deployments` permission
|
||||
- {% data variables.product.prodname_github_apps %} with **Deployments** permission
|
||||
|
||||
### Webhook payload object
|
||||
|
||||
@@ -401,7 +401,7 @@ Activity related to a discussion. For more information, see the "[Using the Grap
|
||||
|
||||
- Repository webhooks
|
||||
- Organization webhooks
|
||||
- {% data variables.product.prodname_github_apps %} with the `discussions` permission
|
||||
- {% data variables.product.prodname_github_apps %} with **Discussions** permission
|
||||
|
||||
### Webhook payload object
|
||||
|
||||
@@ -427,7 +427,7 @@ Activity related to a comment in a discussion. For more information, see "[Using
|
||||
|
||||
- Repository webhooks
|
||||
- Organization webhooks
|
||||
- {% data variables.product.prodname_github_apps %} with the `discussions` permission
|
||||
- {% data variables.product.prodname_github_apps %} with **Discussions** permission
|
||||
|
||||
### Webhook payload object
|
||||
|
||||
@@ -475,7 +475,7 @@ Key | Type | Description
|
||||
|
||||
- Repository webhooks
|
||||
- Organization webhooks
|
||||
- {% data variables.product.prodname_github_apps %} with the `contents` permission
|
||||
- {% data variables.product.prodname_github_apps %} with **Contents** permission
|
||||
|
||||
### Webhook payload object
|
||||
|
||||
@@ -518,7 +518,7 @@ Key | Type | Description
|
||||
|
||||
- Repository webhooks
|
||||
- Organization webhooks
|
||||
- {% data variables.product.prodname_github_apps %} with the `contents` permission
|
||||
- {% data variables.product.prodname_github_apps %} with **Contents** permission
|
||||
|
||||
### Webhook payload object
|
||||
|
||||
@@ -576,7 +576,7 @@ Key | Type | Description
|
||||
|
||||
- Repository webhooks
|
||||
- Organization webhooks
|
||||
- {% data variables.product.prodname_github_apps %} with the `issues` permission
|
||||
- {% data variables.product.prodname_github_apps %} with **Issues** permission
|
||||
|
||||
### Webhook payload object
|
||||
|
||||
@@ -599,7 +599,7 @@ Key | Type | Description
|
||||
|
||||
- Repository webhooks
|
||||
- Organization webhooks
|
||||
- {% data variables.product.prodname_github_apps %} with the `issues` permission
|
||||
- {% data variables.product.prodname_github_apps %} with **Issues** permission
|
||||
|
||||
### Webhook payload object
|
||||
|
||||
@@ -622,7 +622,7 @@ Key | Type | Description
|
||||
|
||||
- Repository webhooks
|
||||
- Organization webhooks
|
||||
- {% data variables.product.prodname_github_apps %} with the `metadata` permission
|
||||
- {% data variables.product.prodname_github_apps %} with **Metadata** permission
|
||||
|
||||
### Webhook payload object
|
||||
|
||||
@@ -673,7 +673,7 @@ For a detailed description of this payload and the payload for each type of `act
|
||||
|
||||
- Repository webhooks
|
||||
- Organization webhooks
|
||||
- {% data variables.product.prodname_github_apps %} with the `members` permission
|
||||
- {% data variables.product.prodname_github_apps %} with **Members** permission
|
||||
|
||||
### Webhook payload object
|
||||
|
||||
@@ -695,7 +695,7 @@ For a detailed description of this payload and the payload for each type of `act
|
||||
### Availability
|
||||
|
||||
- Organization webhooks
|
||||
- {% data variables.product.prodname_github_apps %} with the `members` permission
|
||||
- {% data variables.product.prodname_github_apps %} with **Members** permission
|
||||
|
||||
### Webhook payload object
|
||||
|
||||
@@ -721,7 +721,7 @@ Activity related to merge groups in a merge queue. The type of activity is speci
|
||||
|
||||
- Repository webhooks
|
||||
- Organization webhooks
|
||||
- {% data variables.product.prodname_github_apps %} with the `merge_queues` permission
|
||||
- {% data variables.product.prodname_github_apps %} with **Merge queues** permission
|
||||
|
||||
### Webhook payload object
|
||||
|
||||
@@ -775,7 +775,7 @@ Key | Type | Description
|
||||
|
||||
- Repository webhooks
|
||||
- Organization webhooks
|
||||
- {% data variables.product.prodname_github_apps %} with the `pull_requests` permission
|
||||
- {% data variables.product.prodname_github_apps %} with **Pull requests** permission
|
||||
|
||||
### Webhook payload object
|
||||
|
||||
@@ -798,7 +798,7 @@ Key | Type | Description
|
||||
{% ifversion ghes or ghae %}
|
||||
- GitHub Enterprise webhooks only receive `created` and `deleted` events. For more information, "[Global webhooks](/rest/reference/enterprise-admin#global-webhooks/).{% endif %}
|
||||
- Organization webhooks only receive the `deleted`, `added`, `removed`, `renamed`, and `invited` events
|
||||
- {% data variables.product.prodname_github_apps %} with the `members` permission
|
||||
- {% data variables.product.prodname_github_apps %} with **Members** permission
|
||||
|
||||
### Webhook payload object
|
||||
|
||||
@@ -824,7 +824,7 @@ Key | Type | Description
|
||||
### Availability
|
||||
|
||||
- Organization webhooks
|
||||
- {% data variables.product.prodname_github_apps %} with the `organization_administration` permission
|
||||
- {% data variables.product.prodname_github_apps %} with **Administration** organization permission
|
||||
|
||||
### Webhook payload object
|
||||
|
||||
@@ -870,7 +870,7 @@ Activity related to {% data variables.product.prodname_registry %}. {% data reus
|
||||
|
||||
- Repository webhooks
|
||||
- Organization webhooks
|
||||
- {% data variables.product.prodname_github_apps %} with the `pages` permission
|
||||
- {% data variables.product.prodname_github_apps %} with **Pages** permission
|
||||
|
||||
### Webhook payload object
|
||||
|
||||
@@ -921,7 +921,7 @@ Key | Type | Description
|
||||
|
||||
- Repository webhooks
|
||||
- Organization webhooks
|
||||
- {% data variables.product.prodname_github_apps %} with the `repository_projects` or `organization_projects` permission
|
||||
- {% data variables.product.prodname_github_apps %} with **Projects** repository or organization permission
|
||||
|
||||
{% ifversion projects-v2 %}
|
||||
{% note %}
|
||||
@@ -953,7 +953,7 @@ Key | Type | Description
|
||||
|
||||
- Repository webhooks
|
||||
- Organization webhooks
|
||||
- {% data variables.product.prodname_github_apps %} with the `repository_projects` or `organization_projects` permission
|
||||
- {% data variables.product.prodname_github_apps %} with **Projects** repository or organization permission
|
||||
|
||||
{% ifversion projects-v2 %}
|
||||
{% note %}
|
||||
@@ -983,7 +983,7 @@ Key | Type | Description
|
||||
|
||||
- Repository webhooks
|
||||
- Organization webhooks
|
||||
- {% data variables.product.prodname_github_apps %} with the `repository_projects` or `organization_projects` permission
|
||||
- {% data variables.product.prodname_github_apps %} with **Projects** repository or organization permission
|
||||
|
||||
{% ifversion projects-v2 %}
|
||||
{% note %}
|
||||
@@ -1020,7 +1020,7 @@ Activity related to items in a {% data variables.projects.project_v2 %}. {% data
|
||||
### Availability
|
||||
|
||||
- Organization webhooks
|
||||
- {% data variables.product.prodname_github_apps %} with the `organization_projects` permission
|
||||
- {% data variables.product.prodname_github_apps %} with **Projects** organization permission
|
||||
|
||||
### Webhook payload object
|
||||
|
||||
@@ -1046,7 +1046,7 @@ Key | Type | Description
|
||||
|
||||
- Repository webhooks
|
||||
- Organization webhooks
|
||||
- {% data variables.product.prodname_github_apps %} with the `metadata` permission
|
||||
- {% data variables.product.prodname_github_apps %} with **Metadata** permission
|
||||
|
||||
### Webhook payload object
|
||||
|
||||
@@ -1073,7 +1073,7 @@ Key | Type | Description
|
||||
|
||||
- Repository webhooks
|
||||
- Organization webhooks
|
||||
- {% data variables.product.prodname_github_apps %} with the `pull_requests` permission
|
||||
- {% data variables.product.prodname_github_apps %} with **Pull requests** permission
|
||||
|
||||
### Webhook payload object
|
||||
|
||||
@@ -1098,7 +1098,7 @@ Deliveries for `review_requested` and `review_request_removed` events will have
|
||||
|
||||
- Repository webhooks
|
||||
- Organization webhooks
|
||||
- {% data variables.product.prodname_github_apps %} with the `pull_requests` permission
|
||||
- {% data variables.product.prodname_github_apps %} with **Pull requests** permission
|
||||
|
||||
### Webhook payload object
|
||||
|
||||
@@ -1120,7 +1120,7 @@ Deliveries for `review_requested` and `review_request_removed` events will have
|
||||
|
||||
- Repository webhooks
|
||||
- Organization webhooks
|
||||
- {% data variables.product.prodname_github_apps %} with the `pull_requests` permission
|
||||
- {% data variables.product.prodname_github_apps %} with **Pull requests** permission
|
||||
|
||||
### Webhook payload object
|
||||
|
||||
@@ -1143,7 +1143,7 @@ Deliveries for `review_requested` and `review_request_removed` events will have
|
||||
|
||||
- Repository webhooks
|
||||
- Organization webhooks
|
||||
- {% data variables.product.prodname_github_apps %} with the `pull_requests` permission
|
||||
- {% data variables.product.prodname_github_apps %} with **Pull requests** permission
|
||||
|
||||
### Webhook payload object
|
||||
|
||||
@@ -1171,7 +1171,7 @@ Deliveries for `review_requested` and `review_request_removed` events will have
|
||||
|
||||
- Repository webhooks
|
||||
- Organization webhooks
|
||||
- {% data variables.product.prodname_github_apps %} with the `contents` permission
|
||||
- {% data variables.product.prodname_github_apps %} with **Contents** permission
|
||||
|
||||
### Webhook payload object
|
||||
|
||||
@@ -1215,7 +1215,7 @@ Key | Type | Description
|
||||
|
||||
- Repository webhooks
|
||||
- Organization webhooks
|
||||
- {% data variables.product.prodname_github_apps %} with the `contents` permission
|
||||
- {% data variables.product.prodname_github_apps %} with **Contents** permission
|
||||
|
||||
### Webhook payload object
|
||||
|
||||
@@ -1236,7 +1236,7 @@ This event occurs when a {% data variables.product.prodname_github_app %} sends
|
||||
|
||||
### Availability
|
||||
|
||||
- {% data variables.product.prodname_github_apps %} must have the `contents` permission to receive this webhook.
|
||||
- {% data variables.product.prodname_github_apps %} with **Contents** permission
|
||||
|
||||
### Webhook payload example
|
||||
|
||||
@@ -1250,7 +1250,7 @@ This event occurs when a {% data variables.product.prodname_github_app %} sends
|
||||
|
||||
- Repository webhooks receive all event types except `deleted`
|
||||
- Organization webhooks
|
||||
- {% data variables.product.prodname_github_apps %} with the `metadata` permission receive all event types except `deleted`
|
||||
- {% data variables.product.prodname_github_apps %} with **Metadata** permission receive all event types except `deleted`
|
||||
|
||||
### Webhook payload object
|
||||
|
||||
@@ -1319,7 +1319,7 @@ Key | Type | Description
|
||||
|
||||
- Repository webhooks
|
||||
- Organization webhooks
|
||||
- {% data variables.product.prodname_github_apps %} with the `secret_scanning_alerts:read` permission
|
||||
- {% data variables.product.prodname_github_apps %} with **Secret scanning alerts** permission
|
||||
|
||||
### Webhook payload object
|
||||
|
||||
@@ -1343,7 +1343,7 @@ Key | Type | Description
|
||||
|
||||
- Repository webhooks
|
||||
- Organization webhooks
|
||||
- {% data variables.product.prodname_github_apps %} with the `secret_scanning_alerts:read` permission
|
||||
- {% data variables.product.prodname_github_apps %} with **Secret scanning alerts** permission
|
||||
|
||||
### Webhook payload object
|
||||
|
||||
@@ -1366,7 +1366,7 @@ The security advisory dataset also powers the GitHub {% data variables.product.p
|
||||
|
||||
### Availability
|
||||
|
||||
- {% data variables.product.prodname_github_apps %} with the `security_events` permission
|
||||
- {% data variables.product.prodname_github_apps %}
|
||||
|
||||
### Webhook payload object
|
||||
|
||||
@@ -1391,7 +1391,7 @@ Activity related to enabling or disabling code security and analysis features fo
|
||||
|
||||
- Repository webhooks
|
||||
- Organization webhooks
|
||||
- {% data variables.product.prodname_github_apps %} with at least `read-only` access on repositories administration
|
||||
- {% data variables.product.prodname_github_apps %} with **Administration** repository permission
|
||||
|
||||
### Webhook payload object
|
||||
|
||||
@@ -1464,7 +1464,7 @@ You can only create a sponsorship webhook on {% data variables.product.prodname_
|
||||
|
||||
- Repository webhooks
|
||||
- Organization webhooks
|
||||
- {% data variables.product.prodname_github_apps %} with the `statuses` permission
|
||||
- {% data variables.product.prodname_github_apps %} with **Commit statuses** permission
|
||||
|
||||
### Webhook payload object
|
||||
|
||||
@@ -1492,7 +1492,7 @@ Key | Type | Description
|
||||
### Availability
|
||||
|
||||
- Organization webhooks
|
||||
- {% data variables.product.prodname_github_apps %} with the `members` permission
|
||||
- {% data variables.product.prodname_github_apps %} with **Members** permission
|
||||
|
||||
### Webhook payload object
|
||||
|
||||
@@ -1523,7 +1523,7 @@ Key | Type | Description
|
||||
|
||||
- Repository webhooks
|
||||
- Organization webhooks
|
||||
- {% data variables.product.prodname_github_apps %} with the `members` permission
|
||||
- {% data variables.product.prodname_github_apps %} with **Members** permission
|
||||
|
||||
### Webhook payload object
|
||||
|
||||
@@ -1564,7 +1564,7 @@ The event’s actor is the [user](/rest/reference/users) who starred a repositor
|
||||
|
||||
- Repository webhooks
|
||||
- Organization webhooks
|
||||
- {% data variables.product.prodname_github_apps %} with the `metadata` permission
|
||||
- {% data variables.product.prodname_github_apps %} with **Metadata** permission
|
||||
|
||||
### Webhook payload object
|
||||
|
||||
@@ -1585,7 +1585,7 @@ This event occurs when someone triggers a workflow run on GitHub or sends a `POS
|
||||
|
||||
### Availability
|
||||
|
||||
- {% data variables.product.prodname_github_apps %} must have the `contents` permission to receive this webhook.
|
||||
- {% data variables.product.prodname_github_apps %} with **Contents** permission
|
||||
|
||||
### Webhook payload object
|
||||
|
||||
@@ -1634,7 +1634,7 @@ When a {% data variables.product.prodname_actions %} workflow run is requested o
|
||||
|
||||
### Availability
|
||||
|
||||
- {% data variables.product.prodname_github_apps %} with the `actions` or `contents` permissions.
|
||||
- {% data variables.product.prodname_github_apps %} with **Actions** or **Contents** permissions
|
||||
|
||||
### Webhook payload object
|
||||
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Extensiones e integraciones de GitHub
|
||||
intro: 'Utiliza las extensiones {% data variables.product.product_name %} para trabajar sin inconvenientes en los repositorios {% data variables.product.product_name %} dentro de las aplicaciones de terceros.'
|
||||
title: GitHub extensions and integrations
|
||||
intro: 'Use {% data variables.product.product_name %} extensions to work seamlessly in {% data variables.product.product_name %} repositories within third-party applications.'
|
||||
redirect_from:
|
||||
- /articles/about-github-extensions-for-third-party-applications
|
||||
- /articles/github-extensions-and-integrations
|
||||
@@ -10,53 +10,43 @@ versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
shortTitle: Extensions & integrations
|
||||
ms.openlocfilehash: f33ce9b9ae55e523bedff1309f3f2f15202dcf82
|
||||
ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: es-ES
|
||||
ms.lasthandoff: 09/11/2022
|
||||
ms.locfileid: '147884217'
|
||||
---
|
||||
## Herramientas del editor
|
||||
## Editor tools
|
||||
|
||||
Puedes conectarte a los repositorios de {% data variables.product.product_name %} dentro de las herramientas de edición de terceros tales como Atom, Unity y {% data variables.product.prodname_vs %}.
|
||||
You can connect to {% data variables.product.product_name %} repositories within third-party editor tools such as Unity and {% data variables.product.prodname_vs %}.
|
||||
|
||||
### {% data variables.product.product_name %} para Atom
|
||||
### {% data variables.product.product_name %} for Unity
|
||||
|
||||
Con el {% data variables.product.product_name %} para la extensión de Atom, puedes confirmar, subir, extraer, resolver conflictos de fusión y mucho más desde el editor de Atom. Para más información, vea el [sitio oficial de {% data variables.product.product_name %} para Atom](https://github.atom.io/).
|
||||
|
||||
### {% data variables.product.product_name %} para Unity
|
||||
|
||||
Con el {% data variables.product.product_name %} para la extensión del editor de Unity, puedes desarrollar en Unity, la plataforma de código abierto de desarrollo de juegos, y ver tu trabajo en {% data variables.product.product_name %}. Para más información, vea el [sitio](https://unity.github.com/) oficial de la extensión del editor de Unity o la [documentación](https://github.com/github-for-unity/Unity/tree/master/docs).
|
||||
With the {% data variables.product.product_name %} for Unity editor extension, you can develop on Unity, the open source game development platform, and see your work on {% data variables.product.product_name %}. For more information, see the official Unity editor extension [site](https://unity.github.com/) or the [documentation](https://github.com/github-for-unity/Unity/tree/master/docs).
|
||||
|
||||
### {% data variables.product.product_name %} for {% data variables.product.prodname_vs %}
|
||||
|
||||
Con {% data variables.product.product_name %} para la extensión {% data variables.product.prodname_vs %}, puedes trabajar en repositorios de {% data variables.product.product_name %} sin salir de {% data variables.product.prodname_vs %}. Para obtener más información, consulta el [sitio](https://visualstudio.github.com/) oficial de la extensión de {% data variables.product.prodname_vs %} o la [documentación](https://github.com/github/VisualStudio/tree/master/docs).
|
||||
With the {% data variables.product.product_name %} for {% data variables.product.prodname_vs %} extension, you can work in {% data variables.product.product_name %} repositories without leaving {% data variables.product.prodname_vs %}. For more information, see the official {% data variables.product.prodname_vs %} extension [site](https://visualstudio.github.com/) or [documentation](https://github.com/github/VisualStudio/tree/master/docs).
|
||||
|
||||
### {% data variables.product.prodname_dotcom %} para {% data variables.product.prodname_vscode %}
|
||||
### {% data variables.product.prodname_dotcom %} for {% data variables.product.prodname_vscode %}
|
||||
|
||||
Con {% data variables.product.prodname_dotcom %} para la extensión {% data variables.product.prodname_vscode %}, puedes revisar y administrar solicitudes de incorporación de cambios de {% data variables.product.product_name %} en {% data variables.product.prodname_vscode_shortname %}. Para obtener más información, consulta el [sitio](https://vscode.github.com/) oficial de la extensión de {% data variables.product.prodname_vscode_shortname %} o la [documentación](https://github.com/Microsoft/vscode-pull-request-github).
|
||||
With the {% data variables.product.prodname_dotcom %} for {% data variables.product.prodname_vscode %} extension, you can review and manage {% data variables.product.product_name %} pull requests in {% data variables.product.prodname_vscode_shortname %}. For more information, see the official {% data variables.product.prodname_vscode_shortname %} extension [site](https://vscode.github.com/) or [documentation](https://github.com/Microsoft/vscode-pull-request-github).
|
||||
|
||||
## Herramientas de administración de proyectos
|
||||
## Project management tools
|
||||
|
||||
Puedes integrar tu cuenta organizacional o personal en {% data variables.product.product_location %} con herramientas de administración de proyectos de terceros, tales como Jira.
|
||||
You can integrate your personal or organization account on {% data variables.product.product_location %} with third-party project management tools, such as Jira.
|
||||
|
||||
### Integración de Jira Cloud y {% data variables.product.product_name %}.com
|
||||
### Jira Cloud and {% data variables.product.product_name %}.com integration
|
||||
|
||||
Puedes integrar Jira Cloud con tu cuenta personal o de organización para escanear confirmaciones y solicitudes de extracción, y crear los metadatos e hipervínculos correspondientes en cualquiera de las propuestas de Jira mencionadas. Para más información, visite la [aplicación de integración de Jira](https://github.com/marketplace/jira-software-github) en Marketplace.
|
||||
You can integrate Jira Cloud with your personal or organization account to scan commits and pull requests, creating relevant metadata and hyperlinks in any mentioned Jira issues. For more information, visit the [Jira integration app](https://github.com/marketplace/jira-software-github) in the marketplace.
|
||||
|
||||
## Herramientas de comunicación para equipos
|
||||
## Team communication tools
|
||||
|
||||
Puedes integrar tu cuenta organizacional o personal en {% data variables.product.product_location %} con herramientas de comunicación de equipos de terceros, tales como Slack o Microsoft Teams.
|
||||
You can integrate your personal or organization account on {% data variables.product.product_location %} with third-party team communication tools, such as Slack or Microsoft Teams.
|
||||
|
||||
### Integración con Slack y con {% data variables.product.product_name %}
|
||||
### Slack and {% data variables.product.product_name %} integration
|
||||
|
||||
La aplicación Slack + {% data variables.product.prodname_dotcom %} le permite suscribirse a repositorios u organizaciones, y obtener actualizaciones en tiempo real sobre incidencias, solicitudes de incorporación de cambios, confirmaciones, debates, versiones, revisiones de implementación y estados de implementación. También puede realizar actividades como abrir y cerrar incidencias, y puede ver referencias detalladas a incidencias y solicitudes de incorporación de cambios sin salir de Slack. La aplicación también le hará ping personalmente en Slack si le se menciona como parte de cualquier notificación de {% data variables.product.prodname_dotcom %} que reciba en canales o chats personales.
|
||||
The Slack + {% data variables.product.prodname_dotcom %} app lets you subscribe to your repositories or organizations and get realtime updates about issues, pull requests, commits, discussions, releases, deployment reviews and deployment statuses. You can also perform activities like opening and closing issues, and you can see detailed references to issues and pull requests without leaving Slack. The app will also ping you personally in Slack if you are mentioned as part of any {% data variables.product.prodname_dotcom %} notifications that you receive in your channels or personal chats.
|
||||
|
||||
La aplicación Slack + {% data variables.product.prodname_dotcom %} también es compatible con [Slack Enterprise Grid](https://slack.com/intl/en-in/help/articles/360000281563-Manage-apps-on-Enterprise-Grid). Para más información, visite la [aplicación Slack + {% data variables.product.prodname_dotcom %}](https://github.com/marketplace/slack-github) en Marketplace.
|
||||
The Slack + {% data variables.product.prodname_dotcom %} app is also compatible with [Slack Enterprise Grid](https://slack.com/intl/en-in/help/articles/360000281563-Manage-apps-on-Enterprise-Grid). For more information, visit the [Slack + {% data variables.product.prodname_dotcom %} app](https://github.com/marketplace/slack-github) in the marketplace.
|
||||
|
||||
### Microsoft Teams y su integración con {% data variables.product.product_name %}
|
||||
### Microsoft Teams and {% data variables.product.product_name %} integration
|
||||
|
||||
La aplicación {% data variables.product.prodname_dotcom %} para Teams le permite suscribirse a repositorios u organizaciones, y obtener actualizaciones en tiempo real sobre incidencias, solicitudes de incorporación de cambios, confirmaciones, debates, versiones, revisiones de implementación y estados de implementación. También puede realizar actividades como abrir y cerrar incidencias, comentar incidencias y solicitudes de incorporación de cambios, y puede ver referencias detalladas a incidencias y solicitudes de incorporación de cambios sin salir de Microsoft Teams. La aplicación también le hará ping personalmente en Teams si le se menciona como parte de cualquier notificación de {% data variables.product.prodname_dotcom %} que reciba en canales o chats personales.
|
||||
The {% data variables.product.prodname_dotcom %} for Teams app lets you subscribe to your repositories or organizations and get realtime updates about issues, pull requests, commits, discussions, releases, deployment reviews and deployment statuses. You can also perform activities like opening and closing issues, commenting on your issues and pull requests, and you can see detailed references to issues and pull requests without leaving Microsoft Teams. The app will also ping you personally in Teams if you are mentioned as part of any {% data variables.product.prodname_dotcom %} notifications that you receive in your channels or personal chats.
|
||||
|
||||
Para más información, visite la [aplicación {% data variables.product.prodname_dotcom %} para Teams](https://appsource.microsoft.com/en-us/product/office/WA200002077) en Microsoft AppSource.
|
||||
For more information, visit the [{% data variables.product.prodname_dotcom %} for Teams app](https://appsource.microsoft.com/en-us/product/office/WA200002077) in Microsoft AppSource.
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Asociar editores de texto con Git
|
||||
intro: Usar un editor de texto para abrir y editar tus archivos con Git.
|
||||
title: Associating text editors with Git
|
||||
intro: Use a text editor to open and edit your files with Git.
|
||||
redirect_from:
|
||||
- /textmate
|
||||
- /articles/using-textmate-as-your-default-editor
|
||||
@@ -15,48 +15,33 @@ versions:
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
shortTitle: Associate text editors
|
||||
ms.openlocfilehash: 0d02c32ff04d4a5a2a1003464175e866630603f4
|
||||
ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: es-ES
|
||||
ms.lasthandoff: 09/11/2022
|
||||
ms.locfileid: '145148763'
|
||||
---
|
||||
{% mac %}
|
||||
|
||||
## Usar Atom como editor
|
||||
## Using {% data variables.product.prodname_vscode %} as your editor
|
||||
|
||||
1. Instale [Atom](https://atom.io/). Para más información, vea "[Instalación de Atom](https://flight-manual.atom.io/getting-started/sections/installing-atom/)" en la documentación de Atom.
|
||||
1. Install [{% data variables.product.prodname_vscode %}](https://code.visualstudio.com/) ({% data variables.product.prodname_vscode_shortname %}). For more information, see "[Setting up {% data variables.product.prodname_vscode_shortname %}](https://code.visualstudio.com/Docs/setup/setup-overview)" in the {% data variables.product.prodname_vscode_shortname %} documentation.
|
||||
{% data reusables.command_line.open_the_multi_os_terminal %}
|
||||
3. Escriba el siguiente comando:
|
||||
```shell
|
||||
$ git config --global core.editor "atom --wait"
|
||||
```
|
||||
|
||||
## Uso de {% data variables.product.prodname_vscode %} como editor
|
||||
|
||||
1. Instala [{% data variables.product.prodname_vscode %}](https://code.visualstudio.com/) ({% data variables.product.prodname_vscode_shortname %}). Para obtener más información, consulta la documentación de {% data variables.product.prodname_vscode_shortname %}, la sección "[Configuración de {% data variables.product.prodname_vscode_shortname %}](https://code.visualstudio.com/Docs/setup/setup-overview)".
|
||||
{% data reusables.command_line.open_the_multi_os_terminal %}
|
||||
3. Escriba el siguiente comando:
|
||||
3. Type this command:
|
||||
```shell
|
||||
$ git config --global core.editor "code --wait"
|
||||
```
|
||||
|
||||
## Usar Sublime Text como editor
|
||||
## Using Sublime Text as your editor
|
||||
|
||||
1. Instale [Sublime Text](https://www.sublimetext.com/). Para obtener más información, vea "[Instalación](https://docs.sublimetext.io/guide/getting-started/installation.html)" en la documentación de Sublime Text.
|
||||
1. Install [Sublime Text](https://www.sublimetext.com/). For more information, see "[Installation](https://docs.sublimetext.io/guide/getting-started/installation.html)" in the Sublime Text documentation.
|
||||
{% data reusables.command_line.open_the_multi_os_terminal %}
|
||||
3. Escriba el siguiente comando:
|
||||
3. Type this command:
|
||||
```shell
|
||||
$ git config --global core.editor "subl -n -w"
|
||||
```
|
||||
|
||||
## Usar TextMate como editor
|
||||
## Using TextMate as your editor
|
||||
|
||||
1. Instale [TextMate](https://macromates.com/).
|
||||
2. Instale la utilidad de shell `mate` de TextMate. Para obtener más información, vea "[`mate` y `rmate`](https://macromates.com/blog/2011/mate-and-rmate/)" en la documentación de TextMate.
|
||||
1. Install [TextMate](https://macromates.com/).
|
||||
2. Install TextMate's `mate` shell utility. For more information, see "[`mate` and `rmate`](https://macromates.com/blog/2011/mate-and-rmate/)" in the TextMate documentation.
|
||||
{% data reusables.command_line.open_the_multi_os_terminal %}
|
||||
4. Escriba el siguiente comando:
|
||||
4. Type this command:
|
||||
```shell
|
||||
$ git config --global core.editor "mate -w"
|
||||
```
|
||||
@@ -64,38 +49,29 @@ ms.locfileid: '145148763'
|
||||
|
||||
{% windows %}
|
||||
|
||||
## Usar Atom como editor
|
||||
## Using {% data variables.product.prodname_vscode %} as your editor
|
||||
|
||||
1. Instale [Atom](https://atom.io/). Para más información, vea "[Instalación de Atom](https://flight-manual.atom.io/getting-started/sections/installing-atom/)" en la documentación de Atom.
|
||||
1. Install [{% data variables.product.prodname_vscode %}](https://code.visualstudio.com/) ({% data variables.product.prodname_vscode_shortname %}). For more information, see "[Setting up {% data variables.product.prodname_vscode_shortname %}](https://code.visualstudio.com/Docs/setup/setup-overview)" in the {% data variables.product.prodname_vscode_shortname %} documentation.
|
||||
{% data reusables.command_line.open_the_multi_os_terminal %}
|
||||
3. Escriba el siguiente comando:
|
||||
```shell
|
||||
$ git config --global core.editor "atom --wait"
|
||||
```
|
||||
|
||||
## Uso de {% data variables.product.prodname_vscode %} como editor
|
||||
|
||||
1. Instala [{% data variables.product.prodname_vscode %}](https://code.visualstudio.com/) ({% data variables.product.prodname_vscode_shortname %}). Para obtener más información, consulta la documentación de {% data variables.product.prodname_vscode_shortname %}, la sección "[Configuración de {% data variables.product.prodname_vscode_shortname %}](https://code.visualstudio.com/Docs/setup/setup-overview)".
|
||||
{% data reusables.command_line.open_the_multi_os_terminal %}
|
||||
3. Escriba el siguiente comando:
|
||||
3. Type this command:
|
||||
```shell
|
||||
$ git config --global core.editor "code --wait"
|
||||
```
|
||||
|
||||
## Usar Sublime Text como editor
|
||||
## Using Sublime Text as your editor
|
||||
|
||||
1. Instale [Sublime Text](https://www.sublimetext.com/). Para obtener más información, vea "[Instalación](https://docs.sublimetext.io/guide/getting-started/installation.html)" en la documentación de Sublime Text.
|
||||
1. Install [Sublime Text](https://www.sublimetext.com/). For more information, see "[Installation](https://docs.sublimetext.io/guide/getting-started/installation.html)" in the Sublime Text documentation.
|
||||
{% data reusables.command_line.open_the_multi_os_terminal %}
|
||||
3. Escriba el siguiente comando:
|
||||
3. Type this command:
|
||||
```shell
|
||||
$ git config --global core.editor "'C:/Program Files (x86)/sublime text 3/subl.exe' -w"
|
||||
```
|
||||
|
||||
## Usar Notepad++ como editor
|
||||
## Using Notepad++ as your editor
|
||||
|
||||
1. Instale Notepad++ desde https://notepad-plus-plus.org/. Para obtener más información, vea "[Introducción](https://npp-user-manual.org/docs/getting-started/)" en la documentación de Notepad++.
|
||||
1. Install Notepad++ from https://notepad-plus-plus.org/. For more information, see "[Getting started](https://npp-user-manual.org/docs/getting-started/)" in the Notepad++ documentation.
|
||||
{% data reusables.command_line.open_the_multi_os_terminal %}
|
||||
3. Escriba el siguiente comando:
|
||||
3. Type this command:
|
||||
```shell
|
||||
$ git config --global core.editor "'C:/Program Files (x86)/Notepad++/notepad++.exe' -multiInst -notabbar -nosession -noPlugin"
|
||||
```
|
||||
@@ -103,29 +79,20 @@ ms.locfileid: '145148763'
|
||||
|
||||
{% linux %}
|
||||
|
||||
## Usar Atom como editor
|
||||
## Using {% data variables.product.prodname_vscode %} as your editor
|
||||
|
||||
1. Instale [Atom](https://atom.io/). Para más información, vea "[Instalación de Atom](https://flight-manual.atom.io/getting-started/sections/installing-atom/)" en la documentación de Atom.
|
||||
1. Install [{% data variables.product.prodname_vscode %}](https://code.visualstudio.com/) ({% data variables.product.prodname_vscode_shortname %}). For more information, see "[Setting up {% data variables.product.prodname_vscode_shortname %}](https://code.visualstudio.com/Docs/setup/setup-overview)" in the {% data variables.product.prodname_vscode_shortname %} documentation.
|
||||
{% data reusables.command_line.open_the_multi_os_terminal %}
|
||||
3. Escriba el siguiente comando:
|
||||
```shell
|
||||
$ git config --global core.editor "atom --wait"
|
||||
```
|
||||
|
||||
## Uso de {% data variables.product.prodname_vscode %} como editor
|
||||
|
||||
1. Instala [{% data variables.product.prodname_vscode %}](https://code.visualstudio.com/) ({% data variables.product.prodname_vscode_shortname %}). Para obtener más información, consulta la documentación de {% data variables.product.prodname_vscode_shortname %}, la sección "[Configuración de {% data variables.product.prodname_vscode_shortname %}](https://code.visualstudio.com/Docs/setup/setup-overview)".
|
||||
{% data reusables.command_line.open_the_multi_os_terminal %}
|
||||
3. Escriba el siguiente comando:
|
||||
3. Type this command:
|
||||
```shell
|
||||
$ git config --global core.editor "code --wait"
|
||||
```
|
||||
|
||||
## Usar Sublime Text como editor
|
||||
## Using Sublime Text as your editor
|
||||
|
||||
1. Instale [Sublime Text](https://www.sublimetext.com/). Para obtener más información, vea "[Instalación](https://docs.sublimetext.io/guide/getting-started/installation.html)" en la documentación de Sublime Text.
|
||||
1. Install [Sublime Text](https://www.sublimetext.com/). For more information, see "[Installation](https://docs.sublimetext.io/guide/getting-started/installation.html)" in the Sublime Text documentation.
|
||||
{% data reusables.command_line.open_the_multi_os_terminal %}
|
||||
3. Escriba el siguiente comando:
|
||||
3. Type this command:
|
||||
```shell
|
||||
$ git config --global core.editor "subl -n -w"
|
||||
```
|
||||
|
||||
@@ -32,6 +32,7 @@ featuredLinks:
|
||||
- /get-started/onboarding/getting-started-with-github-enterprise-cloud
|
||||
- /get-started/onboarding/getting-started-with-github-enterprise-server
|
||||
- /get-started/onboarding/getting-started-with-github-ae
|
||||
- /get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/quickstart-for-writing-on-github
|
||||
popular:
|
||||
- /github/getting-started-with-github/signing-up-for-a-new-github-account
|
||||
- /get-started/quickstart/hello-world
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Comunicarse en GitHub
|
||||
intro: 'Puedes debatir cambios y proyectos específicos, así como metas de equipo o ideas más amplias, usando tipos diferentes de debates en {% data variables.product.product_name %}.'
|
||||
title: Communicating on GitHub
|
||||
intro: 'You can discuss specific projects and changes, as well as broader ideas or team goals, using different types of discussions on {% data variables.product.product_name %}.'
|
||||
miniTocMaxHeadingLevel: 3
|
||||
redirect_from:
|
||||
- /github/collaborating-with-issues-and-pull-requests/getting-started/quickstart-for-communicating-on-github
|
||||
@@ -18,137 +18,137 @@ topics:
|
||||
- Issues
|
||||
- Discussions
|
||||
- Fundamentals
|
||||
ms.openlocfilehash: 6c7461a01cd0bc44bff93b1eb4e8a013d26bc147
|
||||
ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: es-ES
|
||||
ms.lasthandoff: 09/05/2022
|
||||
ms.locfileid: '147408895'
|
||||
---
|
||||
## Introducción
|
||||
## Introduction
|
||||
|
||||
{% data variables.product.product_name %} proporciona herramientas de comunicación colaborativas que te permiten interactuar de cerca con tu comunidad. Esta guía de inicio rápido te mostrará cómo escoger la herramienta correcta para tus necesidades.
|
||||
{% data variables.product.product_name %} provides built-in collaborative communication tools allowing you to interact closely with your community. This quickstart guide will show you how to pick the right tool for your needs.
|
||||
|
||||
{% ifversion discussions %} Puedes crear y participar en propuestas, solicitudes de cambios, {% data variables.product.prodname_discussions %} y debates de equipo, dependiendo del tipo de conversación que te gustaría tener.
|
||||
{% else %} Puedes crear y participar en propuestas, solicitudes de extracción y debates de equipos, dependiendo del tipo de conversación que quieras tener.
|
||||
{% ifversion discussions %}
|
||||
You can create and participate in issues, pull requests, {% data variables.product.prodname_discussions %}, and team discussions, depending on the type of conversation you'd like to have.
|
||||
{% else %}
|
||||
You can create and participate in issues, pull requests and team discussions, depending on the type of conversation you'd like to have.
|
||||
{% endif %}
|
||||
|
||||
### {% data variables.product.prodname_github_issues %}
|
||||
- son útiles para debatir los detalles específicos de un proyecto, tales como los reportes de errores, mejoras planeadas y retroalimentación.
|
||||
- son específicas de un repositorio y, habitualmente, es claro quién es el propietario.
|
||||
- a menudo se refiere a ellas como el sistema de rastreo de errores de {% data variables.product.prodname_dotcom %}.
|
||||
- are useful for discussing specific details of a project such as bug reports, planned improvements and feedback.
|
||||
- are specific to a repository, and usually have a clear owner.
|
||||
- are often referred to as {% data variables.product.prodname_dotcom %}'s bug-tracking system.
|
||||
|
||||
### Solicitudes de incorporación de cambios
|
||||
- te permiten proponer cambios específicos.
|
||||
- te permiten comentar directamente en los cambios propuestos que otros sugieren.
|
||||
- son específicos para un repositorio.
|
||||
### Pull requests
|
||||
- allow you to propose specific changes.
|
||||
- allow you to comment directly on proposed changes suggested by others.
|
||||
- are specific to a repository.
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
### {% data variables.product.prodname_discussions %}
|
||||
- son como un foro y son muy útiles para ideas y debates abiertos en donde es importante la colaboración.
|
||||
- pueden abarcar muchos repositorios.
|
||||
- proporcionan una experiencia colaborativa fuera de la base de código, lo cual permite la lluvia de ideas y la creación de una base de conocimiento comunitario.
|
||||
- a menudo no se sabe quién es el propietario.
|
||||
- a menudo no dan como resultado una tarea sobre la cual se pueda actuar.
|
||||
- are like a forum, and are best used for open-form ideas and discussions where collaboration is important.
|
||||
- may span many repositories.
|
||||
- provide a collaborative experience outside the codebase, allowing the brainstorming of ideas, and the creation of a community knowledge base.
|
||||
- often don’t have a clear owner.
|
||||
- often do not result in an actionable task.
|
||||
{% endif %}
|
||||
|
||||
### Discusiones de equipo
|
||||
- pueden iniciarse en la página de tu equipo para tener conversaciones que abarquen varios proyectos y no pertenecen solo a una propuesta o solicitud de cambios específicas. En vez de abrir un informe de problemas en un repositorio para debatir sobre una idea, puedes incluir a todo el equipo si tienes una conversación en un debate de equipo.
|
||||
- te permiten mantener debates con tu equipo sobre planeación, análisis, diseño, investigación de usuarios y toma de decisiones generales de un proyecto, todo en un solo lugar.{% ifversion ghes or ghae %}
|
||||
- proporcionan una experiencia colaborativa fuera de la base de código, lo cual permite la lluvia de ideas.
|
||||
- a menudo no se sabe quién es el propietario.
|
||||
- a menudo no dan como resultad una tarea sobre la cual se pueda actuar.{% endif %}
|
||||
### Team discussions
|
||||
- can be started on your team's page for conversations that span across projects and don't belong in a specific issue or pull request. Instead of opening an issue in a repository to discuss an idea, you can include the entire team by having a conversation in a team discussion.
|
||||
- allow you to hold discussions with your team about planning, analysis, design, user research and general project decision making in one place.{% ifversion ghes or ghae %}
|
||||
- provide a collaborative experience outside the codebase, allowing the brainstorming of ideas.
|
||||
- often don’t have a clear owner.
|
||||
- often do not result in an actionable task.{% endif %}
|
||||
|
||||
## ¿Qué debate debo utilizar?
|
||||
## Which discussion tool should I use?
|
||||
|
||||
### Casos de las propuestas
|
||||
### Scenarios for issues
|
||||
|
||||
- Quiero dar seguimiento a las tareas, ampliaciones y errores.
|
||||
- Quiero emitir un reporte de errores.
|
||||
- Quiero compartir retroalimentación sobre una característica específica.
|
||||
- Quiero hacer una pregunta sobre los archivos del repositorio.
|
||||
- I want to keep track of tasks, enhancements and bugs.
|
||||
- I want to file a bug report.
|
||||
- I want to share feedback about a specific feature.
|
||||
- I want to ask a question about files in the repository.
|
||||
|
||||
#### Ejemplo de propuesta
|
||||
#### Issue example
|
||||
|
||||
Este ejemplo demuestra cómo un usuario de {% data variables.product.prodname_dotcom %} creó una propuesta en nuestro repositorio de documentación de código abierto para concientizarnos de un error y debatir sobre cómo arreglarlo.
|
||||
This example illustrates how a {% data variables.product.prodname_dotcom %} user created an issue in our documentation open source repository to make us aware of a bug, and discuss a fix.
|
||||
|
||||
|
||||
|
||||
|
||||
- Un usuario notó que el color azul del letrero en la parte superior de la página de la versión china de los documentos de {% data variables.product.prodname_dotcom %} hace que el texto contenido sea ilegible.
|
||||
- El usurio creó una propuesta en el repositorio, la cual declaraba el problema y sugería un arreglo (el cual es utilizar un color de fondo diferente para el letrero).
|
||||
- Se produce un debate y, periódicamente, se llega a un consenso sobre qué solución aplicar.
|
||||
- Entonces, un colaborador puede crear una solicitud de cambios con la solución.
|
||||
- A user noticed that the blue color of the banner at the top of the page in the Chinese version of the {% data variables.product.prodname_dotcom %} Docs makes the text in the banner unreadable.
|
||||
- The user created an issue in the repository, stating the problem and suggesting a fix (which is, use a different background color for the banner).
|
||||
- A discussion ensues, and eventually, a consensus will be reached about the fix to apply.
|
||||
- A contributor can then create a pull request with the fix.
|
||||
|
||||
### Escenarios para solicitudes de cambios
|
||||
### Scenarios for pull requests
|
||||
|
||||
- Quiero arreglar un error tipográcifo en un repositorio.
|
||||
- Quiero hacer cambios en un repositorio.
|
||||
- Quiero hacer cambios para corregir un error.
|
||||
- Quiero comentar en los cambios que otros sugieren.
|
||||
- I want to fix a typo in a repository.
|
||||
- I want to make changes to a repository.
|
||||
- I want to make changes to fix an issue.
|
||||
- I want to comment on changes suggested by others.
|
||||
|
||||
#### Ejemplo de solicitud de incorporación de cambios
|
||||
#### Pull request example
|
||||
|
||||
Este ejemplo ilustra cómo un usuario de {% data variables.product.prodname_dotcom %} creó una solicitud de cambios en el repositorio de código abierto de nuestra documentación para arreglar un error tipográfico.
|
||||
This example illustrates how a {% data variables.product.prodname_dotcom %} user created a pull request in our documentation open source repository to fix a typo.
|
||||
|
||||
En la pestaña **Conversación** de la solicitud de incorporación de cambios, el autor explica por qué ha creado la solicitud de incorporación de cambios.
|
||||
In the **Conversation** tab of the pull request, the author explains why they created the pull request.
|
||||
|
||||
|
||||
|
||||
|
||||
La pestaña **Archivos cambiados** de la solicitud de incorporación de cambios muestra la corrección implementada.
|
||||
The **Files changed** tab of the pull request shows the implemented fix.
|
||||
|
||||
|
||||
|
||||
|
||||
- Este contribuyente nota un error tipográfico en el repositorio.
|
||||
- El usuario crea una solicitud de cambios con la solución.
|
||||
- Un mantenedor de repositorio revisa la solicitud de cambios, la comenta y la fusiona.
|
||||
- This contributor notices a typo in the repository.
|
||||
- The user creates a pull request with the fix.
|
||||
- A repository maintainer reviews the pull request, comments on it, and merges it.
|
||||
|
||||
{% ifversion discussions %}
|
||||
### Casos para los {% data variables.product.prodname_discussions %}
|
||||
### Scenarios for {% data variables.product.prodname_discussions %}
|
||||
|
||||
- Tengo una pregunta que no se relaciona necesariamente con los archivos específicos del repositorio.
|
||||
- Quiero compartir las noticias con mis colaboradores o con mi equipo.
|
||||
- Quiero comenzar o participar en una conversación abierta.
|
||||
- Quiero hacer un anuncio a mi comunidad.
|
||||
- I have a question that's not necessarily related to specific files in the repository.
|
||||
- I want to share news with my collaborators, or my team.
|
||||
- I want to start or participate in an open-ended conversation.
|
||||
- I want to make an announcement to my community.
|
||||
|
||||
#### Ejemplo de {% data variables.product.prodname_discussions %}
|
||||
#### {% data variables.product.prodname_discussions %} example
|
||||
|
||||
Este ejemplo muestra la publicación de bienvenida de {% data variables.product.prodname_discussions %} para el repositorio de código abierto de los documentos de {% data variables.product.prodname_dotcom %} e ilustra cómo el equipo quiere colaborar con su comunidad.
|
||||
This example shows the {% data variables.product.prodname_discussions %} welcome post for the {% data variables.product.prodname_dotcom %} Docs open source repository, and illustrates how the team wants to collaborate with their community.
|
||||
|
||||
|
||||
|
||||
|
||||
El mantenedor de la comunidad inició un debate para recibir a la comunidad y para pedir a los miembros que se presentaran a sí mismos. Esta publicación fomenta un ambiente acogedor para los visitantes y contribuyentes. Esta publicación también aclara que al equipo le complace ayudar a los contribuyentes del repositorio.
|
||||
This community maintainer started a discussion to welcome the community, and to ask members to introduce themselves. This post fosters an inviting atmosphere for visitors and contributors. The post also clarifies that the team's happy to help with contributions to the repository.
|
||||
|
||||
{% endif %}
|
||||
### Casos de debates de equipo
|
||||
### Scenarios for team discussions
|
||||
|
||||
- Tengo una pregunta que no se relaciona necesariamente con los archivos específicos del repositorio.
|
||||
- Quiero compartir las noticias con mis colaboradores o con mi equipo.
|
||||
- Quiero comenzar o participar en una conversación abierta.
|
||||
- Quiero anunciar algo a mi equipo.
|
||||
- I have a question that's not necessarily related to specific files in the repository.
|
||||
- I want to share news with my collaborators, or my team.
|
||||
- I want to start or participate in an open-ended conversation.
|
||||
- I want to make an announcement to my team.
|
||||
|
||||
{% ifversion fpt or ghec %} Como puedes ver, los debates de equipo son muy similares a los {% data variables.product.prodname_discussions %}. Para {% data variables.product.prodname_dotcom_the_website %}, te recomendamos utilizar los {% data variables.product.prodname_discussions %} como inicio de conversaciones. Puedes utilizar los {% data variables.product.prodname_discussions %} para colaborar con cualquier comunidad en {% data variables.product.prodname_dotcom %}. Si eres parte de una organización y te gustaría iniciar conversaciones dentro de tu organización o del equipo que está dentro de ella, debes utilizar los debates de equipo.
|
||||
{% ifversion fpt or ghec %}
|
||||
As you can see, team discussions are very similar to {% data variables.product.prodname_discussions %}. For {% data variables.product.prodname_dotcom_the_website %}, we recommend using {% data variables.product.prodname_discussions %} as the starting point for conversations. You can use {% data variables.product.prodname_discussions %} to collaborate with any community on {% data variables.product.prodname_dotcom %}. If you are part of an organization, and would like to initiate conversations within your organization or team within that organization, you should use team discussions.
|
||||
{% endif %}
|
||||
|
||||
#### Ejemplo de debates de equipo
|
||||
#### Team discussion example
|
||||
|
||||
En este ejemplo se muestra una publicación de equipo para el equipo `octo-team`.
|
||||
This example shows a team post for the `octo-team` team.
|
||||
|
||||
|
||||
|
||||
|
||||
El miembro del equipo `octocat` publicó un debate de equipo e informó al equipo de varias cosas:
|
||||
- Un miembro del equipo llamado Mona inició eventos de juego remotos.
|
||||
- Hay una publicación del blog que describe cómo los equipos utilizan {% data variables.product.prodname_actions %} para producir sus documentos.
|
||||
- Los materiales sobre el "All Hands" de abril está ahora disponible para que lo vean todos los miembros del equipo.
|
||||
The `octocat` team member posted a team discussion, informing the team of various things:
|
||||
- A team member called Mona started remote game events.
|
||||
- There is a blog post describing how the teams use {% data variables.product.prodname_actions %} to produce their docs.
|
||||
- Material about the April All Hands is now available for all team members to view.
|
||||
|
||||
## Pasos siguientes
|
||||
## Next steps
|
||||
|
||||
Estos ejemplos te muestran cómo decidir cuál es la mejor herramienta para tus conversaciones en {% data variables.product.product_name %}. Pero esto es solo el inicio; puedes hacer mucho más para confeccionar estas herramientas de acuerdo con tus necesidades.
|
||||
These examples showed you how to decide which is the best tool for your conversations on {% data variables.product.product_name %}. But this is only the beginning; there is so much more you can do to tailor these tools to your needs.
|
||||
|
||||
Para las propuestas, por ejemplo, puedes etiquetarlas con etiquetas para buscarlas más rápidamente y crear plantillas de propuesta para ayudar a los contribuyentes a abrir propuestas significativas. Para obtener más información, consulta "[Acerca de las propuestas](/github/managing-your-work-on-github/about-issues#working-with-issues)" y "[Acerca de las plantillas de propuestas y solicitudes de incorporación de cambios](/communities/using-templates-to-encourage-useful-issues-and-pull-requests/about-issue-and-pull-request-templates)".
|
||||
For issues, for example, you can tag issues with labels for quicker searching and create issue templates to help contributors open meaningful issues. For more information, see "[About issues](/github/managing-your-work-on-github/about-issues#working-with-issues)" and "[About issue and pull request templates](/communities/using-templates-to-encourage-useful-issues-and-pull-requests/about-issue-and-pull-request-templates)."
|
||||
|
||||
Para las solicitudes de cambio, puedes crear borradores de estas si los cambios que propones aún están en curso. Los borradores de solicitudes de cambios no pueden fusionarse hasta que se marquen como listos para revisión. Para más información, vea "[Acerca de las solicitudes de incorporación de cambios](/github/collaborating-with-issues-and-pull-requests/about-pull-requests#draft-pull-requests)".
|
||||
For pull requests, you can create draft pull requests if your proposed changes are still a work in progress. Draft pull requests cannot be merged until they're marked as ready for review. For more information, see "[About pull requests](/github/collaborating-with-issues-and-pull-requests/about-pull-requests#draft-pull-requests)."
|
||||
|
||||
{% ifversion discussions %} Para el caso de los {% data variables.product.prodname_discussions %}, puedes{% ifversion fpt or ghec %} configurar un código de conducta y{% endif %} fijar los debates que contengan información importante de tu comunidad. Para más información, vea "[Acerca de los debates](/discussions/collaborating-with-your-community-using-discussions/about-discussions)".
|
||||
{% ifversion discussions %}
|
||||
For {% data variables.product.prodname_discussions %}, you can{% ifversion fpt or ghec %} set up a code of conduct and{% endif %} pin discussions that contain important information for your community. For more information, see "[About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions)."
|
||||
{% endif %}
|
||||
|
||||
Para el caso de los debates de equipo, puedes editarlos o borrarlos en la página del equipo y puedes configurar las notificaciones para estos. Para obtener más información, consulta "[Acerca de los debates de equipo](/organizations/collaborating-with-your-team/about-team-discussions)".
|
||||
For team discussions, you can edit or delete discussions on a team's page, and you can configure notifications for team discussions. For more information, see "[About team discussions](/organizations/collaborating-with-your-team/about-team-discussions)."
|
||||
|
||||
To learn some advanced formatting features that will help you communicate, see "[Quickstart for writing on {% data variables.product.prodname_dotcom %}](/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/quickstart-for-writing-on-github)."
|
||||
@@ -1,12 +1,12 @@
|
||||
---
|
||||
title: Recursos de aprendizaje de Git y GitHub
|
||||
title: Git and GitHub learning resources
|
||||
redirect_from:
|
||||
- /articles/good-resources-for-learning-git-and-github
|
||||
- /articles/what-are-other-good-resources-for-learning-git-and-github
|
||||
- /articles/git-and-github-learning-resources
|
||||
- /github/getting-started-with-github/git-and-github-learning-resources
|
||||
- /github/getting-started-with-github/quickstart/git-and-github-learning-resources
|
||||
intro: 'Hay muchos recursos útiles de Git y {% data variables.product.product_name %} disponibles en la web. La siguientes es una pequeña lista de nuestros favoritos.'
|
||||
intro: 'There are a lot of helpful Git and {% data variables.product.product_name %} resources on the web. This is a short list of our favorites!'
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
@@ -15,55 +15,49 @@ versions:
|
||||
authors:
|
||||
- GitHub
|
||||
shortTitle: Learning resources
|
||||
ms.openlocfilehash: d8d0457de2842392febee0c90660285e9b1afef8
|
||||
ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: es-ES
|
||||
ms.lasthandoff: 09/05/2022
|
||||
ms.locfileid: '146139300'
|
||||
---
|
||||
## Utilizar GitHub
|
||||
## Using Git
|
||||
|
||||
Para familiarizarse con Git, visite el [sitio oficial del proyecto de Git](https://git-scm.com) y lea el [libro ProGit](http://git-scm.com/book). También puedes revisar la [lista de comandos de Git](https://git-scm.com/docs).
|
||||
Familiarize yourself with Git by visiting the [official Git project site](https://git-scm.com) and reading the [ProGit book](http://git-scm.com/book). You can also review the [Git command list](https://git-scm.com/docs).
|
||||
|
||||
## Uso de {% data variables.product.product_name %}
|
||||
## Using {% data variables.product.product_name %}
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
|
||||
{% data variables.product.prodname_learning %} ofrece cursos interactivos gratuitos integrados en {% data variables.product.prodname_dotcom %} con evaluación y asistencia instantáneas y automatizadas. Aprende a abrir tu primera solicitud de extracción, hacer tu primera contribución de código abierto, crear un sitio {% data variables.product.prodname_pages %}, y mucho más. Para más información sobre las ofertas de cursos, vea [{% data variables.product.prodname_learning %}]({% data variables.product.prodname_learning_link %}).
|
||||
{% data variables.product.prodname_learning %} offers free interactive courses that are built into {% data variables.product.prodname_dotcom %} with instant automated feedback and help. Learn to open your first pull request, make your first open source contribution, create a {% data variables.product.prodname_pages %} site, and more. For more information about course offerings, see [{% data variables.product.prodname_learning %}]({% data variables.product.prodname_learning_link %}).
|
||||
|
||||
{% endif %}
|
||||
|
||||
Familiarícese mejor con {% data variables.product.product_name %} con ayuda de nuestros artículos de [introducción](/categories/getting-started-with-github/). Vea nuestro [flujo de {% data variables.product.prodname_dotcom %}](https://guides.github.com/introduction/flow) para obtener una introducción al proceso. Consulte nuestras [guías de información general](https://guides.github.com) para examinar los conceptos básicos.
|
||||
Become better acquainted with {% data variables.product.product_name %} through our [getting started](/categories/getting-started-with-github/) articles. See our [{% data variables.product.prodname_dotcom %} flow](https://guides.github.com/introduction/flow) for a process introduction. Refer to our [overview guides](https://guides.github.com) to walk through basic concepts.
|
||||
|
||||
{% data reusables.support.ask-and-answer-forum %}
|
||||
|
||||
### Ramas, bifurcaciones y solicitudes de extracción
|
||||
### Branches, forks, and pull requests
|
||||
|
||||
Obtenga información sobre la [creación de ramas de Git](http://learngitbranching.js.org/) mediante una herramienta interactiva. Obtenga información sobre [bifurcaciones](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks) y [solicitudes de incorporación de cambios](/articles/using-pull-requests), y [sobre cómo usamos solicitudes de incorporación de cambios](https://github.com/blog/1124-how-we-use-pull-requests-to-build-github) en {% data variables.product.prodname_dotcom %}. Acceda a referencias sobre el uso de {% data variables.product.prodname_dotcom %} desde la [línea de comandos](https://cli.github.com/).
|
||||
Learn about [Git branching](http://learngitbranching.js.org/) using an interactive tool. Read about [forks](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks) and [pull requests](/articles/using-pull-requests) as well as [how we use pull requests](https://github.com/blog/1124-how-we-use-pull-requests-to-build-github) at {% data variables.product.prodname_dotcom %}. Access references about using {% data variables.product.prodname_dotcom %} from the [command line](https://cli.github.com/).
|
||||
|
||||
### Ponte al día
|
||||
### Tune in
|
||||
|
||||
En nuestro [canal de aprendizaje y guías en YouTube](https://youtube.com/githubguides) de {% data variables.product.prodname_dotcom %} se ofrecen tutoriales sobre [solicitudes de incorporación de cambios](https://www.youtube.com/watch?v=d5wpJ5VimSU&list=PLg7s6cbtAD15G8lNyoaYDuKZSKyJrgwB-&index=19), [bifurcaciones](https://www.youtube.com/watch?v=5oJHRbqEofs), [fusión mediante cambio de base](https://www.youtube.com/watch?v=SxzjZtJwOgo&list=PLg7s6cbtAD15G8lNyoaYDuKZSKyJrgwB-&index=22) y [restablecimiento](https://www.youtube.com/watch?v=BKPjPMVB81g) de funciones. Cada tema se cubre en menos de 5 minutos.
|
||||
Our {% data variables.product.prodname_dotcom %} [YouTube Training and Guides channel](https://youtube.com/githubguides) offers tutorials about [pull requests](https://www.youtube.com/watch?v=d5wpJ5VimSU&list=PLg7s6cbtAD15G8lNyoaYDuKZSKyJrgwB-&index=19), [forking](https://www.youtube.com/watch?v=5oJHRbqEofs), [rebase](https://www.youtube.com/watch?v=SxzjZtJwOgo&list=PLg7s6cbtAD15G8lNyoaYDuKZSKyJrgwB-&index=22), and [reset](https://www.youtube.com/watch?v=BKPjPMVB81g) functions. Each topic is covered in 5 minutes or less.
|
||||
|
||||
## Cursos
|
||||
## Training
|
||||
|
||||
### Cursos gratuitos
|
||||
### Free courses
|
||||
|
||||
{% data variables.product.product_name %} ofrece una serie de [cursos de aprendizaje a petición](https://skills.github.com/) e interactivos, como [Introducción a {% data variables.product.prodname_dotcom %}](https://github.com/skills/introduction-to-github), y cursos herramientas específicas de {% data variables.product.product_name %}, como {% data variables.product.prodname_actions %}.
|
||||
{% data variables.product.product_name %} offers a series of interactive, [on-demand training courses](https://skills.github.com/) including [Introduction to {% data variables.product.prodname_dotcom %}](https://github.com/skills/introduction-to-github); and courses on {% data variables.product.product_name %} specific tools such as {% data variables.product.prodname_actions %}.
|
||||
|
||||
### Programas educativos basados en la web de {% data variables.product.prodname_dotcom %}
|
||||
### {% data variables.product.prodname_dotcom %}'s web-based educational programs
|
||||
|
||||
{% data variables.product.prodname_dotcom %} ofrece [entrenamientos](https://services.github.com/#upcoming-events) en directo con un enfoque práctico basado en proyectos para los usuarios a los que les encanta la línea de comandos y a los que no.
|
||||
{% data variables.product.prodname_dotcom %} offers live [trainings](https://services.github.com/#upcoming-events) with a hands-on, project-based approach for those who love the command line and those who don't.
|
||||
|
||||
### Capacitación para tu compañía
|
||||
### Training for your company
|
||||
|
||||
{% data variables.product.prodname_dotcom %} ofrece [clases presenciales](https://services.github.com/#offerings) impartidas por formadores altamente experimentados. [Póngase en contacto con nosotros](https://services.github.com/#contact) para formular sus preguntas relacionadas con el entrenamiento.
|
||||
{% data variables.product.prodname_dotcom %} offers [in-person classes](https://services.github.com/#offerings) taught by our highly-experienced educators. [Contact us](https://services.github.com/#contact) to ask your training-related questions.
|
||||
|
||||
## Extras
|
||||
|
||||
Un [curso de Git en línea](https://www.pluralsight.com/courses/code-school-git-real) interactivo de [Pluralsight](https://www.pluralsight.com/codeschool) tiene siete niveles con docenas de ejercicios en un formato de juego divertido. No dude en adaptar nuestras [plantillas de .gitignore](https://github.com/github/gitignore) para adecuarlas a sus necesidades.
|
||||
An interactive [online Git course](https://www.pluralsight.com/courses/code-school-git-real) from [Pluralsight](https://www.pluralsight.com/codeschool) has seven levels with dozens of exercises in a fun game format. Feel free to adapt our [.gitignore templates](https://github.com/github/gitignore) to meet your needs.
|
||||
|
||||
Amplíe los conocimientos sobre {% data variables.product.prodname_dotcom %} mediante {% ifversion fpt or ghec %}[integraciones](/articles/about-integrations){% else %}integraciones{% endif %}, o bien con la instalación de [{% data variables.product.prodname_desktop %}](https://desktop.github.com) y el sólido editor de texto [Atom](https://atom.io).
|
||||
Extend your {% data variables.product.prodname_dotcom %} reach through {% ifversion fpt or ghec %}[integrations](/articles/about-integrations){% else %}integrations{% endif %}, or by installing [{% data variables.product.prodname_desktop %}](https://desktop.github.com) and the robust [{% data variables.product.prodname_vscode %}](https://code.visualstudio.com/) text editor.
|
||||
|
||||
Obtenga información sobre cómo iniciar y aumentar el proyecto de código abierto con las [Guías de código abierto](https://opensource.guide/).
|
||||
Learn how to launch and grow your open source project with the [Open Source Guides](https://opensource.guide/).
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Acerca de escritura y formato en GitHub
|
||||
intro: GitHub combina una sintáxis para el texto con formato llamado formato Markdown de GitHub con algunas características de escritura únicas.
|
||||
title: About writing and formatting on GitHub
|
||||
intro: GitHub combines a syntax for formatting text called GitHub Flavored Markdown with a few unique writing features.
|
||||
redirect_from:
|
||||
- /articles/about-writing-and-formatting-on-github
|
||||
- /github/writing-on-github/about-writing-and-formatting-on-github
|
||||
@@ -10,40 +10,36 @@ versions:
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
shortTitle: Write & format on GitHub
|
||||
ms.openlocfilehash: 7819ebc6bbf3ffa8696c87f82745a19c103c8134
|
||||
ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: es-ES
|
||||
ms.lasthandoff: 09/09/2022
|
||||
ms.locfileid: '147860838'
|
||||
shortTitle: About writing & formatting
|
||||
---
|
||||
[Markdown](http://daringfireball.net/projects/markdown/) es una sintaxis fácil de leer y escribir para dar formato al texto sin formato.
|
||||
[Markdown](http://daringfireball.net/projects/markdown/) is an easy-to-read, easy-to-write syntax for formatting plain text.
|
||||
|
||||
Le hemos agregado alguna funcionalidad personalizada para crear el formato Markdown de {% data variables.product.prodname_dotcom %}, usado para dar formato a la prosa y al código en todo nuestro sitio.
|
||||
We've added some custom functionality to create {% data variables.product.prodname_dotcom %} Flavored Markdown, used to format prose and code across our site.
|
||||
|
||||
También puede interactuar con otros usuarios en solicitudes de incorporación de cambios e incidencias mediante características como [@mentions](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams), [referencias de incidencia y PR](/articles/basic-writing-and-formatting-syntax/#referencing-issues-and-pull-requests), y [emoji](/articles/basic-writing-and-formatting-syntax/#using-emoji).
|
||||
You can also interact with other users in pull requests and issues using features like [@mentions](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams), [issue and PR references](/articles/basic-writing-and-formatting-syntax/#referencing-issues-and-pull-requests), and [emoji](/articles/basic-writing-and-formatting-syntax/#using-emoji).
|
||||
|
||||
## Barra de herramientas de formato de texto
|
||||
## Text formatting toolbar
|
||||
|
||||
Cada campo de comentario en {% data variables.product.product_name %} contiene una barra de herramientas de formato de texto, lo que te permite dar formato a tu texto sin tener que aprender la sintáxis de Markdown. Además del formato de Markdown como los estilos de negrita y cursiva, y la creación de encabezados, enlaces y listas, la barra de herramientas incluye características específicas de {% data variables.product.product_name %}, como @mentions, listados de tareas y vínculos a incidencias y solicitudes de incorporación de cambios.
|
||||
Every comment field on {% data variables.product.product_name %} contains a text formatting toolbar, allowing you to format your text without learning Markdown syntax. In addition to Markdown formatting like bold and italic styles and creating headers, links, and lists, the toolbar includes {% data variables.product.product_name %}-specific features such as @mentions, task lists, and links to issues and pull requests.
|
||||
|
||||
{% ifversion fixed-width-font-gfm-fields %}
|
||||
|
||||
## Habilitar fuentes de ancho fijo en el editor
|
||||
## Enabling fixed-width fonts in the editor
|
||||
|
||||
Puedes habilitar las fuentes de ancho fijo en cada campo de comentario de {% data variables.product.product_name %}. Cada carácter en una fuente de ancho fijo o de monoespacio ocupa el mismo espacio horizontal, lo cual hace más fácil la edición de las estructuras de lenguaje de marcado, tales como tablas y fragmentos de código.
|
||||
You can enable a fixed-width font in every comment field on {% data variables.product.product_name %}. Each character in a fixed-width, or monospace, font occupies the same horizontal space which can make it easier to edit advanced Markdown structures such as tables and code snippets.
|
||||
|
||||
|
||||
|
||||
|
||||
{% data reusables.user-settings.access_settings %} {% data reusables.user-settings.appearance-settings %}
|
||||
1. En "Preferencia de fuente del editor de Markdown", seleccione **Usar una fuente de ancho fijo (monoespacial) al editar Markdown**.
|
||||
|
||||
{% data reusables.user-settings.access_settings %}
|
||||
{% data reusables.user-settings.appearance-settings %}
|
||||
1. Under "Markdown editor font preference", select **Use a fixed-width (monospace) font when editing Markdown**.
|
||||
|
||||
|
||||
{% endif %}
|
||||
|
||||
## Información adicional
|
||||
## Further reading
|
||||
|
||||
- [Especificación de {% data variables.product.prodname_dotcom %} Flavored Markdown](https://github.github.com/gfm/)
|
||||
- "[Sintaxis de escritura y formato básicos](/articles/basic-writing-and-formatting-syntax)"
|
||||
- "[Trabajo con el formato avanzado](/articles/working-with-advanced-formatting)"
|
||||
- [{% data variables.product.prodname_dotcom %} Flavored Markdown Spec](https://github.github.com/gfm/)
|
||||
- "[Basic writing and formatting syntax](/articles/basic-writing-and-formatting-syntax)"
|
||||
- "[Working with advanced formatting](/articles/working-with-advanced-formatting)"
|
||||
- "[Quickstart for writing on {% data variables.product.prodname_dotcom %}](/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/quickstart-for-writing-on-github)"
|
||||
|
||||
@@ -179,13 +179,7 @@ You can specify the theme an image is displayed for in Markdown by using the HTM
|
||||
|
||||
For example, the following code displays a sun image for light themes and a moon for dark themes:
|
||||
|
||||
```HTML
|
||||
<picture>
|
||||
<source media="(prefers-color-scheme: dark)" srcset="https://user-images.githubusercontent.com/25423296/163456776-7f95b81a-f1ed-45f7-b7ab-8fa810d529fa.png">
|
||||
<source media="(prefers-color-scheme: light)" srcset="https://user-images.githubusercontent.com/25423296/163456779-a8556205-d0a5-45e2-ac17-42d089e3c3f8.png">
|
||||
<img alt="Shows an illustrated sun in light color mode and a moon with stars in dark color mode." src="https://user-images.githubusercontent.com/25423296/163456779-a8556205-d0a5-45e2-ac17-42d089e3c3f8.png">
|
||||
</picture>
|
||||
```
|
||||
{% data reusables.getting-started.picture-element-example %}
|
||||
|
||||
The old method of specifying images based on the theme, by using a fragment appended to the URL (`#gh-dark-mode-only` or `#gh-light-mode-only`), is deprecated and will be removed in favor of the new method described above.
|
||||
{% endif %}
|
||||
@@ -216,7 +210,7 @@ To order your list, precede each line with a number.
|
||||
|
||||
You can create a nested list by indenting one or more list items below another item.
|
||||
|
||||
To create a nested list using the web editor on {% data variables.product.product_name %} or a text editor that uses a monospaced font, like [Atom](https://atom.io/), you can align your list visually. Type space characters in front of your nested list item, until the list marker character (<kbd>-</kbd> or <kbd>*</kbd>) lies directly below the first character of the text in the item above it.
|
||||
To create a nested list using the web editor on {% data variables.product.product_name %} or a text editor that uses a monospaced font, like [{% data variables.product.prodname_vscode %}](https://code.visualstudio.com/), you can align your list visually. Type space characters in front of your nested list item, until the list marker character (<kbd>-</kbd> or <kbd>*</kbd>) lies directly below the first character of the text in the item above it.
|
||||
|
||||
```markdown
|
||||
1. First list item
|
||||
@@ -394,3 +388,4 @@ For more information, see Daring Fireball's "[Markdown Syntax](https://daringfir
|
||||
- [{% data variables.product.prodname_dotcom %} Flavored Markdown Spec](https://github.github.com/gfm/)
|
||||
- "[About writing and formatting on GitHub](/articles/about-writing-and-formatting-on-github)"
|
||||
- "[Working with advanced formatting](/articles/working-with-advanced-formatting)"
|
||||
- "[Quickstart for writing on {% data variables.product.prodname_dotcom %}](/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/quickstart-for-writing-on-github)"
|
||||
|
||||
@@ -12,6 +12,7 @@ versions:
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
children:
|
||||
- /quickstart-for-writing-on-github
|
||||
- /about-writing-and-formatting-on-github
|
||||
- /basic-writing-and-formatting-syntax
|
||||
shortTitle: Start writing on GitHub
|
||||
|
||||
@@ -70,8 +70,8 @@ You can find the node ID of an organization project if you know the organization
|
||||
```shell
|
||||
curl --request POST \
|
||||
--url https://api.github.com/graphql \
|
||||
--header 'Authorization: Bearer <em>TOKEN</em>' \
|
||||
--data '{"query":"query{organization(login: \"<em>ORGANIZATION</em>\") {projectV2(number: <em>NUMBER</em>){id}}}"}'
|
||||
--header 'Authorization: Bearer TOKEN' \
|
||||
--data '{"query":"query{organization(login: \"ORGANIZATION\") {projectV2(number: NUMBER){id}}}"}'
|
||||
```
|
||||
{% endcurl %}
|
||||
|
||||
@@ -79,8 +79,8 @@ curl --request POST \
|
||||
```shell
|
||||
gh api graphql -f query='
|
||||
query{
|
||||
organization(login: "<em>ORGANIZATION</em>"){
|
||||
projectV2(number: <em>NUMBER</em>) {
|
||||
organization(login: "ORGANIZATION"){
|
||||
projectV2(number: NUMBER) {
|
||||
id
|
||||
}
|
||||
}
|
||||
@@ -94,8 +94,8 @@ You can also find the node ID of all projects in your organization. The followin
|
||||
```shell
|
||||
curl --request POST \
|
||||
--url https://api.github.com/graphql \
|
||||
--header 'Authorization: Bearer <em>TOKEN</em>' \
|
||||
--data '{"query":"{organization(login: \"<em>ORGANIZATION</em>\") {projectsV2(first: 20) {nodes {id title}}}}"}'
|
||||
--header 'Authorization: Bearer TOKEN' \
|
||||
--data '{"query":"{organization(login: \"ORGANIZATION") {projectsV2(first: 20) {nodes {id title}}}}"}'
|
||||
```
|
||||
{% endcurl %}
|
||||
|
||||
@@ -103,7 +103,7 @@ curl --request POST \
|
||||
```shell
|
||||
gh api graphql -f query='
|
||||
query{
|
||||
organization(login: "<em>ORGANIZATION</em>") {
|
||||
organization(login: "ORGANIZATION") {
|
||||
projectsV2(first: 20) {
|
||||
nodes {
|
||||
id
|
||||
@@ -125,8 +125,8 @@ You can find the node ID of a user project if you know the project number. Repla
|
||||
```shell
|
||||
curl --request POST \
|
||||
--url https://api.github.com/graphql \
|
||||
--header 'Authorization: Bearer <em>TOKEN</em>' \
|
||||
--data '{"query":"query{user(login: \"<em>USER</em>\") {projectV2(number: <em>NUMBER</em>){id}}}"}'
|
||||
--header 'Authorization: Bearer TOKEN' \
|
||||
--data '{"query":"query{user(login: \"USER\") {projectV2(number: NUMBER){id}}}"}'
|
||||
```
|
||||
{% endcurl %}
|
||||
|
||||
@@ -134,8 +134,8 @@ curl --request POST \
|
||||
```shell
|
||||
gh api graphql -f query='
|
||||
query{
|
||||
user(login: "<em>USER</em>"){
|
||||
projectV2(number: <em>NUMBER</em>) {
|
||||
user(login: "USER"){
|
||||
projectV2(number: NUMBER) {
|
||||
id
|
||||
}
|
||||
}
|
||||
@@ -149,8 +149,8 @@ You can also find the node ID for all of your projects. The following example wi
|
||||
```shell
|
||||
curl --request POST \
|
||||
--url https://api.github.com/graphql \
|
||||
--header 'Authorization: Bearer <em>TOKEN</em>' \
|
||||
--data '{"query":"{user(login: \"<em>USER</em>\") {projectsV2(first: 20) {nodes {id title}}}}"}'
|
||||
--header 'Authorization: Bearer TOKEN' \
|
||||
--data '{"query":"{user(login: \"USER\") {projectsV2(first: 20) {nodes {id title}}}}"}'
|
||||
```
|
||||
{% endcurl %}
|
||||
|
||||
@@ -158,7 +158,7 @@ curl --request POST \
|
||||
```shell
|
||||
gh api graphql -f query='
|
||||
query{
|
||||
user(login: "<em>USER</em>") {
|
||||
user(login: "USER") {
|
||||
projectsV2(first: 20) {
|
||||
nodes {
|
||||
id
|
||||
@@ -180,8 +180,8 @@ The following example will return the ID, name, settings, and configuration for
|
||||
```shell
|
||||
curl --request POST \
|
||||
--url https://api.github.com/graphql \
|
||||
--header 'Authorization: Bearer <em>TOKEN</em>' \
|
||||
--data '{"query":"query{ node(id: \"<em>PROJECT_ID</em>\") { ... on ProjectV2 { fields(first: 20) { nodes { ... on ProjectV2Field { id name } ... on ProjectV2IterationField { id name configuration { iterations { startDate id }}} ... on ProjectV2SingleSelectField { id name options { id name }}}}}}}"}'
|
||||
--header 'Authorization: Bearer TOKEN' \
|
||||
--data '{"query":"query{ node(id: \"PROJECT_ID\") { ... on ProjectV2 { fields(first: 20) { nodes { ... on ProjectV2Field { id name } ... on ProjectV2IterationField { id name configuration { iterations { startDate id }}} ... on ProjectV2SingleSelectField { id name options { id name }}}}}}}"}'
|
||||
```
|
||||
{% endcurl %}
|
||||
|
||||
@@ -189,7 +189,7 @@ curl --request POST \
|
||||
```shell
|
||||
gh api graphql -f query='
|
||||
query{
|
||||
node(id: "<em>PROJECT_ID</em>") {
|
||||
node(id: "PROJECT_ID") {
|
||||
... on ProjectV2 {
|
||||
fields(first: 20) {
|
||||
nodes {
|
||||
@@ -284,8 +284,8 @@ If you just need the name and ID of a field, and do not need information about i
|
||||
```shell
|
||||
curl --request POST \
|
||||
--url https://api.github.com/graphql \
|
||||
--header 'Authorization: Bearer <em>TOKEN</em>' \
|
||||
--data '{"query":"query{ node(id: \"<em>PROJECT_ID</em>\") { ... on ProjectV2 { fields(first: 20) { nodes { ... on ProjectV2FieldCommon { id name }}}}}}"}'
|
||||
--header 'Authorization: Bearer TOKEN' \
|
||||
--data '{"query":"query{ node(id: \"PROJECT_ID\") { ... on ProjectV2 { fields(first: 20) { nodes { ... on ProjectV2FieldCommon { id name }}}}}}"}'
|
||||
```
|
||||
{% endcurl %}
|
||||
|
||||
@@ -293,7 +293,7 @@ curl --request POST \
|
||||
```shell
|
||||
gh api graphql -f query='
|
||||
query{
|
||||
node(id: "<em>PROJECT_ID</em>") {
|
||||
node(id: "PROJECT_ID") {
|
||||
... on ProjectV2 {
|
||||
fields(first: 20) {
|
||||
nodes {
|
||||
@@ -354,8 +354,8 @@ The following example will return the first 20 issues, pull requests, and draft
|
||||
```shell
|
||||
curl --request POST \
|
||||
--url https://api.github.com/graphql \
|
||||
--header 'Authorization: Bearer <em>TOKEN</em>' \
|
||||
--data '{"query":"query{ node(id: \"<em>PROJECT_ID</em>\") { ... on ProjectV2 { items(first: 20) { nodes{ id fieldValues(first: 8) { nodes{ ... on ProjectV2ItemFieldTextValue { text field { ... on ProjectV2FieldCommon { name }}} ... on ProjectV2ItemFieldDateValue { date field { ... on ProjectV2FieldCommon { name } } } ... on ProjectV2ItemFieldSingleSelectValue { name field { ... on ProjectV2FieldCommon { name }}}}} content{ ... on DraftIssue { title body } ...on Issue { title assignees(first: 10) { nodes{ login }}} ...on PullRequest { title assignees(first: 10) { nodes{ login }}}}}}}}}"}'
|
||||
--header 'Authorization: Bearer TOKEN' \
|
||||
--data '{"query":"query{ node(id: \"PROJECT_ID\") { ... on ProjectV2 { items(first: 20) { nodes{ id fieldValues(first: 8) { nodes{ ... on ProjectV2ItemFieldTextValue { text field { ... on ProjectV2FieldCommon { name }}} ... on ProjectV2ItemFieldDateValue { date field { ... on ProjectV2FieldCommon { name } } } ... on ProjectV2ItemFieldSingleSelectValue { name field { ... on ProjectV2FieldCommon { name }}}}} content{ ... on DraftIssue { title body } ...on Issue { title assignees(first: 10) { nodes{ login }}} ...on PullRequest { title assignees(first: 10) { nodes{ login }}}}}}}}}"}'
|
||||
```
|
||||
{% endcurl %}
|
||||
|
||||
@@ -363,7 +363,7 @@ curl --request POST \
|
||||
```shell
|
||||
gh api graphql -f query='
|
||||
query{
|
||||
node(id: "<em>PROJECT_ID</em>") {
|
||||
node(id: "PROJECT_ID") {
|
||||
... on ProjectV2 {
|
||||
items(first: 20) {
|
||||
nodes{
|
||||
@@ -446,8 +446,8 @@ The following example will add an issue or pull request to your project. Replace
|
||||
```shell
|
||||
curl --request POST \
|
||||
--url https://api.github.com/graphql \
|
||||
--header 'Authorization: Bearer <em>TOKEN</em>' \
|
||||
--data '{"query":"mutation {addProjectV2ItemById(input: {projectId: \"<em>PROJECT_ID</em>\" contentId: \"<em>CONTENT_ID</em>\"}) {item {id}}}"}'
|
||||
--header 'Authorization: Bearer TOKEN' \
|
||||
--data '{"query":"mutation {addProjectV2ItemById(input: {projectId: \"PROJECT_ID\" contentId: \"CONTENT_ID\"}) {item {id}}}"}'
|
||||
```
|
||||
{% endcurl %}
|
||||
|
||||
@@ -455,7 +455,7 @@ curl --request POST \
|
||||
```shell
|
||||
gh api graphql -f query='
|
||||
mutation {
|
||||
addProjectV2ItemById(input: {projectId: "<em>PROJECT_ID</em>" contentId: "<em>CONTENT_ID</em>"}) {
|
||||
addProjectV2ItemById(input: {projectId: "PROJECT_ID" contentId: "CONTENT_ID"}) {
|
||||
item {
|
||||
id
|
||||
}
|
||||
@@ -488,8 +488,8 @@ The following example will add a draft issue to your project. Replace `PROJECT_I
|
||||
```shell
|
||||
curl --request POST \
|
||||
--url https://api.github.com/graphql \
|
||||
--header 'Authorization: Bearer <em>TOKEN</em>' \
|
||||
--data '{"query":"mutation {addProjectV2DraftIssue(input: {projectId: "<em>PROJECT_ID</em>" title: "<em>TITLE</em>" body: "<em>BODY</em>"}) {projectItem {id}}}"}'
|
||||
--header 'Authorization: Bearer TOKEN' \
|
||||
--data '{"query":"mutation {addProjectV2DraftIssue(input: {projectId: \"PROJECT_ID\" title: \"TITLE\" body: \"BODY\"}) {projectItem {id}}}"}'
|
||||
```
|
||||
{% endcurl %}
|
||||
|
||||
@@ -497,7 +497,7 @@ curl --request POST \
|
||||
```shell
|
||||
gh api graphql -f query='
|
||||
mutation {
|
||||
addProjectV2DraftIssue(input: {projectId: "<em>PROJECT_ID</em>" title: "<em>TITLE</em>" body: "<em>BODY</em>"}) {
|
||||
addProjectV2DraftIssue(input: {projectId: "PROJECT_ID" title: "TITLE" body: "BODY"}) {
|
||||
projectItem {
|
||||
id
|
||||
}
|
||||
@@ -528,8 +528,8 @@ The following example will update your project's settings. Replace `PROJECT_ID`
|
||||
```shell
|
||||
curl --request POST \
|
||||
--url https://api.github.com/graphql \
|
||||
--header 'Authorization: Bearer <em>TOKEN</em>' \
|
||||
--data '{"query":"mutation { updateProjectV2(input: { projectId: \"<em>PROJECT_ID</em>\", title: \"Project title\", public: false, readme: \"# Project README\n\nA long description\", shortDescription: \"A short description\"}) { projectV2 { id, title, readme, shortDescription }}}"}'
|
||||
--header 'Authorization: Bearer TOKEN' \
|
||||
--data '{"query":"mutation { updateProjectV2(input: { projectId: \"PROJECT_ID\", title: \"Project title\", public: false, readme: \"# Project README\n\nA long description\", shortDescription: \"A short description\"}) { projectV2 { id, title, readme, shortDescription }}}"}'
|
||||
```
|
||||
{% endcurl %}
|
||||
|
||||
@@ -539,7 +539,7 @@ gh api graphql -f query='
|
||||
mutation {
|
||||
updateProjectV2(
|
||||
input: {
|
||||
projectId: "<em>PROJECT_ID</em>",
|
||||
projectId: "PROJECT_ID",
|
||||
title: "Project title",
|
||||
public: false,
|
||||
readme: "# Project README\n\nA long description",
|
||||
@@ -565,8 +565,8 @@ The following example will update the value of a text field for an item. Replace
|
||||
```shell
|
||||
curl --request POST \
|
||||
--url https://api.github.com/graphql \
|
||||
--header 'Authorization: Bearer <em>TOKEN</em>' \
|
||||
--data '{"query":"mutation {updateProjectV2ItemFieldValue( input: { projectId: "<em>PROJECT_ID</em>" itemId: "<em>ITEM_ID</em>" fieldId: "<em>FIELD_ID</em>" value: { text: "Updated text" }}) { projectV2Item { id }}}"}'
|
||||
--header 'Authorization: Bearer TOKEN' \
|
||||
--data '{"query":"mutation {updateProjectV2ItemFieldValue( input: { projectId: "PROJECT_ID" itemId: "ITEM_ID" fieldId: "FIELD_ID" value: { text: "Updated text" }}) { projectV2Item { id }}}"}'
|
||||
```
|
||||
{% endcurl %}
|
||||
|
||||
@@ -576,9 +576,9 @@ gh api graphql -f query='
|
||||
mutation {
|
||||
updateProjectV2ItemFieldValue(
|
||||
input: {
|
||||
projectId: "<em>PROJECT_ID</em>"
|
||||
itemId: "<em>ITEM_ID</em>"
|
||||
fieldId: "<em>FIELD_ID</em>"
|
||||
projectId: "PROJECT_ID"
|
||||
itemId: "ITEM_ID"
|
||||
fieldId: "FIELD_ID"
|
||||
value: {
|
||||
text: "Updated text"
|
||||
}
|
||||
@@ -619,8 +619,8 @@ The following example will update the value of a single select field for an item
|
||||
```shell
|
||||
curl --request POST \
|
||||
--url https://api.github.com/graphql \
|
||||
--header 'Authorization: Bearer <em>TOKEN</em>' \
|
||||
--data '{"query":"mutation {updateProjectV2ItemFieldValue( input: { projectId: "<em>PROJECT_ID</em>" itemId: "<em>ITEM_ID</em>" fieldId: "<em>FIELD_ID</em>" value: { singleSelectOptionId: "<em>OPTION_ID</em>" }}) { projectV2Item { id }}}"}'
|
||||
--header 'Authorization: Bearer TOKEN' \
|
||||
--data '{"query":"mutation {updateProjectV2ItemFieldValue( input: { projectId: "PROJECT_ID" itemId: "ITEM_ID" fieldId: "FIELD_ID" value: { singleSelectOptionId: "OPTION_ID" }}) { projectV2Item { id }}}"}'
|
||||
```
|
||||
{% endcurl %}
|
||||
|
||||
@@ -630,11 +630,11 @@ gh api graphql -f query='
|
||||
mutation {
|
||||
updateProjectV2ItemFieldValue(
|
||||
input: {
|
||||
projectId: "<em>PROJECT_ID</em>"
|
||||
itemId: "<em>ITEM_ID</em>"
|
||||
fieldId: "<em>FIELD_ID</em>"
|
||||
projectId: "PROJECT_ID"
|
||||
itemId: "ITEM_ID"
|
||||
fieldId: "FIELD_ID"
|
||||
value: {
|
||||
singleSelectOptionId: "<em>OPTION_ID</em>"
|
||||
singleSelectOptionId: "OPTION_ID"
|
||||
}
|
||||
}
|
||||
) {
|
||||
@@ -659,8 +659,8 @@ The following example will update the value of an iteration field for an item.
|
||||
```shell
|
||||
curl --request POST \
|
||||
--url https://api.github.com/graphql \
|
||||
--header 'Authorization: Bearer <em>TOKEN</em>' \
|
||||
--data '{"query":"mutation {updateProjectV2ItemFieldValue( input: { projectId: "<em>PROJECT_ID</em>" itemId: "<em>ITEM_ID</em>" fieldId: "<em>FIELD_ID</em>" value: { singleSelectOptionId: "<em>OPTION_ID</em>" }}) { projectV2Item { id }}}"}'
|
||||
--header 'Authorization: Bearer TOKEN' \
|
||||
--data '{"query":"mutation {updateProjectV2ItemFieldValue( input: { projectId: "PROJECT_ID" itemId: "ITEM_ID" fieldId: "FIELD_ID" value: { singleSelectOptionId: "OPTION_ID" }}) { projectV2Item { id }}}"}'
|
||||
```
|
||||
{% endcurl %}
|
||||
|
||||
@@ -670,11 +670,11 @@ gh api graphql -f query='
|
||||
mutation {
|
||||
updateProjectV2ItemFieldValue(
|
||||
input: {
|
||||
projectId: "<em>PROJECT_ID</em>"
|
||||
itemId: "<em>ITEM_ID</em>"
|
||||
fieldId: "<em>FIELD_ID</em>"
|
||||
projectId: "PROJECT_ID"
|
||||
itemId: "ITEM_ID"
|
||||
fieldId: "FIELD_ID"
|
||||
value: {
|
||||
iterationId: "<em>ITERATION_ID</em>"
|
||||
iterationId: "ITERATION_ID"
|
||||
}
|
||||
}
|
||||
) {
|
||||
@@ -694,8 +694,8 @@ The following example will delete an item from a project. Replace `PROJECT_ID` w
|
||||
```shell
|
||||
curl --request POST \
|
||||
--url https://api.github.com/graphql \
|
||||
--header 'Authorization: Bearer <em>TOKEN</em>' \
|
||||
--data '{"query":"mutation {deleteProjectV2Item(input: {projectId: \"<em>PROJECT_ID</em>\" itemId: \"<em>ITEM_ID</em>\"}) {deletedItemId}}"}'
|
||||
--header 'Authorization: Bearer TOKEN' \
|
||||
--data '{"query":"mutation {deleteProjectV2Item(input: {projectId: \"PROJECT_ID\" itemId: \"ITEM_ID\"}) {deletedItemId}}"}'
|
||||
```
|
||||
{% endcurl %}
|
||||
|
||||
@@ -705,8 +705,8 @@ gh api graphql -f query='
|
||||
mutation {
|
||||
deleteProjectV2Item(
|
||||
input: {
|
||||
projectId: "<em>PROJECT_ID</em>"
|
||||
itemId: "<em>ITEM_ID</em>"
|
||||
projectId: "PROJECT_ID"
|
||||
itemId: "ITEM_ID"
|
||||
}
|
||||
) {
|
||||
deletedItemId
|
||||
|
||||
@@ -192,7 +192,7 @@ For pull requests, you can also use search to:
|
||||
- Filter pull requests by [reviewer](/articles/about-pull-request-reviews/): `state:open type:pr reviewed-by:octocat`
|
||||
- Filter pull requests by the specific user [requested for review](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review): `state:open type:pr review-requested:octocat`{% ifversion fpt or ghae or ghes > 3.2 or ghec %}
|
||||
- Filter pull requests that someone has asked you directly to review: `state:open type:pr user-review-requested:@me`{% endif %}
|
||||
- Filter pull requests by the team requested for review: `state:open type:pr team-review-requested:github/atom`
|
||||
- Filter pull requests by the team requested for review: `state:open type:pr team-review-requested:github/docs`
|
||||
- Filter for pull requests that are linked to an issue that the pull request may close: `linked:issue`
|
||||
|
||||
## Sorting issues and pull requests
|
||||
|
||||
@@ -62,11 +62,11 @@ For more information on Punycodes, see [Internationalized domain name](https://e
|
||||
{% data reusables.command_line.open_the_multi_os_terminal %}
|
||||
6. To confirm that your DNS record configured correctly, use the `dig` command, replacing _WWW.EXAMPLE.COM_ with your subdomain.
|
||||
```shell
|
||||
$ dig <em>WWW.EXAMPLE.COM</em> +nostats +nocomments +nocmd
|
||||
> ;<em>WWW.EXAMPLE.COM.</em> IN A
|
||||
> <em>WWW.EXAMPLE.COM.</em> 3592 IN CNAME <em>YOUR-USERNAME</em>.github.io.
|
||||
> <em>YOUR-USERNAME</em>.github.io. 43192 IN CNAME <em> GITHUB-PAGES-SERVER </em>.
|
||||
> <em> GITHUB-PAGES-SERVER </em>. 22 IN A 192.0.2.1
|
||||
$ dig WWW.EXAMPLE.COM +nostats +nocomments +nocmd
|
||||
> ;WWW.EXAMPLE.COM. IN A
|
||||
> WWW.EXAMPLE.COM. 3592 IN CNAME YOUR-USERNAME.github.io.
|
||||
> YOUR-USERNAME.github.io. 43192 IN CNAME GITHUB-PAGES-SERVER .
|
||||
> GITHUB-PAGES-SERVER . 22 IN A 192.0.2.1
|
||||
```
|
||||
{% data reusables.pages.build-locally-download-cname %}
|
||||
{% data reusables.pages.enforce-https-custom-domain %}
|
||||
@@ -104,19 +104,19 @@ To set up an apex domain, such as `example.com`, you must configure a custom dom
|
||||
6. To confirm that your DNS record configured correctly, use the `dig` command, replacing _EXAMPLE.COM_ with your apex domain. Confirm that the results match the IP addresses for {% data variables.product.prodname_pages %} above.
|
||||
- For `A` records.
|
||||
```shell
|
||||
$ dig <em>EXAMPLE.COM</em> +noall +answer -t A
|
||||
> <em>EXAMPLE.COM</em> 3600 IN A 185.199.108.153
|
||||
> <em>EXAMPLE.COM</em> 3600 IN A 185.199.109.153
|
||||
> <em>EXAMPLE.COM</em> 3600 IN A 185.199.110.153
|
||||
> <em>EXAMPLE.COM</em> 3600 IN A 185.199.111.153
|
||||
$ dig EXAMPLE.COM +noall +answer -t A
|
||||
> EXAMPLE.COM 3600 IN A 185.199.108.153
|
||||
> EXAMPLE.COM 3600 IN A 185.199.109.153
|
||||
> EXAMPLE.COM 3600 IN A 185.199.110.153
|
||||
> EXAMPLE.COM 3600 IN A 185.199.111.153
|
||||
```
|
||||
- For `AAAA` records.
|
||||
```shell
|
||||
$ dig <em>EXAMPLE.COM</em> +noall +answer -t AAAA
|
||||
> <em>EXAMPLE.COM</em> 3600 IN AAAA 2606:50c0:8000::153
|
||||
> <em>EXAMPLE.COM</em> 3600 IN AAAA 2606:50c0:8001::153
|
||||
> <em>EXAMPLE.COM</em> 3600 IN AAAA 2606:50c0:8002::153
|
||||
> <em>EXAMPLE.COM</em> 3600 IN AAAA 2606:50c0:8003::153
|
||||
$ dig EXAMPLE.COM +noall +answer -t AAAA
|
||||
> EXAMPLE.COM 3600 IN AAAA 2606:50c0:8000::153
|
||||
> EXAMPLE.COM 3600 IN AAAA 2606:50c0:8001::153
|
||||
> EXAMPLE.COM 3600 IN AAAA 2606:50c0:8002::153
|
||||
> EXAMPLE.COM 3600 IN AAAA 2606:50c0:8003::153
|
||||
```
|
||||
{% data reusables.pages.build-locally-download-cname %}
|
||||
{% data reusables.pages.enforce-https-custom-domain %}
|
||||
@@ -132,11 +132,11 @@ After you configure the apex domain, you must configure a CNAME record with your
|
||||
1. Navigate to your DNS provider and create a `CNAME` record that points `www.example.com` to the default domain for your site: `<user>.github.io` or `<organization>.github.io`. Do not include the repository name. {% data reusables.pages.contact-dns-provider %} {% data reusables.pages.default-domain-information %}
|
||||
2. To confirm that your DNS record configured correctly, use the `dig` command, replacing _WWW.EXAMPLE.COM_ with your `www` subdomain variant.
|
||||
```shell
|
||||
$ dig <em>WWW.EXAMPLE.COM</em> +nostats +nocomments +nocmd
|
||||
> ;<em>WWW.EXAMPLE.COM.</em> IN A
|
||||
> <em>WWW.EXAMPLE.COM.</em> 3592 IN CNAME <em>YOUR-USERNAME</em>.github.io.
|
||||
> <em>YOUR-USERNAME</em>.github.io. 43192 IN CNAME <em> GITHUB-PAGES-SERVER </em>.
|
||||
> <em> GITHUB-PAGES-SERVER </em>. 22 IN A 192.0.2.1
|
||||
$ dig WWW.EXAMPLE.COM +nostats +nocomments +nocmd
|
||||
> ;WWW.EXAMPLE.COM IN A
|
||||
> WWW.EXAMPLE.COM. 3592 IN CNAME YOUR-USERNAME.github.io.
|
||||
> YOUR-USERNAME.github.io. 43192 IN CNAME GITHUB-PAGES-SERVER.
|
||||
> GITHUB-PAGES-SERVER. 22 IN A 192.0.2.1
|
||||
```
|
||||
## Removing a custom domain
|
||||
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Resolver un conflicto de fusión con la línea de comando
|
||||
intro: Puedes resolver conflictos de fusión con la línea de comando y un editor de texto.
|
||||
title: Resolving a merge conflict using the command line
|
||||
intro: You can resolve merge conflicts using the command line and a text editor.
|
||||
redirect_from:
|
||||
- /github/collaborating-with-issues-and-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-using-the-command-line
|
||||
- /articles/resolving-a-merge-conflict-from-the-command-line
|
||||
@@ -15,33 +15,27 @@ versions:
|
||||
topics:
|
||||
- Pull requests
|
||||
shortTitle: Resolve merge conflicts in Git
|
||||
ms.openlocfilehash: 1d4ff97c2a93d3e5a7aebaa8752810e284203bc1
|
||||
ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: es-ES
|
||||
ms.lasthandoff: 09/11/2022
|
||||
ms.locfileid: '147883461'
|
||||
---
|
||||
Los conflictos de fusión ocurren cuando se hacen cambios contrapuestos en la misma línea de un archivo o cuando una persona edita un archivo y otra persona borra el mismo archivo. Para más información, vea "[Acerca de los conflictos de combinación](/articles/about-merge-conflicts/)".
|
||||
Merge conflicts occur when competing changes are made to the same line of a file, or when one person edits a file and another person deletes the same file. For more information, see "[About merge conflicts](/articles/about-merge-conflicts/)."
|
||||
|
||||
{% tip %}
|
||||
|
||||
**Sugerencia:** Puede usar el editor de conflictos de {% data variables.product.product_name %} para resolver conflictos de combinación de cambios de líneas contrapuestos entre ramas que forman parte de una solicitud de incorporación de cambios. Para más información, vea "[Resolución de un conflicto de combinación en GitHub](/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-on-github)".
|
||||
**Tip:** You can use the conflict editor on {% data variables.product.product_name %} to resolve competing line change merge conflicts between branches that are part of a pull request. For more information, see "[Resolving a merge conflict on GitHub](/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-on-github)."
|
||||
|
||||
{% endtip %}
|
||||
|
||||
## Conflictos de fusión de cambios de líneas contrapuestos
|
||||
## Competing line change merge conflicts
|
||||
|
||||
Para resolver un conflicto de fusión causado por cambios de líneas contrapuestos, debes decidir qué cambios incorporar desde las diferentes ramas de una confirmación nueva.
|
||||
To resolve a merge conflict caused by competing line changes, you must choose which changes to incorporate from the different branches in a new commit.
|
||||
|
||||
Por ejemplo, si usted y otra persona han editado el archivo _styleguide.md_ en las mismas líneas de diferentes ramas del mismo repositorio de Git, recibirá un error de conflicto de combinación cuando intente combinar estas ramas. Debes resolver este conflicto de fusión con una confirmación nueva antes de que puedas fusionar estas ramas.
|
||||
For example, if you and another person both edited the file _styleguide.md_ on the same lines in different branches of the same Git repository, you'll get a merge conflict error when you try to merge these branches. You must resolve this merge conflict with a new commit before you can merge these branches.
|
||||
|
||||
{% data reusables.command_line.open_the_multi_os_terminal %}
|
||||
2. Navega en el repositorio de Git local que tiene el conflicto de fusión.
|
||||
2. Navigate into the local Git repository that has the merge conflict.
|
||||
```shell
|
||||
cd <em>REPOSITORY-NAME</em>
|
||||
cd REPOSITORY-NAME
|
||||
```
|
||||
3. Genera una lista de los archivos afectados por el conflicto de fusión. En este ejemplo, el archivo *styleguide.md* tiene un conflicto de combinación.
|
||||
3. Generate a list of the files affected by the merge conflict. In this example, the file *styleguide.md* has a merge conflict.
|
||||
```shell
|
||||
$ git status
|
||||
> # On branch branch-b
|
||||
@@ -55,8 +49,8 @@ Por ejemplo, si usted y otra persona han editado el archivo _styleguide.md_ en l
|
||||
> #
|
||||
> no changes added to commit (use "git add" and/or "git commit -a")
|
||||
```
|
||||
4. Abra el editor de texto que prefiera, por ejemplo [Atom](https://atom.io/), y vaya al archivo que tiene conflictos de combinación.
|
||||
5. Para ver el origen de un conflicto de combinación en el archivo, busque el marcador de conflicto `<<<<<<<` en el archivo. Al abrir el archivo en el editor de texto, verá los cambios de la rama HEAD o de base después de la línea `<<<<<<< HEAD`. A continuación, verá `=======`, que divide los cambios de los de la otra rama, seguido de `>>>>>>> BRANCH-NAME`. En este ejemplo, una persona ha escrito "abrir una incidencia" en la rama HEAD o de base, y otra persona ha escrito "formula tu pregunta en IRC" en la rama comparada o `branch-a`.
|
||||
4. Open your favorite text editor, such as [{% data variables.product.prodname_vscode %}](https://code.visualstudio.com/), and navigate to the file that has merge conflicts.
|
||||
5. To see the beginning of the merge conflict in your file, search the file for the conflict marker `<<<<<<<`. When you open the file in your text editor, you'll see the changes from the HEAD or base branch after the line `<<<<<<< HEAD`. Next, you'll see `=======`, which divides your changes from the changes in the other branch, followed by `>>>>>>> BRANCH-NAME`. In this example, one person wrote "open an issue" in the base or HEAD branch and another person wrote "ask your question in IRC" in the compare branch or `branch-a`.
|
||||
|
||||
```
|
||||
If you have questions, please
|
||||
@@ -66,34 +60,34 @@ Por ejemplo, si usted y otra persona han editado el archivo _styleguide.md_ en l
|
||||
ask your question in IRC.
|
||||
>>>>>>> branch-a
|
||||
```
|
||||
{% data reusables.pull_requests.decide-how-to-resolve-competing-line-change-merge-conflict %}En este ejemplo, ambos cambios se incorporaron en la fusión final:
|
||||
{% data reusables.pull_requests.decide-how-to-resolve-competing-line-change-merge-conflict %} In this example, both changes are incorporated into the final merge:
|
||||
|
||||
```shell
|
||||
If you have questions, please open an issue or ask in our IRC channel if it's more urgent.
|
||||
```
|
||||
7. Agrega o lanza tus cambios.
|
||||
7. Add or stage your changes.
|
||||
```shell
|
||||
$ git add .
|
||||
```
|
||||
8. Confirma tus cambios con un comentario.
|
||||
8. Commit your changes with a comment.
|
||||
```shell
|
||||
$ git commit -m "Resolved merge conflict by incorporating both suggestions."
|
||||
```
|
||||
|
||||
Ahora puede combinar las ramas en la línea de comandos, o bien [insertar los cambios en el repositorio remoto](/github/getting-started-with-github/pushing-commits-to-a-remote-repository/) en {% data variables.product.product_name %} y [combinar los cambios](/articles/merging-a-pull-request/) en una solicitud de incorporación de cambios.
|
||||
You can now merge the branches on the command line or [push your changes to your remote repository](/github/getting-started-with-github/pushing-commits-to-a-remote-repository/) on {% data variables.product.product_name %} and [merge your changes](/articles/merging-a-pull-request/) in a pull request.
|
||||
|
||||
## Conflictos de fusión de archivos eliminados
|
||||
## Removed file merge conflicts
|
||||
|
||||
Para resolver un conflicto de fusión causado por cambios contrapuestos en un archivo, cuando una persona elimina un archivo en una rama y otra persona edita el mismo archivo, debes decidir si eliminar o conservar el archivo eliminado en una confirmación nueva.
|
||||
To resolve a merge conflict caused by competing changes to a file, where a person deletes a file in one branch and another person edits the same file, you must choose whether to delete or keep the removed file in a new commit.
|
||||
|
||||
Por ejemplo, si ha editado un archivo, como *README.md*, y otra persona ha eliminado el mismo archivo en otra rama del mismo repositorio de Git, recibirá un error de conflicto de combinación cuando intente combinar estas ramas. Debes resolver este conflicto de fusión con una confirmación nueva antes de que puedas fusionar estas ramas.
|
||||
For example, if you edited a file, such as *README.md*, and another person removed the same file in another branch in the same Git repository, you'll get a merge conflict error when you try to merge these branches. You must resolve this merge conflict with a new commit before you can merge these branches.
|
||||
|
||||
{% data reusables.command_line.open_the_multi_os_terminal %}
|
||||
2. Navega en el repositorio de Git local que tiene el conflicto de fusión.
|
||||
2. Navigate into the local Git repository that has the merge conflict.
|
||||
```shell
|
||||
cd <em>REPOSITORY-NAME</em>
|
||||
cd REPOSITORY-NAME
|
||||
```
|
||||
2. Genera una lista de los archivos afectados por el conflicto de fusión. En este ejemplo, el archivo *README.md* tiene un conflicto de combinación.
|
||||
2. Generate a list of the files affected by the merge conflict. In this example, the file *README.md* has a merge conflict.
|
||||
```shell
|
||||
$ git status
|
||||
> # On branch main
|
||||
@@ -106,32 +100,32 @@ Por ejemplo, si ha editado un archivo, como *README.md*, y otra persona ha elimi
|
||||
> # Unmerged paths:
|
||||
> # (use "git add/rm <file>..." as appropriate to mark resolution)
|
||||
> #
|
||||
> # deleted by us: README.md
|
||||
> # deleted by us: README.md
|
||||
> #
|
||||
> # no changes added to commit (use "git add" and/or "git commit -a")
|
||||
```
|
||||
3. Abra el editor de texto que prefiera, por ejemplo [Atom](https://atom.io/), y vaya al archivo que tiene conflictos de combinación.
|
||||
6. Decide si quieres conservar el archivo eliminado. Puede que quieras ver los últimos cambios hechos en el archivo eliminado en tu editor de texto.
|
||||
3. Open your favorite text editor, such as [{% data variables.product.prodname_vscode %}](https://code.visualstudio.com/), and navigate to the file that has merge conflicts.
|
||||
6. Decide if you want keep the removed file. You may want to view the latest changes made to the removed file in your text editor.
|
||||
|
||||
Para volver a agregar el archivo eliminado a tu repositorio:
|
||||
To add the removed file back to your repository:
|
||||
```shell
|
||||
$ git add README.md
|
||||
```
|
||||
Para eliminar este archivo de tu repositorio:
|
||||
To remove this file from your repository:
|
||||
```shell
|
||||
$ git rm README.md
|
||||
> README.md: needs merge
|
||||
> rm 'README.md'
|
||||
```
|
||||
7. Confirma tus cambios con un comentario.
|
||||
7. Commit your changes with a comment.
|
||||
```shell
|
||||
$ git commit -m "Resolved merge conflict by keeping README.md file."
|
||||
> [branch-d 6f89e49] Merge branch 'branch-c' into branch-d
|
||||
```
|
||||
|
||||
Ahora puede combinar las ramas en la línea de comandos, o bien [insertar los cambios en el repositorio remoto](/github/getting-started-with-github/pushing-commits-to-a-remote-repository/) en {% data variables.product.product_name %} y [combinar los cambios](/articles/merging-a-pull-request/) en una solicitud de incorporación de cambios.
|
||||
You can now merge the branches on the command line or [push your changes to your remote repository](/github/getting-started-with-github/pushing-commits-to-a-remote-repository/) on {% data variables.product.product_name %} and [merge your changes](/articles/merging-a-pull-request/) in a pull request.
|
||||
|
||||
## Información adicional
|
||||
## Further reading
|
||||
|
||||
- "[Acerca de los conflictos de combinación](/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/about-merge-conflicts)"
|
||||
- "[Extracción del repositorio de las solicitudes de incorporación de cambios localmente](/articles/checking-out-pull-requests-locally/)"
|
||||
- "[About merge conflicts](/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/about-merge-conflicts)"
|
||||
- "[Checking out pull requests locally](/articles/checking-out-pull-requests-locally/)"
|
||||
|
||||
@@ -83,7 +83,7 @@ If you decide you don't want the changes in a topic branch to be merged to the u
|
||||
To merge a pull request, use the `gh pr merge` subcommand. Replace `pull-request` with the number, URL, or head branch of the pull request.
|
||||
|
||||
```shell
|
||||
gh pr merge <em>pull-request</em>
|
||||
gh pr merge PULL-REQUEST
|
||||
```
|
||||
|
||||
Follow the interactive prompts to complete the merge. For more information about the merge methods that you can choose, see "[About pull request merges](/github/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges)."
|
||||
|
||||
@@ -90,7 +90,7 @@ You can choose whether {% data variables.large_files.product_name_long %} ({% da
|
||||
1. To create a release, use the `gh release create` subcommand. Replace `tag` with the desired tag for the release.
|
||||
|
||||
```shell
|
||||
gh release create <em>tag</em>
|
||||
gh release create TAG
|
||||
```
|
||||
|
||||
2. Follow the interactive prompts. Alternatively, you can specify arguments to skip these prompts. For more information about possible arguments, see [the {% data variables.product.prodname_cli %} manual](https://cli.github.com/manual/gh_release_create). For example, this command creates a prerelease with the specified title and notes.
|
||||
@@ -153,7 +153,7 @@ Releases cannot currently be edited with {% data variables.product.prodname_cli
|
||||
1. To delete a release, use the `gh release delete` subcommand. Replace `tag` with the tag of the release to delete. Use the `-y` flag to skip confirmation.
|
||||
|
||||
```shell
|
||||
gh release delete <em>tag</em> -y
|
||||
gh release delete TAG -y
|
||||
```
|
||||
|
||||
{% endcli %}
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Acerca de los archivos grandes en GitHub
|
||||
intro: '{% data variables.product.product_name %} limita el tamaño de los archivos que puedes rastrear en los repositorios regulares de Git. Aprende cómo rastrear o eliminar archivos que sobrepasan el límite.'
|
||||
title: About large files on GitHub
|
||||
intro: '{% data variables.product.product_name %} limits the size of files you can track in regular Git repositories. Learn how to track or remove files that are beyond the limit.'
|
||||
redirect_from:
|
||||
- /articles/distributing-large-binaries
|
||||
- /github/managing-large-files/distributing-large-binaries
|
||||
@@ -22,88 +22,85 @@ versions:
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
shortTitle: Large files
|
||||
ms.openlocfilehash: c9910f669b13c0c2bc4a8517ac6b33476b23b475
|
||||
ms.sourcegitcommit: 80842b4e4c500daa051eff0ccd7cde91c2d4bb36
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: es-ES
|
||||
ms.lasthandoff: 09/12/2022
|
||||
ms.locfileid: '146331652'
|
||||
---
|
||||
## Acerca de los límites de tamaño en {% data variables.product.product_name %}
|
||||
|
||||
{% ifversion fpt or ghec %} {% data variables.product.product_name %} intenta proporcionar un abundante almacenamiento para todos los repositorios de Git, pero hay límites muy estrictos de tamaños de archivos y repositorios. Para garantizar el rendimiento y la legibilidad para nuestros usuarios, monitoreamos activamente las señales de la salud general de los repositorios. La salud de los repositorios es una función de varios factores de interacción, incluyendo el tamaño, frecuencia de confirmaciones y estructura.
|
||||
## About size limits on {% data variables.product.product_name %}
|
||||
|
||||
### Límites de tamaño de archivo
|
||||
{% ifversion fpt or ghec %}
|
||||
{% data variables.product.product_name %} tries to provide abundant storage for all Git repositories, although there are hard limits for file and repository sizes. To ensure performance and reliability for our users, we actively monitor signals of overall repository health. Repository health is a function of various interacting factors, including size, commit frequency, contents, and structure.
|
||||
|
||||
### File size limits
|
||||
{% endif %}
|
||||
|
||||
{% data variables.product.product_name %} limita el tamaño de los archivos permitidos en los repositorios. Recibirás una advertencia de Git si intentas añadir o actualizar un archivo mayor a {% data variables.large_files.warning_size %}. Los cambios aún se subirán a tu repositorio, pero puedes considerar eliminar la confirmación para minimizar el impacto en el rendimiento. Para obtener más información, consulte "[Eliminación de archivos del historial de un repositorio](#removing-files-from-a-repositorys-history)".
|
||||
{% data variables.product.product_name %} limits the size of files allowed in repositories. If you attempt to add or update a file that is larger than {% data variables.large_files.warning_size %}, you will receive a warning from Git. The changes will still successfully push to your repository, but you can consider removing the commit to minimize performance impact. For more information, see "[Removing files from a repository's history](#removing-files-from-a-repositorys-history)."
|
||||
|
||||
{% note %}
|
||||
|
||||
**Nota:** Si agrega un archivo a un repositorio por medio de un explorador, el archivo no puede ser mayor de {% data variables.large_files.max_github_browser_size %}. Para obtener más información, consulte "[Adición de un archivo a un repositorio](/repositories/working-with-files/managing-files/adding-a-file-to-a-repository)".
|
||||
**Note:** If you add a file to a repository via a browser, the file can be no larger than {% data variables.large_files.max_github_browser_size %}. For more information, see "[Adding a file to a repository](/repositories/working-with-files/managing-files/adding-a-file-to-a-repository)."
|
||||
|
||||
{% endnote %}
|
||||
|
||||
{% ifversion ghes %}By default, {% endif %}{% data variables.product.product_name %} bloquea los envíos de cambios que superan los {% data variables.large_files.max_github_size %}. {% ifversion ghes %}Sin embargo, el administrador de un sitio puede configurar un límite diferente para {% data variables.product.product_location %}. Para obtener más información, consulte "[Configuración de límites de envío de cambios en Git](/enterprise/admin/guides/installation/setting-git-push-limits)".{% endif %}
|
||||
{% ifversion ghes %}By default, {% endif %}{% data variables.product.product_name %} blocks files larger than {% data variables.large_files.max_github_size %}. {% ifversion ghes %}However, a site administrator can configure a different limit for {% data variables.product.product_location %}. For more information, see "[Setting Git push limits](/enterprise/admin/guides/installation/setting-git-push-limits)."{% endif %}
|
||||
|
||||
Para rastrear archivos que sobrepasen este límite, debes utilizar {% data variables.large_files.product_name_long %} ({% data variables.large_files.product_name_short %}). Para obtener más información, consulte "[Acerca de {% data variables.large_files.product_name_long %}](/repositories/working-with-files/managing-large-files/about-git-large-file-storage)".
|
||||
To track files beyond this limit, you must use {% data variables.large_files.product_name_long %} ({% data variables.large_files.product_name_short %}). For more information, see "[About {% data variables.large_files.product_name_long %}](/repositories/working-with-files/managing-large-files/about-git-large-file-storage)."
|
||||
|
||||
Si necesitas distribuir archivos grandes dentro de tu repositorio, puedes crear lanzamientos en {% data variables.product.product_location %} en vez de rastrear los archivos. Para obtener más información, consulte "[Distribución de archivos binarios grandes](#distributing-large-binaries)".
|
||||
If you need to distribute large files within your repository, you can create releases on {% data variables.product.product_location %} instead of tracking the files. For more information, see "[Distributing large binaries](#distributing-large-binaries)."
|
||||
|
||||
Git no se diseñó para manejar archivos grandes de SQL. Para compartir bases de datos grandes con otros desarrolladores, se recomienda usar [Dropbox](https://www.dropbox.com/).
|
||||
Git is not designed to handle large SQL files. To share large databases with other developers, we recommend using [Dropbox](https://www.dropbox.com/).
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
### Límites de tamaño de repositorio
|
||||
{% ifversion fpt or ghec or ghae %}
|
||||
### Repository size limits
|
||||
|
||||
Te recomendamos que los repositorios sean siempre pequeños, idealmente, de menos de 1 GB, y se recomienda ampliamente que sean de menos de 5GB. Los repositorios más pequeños se clonan más rápido y se puede mantenerlos mejor y trabajar en ellos más fácilmente. Si tu repositorio impacta excesivamente nuestra infraestructura, puede que recibas un mensaje de correo electrónico de {% data variables.contact.github_support %}, el cual te solicitará que tomes acciones correctivas. Intentamos ser flexibles, especialmente con proyectos grandes que tienen muchos colaboradores, y trabajaremos junto contigo para encontrar una resolución cada que sea posible. Puedes prevenir que tu repositorio impacte nuestra infraestructura si administras el tamaño de tu repositorio y su salud general con eficacia. Puede encontrar consejos y una herramienta para el análisis de repositorios en el repositorio [`github/git-sizer`](https://github.com/github/git-sizer).
|
||||
We recommend repositories remain small, ideally less than 1 GB, and less than 5 GB is strongly recommended. {% ifversion ghae %}The maximum size for a repository on {% data variables.product.product_name %} is 100 GB. {% endif %}Smaller repositories are faster to clone and easier to work with and maintain. If your repository excessively impacts our infrastructure, you might receive an email from {% data variables.contact.github_support %} asking you to take corrective action. We try to be flexible, especially with large projects that have many collaborators, and will work with you to find a resolution whenever possible. You can prevent your repository from impacting our infrastructure by effectively managing your repository's size and overall health. You can find advice and a tool for repository analysis in the [`github/git-sizer`](https://github.com/github/git-sizer) repository.
|
||||
|
||||
Las dependencias externas pueden causar que los repositorios de Git se hagan muy grandes. Para evitar llenar un repositorio con dependencias externas, te recomendamos utilizar un administrador de paquetes. Entre los administradores de paquetes más populares para los lenguajes comunes se incluyen [Bundler](http://bundler.io/), el [Administrador de paquetes de Node](http://npmjs.org/) y [Maven](http://maven.apache.org/). Estos administradores de paquetes soportan la utilización directa de repositorios de Git para que no dependas de fuentes pre-empacadas.
|
||||
External dependencies can cause Git repositories to become very large. To avoid filling a repository with external dependencies, we recommend you use a package manager. Popular package managers for common languages include [Bundler](http://bundler.io/), [Node's Package Manager](http://npmjs.org/), and [Maven](http://maven.apache.org/). These package managers support using Git repositories directly, so you don't need pre-packaged sources.
|
||||
|
||||
Git no está diseñado para fungir como una herramienta de respaldo. Sin embargo, hay muchas soluciones diseñadas específicamente para realizar copias de seguridad, como [Arq](https://www.arqbackup.com/), [Carbonite](http://www.carbonite.com/) y [CrashPlan](https://www.crashplan.com/en-us/).
|
||||
Git is not designed to serve as a backup tool. However, there are many solutions specifically designed for performing backups, such as [Arq](https://www.arqbackup.com/), [Carbonite](http://www.carbonite.com/), and [CrashPlan](https://www.crashplan.com/en-us/).
|
||||
{% endif %}
|
||||
|
||||
## Eliminar archivos del historial de un repositorio
|
||||
## Removing files from a repository's history
|
||||
|
||||
{% warning %}
|
||||
|
||||
**Advertencia**: Estos procedimientos eliminarán archivos de manera permanente del repositorio de su equipo y de {% data variables.product.product_location %}. Si el archivo es importante, haz una copia de seguridad local en un directorio por fuera del repositorio.
|
||||
**Warning**: These procedures will permanently remove files from the repository on your computer and {% data variables.product.product_location %}. If the file is important, make a local backup copy in a directory outside of the repository.
|
||||
|
||||
{% endwarning %}
|
||||
|
||||
### Eliminar un archivo agregado en la confirmación más reciente no subida
|
||||
### Removing a file added in the most recent unpushed commit
|
||||
|
||||
Si el archivo se agregó con tu confirmación más reciente, y no lo subiste a {% data variables.product.product_location %}, puedes eliminar el archivo y modificar la confirmación:
|
||||
If the file was added with your most recent commit, and you have not pushed to {% data variables.product.product_location %}, you can delete the file and amend the commit:
|
||||
|
||||
{% data reusables.command_line.open_the_multi_os_terminal %} {% data reusables.command_line.switching_directories_procedural %}
|
||||
3. Para quitar el archivo, escriba `git rm --cached`:
|
||||
{% data reusables.command_line.open_the_multi_os_terminal %}
|
||||
{% data reusables.command_line.switching_directories_procedural %}
|
||||
3. To remove the file, enter `git rm --cached`:
|
||||
```shell
|
||||
$ git rm --cached <em>giant_file</em>
|
||||
$ git rm --cached GIANT_FILE
|
||||
# Stage our giant file for removal, but leave it on disk
|
||||
```
|
||||
4. Confirme este cambio con `--amend -CHEAD`:
|
||||
4. Commit this change using `--amend -CHEAD`:
|
||||
```shell
|
||||
$ git commit --amend -CHEAD
|
||||
# Amend the previous commit with your change
|
||||
# Simply making a new commit won't work, as you need
|
||||
# to remove the file from the unpushed history as well
|
||||
```
|
||||
5. Sube tus confirmaciones a {% data variables.product.product_location %}:
|
||||
5. Push your commits to {% data variables.product.product_location %}:
|
||||
```shell
|
||||
$ git push
|
||||
# Push our rewritten, smaller commit
|
||||
```
|
||||
|
||||
### Eliminar un archivo que se añadió en una confirmación de cambios previa
|
||||
### Removing a file that was added in an earlier commit
|
||||
|
||||
Si añadiste un archivo en una confirmación previa, necesitas eliminarlo del historial del repositorio. Para quitar archivos del historial del repositorio, puede usar BFG Repo-Cleaner o el comando `git filter-branch`. Para obtener más información, consulte "[Eliminación de datos confidenciales de un repositorio](/github/authenticating-to-github/removing-sensitive-data-from-a-repository)".
|
||||
If you added a file in an earlier commit, you need to remove it from the repository's history. To remove files from the repository's history, you can use the BFG Repo-Cleaner or the `git filter-branch` command. For more information see "[Removing sensitive data from a repository](/github/authenticating-to-github/removing-sensitive-data-from-a-repository)."
|
||||
|
||||
## Distribuir binarios grandes
|
||||
## Distributing large binaries
|
||||
|
||||
Si necesitas distribuir archivos grandes dentro de tu repositorio, puedes crear lanzamientos en {% data variables.product.product_location %}. Los lanzamientos te permiten empaquetar el software, notas de lanzamiento y enlaces a los archivos binarios para que otras personas puedan utilizarlos. Para obtener más información, consulte "[Acerca de las versiones](/github/administering-a-repository/about-releases)".
|
||||
If you need to distribute large files within your repository, you can create releases on {% data variables.product.product_location %}. Releases allow you to package software, release notes, and links to binary files, for other people to use. For more information, visit "[About releases](/github/administering-a-repository/about-releases)."
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
|
||||
No limitamos el tamaño total de los archivos binarios en los lanzamientos o anchos de banda que se utilizan para entregarlos. Sin embargo, cada archivo individual debe ser menor a {% data variables.large_files.max_lfs_size %}.
|
||||
We don't limit the total size of the binary files in the release or the bandwidth used to deliver them. However, each individual file must be smaller than {% data variables.large_files.max_lfs_size %}.
|
||||
|
||||
{% endif %}
|
||||
|
||||
|
||||
@@ -340,7 +340,7 @@ To view a fully interactive version of your Jupyter Notebook, you can set up a n
|
||||
If you're having trouble rendering Jupyter Notebook files in static HTML, you can convert the file locally on the command line by using the [`nbconvert` command](https://github.com/jupyter/nbconvert):
|
||||
|
||||
```shell
|
||||
$ jupyter nbconvert --to html <em>NOTEBOOK-NAME.ipynb</em>
|
||||
$ jupyter nbconvert --to html NOTEBOOK-NAME.ipynb
|
||||
```
|
||||
|
||||
### Further reading
|
||||
|
||||
@@ -163,7 +163,7 @@ With cURL, you will send an `Authorization` header with your token. Replace `YOU
|
||||
```shell
|
||||
curl --request GET \
|
||||
--url "https://api.github.com/octocat" \
|
||||
--header "Authorization: Bearer <em>YOUR-TOKEN</em>"
|
||||
--header "Authorization: Bearer YOUR-TOKEN"
|
||||
```
|
||||
|
||||
{% note %}
|
||||
@@ -326,7 +326,7 @@ To send a header with cURL, use the `--header` or `-H` flag followed by the head
|
||||
curl --request GET \
|
||||
--url "https://api.github.com/octocat" \
|
||||
--header "Accept: application/vnd.github.v3+json" \
|
||||
--header "Authorization: Bearer <em>YOUR-TOKEN</em>"
|
||||
--header "Authorization: Bearer YOUR-TOKEN"
|
||||
```
|
||||
|
||||
{% endcurl %}
|
||||
@@ -390,7 +390,7 @@ To get issues from the `octocat/Spoon-Knife` repository, replace `{owner}` with
|
||||
curl --request GET \
|
||||
--url "https://api.github.com/repos/octocat/Spoon-Knife/issues" \
|
||||
--header "Accept: application/vnd.github.v3+json" \
|
||||
--header "Authorization: Bearer <em>YOUR-TOKEN</em>"
|
||||
--header "Authorization: Bearer YOUR-TOKEN"
|
||||
```
|
||||
|
||||
{% endcurl %}
|
||||
@@ -443,7 +443,7 @@ For cURL, add a `?` to the end of the path, then append your query parameter nam
|
||||
curl --request GET \
|
||||
--url "https://api.github.com/repos/octocat/Spoon-Knife/issues?per_page=2&sort=updated&direction=asc" \
|
||||
--header "Accept: application/vnd.github.v3+json" \
|
||||
--header "Authorization: Bearer <em>YOUR-TOKEN</em>"
|
||||
--header "Authorization: Bearer YOUR-TOKEN"
|
||||
```
|
||||
|
||||
{% endcurl %}
|
||||
@@ -495,7 +495,7 @@ For cURL, use the `--data` flag to pass the body parameters in a JSON object.
|
||||
curl --request POST \
|
||||
--url "https://api.github.com/repos/octocat/Spoon-Knife/issues" \
|
||||
--header "Accept: application/vnd.github.v3+json" \
|
||||
--header "Authorization: Bearer <em>YOUR-TOKEN</em>" \
|
||||
--header "Authorization: Bearer YOUR-TOKEN" \
|
||||
--data '{
|
||||
"title": "Created with the REST API",
|
||||
"body": "This is a test issue created by the REST API"
|
||||
@@ -593,7 +593,7 @@ For example, this request:
|
||||
curl --request GET \
|
||||
--url "https://api.github.com/repos/octocat/Spoon-Knife/issues?per_page=2" \
|
||||
--header "Accept: application/vnd.github.v3+json" \
|
||||
--header "Authorization: Bearer <em>YOUR-TOKEN</em>" \
|
||||
--header "Authorization: Bearer YOUR-TOKEN" \
|
||||
--include
|
||||
```
|
||||
|
||||
@@ -661,7 +661,7 @@ await octokit.request("GET /repos/{owner}/{repo}/issues", {
|
||||
curl --request GET \
|
||||
--url "https://api.github.com/repos/octocat/Spoon-Knife/issues?per_page=2" \
|
||||
--header "Accept: application/vnd.github.v3+json" \
|
||||
--header "Authorization: Bearer <em>YOUR-TOKEN</em>"
|
||||
--header "Authorization: Bearer YOUR-TOKEN"
|
||||
```
|
||||
|
||||
{% endcurl %}
|
||||
@@ -730,7 +730,7 @@ For example, you can use `>` to redirect the response to a file:
|
||||
curl --request GET \
|
||||
--url "https://api.github.com/repos/octocat/Spoon-Knife/issues?per_page=2" \
|
||||
--header "Accept: application/vnd.github.v3+json" \
|
||||
--header "Authorization: Bearer <em>YOUR-TOKEN</em>" > data.json
|
||||
--header "Authorization: Bearer YOUR-TOKEN" > data.json
|
||||
```
|
||||
|
||||
Then you can use jq to get the title and author ID of each issue:
|
||||
|
||||
File diff suppressed because it is too large
Load Diff
@@ -268,7 +268,7 @@ You can filter pull requests based on their [review status](/pull-requests/colla
|
||||
| <code>reviewed-by:<em>USERNAME</em></code> | [**type:pr reviewed-by:gjtorikian**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+reviewed-by%3Agjtorikian&type=Issues) matches pull requests reviewed by a particular person.
|
||||
| <code>review-requested:<em>USERNAME</em></code> | [**type:pr review-requested:benbalter**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+review-requested%3Abenbalter&type=Issues) matches pull requests where a specific person is requested for review. Requested reviewers are no longer listed in the search results after they review a pull request. If the requested person is on a team that is requested for review, then review requests for that team will also appear in the search results.{% ifversion fpt or ghae or ghes > 3.2 or ghec %}
|
||||
| <code>user-review-requested:@me</code> | [**type:pr user-review-requested:@me**](https://github.com/search?q=is%3Apr+user-review-requested%3A%40me+) matches pull requests that you have directly been asked to review.{% endif %}
|
||||
| <code>team-review-requested:<em>TEAMNAME</em></code> | [**type:pr team-review-requested:atom/design**](https://github.com/search?q=type%3Apr+team-review-requested%3Aatom%2Fdesign&type=Issues) matches pull requests that have review requests from the team `atom/design`. Requested reviewers are no longer listed in the search results after they review a pull request.
|
||||
| <code>team-review-requested:<em>TEAMNAME</em></code> | [**type:pr team-review-requested:github/docs**](https://github.com/search?q=type%3Apr+team-review-requested%3Agithub%2Fdocs&type=pullrequests) matches pull requests that have review requests from the team `github/docs`. Requested reviewers are no longer listed in the search results after they review a pull request.
|
||||
|
||||
## Search by when an issue or pull request was created or last updated
|
||||
|
||||
|
||||
@@ -1,9 +0,0 @@
|
||||
---
|
||||
ms.openlocfilehash: ad73c4455042d29d72d3f76dbbdc512487c9303a
|
||||
ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: es-ES
|
||||
ms.lasthandoff: 09/05/2022
|
||||
ms.locfileid: "146139476"
|
||||
---
|
||||
Para ver ejemplos que demuestren características más complejas de {% data variables.product.prodname_actions %}, consulta "[Ejemplos](/actions/examples)". Para ver ejemplos detallados que explican cómo probar el código en un ejecutor, accede a la CLI de {% data variables.product.prodname_dotcom %} y usa características avanzadas, como la simultaneidad y las matrices de prueba.
|
||||
@@ -1,9 +0,0 @@
|
||||
---
|
||||
ms.openlocfilehash: 5cbe77b1e8580e79c7e77b99de3e1973191d2075
|
||||
ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: es-ES
|
||||
ms.lasthandoff: 09/10/2022
|
||||
ms.locfileid: "147879335"
|
||||
---
|
||||
Si establece el permiso de metadatos en `No access` y selecciona un permiso que necesita acceso al repositorio, GitHub invalidará la selección y volverá a establecer el permiso de metadatos en `Read-only`. Para establecer el permiso de metadatos en `No access`, primero debe establecer en `No access` todos los permisos que necesiten acceso al repositorio.
|
||||
@@ -15,6 +15,8 @@ After you connect your account on {% data variables.product.product_location %}
|
||||
|
||||
|
||||
|
||||
If codespaces are billable for the repository you choose, a message will be displayed in subsequent prompts telling you who will pay for the codespace.
|
||||
|
||||
4. Click the branch you want to develop on.
|
||||
|
||||
|
||||
|
||||
@@ -1,27 +1,22 @@
|
||||
---
|
||||
ms.openlocfilehash: 5120f840aab87ca243eed66c5bb6256e80aefeea
|
||||
ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: es-ES
|
||||
ms.lasthandoff: 09/05/2022
|
||||
ms.locfileid: "147064182"
|
||||
---
|
||||
{% ifversion fpt or ghec %}De manera predeterminada, recibirás notificaciones:{% endif %}{% ifversion ghes or ghae %}De manera predeterminada, si el propietario de tu empresa ha configurado las notificaciones por correo electrónico en tu instancia, recibirás {% data variables.product.prodname_dependabot_alerts %}:{% endif %}
|
||||
{% ifversion fpt or ghec %}By default, you will receive notifications:{% endif %}{% ifversion ghes or ghae %}By default, if your enterprise owner has configured email for notifications on your instance, you will receive {% data variables.product.prodname_dependabot_alerts %}:{% endif %}
|
||||
|
||||
- por correo electrónico, se enviará un mensaje de correo electrónico cuando se habilite {% data variables.product.prodname_dependabot %} para un repositorio, cuando se confirme un archivo de manifiesto nuevo en el repositorio y cuando se encuentre una vulnerabilidad nueva de gravedad crítica o alta (la opción **Email each time a vulnerability is found**).
|
||||
- en la interfaz de usuario, se muestra una advertencia en las vistas de archivos y código del repositorio si hay dependencias no seguras (opción **Alertas de la interfaz de usuario**).
|
||||
- en la línea de comandos, las advertencias se muestran como devoluciones de llamada al insertar en repositorios con dependencias no seguras (opción **Línea de comandos**).
|
||||
- en la bandeja de entrada, como notificaciones web. Se enviará una notificación web cuando se habilite {% data variables.product.prodname_dependabot %} en un repositorio, cuando se confirme un archivo de manifiesto nuevo en el repositorio y cuando se encuentre una vulnerabilidad nueva con gravedad crítica o alta (la opción **Web**).{% ifversion not ghae %}
|
||||
- en {% data variables.product.prodname_mobile %}, como notificaciones web. Para más información, vea ["Habilitación de notificaciones de inserción con GitHub Mobile](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#enabling-push-notifications-with-github-mobile)".{% endif %}
|
||||
- by email, an email is sent when {% data variables.product.prodname_dependabot %} is enabled for a repository, when a new manifest file is committed to the repository, and when a new vulnerability with a critical or high severity is found (**Email each time a vulnerability is found** option).
|
||||
- in the user interface, a warning is shown in your repository's file and code views if there are any insecure dependencies (**UI alerts** option).
|
||||
- on the command line, warnings are displayed as callbacks when you push to repositories with any insecure dependencies (**Command Line** option).
|
||||
- in your inbox, as web notifications. A web notification is sent when {% data variables.product.prodname_dependabot %} is enabled for a repository, when a new manifest file is committed to the repository, and when a new vulnerability with a critical or high severity is found (**Web** option).{% ifversion not ghae %}
|
||||
- on {% data variables.product.prodname_mobile %}, as web notifications. For more information, see "[Enabling push notifications with GitHub Mobile](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#enabling-push-notifications-with-github-mobile)."{% endif %}
|
||||
|
||||
{% note %}
|
||||
|
||||
**Nota:** Las notificaciones por correo electrónico y web{% ifversion not ghae %}/{% data variables.product.prodname_mobile %}{% endif %} son las siguientes:
|
||||
**Note:** The email and web{% ifversion not ghae %}/{% data variables.product.prodname_mobile %}{% endif %} notifications are:
|
||||
|
||||
- _por repositorio_ cuando {% data variables.product.prodname_dependabot %} se habilita en el repositorio o cuando se confirma un archivo de manifiesto nuevo en el repositorio.
|
||||
- _per repository_ when {% data variables.product.prodname_dependabot %} is enabled on the repository, or when a new manifest file is committed to the repository.
|
||||
|
||||
- _por organización_ cuando se descubre una vulnerabilidad nueva.
|
||||
- _per organization_ when a new vulnerability is discovered.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
Puede personalizar la forma en que recibe notificaciones sobre {% data variables.product.prodname_dependabot_alerts %}. Por ejemplo, puede recibir un correo electrónico semanal con el resumen de las alertas de hasta 10 de los repositorios mediante las opciones **Email a digest summary of vulnerabilities** y **Weekly security email digest**.
|
||||
{% ifversion update-notification-settings-22 %}
|
||||
You can customize the way you are notified about {% data variables.product.prodname_dependabot_alerts %}. For example, you can receive a daily or weekly digest email summarizing alerts for up to 10 of your repositories using the **Email weekly digest** option.
|
||||
{% else %}
|
||||
You can customize the way you are notified about {% data variables.product.prodname_dependabot_alerts %}. For example, you can receive a weekly digest email summarizing alerts for up to 10 of your repositories using the **Email a digest summary of vulnerabilities** and **Weekly security email digest** options.{% endif %}
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: サブスクリプションを表示する
|
||||
intro: 通知の送信元と通知のボリュームを把握するため、定期的にサブスクリプションを確認し、リポジトリを Watch することをお勧めします。
|
||||
title: Viewing your subscriptions
|
||||
intro: 'To understand where your notifications are coming from and your notifications volume, we recommend reviewing your subscriptions and watched repositories regularly.'
|
||||
redirect_from:
|
||||
- /articles/subscribing-to-conversations
|
||||
- /articles/unsubscribing-from-conversations
|
||||
@@ -24,63 +24,61 @@ versions:
|
||||
topics:
|
||||
- Notifications
|
||||
shortTitle: View subscriptions
|
||||
ms.openlocfilehash: 34faad79004d34f5beb14e8992b9aff4e6a3ab39
|
||||
ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: ja-JP
|
||||
ms.lasthandoff: 09/10/2022
|
||||
ms.locfileid: '145117238'
|
||||
---
|
||||
{% data variables.product.product_name %} で進行中のアクティビティのサブスクリプションの通知を受け取ります。 会話をサブスクライブする理由はたくさんあります。 詳細については、「[通知について](/github/managing-subscriptions-and-notifications-on-github/about-notifications#notifications-and-subscriptions)」を参照してください。
|
||||
You receive notifications for your subscriptions of ongoing activity on {% data variables.product.product_name %}. There are many reasons you can be subscribed to a conversation. For more information, see "[About notifications](/github/managing-subscriptions-and-notifications-on-github/about-notifications#notifications-and-subscriptions)."
|
||||
|
||||
健全な通知ワークフローの一環として、サブスクリプションの監査とサブスクライブ解除をお勧めします。 登録解除のオプションの詳細については、「[サブスクリプションの管理」を](/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions)参照してください。
|
||||
We recommend auditing and unsubscribing from your subscriptions as a part of a healthy notifications workflow. For more information about your options for unsubscribing, see "[Managing subscriptions](/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions)."
|
||||
|
||||
## 通知過多の理由を診断する
|
||||
## Diagnosing why you receive too many notifications
|
||||
|
||||
インボックスの通知が多すぎて管理できない場合は、サブスクリプションが多すぎないか確認したり、通知設定を変更して、サブスクリプションと受信する通知の種類を減らしたりすることを検討してください。 たとえば、設定を無効にして、チームまたはリポジトリに参加するたびにすべてのリポジトリとすべての Team ディスカッションを自動的に監視することを検討できます。
|
||||
When your inbox has too many notifications to manage, consider whether you have oversubscribed or how you can change your notification settings to reduce the subscriptions you have and the types of notifications you're receiving. For example, you may consider disabling the settings to automatically watch all repositories and all team discussions whenever you've joined a team or repository.
|
||||
|
||||
|
||||
{% ifversion update-notification-settings-22 %}
|
||||
|
||||
{% else %}
|
||||
{% endif %}
|
||||
|
||||
詳細については、「[通知の設定](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#automatic-watching)」を参照してください。
|
||||
For more information, see "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#automatic-watching)."
|
||||
|
||||
リポジトリのサブスクリプションの概要を確認するには、「[Watch しているリポジトリを確認する](#reviewing-repositories-that-youre-watching)」を参照してください。 {% tip %}
|
||||
To see an overview of your repository subscriptions, see "[Reviewing repositories that you're watching](#reviewing-repositories-that-youre-watching)."
|
||||
{% tip %}
|
||||
|
||||
**ヒント:** 通知するイベントの種類を選択するには、**監視ページ** の **[Watch/Watch 解除]** ドロップダウン リストの [[カスタム]](https://github.com/watching) オプションを使用するか、{% data variables.product.product_name %} の任意のリポジトリ ページを使用します。 詳細については、「[通知の設定](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#configuring-your-watch-settings-for-an-individual-repository)」を参照してください。
|
||||
**Tip:** You can select the types of event to be notified of by using the **Custom** option of the **Watch/Unwatch** dropdown list in your [watching page](https://github.com/watching) or on any repository page on {% data variables.product.product_name %}. For more information, see "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#configuring-your-watch-settings-for-an-individual-repository)."
|
||||
|
||||
{% endtip %}
|
||||
|
||||
過去に Watch することを選択したリポジトリが忘れらていることが多くあります。 「Watched repositories」ページから、リポジトリから素早く Watch 解除することができます。 サブスクライブ解除する方法について詳しくは、{% data variables.product.prodname_blog %} の「[Watch 解除の推奨](https://github.blog/changelog/2020-11-10-unwatch-recommendations/)」および「[サブスクリプションを管理する](/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions)」を参照してください。 トリアージワークフローを作成して、受信する通知を支援することもできます。 トリアージ ワークフローのガイダンスについては、「[通知をトリアージするためのワークフローのカスタマイズ](/github/managing-subscriptions-and-notifications-on-github/customizing-a-workflow-for-triaging-your-notifications)」を参照してください。
|
||||
Many people forget about repositories that they've chosen to watch in the past. From the "Watched repositories" page you can quickly unwatch repositories. For more information on ways to unsubscribe, see "[Unwatch recommendations](https://github.blog/changelog/2020-11-10-unwatch-recommendations/)" on {% data variables.product.prodname_blog %} and "[Managing your subscriptions](/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions)." You can also create a triage workflow to help with the notifications you receive. For guidance on triage workflows, see "[Customizing a workflow for triaging your notifications](/github/managing-subscriptions-and-notifications-on-github/customizing-a-workflow-for-triaging-your-notifications)."
|
||||
|
||||
## サブスクリプションのリストを確認する
|
||||
## Reviewing all of your subscriptions
|
||||
|
||||
{% data reusables.notifications.access_notifications %}
|
||||
1. 左側のサイドバーの、通知元のリポジトリリストの下にある [通知の管理] ドロップダウンを使用して、 **[サブスクリプション]** をクリックします。
|
||||
![[通知の管理] ドロップダウン メニュー オプション](/assets/images/help/notifications-v2/manage-notifications-options.png)
|
||||
1. In the left sidebar, under the list of repositories that you have notifications from, use the "Manage notifications" drop-down to click **Subscriptions**.
|
||||
|
||||
|
||||
2. フィルタとソートを使用して、サブスクリプションのリストを絞り込み、通知の受信を希望しない会話のサブスクリプションを解除します。
|
||||
2. Use the filters and sort to narrow the list of subscriptions and begin unsubscribing to conversations you no longer want to receive notifications for.
|
||||
|
||||
|
||||
|
||||
|
||||
{% tip %}
|
||||
|
||||
**ヒント:**
|
||||
- 忘れている可能性のあるサブスクリプションを確認するには、[least recently subscribed] でソートします。
|
||||
**Tips:**
|
||||
- To review subscriptions you may have forgotten about, sort by "least recently subscribed."
|
||||
|
||||
- 引き続き通知が受信可能なリポジトリのリストを確認するには、[filter by repository] ドロップダウンメニューのリポジトリリストを参照します。
|
||||
- To review a list of repositories that you can still receive notifications for, see the repository list in the "filter by repository" drop-down menu.
|
||||
|
||||
{% endtip %}
|
||||
|
||||
## Watch しているリポジトリを確認する
|
||||
## Reviewing repositories that you're watching
|
||||
|
||||
1. 左側のサイドバーの、リポジトリ リストの下にある [通知の管理] ドロップダウン メニューを使用して、 **[Watched repositories]** をクリックします。
|
||||
![[通知の管理] ドロップダウン メニュー オプション](/assets/images/help/notifications-v2/manage-notifications-options.png)
|
||||
2. Watch しているリポジトリを評価し、それらの更新がまだ関連していて有用であるかどうかを判断します。 リポジトリを Watch すると、そのリポジトリのすべての会話が通知されます。
|
||||
|
||||
1. In the left sidebar, under the list of repositories, use the "Manage notifications" drop-down menu and click **Watched repositories**.
|
||||
|
||||
2. Evaluate the repositories that you are watching and decide if their updates are still relevant and helpful. When you watch a repository, you will be notified of all conversations for that repository.
|
||||
|
||||
|
||||
{% tip %}
|
||||
|
||||
**ヒント:** リポジトリを監視する代わりに、{% data reusables.notifications-v2.custom-notification-types %} (リポジトリで有効になっている場合) の更新がある場合、またはこれらのオプションの任意の組み合わせがある場合にのみ通知を受信するか、リポジトリの監視を完全に解除することを検討してください。
|
||||
**Tip:** Instead of watching a repository, consider only receiving notifications when there are updates to {% data reusables.notifications-v2.custom-notification-types %} (if enabled for the repository), or any combination of these options, or completely unwatching a repository.
|
||||
|
||||
リポジトリの Watch を解除しても、@mentioned されたときやスレッドに参加しているときには通知を受信することができます。 特定のイベント タイプの通知を受信するように設定すると、リポジトリにこれらのイベント タイプが更新された場合、スレッドに参加している場合、または参加している自分またはチームが @mentioned された場合にのみ通知されます。
|
||||
When you unwatch a repository, you can still be notified when you're @mentioned or participating in a thread. When you configure to receive notifications for certain event types, you're only notified when there are updates to these event types in the repository, you're participating in a thread, or you or a team you're on is @mentioned.
|
||||
|
||||
{% endtip %}
|
||||
|
||||
@@ -79,15 +79,27 @@ You can customize notifications for a repository. For example, you can choose to
|
||||
### Participating in conversations
|
||||
Anytime you comment in a conversation or when someone @mentions your username, you are _participating_ in a conversation. By default, you are automatically subscribed to a conversation when you participate in it. You can unsubscribe from a conversation you've participated in manually by clicking **Unsubscribe** on the issue or pull request or through the **Unsubscribe** option in the notifications inbox.
|
||||
|
||||
For conversations you're watching or participating in, you can choose whether you want to receive notifications by email or through the notifications inbox on {% data variables.product.product_location %}{% ifversion fpt or ghes or ghec %} and {% data variables.product.prodname_mobile %}{% endif %}.
|
||||
{% ifversion update-notification-settings-22 %}For conversations you're watching or participating in, you can choose whether you want to receive notifications on {% data variables.product.company_short %} or by email in your notification settings. For more information, see "[Choosing your notification settings](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications#choosing-your-notification-settings)."
|
||||
|
||||
|
||||
|
||||
{% else %}
|
||||
|
||||
For conversations you're watching or participating in, you can choose whether you want to receive notifications by email or through the notifications inbox on {% data variables.product.product_location %}{% ifversion ghes %} and {% data variables.product.prodname_mobile %}{% endif %}. For more information, see "[Choosing your notification settings](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications#choosing-your-notification-settings)."
|
||||
|
||||
{% endif %}
|
||||
|
||||
|
||||
|
||||
|
||||
For example:
|
||||
- If you don't want notifications to be sent to your email, unselect **email** for participating and watching notifications.
|
||||
- If you want to receive notifications by email when you've participated in a conversation, then you can select **email** under "Participating".
|
||||
|
||||
If you do not enable watching or participating notifications for web{% ifversion fpt or ghes or ghec %} and mobile{% endif %}, then your notifications inbox will not have any updates.
|
||||
{% ifversion update-notification-settings-22 %}If you do not enable "Notify me: On GitHub" for watching or participating notifications, then your notifications inbox will not have any updates.
|
||||
|
||||
{% else %}
|
||||
|
||||
If you do not enable watching or participating notifications for web{% ifversion ghes %} and mobile{% endif %}, then your notifications inbox will not have any updates.{% endif %}
|
||||
|
||||
## Customizing your email notifications
|
||||
|
||||
@@ -146,11 +158,16 @@ Email notifications from {% data variables.product.product_location %} contain t
|
||||
|
||||
## Automatic watching
|
||||
|
||||
By default, anytime you gain access to a new repository, you will automatically begin watching that repository. Anytime you join a new team, you will automatically be subscribed to updates and receive notifications when that team is @mentioned. If you don't want to automatically be subscribed, you can unselect the automatic watching options.
|
||||
By default, anytime you gain access to a new repository, you will automatically begin watching that repository. Anytime you join a new team, you will automatically be subscribed to updates and receive notifications when that team is @mentioned. If you don't want to automatically be subscribed, you can unselect the automatic watching options in your notification settings.
|
||||
|
||||
|
||||
{% ifversion update-notification-settings-22 %}
|
||||
|
||||
{% else %}
|
||||
{% endif %}
|
||||
|
||||
If "Automatically watch repositories" is disabled, then you will not automatically watch your own repositories. You must navigate to your repository page and choose the watch option.
|
||||
If "Automatically watch repositories" is disabled, then you will not automatically watch your own repositories. You must navigate to your repository page and choose the watch option.
|
||||
|
||||
For more information, see "[Choosing your notification settings](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications#choosing-your-notification-settings)."
|
||||
|
||||
## Configuring your watch settings for an individual repository
|
||||
|
||||
@@ -172,9 +189,17 @@ If you belong to an organization, you can choose the email account you want noti
|
||||
|
||||
{% data reusables.notifications.access_notifications %}
|
||||
{% data reusables.notifications-v2.manage-notifications %}
|
||||
|
||||
3. Under "Default notification email", select the email address you'd like notifications sent to.
|
||||
|
||||
4. Click **Save**.
|
||||
{% ifversion update-notification-settings-22 %}
|
||||
|
||||
|
||||
|
||||
{% else %}
|
||||
|
||||
{% endif %}
|
||||
{% ifversion ghes or ghae %}
|
||||
4. Click **Save**.{% endif %}
|
||||
|
||||
### Customizing email routes per organization
|
||||
|
||||
@@ -182,12 +207,35 @@ If you are a member of more than one organization, you can configure each one to
|
||||
|
||||
{% data reusables.notifications.access_notifications %}
|
||||
{% data reusables.notifications-v2.manage-notifications %}
|
||||
3. Under "Custom routing," find your organization's name in the list.
|
||||
|
||||
{% ifversion update-notification-settings-22 %}
|
||||
3. Under "Default notifications email", click **Custom routing**.
|
||||
|
||||
|
||||
|
||||
4. Click **Add new route**.
|
||||
|
||||
|
||||
|
||||
5. Click **Pick organization**, then select the organization you want to customize from the dropdown.
|
||||
|
||||
|
||||
|
||||
6. Select one of your verified email addresses, then click **Save**.
|
||||
|
||||
|
||||
|
||||
{% else %}
|
||||
3. Under "Custom routing," find your organization's name in the list.
|
||||
|
||||
|
||||
|
||||
4. Click **Edit** next to the email address you want to change.
|
||||
|
||||
|
||||
|
||||
|
||||
5. Select one of your verified email addresses, then click **Save**.
|
||||
|
||||
|
||||
{% endif %}
|
||||
|
||||
## {% data variables.product.prodname_dependabot_alerts %} notification options
|
||||
|
||||
@@ -197,14 +245,17 @@ If you are a member of more than one organization, you can configure each one to
|
||||
|
||||
For more information about the notification delivery methods available to you, and advice on optimizing your notifications for {% data variables.product.prodname_dependabot_alerts %}, see "[Configuring notifications for {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/configuring-notifications-for-dependabot-alerts)."
|
||||
|
||||
{% ifversion fpt or ghes or ghec %}
|
||||
{% ifversion update-notification-settings-22 or ghes %}
|
||||
## {% data variables.product.prodname_actions %} notification options
|
||||
|
||||
Choose how you want to receive workflow run updates for repositories that you are watching that are set up with {% data variables.product.prodname_actions %}. You can also choose to only receive notifications for failed workflow runs.
|
||||
Choose how you want to receive workflow run updates for repositories that you are watching that are set up with {% data variables.product.prodname_actions %}. You can also choose to only receive notifications for failed workflow runs.{% endif %}
|
||||
|
||||
|
||||
{% ifversion update-notification-settings-22 %}
|
||||
{% endif %}
|
||||
|
||||
{% ifversion ghes %}
|
||||
{% endif %}
|
||||
|
||||
{% endif %}
|
||||
|
||||
{% ifversion fpt or ghec or ghes > 3.3 or ghae > 3.3 %}
|
||||
## Organization alerts notification options
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: プロフィールの README を管理する
|
||||
intro: '{% data variables.product.prodname_dotcom %} プロフィールに README を追加して、他のユーザに自分の情報を伝えることができます。'
|
||||
title: Managing your profile README
|
||||
intro: 'You can add a README to your {% data variables.product.prodname_dotcom %} profile to tell other people about yourself.'
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
@@ -11,71 +11,67 @@ redirect_from:
|
||||
- /github/setting-up-and-managing-your-github-profile/managing-your-profile-readme
|
||||
- /github/setting-up-and-managing-your-github-profile/customizing-your-profile/managing-your-profile-readme
|
||||
shortTitle: Your profile README
|
||||
ms.openlocfilehash: 587bcea1e1a0f96aad8882b41196afcc6e433363
|
||||
ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: ja-JP
|
||||
ms.lasthandoff: 09/05/2022
|
||||
ms.locfileid: '147578901'
|
||||
---
|
||||
## プロフィール README について
|
||||
## About your profile README
|
||||
|
||||
プロフィール README を作成すると、{% data variables.product.product_location %} で自分に関する情報をコミュニティと共有できます。 {% data variables.product.prodname_dotcom %} では、プロフィールページの上部にプロフィール README が表示されます。
|
||||
You can share information about yourself with the community on {% data variables.product.product_location %} by creating a profile README. {% data variables.product.prodname_dotcom %} shows your profile README at the top of your profile page.
|
||||
|
||||
プロフィール README に含める情報を決めることができるため、{% data variables.product.prodname_dotcom %} で自分に関するどのような情報を表示するかを完全に制御できます。 アクセスしたユーザがあなたのプロフィール README を見て、興味深い、楽しい、役立つと感じる可能性のある情報の例は次のとおりです。
|
||||
You decide what information to include in your profile README, so you have full control over how you present yourself on {% data variables.product.prodname_dotcom %}. Here are some examples of information that visitors may find interesting, fun, or useful in your profile README.
|
||||
|
||||
- あなたの仕事や興味について説明した「自己紹介」セクション
|
||||
- あなたが誇りに思っているコントリビューションとそれらのコントリビューションについてのコンテキスト
|
||||
- あなたが関連しているコミュニティでサポートを得るためのガイド
|
||||
- An "About me" section that describes your work and interests
|
||||
- Contributions you're proud of, and context about those contributions
|
||||
- Guidance for getting help in communities where you're involved
|
||||
|
||||
|
||||
|
||||
|
||||
{% data variables.product.company_short %} Flavored Markdown を使用して、テキストをフォーマットし、絵文字、画像、GIF をプロフィール README に含めることができます。 詳細については、「[{% data variables.product.prodname_dotcom %} での書き込みと書式設定の概要](/github/writing-on-github/getting-started-with-writing-and-formatting-on-github)」を参照してください。
|
||||
You can format text and include emoji, images, and GIFs in your profile README by using {% data variables.product.company_short %} Flavored Markdown. For more information, see "[Getting started with writing and formatting on {% data variables.product.prodname_dotcom %}](/github/writing-on-github/getting-started-with-writing-and-formatting-on-github)." For a hands-on guide to customizing your profile README, see "[Quickstart for writing on {% data variables.product.prodname_dotcom %}](/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/quickstart-for-writing-on-github)."
|
||||
|
||||
## 前提条件
|
||||
## Prerequisites
|
||||
|
||||
次のすべてが当てはまる場合、GitHubは プロフィールページにプロフィール README を表示します。
|
||||
GitHub will display your profile README on your profile page if all of the following are true.
|
||||
|
||||
- {% data variables.product.prodname_dotcom %} ユーザ名にマッチする名前のリポジトリを作成した。
|
||||
- リポジトリがパブリックである。
|
||||
- リポジトリのルートに README.md という名前のファイルが含まれている。
|
||||
- README.md ファイルに任意のコンテンツが含まれている。
|
||||
- You've created a repository with a name that matches your {% data variables.product.prodname_dotcom %} username.
|
||||
- The repository is public.
|
||||
- The repository contains a file named README.md in its root.
|
||||
- The README.md file contains any content.
|
||||
|
||||
{% note %}
|
||||
|
||||
**注**: 2020 年 7 月以前にユーザー名と同名のパブリック リポジトリを作成していた場合、{% data variables.product.prodname_dotcom %} のプロフィールにはリポジトリの README が自動的に表示されません。 {% data variables.product.prodname_dotcom_the_website %} のリポジトリに移動して、 **[プロフィールで共有]** をクリックすると、リポジトリの README をプロフィールで手動で共有できます。
|
||||
**Note**: If you created a public repository with the same name as your username before July 2020, {% data variables.product.prodname_dotcom %} won't automatically show the repository's README on your profile. You can manually share the repository's README to your profile by going to the repository on {% data variables.product.prodname_dotcom_the_website %} and clicking **Share to profile**.
|
||||
|
||||
|
||||
|
||||
|
||||
{% endnote %}
|
||||
|
||||
## プロフィールの README を追加する
|
||||
## Adding a profile README
|
||||
|
||||
{% data reusables.repositories.create_new %}
|
||||
2. [Repository name] の下に、{% data variables.product.prodname_dotcom %} のユーザ名とマッチするリポジトリ名を入力します。 たとえば、ユーザ名が「octocat」の場合、リポジトリ名は「octocat」である必要があります。
|
||||
![ユーザー名に一致する [リポジトリ名] フィールド](/assets/images/help/repository/repo-username-match.png)
|
||||
3. 必要に応じて、リポジトリの説明を追加します。 たとえば、「個人リポジトリ」などです。
|
||||
|
||||
4. **[パブリック]** を選択します。
|
||||
![可視性を選択するためのオプション ボタン ([パブリック] が選択された状態)](/assets/images/help/repository/create-personal-repository-visibility.png) {% data reusables.repositories.initialize-with-readme %} {% data reusables.repositories.create-repo %}
|
||||
7. 右側のサイドバーの上にある **[README の編集]** をクリックします。
|
||||
|
||||
2. Under "Repository name", type a repository name that matches your {% data variables.product.prodname_dotcom %} username. For example, if your username is "octocat", the repository name must be "octocat".
|
||||
|
||||
3. Optionally, add a description of your repository. For example, "My personal repository."
|
||||
|
||||
4. Select **Public**.
|
||||
|
||||
{% data reusables.repositories.initialize-with-readme %}
|
||||
{% data reusables.repositories.create-repo %}
|
||||
7. Above the right sidebar, click **Edit README**.
|
||||
|
||||
|
||||
生成された README ファイルには、プロフィール README のアイディアを得るためのテンプレートが事前入力されています。
|
||||
|
||||
The generated README file is pre-populated with a template to give you some inspiration for your profile README.
|
||||
|
||||
|
||||
使用できるすべての絵文字とそのコードの概要については、[絵文字のチート シート](https://www.webfx.com/tools/emoji-cheat-sheet/)を参照してください。
|
||||
For a summary of all the available emojis and their codes, see "[Emoji cheat sheet](https://www.webfx.com/tools/emoji-cheat-sheet/)."
|
||||
|
||||
## プロフィール README を削除する
|
||||
## Removing a profile README
|
||||
|
||||
次のいずれかに該当する場合、プロフィール README は {% data variables.product.prodname_dotcom %} のプロフィールから削除されます。
|
||||
The profile README is removed from your {% data variables.product.prodname_dotcom %} profile if any of the following apply:
|
||||
|
||||
- README ファイルが空であるか、存在しない。
|
||||
- リポジトリがプライベートである。
|
||||
- リポジトリ名がユーザ名とマッチしなくなった。
|
||||
- The README file is empty or doesn't exist.
|
||||
- The repository is private.
|
||||
- The repository name no longer matches your username.
|
||||
|
||||
The method you choose is dependant upon your needs, but if you're unsure, we recommend making your repository private. リポジトリをプライベートにする方法については、「[リポジトリの可視性を変更する](/github/administering-a-repository/setting-repository-visibility#changing-a-repositorys-visibility)」を参照してください。
|
||||
The method you choose depends upon your needs, but if you're unsure, we recommend making your repository private. For steps on how to make your repository private, see "[Changing a repository's visibility](/github/administering-a-repository/setting-repository-visibility#changing-a-repositorys-visibility)."
|
||||
|
||||
## 参考資料
|
||||
## Further reading
|
||||
|
||||
- [README について](/github/creating-cloning-and-archiving-repositories/about-readmes)
|
||||
- [About READMEs](/github/creating-cloning-and-archiving-repositories/about-readmes)
|
||||
|
||||
@@ -1,5 +1,6 @@
|
||||
---
|
||||
title: Creating a JavaScript action
|
||||
shortTitle: Create a JavaScript action
|
||||
intro: 'In this guide, you''ll learn how to build a JavaScript action using the actions toolkit.'
|
||||
redirect_from:
|
||||
- /articles/creating-a-javascript-action
|
||||
@@ -15,7 +16,6 @@ type: tutorial
|
||||
topics:
|
||||
- Action development
|
||||
- JavaScript
|
||||
shortTitle: JavaScript action
|
||||
---
|
||||
|
||||
{% data reusables.actions.enterprise-beta %}
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Releasing and maintaining actions
|
||||
shortTitle: Releasing and maintaining actions
|
||||
shortTitle: Release and maintain actions
|
||||
intro: You can leverage automation and open source best practices to release and maintain actions.
|
||||
type: tutorial
|
||||
topics:
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Configuring OpenID Connect in HashiCorp Vault
|
||||
shortTitle: Configuring OpenID Connect in HashiCorp Vault
|
||||
shortTitle: OpenID Connect in HashiCorp Vault
|
||||
intro: Use OpenID Connect within your workflows to authenticate with HashiCorp Vault.
|
||||
miniTocMaxHeadingLevel: 3
|
||||
versions:
|
||||
|
||||
@@ -1,5 +1,6 @@
|
||||
---
|
||||
title: Autoscaling with self-hosted runners
|
||||
shortTitle: Autoscale self-hosted runners
|
||||
intro: You can automatically scale your self-hosted runners in response to webhook events.
|
||||
versions:
|
||||
fpt: '*'
|
||||
@@ -63,7 +64,7 @@ By default, self-hosted runners will automatically perform a software update whe
|
||||
To turn off automatic software updates and install software updates yourself, specify the `--disableupdate` flag when registering your runner using `config.sh`. For example:
|
||||
|
||||
```shell
|
||||
./config.sh --url <em>https://github.com/octo-org</em> --token <em>example-token</em> --disableupdate
|
||||
./config.sh --url https://github.com/YOUR-ORGANIZATION --token EXAMPLE-TOKEN --disableupdate
|
||||
```
|
||||
|
||||
If you disable automatic updates, you must still update your runner version regularly. New functionality in {% data variables.product.prodname_actions %} requires changes in both the {% data variables.product.prodname_actions %} service _and_ the runner software. The runner may not be able to correctly process jobs that take advantage of new features in {% data variables.product.prodname_actions %} without a software update.
|
||||
|
||||
@@ -59,7 +59,7 @@ For example:
|
||||
{% windows %}
|
||||
|
||||
```shell
|
||||
run.cmd --check --url <em>https://github.com/octo-org/octo-repo</em> --pat <em>ghp_abcd1234</em>
|
||||
run.cmd --check --url https://github.com/YOUR-ORG/YOUR-REPO --pat GHP_ABCD1234
|
||||
```
|
||||
|
||||
{% endwindows %}
|
||||
@@ -79,7 +79,7 @@ To disable TLS certification verification in the self-hosted runner application,
|
||||
|
||||
```shell
|
||||
export GITHUB_ACTIONS_RUNNER_TLS_NO_VERIFY=1
|
||||
./config.sh --url <em>https://github.com/octo-org/octo-repo</em> --token
|
||||
./config.sh --url https://github.com/YOUR-ORG/YOUR-REPO --token
|
||||
./run.sh
|
||||
```
|
||||
|
||||
|
||||
@@ -201,7 +201,7 @@ The `github` context contains information about the workflow run and the event t
|
||||
| `github.ref` | `string` | {% data reusables.actions.ref-description %} |
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 or ghae > 3.3 %}
|
||||
| `github.ref_name` | `string` | {% data reusables.actions.ref_name-description %} |
|
||||
| `github.ref_protected` | `string` | {% data reusables.actions.ref_protected-description %} |
|
||||
| `github.ref_protected` | `boolean` | {% data reusables.actions.ref_protected-description %} |
|
||||
| `github.ref_type` | `string` | {% data reusables.actions.ref_type-description %} |
|
||||
{%- endif %}
|
||||
| `github.path` | `string` | Path on the runner to the file that sets system `PATH` variables from workflow commands. This file is unique to the current step and is a different file for each step in a job. For more information, see "[Workflow commands for {% data variables.product.prodname_actions %}](/actions/learn-github-actions/workflow-commands-for-github-actions#adding-a-system-path)." |
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Finding and customizing actions
|
||||
shortTitle: Finding and customizing actions
|
||||
shortTitle: Find and customize actions
|
||||
intro: 'Actions are the building blocks that power your workflow. A workflow can contain actions created by the community, or you can create your own actions directly within your application''s repository. This guide will show you how to discover, use, and customize actions.'
|
||||
redirect_from:
|
||||
- /actions/automating-your-workflow-with-github-actions/using-github-marketplace-actions
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Understanding GitHub Actions
|
||||
shortTitle: Understanding GitHub Actions
|
||||
shortTitle: Understand GitHub Actions
|
||||
intro: 'Learn the basics of {% data variables.product.prodname_actions %}, including core concepts and essential terminology.'
|
||||
miniTocMaxHeadingLevel: 3
|
||||
redirect_from:
|
||||
@@ -87,15 +87,9 @@ For more information, see "[Creating actions](/actions/creating-actions)."
|
||||
|
||||
{% data reusables.actions.workflow-basic-example-and-explanation %}
|
||||
|
||||
## More complex examples
|
||||
{% data reusables.actions.link-to-example-library %}
|
||||
|
||||
## Next steps
|
||||
|
||||
- To continue learning about {% data variables.product.prodname_actions %}, see "[Finding and customizing actions](/actions/learn-github-actions/finding-and-customizing-actions)."
|
||||
{% ifversion fpt or ghec or ghes %}
|
||||
- To understand how billing works for {% data variables.product.prodname_actions %}, see "[About billing for {% data variables.product.prodname_actions %}](/actions/reference/usage-limits-billing-and-administration#about-billing-for-github-actions)."
|
||||
{% endif %}
|
||||
{% data reusables.actions.onboarding-next-steps %}
|
||||
|
||||
## Contacting support
|
||||
|
||||
|
||||
@@ -1,5 +1,6 @@
|
||||
---
|
||||
title: Re-running workflows and jobs
|
||||
shortTitle: Re-run workflows and jobs
|
||||
intro: 'You can re-run a workflow run{% ifversion re-run-jobs %}, all failed jobs in a workflow run, or specific jobs in a workflow run{% endif %} up to 30 days after its initial run.'
|
||||
permissions: People with write permissions to a repository can re-run workflows in the repository.
|
||||
miniTocMaxHeadingLevel: 3
|
||||
@@ -48,14 +49,14 @@ Re-running a workflow{% ifversion re-run-jobs %} or jobs in a workflow{% endif %
|
||||
To re-run a failed workflow run, use the `run rerun` subcommand. Replace `run-id` with the ID of the failed run that you want to re-run. If you don't specify a `run-id`, {% data variables.product.prodname_cli %} returns an interactive menu for you to choose a recent failed run.
|
||||
|
||||
```shell
|
||||
gh run rerun <em>run-id</em>
|
||||
gh run rerun RUN_ID
|
||||
```
|
||||
|
||||
{% ifversion debug-reruns %}
|
||||
{% data reusables.actions.enable-debug-logging-cli %}
|
||||
|
||||
```shell
|
||||
gh run rerun <em>run-id</em> --debug
|
||||
gh run rerun RUN_ID --debug
|
||||
```
|
||||
|
||||
{% endif %}
|
||||
@@ -90,14 +91,14 @@ If any jobs in a workflow run failed, you can re-run just the jobs that failed.
|
||||
To re-run failed jobs in a workflow run, use the `run rerun` subcommand with the `--failed` flag. Replace `run-id` with the ID of the run for which you want to re-run failed jobs. If you don't specify a `run-id`, {% data variables.product.prodname_cli %} returns an interactive menu for you to choose a recent failed run.
|
||||
|
||||
```shell
|
||||
gh run rerun <em>run-id</em> --failed
|
||||
gh run rerun RUN_ID --failed
|
||||
```
|
||||
|
||||
{% ifversion debug-reruns %}
|
||||
{% data reusables.actions.enable-debug-logging-cli %}
|
||||
|
||||
```shell
|
||||
gh run rerun <em>run-id</em> --failed --debug
|
||||
gh run rerun RUN_ID --failed --debug
|
||||
```
|
||||
|
||||
{% endif %}
|
||||
@@ -127,14 +128,14 @@ When you re-run a specific job in a workflow, a new workflow run will start for
|
||||
To re-run a specific job in a workflow run, use the `run rerun` subcommand with the `--job` flag. Replace `job-id` with the ID of the job that you want to re-run.
|
||||
|
||||
```shell
|
||||
gh run rerun --job <em>job-id</em>
|
||||
gh run rerun --job JOB_ID
|
||||
```
|
||||
|
||||
{% ifversion debug-reruns %}
|
||||
{% data reusables.actions.enable-debug-logging-cli %}
|
||||
|
||||
```shell
|
||||
gh run rerun --job <em>job-id</em> --debug
|
||||
gh run rerun --job JOB_ID --debug
|
||||
```
|
||||
|
||||
{% endif %}
|
||||
|
||||
@@ -1,5 +1,6 @@
|
||||
---
|
||||
title: Publishing Docker images
|
||||
shortTitle: Publish Docker images
|
||||
intro: 'You can publish Docker images to a registry, such as Docker Hub or {% data variables.product.prodname_registry %}, as part of your continuous integration (CI) workflow.'
|
||||
redirect_from:
|
||||
- /actions/language-and-framework-guides/publishing-docker-images
|
||||
|
||||
@@ -77,21 +77,13 @@ Committing the workflow file to a branch in your repository triggers the `push`
|
||||
|
||||
For example, you can see the list of files in your repository:
|
||||
|
||||
|
||||
|
||||
The example workflow you just added is triggered each time code is pushed to the branch, and shows you how {% data variables.product.prodname_actions %} can work with the contents of your repository. For an in-depth tutorial, see "[Understanding {% data variables.product.prodname_actions %}](/actions/learn-github-actions/understanding-github-actions)."
|
||||
|
||||
## More starter workflows
|
||||
|
||||
{% data reusables.actions.workflow-template-overview %}
|
||||
|
||||
## More complex examples
|
||||
{% data reusables.actions.link-to-example-library %}
|
||||
|
||||
## Next steps
|
||||
|
||||
The example workflow you just added runs each time code is pushed to the branch, and shows you how {% data variables.product.prodname_actions %} can work with the contents of your repository. But this is only the beginning of what you can do with {% data variables.product.prodname_actions %}:
|
||||
|
||||
- Your repository can contain multiple workflows that trigger different jobs based on different events.
|
||||
- You can use a workflow to install software testing apps and have them automatically test your code on {% data variables.product.prodname_dotcom %}'s runners.
|
||||
|
||||
{% data variables.product.prodname_actions %} can help you automate nearly every aspect of your application development processes. Ready to get started? Here are some helpful resources for taking your next steps with {% data variables.product.prodname_actions %}:
|
||||
|
||||
- "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)" for an in-depth tutorial.
|
||||
{% data reusables.actions.onboarding-next-steps %}
|
||||
|
||||
@@ -93,13 +93,13 @@ If your repository has environment secrets or can access secrets from the parent
|
||||
To add a repository secret, use the `gh secret set` subcommand. Replace `secret-name` with the name of your secret.
|
||||
|
||||
```shell
|
||||
gh secret set <em>secret-name</em>
|
||||
gh secret set SECRET_NAME
|
||||
```
|
||||
|
||||
The CLI will prompt you to enter a secret value. Alternatively, you can read the value of the secret from a file.
|
||||
|
||||
```shell
|
||||
gh secret set <em>secret-name</em> < secret.txt
|
||||
gh secret set SECRET_NAME < secret.txt
|
||||
```
|
||||
|
||||
To list all secrets for the repository, use the `gh secret list` subcommand.
|
||||
@@ -128,13 +128,13 @@ To list all secrets for the repository, use the `gh secret list` subcommand.
|
||||
To add a secret for an environment, use the `gh secret set` subcommand with the `--env` or `-e` flag followed by the environment name.
|
||||
|
||||
```shell
|
||||
gh secret set --env <em>environment-name</em> <em>secret-name</em>
|
||||
gh secret set --env ENV_NAME SECRET_NAME
|
||||
```
|
||||
|
||||
To list all secrets for an environment, use the `gh secret list` subcommand with the `--env` or `-e` flag followed by the environment name.
|
||||
|
||||
```shell
|
||||
gh secret list --env <em>environment-name</em>
|
||||
gh secret list --env ENV_NAME
|
||||
```
|
||||
|
||||
{% endcli %}
|
||||
@@ -173,25 +173,25 @@ gh auth login --scopes "admin:org"
|
||||
To add a secret for an organization, use the `gh secret set` subcommand with the `--org` or `-o` flag followed by the organization name.
|
||||
|
||||
```shell
|
||||
gh secret set --org <em>organization-name</em> <em>secret-name</em>
|
||||
gh secret set --org ORG_NAME SECRET_NAME
|
||||
```
|
||||
|
||||
By default, the secret is only available to private repositories. To specify that the secret should be available to all repositories within the organization, use the `--visibility` or `-v` flag.
|
||||
|
||||
```shell
|
||||
gh secret set --org <em>organization-name</em> <em>secret-name</em> --visibility all
|
||||
gh secret set --org ORG_NAME SECRET_NAME --visibility all
|
||||
```
|
||||
|
||||
To specify that the secret should be available to selected repositories within the organization, use the `--repos` or `-r` flag.
|
||||
|
||||
```shell
|
||||
gh secret set --org <em>organization-name</em> <em>secret-name</em> --repos <em>repo-name-1</em>,<em>repo-name-2</em>"
|
||||
gh secret set --org ORG_NAME SECRET_NAME --repos REPO-NAME-1, REPO-NAME-2"
|
||||
```
|
||||
|
||||
To list all secrets for an organization, use the `gh secret list` subcommand with the `--org` or `-o` flag followed by the organization name.
|
||||
|
||||
```shell
|
||||
gh secret list --org <em>organization-name</em>
|
||||
gh secret list --org ORG_NAME
|
||||
```
|
||||
|
||||
{% endcli %}
|
||||
|
||||
@@ -1,11 +1,11 @@
|
||||
---
|
||||
title: Using 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'
|
||||
shortTitle: Using {% data variables.actions.hosted_runner %}s
|
||||
---
|
||||
|
||||
## Overview of {% data variables.actions.hosted_runner %}s
|
||||
@@ -87,7 +87,7 @@ You can add a {% data variables.actions.hosted_runner %} to an organization, whe
|
||||
|
||||
## Running jobs on your runner
|
||||
|
||||
Once your runner type has been been defined, you can update your workflows to send jobs to the runner instances for processing. In this example, a runner group is populated with Ubuntu 16-core runners, which have been assigned the label `ubuntu-20.04-16core`. If you have a runner matching this label, the `check-bats-version` job then uses the `runs-on` key to target that runner whenever the job is run:
|
||||
Once your runner type has been defined, you can update your workflow YAML files to send jobs to your newly created runner instances for processing. In this example, a runner group is populated with Ubuntu 16-core runners, which have been assigned the label `ubuntu-20.04-16core`. If you have a runner matching this label, the `check-bats-version` job then uses the `runs-on` key to target that runner whenever the job is run:
|
||||
|
||||
```yaml
|
||||
name: learn-github-actions
|
||||
@@ -104,6 +104,8 @@ jobs:
|
||||
- run: bats -v
|
||||
```
|
||||
|
||||
To find out which runners are enabled for your repository and organization, you must contact your organization admin. Your organization admin can create new runners and runner groups, as well as configure permissions to specify which repositories can access a runner group.
|
||||
|
||||
## Managing access to your runners
|
||||
|
||||
{% note %}
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Creating starter workflows for your organization
|
||||
shortTitle: Creating starter workflows
|
||||
shortTitle: Create starter workflows
|
||||
intro: Learn how you can create starter workflows to help people in your team add new workflows more easily.
|
||||
redirect_from:
|
||||
- /actions/configuring-and-managing-workflows/sharing-workflow-templates-within-your-organization
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Reusing workflows
|
||||
shortTitle: Reusing workflows
|
||||
shortTitle: Reuse workflows
|
||||
intro: Learn how to avoid duplication when creating a workflow by reusing existing workflows.
|
||||
redirect_from:
|
||||
- /actions/learn-github-actions/reusing-workflows
|
||||
@@ -105,7 +105,7 @@ You can define inputs and secrets, which can be passed from the caller workflow
|
||||
on:
|
||||
workflow_call:
|
||||
inputs:
|
||||
username:
|
||||
config-path:
|
||||
required: true
|
||||
type: string
|
||||
secrets:
|
||||
@@ -133,10 +133,10 @@ You can define inputs and secrets, which can be passed from the caller workflow
|
||||
runs-on: ubuntu-latest
|
||||
environment: production
|
||||
steps:
|
||||
- uses: octo-org/my-action@v1
|
||||
with:
|
||||
username: ${{ inputs.username }}
|
||||
token: ${{ secrets.envPAT }}
|
||||
- uses: actions/labeler@v4
|
||||
with:
|
||||
repo-token: ${{ secrets.envPAT }}
|
||||
configuration-path: ${{ inputs.config-path }}
|
||||
```
|
||||
{% endraw %}
|
||||
In the example above, `envPAT` is an environment secret that's been added to the `production` environment. This environment is therefore referenced within the job.
|
||||
@@ -162,7 +162,7 @@ name: Reusable workflow example
|
||||
on:
|
||||
workflow_call:
|
||||
inputs:
|
||||
username:
|
||||
config-path:
|
||||
required: true
|
||||
type: string
|
||||
secrets:
|
||||
@@ -170,14 +170,13 @@ on:
|
||||
required: true
|
||||
|
||||
jobs:
|
||||
example_job:
|
||||
name: Pass input and secrets to my-action
|
||||
triage:
|
||||
runs-on: ubuntu-latest
|
||||
steps:
|
||||
- uses: octo-org/my-action@v1
|
||||
with:
|
||||
username: ${{ inputs.username }}
|
||||
token: ${{ secrets.token }}
|
||||
- uses: actions/labeler@v4
|
||||
with:
|
||||
repo-token: ${{ secrets.token }}
|
||||
configuration-path: ${{ inputs.config-path }}
|
||||
```
|
||||
{% endraw %}
|
||||
|
||||
@@ -256,7 +255,7 @@ When you call a reusable workflow, you can only use the following keywords in th
|
||||
|
||||
### Example caller workflow
|
||||
|
||||
This workflow file calls two workflow files. The second of these, `workflow-B.yml` (shown in the [example reusable workflow](#example-reusable-workflow)), is passed an input (`username`) and a secret (`token`).
|
||||
This workflow file calls two workflow files. The second of these, `workflow-B.yml` (shown in the [example reusable workflow](#example-reusable-workflow)), is passed an input (`config-path`) and a secret (`token`).
|
||||
|
||||
{% raw %}
|
||||
```yaml{:copy}
|
||||
@@ -272,11 +271,14 @@ jobs:
|
||||
uses: octo-org/example-repo/.github/workflows/workflow-A.yml@v1
|
||||
|
||||
call-workflow-passing-data:
|
||||
permissions:
|
||||
contents: read
|
||||
pull-requests: write
|
||||
uses: octo-org/example-repo/.github/workflows/workflow-B.yml@main
|
||||
with:
|
||||
username: mona
|
||||
config-path: .github/labeler.yml
|
||||
secrets:
|
||||
token: ${{ secrets.TOKEN }}
|
||||
token: ${{ secrets.GITHUB_TOKEN }}
|
||||
```
|
||||
{% endraw %}
|
||||
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: 'Sharing workflows, secrets, and runners with your organization'
|
||||
shortTitle: Sharing workflows with your organization
|
||||
shortTitle: Share workflows with your organization
|
||||
intro: 'Learn how you can use organization features to collaborate with your team, by sharing starter workflows, secrets, and self-hosted runners.'
|
||||
redirect_from:
|
||||
- /actions/learn-github-actions/sharing-workflows-with-your-organization
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Triggering a workflow
|
||||
shortTitle: Triggering a workflow
|
||||
shortTitle: Trigger a workflow
|
||||
intro: 'How to automatically trigger {% data variables.product.prodname_actions %} workflows'
|
||||
versions:
|
||||
fpt: '*'
|
||||
|
||||
@@ -93,7 +93,7 @@ By default, the rate limit for {% data variables.product.prodname_actions %} is
|
||||
|
||||
```shell
|
||||
ghe-config actions-rate-limiting.enabled true
|
||||
ghe-config actions-rate-limiting.queue-runs-per-minute <em>RUNS-PER-MINUTE</em>
|
||||
ghe-config actions-rate-limiting.queue-runs-per-minute RUNS-PER-MINUTE
|
||||
```
|
||||
1. To disable the rate limit after it's been enabled, run the following command.
|
||||
|
||||
|
||||
@@ -118,7 +118,7 @@ If the upgrade target you're presented with is a feature release instead of a pa
|
||||
{% data reusables.enterprise_installation.download-package %}
|
||||
4. Run the `ghe-upgrade` command using the package file name:
|
||||
```shell
|
||||
admin@<em>HOSTNAME</em>:~$ ghe-upgrade <em>GITHUB-UPGRADE.hpkg</em>
|
||||
admin@HOSTNAME:~$ ghe-upgrade GITHUB-UPGRADE.hpkg
|
||||
*** verifying upgrade package signature...
|
||||
```
|
||||
5. If a reboot is required for updates for kernel, MySQL, Elasticsearch or other programs, the hotpatch upgrade script notifies you.
|
||||
@@ -170,14 +170,14 @@ While you can use a hotpatch to upgrade to the latest patch release within a fea
|
||||
|
||||
5. Run the `ghe-upgrade` command using the package file name:
|
||||
```shell
|
||||
admin@<em>HOSTNAME</em>:~$ ghe-upgrade <em>GITHUB-UPGRADE.pkg</em>
|
||||
admin@HOSTNAME:~$ ghe-upgrade GITHUB-UPGRADE.pkg
|
||||
*** verifying upgrade package signature...
|
||||
```
|
||||
6. Confirm that you'd like to continue with the upgrade and restart after the package signature verifies. The new root filesystem writes to the secondary partition and the instance automatically restarts in maintenance mode:
|
||||
```shell
|
||||
*** applying update...
|
||||
This package will upgrade your installation to version <em>version-number</em>
|
||||
Current root partition: /dev/xvda1 [<em>version-number</em>]
|
||||
This package will upgrade your installation to version VERSION-NUMBER
|
||||
Current root partition: /dev/xvda1 [VERSION-NUMBER]
|
||||
Target root partition: /dev/xvda2
|
||||
Proceed with installation? [y/N]
|
||||
```
|
||||
|
||||
Some files were not shown because too many files have changed in this diff Show More
Reference in New Issue
Block a user