diff --git a/.github/workflows/move-help-wanted-issues.yml b/.github/workflows/move-help-wanted-issues.yml index b5697b6d7d..5f7b7ae5d9 100644 --- a/.github/workflows/move-help-wanted-issues.yml +++ b/.github/workflows/move-help-wanted-issues.yml @@ -23,6 +23,6 @@ jobs: steps: - uses: alex-page/github-project-automation-plus@bb266ff4dde9242060e2d5418e120a133586d488 with: - project: Docs team reviews + project: Docs open source board column: Help wanted repo-token: ${{ secrets.DOCUBOT_READORG_REPO_WORKFLOW_SCOPES }} diff --git a/.github/workflows/openapi-decorate.yml b/.github/workflows/openapi-decorate.yml index 67e67cac58..f7d85db1c4 100644 --- a/.github/workflows/openapi-decorate.yml +++ b/.github/workflows/openapi-decorate.yml @@ -57,7 +57,7 @@ jobs: uses: EndBug/add-and-commit@050a66787244b10a4874a2a5f682130263edc192 with: # The arguments for the `git add` command - add: '["lib/rest/static/apps", "lib/rest/static/decorated"]' + add: '["lib/rest/static/apps", "lib/rest/static/decorated", "lib/redirects/static/client-side-rest-api-redirects.json"]' # The message for the commit message: 'Add decorated OpenAPI schema files' diff --git a/assets/images/help/desktop/branch-drop-down-pull-request-tab.png b/assets/images/help/desktop/branch-drop-down-pull-request-tab.png index 57f10ab13f..5b9f00d426 100644 Binary files a/assets/images/help/desktop/branch-drop-down-pull-request-tab.png and b/assets/images/help/desktop/branch-drop-down-pull-request-tab.png differ diff --git a/assets/images/help/desktop/checks-dialog.png b/assets/images/help/desktop/checks-dialog.png new file mode 100644 index 0000000000..6e56489139 Binary files /dev/null and b/assets/images/help/desktop/checks-dialog.png differ diff --git a/assets/images/help/desktop/checks-failed-dialog.png b/assets/images/help/desktop/checks-failed-dialog.png new file mode 100644 index 0000000000..5d8571ac61 Binary files /dev/null and b/assets/images/help/desktop/checks-failed-dialog.png differ diff --git a/assets/images/help/desktop/click-pull-request.png b/assets/images/help/desktop/click-pull-request.png index 14af96e9e0..052ae1e765 100644 Binary files a/assets/images/help/desktop/click-pull-request.png and b/assets/images/help/desktop/click-pull-request.png differ diff --git a/assets/images/help/desktop/mac-enable-notifications.png b/assets/images/help/desktop/mac-enable-notifications.png new file mode 100644 index 0000000000..f26bf845e8 Binary files /dev/null and b/assets/images/help/desktop/mac-enable-notifications.png differ diff --git a/assets/images/help/desktop/pull-request-checks-failed-notification.png b/assets/images/help/desktop/pull-request-checks-failed-notification.png new file mode 100644 index 0000000000..27bfa863f2 Binary files /dev/null and b/assets/images/help/desktop/pull-request-checks-failed-notification.png differ diff --git a/assets/images/help/desktop/pull-request-list-sync.png.png b/assets/images/help/desktop/pull-request-list-sync.png.png new file mode 100644 index 0000000000..87a480c5ce Binary files /dev/null and b/assets/images/help/desktop/pull-request-list-sync.png.png differ diff --git a/assets/images/help/desktop/pull-request-review-dialog.png b/assets/images/help/desktop/pull-request-review-dialog.png new file mode 100644 index 0000000000..e1a272291c Binary files /dev/null and b/assets/images/help/desktop/pull-request-review-dialog.png differ diff --git a/assets/images/help/desktop/pull-request-review-notification.png b/assets/images/help/desktop/pull-request-review-notification.png new file mode 100644 index 0000000000..7d040ac580 Binary files /dev/null and b/assets/images/help/desktop/pull-request-review-notification.png differ diff --git a/assets/images/help/desktop/re-run-confirmation-dialog.png b/assets/images/help/desktop/re-run-confirmation-dialog.png new file mode 100644 index 0000000000..9a6aa72dbf Binary files /dev/null and b/assets/images/help/desktop/re-run-confirmation-dialog.png differ diff --git a/assets/images/help/desktop/re-run-failed-checks.png b/assets/images/help/desktop/re-run-failed-checks.png new file mode 100644 index 0000000000..8df302e21d Binary files /dev/null and b/assets/images/help/desktop/re-run-failed-checks.png differ diff --git a/assets/images/help/desktop/re-run-individual-checks.png b/assets/images/help/desktop/re-run-individual-checks.png new file mode 100644 index 0000000000..1147c864bf Binary files /dev/null and b/assets/images/help/desktop/re-run-individual-checks.png differ diff --git a/assets/images/help/desktop/windows-enable-notifications.png b/assets/images/help/desktop/windows-enable-notifications.png new file mode 100644 index 0000000000..650446c57f Binary files /dev/null and b/assets/images/help/desktop/windows-enable-notifications.png differ diff --git a/content/actions/automating-builds-and-tests/building-and-testing-swift.md b/content/actions/automating-builds-and-tests/building-and-testing-swift.md index 9924803df1..b40251f299 100644 --- a/content/actions/automating-builds-and-tests/building-and-testing-swift.md +++ b/content/actions/automating-builds-and-tests/building-and-testing-swift.md @@ -65,7 +65,7 @@ The examples below demonstrate using the `fwal/setup-swift` action. ### Using multiple Swift versions -You can configure your job to use a multiple versions of Swift in a build matrix. +You can configure your job to use multiple versions of Swift in a matrix. ```yaml{:copy} {% data reusables.actions.actions-not-certified-by-github-comment %} diff --git a/content/actions/learn-github-actions/contexts.md b/content/actions/learn-github-actions/contexts.md index 34914d02d6..7b037652c3 100644 --- a/content/actions/learn-github-actions/contexts.md +++ b/content/actions/learn-github-actions/contexts.md @@ -23,7 +23,7 @@ miniTocMaxHeadingLevel: 3 Contexts are a way to access information about workflow runs, runner environments, jobs, and steps. Each context is an object that contains properties, which can be strings or other objects. -{% data reusables.actions.context-contents %} For example, the `matrix` context is only populated for jobs in a [build matrix](/actions/learn-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategymatrix). +{% data reusables.actions.context-contents %} For example, the `matrix` context is only populated for jobs in a [matrix](/actions/learn-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategymatrix). You can access contexts using the expression syntax. For more information, see "[Expressions](/actions/learn-github-actions/expressions)." @@ -552,19 +552,19 @@ The following example contents of the `secrets` context shows the automatic `GIT ## `strategy` context -For workflows with a build matrix, the `strategy` context contains information about the matrix execution strategy for the current job. +For workflows with a matrix, the `strategy` context contains information about the matrix execution strategy for the current job. | Property name | Type | Description | |---------------|------|-------------| | `strategy` | `object` | This context changes for each job in a workflow run. You can access this context from any job or step in a workflow. This object contains all the properties listed below. | -| `strategy.fail-fast` | `string` | When `true`, all in-progress jobs are canceled if any job in a build matrix fails. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/learn-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategyfail-fast)." | -| `strategy.job-index` | `string` | The index of the current job in the build matrix. **Note:** This number is a zero-based number. The first job's index in the build matrix is `0`. | -| `strategy.job-total` | `string` | The total number of jobs in the build matrix. **Note:** This number **is not** a zero-based number. For example, for a build matrix with four jobs, the value of `job-total` is `4`. | +| `strategy.fail-fast` | `string` | When `true`, all in-progress jobs are canceled if any job in a matrix fails. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/learn-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategyfail-fast)." | +| `strategy.job-index` | `string` | The index of the current job in the matrix. **Note:** This number is a zero-based number. The first job's index in the matrix is `0`. | +| `strategy.job-total` | `string` | The total number of jobs in the matrix. **Note:** This number **is not** a zero-based number. For example, for a matrix with four jobs, the value of `job-total` is `4`. | | `strategy.max-parallel` | `string` | The maximum number of jobs that can run simultaneously when using a `matrix` job strategy. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/learn-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategymax-parallel)." | ### Example contents of the `strategy` context -The following example contents of the `strategy` context is from a build matrix with four jobs, and is taken from the final job. Note the difference between the zero-based `job-index` number, and `job-total` which is not zero-based. +The following example contents of the `strategy` context is from a matrix with four jobs, and is taken from the final job. Note the difference between the zero-based `job-index` number, and `job-total` which is not zero-based. ```yaml { @@ -577,7 +577,7 @@ The following example contents of the `strategy` context is from a build matrix ### Example usage of the `strategy` context -This example workflow uses the `strategy.job-index` property to set a unique name for a log file for each job in a build matrix. +This example workflow uses the `strategy.job-index` property to set a unique name for a log file for each job in a matrix. ```yaml{:copy} name: Test matrix @@ -602,18 +602,18 @@ jobs: ## `matrix` context -For workflows with a build matrix, the `matrix` context contains the matrix properties defined in the workflow file that apply to the current job. For example, if you configure a build matrix with the `os` and `node` keys, the `matrix` context object includes the `os` and `node` properties with the values that are being used for the current job. +For workflows with a matrix, the `matrix` context contains the matrix properties defined in the workflow file that apply to the current job. For example, if you configure a matrix with the `os` and `node` keys, the `matrix` context object includes the `os` and `node` properties with the values that are being used for the current job. There are no standard properties in the `matrix` context, only those which are defined in the workflow file. | Property name | Type | Description | |---------------|------|-------------| -| `matrix` | `object` | This context is only available for jobs in a build matrix, and changes for each job in a workflow run. You can access this context from any job or step in a workflow. This object contains the properties listed below. | +| `matrix` | `object` | This context is only available for jobs in a matrix, and changes for each job in a workflow run. You can access this context from any job or step in a workflow. This object contains the properties listed below. | | `matrix.` | `string` | The value of a matrix property. | ### Example contents of the `matrix` context -The following example contents of the `matrix` context is from a job in a build matrix that has the `os` and `node` matrix properties defined in the workflow. The job is executing the matrix combination of an `ubuntu-latest` OS and Node.js version `16`. +The following example contents of the `matrix` context is from a job in a matrix that has the `os` and `node` matrix properties defined in the workflow. The job is executing the matrix combination of an `ubuntu-latest` OS and Node.js version `16`. ```yaml { @@ -624,7 +624,7 @@ The following example contents of the `matrix` context is from a job in a build ### Example usage of the `matrix` context -This example workflow creates a build matrix with `os` and `node` keys. It uses the `matrix.os` property to set the runner type for each job, and uses the `matrix.node` property to set the Node.js version for each job. +This example workflow creates a matrix with `os` and `node` keys. It uses the `matrix.os` property to set the runner type for each job, and uses the `matrix.node` property to set the Node.js version for each job. ```yaml{:copy} name: Test matrix diff --git a/content/actions/migrating-to-github-actions/migrating-from-circleci-to-github-actions.md b/content/actions/migrating-to-github-actions/migrating-from-circleci-to-github-actions.md index 1c61cc8c55..576e0f706e 100644 --- a/content/actions/migrating-to-github-actions/migrating-from-circleci-to-github-actions.md +++ b/content/actions/migrating-to-github-actions/migrating-from-circleci-to-github-actions.md @@ -50,7 +50,7 @@ Both CircleCI and {% data variables.product.prodname_actions %} configure `jobs` Both CircleCI and {% data variables.product.prodname_actions %} provide a mechanism to reuse and share tasks in a workflow. CircleCI uses a concept called orbs, written in YAML, to provide tasks that people can reuse in a workflow. {% data variables.product.prodname_actions %} has powerful and flexible reusable components called actions, which you build with either JavaScript files or Docker images. You can create actions by writing custom code that interacts with your repository in any way you'd like, including integrating with {% data variables.product.product_name %}'s APIs and any publicly available third-party API. For example, an action can publish npm modules, send SMS alerts when urgent issues are created, or deploy production-ready code. For more information, see "[Creating actions](/actions/creating-actions)." -CircleCI can reuse pieces of workflows with YAML anchors and aliases. {% data variables.product.prodname_actions %} supports the most common need for reusability using build matrixes. For more information about build matrixes, see "[Managing complex workflows](/actions/learn-github-actions/managing-complex-workflows/#using-a-build-matrix)." +CircleCI can reuse pieces of workflows with YAML anchors and aliases. {% data variables.product.prodname_actions %} supports the most common need for reusability using matrices. For more information about matrices, see "[Using a matrix for your jobs](/actions/using-jobs/using-a-matrix-for-your-jobs)." ## Using Docker images diff --git a/content/actions/migrating-to-github-actions/migrating-from-jenkins-to-github-actions.md b/content/actions/migrating-to-github-actions/migrating-from-jenkins-to-github-actions.md index ff04a6c387..ca409c3ec0 100644 --- a/content/actions/migrating-to-github-actions/migrating-from-jenkins-to-github-actions.md +++ b/content/actions/migrating-to-github-actions/migrating-from-jenkins-to-github-actions.md @@ -82,9 +82,9 @@ Jenkins can run the `stages` and `steps` in parallel, while {% data variables.pr | ------------- | ------------- | | [`parallel`](https://jenkins.io/doc/book/pipeline/syntax/#parallel) | [`jobs..strategy.max-parallel`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategymax-parallel) | -### Build matrix +### Matrix -Both {% data variables.product.prodname_actions %} and Jenkins let you use a build matrix to define various system combinations. +Both {% data variables.product.prodname_actions %} and Jenkins let you use a matrix to define various system combinations. | Jenkins | {% data variables.product.prodname_actions %} | | ------------- | ------------- | diff --git a/content/actions/migrating-to-github-actions/migrating-from-travis-ci-to-github-actions.md b/content/actions/migrating-to-github-actions/migrating-from-travis-ci-to-github-actions.md index fb1623dd40..5d8af556f7 100644 --- a/content/actions/migrating-to-github-actions/migrating-from-travis-ci-to-github-actions.md +++ b/content/actions/migrating-to-github-actions/migrating-from-travis-ci-to-github-actions.md @@ -60,9 +60,9 @@ Travis CI can use `stages` to run jobs in parallel. Similarly, {% data variables Travis CI and {% data variables.product.prodname_actions %} both support status badges, which let you indicate whether a build is passing or failing. For more information, see ["Adding a workflow status badge to your repository](/actions/managing-workflow-runs/adding-a-workflow-status-badge)." -### Using a build matrix +### Using a matrix -Travis CI and {% data variables.product.prodname_actions %} both support a build matrix, allowing you to perform testing using combinations of operating systems and software packages. For more information, see "[Using a build matrix](/actions/learn-github-actions/managing-complex-workflows#using-a-build-matrix)." +Travis CI and {% data variables.product.prodname_actions %} both support a matrix, allowing you to perform testing using combinations of operating systems and software packages. For more information, see "[Using a matrix for your jobs](/actions/using-jobs/using-a-matrix-for-your-jobs)." Below is an example comparing the syntax for each system: diff --git a/content/actions/using-jobs/index.md b/content/actions/using-jobs/index.md index 1a414c0c1d..b579ac9323 100644 --- a/content/actions/using-jobs/index.md +++ b/content/actions/using-jobs/index.md @@ -13,7 +13,7 @@ children: - /using-jobs-in-a-workflow - /choosing-the-runner-for-a-job - /using-conditions-to-control-job-execution - - /using-a-build-matrix-for-your-jobs + - /using-a-matrix-for-your-jobs - /using-concurrency - /using-environments-for-jobs - /running-jobs-in-a-container diff --git a/content/actions/using-jobs/using-a-build-matrix-for-your-jobs.md b/content/actions/using-jobs/using-a-build-matrix-for-your-jobs.md deleted file mode 100644 index bb1844b8a7..0000000000 --- a/content/actions/using-jobs/using-a-build-matrix-for-your-jobs.md +++ /dev/null @@ -1,30 +0,0 @@ ---- -title: Using a build matrix for your jobs -shortTitle: Using a build matrix for your jobs -intro: Create a build matrix and define variations for each job. -versions: - fpt: '*' - ghes: '*' - ghae: '*' - ghec: '*' -miniTocMaxHeadingLevel: 4 ---- - -{% data reusables.actions.enterprise-beta %} -{% data reusables.actions.enterprise-github-hosted-runners %} - -## Overview - -{% data reusables.actions.jobs.section-using-a-build-matrix-for-your-jobs-strategy %} - -## Creating a matrix of different job configurations - -{% data reusables.actions.jobs.section-using-a-build-matrix-for-your-jobs-matrix %} - -## Canceling remaining jobs if a `matrix` job fails - -{% data reusables.actions.jobs.section-using-a-build-matrix-for-your-jobs-failfast %} - -## Defining the maximum number of concurrent jobs in a `matrix` - -{% data reusables.actions.jobs.section-using-a-build-matrix-for-your-jobs-max-parallel %} diff --git a/content/actions/using-jobs/using-a-matrix-for-your-jobs.md b/content/actions/using-jobs/using-a-matrix-for-your-jobs.md new file mode 100644 index 0000000000..40615bed48 --- /dev/null +++ b/content/actions/using-jobs/using-a-matrix-for-your-jobs.md @@ -0,0 +1,60 @@ +--- +title: Using a matrix for your jobs +shortTitle: Using a matrix +intro: Create a matrix to define variations for each job. +versions: + fpt: '*' + ghes: '*' + ghae: '*' + ghec: '*' +miniTocMaxHeadingLevel: 4 +redirect_from: + - /actions/using-jobs/using-a-build-matrix-for-your-jobs +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +## About matrix strategies + +{% data reusables.actions.jobs.about-matrix-strategy %} + +## Using a matrix strategy + +{% data reusables.actions.jobs.using-matrix-strategy %} + +### Example: Using a single-dimension matrix + +{% data reusables.actions.jobs.single-dimension-matrix %} + +### Example: Using a multi-dimension matrix + +{% data reusables.actions.jobs.multi-dimension-matrix %} + +### Example: Using contexts to create matrices + +{% data reusables.actions.jobs.matrix-from-context %} + +## Expanding or adding matrix configurations + +{% data reusables.actions.jobs.matrix-include %} + +### Example: Expanding configurations + +{% data reusables.actions.jobs.matrix-expand-with-include %} + +### Example: Adding configurations + +{% data reusables.actions.jobs.matrix-add-with-include %} + +## Excluding matrix configurations + +{% data reusables.actions.jobs.matrix-exclude %} + +## Handling failures + +{% data reusables.actions.jobs.section-using-a-build-matrix-for-your-jobs-failfast %} + +## Defining the maximum number of concurrent jobs + +{% data reusables.actions.jobs.section-using-a-build-matrix-for-your-jobs-max-parallel %} diff --git a/content/actions/using-workflows/about-workflows.md b/content/actions/using-workflows/about-workflows.md index e052a37d03..30762e5dd2 100644 --- a/content/actions/using-workflows/about-workflows.md +++ b/content/actions/using-workflows/about-workflows.md @@ -105,9 +105,9 @@ jobs: For more information, see "[Defining prerequisite jobs](/actions/using-jobs/using-jobs-in-a-workflow#defining-prerequisite-jobs)." -### Using a build matrix +### Using a matrix -You can use a build matrix if you want your workflow to run tests across multiple combinations of parameters, such as operating systems, platforms, and languages. The build matrix is created using the `strategy` keyword, which receives the build options as an array. For example, this build matrix will run the job multiple times, using different versions of Node.js: +{% data reusables.actions.jobs.about-matrix-strategy %} The matrix is created using the `strategy` keyword, which receives the build options as an array. For example, this matrix will run the job multiple times, using different versions of Node.js: ```yaml jobs: @@ -115,14 +115,14 @@ jobs: runs-on: ubuntu-latest strategy: matrix: - node: [6, 8, 10] + node: [12, 14, 16] steps: - uses: {% data reusables.actions.action-setup-node %} with: node-version: {% raw %}${{ matrix.node }}{% endraw %} ``` -For more information, see "[Using a build matrix for your jobs](/actions/using-jobs/using-a-build-matrix-for-your-jobs)." +For more information, see "[Using a matrix for your jobs](/actions/using-jobs/using-a-matrix-for-your-jobs)." {% ifversion fpt or ghec %} ### Caching dependencies diff --git a/content/actions/using-workflows/reusing-workflows.md b/content/actions/using-workflows/reusing-workflows.md index c3a090642a..0ab6eaf05e 100644 --- a/content/actions/using-workflows/reusing-workflows.md +++ b/content/actions/using-workflows/reusing-workflows.md @@ -103,8 +103,13 @@ You can define inputs and secrets, which can be passed from the caller workflow required: true ``` {% endraw %} + {% if actions-inherit-secrets-reusable-workflows %} + For details of the syntax for defining inputs and secrets, see [`on.workflow_call.inputs`](/actions/reference/workflow-syntax-for-github-actions#onworkflow_callinputs), [`on.workflow_call.secrets`](/actions/reference/workflow-syntax-for-github-actions#onworkflow_callsecrets) and [`on.workflow_call.secrets.inherit`](/actions/using-workflows/workflow-syntax-for-github-actions#onworkflow_callsecretsinherit). + 1. In the reusable workflow, reference the input or secret that you defined in the `on` key in the previous step. If the secrets are inherited using `secrets: inherit`, you can reference them even if they are not defined in the `on` key. + {%else%} For details of the syntax for defining inputs and secrets, see [`on.workflow_call.inputs`](/actions/reference/workflow-syntax-for-github-actions#onworkflow_callinputs) and [`on.workflow_call.secrets`](/actions/reference/workflow-syntax-for-github-actions#onworkflow_callsecrets). -1. In the reusable workflow, reference the input or secret that you defined in the `on` key in the previous step. + 1. In the reusable workflow, reference the input or secret that you defined in the `on` key in the previous step. + {%endif%} {% raw %} ```yaml @@ -189,6 +194,7 @@ When you call a reusable workflow, you can only use the following keywords in th * [`jobs..with.`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idwithinput_id) * [`jobs..secrets`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idsecrets) * [`jobs..secrets.`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idsecretssecret_id) + {% if actions-inherit-secrets-reusable-workflows %}* [`jobs..secrets.inherit`](/actions/using-workflows/workflow-syntax-for-github-actions#onworkflow_callsecretsinherit){% endif %} * [`jobs..needs`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idneeds) * [`jobs..if`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idif) * [`jobs..permissions`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idpermissions) diff --git a/content/actions/using-workflows/workflow-syntax-for-github-actions.md b/content/actions/using-workflows/workflow-syntax-for-github-actions.md index 926f5966f0..57c81c47b2 100644 --- a/content/actions/using-workflows/workflow-syntax-for-github-actions.md +++ b/content/actions/using-workflows/workflow-syntax-for-github-actions.md @@ -157,6 +157,42 @@ jobs: ``` {% endraw %} +{% if actions-inherit-secrets-reusable-workflows %} + +#### `on.workflow_call.secrets.inherit` + +Use the `inherit` keyword to pass all the calling workflow's secrets to the called workflow. This includes all secrets the calling workflow has access to, namely organization, repository, and environment secrets. The `inherit` keyword can be used to pass secrets across repositories within the same organization, or across organizations within the same enterprise. + +#### Example + +{% raw %} + +```yaml +on: + workflow_dispatch: + +jobs: + pass-secrets-to-workflow: + uses: ./.github/workflows/called-workflow.yml + secrets: inherit +``` + +```yaml +on: + workflow_call: + +jobs: + pass-secret-to-action: + runs-on: ubuntu-latest + steps: + - name: Use a repo or org secret from the calling workflow. + uses: echo ${{ secrets.CALLING_WORKFLOW_SECRET }} +``` + +{% endraw %} + +{%endif%} + #### `on.workflow_call.secrets.` A string identifier to associate with the secret. @@ -745,11 +781,39 @@ If the timeout exceeds the job execution time limit for the runner, the job will ## `jobs..strategy` -{% data reusables.actions.jobs.section-using-a-build-matrix-for-your-jobs-strategy %} +Use `jobs..strategy` to use a matrix strategy for your jobs. {% data reusables.actions.jobs.about-matrix-strategy %} For more information, see "[Using a matrix for your jobs](/actions/using-jobs/using-a-matrix-for-your-jobs)." ### `jobs..strategy.matrix` -{% data reusables.actions.jobs.section-using-a-build-matrix-for-your-jobs-matrix %} +{% data reusables.actions.jobs.using-matrix-strategy %} + +#### Example: Using a single-dimension matrix + +{% data reusables.actions.jobs.single-dimension-matrix %} + +#### Example: Using a multi-dimension matrix + +{% data reusables.actions.jobs.multi-dimension-matrix %} + +#### Example: Using contexts to create matrices + +{% data reusables.actions.jobs.matrix-from-context %} + +### `jobs..strategy.matrix.include` + +{% data reusables.actions.jobs.matrix-include %} + +#### Example: Expanding configurations + +{% data reusables.actions.jobs.matrix-expand-with-include %} + +#### Example: Adding configurations + +{% data reusables.actions.jobs.matrix-add-with-include %} + +### `jobs..strategy.matrix.exclude` + +{% data reusables.actions.jobs.matrix-exclude %} ### `jobs..strategy.fail-fast` diff --git a/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning.md b/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning.md index 6841ecf86f..cccde8bdec 100644 --- a/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning.md +++ b/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning.md @@ -208,7 +208,7 @@ If this parameter is not used, the {% data variables.product.prodname_codeql_wor {% data reusables.code-scanning.codeql-languages-bullets %} -The default {% data variables.product.prodname_codeql_workflow %} file contains a build matrix called `language` which lists the languages in your repository that are analyzed. {% data variables.product.prodname_codeql %} automatically populates this matrix when you add {% data variables.product.prodname_code_scanning %} to a repository. Using the `language` matrix optimizes {% data variables.product.prodname_codeql %} to run each analysis in parallel. We recommend that all workflows adopt this configuration due to the performance benefits of parallelizing builds. For more information about build matrices, see "[Managing complex workflows](/actions/learn-github-actions/managing-complex-workflows#using-a-build-matrix)." +The default {% data variables.product.prodname_codeql_workflow %} file contains a matrix called `language` which lists the languages in your repository that are analyzed. {% data variables.product.prodname_codeql %} automatically populates this matrix when you add {% data variables.product.prodname_code_scanning %} to a repository. Using the `language` matrix optimizes {% data variables.product.prodname_codeql %} to run each analysis in parallel. We recommend that all workflows adopt this configuration due to the performance benefits of parallelizing builds. For more information about matrices, see "[Using a matrix for your jobs](/actions/using-jobs/using-a-matrix-for-your-jobs)." {% data reusables.code-scanning.specify-language-to-analyze %} diff --git a/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md b/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md index f3d53a8507..19757d0512 100644 --- a/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md +++ b/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md @@ -68,7 +68,7 @@ If an automatic build of code for a compiled language within your project fails, - Remove the `autobuild` step from your {% data variables.product.prodname_code_scanning %} workflow and add specific build steps. For information about editing the workflow, see "[Configuring {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/configuring-code-scanning#editing-a-code-scanning-workflow)." For more information about replacing the `autobuild` step, see "[Configuring the {% data variables.product.prodname_codeql %} workflow for compiled languages](/code-security/secure-coding/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)." -- If your workflow doesn't explicitly specify the languages to analyze, {% data variables.product.prodname_codeql %} implicitly detects the supported languages in your code base. In this configuration, out of the compiled languages C/C++, C#, and Java, {% data variables.product.prodname_codeql %} only analyzes the language with the most source files. Edit the workflow and add a build matrix specifying the languages you want to analyze. The default CodeQL analysis workflow uses such a matrix. +- If your workflow doesn't explicitly specify the languages to analyze, {% data variables.product.prodname_codeql %} implicitly detects the supported languages in your code base. In this configuration, out of the compiled languages C/C++, C#, and Java, {% data variables.product.prodname_codeql %} only analyzes the language with the most source files. Edit the workflow and add a matrix specifying the languages you want to analyze. The default CodeQL analysis workflow uses such a matrix. The following extracts from a workflow show how you can use a matrix within the job strategy to specify languages, and then reference each language within the "Initialize {% data variables.product.prodname_codeql %}" step: @@ -190,7 +190,7 @@ If you use self-hosted runners to run {% data variables.product.prodname_codeql ### Use matrix builds to parallelize the analysis -The default {% data variables.product.prodname_codeql_workflow %} uses a build matrix of languages, which causes the analysis of each language to run in parallel. If you have specified the languages you want to analyze directly in the "Initialize CodeQL" step, analysis of each language will happen sequentially. To speed up analysis of multiple languages, modify your workflow to use a matrix. For more information, see the workflow extract in "[Automatic build for a compiled language fails](#automatic-build-for-a-compiled-language-fails)" above. +The default {% data variables.product.prodname_codeql_workflow %} uses a matrix of languages, which causes the analysis of each language to run in parallel. If you have specified the languages you want to analyze directly in the "Initialize CodeQL" step, analysis of each language will happen sequentially. To speed up analysis of multiple languages, modify your workflow to use a matrix. For more information, see the workflow extract in "[Automatic build for a compiled language fails](#automatic-build-for-a-compiled-language-fails)" above. ### Reduce the amount of code being analyzed in a single workflow diff --git a/content/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/committing-and-reviewing-changes-to-your-project.md b/content/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/committing-and-reviewing-changes-to-your-project.md index d685c0ca15..2cb8b56fab 100644 --- a/content/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/committing-and-reviewing-changes-to-your-project.md +++ b/content/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/committing-and-reviewing-changes-to-your-project.md @@ -31,8 +31,8 @@ To change how you view diffs, in the top-right corner of the diff view, click {% ![Diff option menu](/assets/images/help/desktop/diff-selection.png) -If you need to see more of the file than {% data variables.product.prodname_desktop %} shows by default, you can expand the diff. -- To see the next few lines above or below the highlighted changes, click the arrow above or below the line numbers. +If you need to see more of the file than {% data variables.product.prodname_desktop %} shows by default, you can expand the diff. +- To see the next few lines above or below the highlighted changes, click the arrow above or below the line numbers. - To see the entire file, right-click in the diff view and click **Expand Whole File**. ![Expand diff view](/assets/images/help/desktop/expand-diff-view.png) @@ -122,3 +122,11 @@ Once you're satisfied with the changes you've chosen to include in your commit, ![Protected branch warning](/assets/images/help/desktop/protected-branch-warning.png) {% data reusables.desktop.push-origin %} + +6. If you have a pull request based off the branch you are working on, {% data variables.product.prodname_desktop %} will display the status of the checks that have run for the pull request. For more information about checks, see "[Viewing and re-running checks in GitHub Desktop](/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/viewing-and-re-running-checks-in-github-desktop)." + + ![Checks display next to branch name](/assets/images/help/desktop/checks-dialog.png) + + If a pull request has not been created for the current branch, {% data variables.product.prodname_desktop %} will give you the option to create one. For more information, see "[Creating an issue or pull request](/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/creating-an-issue-or-pull-request)." + + ![Creating a pull request](/assets/images/help/desktop/mac-create-pull-request.png) diff --git a/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/configuring-notifications-in-github-desktop.md b/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/configuring-notifications-in-github-desktop.md new file mode 100644 index 0000000000..23ffff371a --- /dev/null +++ b/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/configuring-notifications-in-github-desktop.md @@ -0,0 +1,62 @@ +--- +title: Configuring notifications in GitHub Desktop +shortTitle: Configuring notifications +intro: '{% data variables.product.prodname_desktop %} will keep you up-to-date with notifications about events that occur in your pull request branch.' +versions: + fpt: '*' +--- +## About notifications in {% data variables.product.prodname_desktop %} + +{% data variables.product.prodname_desktop %} will show a system notification for events that occur in the currently selected repository. Notifications will be shown when: + +- Pull request checks have failed. +- A pull request review is left with a comment, approval, or requested changes. + +Clicking the notification will switch application focus to {% data variables.product.prodname_desktop %} and provide more detailed information. + +## Notifications about pull request check failures + +When changes are made to a pull request branch, you will receive a notification if the checks fail. + +![pull request checks failed notification](/assets/images/help/desktop/pull-request-checks-failed-notification.png) + +Clicking the notification will display a dialog with details about the checks. Once you've reviewed why the checks have failed, you can re-run the checks, or quickly switch to the pull request branch to get started on fixing the errors. For more information, see "[Viewing and re-running checks in GitHub Desktop](/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/viewing-and-re-running-checks-in-github-desktop)." + +![checks failed dialog](/assets/images/help/desktop/checks-failed-dialog.png) +## Notifications for pull request reviews + +{% data variables.product.prodname_desktop %} will surface a system notification when a teammate has approved, commented, or requested changes in your pull request. See "[About pull request reviews](/github/collaborating-with-issues-and-pull-requests/about-pull-request-reviews)" for more information on pull request reviews. + +![Pull request review notification](/assets/images/help/desktop/pull-request-review-notification.png) + +Clicking the notification will switch application focus to {% data variables.product.prodname_desktop %} and provide more context for the pull request review comment. + +![pull request review dialog](/assets/images/help/desktop/pull-request-review-dialog.png) +## Enabling notifications + +If system notifications are disabled for {% data variables.product.prodname_desktop %} you can follow the steps below to enable them. + +{% mac %} + +1. Click the **Apple** menu, then select **System Preferences**. +2. Select **Notifications & Focus**. +3. Select **{% data variables.product.prodname_desktop %}** from the list of applications. +4. Click **Allow Notifications**. + +![macOS Notifications & Focus](/assets/images/help/desktop/mac-enable-notifications.png) + +For more information about macOS system notifications, see "[Use notifications on your Mac](https://support.apple.com/en-us/HT204079)." + +{% endmac %} + +{% windows %} + +1. Open the **Start** menu, then select **Settings**. +2. Select **System**, then click **Notifications**. +3. Find **{% data variables.product.prodname_desktop %}** in the application list and click **On**. + +![Enable Windows Notifications](/assets/images/help/desktop/windows-enable-notifications.png) + +For more information about Windows system notifications, see "[Change notification settings in Windows](https://support.microsoft.com/en-us/windows/change-notification-settings-in-windows-8942c744-6198-fe56-4639-34320cf9444e)." + +{% endwindows %} \ No newline at end of file diff --git a/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/index.md b/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/index.md index fbd4c10c20..82b7de9176 100644 --- a/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/index.md +++ b/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/index.md @@ -8,6 +8,8 @@ versions: children: - /creating-an-issue-or-pull-request - /viewing-a-pull-request-in-github-desktop + - /viewing-and-re-running-checks-in-github-desktop + - /configuring-notifications-in-github-desktop - /changing-a-remotes-url-from-github-desktop shortTitle: Work with your remote repo --- diff --git a/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/viewing-a-pull-request-in-github-desktop.md b/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/viewing-a-pull-request-in-github-desktop.md index cbbd24efa4..1bf3e5724a 100644 --- a/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/viewing-a-pull-request-in-github-desktop.md +++ b/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/viewing-a-pull-request-in-github-desktop.md @@ -14,6 +14,8 @@ You can view pull requests that you or your collaborators have proposed in {% da When you view a pull request in {% data variables.product.prodname_desktop %}, you can see a history of commits that contributors made. You can also see which files the commits modified, added, or deleted. From {% data variables.product.prodname_desktop %}, you can open repositories in your preferred text editor to view any changes or make additional changes. After reviewing changes in a pull request, you can give feedback on {% data variables.product.prodname_dotcom %}. For more information, see "[About pull request reviews](/github/collaborating-with-issues-and-pull-requests/about-pull-request-reviews)." +If checks have been enabled in your repository, {% data variables.product.prodname_desktop %} will show the status of the checks on the pull request and allow you to re-run checks. For more information, see "[Viewing and re-running checks in GitHub Desktop](/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/viewing-and-re-running-checks-in-github-desktop)." + ## Viewing a pull request in {% data variables.product.prodname_desktop %} {% data reusables.desktop.current-branch-menu %} {% data reusables.desktop.click-pull-requests %} diff --git a/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/viewing-and-re-running-checks-in-github-desktop.md b/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/viewing-and-re-running-checks-in-github-desktop.md new file mode 100644 index 0000000000..b6f77b98f0 --- /dev/null +++ b/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/viewing-and-re-running-checks-in-github-desktop.md @@ -0,0 +1,28 @@ +--- +title: Viewing and re-running checks in GitHub Desktop +shortTitle: Viewing and re-running checks +intro: 'You can view the status of checks and re-run them in {% data variables.product.prodname_desktop %}.' +versions: + fpt: '*' +--- +## About checks in {% data variables.product.prodname_desktop %} + +{% data variables.product.prodname_desktop %} displays the status of checks that have run in your pull request branches. The checks badge next to the branch name will display the *pending, passing,* or *failing* state of the checks. You can also re-run all, failed, or individual checks when viewing the status of the checks in {% data variables.product.prodname_desktop %}. For more information on setting up checks in your repository, see "[About status checks](/github/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks)." + +{% data variables.product.prodname_desktop %} will also show a system notification when checks fail. For more information on enabling notifications, see "[Configuring notifications in GitHub Desktop](/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/configuring-notifications-in-github-desktop)." + +## Viewing and re-running checks + +{% data reusables.desktop.current-branch-menu %} +{% data reusables.desktop.click-pull-requests %} + ![Pull Requests tab in the Current Branch drop-down menu](/assets/images/help/desktop/branch-drop-down-pull-request-tab.png) +{% data reusables.desktop.choose-pr-from-list %} + ![List of open pull requests in the repository](/assets/images/help/desktop/click-pull-request.png) +4. Click on the pull request number, to the right of the pull request branch name. + ![Checks display next to branch name](/assets/images/help/desktop/checks-dialog.png) +5. To re-run failed checks, click **{% octicon "sync" aria-label="The sync icon" %} Re-run** and select **Re-run Failed Checks**. + ![Re-run failed checks](/assets/images/help/desktop/re-run-failed-checks.png) +6. To re-run individual checks, hover over the individual check you want to re-run and select the {% octicon "sync" aria-label="The sync icon" %} icon to re-run the check. + ![Re-run individual checks](/assets/images/help/desktop/re-run-individual-checks.png) +7. You will see a confirmation dialog with the summary of the checks that will be re-run. Click **Re-run Checks** to confirm that you want to perform the re-run. + ![Re-run confirmation dialog](/assets/images/help/desktop/re-run-confirmation-dialog.png) \ No newline at end of file diff --git a/contributing/content-templates.md b/contributing/content-templates.md index 89ac63763a..657a7f1cfd 100644 --- a/contributing/content-templates.md +++ b/contributing/content-templates.md @@ -300,7 +300,7 @@ versions: - Include any additional features the setup action might provide that are useful to CI. - If applicable, provide examples of configuring exact versions or major/minor versions. - Include information about software already installed on GitHub-hosted runners or software configuration necessary to build and test the project. - - Provide examples of configuring build matrix strategies. + - Provide examples of configuring matrix strategies. - Link out to any docs about available software on the GitHub-hosted runners. (Ex. https://docs.github.com/en/actions/reference/software-installed-on-github-hosted-runners). - Include code samples. --> diff --git a/data/features/actions-inherit-secrets-reusable-workflows.yml b/data/features/actions-inherit-secrets-reusable-workflows.yml new file mode 100644 index 0000000000..2b7e38e99c --- /dev/null +++ b/data/features/actions-inherit-secrets-reusable-workflows.yml @@ -0,0 +1,7 @@ +# Reference: #6920 +# Documentation for inheriting secrets from the calling workflow +versions: + fpt: '*' + ghec: '*' + ghes: '>= 3.6' + ghae: diff --git a/data/release-notes/enterprise-server/3-4/2.yml b/data/release-notes/enterprise-server/3-4/2.yml index d4b2f95d8d..4b631dfb51 100644 --- a/data/release-notes/enterprise-server/3-4/2.yml +++ b/data/release-notes/enterprise-server/3-4/2.yml @@ -13,17 +13,12 @@ sections: - When converting a user account to an organization, if the user account was an owner of the {% data variables.product.prodname_ghe_server %} enterprise account, the converted organization would incorrectly appear in the enterprise owner list. - The `/stafftools/users/ip_addresses/:address` page responded with a `500 Internal Server Error` when attempting to display the page for an IPv6 address. - Creating an impersonation OAuth token using the Enterprise Administration REST API resulted in an error when an integration matching the OAuth Application ID already existed. - - | - When using SAML encrypted assertions with {% data variables.product.prodname_ghe_server %} 3.4.0 and 3.4.1, a new XML attribute `WantAssertionsEncrypted` in the `SPSSODescriptor` contains an invalid attribute for SAML metadata. IdPs that consume this SAML metadata endpoint may encounter errors when validating the SAML metadata XML schema. A fix will be available in the next patch release. [Updated: 2022-04-11] - - To work around this problem, you can take one of the two following actions. - - Reconfigure the IdP by uploading a static copy of the SAML metadata without the `WantAssertionsEncrypted` attribute. - - Copy the SAML metadata, remove `WantAssertionsEncrypted` attribute, host it on a web server, and reconfigure the IdP to point to that URL. changes: - Added support for replica domain names that are more than 63 characters. - Configuration errors that halt a config apply run are now output to the terminal in addition to the configuration log. - If {% data variables.product.prodname_GH_advanced_security %} features are enabled on your instance, the performance of background jobs has improved when processing batches for repository contributions. + known_issues: - On a freshly set up {% data variables.product.prodname_ghe_server %} instance without any users, an attacker could create the first admin user. - Custom firewall rules are removed during the upgrade process. diff --git a/data/reusables/actions/jobs/about-matrix-strategy.md b/data/reusables/actions/jobs/about-matrix-strategy.md new file mode 100644 index 0000000000..6b7e9ceee1 --- /dev/null +++ b/data/reusables/actions/jobs/about-matrix-strategy.md @@ -0,0 +1 @@ +A matrix strategy lets you use variables in a single job definition to automatically create multiple job runs that are based the combinations of the variables. For example, you can use a matrix strategy to test your code in multiple versions of a language or on multiple operating systems. diff --git a/data/reusables/actions/jobs/matrix-add-with-include.md b/data/reusables/actions/jobs/matrix-add-with-include.md new file mode 100644 index 0000000000..166eb08dcb --- /dev/null +++ b/data/reusables/actions/jobs/matrix-add-with-include.md @@ -0,0 +1,29 @@ +For example, this matrix will run 10 jobs, one for each combination of `os` and `version` in the matrix, plus a job for the `os` value of `windows-latest` and `version` value of `17`. + +```yaml +jobs: + example_matrix: + strategy: + matrix: + os: [macos-latest, windows-latest, ubuntu-latest] + version: [12, 14, 16] + include: + - os: windows-latest + version: 17 +``` + +If you don't specify any matrix variables, all configurations under `include` will run. For example, the following workflow would run two jobs, one for each `include` entry. This lets you take advantage of the matrix strategy without having a fully populated matrix. + +```yaml +jobs: + includes_only: + runs-on: ubuntu-latest + strategy: + matrix: + include: + - site: "production" + datacenter: "site-a" + - site: "staging" + datacenter: "site-b" + +``` \ No newline at end of file diff --git a/data/reusables/actions/jobs/matrix-exclude.md b/data/reusables/actions/jobs/matrix-exclude.md new file mode 100644 index 0000000000..6a3044674c --- /dev/null +++ b/data/reusables/actions/jobs/matrix-exclude.md @@ -0,0 +1,22 @@ +To remove specific configurations defined in the matrix, use `jobs..strategy.matrix.exclude`. An excluded configuration only has to be a partial match for it to be excluded. For example, the following workflow will run nine jobs: one job for each of the 12 configurations, minus the one excluded job that matches `{os: macos-latest, version: 12, environment: production}`, and the two excluded jobs that match `{os: windows-latest, version: 16}`. + +```yaml +strategy: + matrix: + os: [macos-latest, windows-latest] + version: [12, 14, 16] + environment: [staging, production] + exclude: + - os: macos-latest + version: 12 + environment: production + - os: windows-latest + version: 16 +runs-on: {% raw %}${{ matrix.os }}{% endraw %} +``` + +{% note %} + +**Note:** All `include` combinations are processed after `exclude`. This allows you to use `include` to add back combinations that were previously excluded. + +{% endnote %} diff --git a/data/reusables/actions/jobs/matrix-expand-with-include.md b/data/reusables/actions/jobs/matrix-expand-with-include.md new file mode 100644 index 0000000000..f8075468a5 --- /dev/null +++ b/data/reusables/actions/jobs/matrix-expand-with-include.md @@ -0,0 +1,22 @@ +For example, the following workflow will run six jobs, one for each combination of `os` and `node`. When the job for the `os` value of `windows-latest` and `node` value of `16` runs, an additional variable called `npm` with the value of `6` will be included in the job. + +```yaml +jobs: + example_matrix: + strategy: + matrix: + os: [windows-latest, ubuntu-latest] + node: [12, 14, 16] + include: + - os: windows-latest + node: 16 + npm: 6 + runs-on: {% raw %}${{ matrix.os }}{% endraw %} + steps: + - uses: {% data reusables.actions.action-setup-node %} + with: + node-version: {% raw %}${{ matrix.node }}{% endraw %} + - if: {% raw %}${{ matrix.npm }}{% endraw %} + run: npm install -g npm@{% raw %}${{ matrix.npm }}{% endraw %} + - run: npm --version +``` diff --git a/data/reusables/actions/jobs/matrix-from-context.md b/data/reusables/actions/jobs/matrix-from-context.md new file mode 100644 index 0000000000..f6eae717e8 --- /dev/null +++ b/data/reusables/actions/jobs/matrix-from-context.md @@ -0,0 +1,30 @@ +You can use contexts to create matrices. For more information about contexts, see "[Contexts](/actions/learn-github-actions/contexts)." + +For example, the following workflow triggers on the `repository_dispatch` event and uses information from the event payload to build the matrix. When a repository dispatch event is created with a payload like the one below, the matrix `version` variable will have a value of `[12, 14, 16]`. For more information about the `repository_dispatch` trigger, see "[Events that trigger workflows](/actions/using-workflows/events-that-trigger-workflows#repository_dispatch)." + +```json +{ + "event_type": "test", + "client_payload": { + "versions": [12, 14, 16] + } +} +``` + +```yaml +on: + repository_dispatch: + types: + - test + +jobs: + example_matrix: + runs-on: ubuntu-latest + strategy: + matrix: + version: {% raw %}${{ github.event.client_payload.versions }}{% endraw %} + steps: + - uses: {% data reusables.actions.action-setup-node %} + with: + node-version: {% raw %}${{ matrix.version }}{% endraw %} +``` diff --git a/data/reusables/actions/jobs/matrix-include.md b/data/reusables/actions/jobs/matrix-include.md new file mode 100644 index 0000000000..cf5e4b1a5d --- /dev/null +++ b/data/reusables/actions/jobs/matrix-include.md @@ -0,0 +1,38 @@ +Use `jobs..strategy.matrix.include` to expand existing matrix configurations or to add new configurations. The value of `include` is a list of objects. + +For each object in the `include` list, the key:value pairs in the object will be added to each of the matrix combinations if none of the key:value pairs overwrite any of the original matrix values. If the object cannot be added to any of the matrix combinations, a new matrix combination will be created instead. Note that the original matrix values will not be overwritten, but added matrix values can be overwritten. + +For example, this matrix: + +```yaml +strategy: + matrix: + fruit: [apple, pear] + animal: [cat, dog] + include: + - color: green + - color: pink + animal: cat + - fruit: apple + shape: circle + - fruit: banana + - fruit: banana + animal: cat +``` + +will result in six jobs with the following matrix combinations: + +- `{fruit: apple, animal: cat, color: pink, shape: circle}` +- `{fruit: apple, animal: dog, color: green, shape: circle}` +- `{fruit: pear, animal: cat, color: pink}` +- `{fruit: pear, animal: dog, color: green}` +- `{fruit: banana}` +- `{fruit: banana, animal: cat}` + +following this logic: + +- `{color: green}` is added to all of the original matrix combinations because it can be added without overwriting any part of the original combinations. +- `{color: pink, animal: cat}` adds `color:pink` only to the original matrix combinations that include `animal: cat`. This overwrites the `color: green` that was added by the previous `include` entry. +- `{fruit: apple, shape: circle}` adds `shape: circle` only to the original matrix combinations that include `fruit: apple`. +- `{fruit: banana}` cannot be added to any original matrix combination without overwriting a value, so it is added as an additional matrix combination. +- `{fruit: banana, animal: cat}` cannot be added to any original matrix combination without overwriting a value, so it is added as an additional matrix combination. It does not add to the `{fruit: banana}` matrix combination because that combination was not one of the original matrix combinations. diff --git a/data/reusables/actions/jobs/multi-dimension-matrix.md b/data/reusables/actions/jobs/multi-dimension-matrix.md new file mode 100644 index 0000000000..5041ca5554 --- /dev/null +++ b/data/reusables/actions/jobs/multi-dimension-matrix.md @@ -0,0 +1,22 @@ +You can specify multiple variables to create a multi-dimensional matrix. A job will run for each possible combination of the variables. + +For example, the following workflow specifies two variables: + +- Two operating systems specified in the `os` variable +- Three Node.js versions specified in the `version` variable + +The workflow will run six jobs, one for each combination of the `os` and `version` variables. Each job will set the `runs-on` value to the current `os` value and will pass the current `version` value to the `actions/setup-node` action. + +```yaml +jobs: + example_matrix: + strategy: + matrix: + os: [ubuntu-18.04, ubuntu-20.04] + version: [10, 12, 14] + runs-on: {% raw %}${{ matrix.os }}{% endraw %} + steps: + - uses: {% data reusables.actions.action-setup-node %} + with: + node-version: {% raw %}${{ matrix.version }}{% endraw %} +``` diff --git a/data/reusables/actions/jobs/section-using-a-build-matrix-for-your-jobs-failfast.md b/data/reusables/actions/jobs/section-using-a-build-matrix-for-your-jobs-failfast.md index 8d0675e225..e1bba5d92a 100644 --- a/data/reusables/actions/jobs/section-using-a-build-matrix-for-your-jobs-failfast.md +++ b/data/reusables/actions/jobs/section-using-a-build-matrix-for-your-jobs-failfast.md @@ -1 +1,23 @@ -When `jobs..strategy.fail-fast` is set to `true`, {% data variables.product.prodname_dotcom %} cancels all in-progress jobs in the matrix if any `matrix` job fails. Default: `true` +You can control how job failures are handled with `jobs..strategy.fail-fast` and `jobs..continue-on-error`. + +`jobs..strategy.fail-fast` applies to the entire matrix. If `jobs..strategy.fail-fast` is set to `true`, {% data variables.product.product_name %} will cancel all in-progress and queued jobs in the matrix if any job in the matrix fails. This property defaults to `true`. + +`jobs..continue-on-error` applies to a single job. If `jobs..continue-on-error` is `true`, other jobs in the matrix will continue running even if the job with `jobs..continue-on-error: true` fails. + +You can use `jobs..strategy.fail-fast` and `jobs..continue-on-error` together. For example, the following workflow will start four jobs. For each job, `continue-on-error` is determined by the value of `matrix.experimental`. If any of the jobs with `continue-on-error: false` fail, all jobs that are in progress or queued will be cancelled. If the job with `continue-on-error: true` fails, the other jobs will not be affected. + + +```yaml +jobs: + test: + runs-on: ubuntu-latest + continue-on-error: {% raw %}${{ matrix.experimental }}{% endraw %} + strategy: + fail-fast: true + matrix: + version: [6, 7, 8] + experimental: [false] + include: + - version: 9 + experimental: true +``` diff --git a/data/reusables/actions/jobs/section-using-a-build-matrix-for-your-jobs-matrix.md b/data/reusables/actions/jobs/section-using-a-build-matrix-for-your-jobs-matrix.md deleted file mode 100644 index c7d820b181..0000000000 --- a/data/reusables/actions/jobs/section-using-a-build-matrix-for-your-jobs-matrix.md +++ /dev/null @@ -1,122 +0,0 @@ - -Use `jobs..strategy.matrix` to define a matrix of different job configurations. A matrix allows you to create multiple jobs by performing variable substitution in a single job definition. For example, you can use a matrix to create jobs for more than one supported version of a programming language, operating system, or tool. A matrix reuses the job's configuration and creates a job for each matrix you configure. - -{% data reusables.actions.usage-matrix-limits %} - -Each option you define in the `matrix` has a key and value. The keys you define become properties in the `matrix` context and you can reference the property in other areas of your workflow file. For example, if you define the key `os` that contains an array of operating systems, you can use the `matrix.os` property as the value of the `runs-on` keyword to create a job for each operating system. For more information, see "[Contexts](/actions/learn-github-actions/contexts)." - -The order that you define a `matrix` matters. The first option you define will be the first job that runs in your workflow. - -#### Example: Running multiple versions of Node.js - -You can specify a matrix by supplying an array for the configuration options. For example, if the runner supports Node.js versions 10, 12, and 14, you could specify an array of those versions in the `matrix`. - -This example creates a matrix of three jobs by setting the `node` key to an array of three Node.js versions. To use the matrix, the example sets the `matrix.node` context property as the value of the `setup-node` action's input parameter `node-version`. As a result, three jobs will run, each using a different Node.js version. - -```yaml -strategy: - matrix: - node: [10, 12, 14] -steps: - # Configures the node version used on GitHub-hosted runners - - uses: {% data reusables.actions.action-setup-node %} - with: - # The Node.js version to configure - node-version: {% raw %}${{ matrix.node }}{% endraw %} -``` - -The `setup-node` action is the recommended way to configure a Node.js version when using {% data variables.product.prodname_dotcom %}-hosted runners. For more information, see the [`setup-node`](https://github.com/actions/setup-node) action. - -#### Example: Running with multiple operating systems - -You can create a matrix to run workflows on more than one runner operating system. You can also specify more than one matrix configuration. This example creates a matrix of 6 jobs: - -- 2 operating systems specified in the `os` array -- 3 Node.js versions specified in the `node` array - -{% data reusables.repositories.actions-matrix-builds-os %} - -```yaml -runs-on: {% raw %}${{ matrix.os }}{% endraw %} -strategy: - matrix: - os: [ubuntu-18.04, ubuntu-20.04] - node: [10, 12, 14] -steps: - - uses: {% data reusables.actions.action-setup-node %} - with: - node-version: {% raw %}${{ matrix.node }}{% endraw %} -``` - -{% ifversion ghae %} -For more information about the configuration of self-hosted runners, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners)." -{% else %}To find supported configuration options for {% data variables.product.prodname_dotcom %}-hosted runners, see "[Virtual environments for {% data variables.product.prodname_dotcom %}-hosted runners](/actions/automating-your-workflow-with-github-actions/virtual-environments-for-github-hosted-runners)." -{% endif %} - -#### Example: Including additional values in combinations - -You can add additional configuration options to a build matrix job that already exists. For example, if you want to use a specific version of `npm` when the job that uses `windows-latest` and version 8 of `node` runs, you can use `include` to specify that additional option. - -{% raw %} -```yaml -runs-on: ${{ matrix.os }} -strategy: - matrix: - os: [macos-latest, windows-latest, ubuntu-18.04] - node: [8, 10, 12, 14] - include: - # includes a new variable of npm with a value of 6 - # for the matrix leg matching the os and version - - os: windows-latest - node: 8 - npm: 6 -``` -{% endraw %} - -#### Example: Including new combinations - -You can use `include` to add new jobs to a build matrix. Any unmatched include configurations are added to the matrix. For example, if you want to use `node` version 14 to build on multiple operating systems, but wanted one extra experimental job using node version 15 on Ubuntu, you can use `include` to specify that additional job. - -{% raw %} -```yaml -runs-on: ${{ matrix.os }} -strategy: - matrix: - node: [14] - os: [macos-latest, windows-latest, ubuntu-18.04] - include: - - node: 15 - os: ubuntu-18.04 - experimental: true -``` -{% endraw %} - -#### Example: Excluding configurations from a matrix - -You can remove a specific configurations defined in the build matrix using the `exclude` option. Using `exclude` removes a job defined by the build matrix. The number of jobs is the cross product of the number of operating systems (`os`) included in the arrays you provide, minus any subtractions (`exclude`). - -{% raw %} -```yaml -runs-on: ${{ matrix.os }} -strategy: - matrix: - os: [macos-latest, windows-latest, ubuntu-18.04] - node: [8, 10, 12, 14] - exclude: - # excludes node 8 on macOS - - os: macos-latest - node: 8 -``` -{% endraw %} - -{% note %} - -**Note:** All `include` combinations are processed after `exclude`. This allows you to use `include` to add back combinations that were previously excluded. - -{% endnote %} - -### Using environment variables in a matrix - -You can add custom environment variables for each test combination by using the `include` key. You can then refer to the custom environment variables in a later step. - -{% data reusables.actions.matrix-variable-example %} diff --git a/data/reusables/actions/jobs/section-using-a-build-matrix-for-your-jobs-max-parallel.md b/data/reusables/actions/jobs/section-using-a-build-matrix-for-your-jobs-max-parallel.md index 224396244a..fd58b0c321 100644 --- a/data/reusables/actions/jobs/section-using-a-build-matrix-for-your-jobs-max-parallel.md +++ b/data/reusables/actions/jobs/section-using-a-build-matrix-for-your-jobs-max-parallel.md @@ -1,6 +1,13 @@ -Use `jobs..strategy.max-parallel` to set the maximum number of jobs that can run simultaneously when using a `matrix` job strategy. By default, {% data variables.product.prodname_dotcom %} will maximize the number of jobs run in parallel depending on the available runners on {% data variables.product.prodname_dotcom %}-hosted virtual machines. +By default, {% data variables.product.product_name %} will maximize the number of jobs run in parallel depending on runner availability. To set the maximum number of jobs that can run simultaneously when using a `matrix` job strategy, use `jobs..strategy.max-parallel`. + +For example, the following workflow will run a maximum of two jobs at a time, even if there are runners available to run all six jobs at once. ```yaml -strategy: - max-parallel: 2 +jobs: + example_matrix: + strategy: + max-parallel: 2 + matrix: + version: [10, 12, 14] + os: [ubuntu-latest, windows-latest] ``` diff --git a/data/reusables/actions/jobs/section-using-a-build-matrix-for-your-jobs-strategy.md b/data/reusables/actions/jobs/section-using-a-build-matrix-for-your-jobs-strategy.md deleted file mode 100644 index c4f74652af..0000000000 --- a/data/reusables/actions/jobs/section-using-a-build-matrix-for-your-jobs-strategy.md +++ /dev/null @@ -1 +0,0 @@ -Use `jobs..strategy` to create a build matrix for your jobs. You can define different variations to run each job in. diff --git a/data/reusables/actions/jobs/single-dimension-matrix.md b/data/reusables/actions/jobs/single-dimension-matrix.md new file mode 100644 index 0000000000..252ff44568 --- /dev/null +++ b/data/reusables/actions/jobs/single-dimension-matrix.md @@ -0,0 +1,15 @@ +You can specify a single variable to create a single-dimension matrix. + +For example, the following workflow defines the variable `version` with the values `[10, 12, 14]`. The workflow will run three jobs, one for each value in the variable. Each job will access the `version` value through the `matrix.version` context and pass the value as `node-version` to the `actions/setup-node` action. + +```yaml +jobs: + example_matrix: + strategy: + matrix: + version: [10, 12, 14] + steps: + - uses: {% data reusables.actions.action-setup-node %} + with: + node-version: {% raw %}${{ matrix.version }}{% endraw %} +``` diff --git a/data/reusables/actions/jobs/using-matrix-strategy.md b/data/reusables/actions/jobs/using-matrix-strategy.md new file mode 100644 index 0000000000..58d520c087 --- /dev/null +++ b/data/reusables/actions/jobs/using-matrix-strategy.md @@ -0,0 +1,25 @@ +Use `jobs..strategy.matrix` to define a matrix of different job configurations. Within your matrix, define one or more variables followed by an array of values. For example, the following matrix has a veriable called `version` with the value `[10, 12, 14]` and a variable called `os` with the value `[ubuntu-latest, windows-latest]`: + +```yaml +jobs: + example_matrix: + strategy: + matrix: + version: [10, 12, 14] + os: [ubuntu-latest, windows-latest] +``` + +A job will run for each possible combination of the variables. In this example, the workflow will run six jobs, one for each combination of the `os` and `version` variables. + +By default, {% data variables.product.product_name %} will maximize the number of jobs run in parallel depending on runner availability. The order of the variables in the matrix determines the order in which the jobs are created. The first variable you define will be the first job that is created in your workflow run. For example, the above matrix will create the jobs in the following order: + +- `{version: 10, os: ubuntu-latest}` +- `{version: 10, os: windows-latest}` +- `{version: 12, os: ubuntu-latest}` +- `{version: 12, os: windows-latest}` +- `{version: 14, os: ubuntu-latest}` +- `{version: 14, os: windows-latest}` + +A matrix will generate a maximum of 256 jobs per workflow run. This limit applies to both {% data variables.product.product_name %}-hosted and self-hosted runners. + +The variables that you define become properties in the `matrix` context, and you can reference the property in other areas of your workflow file. In this example, you can use `matrix.version` and `matrix.os` to access the current value of `version` and `os` that the job is using. For more information, see "[Contexts](/actions/learn-github-actions/contexts)." diff --git a/data/reusables/actions/pass-inputs-to-reusable-workflows.md b/data/reusables/actions/pass-inputs-to-reusable-workflows.md index ce6074f0c9..32d11ea33b 100644 --- a/data/reusables/actions/pass-inputs-to-reusable-workflows.md +++ b/data/reusables/actions/pass-inputs-to-reusable-workflows.md @@ -11,3 +11,19 @@ jobs: envPAT: ${{ secrets.envPAT }} ``` {% endraw %} + +{% if actions-inherit-secrets-reusable-workflows %} +Workflows that call reusable workflows in the same organization or enterprise can use the `inherit` keyword to implicitly pass the secrets. + +{% raw %} +```yaml +jobs: + call-workflow-passing-data: + uses: octo-org/example-repo/.github/workflows/reusable-workflow.yml@main + with: + username: mona + secrets: inherit +``` +{% endraw %} + +{%endif%} \ No newline at end of file diff --git a/data/reusables/repositories/actions-matrix-builds-os.md b/data/reusables/repositories/actions-matrix-builds-os.md deleted file mode 100644 index 228b240daf..0000000000 --- a/data/reusables/repositories/actions-matrix-builds-os.md +++ /dev/null @@ -1 +0,0 @@ -When you define a matrix of operating systems, you must set the value of `runs-on` to the `matrix.os` context property you defined. diff --git a/lib/search/indexes/github-docs-3.1-cn-records.json.br b/lib/search/indexes/github-docs-3.1-cn-records.json.br index 8c8d8f792c..05c87b09fe 100644 --- a/lib/search/indexes/github-docs-3.1-cn-records.json.br +++ b/lib/search/indexes/github-docs-3.1-cn-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:af92f43836e6ee457a69cc24fce354ef9f794c612b66f20c5230555e0e19fcff -size 675448 +oid sha256:cf9b6dc0c924f8338f33a86153363c19a8472998902f8565ae19369847ce0360 +size 674661 diff --git a/lib/search/indexes/github-docs-3.1-cn.json.br b/lib/search/indexes/github-docs-3.1-cn.json.br index c8ad4a6504..ddc3a71600 100644 --- a/lib/search/indexes/github-docs-3.1-cn.json.br +++ b/lib/search/indexes/github-docs-3.1-cn.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:90b9a68c5f82348bb9c779105c9e3eaf874a793c1dd606c884d3bc8d33356679 -size 1359777 +oid sha256:31820e3b8a49b9794e7e62ae4f4741adfed516d3081a21a3354a6d7afbb05017 +size 1358189 diff --git a/lib/search/indexes/github-docs-3.1-en-records.json.br b/lib/search/indexes/github-docs-3.1-en-records.json.br index e29db9651a..77c4ab66c3 100644 --- a/lib/search/indexes/github-docs-3.1-en-records.json.br +++ b/lib/search/indexes/github-docs-3.1-en-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:3e7e89ff99efeec3f128287c4746233769f67cc51b62ea4232ea55e8e97acfc5 -size 907440 +oid sha256:96a12f5882dbe72a90f6b05d2348068bae6156fc1e22aa78d2b37aceda2c72a7 +size 907612 diff --git a/lib/search/indexes/github-docs-3.1-en.json.br b/lib/search/indexes/github-docs-3.1-en.json.br index d33e4e988d..225ad763db 100644 --- a/lib/search/indexes/github-docs-3.1-en.json.br +++ b/lib/search/indexes/github-docs-3.1-en.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:fbcc422edca6a9a1cc86a7e89b6ba612c5111e7a5dbb6b1801c48611d42b7405 -size 3487266 +oid sha256:e428bc80429c73f63f772d70a754c12a5e07b066881f4138de201f64dff8eb39 +size 3491653 diff --git a/lib/search/indexes/github-docs-3.1-es-records.json.br b/lib/search/indexes/github-docs-3.1-es-records.json.br index ad0b7c51a8..76fcc2fcb1 100644 --- a/lib/search/indexes/github-docs-3.1-es-records.json.br +++ b/lib/search/indexes/github-docs-3.1-es-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:f9676a2e1a6565bdb2967fe295835e565c858d0fea4a88389603660d1b142f18 -size 623871 +oid sha256:6bc75e2abc133cea585aab1588840de3ac233286d6b8fcb8626655d39db7a5b4 +size 624580 diff --git a/lib/search/indexes/github-docs-3.1-es.json.br b/lib/search/indexes/github-docs-3.1-es.json.br index 90c38d0a4e..d094fa9eb1 100644 --- a/lib/search/indexes/github-docs-3.1-es.json.br +++ b/lib/search/indexes/github-docs-3.1-es.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:eff23a0aa5a5da74d11c569250efbd4365e4dcea5db1e3fa919fd156620ef139 -size 2626995 +oid sha256:b93304c40738bd97b1b25dae510ae0bbf1215b4c911c6ceb3d2bc6026bc0ba1d +size 2627569 diff --git a/lib/search/indexes/github-docs-3.1-ja-records.json.br b/lib/search/indexes/github-docs-3.1-ja-records.json.br index 7ded226e13..2d024aac13 100644 --- a/lib/search/indexes/github-docs-3.1-ja-records.json.br +++ b/lib/search/indexes/github-docs-3.1-ja-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:c99796742f8bedb8305a30b0af56d533c1a65d20afa5971e74a580a45fe4e641 -size 686879 +oid sha256:1a7f91bbe6b56a8755e26143bf03329181b216f13182cd647c90b74b051e376a +size 685800 diff --git a/lib/search/indexes/github-docs-3.1-ja.json.br b/lib/search/indexes/github-docs-3.1-ja.json.br index a70c93c2bb..a380b36fcc 100644 --- a/lib/search/indexes/github-docs-3.1-ja.json.br +++ b/lib/search/indexes/github-docs-3.1-ja.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:902dcd6c1bb75d4e550f3e9fa7eb4f3bf36147bfb037c9d57ede99f250eec4bc -size 3667899 +oid sha256:c872faac2991ced066b6710455fd8ad07f5fcd95de7cfcccb7a32a0ea1ccf646 +size 3662437 diff --git a/lib/search/indexes/github-docs-3.1-pt-records.json.br b/lib/search/indexes/github-docs-3.1-pt-records.json.br index a57ff322f5..837a571ef7 100644 --- a/lib/search/indexes/github-docs-3.1-pt-records.json.br +++ b/lib/search/indexes/github-docs-3.1-pt-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:581bb47bf5fb0599311bc416787bba09ed36b9170ebe18641c31712f3b8cf183 -size 616530 +oid sha256:571dab563c5de05e52d19f97e5e2880257c21f0e6b559011f49d25f244450d59 +size 615352 diff --git a/lib/search/indexes/github-docs-3.1-pt.json.br b/lib/search/indexes/github-docs-3.1-pt.json.br index 4f39bf8766..512208aaf7 100644 --- a/lib/search/indexes/github-docs-3.1-pt.json.br +++ b/lib/search/indexes/github-docs-3.1-pt.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:8224fcd8c8e7d09150203e74cec8c0513f1b9e84b1c2ef20091cae9c1d3bd70d -size 2530997 +oid sha256:e6f4ff74c09ed27ab1d4fc43e68b60fcaae9ebe0b9c697118e431edde6321e45 +size 2526220 diff --git a/lib/search/indexes/github-docs-3.2-cn-records.json.br b/lib/search/indexes/github-docs-3.2-cn-records.json.br index 661280c46e..d17e360116 100644 --- a/lib/search/indexes/github-docs-3.2-cn-records.json.br +++ b/lib/search/indexes/github-docs-3.2-cn-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:e4e1dea6e369139477c3da2c3e3e331313e9b54bdff27dd65abdf9c55beb2851 -size 691595 +oid sha256:79e6df23df2209ac1707b085bb9180c3c59bd0da3756d8fbea6992989c4c956f +size 692436 diff --git a/lib/search/indexes/github-docs-3.2-cn.json.br b/lib/search/indexes/github-docs-3.2-cn.json.br index 3a7e14ab60..c40e8d2f57 100644 --- a/lib/search/indexes/github-docs-3.2-cn.json.br +++ b/lib/search/indexes/github-docs-3.2-cn.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:95c70f90229cfebe31365d7bf60c09d74a79045ac7da4544e940faddba10f034 -size 1388890 +oid sha256:59a323360507d734ffe5e113e778a71d997306ef3d5152cc25bcf44e079ab408 +size 1388364 diff --git a/lib/search/indexes/github-docs-3.2-en-records.json.br b/lib/search/indexes/github-docs-3.2-en-records.json.br index b2bdbeea2a..ac5f68dc54 100644 --- a/lib/search/indexes/github-docs-3.2-en-records.json.br +++ b/lib/search/indexes/github-docs-3.2-en-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:d7f6243eb9a28aa0f627fbf65b354fbf91b286381e021af35de85d2a3a81f4bd -size 936239 +oid sha256:46466dab2c21c7e2a9d7c0d9b23494c86cdb9488f99f0b711408f48e4df2d9ef +size 937302 diff --git a/lib/search/indexes/github-docs-3.2-en.json.br b/lib/search/indexes/github-docs-3.2-en.json.br index 247de995c6..316375df90 100644 --- a/lib/search/indexes/github-docs-3.2-en.json.br +++ b/lib/search/indexes/github-docs-3.2-en.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:eb08d18a931a15951a3ec165fe40ef5096fb9005dbf56546988a5df90dcdc38c -size 3606110 +oid sha256:9b42f930131f2b4e5a3441941dc2042629470ef143938084ed4763d6f8134001 +size 3611216 diff --git a/lib/search/indexes/github-docs-3.2-es-records.json.br b/lib/search/indexes/github-docs-3.2-es-records.json.br index ae38314646..6debfc41aa 100644 --- a/lib/search/indexes/github-docs-3.2-es-records.json.br +++ b/lib/search/indexes/github-docs-3.2-es-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:0e797ca1944f3334fb5a479f3a7f87e55a049b45650ce1a48c019c84d65a2e67 -size 641314 +oid sha256:68ea078f5d8585badfd6cb948879dabb1fe8feb17dcbf968355af759a333cf12 +size 640723 diff --git a/lib/search/indexes/github-docs-3.2-es.json.br b/lib/search/indexes/github-docs-3.2-es.json.br index c4d042e56a..4709b0dcef 100644 --- a/lib/search/indexes/github-docs-3.2-es.json.br +++ b/lib/search/indexes/github-docs-3.2-es.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:3ac63b4274552fb0efc1b6ab83f3ad1948ad5b558bfcbad0084d88e2073dbad4 -size 2698536 +oid sha256:2f4ce65d6d0674260aa6375a8cd07b3a814e7f79f6dac5823ef402d437dea6f2 +size 2700175 diff --git a/lib/search/indexes/github-docs-3.2-ja-records.json.br b/lib/search/indexes/github-docs-3.2-ja-records.json.br index 6698a8cdb1..3bfde9cecb 100644 --- a/lib/search/indexes/github-docs-3.2-ja-records.json.br +++ b/lib/search/indexes/github-docs-3.2-ja-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:57874d26e83d9bc22f06c5ef84f27aad0ab5f8975b130f36b41b8fe8ec1f9ad5 -size 703779 +oid sha256:aac59e60eac4ce45fadbfca1ac0613d3feab06b5f80fa7ecd274e946781745f8 +size 703644 diff --git a/lib/search/indexes/github-docs-3.2-ja.json.br b/lib/search/indexes/github-docs-3.2-ja.json.br index 4a3740d940..1c6d7d3455 100644 --- a/lib/search/indexes/github-docs-3.2-ja.json.br +++ b/lib/search/indexes/github-docs-3.2-ja.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:f7a15e27326f0d942f6aeb5db51bc6526ac8e4fba78e93e2bf35ee37fa4ac7d8 -size 3760017 +oid sha256:ea0beef78f642a439cfbedd793b70b11dea7387b75c8b91dbd454923b8dd78a0 +size 3762087 diff --git a/lib/search/indexes/github-docs-3.2-pt-records.json.br b/lib/search/indexes/github-docs-3.2-pt-records.json.br index 154946c512..b4abc4b04c 100644 --- a/lib/search/indexes/github-docs-3.2-pt-records.json.br +++ b/lib/search/indexes/github-docs-3.2-pt-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:1ff182134a3b0d6fb3a482eaefc08dc460ecf663ecacac3be56d10d7f85316bc -size 631866 +oid sha256:d93c7e7fa03167a8452be39261ff0ff18159808894ac3a117686a77a97877c9d +size 630862 diff --git a/lib/search/indexes/github-docs-3.2-pt.json.br b/lib/search/indexes/github-docs-3.2-pt.json.br index 3387957ef5..edbef7a748 100644 --- a/lib/search/indexes/github-docs-3.2-pt.json.br +++ b/lib/search/indexes/github-docs-3.2-pt.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:ad8f2009b0f63fa3895bea661d3436fc2f0509d8b41b4239eabfafa81bd15211 -size 2591735 +oid sha256:be276a8594a4e65a06875cce63543fef4d8dd623fe06611a4b59b4295d6ed0d4 +size 2589426 diff --git a/lib/search/indexes/github-docs-3.3-cn-records.json.br b/lib/search/indexes/github-docs-3.3-cn-records.json.br index 63d3bcd941..2b3c21988f 100644 --- a/lib/search/indexes/github-docs-3.3-cn-records.json.br +++ b/lib/search/indexes/github-docs-3.3-cn-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:3d60e577e568dc5741a93b11d5126bab72236472be0f5fc0a3eb040fd6138429 -size 715431 +oid sha256:2cf56329e00af7ecd19860547b00af51a37dd8896dcf0dd91fcc61d51d6a8aba +size 715297 diff --git a/lib/search/indexes/github-docs-3.3-cn.json.br b/lib/search/indexes/github-docs-3.3-cn.json.br index 6547c12506..44135bfb0b 100644 --- a/lib/search/indexes/github-docs-3.3-cn.json.br +++ b/lib/search/indexes/github-docs-3.3-cn.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:e20f71c896f5a04844af5987f6e93d13b894b7639e02cd3251b1ef9e60b27e55 -size 1438703 +oid sha256:034f023d843e2408108990ae1d885f5324b358e76eaaafafaefc7ab975f412bf +size 1438315 diff --git a/lib/search/indexes/github-docs-3.3-en-records.json.br b/lib/search/indexes/github-docs-3.3-en-records.json.br index cf8f82c6b6..abeb4aa54a 100644 --- a/lib/search/indexes/github-docs-3.3-en-records.json.br +++ b/lib/search/indexes/github-docs-3.3-en-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:2f815863337e086c1892e04754ff018348ef627f474e9a18ac57e29cea173091 -size 971021 +oid sha256:83e5720f75f56f113c67a23e23d286e9e3d59999e3239b93139a2f96f1d855db +size 972908 diff --git a/lib/search/indexes/github-docs-3.3-en.json.br b/lib/search/indexes/github-docs-3.3-en.json.br index 7754a53c2e..1473509ce1 100644 --- a/lib/search/indexes/github-docs-3.3-en.json.br +++ b/lib/search/indexes/github-docs-3.3-en.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:63c3c28824d31adc5805286b585725baa068cf70dd9aa33ca35fedf0917a6980 -size 3726133 +oid sha256:0df6cf51846d279fe7a6bc3e2c80c532b79b591fe183671d7daa3cbefed67a94 +size 3729509 diff --git a/lib/search/indexes/github-docs-3.3-es-records.json.br b/lib/search/indexes/github-docs-3.3-es-records.json.br index 8380121016..8dacb6865e 100644 --- a/lib/search/indexes/github-docs-3.3-es-records.json.br +++ b/lib/search/indexes/github-docs-3.3-es-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:3a397944601385fa635df85a124baa1847a0f6584624075b46098796ebec573c -size 659403 +oid sha256:d9ffa919d29272047e30cf2ac791b206178828714d0f157be07930f1bd6e37a7 +size 660443 diff --git a/lib/search/indexes/github-docs-3.3-es.json.br b/lib/search/indexes/github-docs-3.3-es.json.br index 65dc3cada2..be5c2d72cc 100644 --- a/lib/search/indexes/github-docs-3.3-es.json.br +++ b/lib/search/indexes/github-docs-3.3-es.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:8382551aea9b965e716de829efaa312d8569c09404c6001d777eb740b657d0f1 -size 2786696 +oid sha256:bafd586134ce0ad6313b57aee3f465b8bb3baa44fd384e24e0a90c4a68c4e308 +size 2787943 diff --git a/lib/search/indexes/github-docs-3.3-ja-records.json.br b/lib/search/indexes/github-docs-3.3-ja-records.json.br index 1c38ad3696..cff2fbb9ff 100644 --- a/lib/search/indexes/github-docs-3.3-ja-records.json.br +++ b/lib/search/indexes/github-docs-3.3-ja-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:337432605ed6bbe3d90f9178a3666b1fce3ff359553c46633f9626dc74c5c6c2 -size 727032 +oid sha256:f07953c6b918479bc793c74ce17d86bc70f331b0466e02b82dfe74cc6c2cd69e +size 726317 diff --git a/lib/search/indexes/github-docs-3.3-ja.json.br b/lib/search/indexes/github-docs-3.3-ja.json.br index dfd59b3a47..cba4dd6f7c 100644 --- a/lib/search/indexes/github-docs-3.3-ja.json.br +++ b/lib/search/indexes/github-docs-3.3-ja.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:6901933de4ebd0db0a2604d85374d890927be9c0d2ccffe23c8c583d9b68e223 -size 3884906 +oid sha256:64d86e600359bfbd6426a62d9da1fa3fe7cafa15df0fdb68745875fe52982378 +size 3884340 diff --git a/lib/search/indexes/github-docs-3.3-pt-records.json.br b/lib/search/indexes/github-docs-3.3-pt-records.json.br index 7195de1ef2..917eed3efd 100644 --- a/lib/search/indexes/github-docs-3.3-pt-records.json.br +++ b/lib/search/indexes/github-docs-3.3-pt-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:5e43516e63e81a5c0128361bf57229677d2abbbce2cef69b6f1a0bc72645fcb6 -size 650629 +oid sha256:de0c5255441f779d18b052f39bf693843bc84a2f3f9c4aebc17ca198d129b73e +size 651040 diff --git a/lib/search/indexes/github-docs-3.3-pt.json.br b/lib/search/indexes/github-docs-3.3-pt.json.br index c7af0ac943..0eb4fa65b4 100644 --- a/lib/search/indexes/github-docs-3.3-pt.json.br +++ b/lib/search/indexes/github-docs-3.3-pt.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:f7415ffe07b461d799a263a6565a7477b7cb7058ccbac02043d4e00112802aba -size 2671648 +oid sha256:a4e492708a6dc845808da524252ad3ca9087e142496bcb62b1adc62151b35824 +size 2671387 diff --git a/lib/search/indexes/github-docs-3.4-cn-records.json.br b/lib/search/indexes/github-docs-3.4-cn-records.json.br index c671b61b7f..f88c956da4 100644 --- a/lib/search/indexes/github-docs-3.4-cn-records.json.br +++ b/lib/search/indexes/github-docs-3.4-cn-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:0a96c81085da8c32d730993f0122f7f416dba92e8bd1aad1093df46c03f1a1cd -size 715010 +oid sha256:842905398b5a1391443a80bbec72506d16e3717e42f1c545a5f57d2b91b6ef20 +size 715635 diff --git a/lib/search/indexes/github-docs-3.4-cn.json.br b/lib/search/indexes/github-docs-3.4-cn.json.br index 4a214735b9..a7ac66e406 100644 --- a/lib/search/indexes/github-docs-3.4-cn.json.br +++ b/lib/search/indexes/github-docs-3.4-cn.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:557b4bf69bae51e1b125a8fe630e56c8038fbaf3e280aafda27aa4b232ae4c06 -size 1439404 +oid sha256:b2d60b155c63d124b91ca198c3382ca7219774f80de6c16e942437abc6302160 +size 1439042 diff --git a/lib/search/indexes/github-docs-3.4-en-records.json.br b/lib/search/indexes/github-docs-3.4-en-records.json.br index f45daba298..ee362b06a7 100644 --- a/lib/search/indexes/github-docs-3.4-en-records.json.br +++ b/lib/search/indexes/github-docs-3.4-en-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:4a41a95e7051ef32e820fcf00be8dd21b826376c7f8d7d36becfe0c4c940aefd -size 978140 +oid sha256:0b35be98e55a668a3c234c323cf02ece353896a16f463ec58005b57484530020 +size 978570 diff --git a/lib/search/indexes/github-docs-3.4-en.json.br b/lib/search/indexes/github-docs-3.4-en.json.br index 455d9c56c6..fb82a1bfc5 100644 --- a/lib/search/indexes/github-docs-3.4-en.json.br +++ b/lib/search/indexes/github-docs-3.4-en.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:86490b480d78d4018e5f06243c080436e0726a797a31827560cf0165f654af9c -size 3746147 +oid sha256:abf1ac88c750cc9d67b365acddf7f0149e917e30d2b3c19fc4e92c350c42ecc2 +size 3748885 diff --git a/lib/search/indexes/github-docs-3.4-es-records.json.br b/lib/search/indexes/github-docs-3.4-es-records.json.br index 238c223b46..59b604dfbe 100644 --- a/lib/search/indexes/github-docs-3.4-es-records.json.br +++ b/lib/search/indexes/github-docs-3.4-es-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:306b1c0bb6736def853dccd8b59e549e0def2961f7531139822d95b6b831dbf3 -size 661436 +oid sha256:9231dd97959076e67d197b0fe3e644749b26d6ff14f416f1b6345f084b3aca15 +size 661787 diff --git a/lib/search/indexes/github-docs-3.4-es.json.br b/lib/search/indexes/github-docs-3.4-es.json.br index 774c135b34..bd8fbf963c 100644 --- a/lib/search/indexes/github-docs-3.4-es.json.br +++ b/lib/search/indexes/github-docs-3.4-es.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:d3188da93de67cb364873938ca05f37d757da987b6f51de0bee761b85c4165f3 -size 2791677 +oid sha256:8d8b68acfba00e6072412a6efa90955fc7561723eea193b159b303c15ec26275 +size 2791634 diff --git a/lib/search/indexes/github-docs-3.4-ja-records.json.br b/lib/search/indexes/github-docs-3.4-ja-records.json.br index ef4c70dde4..4a14b9b557 100644 --- a/lib/search/indexes/github-docs-3.4-ja-records.json.br +++ b/lib/search/indexes/github-docs-3.4-ja-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:5cc282cc0cc8ac919c0c303c1312886d5ccfa2a6749c9eadf0a7eccb0547b7af -size 728194 +oid sha256:a578e25c39bb6a1b39292f75d62e813adb4f5a2993a6f5452d51dc978e959392 +size 728579 diff --git a/lib/search/indexes/github-docs-3.4-ja.json.br b/lib/search/indexes/github-docs-3.4-ja.json.br index 32e21c8dda..c9e7788f13 100644 --- a/lib/search/indexes/github-docs-3.4-ja.json.br +++ b/lib/search/indexes/github-docs-3.4-ja.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:25f9feaaa8ec9560f9514c0c5466fdd9631bf22ee63aa0ba9f9ec8d36431d047 -size 3891769 +oid sha256:e5a73397fc411d1760f3040a958746a64d6083be128347afa10d3337d17e478c +size 3891762 diff --git a/lib/search/indexes/github-docs-3.4-pt-records.json.br b/lib/search/indexes/github-docs-3.4-pt-records.json.br index 635a1b6f23..b1825a63c2 100644 --- a/lib/search/indexes/github-docs-3.4-pt-records.json.br +++ b/lib/search/indexes/github-docs-3.4-pt-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:41f664c30b2d7567093fb9433854fe41e9fd07e5983579ef7dbfd78fd75b4625 -size 652772 +oid sha256:32aec296f2703d158874fb2594efb619ebdf5ab8c477e74092ffb0ffb637da58 +size 652030 diff --git a/lib/search/indexes/github-docs-3.4-pt.json.br b/lib/search/indexes/github-docs-3.4-pt.json.br index 39e17665f6..8a39274e79 100644 --- a/lib/search/indexes/github-docs-3.4-pt.json.br +++ b/lib/search/indexes/github-docs-3.4-pt.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:c44f435e039a550dc60daeb6d23ae5b74bf420318e25bc5e5e8576893bfbf205 -size 2678090 +oid sha256:d0fd78cdfa68eef49ab0680882140e59fce7bfd3bafcc284dd164cc4effdd036 +size 2675110 diff --git a/lib/search/indexes/github-docs-dotcom-cn-records.json.br b/lib/search/indexes/github-docs-dotcom-cn-records.json.br index 2575ed527f..bab12fdfc7 100644 --- a/lib/search/indexes/github-docs-dotcom-cn-records.json.br +++ b/lib/search/indexes/github-docs-dotcom-cn-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:6e7af6acd7531b9ed1a0174141a405027c89a9a019516f85b1300640e8db87ff -size 910938 +oid sha256:59368887e71b51d528194031856006dcac6555fe6cc89fa7d5f92e99af8b2d50 +size 913282 diff --git a/lib/search/indexes/github-docs-dotcom-cn.json.br b/lib/search/indexes/github-docs-dotcom-cn.json.br index 0d01723973..2bfbf015ab 100644 --- a/lib/search/indexes/github-docs-dotcom-cn.json.br +++ b/lib/search/indexes/github-docs-dotcom-cn.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:eae8ba43589036938ef7ac5fc30addbd3d558ab3a3d889692c701b1a90a3e631 -size 1485198 +oid sha256:6ebd1db70157d67b58d038228017723d231124507a0edefba7281dbf69e9d4a5 +size 1492476 diff --git a/lib/search/indexes/github-docs-dotcom-en-records.json.br b/lib/search/indexes/github-docs-dotcom-en-records.json.br index 1545185172..778d13f9a2 100644 --- a/lib/search/indexes/github-docs-dotcom-en-records.json.br +++ b/lib/search/indexes/github-docs-dotcom-en-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:dcb643181bcfb30815ec82d5041ddaecce13fe676a19d31c158ed94ae3115c3e -size 1233215 +oid sha256:d35233a4dcc1dbaf2acdffbca2fac27839e4a1e13ad096a76647305169613ed9 +size 1234871 diff --git a/lib/search/indexes/github-docs-dotcom-en.json.br b/lib/search/indexes/github-docs-dotcom-en.json.br index 5774d2a46c..504bcf5b69 100644 --- a/lib/search/indexes/github-docs-dotcom-en.json.br +++ b/lib/search/indexes/github-docs-dotcom-en.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:56418e6afd0023baa4ded0c5e99a8575d5b2b78ccc4af54220cc112ec460a72d -size 4450675 +oid sha256:65cb7f373042424b3b2db81b6b1fde56d20933b0d3e4017e6fe40e993e2190e6 +size 4459494 diff --git a/lib/search/indexes/github-docs-dotcom-es-records.json.br b/lib/search/indexes/github-docs-dotcom-es-records.json.br index eebb8411be..b3a846cb7c 100644 --- a/lib/search/indexes/github-docs-dotcom-es-records.json.br +++ b/lib/search/indexes/github-docs-dotcom-es-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:dcc58f9e7dce521a3ccf0365f01d434e0fc5cb52101da40bc2c551ae2b324799 -size 820991 +oid sha256:ddede278a48e883aee4aa980b187c1973d34ace6f898062e5d84c787ee199060 +size 823739 diff --git a/lib/search/indexes/github-docs-dotcom-es.json.br b/lib/search/indexes/github-docs-dotcom-es.json.br index 484c54b376..45e568d87f 100644 --- a/lib/search/indexes/github-docs-dotcom-es.json.br +++ b/lib/search/indexes/github-docs-dotcom-es.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:bf49fd0575ce34af363a954cd1c24fc71a3659c64728bfcaec799d5e95b60adc -size 3282584 +oid sha256:92aaeafd731b7b355b0f4a758e13ee433c7b25fa7bb7629ed54dd2d71c68c80b +size 3296697 diff --git a/lib/search/indexes/github-docs-dotcom-ja-records.json.br b/lib/search/indexes/github-docs-dotcom-ja-records.json.br index 478461230c..607dfcc74e 100644 --- a/lib/search/indexes/github-docs-dotcom-ja-records.json.br +++ b/lib/search/indexes/github-docs-dotcom-ja-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:97628d13d596dc6cf0b36900857be592022d31e1823ceb14cbeed857ab34c999 -size 921467 +oid sha256:f9dd91d96c0a560e5411bf6c861a828d6edf7e7f27db207a8cd3eea1529b4377 +size 922869 diff --git a/lib/search/indexes/github-docs-dotcom-ja.json.br b/lib/search/indexes/github-docs-dotcom-ja.json.br index 4a3b0de6c7..31cd445de4 100644 --- a/lib/search/indexes/github-docs-dotcom-ja.json.br +++ b/lib/search/indexes/github-docs-dotcom-ja.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:cd83964a9335e85356e502b5ac5c844ef6f139a985b59e56eff62d96b44f409f -size 4690635 +oid sha256:8f11c5dbf6eed9a84e4c54674ef55ba2d5495ee94271e22a10e3a6b2b0dc15f2 +size 4704369 diff --git a/lib/search/indexes/github-docs-dotcom-pt-records.json.br b/lib/search/indexes/github-docs-dotcom-pt-records.json.br index 4a60f65d91..4479048ba1 100644 --- a/lib/search/indexes/github-docs-dotcom-pt-records.json.br +++ b/lib/search/indexes/github-docs-dotcom-pt-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:41c47f9d68e79927e5d3cdeae121c616c367d0f923fa682d7b15c426777b2bc8 -size 811881 +oid sha256:c47dc47a2ef21e31d0972b0b7f437b1dd84a2215a7fcfecbec771e7fddb99c99 +size 811703 diff --git a/lib/search/indexes/github-docs-dotcom-pt.json.br b/lib/search/indexes/github-docs-dotcom-pt.json.br index 3640c47dde..fced41f5fb 100644 --- a/lib/search/indexes/github-docs-dotcom-pt.json.br +++ b/lib/search/indexes/github-docs-dotcom-pt.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:2d59b52540bf87b496f4f64558a7991622b74dc70dda216a5398c909c211b57c -size 3163273 +oid sha256:21783cabb25ab90d9de6147a3dd348c9524ac82fbf72a97177fa8ef33a41b56e +size 3166648 diff --git a/lib/search/indexes/github-docs-ghae-cn-records.json.br b/lib/search/indexes/github-docs-ghae-cn-records.json.br index 81ccb53045..268e587f56 100644 --- a/lib/search/indexes/github-docs-ghae-cn-records.json.br +++ b/lib/search/indexes/github-docs-ghae-cn-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:9d7a6f6a46a76c4808ef805b0e8701ca7bef88376d18be0888fb9aa734d9cb76 -size 541782 +oid sha256:d371c967e3f4369475ec51c2cf48a3a0c34513995edf6de59a0ab65de0ab0375 +size 542277 diff --git a/lib/search/indexes/github-docs-ghae-cn.json.br b/lib/search/indexes/github-docs-ghae-cn.json.br index e22e3eb4c4..a9453d10b8 100644 --- a/lib/search/indexes/github-docs-ghae-cn.json.br +++ b/lib/search/indexes/github-docs-ghae-cn.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:525386e2c9c3774fb62ae675cf7c241339bbe17f96504f14bf03280dd82921fc -size 1018034 +oid sha256:3647ca51409448fee85c60c1919e7edfd55bdf26528bc7f6a0ea44ec57ccac55 +size 1016813 diff --git a/lib/search/indexes/github-docs-ghae-en-records.json.br b/lib/search/indexes/github-docs-ghae-en-records.json.br index 56acf56c22..d1acb52ae5 100644 --- a/lib/search/indexes/github-docs-ghae-en-records.json.br +++ b/lib/search/indexes/github-docs-ghae-en-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:8298b2645468e27af09f250190c6666e9a41ed589de35dae32f304445c08e75c -size 750653 +oid sha256:a77f536b0fa3c758e711ba41ee0aacb111d6f1a0c9a477c853eabcf27fdb443c +size 753393 diff --git a/lib/search/indexes/github-docs-ghae-en.json.br b/lib/search/indexes/github-docs-ghae-en.json.br index 9492f9719e..bcd43a6763 100644 --- a/lib/search/indexes/github-docs-ghae-en.json.br +++ b/lib/search/indexes/github-docs-ghae-en.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:2759e2ea744c44aadc474569017dedfab174ec9e66148791adff302f43a90608 -size 2845921 +oid sha256:595484b9fd0445cd29865155e564c1ae2cfa3e2f7f412627432b5c587bfc5038 +size 2850884 diff --git a/lib/search/indexes/github-docs-ghae-es-records.json.br b/lib/search/indexes/github-docs-ghae-es-records.json.br index 746312e816..6312c88bac 100644 --- a/lib/search/indexes/github-docs-ghae-es-records.json.br +++ b/lib/search/indexes/github-docs-ghae-es-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:673b0acd57ecd884947ff85a2fda3b200288a1d2f4289414bb03d70eeb0cf262 -size 502783 +oid sha256:8a0c4f56e42ab35cdf425f324a141cc6663465072310481443f40fa4fcd71c7d +size 503093 diff --git a/lib/search/indexes/github-docs-ghae-es.json.br b/lib/search/indexes/github-docs-ghae-es.json.br index 970c022a38..3646522f44 100644 --- a/lib/search/indexes/github-docs-ghae-es.json.br +++ b/lib/search/indexes/github-docs-ghae-es.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:425d8bcf91266f62538fac55736e08383085e99059fb08b3e32d0761ecd99b3c -size 2029020 +oid sha256:0be8f4debe94e3eed956f323515423cb51928ab270301078997b9bc27f3dc47d +size 2032661 diff --git a/lib/search/indexes/github-docs-ghae-ja-records.json.br b/lib/search/indexes/github-docs-ghae-ja-records.json.br index c18bf39453..4033e0ab1e 100644 --- a/lib/search/indexes/github-docs-ghae-ja-records.json.br +++ b/lib/search/indexes/github-docs-ghae-ja-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:1946857efc244266c1c754a9dcfa950b5c83c1ffc26549bd62275d90f1672272 -size 553143 +oid sha256:d3beb6da620992334b7d84f81b8513f21741dc0ff5d65e021b1e1cee5b565bc0 +size 552991 diff --git a/lib/search/indexes/github-docs-ghae-ja.json.br b/lib/search/indexes/github-docs-ghae-ja.json.br index eb9e90f73d..aeb2ccf364 100644 --- a/lib/search/indexes/github-docs-ghae-ja.json.br +++ b/lib/search/indexes/github-docs-ghae-ja.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:35b5d744d1b4cf441f2c8edc2c24a2b038a2f6e7c62a27a01036d15197258370 -size 2822947 +oid sha256:b5cf843a561d14d50bfa6c1c16941ee84f05cd846dfcd73ec076fa058718649e +size 2821108 diff --git a/lib/search/indexes/github-docs-ghae-pt-records.json.br b/lib/search/indexes/github-docs-ghae-pt-records.json.br index 42ee7d2d02..dde2b61384 100644 --- a/lib/search/indexes/github-docs-ghae-pt-records.json.br +++ b/lib/search/indexes/github-docs-ghae-pt-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:eb6d403628897d32ea0d93d3623471771cb9a5e0991170b15ca29e3140489d59 -size 495612 +oid sha256:e06914351c14926b921dd1034ddcc5fdf9a1ff5a26200bc5b2c2c1e938cd0705 +size 496017 diff --git a/lib/search/indexes/github-docs-ghae-pt.json.br b/lib/search/indexes/github-docs-ghae-pt.json.br index 14b76837ec..e5571c810a 100644 --- a/lib/search/indexes/github-docs-ghae-pt.json.br +++ b/lib/search/indexes/github-docs-ghae-pt.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:b04d7966a9b1d8848e3ccb2586b05f2794a5c148319597013e1030c183b091e3 -size 1938418 +oid sha256:d352676d0cbbe7d6357f3e5d306fc713571beb8bdb62c0aaa84a570ec7b69aeb +size 1936232 diff --git a/lib/search/indexes/github-docs-ghec-cn-records.json.br b/lib/search/indexes/github-docs-ghec-cn-records.json.br index 5acddc71e9..367ba039b6 100644 --- a/lib/search/indexes/github-docs-ghec-cn-records.json.br +++ b/lib/search/indexes/github-docs-ghec-cn-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:eb85db683d3116fe91b4be26d3f5631d1e1ab5dbf8bbf14c5392b04ce83fe9f3 -size 859118 +oid sha256:6f891dc793e5801854f7c16fc796b9cc3952cb9c7796f41bfc0470788beccd8b +size 860000 diff --git a/lib/search/indexes/github-docs-ghec-cn.json.br b/lib/search/indexes/github-docs-ghec-cn.json.br index 480a9e66c2..d21cb00675 100644 --- a/lib/search/indexes/github-docs-ghec-cn.json.br +++ b/lib/search/indexes/github-docs-ghec-cn.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:9d35e73e52cf78097721c942f58a219648d69fb42114cf42cd535df0ad87dbc1 -size 1597251 +oid sha256:3464ad9733554dd81888708b1beb85e20f7c10109d7df0f7899bafef304330f8 +size 1598490 diff --git a/lib/search/indexes/github-docs-ghec-en-records.json.br b/lib/search/indexes/github-docs-ghec-en-records.json.br index aca90d0456..427ac0abf2 100644 --- a/lib/search/indexes/github-docs-ghec-en-records.json.br +++ b/lib/search/indexes/github-docs-ghec-en-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:51853ce6f7dbc6d6274492c8328c54cffffcab0c148b5f31606115e3024d6a07 -size 1144320 +oid sha256:4ffadaddbc3f80fc91f03324fee90676ee2fad13a46e746b0920e3dab69dbe8e +size 1144358 diff --git a/lib/search/indexes/github-docs-ghec-en.json.br b/lib/search/indexes/github-docs-ghec-en.json.br index 265346cdb4..ab90320c22 100644 --- a/lib/search/indexes/github-docs-ghec-en.json.br +++ b/lib/search/indexes/github-docs-ghec-en.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:f9eff94d1d4d58ba930ada3c15b88ceaa466663e7b450526a3434db2cb36e590 -size 4366678 +oid sha256:0732e8852f25e1c412e24871647ee3ae87fcc014ab475a88cb1a5e8812f706e5 +size 4372209 diff --git a/lib/search/indexes/github-docs-ghec-es-records.json.br b/lib/search/indexes/github-docs-ghec-es-records.json.br index a0b90c3ca0..2b44898944 100644 --- a/lib/search/indexes/github-docs-ghec-es-records.json.br +++ b/lib/search/indexes/github-docs-ghec-es-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:67c35e05d204f3947f4d7733cbaa0981cb7fe12446b67db511411275904b6d63 -size 796469 +oid sha256:62f234e1b3d528aa40d052b3850f41f42b710aae980bd665d591dad562f23bf9 +size 798241 diff --git a/lib/search/indexes/github-docs-ghec-es.json.br b/lib/search/indexes/github-docs-ghec-es.json.br index e2714cd56e..798e069ede 100644 --- a/lib/search/indexes/github-docs-ghec-es.json.br +++ b/lib/search/indexes/github-docs-ghec-es.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:7acfe209ef929fa154a161ff4834ca07e2a6eba76b935a7b85cc12a73419375a -size 3347786 +oid sha256:010c709b2b0698e197b72b72c7a7a4722884417004125361666dd3a64e0db83a +size 3353379 diff --git a/lib/search/indexes/github-docs-ghec-ja-records.json.br b/lib/search/indexes/github-docs-ghec-ja-records.json.br index d975ae41ac..c06a9c823e 100644 --- a/lib/search/indexes/github-docs-ghec-ja-records.json.br +++ b/lib/search/indexes/github-docs-ghec-ja-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:cc40587a66f12467b37501ef4276fb2fc11224c2bd672568293aa34218dd44bf -size 872849 +oid sha256:04e6f6050552310a6b8374d3c671a28db2ba59de7405500147e3ba86b610b610 +size 872679 diff --git a/lib/search/indexes/github-docs-ghec-ja.json.br b/lib/search/indexes/github-docs-ghec-ja.json.br index c49d3c63ae..2fe3c052c0 100644 --- a/lib/search/indexes/github-docs-ghec-ja.json.br +++ b/lib/search/indexes/github-docs-ghec-ja.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:3eeb12afca0c42cef93fbaf1bf43f739a11a14ec21b63304de721afd62a4fb88 -size 4682617 +oid sha256:aa9432f35e7734940b62a412a637f0242d9cd51dc6fa025e330dd1b1a921f57e +size 4684753 diff --git a/lib/search/indexes/github-docs-ghec-pt-records.json.br b/lib/search/indexes/github-docs-ghec-pt-records.json.br index c2b5264105..9154c87436 100644 --- a/lib/search/indexes/github-docs-ghec-pt-records.json.br +++ b/lib/search/indexes/github-docs-ghec-pt-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:dd91c1867716c53d161c69193ea0f3589548a4a6b40dfceb5f89b4b07182ab59 -size 786196 +oid sha256:12eb0a2f6bbc8dbeb66729ebda093d93e0eaaaa340b1bf6279e2dd617d48857a +size 787519 diff --git a/lib/search/indexes/github-docs-ghec-pt.json.br b/lib/search/indexes/github-docs-ghec-pt.json.br index 274bf50c56..90aa109fe1 100644 --- a/lib/search/indexes/github-docs-ghec-pt.json.br +++ b/lib/search/indexes/github-docs-ghec-pt.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:88ff6e48211c781f7c60ae7b619e53a3e77c7acff04f54fc3d6b95ee738d5e6c -size 3219452 +oid sha256:7ccafaded3b3f39df1eb268e74fb8d353cfc81fc288c3c7e8caba4f0872754f5 +size 3221408 diff --git a/translations/es-ES/content/actions/hosting-your-own-runners/running-scripts-before-or-after-a-job.md b/translations/es-ES/content/actions/hosting-your-own-runners/running-scripts-before-or-after-a-job.md index b343e05f7a..7750faad82 100644 --- a/translations/es-ES/content/actions/hosting-your-own-runners/running-scripts-before-or-after-a-job.md +++ b/translations/es-ES/content/actions/hosting-your-own-runners/running-scripts-before-or-after-a-job.md @@ -73,4 +73,4 @@ There is currently no timeout setting available for scripts executed by `ACTIONS ### Reviewing the workflow run log -To confirm whether your scripts are executing, you can review the logs for that job. The scripts will be listed within separate steps for either `Set up runner` or `Complete runner`, depending on which environment variable is triggering the script. For more information on checking the logs, see "[Viewing logs to diagnose failures](/actions/monitoring-and-troubleshooting-workflows/using-workflow-run-logs#viewing-logs-to-diagnose-failures)." +To confirm whether your scripts are executing, you can review the logs for that job. The scripts will be listed within separate steps for either `Set up runner` or `Complete runner`, depending on which environment variable is triggering the script. Para obtener más información sobre cómo verificar las bitácoras, consulta la sección "[Visualizar las bitácoras para diagnosticar las fallas](/actions/monitoring-and-troubleshooting-workflows/using-workflow-run-logs#viewing-logs-to-diagnose-failures)". diff --git a/translations/es-ES/content/actions/using-workflows/about-workflows.md b/translations/es-ES/content/actions/using-workflows/about-workflows.md index 9ae0106c5c..877efb4754 100644 --- a/translations/es-ES/content/actions/using-workflows/about-workflows.md +++ b/translations/es-ES/content/actions/using-workflows/about-workflows.md @@ -28,7 +28,7 @@ A workflow must contain the following basic components: 1. One or more _jobs_, each of which will execute on a _runner_ machine and run a series of one or more _steps_. 1. Each step can either run a script that you define or run an action, which is a reusable extension that can simplify your workflow. -For more information these basic components, see "[Understanding GitHub Actions](/actions/learn-github-actions/understanding-github-actions#the-components-of-github-actions)." +For more information on these basic components, see "[Understanding GitHub Actions](/actions/learn-github-actions/understanding-github-actions#the-components-of-github-actions)." ![Resumen del flujo de trabajo](/assets/images/help/images/overview-actions-simple.png) diff --git a/translations/es-ES/content/actions/using-workflows/using-starter-workflows.md b/translations/es-ES/content/actions/using-workflows/using-starter-workflows.md index 5e9a212d4d..e4b8a7473e 100644 --- a/translations/es-ES/content/actions/using-workflows/using-starter-workflows.md +++ b/translations/es-ES/content/actions/using-workflows/using-starter-workflows.md @@ -39,7 +39,7 @@ Cualquiera con permiso de escritura en un repositorio puede configurar flujos de {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.actions-tab %} 1. Si ya tienes un flujo de trabajo en tu repositorio, haz clic en **Flujo de trabajo nuevo**. -1. The "{% if actions-starter-template-ui %}Choose a workflow{% else %}Choose a workflow template{% endif %}" page shows a selection of recommended starter workflows. Find the starter workflow that you want to use, then click {% if actions-starter-template-ui %}**Configure**{% else %}**Set up this workflow**{% endif %}.{% if actions-starter-template-ui %} To help you find the starter workflow that you want, you can search for keywords or filter by category.{% endif %} +1. The "{% if actions-starter-template-ui %}Choose a workflow{% else %}Choose a workflow template{% endif %}" page shows a selection of recommended starter workflows. Encuentra el flujo de trabajo inicial que quieras utilizar, luego haz clic en {% if actions-starter-template-ui %}**Configurar**{% else %}**Configurar este flujo de trabajo**{% endif %}.{% if actions-starter-template-ui %} Para ayudarte a encontrar el flujo de trabajo inicial que quieres, puedes buscar las palabras clave o filtrar por categoría.{% endif %} {% if actions-starter-template-ui %}![Configure this workflow](/assets/images/help/settings/actions-create-starter-workflow-updated-ui.png){% else %}![Set up this workflow](/assets/images/help/settings/actions-create-starter-workflow.png){% endif %} 1. Si el flujo de trabajo inicial contiene comentarios que detallen pasos de configuración adicional, sigue estos pasos. Muchos de los flujos de trabajo iniciales tienen guías correspondientes. For more information, see the [{% data variables.product.prodname_actions %} guides](/actions/guides). diff --git a/translations/es-ES/content/admin/all-releases.md b/translations/es-ES/content/admin/all-releases.md index c412a60061..ea1a5719d9 100644 --- a/translations/es-ES/content/admin/all-releases.md +++ b/translations/es-ES/content/admin/all-releases.md @@ -12,7 +12,7 @@ shortTitle: Lanzamientos ## Acerca de los lanzamientos de {% data variables.product.product_name %} -{% data reusables.enterprise.constantly-improving %} {% data variables.product.company_short %} es compatible con los cuatro lanzamientos de características más recientes. For more information, see "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)." +{% data reusables.enterprise.constantly-improving %} {% data variables.product.company_short %} es compatible con los cuatro lanzamientos de características más recientes. Para obtener más información, consulta la sección "[Acerca de las mejoras a los lanzamientos nuevos](/admin/overview/about-upgrades-to-new-releases)". Puedes ver lo nuevo de cada lanzamiento en las [notas de lanzamiento](/admin/release-notes) y puedes ver la documentación de usuario y de administrador de todos los lanzamientos aquí en {% data variables.product.prodname_docs %}. Cuando leas la documentación, asegúrate de seleccionar la versión que refleje tu producto. Para obtener más información, consulta la sección "[Acerca de las versiones de {% data variables.product.prodname_docs %}](/get-started/learning-about-github/about-versions-of-github-docs)". diff --git a/translations/es-ES/content/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise.md b/translations/es-ES/content/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise.md index efd50c0489..ea8ce992bc 100644 --- a/translations/es-ES/content/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise.md +++ b/translations/es-ES/content/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise.md @@ -33,7 +33,7 @@ El {% data variables.product.prodname_dependabot %} ayuda a que los usuarios de {% data reusables.dependabot.dependabot-alerts-beta %} -With {% data variables.product.prodname_dependabot_alerts %}, {% data variables.product.prodname_dotcom %} identifies vulnerable dependencies in repositories and creates alerts on {% data variables.product.product_location %}, using data from the {% data variables.product.prodname_advisory_database %} and the dependency graph service. +Con las {% data variables.product.prodname_dependabot_alerts %}, {% data variables.product.prodname_dotcom %} identifica las dependencias vulnerables en los repositorios y crea alertas en {% data variables.product.product_location %} utilizando datos de la {% data variables.product.prodname_advisory_database %} y del servicio de la gráfica de dependencias. {% data reusables.repositories.tracks-vulnerabilities %} diff --git a/translations/es-ES/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-minio-gateway-for-nas-storage.md b/translations/es-ES/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-minio-gateway-for-nas-storage.md index 0631469119..ec1bdc76bd 100644 --- a/translations/es-ES/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-minio-gateway-for-nas-storage.md +++ b/translations/es-ES/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-minio-gateway-for-nas-storage.md @@ -15,9 +15,13 @@ redirect_from: shortTitle: Puerta de enlace de MinIO para el almacenamiento en NAS --- -## Prerrequisitos +{% warning %} -{% data reusables.actions.enterprise-s3-support-warning %} +**Warning**: MinIO has announced removal of MinIO Gateways. Starting June 1st, 2022, support and bug fixes for the current MinIO NAS Gateway implementation will only be available for paid customers via their LTS support contract. If you want to continue using MinIO Gateways with {% data variables.product.prodname_actions %}, we recommend moving to MinIO LTS support. For more information, see [Scheduled removal of MinIO Gateway for GCS, Azure, HDFS](https://github.com/minio/minio/issues/14331) in the minio/minio repository. + +{% endwarning %} + +## Prerrequisitos Antes de que habilites las {% data variables.product.prodname_actions %}, asegúrate de que has completado los siguientes pasos: diff --git a/translations/es-ES/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-self-hosted-runners-for-your-enterprise.md b/translations/es-ES/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-self-hosted-runners-for-your-enterprise.md index aaa1929bf2..ed31203bba 100644 --- a/translations/es-ES/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-self-hosted-runners-for-your-enterprise.md +++ b/translations/es-ES/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-self-hosted-runners-for-your-enterprise.md @@ -61,7 +61,7 @@ Primero, habilita las {% data variables.product.prodname_actions %} para todas l {% if actions-workflow-policy %} ![Screenshot of "Allow select actions" and "Allow actions created by {% data variables.product.company_short %}" for {% data variables.product.prodname_actions %}](/assets/images/help/settings/actions-policy-allow-select-actions-and-actions-from-github-with-workflows.png) {%- else %} - ![Screenshot of "Allow select actions" and "Allow actions created by {% data variables.product.company_short %}" for {% data variables.product.prodname_actions %}](/assets/images/help/settings/actions-policy-allow-select-actions-and-actions-from-github.png) + ![Captura de pantalla de "Permitir acciones seleccionadas" y "Permitir acciones creadas por {% data variables.product.company_short %}" para las {% data variables.product.prodname_actions %}](/assets/images/help/settings/actions-policy-allow-select-actions-and-actions-from-github.png) {%- endif %} 1. Haz clic en **Save ** (guardar). diff --git a/translations/es-ES/content/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise.md b/translations/es-ES/content/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise.md index a379b1b79a..a879ca25ee 100644 --- a/translations/es-ES/content/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise.md +++ b/translations/es-ES/content/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise.md @@ -48,7 +48,7 @@ Cada acción es un repositorio en la organización `actions` y cada repositorio **Notas:** - Cuando utilices acciones de configuración, (tales como `actions/setup-LANGUAGE`) en {% data variables.product.product_name %} con ejecutores auto-hospedados, tal vez necesites configurar el caché de las herramientas en los ejecutores que no tienen acceso a internet. Para obtener más información, consulta la sección "[ Configurar el caché de herramientas en ejecutores auto-hospedados sin acceso a internet](/enterprise/admin/github-actions/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access)". -- Las mejoras a {% data variables.product.product_name %} no darán como resultado una actualización de las acciones en paquete. +- Bundled actions are automatically updated when {% data variables.product.product_name %} is updated. {% endnote %} diff --git a/translations/es-ES/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise.md b/translations/es-ES/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise.md index 913ddf962e..2ab41a06c4 100644 --- a/translations/es-ES/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise.md +++ b/translations/es-ES/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise.md @@ -15,7 +15,7 @@ topics: - SSO --- -## About authentication for your enterprise +## Acerca de la autenticación para tu empresa {% ifversion ghec %} @@ -29,17 +29,17 @@ The following options are available for account management and authentication on - [Authentication through {% data variables.product.product_location %} with additional SAML access restriction](#authentication-through-githubcom-with-additional-saml-access-restriction) - [Authentication with {% data variables.product.prodname_emus %} and SAML SSO](#authentication-with-enterprise-managed-users-and-saml-sso) -### Authentication through {% data variables.product.product_location %} +### Autenticación mediante {% data variables.product.product_location %} By default, each member must create a personal account on {% data variables.product.product_location %}. You grant access to your enterprise, and the member can access your enterprise's resources after signing into the account on {% data variables.product.product_location %}. The member manages the account, and can contribute to other enterprises, organizations, and repositories on {% data variables.product.product_location %}. -### Authentication through {% data variables.product.product_location %} with additional SAML access restriction +### Autenticación mediante {% data variables.product.product_location %} con restricción de acceso adicional de SAML If you configure additional SAML access restriction, each member must create and manage a personal account on {% data variables.product.product_location %}. You grant access to your enterprise, and the member can access your enterprise's resources after both signing into the account on {% data variables.product.product_location %} and successfully authenticating with your SAML identity provider (IdP). The member can contribute to other enterprises, organizations, and repositories on {% data variables.product.product_location %} using their personal account. For more information about requiring SAML authentication for all access your enterprise's resources, see "[About SAML for enterprise IAM](/admin/identity-and-access-management/using-saml-for-enterprise-iam/about-saml-for-enterprise-iam)." If you use a standalone organization with {% data variables.product.product_name %}, or if you don't want to use SAML authentication for every organization in your enterprise, you can configure SAML for an individual organization. Para obtener más información, consulta la sección "[Acerca de la administración de identidad y accesos con el inicio de sesión único de SAML](/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on)". -### Authentication with {% data variables.product.prodname_emus %} and SAML SSO +### Autenticación con las {% data variables.product.prodname_emus %} y el SSO de SAML If you need more control of the accounts for your enterprise members on {% data variables.product.product_location %}, you can use {% data variables.product.prodname_emus %}. With {% data variables.product.prodname_emus %}, you provision and manage accounts for your enterprise members on {% data variables.product.product_location %} using your IdP. Each member signs into an account that you create, and your enterprise manages the account. Contributions to the rest of {% data variables.product.prodname_dotcom_the_website %} are restricted. Para obtener más información, consulta la sección "[Acerca de {% data variables.product.prodname_emus %}](/admin/identity-and-access-management/using-enterprise-managed-users-and-saml-for-iam/about-enterprise-managed-users)". @@ -47,18 +47,18 @@ If you need more control of the accounts for your enterprise members on {% data Site administrators can decide how people authenticate to access a {% data variables.product.product_name %} instance. You can use {% data variables.product.product_name %}'s built-in authentication, or, if you want to centralize identity and access management for the web applications that your team uses, you can configure an external authentication method. -## Authentication methods for {% data variables.product.product_name %} +## Métodos de autenticación para {% data variables.product.product_name %} The following authentication methods are available for {% data variables.product.product_name %}. - [Built-in authentication](#built-in-authentication) - [External authentication](#external-authentication) -### Built-in authentication +### Autenticación incorporada {% data reusables.enterprise_user_management.built-in-authentication-new-accounts %} To access your instance, people authenticate with the credentials for the account. Para obtener más información, consulta la sección "[Configurar la autenticación incorporada](/admin/identity-and-access-management/using-built-in-authentication/configuring-built-in-authentication)". -### External authentication +### Autenticación externa If you use an external directory or identity provider (IdP) to centralize access to multiple web applications, you may be able to configure external authentication for {% data variables.product.product_location %}. Para obtener más información, consulta lo siguiente. @@ -66,7 +66,7 @@ If you use an external directory or identity provider (IdP) to centralize access - "[Using LDAP for enterprise IAM](/admin/identity-and-access-management/using-ldap-for-enterprise-iam)" - "[Using SAML for enterprise IAM](/admin/identity-and-access-management/using-saml-for-enterprise-iam)" -If you choose to use external authentication, you can also configure fallback authentication for people who don't have an account on your external authentication provider. For example, you may want to grant access to a contractor or machine user. For more information, see "[Allowing built-in authentication for users outside your provider](/admin/identity-and-access-management/managing-iam-for-your-enterprise/allowing-built-in-authentication-for-users-outside-your-provider)." +If you choose to use external authentication, you can also configure fallback authentication for people who don't have an account on your external authentication provider. For example, you may want to grant access to a contractor or machine user. Para obtener más información, consulta la sección "[Permitir la autenticación integrada para los usuarios fuera de tu proveedor](/admin/identity-and-access-management/managing-iam-for-your-enterprise/allowing-built-in-authentication-for-users-outside-your-provider)". {% elsif ghae %} @@ -76,7 +76,7 @@ If you choose to use external authentication, you can also configure fallback au ## About access control -{% ifversion ghec or ghae %}Members of your enterprise{% elsif ghes %}People with access to {% data variables.product.product_location %}{% endif %} can manage access to {% ifversion ghec %}your enterprise's resources{% elsif ghae %}your enterprise{% elsif ghes %}resources on your instance{% endif %} by using organization membership, teams, and roles. Para obtener más información, consulta lo siguiente. +{% ifversion ghec or ghae %}Los moembros de tu empresa{% elsif ghes %}Las personas con acceso a {% data variables.product.product_location %}{% endif %} pueden adminsitrar el acceso a {% ifversion ghec %}los recursos de tu empresa{% elsif ghae %}tu empresa{% elsif ghes %} en tu instancia{% endif %} si utilizan la membrecía organizacional, los equipos y los roles. Para obtener más información, consulta lo siguiente. {%- ifversion ghec %} - "[Invitar a usuarios para que se unan a nuestra organización](/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization)" diff --git a/translations/es-ES/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/allowing-built-in-authentication-for-users-outside-your-provider.md b/translations/es-ES/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/allowing-built-in-authentication-for-users-outside-your-provider.md index 39617e7860..e73dfa38fc 100644 --- a/translations/es-ES/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/allowing-built-in-authentication-for-users-outside-your-provider.md +++ b/translations/es-ES/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/allowing-built-in-authentication-for-users-outside-your-provider.md @@ -55,6 +55,6 @@ Cuando un usuario acepta la invitación, puede utilizar su nombre de usuario y c ## Leer más -- "[Using CAS for enterprise IAM](/admin/identity-and-access-management/using-cas-for-enterprise-iam)" -- "[Using LDAP for enterprise IAM](/admin/identity-and-access-management/using-ldap-for-enterprise-iam)" -- "[Using SAML for enterprise IAM](/admin/identity-and-access-management/using-saml-for-enterprise-iam)" +- "[Utilizar CAS para el IAM empresarial](/admin/identity-and-access-management/using-cas-for-enterprise-iam)" +- "[Utilizar LDAP para el IAM empresarial](/admin/identity-and-access-management/using-ldap-for-enterprise-iam)" +- "[Utilizar SAML para el IAM empresarial](/admin/identity-and-access-management/using-saml-for-enterprise-iam)" diff --git a/translations/es-ES/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication.md b/translations/es-ES/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication.md index 6232e7936b..afd525b0b7 100644 --- a/translations/es-ES/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication.md +++ b/translations/es-ES/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication.md @@ -26,7 +26,7 @@ When you use external authentication, {% data variables.product.product_location {% elsif ghec %} -If you use an enterprise with {% data variables.product.prodname_emus %}, members of your enterprise authenticate to access {% data variables.product.prodname_dotcom %} through your SAML identity provider (IdP). For more information, see "[About authentication for your enterprise](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise#authentication-methods-for-github-enterprise-server)." +If you use an enterprise with {% data variables.product.prodname_emus %}, members of your enterprise authenticate to access {% data variables.product.prodname_dotcom %} through your SAML identity provider (IdP). Para obtener más información, consulta la sección "[Acerca de la autenticación para tu empresa](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise#authentication-methods-for-github-enterprise-server)". {% data variables.product.product_name %} automatically creates a username for each person when the person signs in through your IdP for the first time. @@ -70,7 +70,7 @@ Usernames for user accounts on {% ifversion ghes or ghae %}{% data variables.pro {% data variables.product.product_name %} requires the `NameID` element even if other attributes are present. For more information, see "[SAML configuration reference](/admin/identity-and-access-management/using-saml-for-enterprise-iam/saml-configuration-reference#saml-attributes)." -{% data variables.product.product_name %} creates a mapping between the `NameID` from the IdP and the username {% ifversion ghec or ghae %}in{% elsif ghes %}on{% endif %} {% data variables.product.product_location %}, so the `NameID` should be persistent, unique, and not subject to change for the lifecycle of the user. +{% data variables.product.product_name %} crea un mapeo entre la `NameID` del IdP y el nombre de usuario {% ifversion ghec or ghae %}en{% elsif ghes %}en{% endif %} {% data variables.product.product_location %}, así que la `NameID` debería ser persistente, única y no estar sujeta a los cambios durante el ciclo de vida del usuario. {% ifversion ghes %} {% note %} diff --git a/translations/es-ES/content/admin/identity-and-access-management/using-built-in-authentication/index.md b/translations/es-ES/content/admin/identity-and-access-management/using-built-in-authentication/index.md index 64dd498ccb..403abbd2b1 100644 --- a/translations/es-ES/content/admin/identity-and-access-management/using-built-in-authentication/index.md +++ b/translations/es-ES/content/admin/identity-and-access-management/using-built-in-authentication/index.md @@ -1,6 +1,6 @@ --- title: Usar la autenticación integrada -shortTitle: Built-in authentication +shortTitle: Autenticación incorporada intro: 'If you don''t use a centralized, external system for your users'' identity, you can use built-in authentication to allow {% data variables.product.prodname_ghe_server %} to manage accounts and perform local authentication.' versions: ghes: '*' diff --git a/translations/es-ES/content/admin/identity-and-access-management/using-built-in-authentication/inviting-people-to-use-your-instance.md b/translations/es-ES/content/admin/identity-and-access-management/using-built-in-authentication/inviting-people-to-use-your-instance.md index f2358edd5d..cb68feb6c8 100644 --- a/translations/es-ES/content/admin/identity-and-access-management/using-built-in-authentication/inviting-people-to-use-your-instance.md +++ b/translations/es-ES/content/admin/identity-and-access-management/using-built-in-authentication/inviting-people-to-use-your-instance.md @@ -17,7 +17,7 @@ shortTitle: Invite people {% data reusables.enterprise_user_management.built-in-authentication-new-accounts %} {% data reusables.enterprise_user_management.unauthenticated-sign-ups %} -You can disable unauthenticated sign-ups and require an invitation to create a new user account on your instance. For more information, see "[Disabling unauthenticated sign-ups](/admin/identity-and-access-management/using-built-in-authentication/disabling-unauthenticated-sign-ups)." +You can disable unauthenticated sign-ups and require an invitation to create a new user account on your instance. Para obtener más información, consulta la sección "[Inhabilitar los inicios de sesión no autenticados](/admin/identity-and-access-management/using-built-in-authentication/disabling-unauthenticated-sign-ups)". {% data reusables.enterprise_user_management.alternatively-enable-external-authentication %} diff --git a/translations/es-ES/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/enabling-encrypted-assertions.md b/translations/es-ES/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/enabling-encrypted-assertions.md index b662bfe63e..b2cea03ad2 100644 --- a/translations/es-ES/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/enabling-encrypted-assertions.md +++ b/translations/es-ES/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/enabling-encrypted-assertions.md @@ -57,4 +57,4 @@ To enable encrypted assertions, you must provide {% data variables.product.produ 1. Haz clic en **Guardar parámetros**. {% data reusables.enterprise_site_admin_settings.wait-for-configuration-run %} -Si habilitaste la depuración de SAML para probar la autenticación con las aserciones cifradas, inhabilita la depuración de SAML cuando termines de hacer las pruebas. For more information, see "[Troubleshooting SAML authentication](/admin/identity-and-access-management/using-saml-for-enterprise-iam/troubleshooting-saml-authentication#configuring-saml-debugging)." +Si habilitaste la depuración de SAML para probar la autenticación con las aserciones cifradas, inhabilita la depuración de SAML cuando termines de hacer las pruebas. Para obtener más información, consulta la sección "[Solucionar problemas de la autenticación de SAML](/admin/identity-and-access-management/using-saml-for-enterprise-iam/troubleshooting-saml-authentication#configuring-saml-debugging)". diff --git a/translations/es-ES/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/saml-configuration-reference.md b/translations/es-ES/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/saml-configuration-reference.md index c9957081a2..6d19380a2b 100644 --- a/translations/es-ES/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/saml-configuration-reference.md +++ b/translations/es-ES/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/saml-configuration-reference.md @@ -43,31 +43,31 @@ The SP metadata for an organization on {% data variables.product.product_locatio The SP metadata for an enterprise on {% data variables.product.product_location %} is available at `https://github.com/enterprises/ENTERPRISE/saml/metadata`, where **ENTERPRISE** is the name of your enterprise on {% data variables.product.product_location %}. -| Valor | Otros nombres | Descripción | Ejemplo | -|:--------------------------------------------------------- |:------------------------------------ |:-------------------------------------------------------------------------------------- |:-------------------------------------------------------- | -| ID de Entidad de SP | SP URL, audience restriction | The top-level URL for your enterprise on {% data variables.product.product_location %} | `https://github.com/enterprises/ENTERPRISE` | -| URL del Servicio de Consumidor de Aserciones (ACS) del SP | Reply, recipient, or destination URL | URL a la que el IdP enviará respuestas de SAML | `https://github.com/enterprises/ENTERPRISE/saml/consume` | -| URL de inicio de sesión único (SSO) del SP | | URL en donde el IdP comienza con SSO | `https://github.com/enterprises/ENTERPRISE/saml/sso` | +| Valor | Otros nombres | Descripción | Ejemplo | +|:--------------------------------------------------------- |:---------------------------------------- |:-------------------------------------------------------------------------------------- |:-------------------------------------------------------- | +| ID de Entidad de SP | URL de SP, restricción de la audiencia | The top-level URL for your enterprise on {% data variables.product.product_location %} | `https://github.com/enterprises/ENTERPRISE` | +| URL del Servicio de Consumidor de Aserciones (ACS) del SP | URL de respuesta, receptora o de destino | URL a la que el IdP enviará respuestas de SAML | `https://github.com/enterprises/ENTERPRISE/saml/consume` | +| URL de inicio de sesión único (SSO) del SP | | URL en donde el IdP comienza con SSO | `https://github.com/enterprises/ENTERPRISE/saml/sso` | {% elsif ghes %} -The SP metadata for {% data variables.product.product_location %} is available at `http(s)://HOSTNAME/saml/metadata`, where **HOSTNAME** is the hostname for your instance. {% data variables.product.product_name %} uses the `urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST` binding. +The SP metadata for {% data variables.product.product_location %} is available at `http(s)://HOSTNAME/saml/metadata`, where **HOSTNAME** is the hostname for your instance. {% data variables.product.product_name %} utiliza el enlace `urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST`. -| Valor | Otros nombres | Descripción | Ejemplo | -|:--------------------------------------------------------- |:------------------------------------ |:---------------------------------------------------------------- |:--------------------------------- | -| ID de Entidad de SP | SP URL, audience restriction | Your top-level URL for {% data variables.product.product_name %} | `http(s)://HOSTNAME` | -| URL del Servicio de Consumidor de Aserciones (ACS) del SP | Reply, recipient, or destination URL | URL a la que el IdP enviará respuestas de SAML | `http(s)://HOSTNAME/saml/consume` | -| URL de inicio de sesión único (SSO) del SP | | URL en donde el IdP comienza con SSO | `http(s)://HOSTNAME/sso` | +| Valor | Otros nombres | Descripción | Ejemplo | +|:--------------------------------------------------------- |:---------------------------------------- |:---------------------------------------------------------------- |:--------------------------------- | +| ID de Entidad de SP | URL de SP, restricción de la audiencia | Your top-level URL for {% data variables.product.product_name %} | `http(s)://HOSTNAME` | +| URL del Servicio de Consumidor de Aserciones (ACS) del SP | URL de respuesta, receptora o de destino | URL a la que el IdP enviará respuestas de SAML | `http(s)://HOSTNAME/saml/consume` | +| URL de inicio de sesión único (SSO) del SP | | URL en donde el IdP comienza con SSO | `http(s)://HOSTNAME/sso` | {% elsif ghae %} -The SP metadata for your enterprise on {% data variables.product.product_name %} is available at `https://HOSTNAME/saml/metadata`, where **HOSTNAME** is the hostname for your enterprise on {% data variables.product.product_name %}. {% data variables.product.product_name %} uses the `urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST` binding. +The SP metadata for your enterprise on {% data variables.product.product_name %} is available at `https://HOSTNAME/saml/metadata`, where **HOSTNAME** is the hostname for your enterprise on {% data variables.product.product_name %}. {% data variables.product.product_name %} utiliza el enlace `urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST`. -| Valor | Otros nombres | Descripción | Ejemplo | -|:--------------------------------------------------------- |:------------------------------------ |:---------------------------------------------------------------- |:------------------------------- | -| ID de Entidad de SP | SP URL, audience restriction | Your top-level URL for {% data variables.product.product_name %} | `https://HOSTNAME` | -| URL del Servicio de Consumidor de Aserciones (ACS) del SP | Reply, recipient, or destination URL | URL a la que el IdP enviará respuestas de SAML | `https://HOSTNAME/saml/consume` | -| URL de inicio de sesión único (SSO) del SP | | URL en donde el IdP comienza con SSO | `https://HOSTNAME/sso` | +| Valor | Otros nombres | Descripción | Ejemplo | +|:--------------------------------------------------------- |:---------------------------------------- |:----------------------------------------------------------------------- |:------------------------------- | +| ID de Entidad de SP | URL de SP, restricción de la audiencia | Tu URL de más alto nivel para {% data variables.product.product_name %} | `https://HOSTNAME` | +| URL del Servicio de Consumidor de Aserciones (ACS) del SP | URL de respuesta, receptora o de destino | URL a la que el IdP enviará respuestas de SAML | `https://HOSTNAME/saml/consume` | +| URL de inicio de sesión único (SSO) del SP | | URL en donde el IdP comienza con SSO | `https://HOSTNAME/sso` | {% endif %} @@ -75,14 +75,14 @@ The SP metadata for your enterprise on {% data variables.product.product_name %} The following SAML attributes are available for {% data variables.product.product_name %}.{% ifversion ghes %} You can change the attribute names in the management console, with the exception of the `administrator` attribute. For more information, see "[Accessing the management console](/admin/configuration/configuring-your-enterprise/accessing-the-management-console)."{% endif %} -| Nombre | Required? | Descripción | -|:--------------------- |:--------- |:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `ID del nombre` | Sí | Un identificador de usuario persistente. Se puede usar cualquier formato de identificador de nombre persistente. {% ifversion ghec %}If you use an enterprise with {% data variables.product.prodname_emus %}, {% endif %}{% data variables.product.product_name %} will normalize the `NameID` element to use as a username unless one of the alternative assertions is provided. For more information, see "[Username considerations for external authentication](/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication)." | -| `SessionNotOnOrAfter` | No | The date that {% data variables.product.product_name %} invalidates the associated session. After invalidation, the person must authenticate once again to access {% ifversion ghec or ghae %}your enterprise's resources{% elsif ghes %}{% data variables.product.product_location %}{% endif %}. For more information, see "[Session duration and timeout](#session-duration-and-timeout)." | +| Nombre | Required? | Descripción | +|:--------------------- |:--------- |:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `ID del nombre` | Sí | Un identificador de usuario persistente. Se puede usar cualquier formato de identificador de nombre persistente. {% ifversion ghec %}If you use an enterprise with {% data variables.product.prodname_emus %}, {% endif %}{% data variables.product.product_name %} will normalize the `NameID` element to use as a username unless one of the alternative assertions is provided. Para obtener más información, consulta la sección "[Consideraciones de nombre de usuario para la autenticación externa](/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication)". | +| `SessionNotOnOrAfter` | No | The date that {% data variables.product.product_name %} invalidates the associated session. After invalidation, the person must authenticate once again to access {% ifversion ghec or ghae %}your enterprise's resources{% elsif ghes %}{% data variables.product.product_location %}{% endif %}. For more information, see "[Session duration and timeout](#session-duration-and-timeout)." | {%- ifversion ghes or ghae %} | `administrator` | No | When the value is `true`, {% data variables.product.product_name %} will automatically promote the user to be a {% ifversion ghes %}site administrator{% elsif ghae %}enterprise owner{% endif %}. Any other value or a non-existent value will demote the account and remove administrative access. | | `username` | No | The username for {% data variables.product.product_location %}. | {%- endif %} -| `full_name` | No | {% ifversion ghec %}If you configure SAML SSO for an enterprise and you use {% data variables.product.prodname_emus %}, the{% else %}The{% endif %} full name of the user to display on the user's profile page. | | `emails` | No | Las direcciones de correo electrónico del usuario.{% ifversion ghes or ghae %} Puedes especificar más de una dirección.{% endif %}{% ifversion ghec or ghes %} Si sincronizas el uso de licencias entre {% data variables.product.prodname_ghe_server %} y {% data variables.product.prodname_ghe_cloud %}, {% data variables.product.prodname_github_connect %} utiliza `emails` para identificar a los usuarios únicos entre los productos. Para obtener más información, consulta la sección "[Sincronizar el uso de licencias entre {% data variables.product.prodname_ghe_server %} y {% data variables.product.prodname_ghe_cloud %}](/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud)".{% endif %} | | `public_keys` | No | {% ifversion ghec %}Si configuras el SSO de SAML para una empresa y utilizas {% data variables.product.prodname_emus %}, las{% else %}Las{% endif %}llaves SSH públicas para el usuario. You can specify more than one key. | | `gpg_keys` | No | {% ifversion ghec %}If you configure SAML SSO for an enterprise and you use {% data variables.product.prodname_emus %}, the{% else %}The{% endif %} GPG keys for the user. You can specify more than one key. | +| `full_name` | No | {% ifversion ghec %}If you configure SAML SSO for an enterprise and you use {% data variables.product.prodname_emus %}, the{% else %}The{% endif %} full name of the user to display on the user's profile page. | | `emails` | No | Las direcciones de correo electrónico del usuario.{% ifversion ghes or ghae %} Puedes especificar más de una dirección.{% endif %}{% ifversion ghec or ghes %} Si sincronizas el uso de licencias entre {% data variables.product.prodname_ghe_server %} y {% data variables.product.prodname_ghe_cloud %}, {% data variables.product.prodname_github_connect %} utiliza `emails` para identificar a los usuarios únicos entre los productos. Para obtener más información, consulta la sección "[Sincronizar el uso de licencias entre {% data variables.product.prodname_ghe_server %} y {% data variables.product.prodname_ghe_cloud %}](/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud)".{% endif %} | | `public_keys` | No | {% ifversion ghec %}Si configuras el SSO de SAML para una empresa y utilizas {% data variables.product.prodname_emus %}, las{% else %}Las{% endif %}llaves SSH públicas para el usuario. You can specify more than one key. | | `gpg_keys` | No | {% ifversion ghec %}If you configure SAML SSO for an enterprise and you use {% data variables.product.prodname_emus %}, the{% else %}The{% endif %} GPG keys for the user. Puedes especificar más de una clave. | Para especificar más de un valor para un atributo, utiliza elementos múltiples de ``. @@ -128,7 +128,7 @@ Para especificar más de un valor para un atributo, utiliza elementos múltiples ## Session duration and timeout -To prevent a person from authenticating with your IdP and staying authorized indefinitely, {% data variables.product.product_name %} periodically invalidates the session for each user account with access to {% ifversion ghec or ghae %}your enterprise's resources{% elsif ghes %}{% data variables.product.product_location %}{% endif %}. After invalidation, the person must authenticate with your IdP once again. By default, if your IdP does not assert a value for the `SessionNotOnOrAfter` attribute, {% data variables.product.product_name %} invalidates a session {% ifversion ghec %}24 hours{% elsif ghes or ghae %}one week{% endif %} after successful authentication with your IdP. +Para prevenir que una persona se autentique con tu IdP y se mantenga autorizad por tiempo indefinido, {% data variables.product.product_name %} invalida con frecuencia la sesión de cada cuenta de usuario con acceso a {% ifversion ghec or ghae %}los recursos de tu empresa{% elsif ghes %}{% data variables.product.product_location %}{% endif %}. After invalidation, the person must authenticate with your IdP once again. By default, if your IdP does not assert a value for the `SessionNotOnOrAfter` attribute, {% data variables.product.product_name %} invalidates a session {% ifversion ghec %}24 hours{% elsif ghes or ghae %}one week{% endif %} after successful authentication with your IdP. To customize the session duration, you may be able to define the value of the `SessionNotOnOrAfter` attribute on your IdP. If you define a value less than 24 hours, {% data variables.product.product_name %} may prompt people to authenticate every time {% data variables.product.product_name %} initiates a redirect. diff --git a/translations/es-ES/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/troubleshooting-saml-authentication.md b/translations/es-ES/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/troubleshooting-saml-authentication.md index 2bfb191e2d..a1af4772e3 100644 --- a/translations/es-ES/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/troubleshooting-saml-authentication.md +++ b/translations/es-ES/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/troubleshooting-saml-authentication.md @@ -65,7 +65,7 @@ Cuando el usuario vuelve a ingresar, {% data variables.product.prodname_ghe_serv > Another user already owns the account. Please have your administrator check the authentication log. -Este mensaje habitualmente indica que el nombre de usuario o dirección de correo electrónico cambió en el IdP. Asegúrate de que el mapeo de la `NameID` de la cuenta de usuario de {% data variables.product.prodname_ghe_server %} coincida con la `NameID` en tu IdP. For more information, see "[Updating a user's SAML `NameID`](/admin/identity-and-access-management/using-saml-for-enterprise-iam/updating-a-users-saml-nameid)." +Este mensaje habitualmente indica que el nombre de usuario o dirección de correo electrónico cambió en el IdP. Asegúrate de que el mapeo de la `NameID` de la cuenta de usuario de {% data variables.product.prodname_ghe_server %} coincida con la `NameID` en tu IdP. Para obtener más información, consulta la sección "[Actualizar la `NameID` de SAML de un usuario](/admin/identity-and-access-management/using-saml-for-enterprise-iam/updating-a-users-saml-nameid)". ## Si la respuesta SAML no está firmada o la firma no coincide con los contenidos, se presentará el siguiente mensaje de error en el registro de autenticación: diff --git a/translations/es-ES/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise.md b/translations/es-ES/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise.md index 41613cb015..34a81c4019 100644 --- a/translations/es-ES/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise.md +++ b/translations/es-ES/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise.md @@ -23,7 +23,7 @@ topics: - Security --- -## About audit logs +## Acerca de las bitácoras de auditoría {% data reusables.audit_log.retention-periods %} @@ -50,7 +50,7 @@ For a full list of audit log actions that may appear in your enterprise audit lo {% ifversion ghec %} ## Git events -Git events data, such as cloning, fetching, and pushing is logged. For more information, see "[Streaming the audit log for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise)." +Git events data, such as cloning, fetching, and pushing is logged. Para obtener más información, consulta la sección "[Transmitir la bitácora de auditoría de tu empresa](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise)". {% endif %} diff --git a/translations/es-ES/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise.md b/translations/es-ES/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise.md index 2135884fdd..09b5f071d4 100644 --- a/translations/es-ES/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise.md +++ b/translations/es-ES/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise.md @@ -126,9 +126,9 @@ topics: | `business.set_fork_pr_workflows_policy` | The policy for workflows on private repository forks was changed. Para obtener más información, consulta la sección "{% ifversion ghec %}[Requerir políticas para las {% data variables.product.prodname_actions %} en una empresa](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise#enforcing-a-policy-for-fork-pull-requests-in-private-repositories){% else ifversion ghes > 2.22 %}[Habilitar los flujos de trabajo para las bifurcaciones de repositorios privados](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enforcing-github-actions-policies-for-your-enterprise#enabling-workflows-for-private-repository-forks){% endif %}". {%- endif %} {%- ifversion ghes %} -| `business.update_actions_settings` | An enterprise owner or site administrator updated {% data variables.product.prodname_actions %} policy settings for an enterprise. For more information, see "[Enforcing policies for GitHub Actions in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise)." +| `business.update_actions_settings` | An enterprise owner or site administrator updated {% data variables.product.prodname_actions %} policy settings for an enterprise. Para obtener más información, consulta la sección "[Requerir políticas para las GitHub Actions en tu empresa](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise)". {%- endif %} -| `business.update_default_repository_permission` | The base repository permission setting was updated for all organizations in an enterprise. For more information, see "[Enforcing a policy for base repository permissions](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-base-repository-permissions)." | `business.update_member_repository_creation_permission` | The repository creation setting was updated for an enterprise. For more information, see "[Enforcing a policy for repository creation](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-repository-creation)." | `business.update_member_repository_invitation_permission` | The policy setting for enterprise members inviting outside collaborators to repositories was updated. For more information, see "[Enforcing a policy for inviting outside collaborators to repositories](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-inviting-outside-collaborators-to-repositories)." +| `business.update_default_repository_permission` | The base repository permission setting was updated for all organizations in an enterprise. Para obtener más información, consulta la sección "[Requerir una política para los permisos de los repositorios base](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-base-repository-permissions)". | `business.update_member_repository_creation_permission` | The repository creation setting was updated for an enterprise. For more information, see "[Enforcing a policy for repository creation](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-repository-creation)." | `business.update_member_repository_invitation_permission` | The policy setting for enterprise members inviting outside collaborators to repositories was updated. For more information, see "[Enforcing a policy for inviting outside collaborators to repositories](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-inviting-outside-collaborators-to-repositories)." {%- ifversion ghec %} | `business.update_saml_provider_settings` | The SAML single sign-on provider settings for an enterprise were updated. {%- endif %} @@ -145,10 +145,10 @@ topics: ### `checks` category actions -| Acción | Descripción | -| ------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `checks.auto_trigger_disabled` | Automatic creation of check suites was disabled on a repository in the organization or enterprise. For more information, see "[Update repository preferences for check suites](/rest/reference/checks#update-repository-preferences-for-check-suites)." | -| `checks.auto_trigger_enabled` | Automatic creation of check suites was enabled on a repository in the organization or enterprise. For more information, see "[Update repository preferences for check suites](/rest/reference/checks#update-repository-preferences-for-check-suites)." | +| Acción | Descripción | +| ------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `checks.auto_trigger_disabled` | Automatic creation of check suites was disabled on a repository in the organization or enterprise. For more information, see "[Update repository preferences for check suites](/rest/reference/checks#update-repository-preferences-for-check-suites)." | +| `checks.auto_trigger_enabled` | Automatic creation of check suites was enabled on a repository in the organization or enterprise. Para obtener más información, consulta la sección "[Actualizar las preferencias de repositorio para las suites de verificación](/rest/reference/checks#update-repository-preferences-for-check-suites)". | {%- ifversion fpt or ghec %} | `checks.delete_logs` | Logs in a check suite were deleted. {%- endif %} @@ -181,11 +181,11 @@ topics: {%- ifversion ghes %} ### `config_entry` category actions -| Acción | Descripción | -| ---------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `config_entry.create` | A configuration setting was created. These events are only visible in the site admin audit log. The type of events recorded relate to:
- Enterprise settings and policies
- Organization and repository permissions and settings
- Git, Git LFS, {% data variables.product.prodname_github_connect %}, {% data variables.product.prodname_registry %}, project, and code security settings. | -| `config_entry.destroy` | A configuration setting was deleted. These events are only visible in the site admin audit log. El tipo de eventos registrado se relaciona con:
- Políticas y ajustes de empresa
- Permisos y ajustes de repositorio y organización
- Git, LFS de Git, {% data variables.product.prodname_github_connect %}, {% data variables.product.prodname_registry %}, proyecto, y ajustes de seguridad de código. | -| `config_entry.update` | A configuration setting was edited. These events are only visible in the site admin audit log. El tipo de eventos registrado se relaciona con:
- Políticas y ajustes de empresa
- Permisos y ajustes de repositorio y organización
- Git, LFS de Git, {% data variables.product.prodname_github_connect %}, {% data variables.product.prodname_registry %}, proyecto, y ajustes de seguridad de código. | +| Acción | Descripción | +| ---------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `config_entry.create` | A configuration setting was created. These events are only visible in the site admin audit log. The type of events recorded relate to:
- Enterprise settings and policies
- Organization and repository permissions and settings
- Git, Git LFS, {% data variables.product.prodname_github_connect %}, {% data variables.product.prodname_registry %}, project, and code security settings. | +| `config_entry.destroy` | A configuration setting was deleted. Estos eventos solo se pueden ver en la bitácora de auditoría del administrador de sitio. El tipo de eventos registrado se relaciona con:
- Políticas y ajustes de empresa
- Permisos y ajustes de repositorio y organización
- Git, LFS de Git, {% data variables.product.prodname_github_connect %}, {% data variables.product.prodname_registry %}, proyecto, y ajustes de seguridad de código. | +| `config_entry.update` | A configuration setting was edited. Estos eventos solo se pueden ver en la bitácora de auditoría del administrador de sitio. El tipo de eventos registrado se relaciona con:
- Políticas y ajustes de empresa
- Permisos y ajustes de repositorio y organización
- Git, LFS de Git, {% data variables.product.prodname_github_connect %}, {% data variables.product.prodname_registry %}, proyecto, y ajustes de seguridad de código. | {%- endif %} {%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-4864 %} @@ -313,12 +313,12 @@ topics: {%- ifversion ghec %} ### `enterprise_domain` category actions -| Acción | Descripción | -| --------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `enterprise_domain.approve` | An enterprise domain was approved for an enterprise. For more information, see "[Approving a domain for your enterprise account](/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise#approving-a-domain-for-your-enterprise-account)." | -| `enterprise_domain.create` | An enterprise domain was added to an enterprise. For more information, see "[Verifying a domain for your enterprise account](/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise#verifying-a-domain-for-your-enterprise-account)." | -| `enterprise_domain.destroy` | An enterprise domain was removed from an enterprise. For more information, see "[Removing an approved or verified domain](/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise#removing-an-approved-or-verified-domain)." | -| `enterprise_domain.verify` | An enterprise domain was verified for an enterprise. For more information, see "[Verifying a domain for your enterprise account](/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise#verifying-a-domain-for-your-enterprise-account)." | +| Acción | Descripción | +| --------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `enterprise_domain.approve` | An enterprise domain was approved for an enterprise. For more information, see "[Approving a domain for your enterprise account](/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise#approving-a-domain-for-your-enterprise-account)." | +| `enterprise_domain.create` | An enterprise domain was added to an enterprise. For more information, see "[Verifying a domain for your enterprise account](/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise#verifying-a-domain-for-your-enterprise-account)." | +| `enterprise_domain.destroy` | An enterprise domain was removed from an enterprise. For more information, see "[Removing an approved or verified domain](/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise#removing-an-approved-or-verified-domain)." | +| `enterprise_domain.verify` | An enterprise domain was verified for an enterprise. Para obtener más información, consulta la sección "[Verificar un dominio para tu cuenta empresarial](/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise#verifying-a-domain-for-your-enterprise-account)". | ### `enterprise_installation` category actions @@ -332,15 +332,15 @@ topics: {%- ifversion fpt or ghec %} ### acciones de la categoría `environment` -| Acción | Descripción | -| ------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `environment.add_protection_rule` | A {% data variables.product.prodname_actions %} environment protection rule was created via the API. For more information, see "[Environment protection rules](/actions/deployment/targeting-different-environments/using-environments-for-deployment#environment-protection-rules)." | -| `environment.create_actions_secret` | A secret was created for a {% data variables.product.prodname_actions %} environment via the API. For more information, see "[Environment secrets](/actions/deployment/targeting-different-environments/using-environments-for-deployment#environment-secrets)." | -| `environment.delete` | An environment was deleted via the API. For more information, see "[Deleting an environment](/actions/deployment/targeting-different-environments/using-environments-for-deployment#deleting-an-environment)." | -| `environment.remove_actions_secret` | A secret was deleted for a {% data variables.product.prodname_actions %} environment via the API. For more information, see "[Environment secrets](/actions/deployment/targeting-different-environments/using-environments-for-deployment#environment-secrets)." | -| `environment.remove_protection_rule` | A {% data variables.product.prodname_actions %} environment protection rule was deleted via the API. For more information, see "[Environment protection rules](/actions/deployment/targeting-different-environments/using-environments-for-deployment#environment-protection-rules)." | -| `environment.update_actions_secret` | A secret was updated for a {% data variables.product.prodname_actions %} environment via the API. For more information, see "[Environment secrets](/actions/deployment/targeting-different-environments/using-environments-for-deployment#environment-secrets)." | -| `environment.update_protection_rule` | A {% data variables.product.prodname_actions %} environment protection rule was updated via the API. For more information, see "[Environment protection rules](/actions/deployment/targeting-different-environments/using-environments-for-deployment#environment-protection-rules)." | +| Acción | Descripción | +| ------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `environment.add_protection_rule` | A {% data variables.product.prodname_actions %} environment protection rule was created via the API. For more information, see "[Environment protection rules](/actions/deployment/targeting-different-environments/using-environments-for-deployment#environment-protection-rules)." | +| `environment.create_actions_secret` | A secret was created for a {% data variables.product.prodname_actions %} environment via the API. For more information, see "[Environment secrets](/actions/deployment/targeting-different-environments/using-environments-for-deployment#environment-secrets)." | +| `environment.delete` | An environment was deleted via the API. For more information, see "[Deleting an environment](/actions/deployment/targeting-different-environments/using-environments-for-deployment#deleting-an-environment)." | +| `environment.remove_actions_secret` | A secret was deleted for a {% data variables.product.prodname_actions %} environment via the API. Para obtener más información, consulta la sección ["Secretos de ambiente](/actions/deployment/targeting-different-environments/using-environments-for-deployment#environment-secrets)". | +| `environment.remove_protection_rule` | A {% data variables.product.prodname_actions %} environment protection rule was deleted via the API. Para obtener más información, consulta la sección "[reglas de protección de ambiente](/actions/deployment/targeting-different-environments/using-environments-for-deployment#environment-protection-rules)". | +| `environment.update_actions_secret` | A secret was updated for a {% data variables.product.prodname_actions %} environment via the API. Para obtener más información, consulta la sección ["Secretos de ambiente](/actions/deployment/targeting-different-environments/using-environments-for-deployment#environment-secrets)". | +| `environment.update_protection_rule` | A {% data variables.product.prodname_actions %} environment protection rule was updated via the API. Para obtener más información, consulta la sección "[reglas de protección de ambiente](/actions/deployment/targeting-different-environments/using-environments-for-deployment#environment-protection-rules)". | {%- endif %} {%- ifversion ghae %} @@ -463,11 +463,11 @@ topics: ### `issues` category actions -| Acción | Descripción | -| ------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `issues.deletes_disabled` | The ability for enterprise members to delete issues was disabled. Members cannot delete issues in any organizations in an enterprise. For more information, see "[Enforcing a policy for deleting issues](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-deleting-issues)." | -| `issues.deletes_enabled` | The ability for enterprise members to delete issues was enabled. Members can delete issues in any organizations in an enterprise. For more information, see "[Enforcing a policy for deleting issues](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-deleting-issues)." | -| `issues.deletes_policy_cleared` | An enterprise owner{% ifversion ghes %} or site administrator{% endif %} cleared the policy setting for allowing members to delete issues in an enterprise. For more information, see "[Enforcing a policy for deleting issues](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-deleting-issues)." | +| Acción | Descripción | +| ------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `issues.deletes_disabled` | The ability for enterprise members to delete issues was disabled. Members cannot delete issues in any organizations in an enterprise. For more information, see "[Enforcing a policy for deleting issues](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-deleting-issues)." | +| `issues.deletes_enabled` | The ability for enterprise members to delete issues was enabled. Members can delete issues in any organizations in an enterprise. Para obtener más información, consulta la sección "[Requerir una política para borrar las propuestas](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-deleting-issues)". | +| `issues.deletes_policy_cleared` | An enterprise owner{% ifversion ghes %} or site administrator{% endif %} cleared the policy setting for allowing members to delete issues in an enterprise. Para obtener más información, consulta la sección "[Requerir una política para borrar las propuestas](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-deleting-issues)". | {%- ifversion fpt or ghec %} ### acciones de la categoría `marketplace_agreement_signature` @@ -490,33 +490,33 @@ topics: ### Acciones de la categoría `members_can_create_pages` -| Acción | Descripción | -| ---------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `members_can_create_pages.disable` | The ability for members to publish {% data variables.product.prodname_pages %} was disabled. Members cannot publish {% data variables.product.prodname_pages %} in an organization. For more information, see "[Managing the publication of GitHub Pages sites for your organization](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)." | -| `members_can_create_pages.enable` | The ability for members to publish {% data variables.product.prodname_pages %} was enabled. Members can publish {% data variables.product.prodname_pages %} in an organization. For more information, see "[Managing the publication of GitHub Pages sites for your organization](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)." | +| Acción | Descripción | +| ---------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `members_can_create_pages.disable` | The ability for members to publish {% data variables.product.prodname_pages %} was disabled. Members cannot publish {% data variables.product.prodname_pages %} in an organization. Para obtener más información, consulta la sección "[Administrar la publicación de los sitios de GitHub Pages para tu organización](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)". | +| `members_can_create_pages.enable` | The ability for members to publish {% data variables.product.prodname_pages %} was enabled. Members can publish {% data variables.product.prodname_pages %} in an organization. Para obtener más información, consulta la sección "[Administrar la publicación de los sitios de GitHub Pages para tu organización](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)". | ### `members_can_create_private_pages` category actions -| Acción | Descripción | -| ------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `members_can_create_private_pages.disable` | The ability for members to publish private {% data variables.product.prodname_pages %} was disabled. Members cannot publish private {% data variables.product.prodname_pages %} in an organization. For more information, see "[Managing the publication of GitHub Pages sites for your organization](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)." | -| `members_can_create_private_pages.enable` | The ability for members to publish private {% data variables.product.prodname_pages %} was enabled. Members can publish private {% data variables.product.prodname_pages %} in an organization. For more information, see "[Managing the publication of GitHub Pages sites for your organization](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)." | +| Acción | Descripción | +| ------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `members_can_create_private_pages.disable` | The ability for members to publish private {% data variables.product.prodname_pages %} was disabled. Members cannot publish private {% data variables.product.prodname_pages %} in an organization. For more information, see "[Managing the publication of GitHub Pages sites for your organization](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)." | +| `members_can_create_private_pages.enable` | The ability for members to publish private {% data variables.product.prodname_pages %} was enabled. Members can publish private {% data variables.product.prodname_pages %} in an organization. Para obtener más información, consulta la sección "[Administrar la publicación de los sitios de GitHub Pages para tu organización](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)". | ### `members_can_create_public_pages` category actions -| Acción | Descripción | -| ----------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `members_can_create_public_pages.disable` | The ability for members to publish public {% data variables.product.prodname_pages %} was disabled. Members cannot publish public {% data variables.product.prodname_pages %} in an organization. For more information, see "[Managing the publication of GitHub Pages sites for your organization](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)." | -| `members_can_create_public_pages.enable` | The ability for members to publish public {% data variables.product.prodname_pages %} was enabled. Members can publish public {% data variables.product.prodname_pages %} in an organization. For more information, see "[Managing the publication of GitHub Pages sites for your organization](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)." | +| Acción | Descripción | +| ----------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `members_can_create_public_pages.disable` | The ability for members to publish public {% data variables.product.prodname_pages %} was disabled. Members cannot publish public {% data variables.product.prodname_pages %} in an organization. Para obtener más información, consulta la sección "[Administrar la publicación de los sitios de GitHub Pages para tu organización](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)". | +| `members_can_create_public_pages.enable` | The ability for members to publish public {% data variables.product.prodname_pages %} was enabled. Members can publish public {% data variables.product.prodname_pages %} in an organization. Para obtener más información, consulta la sección "[Administrar la publicación de los sitios de GitHub Pages para tu organización](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)". | {%- ifversion ghec or ghes or ghae %} ### `members_can_delete_repos` category actions -| Acción | Descripción | -| ---------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| `members_can_delete_repos.clear` | An enterprise owner{% ifversion ghes %} or site administrator{% endif %} cleared the policy setting for deleting or transfering repositories in any organizations in an enterprise. For more information, see "[Enforcing a policy for repository deletion and transfer](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-repository-deletion-and-transfer)." | -| `members_can_delete_repos.disable` | The ability for enterprise members to delete repositories was disabled. Members cannot delete or transfer repositories in any organizations in an enterprise. For more information, see "[Enforcing a policy for repository deletion and transfer](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-repository-deletion-and-transfer)." | -| `members_can_delete_repos.enable` | The ability for enterprise members to delete repositories was enabled. Members can delete or transfer repositories in any organizations in an enterprise. For more information, see "[Enforcing a policy for repository deletion and transfer](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-repository-deletion-and-transfer)." | +| Acción | Descripción | +| ---------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `members_can_delete_repos.clear` | An enterprise owner{% ifversion ghes %} or site administrator{% endif %} cleared the policy setting for deleting or transfering repositories in any organizations in an enterprise. For more information, see "[Enforcing a policy for repository deletion and transfer](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-repository-deletion-and-transfer)." | +| `members_can_delete_repos.disable` | The ability for enterprise members to delete repositories was disabled. Members cannot delete or transfer repositories in any organizations in an enterprise. Para obtener más información, consulta la sección "[Requerir una política para el borrado y transferencia de repositorios](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-repository-deletion-and-transfer)". | +| `members_can_delete_repos.enable` | The ability for enterprise members to delete repositories was enabled. Members can delete or transfer repositories in any organizations in an enterprise. Para obtener más información, consulta la sección "[Requerir una política para el borrado y transferencia de repositorios](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-repository-deletion-and-transfer)". | ### `members_can_view_dependency_insights` category actions @@ -592,7 +592,7 @@ topics: {%- ifversion fpt or ghec %} | `org.codespaces_trusted_repo_access_granted` | {% data variables.product.prodname_codespaces %} was granted trusted repository access to all other repositories in an organization. Para obtener más información, consulta la sección "[Administrar el acceso de un repositorio a los codespces de tu organización](/codespaces/managing-codespaces-for-your-organization/managing-repository-access-for-your-organizations-codespaces)". | `org.codespaces_trusted_repo_access_revoked` | {% data variables.product.prodname_codespaces %} trusted repository access to all other repositories in an organization was revoked. Para obtener más información, consulta la sección "[Administrar el acceso de un repositorio a los codespces de tu organización](/codespaces/managing-codespaces-for-your-organization/managing-repository-access-for-your-organizations-codespaces)". {%- endif %} -| `org.config.disable_collaborators_only` | The interaction limit for collaborators only for an organization was disabled. |{% ifversion fpt or ghec %}Para obtener más información, consulta la sección "[Limitar las interaciones en tu organización](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization#limiting-interactions-in-your-organization)."{% endif %}| | `org.config.disable_contributors_only` | Se inhabilitó el límite de interacción para los contribuyentes previos únicamente para una organización. |{% ifversion fpt or ghec %}Para obtener más información, consulta la sección "[Limitar las interacciones en tu organización](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization#limiting-interactions-in-your-organization)."{% endif %}| | `org.config.disable_sockpuppet_disallowed` | Se inhabilitó el límite de interacciones para los usuarios existentes únicamente para una organización. |{% ifversion fpt or ghec %}Para obtener más información, consulta la sección "[Limitar las interaciones en tu organización](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization#limiting-interactions-in-your-organization)."{% endif %}| | `org.config.enable_collaborators_only` | Se habilitó el límite de interacción para los colaboradores únicamente para una organización. |{% ifversion fpt or ghec %}Para obtener más información, consulta la sección "[Limitar las interaciones en tu organización](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization#limiting-interactions-in-your-organization)."{% endif %}| | `org.config.enable_contributors_only` | Se habilitó el límite de interacción para los contribuyentes previos únicamente para una organización. |{% ifversion fpt or ghec %}Para obtener más información, consulta la sección "[Limitar las interacciones en tu organización](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization#limiting-interactions-in-your-organization)."{% endif %}| | `org.config.enable_sockpuppet_disallowed` | Se habilitó el límite de interacción para los usuarios existentes únicamente para una organización. |{% ifversion fpt or ghec %}Para obtener más información, consulta la sección "[Limitar las interacciones en tu organización](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization#limiting-interactions-in-your-organization)."{% endif %}| | `org.confirm_business_invitation` | Se confirmó una invitación para que una organización se una a una empresa. |{% ifversion ghec %}For more information, see "[Inviting an organization to join your enterprise account](/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise#inviting-an-organization-to-join-your-enterprise-account)."{% endif %}| | `org.create` | An organization was created. Para obtener más información, consulta la sección "[Crear una organización nueva desde cero](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)". +| `org.config.disable_collaborators_only` | The interaction limit for collaborators only for an organization was disabled. |{% ifversion fpt or ghec %}Para obtener más información, consulta la sección "[Limitar las interaciones en tu organización](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization#limiting-interactions-in-your-organization)."{% endif %}| | `org.config.disable_contributors_only` | Se inhabilitó el límite de interacción para los contribuyentes previos únicamente para una organización. |{% ifversion fpt or ghec %}Para obtener más información, consulta la sección "[Limitar las interacciones en tu organización](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization#limiting-interactions-in-your-organization)."{% endif %}| | `org.config.disable_sockpuppet_disallowed` | Se inhabilitó el límite de interacciones para los usuarios existentes únicamente para una organización. |{% ifversion fpt or ghec %}Para obtener más información, consulta la sección "[Limitar las interaciones en tu organización](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization#limiting-interactions-in-your-organization)."{% endif %}| | `org.config.enable_collaborators_only` | Se habilitó el límite de interacción para los colaboradores únicamente para una organización. |{% ifversion fpt or ghec %}Para obtener más información, consulta la sección "[Limitar las interaciones en tu organización](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization#limiting-interactions-in-your-organization)."{% endif %}| | `org.config.enable_contributors_only` | Se habilitó el límite de interacción para los contribuyentes previos únicamente para una organización. |{% ifversion fpt or ghec %}Para obtener más información, consulta la sección "[Limitar las interacciones en tu organización](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization#limiting-interactions-in-your-organization)."{% endif %}| | `org.config.enable_sockpuppet_disallowed` | Se habilitó el límite de interacción para los usuarios existentes únicamente para una organización. |{% ifversion fpt or ghec %}Para obtener más información, consulta la sección "[Limitar las interacciones en tu organización](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization#limiting-interactions-in-your-organization)."{% endif %}| | `org.confirm_business_invitation` | Se confirmó una invitación para que una organización se una a una empresa. |{% ifversion ghec %}Para obtener más información, consulta la sección "[Invitar a una organización para que se una a tu cuenta empresarial](/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise#inviting-an-organization-to-join-your-enterprise-account)."{% endif %}| | `org.create` | Se creó una organización. Para obtener más información, consulta la sección "[Crear una organización nueva desde cero](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)". {%- ifversion fpt or ghec or ghes %} | `org.create_actions_secret` | A {% data variables.product.prodname_actions %} secret was created for an organization. Para obtener más información, consulta la sección "[Crear secretos cifrados para una organización](/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-an-organization)". {%- endif %} @@ -606,7 +606,7 @@ topics: {%- ifversion not ghae %} | `org.disable_two_factor_requirement` | An organization owner disabled a two-factor authentication requirement for all members{% ifversion fpt or ghec %}, billing managers,{% endif %} and outside collaborators in an organization. {%- endif %} -| `org.display_commenter_full_name_disabled` | An organization owner disabled the display of a commenter's full name in an organization. Members cannot see a comment author's full name. | `org.display_commenter_full_name_enabled` | An organization owner enabled the display of a commenter's full name in an organization. Members can see a comment author's full name. | `org.enable_member_team_creation_permission` | An organization owner allowed members to create teams. Para obtener más información, consulta "[Configurar los permisos de creación de equipo en tu organización](/organizations/managing-organization-settings/setting-team-creation-permissions-in-your-organization)." | `org.enable_reader_discussion_creation_permission` | An organization owner allowed users with read access to create discussions in an organization. {% ifversion fpt or ghec %}For more information, see "[Allowing or disallowing users with read access to create discussions](/organizations/managing-organization-settings/managing-discussion-creation-for-repositories-in-your-organization)."{% endif %} +| `org.display_commenter_full_name_disabled` | An organization owner disabled the display of a commenter's full name in an organization. Members cannot see a comment author's full name. | `org.display_commenter_full_name_enabled` | An organization owner enabled the display of a commenter's full name in an organization. Members can see a comment author's full name. | `org.enable_member_team_creation_permission` | An organization owner allowed members to create teams. Para obtener más información, consulta "[Configurar los permisos de creación de equipo en tu organización](/organizations/managing-organization-settings/setting-team-creation-permissions-in-your-organization)." | `org.enable_reader_discussion_creation_permission` | An organization owner allowed users with read access to create discussions in an organization. {% ifversion fpt or ghec %}Para obtener más información, consulta la sección "[Permitir o dejar de permitir que los usuarios con acceso de lectura creen debates](/organizations/managing-organization-settings/managing-discussion-creation-for-repositories-in-your-organization)".{% endif %} {%- ifversion fpt or ghec %} | `org.enable_oauth_app_restrictions` | Third-party application access restrictions for an organization were enabled. For more information, see "[Enabling OAuth App access restrictions for your organization](/organizations/restricting-access-to-your-organizations-data/enabling-oauth-app-access-restrictions-for-your-organization)." {%- endif %} @@ -616,7 +616,7 @@ topics: {%- ifversion not ghae %} | `org.enable_two_factor_requirement` | An organization owner requires two-factor authentication for all members{% ifversion fpt or ghec %}, billing managers,{% endif %} and outside collaborators in an organization. {%- endif %} -| `org.integration_manager_added` | An organization owner granted a member access to manage all GitHub Apps owned by an organization. | `org.integration_manager_removed` | An organization owner removed access to manage all GitHub Apps owned by an organization from an organization member. | `org.invite_member` | A new user was invited to join an organization. |{% ifversion fpt or ghec %}For more information, see "[Inviting users to join your organization](/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization)."{% endif %}| | `org.invite_to_business` | An organization was invited to join an enterprise. | `org.members_can_update_protected_branches.clear` | An organization owner unset a policy for whether members of an organization can update protected branches on repositories in an organization. Organization administrators can choose whether to allow updating protected branches settings. | `org.members_can_update_protected_branches.disable` | The ability for enterprise members to update protected branches was disabled. Only enterprise owners can update protected branches. | `org.members_can_update_protected_branches.enable` | The ability for enterprise members to update protected branches was enabled. Members of an organization can update protected branches. +| `org.integration_manager_added` | An organization owner granted a member access to manage all GitHub Apps owned by an organization. | `org.integration_manager_removed` | An organization owner removed access to manage all GitHub Apps owned by an organization from an organization member. | `org.invite_member` | A new user was invited to join an organization. |{% ifversion fpt or ghec %}For more information, see "[Inviting users to join your organization](/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization)."{% endif %}| | `org.invite_to_business` | An organization was invited to join an enterprise. | `org.members_can_update_protected_branches.clear` | An organization owner unset a policy for whether members of an organization can update protected branches on repositories in an organization. Los administradores de las organizaciones pudieron elegir si se permitía la actualización de los ajustes de ramas protegidas o no. | `org.members_can_update_protected_branches.disable` | The ability for enterprise members to update protected branches was disabled. Solo los propietarios de las empresas pueden actualizar las ramas protegidas. | `org.members_can_update_protected_branches.enable` | The ability for enterprise members to update protected branches was enabled. Members of an organization can update protected branches. {%- ifversion fpt or ghec %} | `org.oauth_app_access_approved` | An owner [granted organization access to an {% data variables.product.prodname_oauth_app %}](/organizations/restricting-access-to-your-organizations-data/approving-oauth-apps-for-your-organization). | `org.oauth_app_access_denied` | An owner [disabled a previously approved {% data variables.product.prodname_oauth_app %}'s access](/organizations/restricting-access-to-your-organizations-data/denying-access-to-a-previously-approved-oauth-app-for-your-organization) to an organization. | `org.oauth_app_access_requested` | An organization member requested that an owner grant an {% data variables.product.prodname_oauth_app %} access to an organization. {%- endif %} @@ -630,10 +630,10 @@ topics: {%- endif %} | `org.runner_group_updated` | The configuration of a self-hosted runner group was changed. Para obtener más información, consulta la sección "[Cambiar la política de acceso para un grupo de ejecutores auto-hospedados](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#changing-the-access-policy-of-a-self-hosted-runner-group)". | `org.runner_group_runner_removed` | The REST API was used to remove a self-hosted runner from a group. Para obtener más información, consulta la sección "[Eliminar un ejecutor auto-hospedado de un grupo en una organización](/rest/reference/actions#remove-a-self-hosted-runner-from-a-group-for-an-organization)". | `org.runner_group_runners_added` | A self-hosted runner was added to a group. Para obtener más información, consulta la sección [Mover un ejecutor auto-hospedado a un grupo](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#moving-a-self-hosted-runner-to-a-group). | `org.runner_group_runners_updated`| A runner group's list of members was updated. Para obtener más información, consulta la sección "[Configurar ejecutores auto-hospedados en un grupo para una organización](/rest/reference/actions#set-self-hosted-runners-in-a-group-for-an-organization)". {%- ifversion fpt or ghec %} -| `org.runner_group_visiblity_updated` | The visibility of a self-hosted runner group was updated via the REST API. For more information, see "[Update a self-hosted runner group for an organization](/rest/reference/actions#update-a-self-hosted-runner-group-for-an-organization)." +| `org.runner_group_visiblity_updated` | The visibility of a self-hosted runner group was updated via the REST API. Para obtener más información, consulta la sección "[Actualizar un grupo de ejecutores auto-hospedados para una organización](/rest/reference/actions#update-a-self-hosted-runner-group-for-an-organization)". {%- endif %} {%- if secret-scanning-audit-log-custom-patterns %} -| `org.secret_scanning_push_protection_disable` | An organization owner or administrator disabled push protection for secret scanning. For more information, see "[Protecting pushes with secret scanning](/enterprise-cloud@latest/code-security/secret-scanning/protecting-pushes-with-secret-scanning)." | `org.secret_scanning_push_protection_enable` | An organization owner or administrator enabled push protection for secret scanning. +| `org.secret_scanning_push_protection_disable` | An organization owner or administrator disabled push protection for secret scanning. Para obtener más información, consulta la sección "[Proteger las subidas de información con el escaneo de secretos](/enterprise-cloud@latest/code-security/secret-scanning/protecting-pushes-with-secret-scanning)". | `org.secret_scanning_push_protection_enable` | An organization owner or administrator enabled push protection for secret scanning. {%- endif %} {%- ifversion fpt or ghec or ghes > 3.1 or ghae %} | `org.self_hosted_runner_online` | The runner application was started. Solo se puede ver utilizando la API de REST; no está visible en la IU o en la exportación de JSON/CSV. Para obtener más información, consulta "[Comprobar el estado de un ejecutor autoalojado](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)." | `org.self_hosted_runner_offline` | The runner application was stopped. Solo se puede ver utilizando la API de REST; no está visible en la IU o en la exportación de JSON/CSV. Para obtener más información, consulta "[Comprobar el estado de un ejecutor autoalojado](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)." @@ -666,23 +666,23 @@ topics: {%- ifversion ghec or ghes or ghae %} ### acciones de la categoría `org_credential_authorization` -| Acción | Descripción | -| ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `org_credential_authorization.deauthorized` | A member deauthorized credentials for use with SAML single sign-on. | -| {% ifversion ghec or ghae %}For more information, see "[Authenticating with SAML single sign-on](/authentication/authenticating-with-saml-single-sign-on)."{% endif %} | | -| `org_credential_authorization.grant` | A member authorized credentials for use with SAML single sign-on. | -| {% ifversion ghec or ghae %}For more information, see "[Authenticating with SAML single sign-on](/authentication/authenticating-with-saml-single-sign-on)."{% endif %} | | -| `org_credential_authorization.revoke` | An owner revoked authorized credentials. {% ifversion ghec %}For more information, see "[Viewing and managing your active SAML sessions](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization)."{% endif %} +| Acción | Descripción | +| --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `org_credential_authorization.deauthorized` | A member deauthorized credentials for use with SAML single sign-on. | +| {% ifversion ghec or ghae %}For more information, see "[Authenticating with SAML single sign-on](/authentication/authenticating-with-saml-single-sign-on)."{% endif %} | | +| `org_credential_authorization.grant` | A member authorized credentials for use with SAML single sign-on. | +| {% ifversion ghec or ghae %}Para obtener más información, consulta la sección "[Autenticarse con el inicio de sesión único de SAML](/authentication/authenticating-with-saml-single-sign-on)".{% endif %} | | +| `org_credential_authorization.revoke` | An owner revoked authorized credentials. {% ifversion ghec %}For more information, see "[Viewing and managing your active SAML sessions](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization)."{% endif %} {%- endif %} {%- if secret-scanning-audit-log-custom-patterns %} -### `org_secret_scanning_custom_pattern` category actions +### Acciones de la categoría `org_secret_scanning_custom_pattern` -| Acción | Descripción | -| ------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `org_secret_scanning_custom_pattern.create` | A custom pattern is published for secret scanning in an organization. For more information, see "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning#defining-a-custom-pattern-for-an-organization)." | -| `org_secret_scanning_custom_pattern.delete` | A custom pattern is removed from secret scanning in an organization. For more information, see "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning#removing-a-custom-pattern)." | -| `org_secret_scanning_custom_pattern.update` | Changes to a custom pattern are saved for secret scanning in an organization. For more information, see "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning#editing-a-custom-pattern)." | +| Acción | Descripción | +| ------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `org_secret_scanning_custom_pattern.create` | A custom pattern is published for secret scanning in an organization. Para obtener más información, consulta la sección "[Definir los patrones personalizados para el escaneo de secretos](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning#defining-a-custom-pattern-for-an-organization)". | +| `org_secret_scanning_custom_pattern.delete` | A custom pattern is removed from secret scanning in an organization. Para obtener más información, consulta la sección "[Definir los patrones personalizados para el escaneo de secretos](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning#removing-a-custom-pattern)". | +| `org_secret_scanning_custom_pattern.update` | Changes to a custom pattern are saved for secret scanning in an organization. Para obtener más información, consulta la sección "[Definir los patrones personalizados para el escaneo de secretos](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning#editing-a-custom-pattern)". | {%- endif %} ### `organization_default_label` category actions @@ -696,38 +696,38 @@ topics: {%- ifversion fpt or ghec or ghes > 3.1 %} ### `organization_domain` category actions -| Acción | Descripción | -| ----------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `organization_domain.approve` | An enterprise domain was approved for an organization. For more information, see "[Approving a domain for your organization](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization#approving-a-domain-for-your-organization)." | -| `organization_domain.create` | An enterprise domain was added to an organization. For more information, see "[Verifying a domain for your organization](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization#verifying-a-domain-for-your-organization)." | -| `organization_domain.destroy` | An enterprise domain was removed from an organization. For more information, see "[Removing an approved or verified domain](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization#removing-an-approved-or-verified-domain)." | -| `organization_domain.verify` | An enterprise domain was verified for an organization. For more information, see "[Verifying a domain for your organization](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization#verifying-a-domain-for-your-organization)." | +| Acción | Descripción | +| ----------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `organization_domain.approve` | An enterprise domain was approved for an organization. For more information, see "[Approving a domain for your organization](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization#approving-a-domain-for-your-organization)." | +| `organization_domain.create` | An enterprise domain was added to an organization. For more information, see "[Verifying a domain for your organization](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization#verifying-a-domain-for-your-organization)." | +| `organization_domain.destroy` | An enterprise domain was removed from an organization. For more information, see "[Removing an approved or verified domain](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization#removing-an-approved-or-verified-domain)." | +| `organization_domain.verify` | An enterprise domain was verified for an organization. Para obtener más información, consulta la sección "[Verificar un dominio para tu organización](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization#verifying-a-domain-for-your-organization)". | ### `organization_projects_change` category actions | Acción | Descripción | | -------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `organization_projects_change.clear` | An enterprise owner{% ifversion ghes %} or site administrator{% endif %} cleared the policy setting for organization-wide project boards in an enterprise. For more information, see "[Enforcing a policy for organization-wide project boards](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-project-board-policies-in-your-enterprise#enforcing-a-policy-for-organization-wide-project-boards)." | -| `organization_projects_change.disable` | Organization projects were disabled for all organizations in an enterprise. For more information, see "[Enforcing a policy for organization-wide project boards](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-project-board-policies-in-your-enterprise#enforcing-a-policy-for-organization-wide-project-boards)." | -| `organization_projects_change.enable` | Organization projects were enabled for all organizations in an enterprise. For more information, see "[Enforcing a policy for organization-wide project boards](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-project-board-policies-in-your-enterprise#enforcing-a-policy-for-organization-wide-project-boards)." | +| `organization_projects_change.disable` | Organization projects were disabled for all organizations in an enterprise. Para obtener más información, consulta la sección "[Requerir una política para los tableros de proyecto en toda la organización](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-project-board-policies-in-your-enterprise#enforcing-a-policy-for-organization-wide-project-boards)". | +| `organization_projects_change.enable` | Organization projects were enabled for all organizations in an enterprise. Para obtener más información, consulta la sección "[Requerir una política para los tableros de proyecto en toda la organización](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-project-board-policies-in-your-enterprise#enforcing-a-policy-for-organization-wide-project-boards)". | {%- endif %} {%- ifversion fpt or ghec or ghes > 3.0 or ghae %} ### Acciones de la categoría `packages` -| Acción | Descripción | -| ------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `packages.insecure_hash` | Maven published an insecure hash for a specific package version. | +| Acción | Descripción | +| ------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `packages.insecure_hash` | Maven published an insecure hash for a specific package version. | | `packages.package_deleted` | A package was deleted from an organization.{% ifversion fpt or ghec or ghes > 3.1 %} For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)."{% endif %} -| `packages.package_published` | A package was published or republished to an organization. | +| `packages.package_published` | A package was published or republished to an organization. | | `packages.package_restored` | An entire package was restored.{% ifversion fpt or ghec or ghes > 3.1 %} For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)."{% endif %} | `packages.package_version_deleted` | A specific package version was deleted.{% ifversion fpt or ghec or ghes > 3.1 %} For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)."{% endif %} -| `packages.package_version_published` | A specific package version was published or republished to a package. | -| `packages.package_version_restored` | A specific package version was deleted.{% ifversion fpt or ghec or ghes > 3.1 %} For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)."{% endif %} -| `packages.part_upload` | A specific package version was partially uploaded to an organization. | -| `packages.upstream_package_fetched` | A specific package version was fetched from the npm upstream proxy. | -| `packages.version_download` | A specific package version was downloaded. | -| `packages.version_upload` | A specific package version was uploaded. | +| `packages.package_version_published` | A specific package version was published or republished to a package. | +| `packages.package_version_restored` | Se borró una versión específica de un paquete.{% ifversion fpt or ghec or ghes > 3.1 %} Para obtener más información, consulta la sección "[Borrar y restablecer un paquete](/packages/learn-github-packages/deleting-and-restoring-a-package)".{% endif %} +| `packages.part_upload` | A specific package version was partially uploaded to an organization. | +| `packages.upstream_package_fetched` | A specific package version was fetched from the npm upstream proxy. | +| `packages.version_download` | A specific package version was downloaded. | +| `packages.version_upload` | A specific package version was uploaded. | {%- endif %} {%- ifversion fpt or ghec %} @@ -760,12 +760,12 @@ topics: {%- ifversion ghes %} ### `pre_receive_environment` category actions -| Acción | Descripción | -| ---------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `pre_receive_environment.create` | A pre-receive hook environment was created. For more information, see "[Creating a pre-receive hook environment](/admin/policies/enforcing-policy-with-pre-receive-hooks/creating-a-pre-receive-hook-environment)." | -| `pre_receive_environment.destroy` | A pre-receive hook environment was deleted. For more information, see "[Creating a pre-receive hook environment](/admin/policies/enforcing-policy-with-pre-receive-hooks/creating-a-pre-receive-hook-environment)." | -| `pre_receive_environment.download` | A pre-receive hook environment was downloaded. For more information, see "[Creating a pre-receive hook environment](/admin/policies/enforcing-policy-with-pre-receive-hooks/creating-a-pre-receive-hook-environment)." | -| `pre_receive_environment.update` | A pre-receive hook environment was updated. For more information, see "[Creating a pre-receive hook environment](/admin/policies/enforcing-policy-with-pre-receive-hooks/creating-a-pre-receive-hook-environment)." | +| Acción | Descripción | +| ---------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `pre_receive_environment.create` | A pre-receive hook environment was created. For more information, see "[Creating a pre-receive hook environment](/admin/policies/enforcing-policy-with-pre-receive-hooks/creating-a-pre-receive-hook-environment)." | +| `pre_receive_environment.destroy` | A pre-receive hook environment was deleted. Para obtener más información, consulta la sección "[Crear un ambiente de gancho de pre-recepción](/admin/policies/enforcing-policy-with-pre-receive-hooks/creating-a-pre-receive-hook-environment)". | +| `pre_receive_environment.download` | A pre-receive hook environment was downloaded. Para obtener más información, consulta la sección "[Crear un ambiente de gancho de pre-recepción](/admin/policies/enforcing-policy-with-pre-receive-hooks/creating-a-pre-receive-hook-environment)". | +| `pre_receive_environment.update` | A pre-receive hook environment was updated. Para obtener más información, consulta la sección "[Crear un ambiente de gancho de pre-recepción](/admin/policies/enforcing-policy-with-pre-receive-hooks/creating-a-pre-receive-hook-environment)". | ### `pre_receive_hook` category actions @@ -806,7 +806,7 @@ topics: | `project.link` | A repository was linked to a project board. For more information, see "[Linking a repository to a project board](/issues/organizing-your-work-with-project-boards/managing-project-boards/linking-a-repository-to-a-project-board)." | | `project.open` | A project board was reopened. For more information, see "[Reopening a closed project board](/issues/organizing-your-work-with-project-boards/managing-project-boards/reopening-a-closed-project-board)." | | `project.rename` | A project board was renamed. For more information, see "[Editing a project board](/issues/organizing-your-work-with-project-boards/managing-project-boards/editing-a-project-board)." | -| `project.unlink` | A repository was unlinked from a project board. For more information, see "[Linking a repository to a project board](/issues/organizing-your-work-with-project-boards/managing-project-boards/linking-a-repository-to-a-project-board)." | +| `project.unlink` | A repository was unlinked from a project board. Para obtener más información, consulta "[Vincular un repositorio con un tablero de proyecto](/issues/organizing-your-work-with-project-boards/managing-project-boards/linking-a-repository-to-a-project-board)". | | `project.update_org_permission` | The project's base-level permission for all organization members was changed or removed. For more information, see "[Managing access to a project board for organization members](/organizations/managing-access-to-your-organizations-project-boards/managing-access-to-a-project-board-for-organization-members)." | | `project.update_team_permission` | A team's project board permission level was changed or when a team was added or removed from a project board. For more information, see "[Managing team access to an organization project board](/organizations/managing-access-to-your-organizations-project-boards/managing-team-access-to-an-organization-project-board)." | | `project.update_user_permission` | An organization member or outside collaborator was added to or removed from a project board or had their permission level changed. For more information, see "[Managing an individual’s access to an organization project board](/organizations/managing-access-to-your-organizations-project-boards/managing-an-individuals-access-to-an-organization-project-board)." | @@ -814,10 +814,10 @@ topics: {%- ifversion fpt or ghec %} ### `project_field` category actions -| Acción | Descripción | -| ---------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `project_field.create` | A field was created in a project board. For more information, see "[Creating a project (beta)](/issues/trying-out-the-new-projects-experience/creating-a-project#adding-fields)." | -| `project_field.delete` | A field was deleted in a project board. For more information, see "[Creating a project (beta)](/issues/trying-out-the-new-projects-experience/creating-a-project#adding-fields)." | +| Acción | Descripción | +| ---------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `project_field.create` | A field was created in a project board. For more information, see "[Creating a project (beta)](/issues/trying-out-the-new-projects-experience/creating-a-project#adding-fields)." | +| `project_field.delete` | A field was deleted in a project board. Para obtener más información, consulta la sección "[Crear un proyecto (beta)](/issues/trying-out-the-new-projects-experience/creating-a-project#adding-fields)". | ### `project_view` category actions @@ -876,11 +876,11 @@ topics: ### Acciones de la categoría `pull_request_review` -| Acción | Descripción | -| ----------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| `pull_request_review.delete` | Se borró una revisión en una solicitud de cambios. | -| `pull_request_review.dismiss` | A review on a pull request was dismissed. Para obtener más información, consulta "[Descartar una revisión de solicitud de extracción](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/dismissing-a-pull-request-review)". | -| `pull_request_review.submit` | A review on a pull request was submitted. For more information, see "[Submitting your review](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request#submitting-your-review)." | +| Acción | Descripción | +| ----------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `pull_request_review.delete` | Se borró una revisión en una solicitud de cambios. | +| `pull_request_review.dismiss` | Se descartó una revisión de una solicitud de cambios. Para obtener más información, consulta "[Descartar una revisión de solicitud de extracción](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/dismissing-a-pull-request-review)". | +| `pull_request_review.submit` | A review on a pull request was submitted. For more information, see "[Submitting your review](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request#submitting-your-review)." | ### Acciones de la categoría `pull_request_review_comment` @@ -991,20 +991,20 @@ topics: {%- if secret-scanning-audit-log-custom-patterns %} -### `repository_secret_scanning_custom_pattern` category actions +### Acciones de la categoría `repository_secret_scanning_custom_pattern` -| Acción | Descripción | -| -------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `repository_secret_scanning_custom_pattern.create` | A custom pattern is published for secret scanning in a repository. For more information, see "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning#defining-a-custom-pattern-for-a-repository)." | -| `repository_secret_scanning_custom_pattern.delete` | A custom pattern is removed from secret scanning in a repository. For more information, see "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning#removing-a-custom-pattern)." | -| `repository_secret_scanning_custom_pattern.update` | Changes to a custom pattern are saved for secret scanning in a repository. For more information, see "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning#editing-a-custom-pattern)." | +| Acción | Descripción | +| -------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `repository_secret_scanning_custom_pattern.create` | A custom pattern is published for secret scanning in a repository. Para obtener más información, consulta la sección "[Definir los patrones personalizados para el escaneo de secretos](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning#defining-a-custom-pattern-for-a-repository)". | +| `repository_secret_scanning_custom_pattern.delete` | A custom pattern is removed from secret scanning in a repository. Para obtener más información, consulta la sección "[Definir los patrones personalizados para el escaneo de secretos](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning#removing-a-custom-pattern)". | +| `repository_secret_scanning_custom_pattern.update` | Changes to a custom pattern are saved for secret scanning in a repository. Para obtener más información, consulta la sección "[Definir los patrones personalizados para el escaneo de secretos](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning#editing-a-custom-pattern)". | -### `repository_secret_scanning_push_protection` category actions +### Acciones de la categoría `repository_secret_scanning_push_protection` -| Acción | Descripción | -| ---------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `repository_secret_scanning_push_protection.disable` | A repository owner or administrator disabled secret scanning for a repository. For more information, see "[Protecting pushes with secret scanning](/code-security/secret-scanning/protecting-pushes-with-secret-scanning)." | -| `repository_secret_scanning_push_protection.enable` | A repository owner or administrator enabled secret scanning for a repository. For more information, see "[Protecting pushes with secret scanning](/code-security/secret-scanning/protecting-pushes-with-secret-scanning)." | +| Acción | Descripción | +| ---------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `repository_secret_scanning_push_protection.disable` | A repository owner or administrator disabled secret scanning for a repository. Para obtener más información, consulta la sección "[Proteger las subidas de información con el escaneo de secretos](/code-security/secret-scanning/protecting-pushes-with-secret-scanning)". | +| `repository_secret_scanning_push_protection.enable` | A repository owner or administrator enabled secret scanning for a repository. Para obtener más información, consulta la sección "[Proteger las subidas de información con el escaneo de secretos](/code-security/secret-scanning/protecting-pushes-with-secret-scanning)". | {%- endif %} ### `repository_visibility_change` category actions @@ -1036,10 +1036,10 @@ topics: ### `required_status_check` category actions -| Acción | Descripción | -| ------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `required_status_check.create` | A status check was marked as required for a protected branch. For more information, see "[Require status checks before merging](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches#require-status-checks-before-merging)." | -| `required_status_check.destroy` | A status check was no longer marked as required for a protected branch. For more information, see "[Require status checks before merging](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches#require-status-checks-before-merging)." | +| Acción | Descripción | +| ------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `required_status_check.create` | A status check was marked as required for a protected branch. For more information, see "[Require status checks before merging](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches#require-status-checks-before-merging)." | +| `required_status_check.destroy` | A status check was no longer marked as required for a protected branch. Para obtener más información, consulta la sección "[Requerir verificaciones de estado antes de la fusión](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches#require-status-checks-before-merging)". | {%- ifversion ghec or ghes > 3.1 %} ### `restrict_notification_delivery` category actions @@ -1088,27 +1088,27 @@ topics: {%- ifversion fpt or ghec %} ### acciones de la categoría `sponsors` -| Acción | Descripción | -| ------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `sponsors.agreement_sign` | A {% data variables.product.prodname_sponsors %} agreement was signed on behalf of an organization. | -| `sponsors.custom_amount_settings_change` | Custom amounts for {% data variables.product.prodname_sponsors %} were enabled or disabled, or the suggested custom amount was changed. For more information, see "[Managing your sponsorship tiers](/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers)." | -| `sponsors.fiscal_host_change` | The fiscal host for a {% data variables.product.prodname_sponsors %} listing was updated. | -| `sponsors.withdraw_agreement_signature` | A signature was withdrawn from a {% data variables.product.prodname_sponsors %} agreement that applies to an organization. | -| `sponsors.repo_funding_links_file_action` | The FUNDING file in a repository was changed. Para obtener más información, consulta "[Mostrar un botón de patrocinador en tu repositorio](/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/displaying-a-sponsor-button-in-your-repository)". | -| `sponsors.sponsor_sponsorship_cancel` | A sponsorship was canceled. For more information, see "[Downgrading a sponsorship](/billing/managing-billing-for-github-sponsors/downgrading-a-sponsorship)." | -| `sponsors.sponsor_sponsorship_create` | A sponsorship was created, by sponsoring an account. For more information, see "[Sponsoring an open source contributor](/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor)." | -| `sponsors.sponsor_sponsorship_payment_complete` | After you sponsor an account and a payment has been processed, the sponsorship payment was marked as complete. For more information, see "[Sponsoring an open source contributor](/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor)." | -| `sponsors.sponsor_sponsorship_preference_change` | The option to receive email updates from a sponsored account was changed. Para obtener más información, consulta "[Administar tu patrocinio](/sponsors/sponsoring-open-source-contributors/managing-your-sponsorship)". | -| `sponsors.sponsor_sponsorship_tier_change` | A sponsorship was upgraded or downgraded. Para obtener más información, consulta "[Actualizar un patrocinio](/billing/managing-billing-for-github-sponsors/upgrading-a-sponsorship)" y "[Bajar de categoría un patrocinio](/billing/managing-billing-for-github-sponsors/downgrading-a-sponsorship)." | -| `sponsors.sponsored_developer_approve` | A {% data variables.product.prodname_sponsors %} account was approved. For more information, see "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)." | -| `sponsors.sponsored_developer_create` | A {% data variables.product.prodname_sponsors %} account was created. For more information, see "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)." | -| `sponsors.sponsored_developer_disable` | A {% data variables.product.prodname_sponsors %} account was disabled. | -| `sponsors.sponsored_developer_profile_update` | You edit a sponsored organization profile. For more information, see "[Editing your profile details for {% data variables.product.prodname_sponsors %}](/sponsors/receiving-sponsorships-through-github-sponsors/editing-your-profile-details-for-github-sponsors)." | -| `sponsors.sponsored_developer_redraft` | A {% data variables.product.prodname_sponsors %} account was returned to draft state from approved state. | -| `sponsors.sponsored_developer_request_approval` | An application for {% data variables.product.prodname_sponsors %} was submitted for approval. For more information, see "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)." | -| `sponsors.sponsored_developer_tier_description_update` | The description for a sponsorship tier was changed. For more information, see "[Managing your sponsorship tiers](/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers)." | -| `sponsors.update_tier_welcome_message` | The welcome message for a {% data variables.product.prodname_sponsors %} tier for an organization was updated. | -| `sponsors.update_tier_repository` | A {% data variables.product.prodname_sponsors %} tier changed access for a repository. | +| Acción | Descripción | +| ------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `sponsors.agreement_sign` | A {% data variables.product.prodname_sponsors %} agreement was signed on behalf of an organization. | +| `sponsors.custom_amount_settings_change` | Custom amounts for {% data variables.product.prodname_sponsors %} were enabled or disabled, or the suggested custom amount was changed. For more information, see "[Managing your sponsorship tiers](/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers)." | +| `sponsors.fiscal_host_change` | The fiscal host for a {% data variables.product.prodname_sponsors %} listing was updated. | +| `sponsors.withdraw_agreement_signature` | A signature was withdrawn from a {% data variables.product.prodname_sponsors %} agreement that applies to an organization. | +| `sponsors.repo_funding_links_file_action` | The FUNDING file in a repository was changed. Para obtener más información, consulta "[Mostrar un botón de patrocinador en tu repositorio](/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/displaying-a-sponsor-button-in-your-repository)". | +| `sponsors.sponsor_sponsorship_cancel` | A sponsorship was canceled. For more information, see "[Downgrading a sponsorship](/billing/managing-billing-for-github-sponsors/downgrading-a-sponsorship)." | +| `sponsors.sponsor_sponsorship_create` | A sponsorship was created, by sponsoring an account. For more information, see "[Sponsoring an open source contributor](/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor)." | +| `sponsors.sponsor_sponsorship_payment_complete` | After you sponsor an account and a payment has been processed, the sponsorship payment was marked as complete. Para obtener más información, consulta la sección "[Patrocinar a un contribuyente de código libre](/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor)". | +| `sponsors.sponsor_sponsorship_preference_change` | The option to receive email updates from a sponsored account was changed. Para obtener más información, consulta "[Administar tu patrocinio](/sponsors/sponsoring-open-source-contributors/managing-your-sponsorship)". | +| `sponsors.sponsor_sponsorship_tier_change` | A sponsorship was upgraded or downgraded. Para obtener más información, consulta "[Actualizar un patrocinio](/billing/managing-billing-for-github-sponsors/upgrading-a-sponsorship)" y "[Bajar de categoría un patrocinio](/billing/managing-billing-for-github-sponsors/downgrading-a-sponsorship)." | +| `sponsors.sponsored_developer_approve` | A {% data variables.product.prodname_sponsors %} account was approved. For more information, see "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)." | +| `sponsors.sponsored_developer_create` | A {% data variables.product.prodname_sponsors %} account was created. Para obtener más información, consulta la sección "[Configurar {% data variables.product.prodname_sponsors %} para tu organización](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)". | +| `sponsors.sponsored_developer_disable` | A {% data variables.product.prodname_sponsors %} account was disabled. | +| `sponsors.sponsored_developer_profile_update` | You edit a sponsored organization profile. For more information, see "[Editing your profile details for {% data variables.product.prodname_sponsors %}](/sponsors/receiving-sponsorships-through-github-sponsors/editing-your-profile-details-for-github-sponsors)." | +| `sponsors.sponsored_developer_redraft` | A {% data variables.product.prodname_sponsors %} account was returned to draft state from approved state. | +| `sponsors.sponsored_developer_request_approval` | An application for {% data variables.product.prodname_sponsors %} was submitted for approval. Para obtener más información, consulta la sección "[Configurar {% data variables.product.prodname_sponsors %} para tu organización](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)". | +| `sponsors.sponsored_developer_tier_description_update` | The description for a sponsorship tier was changed. Para obtener más información, consulta la sección "[Administrar tus niveles de patrocinio](/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers)". | +| `sponsors.update_tier_welcome_message` | The welcome message for a {% data variables.product.prodname_sponsors %} tier for an organization was updated. | +| `sponsors.update_tier_repository` | A {% data variables.product.prodname_sponsors %} tier changed access for a repository. | {%- endif %} {%- ifversion ghec or ghes or ghae %} @@ -1151,15 +1151,15 @@ topics: ### acciones de la categoría `team` -| Acción | Descripción | -| ------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `team.add_member` | A member of an organization was added to a team. For more information, see "[Adding organization members to a team](/organizations/organizing-members-into-teams/adding-organization-members-to-a-team)." | -| `team.add_repository` | A team was given access and permissions to a repository. | -| `team.change_parent_team` | A child team was created or a child team's parent was changed. For more information, see "[Moving a team in your organization’s hierarchy](/organizations/organizing-members-into-teams/moving-a-team-in-your-organizations-hierarchy)." | -| `team.change_privacy` | A team's privacy level was changed. For more information, see "[Changing team visibility](/organizations/organizing-members-into-teams/changing-team-visibility)." | -| `team.create` | Se agregó una cuenta de usuario o repositorio a un equipo. | -| `team.delete` | Se eliminó una cuenta de usuario o repositorio de un equipo. | -| `team.destroy` | Se eliminó un equipo. | +| Acción | Descripción | +| ------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `team.add_member` | A member of an organization was added to a team. Para obtener más información, consulta la sección "[Agregar miembros organizacionales a un equipo](/organizations/organizing-members-into-teams/adding-organization-members-to-a-team)". | +| `team.add_repository` | A team was given access and permissions to a repository. | +| `team.change_parent_team` | A child team was created or a child team's parent was changed. For more information, see "[Moving a team in your organization’s hierarchy](/organizations/organizing-members-into-teams/moving-a-team-in-your-organizations-hierarchy)." | +| `team.change_privacy` | A team's privacy level was changed. For more information, see "[Changing team visibility](/organizations/organizing-members-into-teams/changing-team-visibility)." | +| `team.create` | Se agregó una cuenta de usuario o repositorio a un equipo. | +| `team.delete` | Se eliminó una cuenta de usuario o repositorio de un equipo. | +| `team.destroy` | Se eliminó un equipo. | {%- ifversion ghec or ghes or ghae %} | `team.demote_maintainer` | A user was demoted from a team maintainer to a team member. | `team.promote_maintainer` | A user was promoted from a team member to a team maintainer. For more information, see "[Promoting an organization member to team maintainer](/organizations/organizing-members-into-teams/assigning-the-team-maintainer-role-to-a-team-member#promoting-an-organization-member-to-team-maintainer)." {%- endif %} @@ -1220,7 +1220,7 @@ topics: {%- ifversion ghes %} | `user.promote` | An ordinary user account was promoted to a site administrator. {%- endif %} -| `user.recreate` | A user's account was restored. | `user.remove_email` | An email address was removed from a user account. | `user.remove_large_scale_contributor_flag` | A user account was no longer flagged as a large scale contributor. | `user.rename` | A username was changed. | `user.reset_password` | A user reset their account password. | `user.show_private_contributions_count` | A user changed the visibility of their private contributions. The number of contributions to private repositories on the user's profile are now shown. For more information, see "[Publicizing or hiding your private contributions on your profile](/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/publicizing-or-hiding-your-private-contributions-on-your-profile)." | `user.sign_in_from_unrecognized_device` | A user signed in from an unrecognized device. | `user.sign_in_from_unrecognized_device_and_location` | A user signed in from an unrecognized device and location. | `user.sign_in_from_unrecognized_location` | A user signed in from an unrecognized location. | `user.suspend` | A user account was suspended by an enterprise owner {% ifversion ghes %} or site administrator{% endif %}. | `user.two_factor_challenge_failure` | A 2FA challenge issued for a user account failed. | `user.two_factor_challenge_success` | A 2FA challenge issued for a user account succeeded. | `user.two_factor_recover` | A user used their 2FA recovery codes. | `user.two_factor_recovery_codes_downloaded` | A user downloaded 2FA recovery codes for their account. | `user.two_factor_recovery_codes_printed` | A user printed 2FA recovery codes for their account. | `user.two_factor_recovery_codes_viewed` | A user viewed 2FA recovery codes for their account. | `user.two_factor_requested` | A user was prompted for a two-factor authentication code. | `user.unblock_user` | A user was unblocked another user{% ifversion ghes %} or a site administrator{% endif %}. | `user.unminimize_comment` | A comment made by a user was unminimized. | `user.unsuspend` | A user account was unsuspended by an enterprise owner {% ifversion ghes %} or site administrator{% endif %}. +| `user.recreate` | A user's account was restored. | `user.remove_email` | An email address was removed from a user account. | `user.remove_large_scale_contributor_flag` | A user account was no longer flagged as a large scale contributor. | `user.rename` | A username was changed. | `user.reset_password` | A user reset their account password. | `user.show_private_contributions_count` | A user changed the visibility of their private contributions. The number of contributions to private repositories on the user's profile are now shown. Para obtener más información, consulta la sección "[Publicar u ocultar tus contribuciones privadas en tu perfil](/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/publicizing-or-hiding-your-private-contributions-on-your-profile)". | `user.sign_in_from_unrecognized_device` | A user signed in from an unrecognized device. | `user.sign_in_from_unrecognized_device_and_location` | A user signed in from an unrecognized device and location. | `user.sign_in_from_unrecognized_location` | A user signed in from an unrecognized location. | `user.suspend` | A user account was suspended by an enterprise owner {% ifversion ghes %} or site administrator{% endif %}. | `user.two_factor_challenge_failure` | A 2FA challenge issued for a user account failed. | `user.two_factor_challenge_success` | A 2FA challenge issued for a user account succeeded. | `user.two_factor_recover` | A user used their 2FA recovery codes. | `user.two_factor_recovery_codes_downloaded` | A user downloaded 2FA recovery codes for their account. | `user.two_factor_recovery_codes_printed` | A user printed 2FA recovery codes for their account. | `user.two_factor_recovery_codes_viewed` | A user viewed 2FA recovery codes for their account. | `user.two_factor_requested` | A user was prompted for a two-factor authentication code. | `user.unblock_user` | A user was unblocked another user{% ifversion ghes %} or a site administrator{% endif %}. | `user.unminimize_comment` | A comment made by a user was unminimized. | `user.unsuspend` | A user account was unsuspended by an enterprise owner {% ifversion ghes %} or site administrator{% endif %}. {%- endif %} {%- ifversion ghec or ghes %} diff --git a/translations/es-ES/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/searching-the-audit-log-for-your-enterprise.md b/translations/es-ES/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/searching-the-audit-log-for-your-enterprise.md index 0f8ea1a2b2..851e773cf2 100644 --- a/translations/es-ES/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/searching-the-audit-log-for-your-enterprise.md +++ b/translations/es-ES/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/searching-the-audit-log-for-your-enterprise.md @@ -29,7 +29,7 @@ You can search your enterprise audit log directly from the user interface by usi For more information about viewing your enterprise audit log, see "[Accessing the audit log for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/accessing-the-audit-log-for-your-enterprise)." -You can also use the API to retrieve audit log events. For more information, see "[Using the audit log API for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/using-the-audit-log-api-for-your-enterprise)." +You can also use the API to retrieve audit log events. Para obtener más información, consulta la sección "[Utilizar la API de bitácora de auditoría para tu empresa](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/using-the-audit-log-api-for-your-enterprise)". Nota que no puedes buscar entradas utilizando texto. Sin embargo, puedes construir consultas de búsqueda utilizando una variedad de filtros. Muchos operadores que se utilizan cuando se busca el registro por queries, tales como `-`, `>`, o `<`, empatan con el mismo formato que si se busca con {% data variables.product.product_name %}. Para obtener más información, consulta la sección "[Buscar en {% data variables.product.prodname_dotcom %}](/search-github/getting-started-with-searching-on-github/about-searching-on-github)". diff --git a/translations/es-ES/content/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on.md b/translations/es-ES/content/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on.md index ad2e7d4013..e56e1a8b4d 100644 --- a/translations/es-ES/content/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on.md +++ b/translations/es-ES/content/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on.md @@ -50,7 +50,7 @@ Para utilizar un token de acceso personal existente o nuevo o una llave SSH con You must have an active SAML session each time you authorize an {% data variables.product.prodname_oauth_app %} or {% data variables.product.prodname_github_app %} to access an organization that uses or enforces SAML SSO. You can create an active SAML session by navigating to `https://github.com/orgs/ORGANIZATION-NAME/sso` in your browser. -After an enterprise or organization owner enables or enforces SAML SSO for an organization, and after you authenticate via SAML for the first time, you must reauthorize any {% data variables.product.prodname_oauth_apps %} or {% data variables.product.prodname_github_apps %} that you previously authorized to access the organization. +Después de que un propietario de empresa u organización habilita o requiere el SSO de SAML para una organización y después de que te autentiques a través del SAML por primera vez, debes volver a autorizar cualquier {% data variables.product.prodname_oauth_apps %} o {% data variables.product.prodname_github_apps %} que hayas autorizado anteriormente para que acceda a dicha organización. To see the {% data variables.product.prodname_oauth_apps %} you've authorized, visit your [{% data variables.product.prodname_oauth_apps %} page](https://github.com/settings/applications). To see the {% data variables.product.prodname_github_apps %} you've authorized, visit your [{% data variables.product.prodname_github_apps %} page](https://github.com/settings/apps/authorizations). diff --git a/translations/es-ES/content/authentication/connecting-to-github-with-ssh/about-ssh.md b/translations/es-ES/content/authentication/connecting-to-github-with-ssh/about-ssh.md index 47dc88ef2a..4b1fcf0011 100644 --- a/translations/es-ES/content/authentication/connecting-to-github-with-ssh/about-ssh.md +++ b/translations/es-ES/content/authentication/connecting-to-github-with-ssh/about-ssh.md @@ -29,7 +29,7 @@ Si no has usado tu clave SSH por un año, entonces {% data variables.product.pro {% ifversion fpt %} Las organizaciones que utilizan {% data variables.product.prodname_ghe_cloud %} pueden proporcionar certificados SSH, los cuales pueden utilizar los miembros para acceder a los repositorios de dicha organización sin agregar el certificado a su cuenta de {% data variables.product.product_name %}. Si estás utilizando un certificado SSH, no puedes utilizarlo para acceder a las bifurcaciones de los repositorios de la organización si estas le pertenecen a tu cuenta personal. Para obtener más información, consulta la sección "[Acerca de las autoridades de certificados SSH](/enterprise-cloud@latest/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities)" en la documentación de {% data variables.product.prodname_ghe_cloud %}. {% else ghec or ghes or ghae %} -Si eres miembro de una organización que provee certificados SSH, puedes usar tu certificado para acceder a los repositorios de esa organización sin agregar el certificado a tu cuenta de {% data variables.product.product_name %}. No puedes utilizar tu certificado para acceder a las bifurcaciones de los repositorios de la organización si estas bifurcaciones le pertenecen a tu cuenta personal. For more information, see "[About SSH certificate authorities](/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities)." +Si eres miembro de una organización que provee certificados SSH, puedes usar tu certificado para acceder a los repositorios de esa organización sin agregar el certificado a tu cuenta de {% data variables.product.product_name %}. No puedes utilizar tu certificado para acceder a las bifurcaciones de los repositorios de la organización si estas bifurcaciones le pertenecen a tu cuenta personal. Para obtener más información, consulta la sección [Acerca de las autoridades de certificados SSH](/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities)". {% endif %} ## Leer más diff --git a/translations/es-ES/content/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/setting-up-visual-studio-subscriptions-with-github-enterprise.md b/translations/es-ES/content/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/setting-up-visual-studio-subscriptions-with-github-enterprise.md index 0303b213ec..0f327fa0ca 100644 --- a/translations/es-ES/content/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/setting-up-visual-studio-subscriptions-with-github-enterprise.md +++ b/translations/es-ES/content/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/setting-up-visual-studio-subscriptions-with-github-enterprise.md @@ -50,14 +50,14 @@ Una persona podría completar las tareas porque tiene todos los roles, pero podr 1. Si el administrador de suscripciones no inhabilitó las notificaciones por correo electrónico, el suscriptor recibirá dos correos electrónicos de confirmación. Para obtener más información, consulta la sección [Suscripciones de {% data variables.product.prodname_vs %} con {% data variables.product.prodname_enterprise %}](https://docs.microsoft.com/en-us/visualstudio/subscriptions/access-github#what-is-the-visual-studio-subscription-with-github-enterprise-setup-process) en los documentos de Microsoft. -1. Un propietario de organización debe invitar al suscriptor a la organización en {% data variables.product.product_location %} desde el paso 1. The subscriber can accept the invitation with an existing personal account on {% data variables.product.prodname_dotcom_the_website %} or create a new account. Después de que el suscriptor se una a la organización, este se convierte en miembro de la empresa. Para obtener más información, consulta la sección "[Invitar usuarios para que se unan a tu organización](/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization)". +1. Un propietario de organización debe invitar al suscriptor a la organización en {% data variables.product.product_location %} desde el paso 1. El suscriptor puede aceptar la invitación con una cuenta personal existente de {% data variables.product.prodname_dotcom_the_website %} o crear una cuenta nueva. Después de que el suscriptor se una a la organización, este se convierte en miembro de la empresa. Para obtener más información, consulta la sección "[Invitar usuarios para que se unan a tu organización](/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization)". {% tip %} **Tips**: - Si bien no se requiere, recomendamos que el propietario de la organización envíe una invitación a la misma dirección de correo electrónico que se utiliza para el Nombre Primario de Usuario (UPN) del suscriptor. Cuando la dirección de correo electrónico de {% data variables.product.product_location %} coincide con el UPN del suscriptor, puedes asegurar que otra empresa no reclame la licencia del suscriptor. - - If the subscriber accepts the invitation to the organization with an existing personal account on {% data variables.product.product_location %}, we recommend that the subscriber add the email address they use for {% data variables.product.prodname_vs %} to their personal account on {% data variables.product.product_location %}. Para obtener más información, consula la sección "[Agregar una dirección de correo electrónico a tu cuenta de {% data variables.product.prodname_dotcom %}](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/adding-an-email-address-to-your-github-account)". + - Si el suscriptor acepta la invitación a la organización con una cuenta personal existente en {% data variables.product.product_location %}, recomendamos que este agregue la dirección de correo electrónico que utiliza para {% data variables.product.prodname_vs %} a su cuenta personal de {% data variables.product.product_location %}. Para obtener más información, consula la sección "[Agregar una dirección de correo electrónico a tu cuenta de {% data variables.product.prodname_dotcom %}](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/adding-an-email-address-to-your-github-account)". - Si el propietario de la organización debe invitar a una gran cantidad de suscriptores, puedes llevar el proceso más rápidamente con un script. Para obtener más información, consulta el [script de ejemplo de PowerShell](https://github.com/github/platform-samples/blob/master/api/powershell/invite_members_to_org.ps1) en el repositorio `github/platform-samples`. {% endtip %} diff --git a/translations/es-ES/content/code-security/dependabot/dependabot-alerts/configuring-dependabot-alerts.md b/translations/es-ES/content/code-security/dependabot/dependabot-alerts/configuring-dependabot-alerts.md index 811f238b11..336fdb6182 100644 --- a/translations/es-ES/content/code-security/dependabot/dependabot-alerts/configuring-dependabot-alerts.md +++ b/translations/es-ES/content/code-security/dependabot/dependabot-alerts/configuring-dependabot-alerts.md @@ -71,7 +71,7 @@ Predeterminadamente, notificamos a las personas con permisos administrativos en 1. Under "Code security and analysis", to the right of {% data variables.product.prodname_dependabot_alerts %}, click **Disable** or **Enable**. ![Screenshot of "Configure security and analysis" features with the "Disable" button emphasized for Dependabot alerts](/assets/images/help/dependabot/dependabot-alerts-disable-or-enable-fpt-private.png) {% endif %}{% ifversion ghes or ghae %} -{% data variables.product.prodname_dependabot_alerts %} for your repository can be enabled or disabled by your enterprise owner. For more information, see "[Enabling Dependabot for your enterprise](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)." +{% data variables.product.prodname_dependabot_alerts %} for your repository can be enabled or disabled by your enterprise owner. Para obtener más información, consulta la sección "[Habilitar al Dependabot para tu empresa](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)". {% endif %} ## Administrar las {% data variables.product.prodname_dependabot_alerts %} para tu organización @@ -82,7 +82,7 @@ Predeterminadamente, notificamos a las personas con permisos administrativos en {% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} {% data reusables.organizations.security-and-analysis %} -2. Under "Code security and analysis", to the right of {% data variables.product.prodname_dependabot_alerts %}, click **Disable all** or **Enable all**. +2. Debajo de "Análisis y seguridad del código", a la derecha de las {% data variables.product.prodname_dependabot_alerts %}, haz clic en **Inhabilitar todas** o **Habilitar todas**. {% ifversion fpt or ghec %} ![Screenshot of "Configure security and analysis" features with the "Enable all" or "Disable all" button emphasized for Dependabot alerts](/assets/images/help/dependabot/dependabot-alerts-disable-or-enable-fpt.png) {% endif %} diff --git a/translations/es-ES/content/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts.md b/translations/es-ES/content/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts.md index ed3a36397f..c5f632c3e2 100644 --- a/translations/es-ES/content/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts.md +++ b/translations/es-ES/content/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts.md @@ -123,7 +123,7 @@ For supported languages, {% data variables.product.prodname_dependabot %} detect If you schedule extensive work to upgrade a dependency, or decide that an alert does not need to be fixed, you can dismiss the alert. Dismissing alerts that you have already assessed makes it easier to triage new alerts as they appear. -1. View the details for an alert. For more information, see "[Viewing vulnerable dependencies](#viewing-vulnerable-dependencies)" (above). +1. Ver los detalles de una alerta. Para obtener más información, consulta la sección "[Ver las dependencias vulnerables](#viewing-vulnerable-dependencies)" (anteriormente). 1. Select the "Dismiss" dropdown, and click a reason for dismissing the alert.{% if reopen-dependabot-alerts %} Unfixed dismissed alerts can be reopened later.{% endif %} ![Elegir una razón para descartar la alerta a través del menú desplegable de "Descartar"](/assets/images/help/repository/dependabot-alert-dismiss-drop-down-ungrouped.png) {% if reopen-dependabot-alerts %} diff --git a/translations/es-ES/content/code-security/security-overview/filtering-alerts-in-the-security-overview.md b/translations/es-ES/content/code-security/security-overview/filtering-alerts-in-the-security-overview.md index 96796f3a9b..138eb640d7 100644 --- a/translations/es-ES/content/code-security/security-overview/filtering-alerts-in-the-security-overview.md +++ b/translations/es-ES/content/code-security/security-overview/filtering-alerts-in-the-security-overview.md @@ -134,10 +134,10 @@ Available in the {% data variables.product.prodname_dependabot %} alert views. Y Disponible en las vistas de alerta del escaneo de secretos. -| Qualifier | Descripción | -| ------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `secret-type:SERVICE_PROVIDER` | Muestra alertas para el secreto y proveedor especificados. Para obtener más información, consulta la sección "[patrones de {% data variables.product.prodname_secret_scanning_caps %}](/code-security/secret-scanning/secret-scanning-patterns)". | -| `secret-type:CUSTOM-PATTERN` | Muestra alertas para los secretos que coinciden con el patrón personalizado específico. For more information, see "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)." | +| Qualifier | Descripción | +| ------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `secret-type:SERVICE_PROVIDER` | Muestra alertas para el secreto y proveedor especificados. Para obtener más información, consulta la sección "[patrones de {% data variables.product.prodname_secret_scanning_caps %}](/code-security/secret-scanning/secret-scanning-patterns)". | +| `secret-type:CUSTOM-PATTERN` | Muestra alertas para los secretos que coinciden con el patrón personalizado específico. Para obtener más información, consulta la sección "[Definir los patrones personalizados para el escaneo de secretos](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)". | ## Filtrar por proveedor diff --git a/translations/es-ES/content/code-security/supply-chain-security/end-to-end-supply-chain/securing-accounts.md b/translations/es-ES/content/code-security/supply-chain-security/end-to-end-supply-chain/securing-accounts.md index 55a499e3c7..5b0f8f547b 100644 --- a/translations/es-ES/content/code-security/supply-chain-security/end-to-end-supply-chain/securing-accounts.md +++ b/translations/es-ES/content/code-security/supply-chain-security/end-to-end-supply-chain/securing-accounts.md @@ -18,11 +18,11 @@ topics: ## Acerca de esta guía -This guide describes the highest impact changes you can make to increase account security. Each section outlines a change you can make to your processes to improve the security. The highest impact changes are listed first. +This guide describes the highest impact changes you can make to increase account security. Each section outlines a change you can make to your processes to improve the security. Los cambios de más alto impacto se listan primero. -## What's the risk? +## ¿Cuál es el riesgo? -Account security is fundamental to the security of your supply chain. If an attacker can take over your account on {% data variables.product.product_name %}, they can then make malicious changes to your code or build process. So your first goal should be to make it difficult for someone to take over your account and the accounts of other {% ifversion ghes %}users{% else %}members{% endif %} of {% ifversion fpt %}your organization{% elsif ghec or ghae %}your organization or enterprise{% elsif ghes %}{% data variables.product.product_location %}{% endif %}. +Account security is fundamental to the security of your supply chain. If an attacker can take over your account on {% data variables.product.product_name %}, they can then make malicious changes to your code or build process. Así que tu primera meta debería ser que fuera difícil que alguien se apoderara de tu cuenta y de las cuentas de otros {% ifversion ghes %}usuarios{% else %}miembros{% endif %} de {% ifversion fpt %}tu organización{% elsif ghec or ghae %}tu organización o empresa{% elsif ghes %}{% data variables.product.product_location %}{% endif %}. {% ifversion ghec or ghes %} ## Centralize authentication @@ -31,7 +31,7 @@ Account security is fundamental to the security of your supply chain. If an atta {% ifversion ghec %} If you're an enterprise or organization owner, you can configure centralized authentication with SAML. While you can add or remove members manually, it's simpler and more secure to set up single sign-on (SSO) and SCIM between {% data variables.product.product_name %} and your SAML identity provider (IdP). This also simplifies the authentication process for all members of your enterprise. -You can configure SAML authentication for an enterprise or organization account. With SAML, you can grant access to the personal accounts of members of your enterprise or organization on {% data variables.product.product_location %} through your IdP, or you can create and control the accounts that belong to your enterprise by using {% data variables.product.prodname_emus %}. For more information, see "[About authentication for your enterprise](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise)." +You can configure SAML authentication for an enterprise or organization account. With SAML, you can grant access to the personal accounts of members of your enterprise or organization on {% data variables.product.product_location %} through your IdP, or you can create and control the accounts that belong to your enterprise by using {% data variables.product.prodname_emus %}. Para obtener más información, consulta la sección "[Acerca de la autenticación para tu empresa](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise)". After you configure SAML authentication, when members request access to your resources, they'll be directed to your SSO flow to ensure they are still recognized by your IdP. If they are unrecognized, their request is declined. @@ -89,7 +89,7 @@ Para obtener más información, consulta las secciones {% ifversion ghec %}"[Ace {% ifversion ghec or ghes %} {% note %} -**Note**: Depending on the authentication method that {% ifversion ghec %}an enterprise owner{% elsif ghes %}a site administrator{% endif %} has configured for {% ifversion ghec %}your enterprise on {% endif %}{% data variables.product.product_location %}, you may not be able to enable 2FA for your personal account. +**Nota**: Dependiendo del método de autenticación que haya configurado {% ifversion ghec %}un propietario de empresa{% elsif ghes %}un administrador de sitio{% endif %} para {% ifversion ghec %}tu empresa en {% endif %}{% data variables.product.product_location %}, podrías no poder habilitar la 2FA para tu cuenta personal. {% endnote %} {% endif %} @@ -103,7 +103,7 @@ When you set up 2FA, you should always download the recovery codes and set up mo {% ifversion ghec or ghes %} {% note %} -**Note**: Depending on the authentication method that {% ifversion ghec %}an enterprise owner{% elsif ghes %}a site administrator{% endif %} has configured for {% ifversion ghec %}your enterprise on {% endif %}{% data variables.product.product_location %}, you may not be able to require 2FA for your organization. +**Nota**: Dependiendo del método de autenticación que haya configurado {% ifversion ghec %}un propietario de empresa{% elsif ghes %}un administrador de sitio{% endif %} para {% ifversion ghec %}tu empresa en {% endif %}{% data variables.product.product_location %}, podrías no poder requerir la 2FA para tu organización. {% endnote %} {% endif %} diff --git a/translations/es-ES/content/code-security/supply-chain-security/end-to-end-supply-chain/securing-code.md b/translations/es-ES/content/code-security/supply-chain-security/end-to-end-supply-chain/securing-code.md index 006c2eefc0..00669bbdd6 100644 --- a/translations/es-ES/content/code-security/supply-chain-security/end-to-end-supply-chain/securing-code.md +++ b/translations/es-ES/content/code-security/supply-chain-security/end-to-end-supply-chain/securing-code.md @@ -18,9 +18,9 @@ topics: ## Acerca de esta guía -This guide describes the highest impact changes you can make to improve the security of your code. Cada sección detalla un cambio que puedes hacer a tus procesos para mejorar la seguridad. The highest impact changes are listed first. +This guide describes the highest impact changes you can make to improve the security of your code. Cada sección detalla un cambio que puedes hacer a tus procesos para mejorar la seguridad. Los cambios de más alto impacto se listan primero. -## What's the risk? +## ¿Cuál es el riesgo? Key risks in the development process include: @@ -77,7 +77,7 @@ Code often needs to communicate with other systems over a network, and requires {% elsif ghec %} If your organization uses {% data variables.product.prodname_GH_advanced_security %}, you can enable {% data variables.product.prodname_secret_scanning_GHAS %} on any repository owned by the organization. You can also define custom patterns to detect additional secrets at the repository, organization, or enterprise level. For more information, see "[About {% data variables.product.prodname_secret_scanning_GHAS %}](/code-security/secret-scanning/about-secret-scanning#about-secret-scanning-for-advacned-security)." {% else %} -You can configure {% data variables.product.prodname_secret_scanning %} to check for secrets issued by many service providers and to notify you when any are detected. You can also define custom patterns to detect additional secrets at the repository, organization, or enterprise level. For more information, see "[About secret scanning](/code-security/secret-scanning/about-secret-scanning)" and "[Secret scanning patterns](/code-security/secret-scanning/secret-scanning-patterns)." +You can configure {% data variables.product.prodname_secret_scanning %} to check for secrets issued by many service providers and to notify you when any are detected. También puedes definir patrones personalizados para detectar secretos adicionales a nivel de repositorio, organización o empresa. For more information, see "[About secret scanning](/code-security/secret-scanning/about-secret-scanning)" and "[Secret scanning patterns](/code-security/secret-scanning/secret-scanning-patterns)." {% endif %} {% ifversion fpt or ghec or ghes > 3.2 %} @@ -89,7 +89,7 @@ Besides your code, you probably need to use secrets in other places. For example {% endif %} {% ifversion ghes > 3.2 %} -Además de tu código, probablemente necesitarás utilizar secretos en otros lugares. For example, to allow {% data variables.product.prodname_actions %} workflows or {% data variables.product.prodname_dependabot %} to communicate with other systems. For more information on how to securely store and use secrets, see "[Encrypted secrets in Actions](/actions/security-guides/encrypted-secrets)", and "[Managing encrypted secrets for Dependabot](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-encrypted-secrets-for-dependabot)." +Además de tu código, probablemente necesitarás utilizar secretos en otros lugares. For example, to allow {% data variables.product.prodname_actions %} workflows or {% data variables.product.prodname_dependabot %} to communicate with other systems. Para obtener más información sobre cómo almacenar y utilizar los secretos de forma segura, consulta las secciones "[Secretos cifrados en las acciones](/actions/security-guides/encrypted-secrets)" y "[Administrar los secretos cifrados para el Dependabot](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-encrypted-secrets-for-dependabot)". {% endif %} ## Keep vulnerable coding patterns out of your repository diff --git a/translations/es-ES/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-supply-chain-security.md b/translations/es-ES/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-supply-chain-security.md index fb7db6624e..f1911cf350 100644 --- a/translations/es-ES/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-supply-chain-security.md +++ b/translations/es-ES/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-supply-chain-security.md @@ -27,7 +27,7 @@ With the accelerated use of open source, most projects depend on hundreds of ope You add dependencies directly to your supply chain when you specify them in a manifest file or a lockfile. Dependencies can also be included transitively, that is, even if you don’t specify a particular dependency, but a dependency of yours uses it, then you’re also dependent on that dependency. -{% data variables.product.product_name %} offers a range of features to help you understand the dependencies in your environment{% ifversion ghes < 3.3 or ghae %} and know about vulnerabilities in those dependencies{% endif %}{% ifversion fpt or ghec or ghes > 3.2 %}, know about vulnerabilities in those dependencies, and patch them{% endif %}. +{% data variables.product.product_name %} ofrece un rango de características que te ayudan a entender las dependencias en tu ambiente{% ifversion ghes < 3.3 or ghae %} y conocer las vulnerabilidades en dichas dependencias{% endif %}{% ifversion fpt or ghec or ghes > 3.2 %}, conocer las vulnerabilidades en dichas dependencias y parcharlas{% endif %}. The supply chain features on {% data variables.product.product_name %} are: - **Gráfica de dependencias** @@ -137,7 +137,7 @@ Private repositories: {% elsif ghec %} - **Dependency review**—available in private repositories owned by organizations provided you have a license for {% data variables.product.prodname_GH_advanced_security %} and the dependency graph enabled. Para obtener más información, consulta las secciones "[Acerca de la {% data variables.product.prodname_GH_advanced_security %}](/get-started/learning-about-github/about-github-advanced-security)" y "[Explorar las dependencias de un repositorio](/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository#enabling-and-disabling-the-dependency-graph-for-a-private-repository)" {% endif %} -- **{% data variables.product.prodname_dependabot_alerts %}**—no se habilita predeterminadamente. Los propietarios de los repositorios privados o las personas con acceso administrativo puede habilitar las {% data variables.product.prodname_dependabot_alerts %} si habilitan la gráfica de dependencias y las {% data variables.product.prodname_dependabot_alerts %} para sus repositorios. You can also enable or disable Dependabot alerts for all repositories owned by your user account or organization. Para obtener más información, consulta la sección "[Administrar los ajustes de seguridad y análisis para tu cuenta de usuario](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-security-and-analysis-settings-for-your-user-account)" o "[Administrar lis ajustes de seguridad y análisis para tu organización](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization)". +- **{% data variables.product.prodname_dependabot_alerts %}**—no se habilita predeterminadamente. Los propietarios de los repositorios privados o las personas con acceso administrativo puede habilitar las {% data variables.product.prodname_dependabot_alerts %} si habilitan la gráfica de dependencias y las {% data variables.product.prodname_dependabot_alerts %} para sus repositorios. También puedes habilitar o inhabilitar las alertas del Dependabot para todos los repositorios que pertenezcan a tu cuenta de usuario u organización. Para obtener más información, consulta la sección "[Administrar los ajustes de seguridad y análisis para tu cuenta de usuario](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-security-and-analysis-settings-for-your-user-account)" o "[Administrar lis ajustes de seguridad y análisis para tu organización](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization)". Any repository type: - **{% data variables.product.prodname_dependabot_security_updates %}**—no se habilita predeterminadamente. Puedes habilitar las {% data variables.product.prodname_dependabot_security_updates %} para cualquier repositorio que utilice {% data variables.product.prodname_dependabot_alerts %} y la gráfica de dependencias. For information about enabling security updates, see "[Configuring {% data variables.product.prodname_dependabot_security_updates %}](/code-security/dependabot/dependabot-security-updates/configuring-dependabot-security-updates)." @@ -149,6 +149,6 @@ Any repository type: - **Dependency review**—available when dependency graph is enabled for {% data variables.product.product_location %} and {% data variables.product.prodname_advanced_security %} is enabled for the organization or repository. For more information, see "[About {% data variables.product.prodname_GH_advanced_security %}](/get-started/learning-about-github/about-github-advanced-security)." {% endif %} {% ifversion ghes > 3.2 %} -- **{% data variables.product.prodname_dependabot_security_updates %}**—no se habilita predeterminadamente. Puedes habilitar las {% data variables.product.prodname_dependabot_security_updates %} para cualquier repositorio que utilice {% data variables.product.prodname_dependabot_alerts %} y la gráfica de dependencias. For information about enabling security updates, see "[Configuring {% data variables.product.prodname_dependabot_security_updates %}](/code-security/dependabot/dependabot-security-updates/configuring-dependabot-security-updates)." -- **{% data variables.product.prodname_dependabot_version_updates %}**—no se habilita predeterminadamente. Las personas con permisos de escritura en un repositorio pueden habilitar las {% data variables.product.prodname_dependabot_version_updates %}. For information about enabling version updates, see "[Configuring {% data variables.product.prodname_dependabot_version_updates %}](/code-security/dependabot/dependabot-version-updates/configuring-dependabot-version-updates)." +- **{% data variables.product.prodname_dependabot_security_updates %}**—no se habilita predeterminadamente. Puedes habilitar las {% data variables.product.prodname_dependabot_security_updates %} para cualquier repositorio que utilice {% data variables.product.prodname_dependabot_alerts %} y la gráfica de dependencias. Para obtener más información sobre cómo habilitar las actualizaciones de seguridad, consulta la sección "[Configurar las {% data variables.product.prodname_dependabot_security_updates %}](/code-security/dependabot/dependabot-security-updates/configuring-dependabot-security-updates)". +- **{% data variables.product.prodname_dependabot_version_updates %}**—no se habilita predeterminadamente. Las personas con permisos de escritura en un repositorio pueden habilitar las {% data variables.product.prodname_dependabot_version_updates %}. Para obtener más información sobre cómo habilitar las actualizaciones de versión, consulta la sección "[Configurar las {% data variables.product.prodname_dependabot_version_updates %}](/code-security/dependabot/dependabot-version-updates/configuring-dependabot-version-updates)". {% endif %} diff --git a/translations/es-ES/content/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-the-dependency-graph.md b/translations/es-ES/content/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-the-dependency-graph.md index 1a4c8b7d6b..383ac86645 100644 --- a/translations/es-ES/content/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-the-dependency-graph.md +++ b/translations/es-ES/content/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-the-dependency-graph.md @@ -1,6 +1,6 @@ --- title: Configuring the dependency graph -intro: You can allow users to identify their projects' dependencies by enabling the dependency graph. +intro: Puedes permitir que los usuarios identifiquen las dependencias de sus proyectos si habilitas la gráfica de dependencias. redirect_from: - /code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph#enabling-the-dependency-graph versions: diff --git a/translations/es-ES/content/codespaces/customizing-your-codespace/setting-your-timeout-period-for-codespaces.md b/translations/es-ES/content/codespaces/customizing-your-codespace/setting-your-timeout-period-for-codespaces.md index c5063f41a7..c7327145e7 100644 --- a/translations/es-ES/content/codespaces/customizing-your-codespace/setting-your-timeout-period-for-codespaces.md +++ b/translations/es-ES/content/codespaces/customizing-your-codespace/setting-your-timeout-period-for-codespaces.md @@ -12,6 +12,8 @@ shortTitle: Configurar el tiempo de inactividad Un codespace dejará de ejecutarse después de un periodo de inactividad. Puedes especificar la longitud de este periodo. El ajuste actualizado se aplicará a cualquier codespace recién creado. +Some organizations may have a maximum idle timeout policy. If an organization policy sets a maximum timeout which is less than the default timeout you have set, the organization's timeout will be used instead of your setting, and you will be notified of this after the codespace is created. For more information, see "[Restricting the idle timeout period](/codespaces/managing-codespaces-for-your-organization/restricting-the-idle-timeout-period)." + {% warning %} **Advertencia**: Los Coespaces se facturan por minuto. Si no estás utilizando un codespace activamente, pero este no ha llegado a su tiempo de inactividad, se te cobrará por el tiempo durante el cual este se ejecute de todos modos. Para obtener más información, consulta la sección "[Acerca de la facturación para los Codespaces](/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces#codespaces-pricing)". @@ -34,7 +36,7 @@ Un codespace dejará de ejecutarse después de un periodo de inactividad. Puedes {% data reusables.cli.cli-learn-more %} -Para configurar el periodo de inactividad cuando creas un codespace, utiliza el argumento `idle-timeout` con el subcomando `codespace create`. Especifica el tiempo en minutos, seguido de `m`. La hora debe ser entre 5 y 240 minutos (4 horas). +Para configurar el periodo de inactividad cuando creas un codespace, utiliza el argumento `idle-timeout` con el subcomando `codespace create`. Especifica el tiempo en minutos, seguido de `m`. El tiempo debe ser de entre 5 minutos y 240 minutos (4 horas). ```shell gh codespace create --idle-timeout 90m diff --git a/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/index.md b/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/index.md index 71d9910b79..aaf47bb23d 100644 --- a/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/index.md +++ b/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/index.md @@ -15,6 +15,7 @@ children: - /reviewing-your-organizations-audit-logs-for-codespaces - /restricting-access-to-machine-types - /restricting-the-visibility-of-forwarded-ports + - /restricting-the-idle-timeout-period shortTitle: Admnistrar tu organización --- diff --git a/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types.md b/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types.md index 9be06c5572..35216c6d1a 100644 --- a/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types.md +++ b/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types.md @@ -1,9 +1,9 @@ --- title: Restringir el acceso a los tipos de máquina -shortTitle: Acceso de los tipos de máquina +shortTitle: Restrict machine types intro: Puedes configurar restricciones en los tipos de máquina que los usuarios pueden elegir cuando crean codespaces en tu organizción. product: '{% data reusables.gated-features.codespaces %}' -permissions: 'To manage access to machine types for the repositories in an organization, you must be an organization owner.' +permissions: 'To manage access to machine types for the repositories in an organization, you must be an owner of the organization.' versions: fpt: '*' ghec: '*' @@ -20,7 +20,7 @@ Como propietario de organización, podrías querer configurar restricciones en l ### Comportamiento cuando configuras una restricción de tipo de máquina -If there are existing codespaces that no longer conform to a policy you have defined, these codespaces will continue to operate until they are stopped or time out. Cuando el usuario intente reanudar el codespace, se le mostrará un mensaje que indica que el tipo de máquina que se seleccionó actualmente ya no está permitido en esta organización y se indicará elegir un tipo de máquina como alternativa. +Si existen codespaces que ya no se conformen con alguna política que hayas definido, estos seguirán operando hasta que se les detenga o hasta que se agote el tiempo. Cuando el usuario intente reanudar el codespace, se le mostrará un mensaje que indica que el tipo de máquina que se seleccionó actualmente ya no está permitido en esta organización y se indicará elegir un tipo de máquina como alternativa. Si eliminas tipos de máquina con especificaciones más altas, los cuales requiera la configuración de {% data variables.product.prodname_codespaces %} para un repositorio individual de tu organización, entonces no se podrá crear un codespace en dicho repositorio. Cuando alguien intenta crear un codespace, verán un mensaje que les dice que no hay tipos de máquina válidos disponibles que cumplan con los requisitos de la configuración de {% data variables.product.prodname_codespaces %} del repositorio. @@ -47,33 +47,22 @@ Si agregas una política a nivel organizacional, deberías configurarla en la el {% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} -1. En la sección de "Código, planeación y automatización" de la barra lateral, selecciona **{% octicon "codespaces" aria-label="The codespaces icon" %} {% data variables.product.prodname_codespaces %}** y luego haz clic en **Política**. -2. En la página de "Políticas de los codespaces", haz clic en **Crear política**. -3. Ingresa un nombre para tu política nueva. -4. Haz clic en **Agregar restricción** y elige **Tipos de máquina**. +{% data reusables.codespaces.codespaces-org-policies %} +1. Haz clic en **Agregar restricción** y elige **Tipos de máquina**. ![Agrega una restricción para los tipos de máquina](/assets/images/help/codespaces/add-constraint-dropdown.png) -5. Haz clic en {% octicon "pencil" aria-label="The edit icon" %} para editar la restricción y luego borra la selección de cualquier tipo de máquina que no quieras que estén disponibles. +1. Haz clic en {% octicon "pencil" aria-label="The edit icon" %} para editar la restricción y luego borra la selección de cualquier tipo de máquina que no quieras que estén disponibles. ![Editar la restricción de tipo de máquina](/assets/images/help/codespaces/edit-machine-constraint.png) -6. En el área de "Cambiar destino de la política", haz clic en el botón desplegable. -7. Elige y asea **Todos los repositorios** o **Repositorios seleccionados** para determinar a cuáles aplicará esta política. -8. Si eliges **Repositorios seleccionados**: - 1. Da clic en {% octicon "gear" aria-label="The settings icon" %}. - - ![Editar los ajustes para la política](/assets/images/help/codespaces/policy-edit.png) - - 2. Selecciona los repositorios a los cuales quieres que aplique esta política. - 3. En la parte inferior de la lista de repositorios, haz clic en **Seleccionar repositorios**. - - ![Selecciona los repositorios para esta política](/assets/images/help/codespaces/policy-select-repos.png) - -9. Haz clic en **Save ** (guardar). - +{% data reusables.codespaces.codespaces-policy-targets %} +1. If you want to add another constraint to the policy, click **Add constraint** and choose another constraint. For information about other constraints, see "[Restricting the visibility of forwarded ports](/codespaces/managing-codespaces-for-your-organization/restricting-the-visibility-of-forwarded-ports)" and "[Restricting the idle timeout period](/codespaces/managing-codespaces-for-your-organization/restricting-the-idle-timeout-period)." +1. After you have finished adding constraints to your policy, click **Save**. ## Editar una política +You can edit an existing policy. For example, you may want to add or remove constraints to or from a policy. + 1. Muestra la página de "Políticas del Codespace". Para obtener más información, consulta la sección "[Agregar una política para limitar los tipos de máquina disponibles](#adding-a-policy-to-limit-the-available-machine-types)". 1. Haz clic en el nombre de la política que quieres editar. 1. Haz los cambios requeridos y luego haz clic en **Guardar**. diff --git a/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/restricting-the-idle-timeout-period.md b/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/restricting-the-idle-timeout-period.md new file mode 100644 index 0000000000..ffa73b00d9 --- /dev/null +++ b/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/restricting-the-idle-timeout-period.md @@ -0,0 +1,79 @@ +--- +title: Restricting the idle timeout period +shortTitle: Restrict timeout periods +intro: You can set a maximum timeout period for any codespaces owned by your organization. +product: '{% data reusables.gated-features.codespaces %}' +permissions: 'To manage timeout constraints for an organization''s codespaces, you must be an owner of the organization.' +versions: + fpt: '*' + ghec: '*' +type: how_to +topics: + - Codespaces +--- + +## Resumen + +By default, codespaces time out after 30 minutes of inactivity. When a codespace times out it is stopped and will no longer incur charges for compute usage. + +The personal settings of a {% data variables.product.prodname_dotcom %} user allow them to define their own timeout period for codespaces they create. This may be longer than the default 30-minute period. For more information, see "[Setting your timeout period for Codespaces](/codespaces/customizing-your-codespace/setting-your-timeout-period-for-codespaces)." + +As an organization owner, you may want to configure constraints on the maximum idle timeout period for codespaces owned by your organization. This can help you limit costs associated with codespaces that are left to timeout after long periods of inactivity. You can set a maximum timeout for all codespaces owned by your organization, or for the codespaces of specific repositories. + +{% note %} + +**Note**: Maximum idle timeout constraints only apply to codespaces that are owned by your organization. + +{% endnote %} + +For more information about pricing for {% data variables.product.prodname_codespaces %} compute usage, see "[About billing for Codespaces](/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces#codespaces-pricing)." + +### Behavior when you set a maximum idle timeout constraint + +If someone sets the default idle timeout to 90 minutes in their personal settings and they then start a codespace for a repository with a maximum idle timeout constraint of 60 minutes, the codespace will time out after 60 minutes of inactivity. When codespace creation completes, a message explaining this will be displayed: + +> Idle timeout for this codespace is set to 60 minutes in compliance with your organization’s policy. + +### Configurar políticas específicas para los repositorios y a lo largo de la organización + +When you create a policy, you choose whether it applies to all repositories in your organization, or only to specified repositories. If you create an organization-wide policy with a timeout constraint, then the timeout constraints in any policies that are targeted at specific repositories must fall within the restriction configured for the entire organization. The shortest timeout period - in an organization-wide policy, a policy targeted at specified repositories, or in someone's personal settings - is applied. + +If you add an organization-wide policy with a timeout constraint, you should set the timeout to the longest acceptable period. You can then add separate policies that set the maximum timeout to a shorter period for specific repositories in your organization. + +## Adding a policy to set a maximum idle timeout period + +{% data reusables.profile.access_org %} +{% data reusables.profile.org_settings %} +{% data reusables.codespaces.codespaces-org-policies %} +1. Click **Add constraint** and choose **Maximum idle timeout**. + + ![Add a constraint for idle timeout](/assets/images/help/codespaces/add-constraint-dropdown-timeout.png) + +1. Click {% octicon "pencil" aria-label="The edit icon" %} to edit the constraint. + + ![Edit the timeout constraint](/assets/images/help/codespaces/edit-timeout-constraint.png) + +1. Enter the maximum number of minutes codespaces can remain inactive before they time out, then click **Save**. + + ![Choose the port visibility options](/assets/images/help/codespaces/maximum-minutes-timeout.png) + +{% data reusables.codespaces.codespaces-policy-targets %} +1. If you want to add another constraint to the policy, click **Add constraint** and choose another constraint. For information about other constraints, see "[Restricting access to machine types](/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types)" and "[Restricting the visibility of forwarded ports](/codespaces/managing-codespaces-for-your-organization/restricting-the-visibility-of-forwarded-ports)." +1. After you have finished adding constraints to your policy, click **Save**. + +The policy will be applied to all new codespaces that are created, and to existing codespaces the next time they are started. + +## Editar una política + +You can edit an existing policy. For example, you may want to add or remove constraints to or from a policy. + +1. Muestra la página de "Políticas del Codespace". For more information, see "[Adding a policy to set a maximum idle timeout period](#adding-a-policy-to-set-a-maximum-idle-timeout-period)." +1. Haz clic en el nombre de la política que quieres editar. +1. Haz los cambios requeridos y luego haz clic en **Guardar**. + +## Borrar una política + +1. Muestra la página de "Políticas del Codespace". For more information, see "[Adding a policy to set a maximum idle timeout period](#adding-a-policy-to-set-a-maximum-idle-timeout-period)." +1. Haz clic en el botón de borrar a la derecha de la política que quieras borrar. + + ![El botón de borrar para una política](/assets/images/help/codespaces/policy-delete.png) diff --git a/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/restricting-the-visibility-of-forwarded-ports.md b/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/restricting-the-visibility-of-forwarded-ports.md index 6b4f7ce02b..4679bf6b63 100644 --- a/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/restricting-the-visibility-of-forwarded-ports.md +++ b/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/restricting-the-visibility-of-forwarded-ports.md @@ -1,9 +1,9 @@ --- title: Restricting the visibility of forwarded ports -shortTitle: Restricting port visibility +shortTitle: Restrict port visibility intro: You can set constraints on the visibility options users can choose when they forward ports from codespaces in your organization. product: '{% data reusables.gated-features.codespaces %}' -permissions: 'To manage access to port visibility constraints for the repositories in an organization, you must be an organization owner.' +permissions: 'To manage access to port visibility constraints for the repositories in an organization, you must be an owner of the organization.' versions: fpt: '*' ghec: '*' @@ -20,7 +20,7 @@ As an organization owner, you may want to configure constraints on the visibilit ### Behavior when you set a port visibility constraint -If there are existing codespaces that no longer conform to a policy you have defined, these codespaces will continue to operate until they are stopped or time out. When the user resumes the codespace, it will be subject to the policy constraints. +Si existen codespaces que ya no se conformen con alguna política que hayas definido, estos seguirán operando hasta que se les detenga o hasta que se agote el tiempo. When the user resumes the codespace, it will be subject to the policy constraints. {% note %} @@ -40,14 +40,12 @@ If you add an organization-wide policy, you should set it to the most lenient vi {% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} -1. In the "Code, planning, and automation" section of the sidebar, select **{% octicon "codespaces" aria-label="The codespaces icon" %} {% data variables.product.prodname_codespaces %}** then click **Policies**. -1. En la página de "Políticas de los codespaces", haz clic en **Crear política**. -1. Ingresa un nombre para tu política nueva. +{% data reusables.codespaces.codespaces-org-policies %} 1. Click **Add constraint** and choose **Port visibility**. ![Add a constraint for port visibility](/assets/images/help/codespaces/add-constraint-dropdown-ports.png) -1. Click {% octicon "pencil" aria-label="The edit icon" %} to edit the constraint +1. Click {% octicon "pencil" aria-label="The edit icon" %} to edit the constraint. ![Edit the port visibility constraint](/assets/images/help/codespaces/edit-port-visibility-constraint.png) @@ -55,29 +53,20 @@ If you add an organization-wide policy, you should set it to the most lenient vi ![Choose the port visibility options](/assets/images/help/codespaces/choose-port-visibility-options.png) -1. En el área de "Cambiar destino de la política", haz clic en el botón desplegable. -1. Elige y asea **Todos los repositorios** o **Repositorios seleccionados** para determinar a cuáles aplicará esta política. -1. Si eliges **Repositorios seleccionados**: - 1. Da clic en {% octicon "gear" aria-label="The settings icon" %}. - - ![Editar los ajustes para la política](/assets/images/help/codespaces/policy-edit.png) - - 2. Selecciona los repositorios a los cuales quieres que aplique esta política. - 3. En la parte inferior de la lista de repositorios, haz clic en **Seleccionar repositorios**. - - ![Selecciona los repositorios para esta política](/assets/images/help/codespaces/policy-select-repos.png) - -1. Haz clic en **Save ** (guardar). - +{% data reusables.codespaces.codespaces-policy-targets %} +1. If you want to add another constraint to the policy, click **Add constraint** and choose another constraint. For information about other constraints, see "[Restricting access to machine types](/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types)" and "[Restricting the idle timeout period](/codespaces/managing-codespaces-for-your-organization/restricting-the-idle-timeout-period)." +1. After you have finished adding constraints to your policy, click **Save**. ## Editar una política -1. Muestra la página de "Políticas del Codespace". For more information, see "[Adding a policy to limit the port visibility options](#adding-a-policy-to-limit-the-port-visibility-options)." +You can edit an existing policy. For example, you may want to add or remove constraints to or from a policy. + +1. Muestra la página de "Políticas del Codespace". Para obtener más información, consulta la sección "[Agregar una política para limitar las opciones de visibilidad de puerto](#adding-a-policy-to-limit-the-port-visibility-options)". 1. Haz clic en el nombre de la política que quieres editar. 1. Haz los cambios requeridos y luego haz clic en **Guardar**. ## Borrar una política -1. Muestra la página de "Políticas del Codespace". For more information, see "[Adding a policy to limit the port visibility options](#adding-a-policy-to-limit-the-port-visibility-options)." +1. Muestra la página de "Políticas del Codespace". Para obtener más información, consulta la sección "[Agregar una política para limitar las opciones de visibilidad de puerto](#adding-a-policy-to-limit-the-port-visibility-options)". 1. Haz clic en el botón de borrar a la derecha de la política que quieras borrar. ![El botón de borrar para una política](/assets/images/help/codespaces/policy-delete.png) diff --git a/translations/es-ES/content/codespaces/prebuilding-your-codespaces/managing-prebuilds.md b/translations/es-ES/content/codespaces/prebuilding-your-codespaces/managing-prebuilds.md index 2fc3be5518..b5d7183469 100644 --- a/translations/es-ES/content/codespaces/prebuilding-your-codespaces/managing-prebuilds.md +++ b/translations/es-ES/content/codespaces/prebuilding-your-codespaces/managing-prebuilds.md @@ -88,7 +88,7 @@ Predeterminadamente, el flujo de trabajo de {% data variables.product.prodname_a {% warning %} - **Warning**: Although you can generate the PAT using your existing personal account, we strongly recommend creating a new account with access only to the target repositories required for your scenario. This is because the access token's `repository` permission grants access to all of the repositories that the account has access to. For more information, see "[Signing up for a new GitHub account](/get-started/signing-up-for-github/signing-up-for-a-new-github-account)" and "[Security hardening for {% data variables.product.prodname_actions %}](/actions/security-guides/security-hardening-for-github-actions#considering-cross-repository-access)." + **Warning**: Although you can generate the PAT using your existing personal account, we strongly recommend creating a new account with access only to the target repositories required for your scenario. This is because the access token's `repository` permission grants access to all of the repositories that the account has access to. Para obtener más información, consulta las secciones "[Registrarse para obtener una cuenta nueva de GitHub](/get-started/signing-up-for-github/signing-up-for-a-new-github-account)" y "[Fortalecimiento de seguridad para las {% data variables.product.prodname_actions %}](/actions/security-guides/security-hardening-for-github-actions#considering-cross-repository-access)". {% endwarning %} 1. Give the new account read access to the required repositories. Para obtener más información, consulta la sección "[Administrar el acceso de un individuo a un repositorio de la organización](/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository)". diff --git a/translations/es-ES/content/codespaces/troubleshooting/troubleshooting-prebuilds.md b/translations/es-ES/content/codespaces/troubleshooting/troubleshooting-prebuilds.md index 1994194eff..7860cef261 100644 --- a/translations/es-ES/content/codespaces/troubleshooting/troubleshooting-prebuilds.md +++ b/translations/es-ES/content/codespaces/troubleshooting/troubleshooting-prebuilds.md @@ -46,7 +46,7 @@ cat /workspaces/.codespaces/shared/environment-variables.json | jq '.ACTION_NAME You may notice that sometimes, when you create a new codespace from a prebuild-enabled branch, the "{% octicon "zap" aria-label="The zap icon" %} Prebuild Ready" label is not displayed in the dialog box for choosing a machine type. This means that prebuilds are not currently available. -By default, each time you push to a prebuild-enabled branch, the prebuild template is updated. If the push involves a change to the dev container configuration then, while the update is in progress, the "{% octicon "zap" aria-label="The zap icon" %} Prebuild Ready" label is removed from the list of machine types. During this time you can still create codespaces without a prebuild template. If required, you can reduce the occasions on which prebuilds are unavailable for a repository by setting the prebuild template to be updated only when you make a change to your dev container configuration files, or only on a custom schedule. For more information, see "[Configuring prebuilds](/codespaces/prebuilding-your-codespaces/configuring-prebuilds#configuring-a-prebuild)." +By default, each time you push to a prebuild-enabled branch, the prebuild template is updated. If the push involves a change to the dev container configuration then, while the update is in progress, the "{% octicon "zap" aria-label="The zap icon" %} Prebuild Ready" label is removed from the list of machine types. During this time you can still create codespaces without a prebuild template. If required, you can reduce the occasions on which prebuilds are unavailable for a repository by setting the prebuild template to be updated only when you make a change to your dev container configuration files, or only on a custom schedule. Para obtener más información, consulta la sección "[Configurar las precompilaciones](/codespaces/prebuilding-your-codespaces/configuring-prebuilds#configuring-a-prebuild)". If your branch is not specifically enabled for prebuilds it may still benefit from prebuilds if it was branched from a prebuild-enabled branch. However, if the dev container configuration is changed on your branch, so that it's not the same as the configuration on the base branch, prebuilds will no longer be available on your branch. diff --git a/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/committing-and-reviewing-changes-to-your-project.md b/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/committing-and-reviewing-changes-to-your-project.md index ec56c0afc8..e38173ab49 100644 --- a/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/committing-and-reviewing-changes-to-your-project.md +++ b/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/committing-and-reviewing-changes-to-your-project.md @@ -123,3 +123,11 @@ Una vez que estés satisfecho con los cambios que elegiste incluir en tu confirm ![Advertencia de rama protegida](/assets/images/help/desktop/protected-branch-warning.png) {% data reusables.desktop.push-origin %} + +6. If you have a pull request based off the branch you are working on, {% data variables.product.prodname_desktop %} will display the status of the checks that have run for the pull request. For more information about checks, see "[Viewing and re-running checks in GitHub Desktop](/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/viewing-and-re-running-checks-in-github-desktop)." + + ![Checks display next to branch name](/assets/images/help/desktop/checks-dialog.png) + + If a pull request has not been created for the current branch, {% data variables.product.prodname_desktop %} will give you the option to create one. Para obtener más información, consulta la sección "[Crear un informe de problemas o solicitud de extracción](/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/creating-an-issue-or-pull-request)." + + ![Crear una solicitud de extracción](/assets/images/help/desktop/mac-create-pull-request.png) diff --git a/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/configuring-notifications-in-github-desktop.md b/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/configuring-notifications-in-github-desktop.md new file mode 100644 index 0000000000..683db3c25f --- /dev/null +++ b/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/configuring-notifications-in-github-desktop.md @@ -0,0 +1,63 @@ +--- +title: Configuring notifications in GitHub Desktop +shortTitle: Configurar notificaciones +intro: '{% data variables.product.prodname_desktop %} will keep you up-to-date with notifications about events that occur in your pull request branch.' +versions: + fpt: '*' +--- + +## About notifications in {% data variables.product.prodname_desktop %} + +{% data variables.product.prodname_desktop %} will show a system notification for events that occur in the currently selected repository. Notifications will be shown when: + +- Pull request checks have failed. +- A pull request review is left with a comment, approval, or requested changes. + +Clicking the notification will switch application focus to {% data variables.product.prodname_desktop %} and provide more detailed information. + +## Notifications about pull request check failures + +When changes are made to a pull request branch, you will receive a notification if the checks fail. + +![pull request checks failed notification](/assets/images/help/desktop/pull-request-checks-failed-notification.png) + +Clicking the notification will display a dialog with details about the checks. Once you've reviewed why the checks have failed, you can re-run the checks, or quickly switch to the pull request branch to get started on fixing the errors. For more information, see "[Viewing and re-running checks in GitHub Desktop](/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/viewing-and-re-running-checks-in-github-desktop)." + +![checks failed dialog](/assets/images/help/desktop/checks-failed-dialog.png) +## Notifications for pull request reviews + +{% data variables.product.prodname_desktop %} will surface a system notification when a teammate has approved, commented, or requested changes in your pull request. See "[About pull request reviews](/github/collaborating-with-issues-and-pull-requests/about-pull-request-reviews)" for more information on pull request reviews. + +![Pull request review notification](/assets/images/help/desktop/pull-request-review-notification.png) + +Clicking the notification will switch application focus to {% data variables.product.prodname_desktop %} and provide more context for the pull request review comment. + +![pull request review dialog](/assets/images/help/desktop/pull-request-review-dialog.png) +## Enabling notifications + +If system notifications are disabled for {% data variables.product.prodname_desktop %} you can follow the steps below to enable them. + +{% mac %} + +1. Click the **Apple** menu, then select **System Preferences**. +2. Select **Notifications & Focus**. +3. Select **{% data variables.product.prodname_desktop %}** from the list of applications. +4. Click **Allow Notifications**. + +![macOS Notifications & Focus](/assets/images/help/desktop/mac-enable-notifications.png) + +For more information about macOS system notifications, see "[Use notifications on your Mac](https://support.apple.com/en-us/HT204079)." + +{% endmac %} + +{% windows %} + +1. Open the **Start** menu, then select **Settings**. +2. Select **System**, then click **Notifications**. +3. Find **{% data variables.product.prodname_desktop %}** in the application list and click **On**. + +![Enable Windows Notifications](/assets/images/help/desktop/windows-enable-notifications.png) + +For more information about Windows system notifications, see "[Change notification settings in Windows](https://support.microsoft.com/en-us/windows/change-notification-settings-in-windows-8942c744-6198-fe56-4639-34320cf9444e)." + +{% endwindows %} diff --git a/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/index.md b/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/index.md index 960852938a..cf4e55d417 100644 --- a/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/index.md +++ b/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/index.md @@ -8,6 +8,8 @@ versions: children: - /creating-an-issue-or-pull-request - /viewing-a-pull-request-in-github-desktop + - /viewing-and-re-running-checks-in-github-desktop + - /configuring-notifications-in-github-desktop - /changing-a-remotes-url-from-github-desktop shortTitle: Trabajar con tu repositorio remoto --- diff --git a/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/viewing-a-pull-request-in-github-desktop.md b/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/viewing-a-pull-request-in-github-desktop.md index c79b44b29a..432fc6ad2a 100644 --- a/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/viewing-a-pull-request-in-github-desktop.md +++ b/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/viewing-a-pull-request-in-github-desktop.md @@ -15,6 +15,8 @@ Puedes ver las solicitudes de extracción que tú o tus colaboradores hayan prop Cuando visualizas una solicitud de extracción en {% data variables.product.prodname_desktop %}, puedes ver un historial de confirmaciones que han hecho los colaboradores. También puedes ver qué archivos modificaron, agregaron o borraron estas confirmaciones. Desde {% data variables.product.prodname_desktop %}, puedes abrir los repositorios en tu editor de texto preferido para ver cualquier cambio o para hacer cambios adicionales. Después de recibir los cambios en una solicitud de extracción, puedes dar retroalimentación en {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta la sección "[Acerca de las revisiones de las solicitudes de extracción](/github/collaborating-with-issues-and-pull-requests/about-pull-request-reviews)". +If checks have been enabled in your repository, {% data variables.product.prodname_desktop %} will show the status of the checks on the pull request and allow you to re-run checks. For more information, see "[Viewing and re-running checks in GitHub Desktop](/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/viewing-and-re-running-checks-in-github-desktop)." + ## Visualizar una solicitud de extracción en {% data variables.product.prodname_desktop %} {% data reusables.desktop.current-branch-menu %} {% data reusables.desktop.click-pull-requests %} diff --git a/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/viewing-and-re-running-checks-in-github-desktop.md b/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/viewing-and-re-running-checks-in-github-desktop.md new file mode 100644 index 0000000000..13800972f3 --- /dev/null +++ b/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/viewing-and-re-running-checks-in-github-desktop.md @@ -0,0 +1,25 @@ +--- +title: Viewing and re-running checks in GitHub Desktop +shortTitle: Viewing and re-running checks +intro: 'You can view the status of checks and re-run them in {% data variables.product.prodname_desktop %}.' +versions: + fpt: '*' +--- + +## About checks in {% data variables.product.prodname_desktop %} + +{% data variables.product.prodname_desktop %} displays the status of checks that have run in your pull request branches. The checks badge next to the branch name will display the *pending, passing,* or *failing* state of the checks. You can also re-run all, failed, or individual checks when viewing the status of the checks in {% data variables.product.prodname_desktop %}. For more information on setting up checks in your repository, see "[About status checks](/github/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks)." + +{% data variables.product.prodname_desktop %} will also show a system notification when checks fail. For more information on enabling notifications, see "[Configuring notifications in GitHub Desktop](/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/configuring-notifications-in-github-desktop)." + +## Viewing and re-running checks + +{% data reusables.desktop.current-branch-menu %} +{% data reusables.desktop.click-pull-requests %} + ![Pestaña Pull Requests en el menú desplegable de la rama actual](/assets/images/help/desktop/branch-drop-down-pull-request-tab.png) +{% data reusables.desktop.choose-pr-from-list %} + ![Lista de las solicitudes de extracción abiertas en el repositorio](/assets/images/help/desktop/click-pull-request.png) +4. Click on the pull request number, to the right of the pull request branch name. ![Checks display next to branch name](/assets/images/help/desktop/checks-dialog.png) +5. To re-run failed checks, click **{% octicon "sync" aria-label="The sync icon" %} Re-run** and select **Re-run Failed Checks**. ![Re-run failed checks](/assets/images/help/desktop/re-run-failed-checks.png) +6. To re-run individual checks, hover over the individual check you want to re-run and select the {% octicon "sync" aria-label="The sync icon" %} icon to re-run the check. ![Re-run individual checks](/assets/images/help/desktop/re-run-individual-checks.png) +7. You will see a confirmation dialog with the summary of the checks that will be re-run. Click **Re-run Checks** to confirm that you want to perform the re-run. ![Re-run confirmation dialog](/assets/images/help/desktop/re-run-confirmation-dialog.png) diff --git a/translations/es-ES/content/developers/apps/building-oauth-apps/scopes-for-oauth-apps.md b/translations/es-ES/content/developers/apps/building-oauth-apps/scopes-for-oauth-apps.md index ce655388a0..0bf093dc94 100644 --- a/translations/es-ES/content/developers/apps/building-oauth-apps/scopes-for-oauth-apps.md +++ b/translations/es-ES/content/developers/apps/building-oauth-apps/scopes-for-oauth-apps.md @@ -67,9 +67,9 @@ X-Accepted-OAuth-Scopes: user |  `user:follow` | Otorga acceso para seguir o dejar de seguir a otros usuarios. | | **`delete_repo`** | Otorga acceso para borrar los repositorios administrables. | | **`write:discussion`** | Permite el acceso de lectura y escritura para los debates de equipo. | -|  `read:discussion` | Permite los accesos de lectura y escritura para los debates de equipo.{% ifversion fpt or ghae or ghec %} +|  `read:discussion` | Allows read access for team discussions. | | **`write:packages`** | Otorga acceso para cargar o publicar un paquete en el {% data variables.product.prodname_registry %}. Para obtener más información, consulta la sección "[Publicar un paquete](/github/managing-packages-with-github-packages/publishing-a-package)". | -| **`read:packages`** | Otorga acceso para descargar o instalar paquetes desde el {% data variables.product.prodname_registry %}. Para obtener más información, consulta la sección "[Instalar un paquete](/github/managing-packages-with-github-packages/installing-a-package)". | +| **`read:packages`** | Otorga acceso para descargar o instalar paquetes desde el {% data variables.product.prodname_registry %}. For more information, see "[Installing a package](/github/managing-packages-with-github-packages/installing-a-package)".{% ifversion fpt or ghec or ghes > 3.1 or ghae %} | **`delete:packages`** | Otorga acceso para borrar paquetes del {% data variables.product.prodname_registry %}. Para obtener más información, consulta la sección "[Borrar y restablecer un paquete](/packages/learn-github-packages/deleting-and-restoring-a-package)".{% endif %} | **`admin:gpg_key`** | Administra las llaves GPG totalmente. | |  `write:gpg_key` | Crea, lista, y visualiza los detalles de las llaves GPG. | diff --git a/translations/es-ES/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md b/translations/es-ES/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md index 857f0e8f78..82c5d0766b 100644 --- a/translations/es-ES/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md +++ b/translations/es-ES/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md @@ -811,8 +811,6 @@ Se eliminó el evento para el cual se configuró este webhook. Este evento únic {% endif %} -{% ifversion fpt or ghae or ghec %} - ## paquete Actividad relacionada con el {% data variables.product.prodname_registry %}. {% data reusables.webhooks.action_type_desc %} para obtener más información, consulta la sección "[Administrar paquetes con {% data variables.product.prodname_registry %}](/github/managing-packages-with-github-packages)" para aprender más sobre el {% data variables.product.prodname_registry %}. @@ -832,7 +830,6 @@ Actividad relacionada con el {% data variables.product.prodname_registry %}. {% ### Ejemplo de carga útil del webhook {{ webhookPayloadsForCurrentVersion.package.published }} -{% endif %} ## page_build diff --git a/translations/es-ES/content/discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions.md b/translations/es-ES/content/discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions.md index 2e878ed8b4..ec1f076818 100644 --- a/translations/es-ES/content/discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions.md +++ b/translations/es-ES/content/discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions.md @@ -27,7 +27,7 @@ Para obtener más información acerca de la participación en los debates, consu Para colaborar con los mantenedores en los debates de los repositorios, un administrador de repositorio o mantenedor de proyeto debe habilitar los {% data variables.product.prodname_discussions %} en dicho repositorio. Para obtener más información, consulta la sección "[Habilitar o inhabilitar los {% data variables.product.prodname_discussions %} para un repositorio](/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository)". -Para colaborar con los mantenedores en los debates de las organizaciones, se deben habilitar los {% data variables.product.prodname_discussions %} en la organización. For more information, see "[Enabling or disabling {% data variables.product.prodname_discussions %} for an organization](/organizations/managing-organization-settings/enabling-or-disabling-github-discussions-for-an-organization)." +Para colaborar con los mantenedores en los debates de las organizaciones, se deben habilitar los {% data variables.product.prodname_discussions %} en la organización. Para obtener más información, consulta la sección "[Habilitar o inhabilitar los {% data variables.product.prodname_discussions %} para una organización](/organizations/managing-organization-settings/enabling-or-disabling-github-discussions-for-an-organization)". ## Iniciar un debate diff --git a/translations/es-ES/content/discussions/managing-discussions-for-your-community/managing-categories-for-discussions.md b/translations/es-ES/content/discussions/managing-discussions-for-your-community/managing-categories-for-discussions.md index 077c052178..a6c8bbf306 100644 --- a/translations/es-ES/content/discussions/managing-discussions-for-your-community/managing-categories-for-discussions.md +++ b/translations/es-ES/content/discussions/managing-discussions-for-your-community/managing-categories-for-discussions.md @@ -43,7 +43,7 @@ Cada categoría debe tener un nombre único y un emoji distintivo, y se le puede Puedes editar una categoría para cambiar el emoji, título, descripción y formato de debate de la misma. -1. On {% data variables.product.product_location %}, navigate to the main page of the repository or organization where you want to create a category. +1. En {% data variables.product.product_location %}, navega a la página principal del repositorio u organización en donde quieres crear una categoría. {% data reusables.discussions.discussions-tab %} 1. A la derecha de la categoría en la lista, da clic en {% octicon "pencil" aria-label="The pencil icon" %}. ![Botón de editar a la derecha de la categoría en la lista de categorías de un repositorio](/assets/images/help/discussions/click-edit-for-category.png) 1. {% data reusables.discussions.edit-category-details %} @@ -54,7 +54,7 @@ Puedes editar una categoría para cambiar el emoji, título, descripción y form Cuando borras una categoría, {% data variables.product.product_name %} enviará todos los debates en la categoría que se borró a una categoría existente que elijas. -1. On {% data variables.product.product_location %}, navigate to the main page of the repository or organization where you want to create a category. +1. En {% data variables.product.product_location %}, navega a la página principal del repositorio u organización en donde quieres crear una categoría. {% data reusables.discussions.discussions-tab %} 1. A la derecha de la categoría en la lista, da clic en {% octicon "trash" aria-label="The trash icon" %}. ![Botón de cesto de basura a la derecha de la categoría en la lista de categorías de un repositorio](/assets/images/help/discussions/click-delete-for-category.png) 1. Utiliza el menú desplegable y elige una categoría nueva para cualquier debate en la categoría que estás eliminando. ![Menú desplegable para elegir una categoría nueva cuando se borra una categoría existente](/assets/images/help/discussions/choose-new-category.png) diff --git a/translations/es-ES/content/discussions/managing-discussions-for-your-community/managing-discussions.md b/translations/es-ES/content/discussions/managing-discussions-for-your-community/managing-discussions.md index 758af85fc1..143caba10e 100644 --- a/translations/es-ES/content/discussions/managing-discussions-for-your-community/managing-discussions.md +++ b/translations/es-ES/content/discussions/managing-discussions-for-your-community/managing-discussions.md @@ -56,7 +56,7 @@ You can pin up to four important discussions above the list of discussions for t ## Editar un debate que se fijó -Editar un debate que se ha fijado no cambiará la categoría del mismo. For more information, see "[Managing categories for discussions](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions)." +Editar un debate que se ha fijado no cambiará la categoría del mismo. Para obtener más información, consulta la sección "[Administrar las categorías de los debates](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions)". {% data reusables.discussions.navigate-to-repo-or-org %} {% data reusables.discussions.discussions-tab %} diff --git a/translations/es-ES/content/discussions/quickstart.md b/translations/es-ES/content/discussions/quickstart.md index 749906f158..7dc934485f 100644 --- a/translations/es-ES/content/discussions/quickstart.md +++ b/translations/es-ES/content/discussions/quickstart.md @@ -62,7 +62,7 @@ Cualquier usuario no autenticado que pueda ver un repositorio podrá crear una e Los propietarios de los repositorios y las personas con acceso de escritura en estos pueden crear categorías nuevas para mantener los debates organizados. De la misma manera, ya que los debates de las organizaciones se basan en un repositorio origen, los propietarios de los repositorios y las personas con acceso de escritura con acceso de escritura en el repositorio origen pueden crear categorías nuevas para estos debates. -Los colaboradores que participen y creen debates nuevos pueden agruparlos en las categorías existentes más relevantes. Los debates también pueden volver a categorizarse después de su creación. For more information, see "[Managing categories for discussions](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions)." +Los colaboradores que participen y creen debates nuevos pueden agruparlos en las categorías existentes más relevantes. Los debates también pueden volver a categorizarse después de su creación. Para obtener más información, consulta la sección "[Administrar las categorías de los debates](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions)". {% data reusables.discussions.you-can-label-discussions %} diff --git a/translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/reuse-an-assignment.md b/translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/reuse-an-assignment.md index 080d59b213..bb6993dcdc 100644 --- a/translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/reuse-an-assignment.md +++ b/translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/reuse-an-assignment.md @@ -4,7 +4,7 @@ intro: 'You can reuse an existing assignment in more than one classroom, includi versions: fpt: '*' permissions: 'Organization owners who are admins for a classroom can reuse assignments from a classroom. {% data reusables.classroom.classroom-admins-link %}' -shortTitle: Reuse an assignment +shortTitle: Rechazar una tarea --- ## About reusing assignments diff --git a/translations/es-ES/content/organizations/collaborating-with-your-team/about-team-discussions.md b/translations/es-ES/content/organizations/collaborating-with-your-team/about-team-discussions.md index f1feeea101..c6fcbe38ea 100644 --- a/translations/es-ES/content/organizations/collaborating-with-your-team/about-team-discussions.md +++ b/translations/es-ES/content/organizations/collaborating-with-your-team/about-team-discussions.md @@ -44,7 +44,7 @@ Para obtener más información, consulta la sección {% ifversion fpt or ghae or {% ifversion fpt or ghec %} -## Organization discussions +## Debates de organización También puedes utilizar los debates de la organización para facilitar las conversaciones en ella. Para obtener más información, consulta la sección "[Habilitar o inhabilitar los debates de GitHub en una organización](/organizations/managing-organization-settings/enabling-or-disabling-github-discussions-for-an-organization)". diff --git a/translations/es-ES/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization.md b/translations/es-ES/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization.md index db938760cd..0fb25f6b1d 100644 --- a/translations/es-ES/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization.md +++ b/translations/es-ES/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization.md @@ -121,7 +121,7 @@ El {% data variables.product.prodname_dependabot %} puede verificar si hay refer Predeterminadamente, el {% data variables.product.prodname_dependabot %} no puede actualizar las dependencias que se ubican en los repositorios o en los registros de paquetes privados. Sin embargo, si una dependencia se encuentra en un repositorio privado de {% data variables.product.prodname_dotcom %} dentro de la misma organización que el proyecto que la utiliza, puedes permitir al {% data variables.product.prodname_dependabot %} actualizar la versión exitosamente si le otorgas acceso al repositorio en el que se hospeda. -Si tu código depende de paquetes en un registro privado, puedes permitir que el {% data variables.product.prodname_dependabot %} actualice las versiones de estas dependencias si configuras esto a nivel del repositorio. Puedes hacer esto si agregas los detalles de autenticación al archivo _dependabot.yml_ para el repositorio. For more information, see "[Configuration options for the dependabot.yml file](/github/administering-a-repository/configuration-options-for-dependency-updates#configuration-options-for-private-registries)." +Si tu código depende de paquetes en un registro privado, puedes permitir que el {% data variables.product.prodname_dependabot %} actualice las versiones de estas dependencias si configuras esto a nivel del repositorio. Puedes hacer esto si agregas los detalles de autenticación al archivo _dependabot.yml_ para el repositorio. Para obtener más información, consulta la sección "[Opciones de configuración para el archivo dependabot.yml](/github/administering-a-repository/configuration-options-for-dependency-updates#configuration-options-for-private-registries)". Para permitir que el {% data variables.product.prodname_dependabot %} acceda a un repositorio privado de {% data variables.product.prodname_dotcom %}: diff --git a/translations/es-ES/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md b/translations/es-ES/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md index 5b5ecf6cf2..f19ecc1070 100644 --- a/translations/es-ES/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md +++ b/translations/es-ES/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md @@ -75,8 +75,8 @@ Para buscar eventos específicos, utiliza el calificador `action` en tu consulta | [`repository_dependency_graph`](#repository_dependency_graph-category-actions) | Contiene las actividades a nivel de repositorio para habilitar o inhabilitar la gráfica de dependencias para un | | repositorio {% ifversion fpt or ghec %}privado{% endif %}. Para obtener más información, consulta la sección "[Acerca de la gráfica de dependencias](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)".{% endif %}{% ifversion ghes or ghae or ghec %} | | | [`repository_secret_scanning`](#repository_secret_scanning-category-actions) | Contiene actividades a nivel de repositorio relacionadas con el escaneo de secretos. Para obtener más información, consulta la sección "[Acerca del escaneo de secretos"](/github/administering-a-repository/about-secret-scanning). |{% endif %}{% if secret-scanning-audit-log-custom-patterns %} -| [`repository_secret_scanning_custom_pattern`](#respository_secret_scanning_custom_pattern-category-actions) | Contains repository-level activities related to secret scanning custom patterns. For more information, see "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)." |{% endif %}{% if secret-scanning-audit-log-custom-patterns %} -| [`repository_secret_scanning_push_protection`](#respository_secret_scanning_push_protection) | Contains repository-level activities related to secret scanning custom patterns. For more information, see "[Protecting pushes with secert scanning](/code-security/secret-scanning/protecting-pushes-with-secret-scanning)." |{% endif %}{% ifversion fpt or ghes or ghae-issue-4864 or ghec %} +| [`repository_secret_scanning_custom_pattern`](#respository_secret_scanning_custom_pattern-category-actions) | Contains repository-level activities related to secret scanning custom patterns. Para obtener más información, consulta la sección "[Definir los patrones personalizados para el escaneo de secretos](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)". |{% endif %}{% if secret-scanning-audit-log-custom-patterns %} +| [`repository_secret_scanning_push_protection`](#respository_secret_scanning_push_protection) | Contiene actividades a nivel de repositorio relacionadas con los patrones personalizados del escaneo de secretos. For more information, see "[Protecting pushes with secert scanning](/code-security/secret-scanning/protecting-pushes-with-secret-scanning)." |{% endif %}{% ifversion fpt or ghes or ghae-issue-4864 or ghec %} | [`repository_vulnerability_alert`](#repository_vulnerability_alert-category-actions) | Contiene todas las actividades relacionadas con [las {% data variables.product.prodname_dependabot_alerts %} para las dependencias vulnerables](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies).{% endif %}{% ifversion fpt or ghec %} | [`repository_vulnerability_alerts`](#repository_vulnerability_alerts-category-actions) | Contiene actividades de configuración a nivel de repositorio para las {% data variables.product.prodname_dependabot_alerts %}.{% endif %}{% ifversion ghec %} | [`rol`](#role-category-actions) | Contiene todas las actividades relacionadas con los [roles de repositorio personalziados](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization).{% endif %}{% ifversion ghes or ghae or ghec %} @@ -522,12 +522,12 @@ Para obtener más información, consulta la sección "[Administrar la publicaci ### Acciones de la categoría `packages` -| Acción | Descripción | -| --------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `package_version_published` | Se activa cuando se publica una versión del paquete. | +| Acción | Descripción | +| --------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `package_version_published` | Se activa cuando se publica una versión del paquete. | | `package_version_deleted` | Triggered when a specific package version is deleted.{% ifversion fpt or ghec or ghes > 3.1 or ghae %} For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)."{% endif %} | `package_deleted` | Triggered when an entire package is deleted.{% ifversion fpt or ghec or ghes > 3.1 or ghae %} For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)."{% endif %} -| `package_version_restored` | Triggered when a specific package version is deleted.{% ifversion fpt or ghec or ghes > 3.1 or ghae %} For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)."{% endif %} +| `package_version_restored` | Se activa cuando se borra una versión de un paquete específico.{% ifversion fpt or ghec or ghes > 3.1 or ghae %} Para obtener más información, consulta la sección "[Borrar y restablecer un paquete](/packages/learn-github-packages/deleting-and-restoring-a-package)".{% endif %} | `package_restored` | Triggered when an entire package is restored.{% ifversion fpt or ghec or ghes > 3.1 or ghae %} For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)."{% endif %} {% ifversion fpt or ghec %} @@ -694,20 +694,20 @@ Para obtener más información, consulta la sección "[Administrar la publicaci ### `repository_secret_scanning_custom_pattern` category actions -| Acción | Descripción | -| ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `create (crear)` | Triggered when a custom pattern is published for secret scanning in a repository. For more information, see "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning#defining-a-custom-pattern-for-a-repository)." | -| `actualización` | Triggered when changes to a custom pattern are saved for secret scanning in a repository. For more information, see "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning#editing-a-custom-pattern)." | -| `delete` | Triggered when a custom pattern is removed from secret scanning in a repository. For more information, see "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning#removing-a-custom-pattern)." | +| Acción | Descripción | +| ---------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `create (crear)` | Triggered when a custom pattern is published for secret scanning in a repository. For more information, see "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning#defining-a-custom-pattern-for-a-repository)." | +| `actualización` | Triggered when changes to a custom pattern are saved for secret scanning in a repository. Para obtener más información, consulta la sección "[Definir los patrones personalizados para el escaneo de secretos](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning#editing-a-custom-pattern)". | +| `delete` | Triggered when a custom pattern is removed from secret scanning in a repository. Para obtener más información, consulta la sección "[Definir los patrones personalizados para el escaneo de secretos](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning#removing-a-custom-pattern)". | {% endif %}{% if secret-scanning-audit-log-custom-patterns %} ### `repository_secret_scanning_push_protection` category actions -| Acción | Descripción | -| ------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `inhabilitar` | Triggered when a repository owner or person with admin access to the repository disables secret scanning for a repository. For more information, see "[Protecting pushes with secret scanning](/code-security/secret-scanning/protecting-pushes-with-secret-scanning)." | -| `habilitar` | Triggered when a repository owner or person with admin access to the repository enables secret scanning for a repository. | +| Acción | Descripción | +| ------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `inhabilitar` | Se activa cuando un propietario del repositorio o persona con acceso administrativo al mismo inhabilita el escaneo de secretos para un repositorio. For more information, see "[Protecting pushes with secret scanning](/code-security/secret-scanning/protecting-pushes-with-secret-scanning)." | +| `habilitar` | Se activa cuando un propietario del repositorio o persona con acceso administrativo al mismo habilita el escaneo de secretos para un repositorio. | {% endif %}{% ifversion fpt or ghes or ghae-issue-4864 or ghec %} ### acciones de la categoría `repository_vulnerability_alert` diff --git a/translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/about-scim-for-organizations.md b/translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/about-scim-for-organizations.md index cc4b462339..6660eb9146 100644 --- a/translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/about-scim-for-organizations.md +++ b/translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/about-scim-for-organizations.md @@ -12,7 +12,7 @@ topics: - Teams --- -## About SCIM for organizations +## Acerca del SCIM para las organizaciones If your organization uses [SAML SSO](/articles/about-identity-and-access-management-with-saml-single-sign-on), you can implement SCIM to add, manage, and remove organization members' access to {% data variables.product.product_name %}. Por ejemplo, un administrador puede desaprovisionar a un miembro de la organización usando el SCIM y eliminar automáticamente el miembro de la organización. diff --git a/translations/es-ES/content/packages/learn-github-packages/introduction-to-github-packages.md b/translations/es-ES/content/packages/learn-github-packages/introduction-to-github-packages.md index 1ffeed2655..f4716e5ca3 100644 --- a/translations/es-ES/content/packages/learn-github-packages/introduction-to-github-packages.md +++ b/translations/es-ES/content/packages/learn-github-packages/introduction-to-github-packages.md @@ -23,7 +23,7 @@ shortTitle: Introduction ## About {% data variables.product.prodname_registry %} -{% data variables.product.prodname_registry %} is a platform for hosting and managing packages, including containers and other dependencies. {% data variables.product.prodname_registry %} combines your source code and packages in one place to provide integrated permissions management{% ifversion not ghae %} and billing{% endif %}, so you can centralize your software development on {% data variables.product.product_name %}. +{% data variables.product.prodname_registry %} is a platform for hosting and managing packages, including containers and other dependencies. {% data variables.product.prodname_registry %} combines your source code and packages in one place to provide integrated permissions management{% ifversion fpt or ghec %} and billing{% endif %}, so you can centralize your software development on {% data variables.product.product_name %}. You can integrate {% data variables.product.prodname_registry %} with {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} APIs, {% data variables.product.prodname_actions %}, and webhooks to create an end-to-end DevOps workflow that includes your code, CI, and deployment solutions. diff --git a/translations/es-ES/content/packages/quickstart.md b/translations/es-ES/content/packages/quickstart.md index 3f525a2fae..326478f92c 100644 --- a/translations/es-ES/content/packages/quickstart.md +++ b/translations/es-ES/content/packages/quickstart.md @@ -21,7 +21,7 @@ En esta guía, crearás un flujo de trabajo de {% data variables.product.prodnam 1. Crea un repositorio nuevo en {% data variables.product.prodname_dotcom %}, agregando el `.gitignore` para Node. Para obtener más información, consulta la sección "[Crear un repositorio nuevo](/github/creating-cloning-and-archiving-repositories/creating-a-new-repository)". 2. Clona el repositorio en tu máquina local. ```shell - $ git clone https://{% ifversion ghae %}YOUR-HOSTNAME{% else %}github.com{% endif %}/YOUR-USERNAME/YOUR-REPOSITORY.git + $ git clone https://{% ifversion ghes or ghae %}YOUR-HOSTNAME{% else %}github.com{% endif %}/YOUR-USERNAME/YOUR-REPOSITORY.git $ cd YOUR-REPOSITORY ``` 3. Crea un archivo `index.js` y agrega una alerta básica que diga "Hello world!" @@ -49,7 +49,7 @@ En esta guía, crearás un flujo de trabajo de {% data variables.product.prodnam $ git push ``` 6. Crea un directorio de `.github/workflows`. En este directorio, crea un archivo que se llame `release-package.yml`. -7. Copia el siguiente contenido de YAML en el archivo `release-package.yml`{% ifversion ghae %}, reemplazando a `YOUR-HOSTNAME` con el nombre de tu empresa{% endif %}. +7. Copia el siguiente contenido de YAML en el archivo `release-package.yml`{% ifversion ghes or ghae %}, reemplazando a `YOUR-HOSTNAME` con el nombre de tu empresa{% endif %}. ```yaml{:copy} name: Node.js Package @@ -79,7 +79,7 @@ En esta guía, crearás un flujo de trabajo de {% data variables.product.prodnam - uses: {% data reusables.actions.action-setup-node %} with: node-version: 12 - registry-url: {% ifversion ghae %}https://npm.YOUR-HOSTNAME.com/{% else %}https://npm.pkg.github.com/{% endif %} + registry-url: {% ifversion ghes or ghae %}https://npm.YOUR-HOSTNAME.com/{% else %}https://npm.pkg.github.com/{% endif %} - run: npm ci - run: npm publish env: diff --git a/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-a-merge-queue.md b/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-a-merge-queue.md index 0a6a4b9041..f813b60f02 100644 --- a/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-a-merge-queue.md +++ b/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-a-merge-queue.md @@ -15,7 +15,7 @@ redirect_from: {% data reusables.pull_requests.merge-queue-beta %} -## About merge queues +## Acerca de las colas de fusión {% data reusables.pull_requests.merge-queue-overview %} @@ -46,7 +46,7 @@ Para obtener más información acerca de los métodos de fusión, consulta "[Ace {% data reusables.pull_requests.merge-queue-reject %} -## Managing a merge queue +## Administrar una cola de fusión Repository administrators can require a merge by enabling the branch protection setting "Require merge queue" in the protection rules for the base branch. diff --git a/translations/es-ES/content/rest/codespaces/repository-secrets.md b/translations/es-ES/content/rest/codespaces/repository-secrets.md index 681e200c1b..258b351c81 100644 --- a/translations/es-ES/content/rest/codespaces/repository-secrets.md +++ b/translations/es-ES/content/rest/codespaces/repository-secrets.md @@ -10,6 +10,6 @@ topics: miniTocMaxHeadingLevel: 3 --- -## Repository Secrets +## Secretos de repositorio -The Repository Secrets API allows a user to create, list, and delete secrets (such as access tokens for cloud services) for repositories that the user has access to. Estos secretos se hacen disponibles para el codespace en el tiempo de ejecución. Para obtener más información, consulta la sección "[Administrar los secretos cifrados para tu codespace](/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces)". +La API de secretos de repositorio permite que un usuario cree, liste y borre secretos (tales como los tokens de acceso para los servicios en la nube) para los repositorios a los cuales tiene acceso. Estos secretos se hacen disponibles para el codespace en el tiempo de ejecución. Para obtener más información, consulta la sección "[Administrar los secretos cifrados para tu codespace](/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces)". diff --git a/translations/es-ES/content/rest/codespaces/secrets.md b/translations/es-ES/content/rest/codespaces/secrets.md index 2e00573443..4cf7867197 100644 --- a/translations/es-ES/content/rest/codespaces/secrets.md +++ b/translations/es-ES/content/rest/codespaces/secrets.md @@ -10,6 +10,6 @@ miniTocMaxHeadingLevel: 3 allowTitleToDifferFromFilename: true --- -## User Secrets +## Secretos de usuario -The User Secrets API allows a user to create, list, and delete secrets (such as access tokens for cloud services) as well as assign secrets to repositories that the user has access to. Estos secretos se hacen disponibles para el codespace en el tiempo de ejecución. Para obtener más información, consulta la sección "[Administrar los secretos cifrados para tu codespace](/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces)". +La API de secretos de usuario permite que un usuario cree, liste y borre secretos (tales como los tokens de acceso para los servicios en la nube) así como asignar secretos a los repositorios a los que el usuario tenga acceso. Estos secretos se hacen disponibles para el codespace en el tiempo de ejecución. Para obtener más información, consulta la sección "[Administrar los secretos cifrados para tu codespace](/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces)". diff --git a/translations/es-ES/content/rest/collaborators/collaborators.md b/translations/es-ES/content/rest/collaborators/collaborators.md index 41a65987f2..baa91c2713 100644 --- a/translations/es-ES/content/rest/collaborators/collaborators.md +++ b/translations/es-ES/content/rest/collaborators/collaborators.md @@ -1,6 +1,6 @@ --- title: Colaboradores -intro: 'The Collaborators API allows you to add, invite, and remove collaborators from a repository.' +intro: 'La API de colaboradores te permite agregar, invitar y eliminar colaboradores de un repositorio.' versions: fpt: '*' ghes: '*' diff --git a/translations/es-ES/content/rest/dependabot/secrets.md b/translations/es-ES/content/rest/dependabot/secrets.md index 01a598ef20..c947b21daf 100644 --- a/translations/es-ES/content/rest/dependabot/secrets.md +++ b/translations/es-ES/content/rest/dependabot/secrets.md @@ -1,6 +1,6 @@ --- title: Secretos -intro: 'With the Dependabot Secrets API, you can manage and control Dependabot secrets for an organization or repository.' +intro: 'Con la API de secretos del Dependabot, puedes administrar y controlar los secretos del Dependabot para una organización o repositorio.' topics: - API versions: diff --git a/translations/es-ES/content/rest/dependency-graph/dependency-review.md b/translations/es-ES/content/rest/dependency-graph/dependency-review.md index 0935c3ac5f..96520c9722 100644 --- a/translations/es-ES/content/rest/dependency-graph/dependency-review.md +++ b/translations/es-ES/content/rest/dependency-graph/dependency-review.md @@ -16,4 +16,4 @@ allowTitleToDifferFromFilename: true {% data reusables.dependency-review.dependency-review-api-beta-note %} -The Dependency Review API allows you to understand dependency changes, and the security impact of these changes, before you add them to your environment. You can view the diff of dependencies between two commits of a repository, including vulnerability data for any version updates with known vulnerabilities. For more information about dependency review, see "[About dependency review](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review)." +La API de revisión de dependencias te permite entender los cambios a las dependencias y el impacto de seguridad de estos antes de que los agregues a tu ambiente. You can view the diff of dependencies between two commits of a repository, including vulnerability data for any version updates with known vulnerabilities. Para obtener más información sobre la revisión de dependencias, consulta la sección "[Acerca de la revisión de dependencias](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review)". diff --git a/translations/es-ES/content/rest/issues/timeline.md b/translations/es-ES/content/rest/issues/timeline.md index dcb541bf94..832ee529bf 100644 --- a/translations/es-ES/content/rest/issues/timeline.md +++ b/translations/es-ES/content/rest/issues/timeline.md @@ -11,6 +11,6 @@ topics: miniTocMaxHeadingLevel: 3 --- -For more information about the specific events that you can receive from the Issue Events API, see "[Issue event types](/developers/webhooks-and-events/issue-event-types)." Para obtener más información acerca de los eventos específicos que puedes recibir de la API de Eventos para Solicitudes de Extracción, consulta la sección "[Tipos de evento de las Solicitudes de Extracción](/developers/webhooks-and-events/issue-event-types)". Para obtener más información, consulta la "[API de Eventos de GitHub](/developers/webhooks-and-events/github-event-types)". +Para obtener más información sobre los tipos de eventos específicos que puedes recibir desde la API de eventos de propuestas, consulta la sección "[Tipos de eventos de propuestas](/developers/webhooks-and-events/issue-event-types)". Para obtener más información acerca de los eventos específicos que puedes recibir de la API de Eventos para Solicitudes de Extracción, consulta la sección "[Tipos de evento de las Solicitudes de Extracción](/developers/webhooks-and-events/issue-event-types)". Para obtener más información, consulta la "[API de Eventos de GitHub](/developers/webhooks-and-events/github-event-types)". Puedes utilizar esta API para mostrar información sobre los informes de problemas y solicitudes de extracción o para determinar a quién debería notificársele sobre los comentarios en los informes de problemas. diff --git a/translations/es-ES/content/rest/packages.md b/translations/es-ES/content/rest/packages.md index a1ee37e166..97cc2d5bc0 100644 --- a/translations/es-ES/content/rest/packages.md +++ b/translations/es-ES/content/rest/packages.md @@ -11,7 +11,7 @@ redirect_from: - /rest/reference/packages --- -The {% data variables.product.prodname_registry %} API enables you to manage packages using the REST API.{% ifversion fpt or ghec or ghes > 3.1 or ghae %} To learn more about restoring or deleting packages, see "[Restoring and deleting packages](/packages/learn-github-packages/deleting-and-restoring-a-package)."{% endif %} +La API de {% data variables.product.prodname_registry %} te habilita para administrar paquetes utilizando la API de REST.{% ifversion fpt or ghec or ghes > 3.1 or ghae %} Para aprender más sobre cómo restablecer o borrar paquetes, consulta la sección "[restablecer y borrar paquetes](/packages/learn-github-packages/deleting-and-restoring-a-package)".{% endif %} Para utilizar esta API, primero tienes que autenticarte utilizando un token de acceso personal. - Para acceder a los metadatos del paquete, tu token debe incluir el alcance `read:packages`. diff --git a/translations/es-ES/content/rest/secret-scanning.md b/translations/es-ES/content/rest/secret-scanning.md index 840e51573d..6847e3f95d 100644 --- a/translations/es-ES/content/rest/secret-scanning.md +++ b/translations/es-ES/content/rest/secret-scanning.md @@ -16,7 +16,7 @@ redirect_from: La API del {% data variables.product.prodname_secret_scanning %} te permite {% ifversion fpt or ghec or ghes > 3.1 or ghae %}: -- Enable or disable {% data variables.product.prodname_secret_scanning %}{% if secret-scanning-push-protection %} and push protection{% endif %} for a repository. For more information, see "[Repositories](/rest/reference/repos#update-a-repository)" and expand the "Properties of the `security_and_analysis` object" section in the REST API documentation. +- Enable or disable {% data variables.product.prodname_secret_scanning %}{% if secret-scanning-push-protection %} and push protection{% endif %} for a repository. Para obtener más información, consulta la sección "[Repositorios](/rest/reference/repos#update-a-repository)" y expande la sección de "Propiedades del objeto `security_and_analysis`" en la documentación de la API de REST. - Retrieve and update {% data variables.product.prodname_secret_scanning_GHAS %} alerts from a repository. For further details, see the sections below. {%- else %} retrieve and update {% data variables.product.prodname_secret_scanning %} alerts from a repository.{% endif %} diff --git a/translations/es-ES/content/site-policy/acceptable-use-policies/github-acceptable-use-policies.md b/translations/es-ES/content/site-policy/acceptable-use-policies/github-acceptable-use-policies.md index e93cbbfdd8..dc88b27580 100644 --- a/translations/es-ES/content/site-policy/acceptable-use-policies/github-acceptable-use-policies.md +++ b/translations/es-ES/content/site-policy/acceptable-use-policies/github-acceptable-use-policies.md @@ -40,7 +40,7 @@ We do not allow content or activity on GitHub that: ## 3. Intellectual Property, Authenticity, and Private Information -We do not allow content or activity on GitHub that: +No permitimos el contenido o la activad de GitHub que: - que infrinja algún derecho de propiedad de cualquiera de las partes, incluidos la patente, el nombre comercial, el secreto comercial, la propiedad intelectual, el derecho a publicidad o cualquier otro derecho; @@ -64,7 +64,7 @@ We do not allow content or activity on GitHub that is: * using our servers for any form of excessive automated bulk activity, to place undue burden on our servers through automated means, or to relay any form of unsolicited advertising or solicitation through our servers, such as get-rich-quick schemes. ## 5. Site Access and Safety -We do not allow content or activity on GitHub that: +No permitimos el contenido o la activad de GitHub que: - apoye directamente [el ataque ilegal o campañas de malware](/github/site-policy/github-active-malware-or-exploits) que estén causando daños técnicos — tales como utilizar nuestra plataforma para entregar ejecutables malintencionados o como ataque de infraestructura, por ejemplo, organizando ataques de negación de servicio o administrando servidores de control y comando — sin propósitos implícitos o explícitos de uso dual previos a que suceda el abuso; o - uses our servers to disrupt or to attempt to disrupt, or to gain or to attempt to gain unauthorized access to, any service, device, data, account or network. Please note, activities permitted under bug bounty programs, such as the [GitHub Bug Bounty program](https://bounty.github.com), are not considered “unauthorized.” diff --git a/translations/es-ES/content/site-policy/github-terms/github-community-guidelines.md b/translations/es-ES/content/site-policy/github-terms/github-community-guidelines.md index 2cabca28f2..763c72f859 100644 --- a/translations/es-ES/content/site-policy/github-terms/github-community-guidelines.md +++ b/translations/es-ES/content/site-policy/github-terms/github-community-guidelines.md @@ -12,24 +12,24 @@ topics: - Legal --- -Millones de desarrolladores en todo el mundo hospedan millones de proyectos, tanto de código propietario como de código libre, en GitHub. We're fortunate to be able to play a part in enabling collaboration across the developer community every day, which is a responsibility we don’t take lightly. Together, we all have the exciting opportunity to make this a community we can be proud of. +Millones de desarrolladores en todo el mundo hospedan millones de proyectos, tanto de código propietario como de código libre, en GitHub. Somo afortunados de poder tomar parte en habilitar la colaboración a lo largo de la comunidad de desarrolladores cada día, lo cual es una responsabilidad que no nos tomamos a la ligera. Juntos, tenemos la emocionante oportunidad de hacer de esta una comunidad de la cual podamos estar orgullosos. -Nuestra base de usuarios diversa trae perspectivas, ideas y experiencias diferentes y va desde las personas que crearon su primer proyecto de "Hello World" la semana pasada hasta los desarrolladores de software más famosos del mundo. We are committed to making GitHub an environment that welcomes all the different voices and perspectives our community has to offer, while maintaining a safe place for developers to do their best work. +Nuestra base de usuarios diversa trae perspectivas, ideas y experiencias diferentes y va desde las personas que crearon su primer proyecto de "Hello World" la semana pasada hasta los desarrolladores de software más famosos del mundo. Estamos comprometidos a crear un ambiente de GitHub que dé la bienvenida a todas las voces y perspectivas diferentes que nuestra comunidad tiene para ofrecer al mismo tiempo que mantenemos un lugar seguro para que los desarrolladores realicen su mejor trabajo. Al detallar cómo pensamos que debería ser una [comunidad segura, acogedora y productiva](https://opensource.guide/building-community/) en GitHub esperamos ayudarte a entender cómo sería la mejor forma de interactuar y colaborar en nuestra plataforma alineándonos con nuestros [Términos de servicio](/github/site-policy/github-terms-of-service) y [Políticas de uso aceptables](/github/site-policy/github-acceptable-use-policies). -We encourage our community members to communicate expectations clearly, [moderate](#what-if-something-or-someone-offends-you) their projects where possible, and [report](https://github.com/contact/report-abuse) any content that may violate our [policies](/github/site-policy/github-terms-of-service). GitHub Staff will investigate any reports of abuse, and may moderate public content on our site that we determine to be in violation of our Terms of Service. +Invitamos a nuestros miembros de la comunidad para que comuniquen sus expectativas claramente, [moderen](#what-if-something-or-someone-offends-you) sus proyectos en medida de lo posible y [reporten](https://github.com/contact/report-abuse) cualquier contenido que pudiera violar nuestras [políticas](/github/site-policy/github-terms-of-service). GitHub Staff will investigate any reports of abuse, and may moderate public content on our site that we determine to be in violation of our Terms of Service. ## Maintaining a strong community El propósito principal de la comunidad de GitHub es colaborar en proyectos de software. Estamos comprometidos a mantener una comunidad donde los usuarios sean libres de expresarse y desafiar las ideas de los demás, tanto técnicas como de otro tipo. Al mismo tiempo, es importante que los usuarios sigan siendo respetosos y permitan que exista un espacio para que los demás contribuyan abiertamente. Para fomentar un ambiente tanto productivo como seguro, exhortamos a nuestros miembros de la comunidad a seguir estos lineamientos para que se informen de cómo interactuar en nuestra plataforma. A continuación, encontrarás algunas sugerencias de cómo tener interacciones exitosas como un miembro valioso de la comunidad de GitHub. -* **Se receptivo y de mente abierta** - Los usuarios nuevos se unen a nuestra comunidad diariamente. Some are well-established developers, while others are just beginning. Mantente abierto a otras ideas y niveles de experiencia. Permite las opiniones diferentes a la tuya y recibe a los colaboradores nuevos y a aquellos que están comenzando. +* **Se receptivo y de mente abierta** - Los usuarios nuevos se unen a nuestra comunidad diariamente. Algunos son desarrolladores bien establecidos, mientras que otros apenas están comenzando. Mantente abierto a otras ideas y niveles de experiencia. Permite las opiniones diferentes a la tuya y recibe a los colaboradores nuevos y a aquellos que están comenzando. -* **Sé respetuoso** - El trabajar en un ambiente colaborativo, significa que pueden existir los desacuerdos. Pero recuerda criticar las ideas, no a las personas. Share thoughtful, constructive criticism and be courteous to those you interact with. Si no puedes participar respetuosamente, considera retirarte o utilizar alguna de nuestras herramientas de moderación para apaciguar una situación tensa. +* **Sé respetuoso** - El trabajar en un ambiente colaborativo, significa que pueden existir los desacuerdos. Pero recuerda criticar las ideas, no a las personas. Comparte un criticismo constructivo y considerado y sé cortés con las personas que interactúes. Si no puedes participar respetuosamente, considera retirarte o utilizar alguna de nuestras herramientas de moderación para apaciguar una situación tensa. -* **Sé empático** - GitHub es una comunidad global con personas de una amplia gama de antecedentes y perspectivas, muchas de las cuales podrían no ser las mismas que las tuyas. Try to put yourself in others’ shoes and understand their feelings before you address them. Haz tu mejor esfuerzo para ayudar a que la comunidad de GitHub sea un lugar en donde todos se sientan seguros para hacer contribuciones, participar en debates y compartir ideas diferentes. +* **Sé empático** - GitHub es una comunidad global con personas de una amplia gama de antecedentes y perspectivas, muchas de las cuales podrían no ser las mismas que las tuyas. Intenta empatizar con los demás y entiende su sentir antes de que te dirijas a ellos. Haz tu mejor esfuerzo para ayudar a que la comunidad de GitHub sea un lugar en donde todos se sientan seguros para hacer contribuciones, participar en debates y compartir ideas diferentes. ## ¿Qué pasa si algo o alguien te ofende? @@ -39,7 +39,7 @@ While some disagreements can be resolved with direct, respectful communication b * **Comunicar las expectativas** - Los mantenedores pueden configurar lineamientos específicos para las comunidades para ayudar a los usuarios a entender cómo interactuar con sus proyectos, por ejemplo, en el README de un repositorio, el [archivo de CONTRIBUTING](/articles/setting-guidelines-for-repository-contributors/) o en un [código de conducta dedicado](/articles/adding-a-code-of-conduct-to-your-project/). You can find additional information on building communities [here](/communities). -* **Moderate Comments** - Users with [write-access privileges](/articles/repository-permission-levels-for-an-organization/) for a repository can [edit, delete, or hide anyone's comments](/communities/moderating-comments-and-conversations/managing-disruptive-comments) on commits, pull requests, and issues. Cualquier persona con acceso de lectura a un repositorio puede ver el historial de edición del comentario. Comment authors and people with write access to a repository can also delete sensitive information from a [comment's edit history](/communities/moderating-comments-and-conversations/tracking-changes-in-a-comment). El moderar tus proyectos puede sentirse como una tarea grande si hay mucha actividad, pero puedes [agregar colaboradores](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-a-user-account-repository#collaborator-access-for-a-repository-owned-by-a-personal-account) para que te ayuden a administrar tu comunidad. +* **Moderar los comentarios** - Los usuarios con [privilegios de acceso de escritura](/articles/repository-permission-levels-for-an-organization/) en un repositorio pueden [editar, borrar u ocultar los comentarios de quien sea](/communities/moderating-comments-and-conversations/managing-disruptive-comments) en las confirmaciones, solicitudes de cambio y propuestas. Cualquier persona con acceso de lectura a un repositorio puede ver el historial de edición del comentario. Comment authors and people with write access to a repository can also delete sensitive information from a [comment's edit history](/communities/moderating-comments-and-conversations/tracking-changes-in-a-comment). El moderar tus proyectos puede sentirse como una tarea grande si hay mucha actividad, pero puedes [agregar colaboradores](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-a-user-account-repository#collaborator-access-for-a-repository-owned-by-a-personal-account) para que te ayuden a administrar tu comunidad. * **Bloquear conversaciones** - Si un debate en una propuesta, solicitud de cambios o confirmación se sale de control o de tema o viola el código de conducta de tu proyecto o las políticas de GitHub, los colaboradores y el resto de las personas con acceso de descritura pueden [bloquearlo](/articles/locking-conversations/) temporal o permanentemente en la conversación. diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-1/18.yml b/translations/es-ES/data/release-notes/enterprise-server/3-1/18.yml index f912fd5e07..66305adf74 100644 --- a/translations/es-ES/data/release-notes/enterprise-server/3-1/18.yml +++ b/translations/es-ES/data/release-notes/enterprise-server/3-1/18.yml @@ -4,7 +4,7 @@ sections: security_fixes: - "ALTA: Se identificó una vulnerabilidad de desbordamiento de integrales en el analizador de lenguaje de marcado de GitHub, la cual pudo haber ocasionado fugas de información potenciales y RCE. Esta vulnerabilidad la reportó Felix Wilhelm, del proyecto Zero de Google, mediante el programa de Recompensas por Errores de GitHub y se le asignó el CVE-2022-24724." bugs: - - Upgrades could sometimes fail if a high-availability replica's clock was out of sync with the primary. + - Las mejoras fallaron algunas veces si el reloj de una réplica de disponibilidad alta se desincronizó con el primario. - 'OAuth Applications created after September 1st, 2020 were not able to use the [Check an Authorization](https://docs.github.com/en/enterprise-server@3.1/rest/reference/apps#check-an-authorization) API endpoint.' known_issues: - El registor de npm del {% data variables.product.prodname_registry %} ya no regresa un valor de tiempo en las respuestas de metadatos. Esto se hizo para permitir mejoras de rendimiento sustanciales. Seguimos teniendo todos los datos necesarios para devolver un valor de tiempo como parte de la respuesta de metadatos y terminaremos de devolver este valor ene l futuro una vez que hayamos resuelto los problemas de rendimiento existentes. diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-1/19.yml b/translations/es-ES/data/release-notes/enterprise-server/3-1/19.yml index a91afb5d29..365c729530 100644 --- a/translations/es-ES/data/release-notes/enterprise-server/3-1/19.yml +++ b/translations/es-ES/data/release-notes/enterprise-server/3-1/19.yml @@ -2,40 +2,40 @@ date: '2022-04-04' sections: security_fixes: - 'MEDIA: Se identificó una vulnerabilidad de recorrido de ruta en la consola de administración de {% data variables.product.prodname_ghe_server %}, la cual permitió un puenteo de las protecciones CSRF. Esta vulnerabilidad afectó a todas las versiones de {% data variables.product.prodname_ghe_server %} anteriores a la 3.5 y se corrigió en las versiones 3.1.19, 3.2.11, 3.3.6 y 3.4.1. Esta vulnerabilidad se reportó mediante el programa de recompensas por errores de {% data variables.product.prodname_dotcom %} y se le asignó el CVE-2022-23732.' - - 'MEDIUM: An integer overflow vulnerability was identified in the 1.x branch and the 2.x branch of `yajil` which leads to subsequent heap memory corruption when dealing with large (~2GB) inputs. This vulnerability was reported internally and has been assigned CVE-2022-24795. ' - - 'Support bundles could include sensitive files if {% data variables.product.prodname_actions %} was enabled.' + - 'MEDIA: Se identificó una vulnerabilidad de desbordamiento de números enteros en la rama 1.x y 2.x de `yajil`, lo cual conllevó a una corrupción subsecuente de memoria dinámica al lidiar con entradas grandes (~2GB). Esta vulnerabilidad se reportó internamente y se le asignó el CVE-2022-24795. ' + - 'Los paquetes de soporte podrían incluir archivos sensibles si es que se habilitaron las {% data variables.product.prodname_actions %}.' - 'Los paquetes se actualizaron a las últimas versiones de seguridad.' bugs: - - 'The options to enable `TLS 1.0` and `TLS 1.1` in the Privacy settings of the Management Console were shown, although removal of those protocol versions occurred in an earlier release.' - - 'In a HA environment, configuring MSSQL replication could require additional manual steps after enabling {% data variables.product.prodname_actions %} for the first time.' + - 'Se mostraron las opciones para habilitar `TLS 1.0` y `TLS 1.1` en los ajustes de privacidad de la consola de administración a pesar de haber eliminado esas versiones de protocolo que ocurrieron en un lanzamiento anterior.' + - 'En un ambiente de HA, el configurar la replicación de MSSQL podría requerir pasos manuales adicionales después de habilitar las {% data variables.product.prodname_actions %} por primera ocasión.' - 'Un subconjunto de archivos de configuración interna se actualiza de forma más confiable después de un hotpatch.' - - 'The `ghe-run-migrations` script would sometimes fail to generate temporary certificate names correctly.' - - 'In a cluster environment, Git LFS operations could fail with failed internal API calls that crossed multiple web nodes.' - - 'Pre-receive hooks that used `gpg --import` timed out due to insufficient `syscall` privileges.' - - 'In some cluster topologies, webhook delivery information was not available.' + - 'Algunas veces, el script `ghe-run-migrations` falló en generar nombres de certificados temporales correctamente.' + - 'En un ambiente de clúster, las operaciones de LFS de git pudieron haber fallado con llamadas fallidas a la API interna que cruzaron diversos nodos web.' + - 'Los ganchos de pre-recepción que utilizaron `gpg --import` agotaron su tiempo de espera debido a que no tuvieron los privilegios de `syscall` suficientes.' + - 'En algunas topologías de clúster, no estuvo disponible la información de entrega de webhooks.' - 'In HA configurations, tearing down a replica would fail if {% data variables.product.prodname_actions %} had previously been enabled.' - - 'Elasticsearch health checks would not allow a yellow cluster status when running migrations.' - - 'Organizations created as a result of a user transforming their user account into an organization were not added to the global enterprise account.' + - 'La verificación de salud de Elasticsearch no permitió un estado de clúster amarillo al ejecutar las migraciones.' + - 'Las organizaciones que se crearon como resultado de que un usuario haya transformado su cuenta de usuario en una organización no se agregaron a la cuenta empresarial global.' - 'When using `ghe-migrator` or exporting from {% data variables.product.prodname_dotcom_the_website %}, a long-running export would fail when data was deleted mid-export.' - - 'Links to inaccessible pages were removed.' + - 'Se eliminaron los enlaces a las páginas inaccesibles.' - 'El agregar a un equipo como revisor para una solicitud de cambios algunas veces muestra la cantidad incorrecta de miembros en un equipo.' - 'Una gran cantidad de usuarios inactivos podría ocasionar que falle una configuración de {% data variables.product.prodname_github_connect %}.' - - 'The "Feature & beta enrollments" page in the Site admin web UI was incorrectly available.' - - 'The "Site admin mode" link in the site footer did not change state when clicked.' + - 'La página de "Características e inscripciones beta" en la IU web del administrador de sitio estuvieron disponibles de forma incorrecta.' + - 'El enlace de "Modo de administrador de sitio" en el pie de página del sitio no cambió de estado cuando se hizo clic sobre este.' changes: - - 'Memcached connection limits were increased to better accommodate large cluster topologies.' + - 'Los límites de conexión almacenados en la memoria de alto rendimiento se incrementaron para adaptarse mejor a las topologías de clústers grandes.' - 'More effectively identify and delete webhook logs that are outside of the webhook log retention window.' - - 'The Dependency Graph API previously ran with a statically defined port.' - - 'The default shard counts for cluster-related Elasticsearch shard settings have been updated.' - - 'The “Triage” and “Maintain” team roles are preserved during repository migrations.' + - 'La API de la gráfica de dependencias se ejecutó previamente con un puerto definido estáticamente.' + - 'Se actualizó el conteo de fragmentos de los ajustes de fragmentos de la Elasticsearch relacionada con el clúster.' + - 'Los roles de equipo de "Clasificación" y "Mantenimiento" se preservan durante las migraciones de repositorios.' - '`NotProcessedError` exceptions were occurring unnecessarily.' - - 'Performance has been improved for web requests made by enterprise owners.' + - 'Se mejoró el rendimiento para las solicitudes web que hicieron los propietarios de las empresas.' known_issues: - 'El registor de npm del {% data variables.product.prodname_registry %} ya no regresa un valor de tiempo en las respuestas de metadatos. Esto se hizo para permitir mejoras de rendimiento sustanciales. Seguimos teniendo todos los datos necesarios para devolver un valor de tiempo como parte de la respuesta de metadatos y terminaremos de devolver este valor ene l futuro una vez que hayamos resuelto los problemas de rendimiento existentes.' - 'En una instancia recién configurada de {% data variables.product.prodname_ghe_server %} sin ningún usuario, un atacante podría crear el primer usuario adminsitrador.' - 'Las reglas de cortafuegos personalizadas se eliminan durante el proceso de actualización.' - 'Los archivos rastreados del LFS de Git que se [cargaron mediante la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregaron incorrecta y directamente al repositorio.' - 'Las propuestas no pudieron cerrarse si contenían un permalink a un blob en el mismo repositorio en donde la ruta de archvio del blob era más grande a 255 caracteres.' - - 'When "Users can search GitHub.com" is enabled with {% data variables.product.prodname_github_connect %}, issues in private and internal repositories are not included in {% data variables.product.prodname_dotcom_the_website %} search results.' + - 'Cuando se habilita la opción "Los usuarios pueden buscar en GitHub.com" con las propuestas de {% data variables.product.prodname_github_connect %}, las propuestas en los repositorios internos y privados no se incluyen en los resultados de búsqueda de {% data variables.product.prodname_dotcom_the_website %}.' - 'Si se habilitan las {% data variables.product.prodname_actions %} para {% data variables.product.prodname_ghe_server %}, el desmontar un nodo de réplica con `ghe-repl-teardown` tendrá éxito, pero podría devolver un `ERROR:Running migrations`.' - 'Los límites de recursos que son específicos para procesar ganchos de pre-recepción podrían ocasionar que fallen algunos ganchos de pre-recepción.' diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-1/20.yml b/translations/es-ES/data/release-notes/enterprise-server/3-1/20.yml index 7c82e4bfab..e5a8d1f357 100644 --- a/translations/es-ES/data/release-notes/enterprise-server/3-1/20.yml +++ b/translations/es-ES/data/release-notes/enterprise-server/3-1/20.yml @@ -3,11 +3,11 @@ sections: security_fixes: - 'Los paquetes se actualizaron a las últimas versiones de seguridad.' bugs: - - 'Upgrading the nodes in a high availability pair with an upgrade package could cause Elasticsearch to enter an inconsistent state in some cases.' - - 'In some cluster topologies, the command line utilities `ghe-spokesctl` and `ghe-btop` failed to run.' - - 'Elasticsearch indices could be duplicated during a package upgrade, due to an `elasticsearch-upgrade` service running multiple times in parallel.' + - 'El cargar nodos en un par con disponibilidad alta con un paquete de mejora pudo haber causado que Elasticsearch ingresara en un estado inconsistente en algunos casos.' + - 'En algunas topologías de clúster, no pudieron ejecutarse las utilidades de línea de comandos `ghe-spokesctl` y `ghe-btop`.' + - 'Los índices de Elastisearch podrían duplicarse durante la mejora de un paquete debido a que el servicio de `elasticsearch-upgrade` se ejecutó varias veces en paralelo.' - 'The `maint_host_low` job queues were not processed, resulting in some maintenance tasks failing to run.' - - 'When converting a user account to an organization, if the user account was an owner of the {% data variables.product.prodname_ghe_server %} enterprise account, the converted organization would incorrectly appear in the enterprise owner list.' + - 'Cuando conviertes una cuenta de usuario en una organización, si dicha cuenta fue propietaria de la cuenta empresarial de {% data variables.product.prodname_ghe_server %}, la organización convertida se mostró incorrectamente en la lista de propietarios de la empresa.' - 'El crear un token de OAuth de personificación utilizando la API de REST de administración de empresas dio como resultado un error cuando una integración que coincidió con la ID de aplicación de OAuth ya existía.' changes: - 'When attempting to cache a value larger than the maximum allowed in Memcached, an error was raised however the key was not reported.' @@ -17,6 +17,6 @@ sections: - 'Las reglas de cortafuegos personalizadas se eliminan durante el proceso de actualización.' - 'Los archivos rastreados del LFS de Git que se [cargaron mediante la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregaron incorrecta y directamente al repositorio.' - 'Las propuestas no pudieron cerrarse si contenían un permalink a un blob en el mismo repositorio en donde la ruta de archvio del blob era más grande a 255 caracteres.' - - 'When "Users can search GitHub.com" is enabled with {% data variables.product.prodname_github_connect %}, issues in private and internal repositories are not included in {% data variables.product.prodname_dotcom_the_website %} search results.' + - 'Cuando se habilita la opción "Los usuarios pueden buscar en GitHub.com" con las propuestas de {% data variables.product.prodname_github_connect %}, las propuestas en los repositorios internos y privados no se incluyen en los resultados de búsqueda de {% data variables.product.prodname_dotcom_the_website %}.' - 'Si se habilitan las {% data variables.product.prodname_actions %} para {% data variables.product.prodname_ghe_server %}, el desmontar un nodo de réplica con `ghe-repl-teardown` tendrá éxito, pero podría devolver un `ERROR:Running migrations`.' - 'Los límites de recursos que son específicos para procesar ganchos de pre-recepción podrían ocasionar que fallen algunos ganchos de pre-recepción.' diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-2/11.yml b/translations/es-ES/data/release-notes/enterprise-server/3-2/11.yml index ade952ad6b..bd41e099cc 100644 --- a/translations/es-ES/data/release-notes/enterprise-server/3-2/11.yml +++ b/translations/es-ES/data/release-notes/enterprise-server/3-2/11.yml @@ -2,42 +2,42 @@ date: '2022-04-04' sections: security_fixes: - 'MEDIA: Se identificó una vulnerabilidad de recorrido de ruta en la consola de administración de {% data variables.product.prodname_ghe_server %}, la cual permitió un puenteo de las protecciones CSRF. Esta vulnerabilidad afectó a todas las versiones de {% data variables.product.prodname_ghe_server %} anteriores a la 3.5 y se corrigió en las versiones 3.1.19, 3.2.11, 3.3.6 y 3.4.1. Esta vulnerabilidad se reportó mediante el programa de recompensas por errores de {% data variables.product.prodname_dotcom %} y se le asignó el CVE-2022-23732.' - - 'MEDIUM: An integer overflow vulnerability was identified in the 1.x branch and the 2.x branch of `yajil` which leads to subsequent heap memory corruption when dealing with large (~2GB) inputs. This vulnerability was reported internally and has been assigned CVE-2022-24795. ' - - 'Support bundles could include sensitive files if {% data variables.product.prodname_actions %} was enabled.' + - 'MEDIA: Se identificó una vulnerabilidad de desbordamiento de números enteros en la rama 1.x y 2.x de `yajil`, lo cual conllevó a una corrupción subsecuente de memoria dinámica al lidiar con entradas grandes (~2GB). Esta vulnerabilidad se reportó internamente y se le asignó el CVE-2022-24795. ' + - 'Los paquetes de soporte podrían incluir archivos sensibles si es que se habilitaron las {% data variables.product.prodname_actions %}.' - 'Los paquetes se actualizaron a las últimas versiones de seguridad.' bugs: - - 'Minio processes would have high CPU usage if an old configuration option was present after upgrading {% data variables.product.prodname_ghe_server %}.' - - 'The options to enable `TLS 1.0` and `TLS 1.1` in the Privacy settings of the Management Console were shown, although removal of those protocol versions occurred in an earlier release.' - - 'In a HA environment, configuring MSSQL replication could require additional manual steps after enabling {% data variables.product.prodname_actions %} for the first time.' + - 'Los procesos de Minio tuvieron un uso alto de CPU si una opción de configuración estuvo presente después de mejorar a {% data variables.product.prodname_ghe_server %}.' + - 'Se mostraron las opciones para habilitar `TLS 1.0` y `TLS 1.1` en los ajustes de privacidad de la consola de administración a pesar de haber eliminado esas versiones de protocolo que ocurrieron en un lanzamiento anterior.' + - 'En un ambiente de HA, el configurar la replicación de MSSQL podría requerir pasos manuales adicionales después de habilitar las {% data variables.product.prodname_actions %} por primera ocasión.' - 'Un subconjunto de archivos de configuración interna se actualiza de forma más confiable después de un hotpatch.' - - 'The `ghe-run-migrations` script would sometimes fail to generate temporary certificate names correctly.' - - 'In a cluster environment, Git LFS operations could fail with failed internal API calls that crossed multiple web nodes.' - - 'Pre-receive hooks that used `gpg --import` timed out due to insufficient `syscall` privileges.' - - 'In some cluster topologies, webhook delivery information was not available.' - - 'In HA configurations, tearing down a replica would fail if {% data variables.product.prodname_actions %} had previously been enabled.' - - 'Elasticsearch health checks would not allow a yellow cluster status when running migrations.' - - 'Organizations created as a result of a user transforming their user account into an organization were not added to the global enterprise account.' - - 'When using `ghe-migrator` or exporting from {% data variables.product.prodname_dotcom_the_website %}, a long-running export would fail when data was deleted mid-export.' - - 'The {% data variables.product.prodname_actions %} deployment graph would display an error when rendering a pending job.' - - 'Links to inaccessible pages were removed.' + - 'Algunas veces, el script `ghe-run-migrations` falló en generar nombres de certificados temporales correctamente.' + - 'En un ambiente de clúster, las operaciones de LFS de git pudieron haber fallado con llamadas fallidas a la API interna que cruzaron diversos nodos web.' + - 'Los ganchos de pre-recepción que utilizaron `gpg --import` agotaron su tiempo de espera debido a que no tuvieron los privilegios de `syscall` suficientes.' + - 'En algunas topologías de clúster, no estuvo disponible la información de entrega de webhooks.' + - 'En las configuraciones de disponibilidad alta, el derribar una réplica falló si se había habilitado {% data variables.product.prodname_actions %} previamente.' + - 'La verificación de salud de Elasticsearch no permitió un estado de clúster amarillo al ejecutar las migraciones.' + - 'Las organizaciones que se crearon como resultado de que un usuario haya transformado su cuenta de usuario en una organización no se agregaron a la cuenta empresarial global.' + - 'Cuando utilizas `ghe-migrator` o exportas desde {% data variables.product.prodname_dotcom_the_website %}, una exportación de duración larga falló cuando se borraron datos a media exportación.' + - 'La gráfica de despliegue de {% data variables.product.prodname_actions %} mostró un error al procesar un job pendiente.' + - 'Se eliminaron los enlaces a las páginas inaccesibles.' - 'Navigating away from a comparison of two commits in the web UI would have the diff persist in other pages.' - 'El agregar a un equipo como revisor para una solicitud de cambios algunas veces muestra la cantidad incorrecta de miembros en un equipo.' - 'The [Remove team membership for a user](/rest/reference/teams#remove-team-membership-for-a-user) API endpoint would respond with an error when attempting to remove a member managed externally by a SCIM group.' - 'Una gran cantidad de usuarios inactivos podría ocasionar que falle una configuración de {% data variables.product.prodname_github_connect %}.' - - 'The "Feature & beta enrollments" page in the Site admin web UI was incorrectly available.' - - 'The "Site admin mode" link in the site footer did not change state when clicked.' - - 'The `spokesctl cache-policy rm` command no longer fails with the message `error: failed to delete cache policy`.' + - 'La página de "Características e inscripciones beta" en la IU web del administrador de sitio estuvieron disponibles de forma incorrecta.' + - 'El enlace de "Modo de administrador de sitio" en el pie de página del sitio no cambió de estado cuando se hizo clic sobre este.' + - 'El comando `spokesctl cache-policy rm` ya no falla con el mensaje de `error: failed to delete cache policy`.' changes: - - 'Memcached connection limits were increased to better accommodate large cluster topologies.' - - 'The Dependency Graph API previously ran with a statically defined port.' - - 'The default shard counts for cluster-related Elasticsearch shard settings have been updated.' - - 'The “Triage” and “Maintain” team roles are preserved during repository migrations.' - - 'Performance has been improved for web requests made by enterprise owners.' + - 'Los límites de conexión almacenados en la memoria de alto rendimiento se incrementaron para adaptarse mejor a las topologías de clústers grandes.' + - 'La API de la gráfica de dependencias se ejecutó previamente con un puerto definido estáticamente.' + - 'Se actualizó el conteo de fragmentos de los ajustes de fragmentos de la Elasticsearch relacionada con el clúster.' + - 'Los roles de equipo de "Clasificación" y "Mantenimiento" se preservan durante las migraciones de repositorios.' + - 'Se mejoró el rendimiento para las solicitudes web que hicieron los propietarios de las empresas.' known_issues: - 'En una instancia recién configurada de {% data variables.product.prodname_ghe_server %} sin ningún usuario, un atacante podría crear el primer usuario adminsitrador.' - 'Las reglas de cortafuegos personalizadas se eliminan durante el proceso de actualización.' - 'Los archivos rastreados del LFS de Git que se [cargaron mediante la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregaron incorrecta y directamente al repositorio.' - 'Las propuestas no pudieron cerrarse si contenían un permalink a un blob en el mismo repositorio en donde la ruta de archvio del blob era más grande a 255 caracteres.' - - 'When "Users can search GitHub.com" is enabled with {% data variables.product.prodname_github_connect %}, issues in private and internal repositories are not included in {% data variables.product.prodname_dotcom_the_website %} search results.' + - 'Cuando se habilita la opción "Los usuarios pueden buscar en GitHub.com" con las propuestas de {% data variables.product.prodname_github_connect %}, las propuestas en los repositorios internos y privados no se incluyen en los resultados de búsqueda de {% data variables.product.prodname_dotcom_the_website %}.' - 'El registor de npm del {% data variables.product.prodname_registry %} ya no regresa un valor de tiempo en las respuestas de metadatos. Esto se hizo para permitir mejoras de rendimiento sustanciales. Seguimos teniendo todos los datos necesarios para devolver un valor de tiempo como parte de la respuesta de metadatos y terminaremos de devolver este valor ene l futuro una vez que hayamos resuelto los problemas de rendimiento existentes.' - 'Los límites de recursos que son específicos para procesar ganchos de pre-recepción podrían ocasionar que fallen algunos ganchos de pre-recepción.' diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-2/12.yml b/translations/es-ES/data/release-notes/enterprise-server/3-2/12.yml index 7f35bf5c9f..3483d537d3 100644 --- a/translations/es-ES/data/release-notes/enterprise-server/3-2/12.yml +++ b/translations/es-ES/data/release-notes/enterprise-server/3-2/12.yml @@ -3,21 +3,21 @@ sections: security_fixes: - 'Los paquetes se actualizaron a las últimas versiones de seguridad.' bugs: - - 'Upgrading the nodes in a high availability pair with an upgrade package could cause Elasticsearch to enter an inconsistent state in some cases.' - - 'In some cluster topologies, the command line utilities `ghe-spokesctl` and `ghe-btop` failed to run.' - - 'Elasticsearch indices could be duplicated during a package upgrade, due to an `elasticsearch-upgrade` service running multiple times in parallel.' - - 'When converting a user account to an organization, if the user account was an owner of the {% data variables.product.prodname_ghe_server %} enterprise account, the converted organization would incorrectly appear in the enterprise owner list.' + - 'El cargar nodos en un par con disponibilidad alta con un paquete de mejora pudo haber causado que Elasticsearch ingresara en un estado inconsistente en algunos casos.' + - 'En algunas topologías de clúster, no pudieron ejecutarse las utilidades de línea de comandos `ghe-spokesctl` y `ghe-btop`.' + - 'Los índices de Elastisearch podrían duplicarse durante la mejora de un paquete debido a que el servicio de `elasticsearch-upgrade` se ejecutó varias veces en paralelo.' + - 'Cuando conviertes una cuenta de usuario en una organización, si dicha cuenta fue propietaria de la cuenta empresarial de {% data variables.product.prodname_ghe_server %}, la organización convertida se mostró incorrectamente en la lista de propietarios de la empresa.' - 'Creating an impersonation OAuth token using the Enterprise Administration REST API worked incorrectly when an integration matching the OAuth Application ID already existed.' changes: - 'Los errores de configuración que detienen una ejecución de aplicación de configuraciones ahora son el producto de la terminal adicionalmente a la bitácora de configuración.' - - 'When attempting to cache a value larger than the maximum allowed in Memcached, an error was raised however the key was not reported.' + - 'Al intentar almacenar en caché un valor que fuera más grande que el máximo permitido en Memcached, se levantó un error pero la clave no se reportó.' - 'The {% data variables.product.prodname_codeql %} starter workflow no longer errors even if the default token permissions for {% data variables.product.prodname_actions %} are not used.' - - 'If {% data variables.product.prodname_GH_advanced_security %} features are enabled on your instance, the performance of background jobs has improved when processing batches for repository contributions.' + - 'Si se habilitaron las características de {% data variables.product.prodname_GH_advanced_security %} en tu instancia, el rendimiento de los jobs en segundo plano mejoró al procesar los lotes para las contribuciones de repositorio.' known_issues: - 'En una instancia recién configurada de {% data variables.product.prodname_ghe_server %} sin ningún usuario, un atacante podría crear el primer usuario adminsitrador.' - 'Las reglas de cortafuegos personalizadas se eliminan durante el proceso de actualización.' - 'Los archivos rastreados del LFS de Git que se [cargaron mediante la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregaron incorrecta y directamente al repositorio.' - 'Las propuestas no pudieron cerrarse si contenían un permalink a un blob en el mismo repositorio en donde la ruta de archvio del blob era más grande a 255 caracteres.' - - 'When "Users can search GitHub.com" is enabled with {% data variables.product.prodname_github_connect %}, issues in private and internal repositories are not included in {% data variables.product.prodname_dotcom_the_website %} search results.' + - 'Cuando se habilita la opción "Los usuarios pueden buscar en GitHub.com" con las propuestas de {% data variables.product.prodname_github_connect %}, las propuestas en los repositorios internos y privados no se incluyen en los resultados de búsqueda de {% data variables.product.prodname_dotcom_the_website %}.' - 'El registor de npm del {% data variables.product.prodname_registry %} ya no regresa un valor de tiempo en las respuestas de metadatos. Esto se hizo para permitir mejoras de rendimiento sustanciales. Seguimos teniendo todos los datos necesarios para devolver un valor de tiempo como parte de la respuesta de metadatos y terminaremos de devolver este valor ene l futuro una vez que hayamos resuelto los problemas de rendimiento existentes.' - 'Los límites de recursos que son específicos para procesar ganchos de pre-recepción podrían ocasionar que fallen algunos ganchos de pre-recepción.' diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-3/0.yml b/translations/es-ES/data/release-notes/enterprise-server/3-3/0.yml index 11fef155fc..15099e91f7 100644 --- a/translations/es-ES/data/release-notes/enterprise-server/3-3/0.yml +++ b/translations/es-ES/data/release-notes/enterprise-server/3-3/0.yml @@ -93,7 +93,7 @@ sections: - 'El registor de npm del {% data variables.product.prodname_registry %} ya no regresa un valor de tiempo en las respuestas de metadatos. Esto se hizo para permitir mejoras de rendimiento sustanciales. Seguimos teniendo todos los datos necesarios para devolver un valor de tiempo como parte de la respuesta de metadatos y terminaremos de devolver este valor ene l futuro una vez que hayamos resuelto los problemas de rendimiento existentes.' - 'Los límites de recursos que son específicos para procesar ganchos de pre-recepción podrían ocasionar que fallen algunos ganchos de pre-recepción.' - 'Los ajustes de almacenamiento de {% data variables.product.prodname_actions %} no pueden validarse y guardarse en la {% data variables.enterprise.management_console %} cuando se selecciona "Forzar estilo de ruta" y, en su lugar, debe configurarse la utilidad de línea de comando `ghe-actions-precheck`.' - - '{% data variables.product.prodname_ghe_server %} 3.3 instances installed on Azure and provisioned with 32+ CPU cores would fail to launch, due to a bug present in the current Linux kernel. [Updated: 2022-04-08]' + - 'Las instancias de {% data variables.product.prodname_ghe_server %} 3.3 instaladas en Azure y aprovisionadas 32 núcleos de CPU o más fallaron para lanzarse debido a un error presente en el kernel actual de Linux. [Actualizado: 2022-08-04]' deprecations: - heading: 'Obsoletización de GitHub Enterprise Server 2.22' notes: diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-3/1.yml b/translations/es-ES/data/release-notes/enterprise-server/3-3/1.yml index 58c66d2c7d..e7d8e204a3 100644 --- a/translations/es-ES/data/release-notes/enterprise-server/3-3/1.yml +++ b/translations/es-ES/data/release-notes/enterprise-server/3-3/1.yml @@ -14,4 +14,4 @@ sections: - El registor de npm del {% data variables.product.prodname_registry %} ya no regresa un valor de tiempo en las respuestas de metadatos. Esto se hizo para permitir mejoras de rendimiento sustanciales. Seguimos teniendo todos los datos necesarios para devolver un valor de tiempo como parte de la respuesta de metadatos y terminaremos de devolver este valor ene l futuro una vez que hayamos resuelto los problemas de rendimiento existentes. - Los límites de recursos que son específicos para procesar ganchos de pre-recepción podrían ocasionar que fallen algunos ganchos de pre-recepción. - 'Los ajustes de almacenamiento de {% data variables.product.prodname_actions %} no pueden validarse y guardarse en la {% data variables.enterprise.management_console %} cuando se selecciona "Forzar estilo de ruta" y, en su lugar, debe configurarse la utilidad de línea de comando `ghe-actions-precheck`.' - - '{% data variables.product.prodname_ghe_server %} 3.3 instances installed on Azure and provisioned with 32+ CPU cores would fail to launch, due to a bug present in the current Linux kernel. [Updated: 2022-04-08]' + - 'Las instancias de {% data variables.product.prodname_ghe_server %} 3.3 instaladas en Azure y aprovisionadas 32 núcleos de CPU o más fallaron para lanzarse debido a un error presente en el kernel actual de Linux. [Actualizado: 2022-08-04]' diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-3/3.yml b/translations/es-ES/data/release-notes/enterprise-server/3-3/3.yml index 6809ad476b..8259fe7d5e 100644 --- a/translations/es-ES/data/release-notes/enterprise-server/3-3/3.yml +++ b/translations/es-ES/data/release-notes/enterprise-server/3-3/3.yml @@ -26,4 +26,4 @@ sections: - 'El registor de npm del {% data variables.product.prodname_registry %} ya no regresa un valor de tiempo en las respuestas de metadatos. Esto se hizo para permitir mejoras de rendimiento sustanciales. Seguimos teniendo todos los datos necesarios para devolver un valor de tiempo como parte de la respuesta de metadatos y terminaremos de devolver este valor ene l futuro una vez que hayamos resuelto los problemas de rendimiento existentes.' - 'Los límites de recursos que son específicos para procesar ganchos de pre-recepción podrían ocasionar que fallen algunos ganchos de pre-recepción.' - 'Los ajustes de almacenamiento de {% data variables.product.prodname_actions %} no pueden validarse y guardarse en la {% data variables.enterprise.management_console %} cuando se selecciona "Forzar estilo de ruta" y, en su lugar, debe configurarse la utilidad de línea de comando `ghe-actions-precheck`.' - - '{% data variables.product.prodname_ghe_server %} 3.3 instances installed on Azure and provisioned with 32+ CPU cores would fail to launch, due to a bug present in the current Linux kernel. [Updated: 2022-04-08]' + - 'Las instancias de {% data variables.product.prodname_ghe_server %} 3.3 instaladas en Azure y aprovisionadas 32 núcleos de CPU o más fallaron para lanzarse debido a un error presente en el kernel actual de Linux. [Actualizado: 2022-08-04]' diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-3/4.yml b/translations/es-ES/data/release-notes/enterprise-server/3-3/4.yml index 2477e4375b..170e98f407 100644 --- a/translations/es-ES/data/release-notes/enterprise-server/3-3/4.yml +++ b/translations/es-ES/data/release-notes/enterprise-server/3-3/4.yml @@ -21,4 +21,4 @@ sections: - 'El registor de npm del {% data variables.product.prodname_registry %} ya no regresa un valor de tiempo en las respuestas de metadatos. Esto se hizo para permitir mejoras de rendimiento sustanciales. Seguimos teniendo todos los datos necesarios para devolver un valor de tiempo como parte de la respuesta de metadatos y terminaremos de devolver este valor ene l futuro una vez que hayamos resuelto los problemas de rendimiento existentes.' - 'Los límites de recursos que son específicos para procesar ganchos de pre-recepción podrían ocasionar que fallen algunos ganchos de pre-recepción.' - 'Los ajustes de almacenamiento de {% data variables.product.prodname_actions %} no pueden validarse y guardarse en la {% data variables.enterprise.management_console %} cuando se selecciona "Forzar estilo de ruta" y, en su lugar, debe configurarse la utilidad de línea de comando `ghe-actions-precheck`.' - - '{% data variables.product.prodname_ghe_server %} 3.3 instances installed on Azure and provisioned with 32+ CPU cores would fail to launch, due to a bug present in the current Linux kernel. [Updated: 2022-04-08]' + - 'Las instancias de {% data variables.product.prodname_ghe_server %} 3.3 instaladas en Azure y aprovisionadas 32 núcleos de CPU o más fallaron para lanzarse debido a un error presente en el kernel actual de Linux. [Actualizado: 2022-08-04]' diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-3/5.yml b/translations/es-ES/data/release-notes/enterprise-server/3-3/5.yml index 54d04f4e14..2cd7978d8f 100644 --- a/translations/es-ES/data/release-notes/enterprise-server/3-3/5.yml +++ b/translations/es-ES/data/release-notes/enterprise-server/3-3/5.yml @@ -4,7 +4,7 @@ sections: security_fixes: - "ALTA: Se identificó una vulnerabilidad de desbordamiento de integrales en el analizador de lenguaje de marcado de GitHub, la cual pudo haber ocasionado fugas de información potenciales y RCE. Esta vulnerabilidad la reportó Felix Wilhelm, del proyecto Zero de Google, mediante el programa de Recompensas por Errores de GitHub y se le asignó el CVE-2022-24724." bugs: - - Upgrades could sometimes fail if a high-availability replica's clock was out of sync with the primary. + - Las mejoras fallaron algunas veces si el reloj de una réplica de disponibilidad alta se desincronizó con el primario. - 'OAuth Applications created after September 1st, 2020 were not able to use the [Check an Authorization](https://docs.github.com/en/enterprise-server@3.3/rest/reference/apps#check-an-authorization) API endpoint.' known_issues: - Después de haber actualizado a {% data variables.product.prodname_ghe_server %} 3.3, podría que las {% data variables.product.prodname_actions %} no inicien automáticamente. Para resolver este problema, conéctate al aplicativo a través de SSH y ejecuta el comando `ghe-actions-start`. @@ -16,4 +16,4 @@ sections: - El registor de npm del {% data variables.product.prodname_registry %} ya no regresa un valor de tiempo en las respuestas de metadatos. Esto se hizo para permitir mejoras de rendimiento sustanciales. Seguimos teniendo todos los datos necesarios para devolver un valor de tiempo como parte de la respuesta de metadatos y terminaremos de devolver este valor ene l futuro una vez que hayamos resuelto los problemas de rendimiento existentes. - Los límites de recursos que son específicos para procesar ganchos de pre-recepción podrían ocasionar que fallen algunos ganchos de pre-recepción. - 'Los ajustes de almacenamiento de {% data variables.product.prodname_actions %} no pueden validarse y guardarse en la {% data variables.enterprise.management_console %} cuando se selecciona "Forzar estilo de ruta" y, en su lugar, debe configurarse la utilidad de línea de comando `ghe-actions-precheck`.' - - '{% data variables.product.prodname_ghe_server %} 3.3 instances installed on Azure and provisioned with 32+ CPU cores would fail to launch, due to a bug present in the current Linux kernel. [Updated: 2022-04-08]' + - 'Las instancias de {% data variables.product.prodname_ghe_server %} 3.3 instaladas en Azure y aprovisionadas 32 núcleos de CPU o más fallaron para lanzarse debido a un error presente en el kernel actual de Linux. [Actualizado: 2022-08-04]' diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-3/6.yml b/translations/es-ES/data/release-notes/enterprise-server/3-3/6.yml index 5cd4c7c96c..0d67e1969d 100644 --- a/translations/es-ES/data/release-notes/enterprise-server/3-3/6.yml +++ b/translations/es-ES/data/release-notes/enterprise-server/3-3/6.yml @@ -2,48 +2,48 @@ date: '2022-04-04' sections: security_fixes: - 'MEDIA: Se identificó una vulnerabilidad de recorrido de ruta en la consola de administración de {% data variables.product.prodname_ghe_server %}, la cual permitió un puenteo de las protecciones CSRF. Esta vulnerabilidad afectó a todas las versiones de {% data variables.product.prodname_ghe_server %} anteriores a la 3.5 y se corrigió en las versiones 3.1.19, 3.2.11, 3.3.6 y 3.4.1. Esta vulnerabilidad se reportó mediante el programa de recompensas por errores de {% data variables.product.prodname_dotcom %} y se le asignó el CVE-2022-23732.' - - 'MEDIUM: An integer overflow vulnerability was identified in the 1.x branch and the 2.x branch of `yajil` which leads to subsequent heap memory corruption when dealing with large (~2GB) inputs. This vulnerability was reported internally and has been assigned CVE-2022-24795. ' - - 'Support bundles could include sensitive files if {% data variables.product.prodname_actions %} was enabled.' + - 'MEDIA: Se identificó una vulnerabilidad de desbordamiento de números enteros en la rama 1.x y 2.x de `yajil`, lo cual conllevó a una corrupción subsecuente de memoria dinámica al lidiar con entradas grandes (~2GB). Esta vulnerabilidad se reportó internamente y se le asignó el CVE-2022-24795. ' + - 'Los paquetes de soporte podrían incluir archivos sensibles si es que se habilitaron las {% data variables.product.prodname_actions %}.' - 'Los paquetes se actualizaron a las últimas versiones de seguridad.' bugs: - - 'When enabling {% data variables.product.prodname_dependabot %}, an error caused some security advisories to temporarily read as no-longer applicable.' - - 'Minio processes would have high CPU usage if an old configuration option was present after upgrading {% data variables.product.prodname_ghe_server %}.' - - 'The options to enable `TLS 1.0` and `TLS 1.1` in the Privacy settings of the Management Console were shown, although removal of those protocol versions occurred in an earlier release.' - - 'In a HA environment, configuring MSSQL replication could require additional manual steps after enabling {% data variables.product.prodname_actions %} for the first time.' + - 'Al habilitar el {% data variables.product.prodname_dependabot %}, un error ocasionó que algunas asesorías de seguridad se leyeran temporalmente como no aplicables.' + - 'Los procesos de Minio tuvieron un uso alto de CPU si una opción de configuración estuvo presente después de mejorar a {% data variables.product.prodname_ghe_server %}.' + - 'Se mostraron las opciones para habilitar `TLS 1.0` y `TLS 1.1` en los ajustes de privacidad de la consola de administración a pesar de haber eliminado esas versiones de protocolo que ocurrieron en un lanzamiento anterior.' + - 'En un ambiente de HA, el configurar la replicación de MSSQL podría requerir pasos manuales adicionales después de habilitar las {% data variables.product.prodname_actions %} por primera ocasión.' - 'Un subconjunto de archivos de configuración interna se actualiza de forma más confiable después de un hotpatch.' - - 'The `ghe-run-migrations` script would sometimes fail to generate temporary certificate names correctly.' + - 'Algunas veces, el script `ghe-run-migrations` falló en generar nombres de certificados temporales correctamente.' - 'In a cluster environment, Git LFS operations could fail with failed internal API calls that crossed multiple web nodes.' - - 'Pre-receive hooks that used `gpg --import` timed out due to insufficient `syscall` privileges.' - - 'In some cluster topologies, webhook delivery information was not available.' - - 'Elasticsearch health checks would not allow a yellow cluster status when running migrations.' - - 'Repositories would display a non-functional Discussions tab in the web UI.' - - 'Organizations created as a result of a user transforming their user account into an organization were not added to the global enterprise account.' - - 'Links to inaccessible pages were removed.' - - 'The {% data variables.product.prodname_actions %} deployment graph would display an error when rendering a pending job.' - - 'Some instances experienced high CPU usage due to large amounts unnecessary background jobs being queued.' - - 'LDAP user sync jobs would fail when trying to sync GPG keys that had been synced previously.' + - 'Los ganchos de pre-recepción que utilizaron `gpg --import` agotaron su tiempo de espera debido a que no tuvieron los privilegios de `syscall` suficientes.' + - 'En algunas topologías de clúster, no estuvo disponible la información de entrega de webhooks.' + - 'La verificación de salud de Elasticsearch no permitió un estado de clúster amarillo al ejecutar las migraciones.' + - 'Los repositorios mostraron una pestaña de debates sin funcionalidad en la IU web.' + - 'Las organizaciones que se crearon como resultado de que un usuario haya transformado su cuenta de usuario en una organización no se agregaron a la cuenta empresarial global.' + - 'Se eliminaron los enlaces a las páginas inaccesibles.' + - 'La gráfica de despliegue de {% data variables.product.prodname_actions %} mostró un error al procesar un job pendiente.' + - 'Algunas instancias experimentaron un uso de CPU alto debido a que se estaban poniendo en cola cantidades innecesarias de jobs en segundo plano.' + - 'Los jbs de sincronización de usuario de LDAP fallaron al intentar sincronizar claves GPG que se hubieran sincronizado anteriormente.' - 'Following a link to a pull request from the users Pull Request dashboard would result in the repository header not loading.' - 'El agregar a un equipo como revisor para una solicitud de cambios algunas veces muestra la cantidad incorrecta de miembros en un equipo.' - - 'The remove team membership API endpoint would respond with an error when attempting to remove member externally managed via a SCIM Group.' + - 'La terminal de la API de eliminar membrecía de equipo respondió con un error al intentar eliminar a un miembro administrador externamente a través del grupo de SCIM.' - 'Una gran cantidad de usuarios inactivos podría ocasionar que falle una configuración de {% data variables.product.prodname_github_connect %}.' - - 'The "Feature & beta enrollments" page in the Site admin web UI was incorrectly available.' - - 'The "Site admin mode" link in the site footer did not change state when clicked.' + - 'La página de "Características e inscripciones beta" en la IU web del administrador de sitio estuvieron disponibles de forma incorrecta.' + - 'El enlace de "Modo de administrador de sitio" en el pie de página del sitio no cambió de estado cuando se hizo clic sobre este.' - 'The `spokesctl cache-policy rm` command no longer fails with the message `error: failed to delete cache policy`.' changes: - - 'Memcached connection limits were increased to better accommodate large cluster topologies.' - - 'The Dependency Graph API previously ran with a statically defined port.' - - 'The default shard counts for cluster-related Elasticsearch shard settings have been updated.' - - 'When filtering enterprise members by organization role on the "People" page, the text for the dropdown menu items has been improved.' - - 'The “Triage” and “Maintain” team roles are preserved during repository migrations.' - - 'Performance has been improved for web requests made by enterprise owners.' + - 'Los límites de conexión almacenados en la memoria de alto rendimiento se incrementaron para adaptarse mejor a las topologías de clústers grandes.' + - 'La API de la gráfica de dependencias se ejecutó previamente con un puerto definido estáticamente.' + - 'Se actualizó el conteo de fragmentos de los ajustes de fragmentos de la Elasticsearch relacionada con el clúster.' + - 'Cuando se filtraron los miembros de la empresa por rol en la organización en la página de "Personas", el texto de los elementos del menú desplegable se mejoraron.' + - 'Los roles de equipo de "Clasificación" y "Mantenimiento" se preservan durante las migraciones de repositorios.' + - 'Se mejoró el rendimiento para las solicitudes web que hicieron los propietarios de las empresas.' known_issues: - 'Después de haber actualizado a {% data variables.product.prodname_ghe_server %} 3.3, podría que las {% data variables.product.prodname_actions %} no inicien automáticamente. Para resolver este problema, conéctate al aplicativo a través de SSH y ejecuta el comando `ghe-actions-start`.' - 'En una instancia recién configurada de {% data variables.product.prodname_ghe_server %} sin ningún usuario, un atacante podría crear el primer usuario adminsitrador.' - 'Las reglas de cortafuegos personalizadas se eliminan durante el proceso de actualización.' - 'Los archivos rastreados del LFS de Git que se [cargaron mediante la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregaron incorrecta y directamente al repositorio.' - 'Las propuestas no pudieron cerrarse si contenían un permalink a un blob en el mismo repositorio en donde la ruta de archvio del blob era más grande a 255 caracteres.' - - 'When "Users can search GitHub.com" is enabled with {% data variables.product.prodname_github_connect %}, issues in private and internal repositories are not included in {% data variables.product.prodname_dotcom_the_website %} search results.' + - 'Cuando se habilita la opción "Los usuarios pueden buscar en GitHub.com" con las propuestas de {% data variables.product.prodname_github_connect %}, las propuestas en los repositorios internos y privados no se incluyen en los resultados de búsqueda de {% data variables.product.prodname_dotcom_the_website %}.' - 'El registor de npm del {% data variables.product.prodname_registry %} ya no regresa un valor de tiempo en las respuestas de metadatos. Esto se hizo para permitir mejoras de rendimiento sustanciales. Seguimos teniendo todos los datos necesarios para devolver un valor de tiempo como parte de la respuesta de metadatos y terminaremos de devolver este valor ene l futuro una vez que hayamos resuelto los problemas de rendimiento existentes.' - 'Los límites de recursos que son específicos para procesar ganchos de pre-recepción podrían ocasionar que fallen algunos ganchos de pre-recepción.' - 'Los ajustes de almacenamiento de {% data variables.product.prodname_actions %} no pueden validarse y guardarse en la {% data variables.enterprise.management_console %} cuando se selecciona "Forzar estilo de ruta" y, en su lugar, debe configurarse la utilidad de línea de comando `ghe-actions-precheck`.' - - '{% data variables.product.prodname_ghe_server %} 3.3 instances installed on Azure and provisioned with 32+ CPU cores would fail to launch, due to a bug present in the current Linux kernel. [Updated: 2022-04-08]' + - 'Las instancias de {% data variables.product.prodname_ghe_server %} 3.3 instaladas en Azure y aprovisionadas 32 núcleos de CPU o más fallaron para lanzarse debido a un error presente en el kernel actual de Linux. [Actualizado: 2022-08-04]' diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-3/7.yml b/translations/es-ES/data/release-notes/enterprise-server/3-3/7.yml index 7dada12e8c..d29920caba 100644 --- a/translations/es-ES/data/release-notes/enterprise-server/3-3/7.yml +++ b/translations/es-ES/data/release-notes/enterprise-server/3-3/7.yml @@ -3,29 +3,29 @@ sections: security_fixes: - 'Los paquetes se actualizaron a las últimas versiones de seguridad.' bugs: - - 'When a manifest file was deleted from a repository, the manifest would not be removed from the repository''s "Dependency graph" page.' + - 'Cuando se borró un archivo de manifiesto de un repositorio, este no se eliminó de la página de "Gráfica de dependencias" del mismo.' - 'Se resolvió una regresión que pudo haber ocasionado fallas consistentes para recuperar artefactos y descargar archivos de bitácora para {% data variables.product.prodname_actions %}. En algunas circunstancias, dejamos de resolver URL para las comunicaciones internas que utilizaron `localhost` y utilizaron incorrectamente el nombre de host de la instancia en su lugar.' - - 'Upgrading the nodes in a high availability pair with an upgrade package could cause Elasticsearch to enter an inconsistent state in some cases.' - - 'Rotated log files with the extension `.backup` would accumulate in directories containing system logs.' - - 'In some cluster topologies, the command line utilities `ghe-spokesctl` and `ghe-btop` failed to run.' - - 'Elasticsearch indices could be duplicated during a package upgrade, due to an `elasticsearch-upgrade` service running multiple times in parallel.' + - 'El cargar nodos en un par con disponibilidad alta con un paquete de mejora pudo haber causado que Elasticsearch ingresara en un estado inconsistente en algunos casos.' + - 'Se acumularon los archivos de bitácora rotados con la extensión `.backup` enlos directorios que contenían bitácoras de sistema.' + - 'En algunas topologías de clúster, no pudieron ejecutarse las utilidades de línea de comandos `ghe-spokesctl` y `ghe-btop`.' + - 'Los índices de Elastisearch podrían duplicarse durante la mejora de un paquete debido a que el servicio de `elasticsearch-upgrade` se ejecutó varias veces en paralelo.' - 'In the pull request and commit views, rich diffs would fail to load for some files tracked by Git LFS.' - - 'When converting a user account to an organization, if the user account was an owner of the {% data variables.product.prodname_ghe_server %} enterprise account, the converted organization would incorrectly appear in the enterprise owner list.' + - 'Cuando conviertes una cuenta de usuario en una organización, si dicha cuenta fue propietaria de la cuenta empresarial de {% data variables.product.prodname_ghe_server %}, la organización convertida se mostró incorrectamente en la lista de propietarios de la empresa.' - 'El crear un token de OAuth de personificación utilizando la API de REST de administración de empresas dio como resultado un error cuando una integración que coincidió con la ID de aplicación de OAuth ya existía.' - 'The Secret Scanning REST API would return a `500` response code when there were UTF8 characters present in a detected secret.' - - 'Repository cache servers could serve data from non-cache locations even when the data was available in the local cache location.' + - 'Los servidores de caché del repositorio pudieron servir datos de ubicaciones fuera del caché, incluso cuando los datos estuvieron disponibles en la ubicación del caché local.' changes: - 'Los errores de configuración que detienen una ejecución de aplicación de configuraciones ahora son el producto de la terminal adicionalmente a la bitácora de configuración.' - - 'When attempting to cache a value larger than the maximum allowed in Memcached, an error was raised however the key was not reported.' - - 'If {% data variables.product.prodname_GH_advanced_security %} features are enabled on your instance, the performance of background jobs has improved when processing batches for repository contributions.' + - 'Al intentar almacenar en caché un valor que fuera más grande que el máximo permitido en Memcached, se levantó un error pero la clave no se reportó.' + - 'Si se habilitaron las características de {% data variables.product.prodname_GH_advanced_security %} en tu instancia, el rendimiento de los jobs en segundo plano mejoró al procesar los lotes para las contribuciones de repositorio.' known_issues: - 'Después de haber actualizado a {% data variables.product.prodname_ghe_server %} 3.3, podría que las {% data variables.product.prodname_actions %} no inicien automáticamente. Para resolver este problema, conéctate al aplicativo a través de SSH y ejecuta el comando `ghe-actions-start`.' - 'En una instancia recién configurada de {% data variables.product.prodname_ghe_server %} sin ningún usuario, un atacante podría crear el primer usuario adminsitrador.' - 'Las reglas de cortafuegos personalizadas se eliminan durante el proceso de actualización.' - 'Los archivos rastreados del LFS de Git que se [cargaron mediante la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregaron incorrecta y directamente al repositorio.' - 'Las propuestas no pudieron cerrarse si contenían un permalink a un blob en el mismo repositorio en donde la ruta de archvio del blob era más grande a 255 caracteres.' - - 'When "Users can search GitHub.com" is enabled with {% data variables.product.prodname_github_connect %}, issues in private and internal repositories are not included in {% data variables.product.prodname_dotcom_the_website %} search results.' + - 'Cuando se habilita la opción "Los usuarios pueden buscar en GitHub.com" con las propuestas de {% data variables.product.prodname_github_connect %}, las propuestas en los repositorios internos y privados no se incluyen en los resultados de búsqueda de {% data variables.product.prodname_dotcom_the_website %}.' - 'El registor de npm del {% data variables.product.prodname_registry %} ya no regresa un valor de tiempo en las respuestas de metadatos. Esto se hizo para permitir mejoras de rendimiento sustanciales. Seguimos teniendo todos los datos necesarios para devolver un valor de tiempo como parte de la respuesta de metadatos y terminaremos de devolver este valor ene l futuro una vez que hayamos resuelto los problemas de rendimiento existentes.' - 'Los límites de recursos que son específicos para procesar ganchos de pre-recepción podrían ocasionar que fallen algunos ganchos de pre-recepción.' - 'Los ajustes de almacenamiento de {% data variables.product.prodname_actions %} no pueden validarse y guardarse en la {% data variables.enterprise.management_console %} cuando se selecciona "Forzar estilo de ruta" y, en su lugar, debe configurarse la utilidad de línea de comando `ghe-actions-precheck`.' - - '{% data variables.product.prodname_ghe_server %} 3.3 instances installed on Azure and provisioned with 32+ CPU cores would fail to launch, due to a bug present in the current Linux kernel. [Updated: 2022-04-08]' + - 'Las instancias de {% data variables.product.prodname_ghe_server %} 3.3 instaladas en Azure y aprovisionadas 32 núcleos de CPU o más fallaron para lanzarse debido a un error presente en el kernel actual de Linux. [Actualizado: 2022-08-04]' diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-4/0-rc1.yml b/translations/es-ES/data/release-notes/enterprise-server/3-4/0-rc1.yml index d1572ab986..5713f6e979 100644 --- a/translations/es-ES/data/release-notes/enterprise-server/3-4/0-rc1.yml +++ b/translations/es-ES/data/release-notes/enterprise-server/3-4/0-rc1.yml @@ -65,7 +65,7 @@ sections: *Buscar a todos los miembros, equipos y colaboradores que tengan acceso al repositorio. *Ver cuando los miembros tienen tareas de rol mixto, otorgárselas directamente como individuos o indirectamente a través de un equipo. Esto se visualiza a través de una advertencia nueva de "roles mixtos", la cual muestra el rol de nivel más alto que se le otorgó a un usuario si su nivel de permiso es mayor que el de su rol asignado. *Administrar el acceso a los repositorios populares confiablemente, con paginación y menos tiempos de inactividad cuando grupos grandes de usuarios tienen acceso. - - '{% data variables.product.prodname_ghe_server %} 3.4 includes improvements to the repository invitation experience, such as notifications for private repository invites, a UI prompt when visiting a private repository you have a pending invitation for, and a banner on a public repository overview page when there is an pending invitation.' + - '{% data variables.product.prodname_ghe_server %} 3.4 incluye mejoras a la experiencia para invitar a los repositorios, tal como las notificaciones para las invitaciones a los repositorios privados, un mensaje en la IU al visitar un repositorio privado para el cual tienes una invitación pendiente y un letrero en la página de resumen de un repositorio público cuando existe una invitación pendiente.' - 'Ahora puedes utilizar prefijos de un solo carácter para los autoenlaces. Los prefijos de autoenlace ahora también permiten caracteres como `.`, `-`, `_`, `+`, `=`, `:`, `/` y `#`, así como alfanuméricos. Para obtener más información sobre los autoenlaces personalizados, consulta la sección "[Configurar autoenlaces para referenciar recursos externos](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-autolinks-to-reference-external-resources)".' - A `CODE_OF_CONDUCT.md` file in the root of a repository is now highlighted in the "About" sidebar on the repository overview page. - @@ -91,7 +91,7 @@ sections: - heading: 'Cambios a las ramas' notes: - - 'Organization and repository administrators can now trigger webhooks to listen for changes to branch protection rules on their repositories. For more information, see the "[branch_protection_rule](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#branch_protection_rule)" event in the webhooks events and payloads documentation.' + - 'Los administradores de repositorios y organizaciones ahora pueden activar webhooks para escuchar los cambios a las reglas de protección de ramas en sus repositorios. Para obtener más información, consulta el evento de "[branch_protection_rule](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#branch_protection_rule)" en la documentación de las cargas útiles y eventos de webhook.' - Cuando configuras ramas protegidas, ahora puedes requerir que una {% data variables.product.prodname_github_app %} específica proporcione una verificación de estado requerida. Si entonces una aplicación diferente proporciona un estado o si lo hace un usuario a través de un estado de confirmación, se prevendrá la fusión. Esto garantiza que la aplicación correcta valide todos los cambios. Para obtener más información, consulta la "[Bitácora de cambios de {% data variables.product.prodname_dotcom %}](https://github.blog/changelog/2021-12-01-ensure-required-status-checks-provided-by-the-intended-app/)". - Únicamente los usuarios con permisos administrativos son capaces de renombrar las ramas protegidas y modificar las reglas de protección de rama. Anteriormente, con la excepción de la rama predeterminada, cualquier colaborador podía renombrar la rama y, como consecuencia, cualquier regla de protección de rama no comodín que aplicara a dicha rama también se renombraría. Para obtener más información, consulta las secciones "[Renombrar una rama](/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/renaming-a-branch)" y "[Administrar una regla de protección de rama](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule)". - Administrators can now allow only specific users and teams to bypass pull request requirements. For more information, see the "[{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-11-19-allow-bypassing-required-pull-requests/)." @@ -105,7 +105,7 @@ sections: - 'Los flujos de trabajo de {% data variables.product.prodname_actions %} que activa el {% data variables.product.prodname_dependabot %} ahora se enviarán a los secretos del {% data variables.product.prodname_dependabot %}. Ahora puedes hacer extracciones de registros de paquetes privados en tu IC utilizando los mismos secretos que habías configurado para que utilizara el {% data variables.product.prodname_dependabot %}, mejorando la forma en la que las {% data variables.product.prodname_actions %} y el {% data variables.product.prodname_dependabot %} funcionan juntos. Para obtener más información, consulta la sección "[Automatizar el {% data variables.product.prodname_dependabot %} con las {% data variables.product.prodname_actions %}](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/automating-dependabot-with-github-actions)".' - Ahora puedes administrar grupos de ejecutores y ver el estado de tus ejecutores auto-hospedados utilizando páginas nuevas de ejecutores y de grupos de ejecutores en la IU. La página de ajustes de las acciones para tu repositorio u organización ahora muestra una vista de resumen de tus ejecutores y te permite adentrarte en un ejecutor específico para verlo o para ver qué job podría estar ejecutando actualmente. Para obtener más información, consulta la "[bitácora de cambios de {% data variables.product.prodname_dotcom %}](https://github.blog/changelog/2021-09-20-github-actions-experience-refresh-for-the-management-of-self-hosted-runners/)". - 'Los autores de las acciones ahora pueden hacer que su acción se ejecute en Node.js 16 si especifican [`runs.using` cpmo `node16` en el `action.yml` de la acción](/actions/creating-actions/metadata-syntax-for-github-actions#runs-for-javascript-actions). Esto, en conjunto con la compatibilidad existente con Node.js 12; sigue especificando `runs.using: node12` para utilizar el tiempo de ejecución de Node.js 12.' - - 'For manually triggered workflows, {% data variables.product.prodname_actions %} now supports the `choice`, `boolean`, and `environment` input types in addition to the default `string` type. For more information, see "[`on.workflow_dispatch.inputs`](/actions/using-workflows/workflow-syntax-for-github-actions#onworkflow_dispatchinputs)."' + - 'Para los flujos de trabajo que se activan manualmente, {% data variables.product.prodname_actions %} ahora es compatible con los tipos de entrada `choice`, `boolean` y `environment`, adicionalmente al tipo predeterminado `string`. Para obtener más información, consulta "[on.workflow_dispatch.inputs`](/actions/using-workflows/workflow-syntax-for-github-actions#onworkflow_dispatchinputs)".' - Actions written in YAML, also known as composite actions, now support `if` conditionals. This lets you prevent specific steps from executing unless a condition has been met. Like steps defined in workflows, you can use any supported context and expression to create a conditional. - El comportamiento del orden de búsqueda para los ejecutores auto-hospedados cambió para que el ejecutor coincidente que esté disponible primero en cualquier nivel ejecute el job en todos los casos. Esto permite que se envíen jobs mucho más rápido a los ejecutores auto-hospedados, especialmente para las organizaciones y empresas con muchos de ellos. Anteriormente, cuando se ejecutaba un job que requiriera un ejecutor auto-hospedado, {% data variables.product.prodname_actions %} buscaba ejecutores auto-hospedados en el repositorio, organización y empresa, en ese orden. - 'Las etiquetas ejecutoras de los ejecutores auto-hospedados de {% data variables.product.prodname_actions %} ahora se puede listar, agregar y eliminar utilizando la API de REST. Para obtener más información sobre cómo utilizar las API nuevas a nivel de repositorio, organización o empresa, consulta las secciones de "[Repositories](/rest/reference/actions#list-labels-for-a-self-hosted-runner-for-a-repository)", "[Organizations](/rest/reference/actions#add-custom-labels-to-a-self-hosted-runner-for-an-organization)" y "[Enterprises](/rest/reference/enterprise-admin#list-labels-for-a-self-hosted-runner-for-an-enterprise)" en la documentación de la API de REST.' @@ -122,7 +122,7 @@ sections: - El CLI de {% data variables.product.prodname_codeql %} y la extensión de {% data variables.product.prodname_vscode %} ahora son compatibles con la creación de bases de datos y el análisis de código en las máquinas que funcionan con Apple Silicon, tales como Apple M1. Para obtener más información, consulta la "[Bitácora de cambios de {% data variables.product.prodname_dotcom %}](https://github.blog/changelog/2021-11-10-codeql-now-supports-apple-silicon-m1/)". - | La profundidad del análisis del {% data variables.product.prodname_codeql %} se mejoró agregando compatibilidad con más [librerías y marcos de trabajo](https://codeql.github.com/docs/codeql-overview/supported-languages-and-frameworks/) desde el ecosistema de Python. Como resultado, el {% data variables.product.prodname_codeql %} ahora puede detectar aún más fuentes potenciales de datos no confiables, pasos mediante los cuales fluyen los datos y consumidores de datos potencialmente peligrosos en donde podrían terminar estos datos. Esto da como resultado una mejora general de la calidad de las alertas del {% data variables.product.prodname_code_scanning %}. Para obtener más información, consulta la "[Bitácora de cambios de {% data variables.product.prodname_dotcom %}](https://github.blog/changelog/2021-11-24-codeql-code-scanning-now-recognizes-more-python-libraries-and-frameworks/)". - - Code scanning with {% data variables.product.prodname_codeql %} now includes beta support for analyzing code in all common Ruby versions, up to and including 3.02. For more information, see the "[{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-10-27-codeql-code-scanning-adds-beta-support-for-ruby/)." + - El escaneo de código con {% data variables.product.prodname_codeql %} ahora incluye soporte beta para analizar el código en todas las versiones comunes de Ruby, hasta e incluyendo a la 3.02. Para obtener más información, consulta la "[Bitácora de cambios de {% data variables.product.prodname_dotcom %}](https://github.blog/changelog/2021-10-27-codeql-code-scanning-adds-beta-support-for-ruby/)." - | Se han realizado varias mejoras a la API del {% data variables.product.prodname_code_scanning %}: diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-4/0.yml b/translations/es-ES/data/release-notes/enterprise-server/3-4/0.yml index 2947649ba1..128732f1a5 100644 --- a/translations/es-ES/data/release-notes/enterprise-server/3-4/0.yml +++ b/translations/es-ES/data/release-notes/enterprise-server/3-4/0.yml @@ -38,13 +38,13 @@ sections: - heading: Cambios en la administración notes: - - Users can now choose the number of spaces a tab is equal to, by setting their preferred tab size in the "Appearance" settings of their user account. All code with a tab indent will render using the preferred tab size. - - The {% data variables.product.prodname_github_connect %} data connection record now includes a count of the number of active and dormant users and the configured dormancy period. + - Ahora los usuarios pueden elegir la cantidad de espacios que da una tabulación si configuran su tamaño de tabulación en los ajustes de "Apariencia" de sus cuentas de usuario. Todo el código con una sangría de tabulación se interpretará utilizando el tamaño de tabulación preferido. + - El registro de conexión de datos de {% data variables.product.prodname_github_connect %} ahora incluye un conteo de la cantidad de usuarios inactivos y activos y el periodo de inactividad configurado. - You can now give users access to enterprise-specific links by adding custom footers to {% data variables.product.prodname_ghe_server %}. For more information, see "[Configuring custom footers](/admin/configuration/configuring-your-enterprise/configuring-custom-footers)." - heading: Cambios de rendimiento notes: - - WireGuard, used to secure communication between {% data variables.product.prodname_ghe_server %} instances in a High Availability configuration, has been migrated to the Kernel implementation. + - WireGuard, el cual se utiliza para asegurar la comunicación entre las instancias de {% data variables.product.prodname_ghe_server %} en una configuración de disponibilidad alta, se migró a la implementación del Kernel. - heading: Cambios en las notificaciones notes: @@ -170,7 +170,7 @@ sections: - heading: Obsoletización del soporte para XenServer Hypervisor notes: - - Starting in {% data variables.product.prodname_ghe_server %} 3.3, {% data variables.product.prodname_ghe_server %} on XenServer was deprecated and is no longer supported. Please contact [GitHub Support](https://support.github.com) with questions or concerns. + - Desde {% data variables.product.prodname_ghe_server %} 3.3, se obsoletizó el {% data variables.product.prodname_ghe_server %} en XenServer y ya no es compatible. Contacta al [Soporte de GitHub](https://support.github.com) si tienes cualquier duda o pregunta. - heading: Obsoletización de la vista previa de la API de adjuntos de contenido notes: diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-4/1.yml b/translations/es-ES/data/release-notes/enterprise-server/3-4/1.yml index 604e0d4e05..311250658f 100644 --- a/translations/es-ES/data/release-notes/enterprise-server/3-4/1.yml +++ b/translations/es-ES/data/release-notes/enterprise-server/3-4/1.yml @@ -2,51 +2,50 @@ date: '2022-04-04' sections: security_fixes: - 'MEDIA: Se identificó una vulnerabilidad de recorrido de ruta en la consola de administración de {% data variables.product.prodname_ghe_server %}, la cual permitió un puenteo de las protecciones CSRF. Esta vulnerabilidad afectó a todas las versiones de {% data variables.product.prodname_ghe_server %} anteriores a la 3.5 y se corrigió en las versiones 3.1.19, 3.2.11, 3.3.6 y 3.4.1. Esta vulnerabilidad se reportó mediante el programa de recompensas por errores de {% data variables.product.prodname_dotcom %} y se le asignó el CVE-2022-23732.' - - 'MEDIUM: An integer overflow vulnerability was identified in the 1.x branch and the 2.x branch of `yajil` which leads to subsequent heap memory corruption when dealing with large (~2GB) inputs. This vulnerability was reported internally and has been assigned CVE-2022-24795. ' - - 'Support bundles could include sensitive files if {% data variables.product.prodname_actions %} was enabled.' + - 'MEDIA: Se identificó una vulnerabilidad de desbordamiento de números enteros en la rama 1.x y 2.x de `yajil`, lo cual conllevó a una corrupción subsecuente de memoria dinámica al lidiar con entradas grandes (~2GB). Esta vulnerabilidad se reportó internamente y se le asignó el CVE-2022-24795. ' + - 'Los paquetes de soporte podrían incluir archivos sensibles si es que se habilitaron las {% data variables.product.prodname_actions %}.' - 'Los paquetes se actualizaron a las últimas versiones de seguridad.' bugs: - 'A workflow run may not complete if it uses composite-actions.' - - 'When enabling {% data variables.product.prodname_dependabot %}, an error caused some security advisories to temporarily read as no-longer applicable.' - - 'Minio processes would have high CPU usage if an old configuration option was present after upgrading {% data variables.product.prodname_ghe_server %}.' - - 'The options to enable `TLS 1.0` and `TLS 1.1` in the Privacy settings of the Management Console were shown, although removal of those protocol versions occurred in an earlier release.' - - 'In a HA environment, configuring MSSQL replication could require additional manual steps after enabling {% data variables.product.prodname_actions %} for the first time.' - - 'A subset of internal configuration files are more reliably updated after a hotpatch.' - - 'The `ghe-run-migrations` script would sometimes fail to generate temporary certificate names correctly.' - - 'Pre-receive hooks that used `gpg --import` timed out due to insufficient `syscall` privileges.' - - 'In some cluster topologies, webhook delivery information was not available.' - - 'The {% data variables.product.prodname_actions %} deployment graph would display an error when rendering a pending job.' - - 'Elasticsearch health checks would not allow a yellow cluster status when running migrations.' + - 'Al habilitar el {% data variables.product.prodname_dependabot %}, un error ocasionó que algunas asesorías de seguridad se leyeran temporalmente como no aplicables.' + - 'Los procesos de Minio tuvieron un uso alto de CPU si una opción de configuración estuvo presente después de mejorar a {% data variables.product.prodname_ghe_server %}.' + - 'Se mostraron las opciones para habilitar `TLS 1.0` y `TLS 1.1` en los ajustes de privacidad de la consola de administración a pesar de haber eliminado esas versiones de protocolo que ocurrieron en un lanzamiento anterior.' + - 'En un ambiente de HA, el configurar la replicación de MSSQL podría requerir pasos manuales adicionales después de habilitar las {% data variables.product.prodname_actions %} por primera ocasión.' + - 'Un subconjunto de archivos de configuración interna se actualiza de forma más confiable después de un hotpatch.' + - 'Algunas veces, el script `ghe-run-migrations` falló en generar nombres de certificados temporales correctamente.' + - 'Los ganchos de pre-recepción que utilizaron `gpg --import` agotaron su tiempo de espera debido a que no tuvieron los privilegios de `syscall` suficientes.' + - 'En algunas topologías de clúster, no estuvo disponible la información de entrega de webhooks.' + - 'La gráfica de despliegue de {% data variables.product.prodname_actions %} mostró un error al procesar un job pendiente.' + - 'La verificación de salud de Elasticsearch no permitió un estado de clúster amarillo al ejecutar las migraciones.' - 'When using the [Migrations API](/rest/reference/migrations), queued export jobs were not processed.' - - 'Repositories would display a non-functional Discussions tab in the web UI.' - - 'Organizations created as a result of a user transforming their user account into an organization were not added to the global enterprise account.' - - 'LDAP user sync jobs would fail when trying to sync GPG keys that had been synced previously.' - - 'Links to inaccessible pages were removed.' - - 'Some instances experienced high CPU usage due to large amounts unnecessary background jobs being queued.' + - 'Los repositorios mostraron una pestaña de debates sin funcionalidad en la IU web.' + - 'Las organizaciones que se crearon como resultado de que un usuario haya transformado su cuenta de usuario en una organización no se agregaron a la cuenta empresarial global.' + - 'Los jbs de sincronización de usuario de LDAP fallaron al intentar sincronizar claves GPG que se hubieran sincronizado anteriormente.' + - 'Se eliminaron los enlaces a las páginas inaccesibles.' + - 'Algunas instancias experimentaron un uso de CPU alto debido a que se estaban poniendo en cola cantidades innecesarias de jobs en segundo plano.' - 'Empty repositories didnt sync correctly to cache servers.' - - 'Adding a team as a reviewer to a pull request would sometimes show the incorrect number of members on that team.' - - 'The remove team membership API endpoint would respond with an error when attempting to remove member externally managed via a SCIM Group.' - - 'A large number of dormant users could cause a {% data variables.product.prodname_github_connect %} configuration to fail.' - - 'The "Feature & beta enrollments" page in the Site admin web UI was incorrectly available.' - - 'The "Site admin mode" link in the site footer did not change state when clicked.' + - 'El agregar a un equipo como revisor para una solicitud de cambios algunas veces muestra la cantidad incorrecta de miembros en un equipo.' + - 'La terminal de la API de eliminar membrecía de equipo respondió con un error al intentar eliminar a un miembro administrador externamente a través del grupo de SCIM.' + - 'Una gran cantidad de usuarios inactivos podría ocasionar que falle una configuración de {% data variables.product.prodname_github_connect %}.' + - 'La página de "Características e inscripciones beta" en la IU web del administrador de sitio estuvieron disponibles de forma incorrecta.' + - 'El enlace de "Modo de administrador de sitio" en el pie de página del sitio no cambió de estado cuando se hizo clic sobre este.' changes: - - 'Memcached connection limits were increased to better accommodate large cluster topologies.' - - 'The Dependency Graph API previously ran with a statically defined port.' - - 'The default shard counts for cluster-related Elasticsearch shard settings have been updated.' + - 'Los límites de conexión almacenados en la memoria de alto rendimiento se incrementaron para adaptarse mejor a las topologías de clústers grandes.' + - 'La API de la gráfica de dependencias se ejecutó previamente con un puerto definido estáticamente.' + - 'Se actualizó el conteo de fragmentos de los ajustes de fragmentos de la Elasticsearch relacionada con el clúster.' - 'The [Migrations API](/rest/reference/migrations) now generates exports of repositories.' - - 'When filtering enterprise members by organization role on the "People" page, the text for the dropdown menu items has been improved.' - - 'The “Triage” and “Maintain” team roles are preserved during repository migrations.' + - 'Cuando se filtraron los miembros de la empresa por rol en la organización en la página de "Personas", el texto de los elementos del menú desplegable se mejoraron.' + - 'Los roles de equipo de "Clasificación" y "Mantenimiento" se preservan durante las migraciones de repositorios.' - 'Using ghe-migrator or exporting from GitHub.com, an export would not include Pull Request attachments.' - - 'Performance has been improved for web requests made by enterprise owners.' + - 'Se mejoró el rendimiento para las solicitudes web que hicieron los propietarios de las empresas.' known_issues: - 'En una instancia recién configurada de {% data variables.product.prodname_ghe_server %} sin ningún usuario, un atacante podría crear el primer usuario adminsitrador.' - 'Las reglas de cortafuegos personalizadas se eliminan durante el proceso de actualización.' - 'Los archivos rastreados del LFS de Git que se [cargaron mediante la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregaron incorrecta y directamente al repositorio.' - 'Las propuestas no pudieron cerrarse si contenían un permalink a un blob en el mismo repositorio en donde la ruta de archvio del blob era más grande a 255 caracteres.' - - 'When "Users can search GitHub.com" is enabled with {% data variables.product.prodname_github_connect %}, issues in private and internal repositories are not included in {% data variables.product.prodname_dotcom_the_website %} search results.' + - 'Cuando se habilita la opción "Los usuarios pueden buscar en GitHub.com" con las propuestas de {% data variables.product.prodname_github_connect %}, las propuestas en los repositorios internos y privados no se incluyen en los resultados de búsqueda de {% data variables.product.prodname_dotcom_the_website %}.' - 'El registor de npm del {% data variables.product.prodname_registry %} ya no regresa un valor de tiempo en las respuestas de metadatos. Esto se hizo para permitir mejoras de rendimiento sustanciales. Seguimos teniendo todos los datos necesarios para devolver un valor de tiempo como parte de la respuesta de metadatos y terminaremos de devolver este valor ene l futuro una vez que hayamos resuelto los problemas de rendimiento existentes.' - 'Los límites de recursos que son específicos para procesar ganchos de pre-recepción podrían ocasionar que fallen algunos ganchos de pre-recepción.' - - 'Actions services need to be restarted after restoring appliance from backup taken on a different host.' - "Cuando utilizas las aserciones cifradas con {% data variables.product.prodname_ghe_server %} 3.4.0 y 3.4.1, un atributo nuevo de XML `WantAssertionsEncrypted` en el `SPSSODescriptor` contiene un atributo inválido para los metadatos de SAML. Los IdP que consumen esta terminal de metadatos de SAML podrían encontrar errores al validar el modelo XML de los metadatos de SAML. Habrá una corrección disponible en el siguiente lanzamiento de parche. [Actualizado: 2022-04-11]\n\nPara darle una solución a este problema, puedes tomar una de las dos acciones siguientes.\n- Reconfigurar el IdP cargando una copia estática de los metadatos de SAML sin el atributo `WantAssertionsEncrypted`.\n- Copiar los metadatos de SAML, eliminar el atributo `WantAssertionsEncrypted`, hospedarlo en un servidor web y reconfigurar el IdP para que apunte a esa URL.\n" deprecations: - heading: 'Obsoletización de GitHub Enterprise Server 3.0' @@ -57,7 +56,7 @@ sections: - '**{% data variables.product.prodname_ghe_server %} 3.1 se descontinuará el 3 de junio de 2022**. Eso significa que no se harán lanzamientos de parche, aún para los problemas de seguridad críticos, después de esta fecha. Para obtener un rendimiento mejor, una seguridad mejorada y características nuevas, [actualiza a la última versión de {% data variables.product.prodname_ghe_server %}](/enterprise-server@3.4/admin/enterprise-management/upgrading-github-enterprise-server) tan pronto te sea posible.' - heading: 'Obsoletización del soporte para XenServer Hypervisor' notes: - - 'Starting in {% data variables.product.prodname_ghe_server %} 3.3, {% data variables.product.prodname_ghe_server %} on XenServer was deprecated and is no longer supported. Please contact [GitHub Support](https://support.github.com) with questions or concerns.' + - 'Desde {% data variables.product.prodname_ghe_server %} 3.3, se obsoletizó el {% data variables.product.prodname_ghe_server %} en XenServer y ya no es compatible. Contacta al [Soporte de GitHub](https://support.github.com) si tienes cualquier duda o pregunta.' - heading: 'Obsoletización de la vista previa de la API de adjuntos de contenido' notes: - 'Debido a su poco uso, la vista previa de la API de referencias de contenido se hizo obsoleta en {% data variables.product.prodname_ghe_server %} 3.4. Anteriormente, se podía acceder a la API con el encabezado `corsair-preview`. Los usuarios pueden seguir navegando hacia URL externas sin esta API. Cualquier uso registrado de la API de referencias de contenido ya no recibirá una notificación de webhook para las URL de tus dominios registrados y ya no devolveremos códigos de respuesta válidos para los intentos de actualización a los adjuntos de contenido existentes.' diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-4/2.yml b/translations/es-ES/data/release-notes/enterprise-server/3-4/2.yml index 0a2abcc482..94f0cbf376 100644 --- a/translations/es-ES/data/release-notes/enterprise-server/3-4/2.yml +++ b/translations/es-ES/data/release-notes/enterprise-server/3-4/2.yml @@ -3,30 +3,29 @@ sections: security_fixes: - 'Los paquetes se actualizaron a las últimas versiones de seguridad.' bugs: - - 'Resolved a regression that could lead to consistent failures to retrieve artifacts and download log archives for {% data variables.product.prodname_actions %}. In some circumstances we stopped resolving URLs for internal communications that used `localhost`, and instead incorrectly used the instance hostname.' - - 'When a manifest file was deleted from a repository, the manifest would not be removed from the repository''s "Dependency graph" page.' - - 'Upgrading the nodes in a high availability pair with an upgrade package could cause Elasticsearch to enter an inconsistent state in some cases.' - - 'Rotated log files with the extension `.backup` would accumulate in directories containing system logs.' - - 'In some cluster topologies, the command line utilities `ghe-spokesctl` and `ghe-btop` failed to run.' - - 'Elasticsearch indices could be duplicated during a package upgrade, due to an `elasticsearch-upgrade` service running multiple times in parallel.' - - 'Repository cache servers could serve data from non-cache locations even when the data was available in the local cache location.' - - 'When converting a user account to an organization, if the user account was an owner of the {% data variables.product.prodname_ghe_server %} enterprise account, the converted organization would incorrectly appear in the enterprise owner list.' + - 'Se resolvió una regresión que pudo haber ocasionado fallas consistentes para recuperar artefactos y descargar archivos de bitácora para {% data variables.product.prodname_actions %}. En algunas circunstancias, dejamos de resolver URL para las comunicaciones internas que utilizaron `localhost` y utilizaron incorrectamente el nombre de host de la instancia en su lugar.' + - 'Cuando se borró un archivo de manifiesto de un repositorio, este no se eliminó de la página de "Gráfica de dependencias" del mismo.' + - 'El cargar nodos en un par con disponibilidad alta con un paquete de mejora pudo haber causado que Elasticsearch ingresara en un estado inconsistente en algunos casos.' + - 'Se acumularon los archivos de bitácora rotados con la extensión `.backup` enlos directorios que contenían bitácoras de sistema.' + - 'En algunas topologías de clúster, no pudieron ejecutarse las utilidades de línea de comandos `ghe-spokesctl` y `ghe-btop`.' + - 'Los índices de Elastisearch podrían duplicarse durante la mejora de un paquete debido a que el servicio de `elasticsearch-upgrade` se ejecutó varias veces en paralelo.' + - 'Los servidores de caché del repositorio pudieron servir datos de ubicaciones fuera del caché, incluso cuando los datos estuvieron disponibles en la ubicación del caché local.' + - 'Cuando conviertes una cuenta de usuario en una organización, si dicha cuenta fue propietaria de la cuenta empresarial de {% data variables.product.prodname_ghe_server %}, la organización convertida se mostró incorrectamente en la lista de propietarios de la empresa.' - 'The `/stafftools/users/ip_addresses/:address` page responded with a `500 Internal Server Error` when attempting to display the page for an IPv6 address.' - - 'Creating an impersonation OAuth token using the Enterprise Administration REST API resulted in an error when an integration matching the OAuth Application ID already existed.' + - 'El crear un token de OAuth de personificación utilizando la API de REST de administración de empresas dio como resultado un error cuando una integración que coincidió con la ID de aplicación de OAuth ya existía.' - "Cuando utilizas las aserciones cifradas con {% data variables.product.prodname_ghe_server %} 3.4.0 y 3.4.1, un atributo nuevo de XML `WantAssertionsEncrypted` en el `SPSSODescriptor` contiene un atributo inválido para los metadatos de SAML. Los IdP que consumen esta terminal de metadatos de SAML podrían encontrar errores al validar el modelo XML de los metadatos de SAML. Habrá una corrección disponible en el siguiente lanzamiento de parche. [Actualizado: 2022-04-11]\n\nPara darle una solución a este problema, puedes tomar una de las dos acciones siguientes.\n- Reconfigurar el IdP cargando una copia estática de los metadatos de SAML sin el atributo `WantAssertionsEncrypted`.\n- Copiar los metadatos de SAML, eliminar el atributo `WantAssertionsEncrypted`, hospedarlo en un servidor web y reconfigurar el IdP para que apunte a esa URL.\n" changes: - 'Added support for replica domain names that are more than 63 characters.' - - 'Configuration errors that halt a config apply run are now output to the terminal in addition to the configuration log.' - - 'If {% data variables.product.prodname_GH_advanced_security %} features are enabled on your instance, the performance of background jobs has improved when processing batches for repository contributions.' + - 'Los errores de configuración que detienen una ejecución de aplicación de configuraciones ahora son el producto de la terminal adicionalmente a la bitácora de configuración.' + - 'Si se habilitaron las características de {% data variables.product.prodname_GH_advanced_security %} en tu instancia, el rendimiento de los jobs en segundo plano mejoró al procesar los lotes para las contribuciones de repositorio.' known_issues: - 'En una instancia recién configurada de {% data variables.product.prodname_ghe_server %} sin ningún usuario, un atacante podría crear el primer usuario adminsitrador.' - 'Las reglas de cortafuegos personalizadas se eliminan durante el proceso de actualización.' - 'Los archivos rastreados del LFS de Git que se [cargaron mediante la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregaron incorrecta y directamente al repositorio.' - 'Las propuestas no pudieron cerrarse si contenían un permalink a un blob en el mismo repositorio en donde la ruta de archvio del blob era más grande a 255 caracteres.' - - 'When "Users can search GitHub.com" is enabled with {% data variables.product.prodname_github_connect %}, issues in private and internal repositories are not included in {% data variables.product.prodname_dotcom_the_website %} search results.' + - 'Cuando se habilita la opción "Los usuarios pueden buscar en GitHub.com" con las propuestas de {% data variables.product.prodname_github_connect %}, las propuestas en los repositorios internos y privados no se incluyen en los resultados de búsqueda de {% data variables.product.prodname_dotcom_the_website %}.' - 'El registor de npm del {% data variables.product.prodname_registry %} ya no regresa un valor de tiempo en las respuestas de metadatos. Esto se hizo para permitir mejoras de rendimiento sustanciales. Seguimos teniendo todos los datos necesarios para devolver un valor de tiempo como parte de la respuesta de metadatos y terminaremos de devolver este valor ene l futuro una vez que hayamos resuelto los problemas de rendimiento existentes.' - 'Los límites de recursos que son específicos para procesar ganchos de pre-recepción podrían ocasionar que fallen algunos ganchos de pre-recepción.' - - 'Actions services need to be restarted after restoring appliance from backup taken on a different host.' - "Cuando utilizas las aserciones cifradas con {% data variables.product.prodname_ghe_server %} 3.4.0 y 3.4.1, un atributo nuevo de XML `WantAssertionsEncrypted` en el `SPSSODescriptor` contiene un atributo inválido para los metadatos de SAML. Los IdP que consumen esta terminal de metadatos de SAML podrían encontrar errores al validar el modelo XML de los metadatos de SAML. Habrá una corrección disponible en el siguiente lanzamiento de parche. [Actualizado: 2022-04-11]\n\nPara darle una solución a este problema, puedes tomar una de las dos acciones siguientes.\n- Reconfigurar el IdP cargando una copia estática de los metadatos de SAML sin el atributo `WantAssertionsEncrypted`.\n- Copiar los metadatos de SAML, eliminar el atributo `WantAssertionsEncrypted`, hospedarlo en un servidor web y reconfigurar el IdP para que apunte a esa URL.\n" deprecations: - heading: 'Obsoletización de GitHub Enterprise Server 3.0' @@ -37,7 +36,7 @@ sections: - '**{% data variables.product.prodname_ghe_server %} 3.1 se descontinuará el 3 de junio de 2022**. Eso significa que no se harán lanzamientos de parche, aún para los problemas de seguridad críticos, después de esta fecha. Para obtener un rendimiento mejor, una seguridad mejorada y características nuevas, [actualiza a la última versión de {% data variables.product.prodname_ghe_server %}](/enterprise-server@3.4/admin/enterprise-management/upgrading-github-enterprise-server) tan pronto te sea posible.' - heading: 'Obsoletización del soporte para XenServer Hypervisor' notes: - - 'Starting in {% data variables.product.prodname_ghe_server %} 3.3, {% data variables.product.prodname_ghe_server %} on XenServer was deprecated and is no longer supported. Please contact [GitHub Support](https://support.github.com) with questions or concerns.' + - 'Desde {% data variables.product.prodname_ghe_server %} 3.3, se obsoletizó el {% data variables.product.prodname_ghe_server %} en XenServer y ya no es compatible. Contacta al [Soporte de GitHub](https://support.github.com) si tienes cualquier duda o pregunta.' - heading: 'Obsoletización de la vista previa de la API de adjuntos de contenido' notes: - 'Debido a su poco uso, la vista previa de la API de referencias de contenido se hizo obsoleta en {% data variables.product.prodname_ghe_server %} 3.4. Anteriormente, se podía acceder a la API con el encabezado `corsair-preview`. Los usuarios pueden seguir navegando hacia URL externas sin esta API. Cualquier uso registrado de la API de referencias de contenido ya no recibirá una notificación de webhook para las URL de tus dominios registrados y ya no devolveremos códigos de respuesta válidos para los intentos de actualización a los adjuntos de contenido existentes.' diff --git a/translations/es-ES/data/reusables/actions/self-hosted-runner-configure-runner-group.md b/translations/es-ES/data/reusables/actions/self-hosted-runner-configure-runner-group.md index 7a6643338c..7e009d343d 100644 --- a/translations/es-ES/data/reusables/actions/self-hosted-runner-configure-runner-group.md +++ b/translations/es-ES/data/reusables/actions/self-hosted-runner-configure-runner-group.md @@ -1 +1 @@ -1. In the {% ifversion fpt or ghes > 3.1 or ghae or ghec %}"Runners"{% else %}"Self-hosted runners"{% endif %} section of the settings page, next to the runner group you'd like to configure, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **Edit name and [organization|repository] access**. ![Administrar permisos del repositorio](/assets/images/help/settings/actions-runner-manage-permissions.png) \ No newline at end of file +1. En la sección de {% ifversion fpt or ghes > 3.1 or ghae or ghec %}"Ejecutores"{% else %}"Ejecutores auto-hospedados"{% endif %} de la página de ajustes, junto al grupo de ejecutores que te gustaría configurar, haz clic en {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} y luego en **Editar nombre y acceso a la [organización|repositorio]**. ![Administrar permisos del repositorio](/assets/images/help/settings/actions-runner-manage-permissions.png) \ No newline at end of file diff --git a/translations/es-ES/data/reusables/actions/self-hosted-runner-description.md b/translations/es-ES/data/reusables/actions/self-hosted-runner-description.md index e865326637..31171d1a80 100644 --- a/translations/es-ES/data/reusables/actions/self-hosted-runner-description.md +++ b/translations/es-ES/data/reusables/actions/self-hosted-runner-description.md @@ -1 +1 @@ -{% ifversion fpt or ghec %}Self-hosted runners offer more control of hardware, operating system, and software tools than {% data variables.product.prodname_dotcom %}-hosted runners provide. {% endif %}With self-hosted runners, you can create custom hardware configurations that meet your needs with processing power or memory to run larger jobs, install software available on your local network, and choose an operating system{% ifversion fpt or ghec %} not offered by {% data variables.product.prodname_dotcom %}-hosted runners{% endif %}. +{% ifversion fpt or ghec %}Self-hosted runners offer more control of hardware, operating system, and software tools than {% data variables.product.prodname_dotcom %}-hosted runners provide. {% endif %}Con los ejecutores auto-hospedados, puedes crear configuraciones de hardware personalizado que cumplan con tus necesidades con el procesamiento de poder o memoria para ejecutar jobs más grandes, instalar el software disponible en tu red local y elegir un sistema operativo{% ifversion fpt or ghec %} que no ofrezcan los ejecutores que hospeda {% data variables.product.prodname_dotcom %}{% endif %}. diff --git a/translations/es-ES/data/reusables/actions/settings-ui/settings-actions-general.md b/translations/es-ES/data/reusables/actions/settings-ui/settings-actions-general.md index 2e08467c90..bc1137b623 100644 --- a/translations/es-ES/data/reusables/actions/settings-ui/settings-actions-general.md +++ b/translations/es-ES/data/reusables/actions/settings-ui/settings-actions-general.md @@ -1,2 +1,2 @@ -{% comment %}This reusable is only to be used in other repo/org/enterprise setting reusables.{%- endcomment -%} +{% comment %}Este reutilizable solo puede usarse en otro repositorio/organización/empresa ajustando los reutilizables.{%- endcomment -%} 1. In the left sidebar, click {% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %}{% octicon "play" aria-label="The {% data variables.product.prodname_actions %} icon" %} **Actions**, then click **General**.{% else %}**Actions**.{% endif %} \ No newline at end of file diff --git a/translations/es-ES/data/reusables/actions/supported-github-runners.md b/translations/es-ES/data/reusables/actions/supported-github-runners.md index 39f249523a..097ab8c181 100644 --- a/translations/es-ES/data/reusables/actions/supported-github-runners.md +++ b/translations/es-ES/data/reusables/actions/supported-github-runners.md @@ -50,6 +50,17 @@ Ubuntu 18.04 +macOS Monterey 12 + + +macos-12 + + +macOS 12 is currently in public beta. + + + + macOS Big Sur 11 diff --git a/translations/es-ES/data/reusables/audit_log/audit-log-action-categories.md b/translations/es-ES/data/reusables/audit_log/audit-log-action-categories.md index 9129d31bc8..b3b9159cdc 100644 --- a/translations/es-ES/data/reusables/audit_log/audit-log-action-categories.md +++ b/translations/es-ES/data/reusables/audit_log/audit-log-action-categories.md @@ -15,7 +15,7 @@ | `business` | Contains activities related to business settings for an enterprise. {%- endif %} {%- ifversion ghec or ghes or ghae %} -| `business` | Contains activities related to business settings for an enterprise. +| `business` | Contiene actividades relacionadas con los ajustes de negocio para una empresa. {%- endif %} {%- if secret-scanning-audit-log-custom-patterns %} | `business_secret_scanning_custom_pattern` | Contains activities related to custom patterns for secret scanning in an enterprise. @@ -26,7 +26,7 @@ {%- endif %} | `commit_comment` | Contains activities related to updating or deleting commit comments. {%- ifversion ghes %} -| `config_entry` | Contains activities related to configuration settings. These events are only visible in the site admin audit log. +| `config_entry` | Contains activities related to configuration settings. Estos eventos solo se pueden ver en la bitácora de auditoría del administrador de sitio. {%- endif %} {%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-4864 %} | `dependabot_alerts` | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot_alerts %} in existing repositories. Para obtener más información, consulta la sección "[Acerca de las alertas para las dependencias vulnerables](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)". | `dependabot_alerts_new_repos` | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot_alerts %} in new repositories created in the organization. | `dependabot_repository_access` | Contains activities related to which private repositories in an organization {% data variables.product.prodname_dependabot %} is allowed to access. @@ -65,7 +65,7 @@ | `members_can_delete_repos` | Contains activities related to enabling or disabling repository creation for an organization. {%- endif %} {%- ifversion fpt or ghec %} -| `members_can_view_dependency_insights` | Contains organization-level configuration activities allowing organization members to view dependency insights. | `migration` | Contains activities related to transferring data from a *source* location (such as a {% data variables.product.prodname_dotcom_the_website %} organization or a {% data variables.product.prodname_ghe_server %} instance) to a *target* {% data variables.product.prodname_ghe_server %} instance. +| `members_can_view_dependency_insights` | Contains organization-level configuration activities allowing organization members to view dependency insights. | `migration` | Contiene actividades relacionadas con transferir datos desde una ubicación *origen* (Tal como una organización de {% data variables.product.prodname_dotcom_the_website %} o una instancia de {% data variables.product.prodname_ghe_server %}) a una instancia *destino* de {% data variables.product.prodname_ghe_server %}. {%- endif %} | `oauth_access` | Contains activities related to OAuth access tokens. | `oauth_application` | Contains activities related to OAuth Apps. {%- ifversion fpt or ghec %} @@ -76,7 +76,7 @@ | `org_credential_authorization` | Contains activities related to authorizing credentials for use with SAML single sign-on. {%- endif %} {%- if secret-scanning-audit-log-custom-patterns %} -| `org_secret_scanning_custom_pattern` | Contains activities related to custom patterns for secret scanning in an organization. For more information, see "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)." | `org.secret_scanning_push_protection` | Contains activities related to secret scanning custom patterns in an organization. For more information, see "[Protecting pushes with secret scanning](/code-security/secret-scanning/protecting-pushes-with-secret-scanning)." +| `org_secret_scanning_custom_pattern` | Contains activities related to custom patterns for secret scanning in an organization. Para obtener más información, consulta la sección "[Definir los patrones personalizados para el escaneo de secretos](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)". | `org.secret_scanning_push_protection` | Contains activities related to secret scanning custom patterns in an organization. Para obtener más información, consulta la sección "[Proteger las subidas de información con el escaneo de secretos](/code-security/secret-scanning/protecting-pushes-with-secret-scanning)". {%- endif %} | `organization_default_label` | Contains activities related to default labels for repositories in an organization. {%- ifversion fpt or ghec or ghes > 3.1 %} @@ -111,7 +111,7 @@ | `repository_secret_scanning` | Contains repository-level activities related to secret scanning. Para obtener más información, consulta la sección "[Acerca del escaneo de secretos"](/github/administering-a-repository/about-secret-scanning). {%- endif %} {%- if secret-scanning-audit-log-custom-patterns %} -| `repository_secret_scanning_custom_pattern` | Contains activities related to secret scanning custom patterns in a repository. For more information, see "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)." |{% endif %}{% if secret-scanning-audit-log-custom-patterns %}| | `repository_secret_scanning_push_protection` | Contains activities related to secret scanning custom patterns in a repository. For more information, see "[Protecting pushes with secret scanning](/code-security/secret-scanning/protecting-pushes-with-secret-scanning)." +| `repository_secret_scanning_custom_pattern` | Contains activities related to secret scanning custom patterns in a repository. Para obtener más información, consulta la sección "[Definir los patrones personalizados para el escaneo de secretos](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)". |{% endif %}{% if secret-scanning-audit-log-custom-patterns %}| | `repository_secret_scanning_push_protection` | Contains activities related to secret scanning custom patterns in a repository. Para obtener más información, consulta la sección "[Proteger las subidas de información con el escaneo de secretos](/code-security/secret-scanning/protecting-pushes-with-secret-scanning)". {%- endif %} {%- ifversion fpt or ghec %} | `repository_visibility_change` | Contains activities related to allowing organization members to change repository visibilities for the organization. diff --git a/translations/es-ES/data/reusables/billing/license-statuses.md b/translations/es-ES/data/reusables/billing/license-statuses.md index 3b307eb69e..5b9973dc16 100644 --- a/translations/es-ES/data/reusables/billing/license-statuses.md +++ b/translations/es-ES/data/reusables/billing/license-statuses.md @@ -1,5 +1,5 @@ {% ifversion ghec %} -If your license includes {% data variables.product.prodname_vss_ghe %}, you can identify whether a personal account on {% data variables.product.prodname_dotcom_the_website %} has successfully matched with a {% data variables.product.prodname_vs %} subscriber by downloading the CSV file that contains additional license details. The license status will be one of the following. +Si tu licencia incluye {% data variables.product.prodname_vss_ghe %}, puedes identificar si una cuenta personal de {% data variables.product.prodname_dotcom_the_website %} coincidió exitosamente con un suscriptor de {% data variables.product.prodname_vs %} si descargas el archivo de CSV que contiene detalles de licencia adicionales. The license status will be one of the following. - "Matched": The personal account on {% data variables.product.prodname_dotcom_the_website %} is linked with a {% data variables.product.prodname_vs %} subscriber. - "Pending Invitation": An invitation was sent to a {% data variables.product.prodname_vs %} subscriber, but the subscriber has not accepted the invitation. - Blank: There is no {% data variables.product.prodname_vs %} association to consider for the personal account on {% data variables.product.prodname_dotcom_the_website %}. diff --git a/translations/es-ES/data/reusables/codespaces/billing-for-prebuilds.md b/translations/es-ES/data/reusables/codespaces/billing-for-prebuilds.md index 9b7dd7c7e4..c8d39ee7f1 100644 --- a/translations/es-ES/data/reusables/codespaces/billing-for-prebuilds.md +++ b/translations/es-ES/data/reusables/codespaces/billing-for-prebuilds.md @@ -2,6 +2,6 @@ By default, a {% data variables.product.prodname_actions %} workflow is triggere If you are an organization owner, you can track usage of prebuild workflows by downloading a {% data variables.product.prodname_actions %} usage report for your organization. You can identify workflow runs for prebuilds by filtering the CSV output to only include the workflow called "Create Codespaces Prebuilds." Para obtener más información, consulta la sección "[Visualizar tu uso de {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions/viewing-your-github-actions-usage#viewing-github-actions-usage-for-your-organization)". -To reduce consumption of Actions minutes, you can set a prebuild template to be updated only when you make a change to your dev container configuration files, or only on a custom schedule. For more information, see "[Configuring prebuilds](/codespaces/prebuilding-your-codespaces/configuring-prebuilds#configuring-a-prebuild)." +To reduce consumption of Actions minutes, you can set a prebuild template to be updated only when you make a change to your dev container configuration files, or only on a custom schedule. Para obtener más información, consulta la sección "[Configurar las precompilaciones](/codespaces/prebuilding-your-codespaces/configuring-prebuilds#configuring-a-prebuild)". While {% data variables.product.prodname_codespaces %} prebuilds is in beta there is no charge for storage of templates. When prebuilds become generally available, you will be billed for storing prebuild templates for each prebuild configuration in each region selected for that configuration. diff --git a/translations/es-ES/data/reusables/codespaces/codespaces-org-policies.md b/translations/es-ES/data/reusables/codespaces/codespaces-org-policies.md new file mode 100644 index 0000000000..5fba4d095d --- /dev/null +++ b/translations/es-ES/data/reusables/codespaces/codespaces-org-policies.md @@ -0,0 +1,3 @@ +1. In the "Code, planning, and automation" section of the sidebar, select **{% octicon "codespaces" aria-label="The codespaces icon" %} {% data variables.product.prodname_codespaces %}** then click **Policies**. +1. En la página de "Políticas de los codespaces", haz clic en **Crear política**. +1. Ingresa un nombre para tu política nueva. \ No newline at end of file diff --git a/translations/es-ES/data/reusables/codespaces/codespaces-policy-targets.md b/translations/es-ES/data/reusables/codespaces/codespaces-policy-targets.md new file mode 100644 index 0000000000..2ce9cba031 --- /dev/null +++ b/translations/es-ES/data/reusables/codespaces/codespaces-policy-targets.md @@ -0,0 +1,11 @@ +1. En el área de "Cambiar destino de la política", haz clic en el botón desplegable. +1. Elige y asea **Todos los repositorios** o **Repositorios seleccionados** para determinar a cuáles aplicará esta política. +1. Si eliges **Repositorios seleccionados**: + 1. Da clic en {% octicon "gear" aria-label="The settings icon" %}. + + ![Editar los ajustes para la política](/assets/images/help/codespaces/policy-edit.png) + + 2. Selecciona los repositorios a los cuales quieres que aplique esta política. + 3. En la parte inferior de la lista de repositorios, haz clic en **Seleccionar repositorios**. + + ![Selecciona los repositorios para esta política](/assets/images/help/codespaces/policy-select-repos.png) diff --git a/translations/es-ES/data/reusables/discussions/starting-a-poll.md b/translations/es-ES/data/reusables/discussions/starting-a-poll.md index 0ecfc99b37..d3e097f3b9 100644 --- a/translations/es-ES/data/reusables/discussions/starting-a-poll.md +++ b/translations/es-ES/data/reusables/discussions/starting-a-poll.md @@ -6,4 +6,4 @@ 1. Type a question for your poll. ![Screenshot showing text fields for the poll's question](/assets/images/help/discussions/new-poll-question.png) 1. Type at least two options for your poll. ![Screenshot showing text fields for the poll's options](/assets/images/help/discussions/new-poll-options.png) 1. Optionally, to add a extra poll options, click **Add an option**. ![Screenshot showing "Add an option" button](/assets/images/help/discussions/new-poll-add-option.png) -1. Click **Start poll**. ![Screenshot showing the "Start poll" button](/assets/images/help/discussions/new-poll-start-poll-button.png) \ No newline at end of file +1. Click **Start poll**. ![Captura de pantalla que muestra el botón "Iniciar encuesta"](/assets/images/help/discussions/new-poll-start-poll-button.png) \ No newline at end of file diff --git a/translations/es-ES/data/reusables/enterprise_user_management/alternatively-enable-external-authentication.md b/translations/es-ES/data/reusables/enterprise_user_management/alternatively-enable-external-authentication.md index 70b8f88726..61161aed3b 100644 --- a/translations/es-ES/data/reusables/enterprise_user_management/alternatively-enable-external-authentication.md +++ b/translations/es-ES/data/reusables/enterprise_user_management/alternatively-enable-external-authentication.md @@ -1 +1 @@ -Alternatively, you can configure external authentication for {% data variables.product.product_location %}. If you use external authentication, you must invite people to use your instance through your authentication provider. For more information, see "[About authentication for your enterprise](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise#external-authentication)." +Alternatively, you can configure external authentication for {% data variables.product.product_location %}. If you use external authentication, you must invite people to use your instance through your authentication provider. Para obtener más información, consulta la sección "[Acerca de la autenticación para tu empresa](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise#external-authentication)". diff --git a/translations/es-ES/data/reusables/enterprise_user_management/built-in-authentication-option.md b/translations/es-ES/data/reusables/enterprise_user_management/built-in-authentication-option.md index a173386b02..d46273968c 100644 --- a/translations/es-ES/data/reusables/enterprise_user_management/built-in-authentication-option.md +++ b/translations/es-ES/data/reusables/enterprise_user_management/built-in-authentication-option.md @@ -1 +1 @@ -Opcionalmente, para permitir que las personas sin una cuenta en tu sistema de autenticación externa inicien sesión con una autenticación integrada, selecciona **Permitir la autenticación integrada**. For more information, see "[Allowing built-in authentication for users outside your provider](/admin/identity-and-access-management/managing-iam-for-your-enterprise/allowing-built-in-authentication-for-users-outside-your-provider)." +Opcionalmente, para permitir que las personas sin una cuenta en tu sistema de autenticación externa inicien sesión con una autenticación integrada, selecciona **Permitir la autenticación integrada**. Para obtener más información, consulta la sección "[Permitir la autenticación integrada para los usuarios fuera de tu proveedor](/admin/identity-and-access-management/managing-iam-for-your-enterprise/allowing-built-in-authentication-for-users-outside-your-provider)". diff --git a/translations/es-ES/data/reusables/enterprise_user_management/built-in-authentication.md b/translations/es-ES/data/reusables/enterprise_user_management/built-in-authentication.md index 8ae507793d..9168f089f1 100644 --- a/translations/es-ES/data/reusables/enterprise_user_management/built-in-authentication.md +++ b/translations/es-ES/data/reusables/enterprise_user_management/built-in-authentication.md @@ -1 +1 @@ -Si quieres permitir la autenticación de algunas personas que no tienen una cuenta en tu proveedor de autenticación externo, puedes permitir una reversión a las cuentas locales en {% data variables.product.product_location %}. For more information, see "[Allowing built-in authentication for users outside your provider](/admin/identity-and-access-management/managing-iam-for-your-enterprise/allowing-built-in-authentication-for-users-outside-your-provider)." +Si quieres permitir la autenticación de algunas personas que no tienen una cuenta en tu proveedor de autenticación externo, puedes permitir una reversión a las cuentas locales en {% data variables.product.product_location %}. Para obtener más información, consulta la sección "[Permitir la autenticación integrada para los usuarios fuera de tu proveedor](/admin/identity-and-access-management/managing-iam-for-your-enterprise/allowing-built-in-authentication-for-users-outside-your-provider)". diff --git a/translations/es-ES/data/reusables/gated-features/dependency-vulnerable-calls.md b/translations/es-ES/data/reusables/gated-features/dependency-vulnerable-calls.md index 209f8249d1..1f6773128e 100644 --- a/translations/es-ES/data/reusables/gated-features/dependency-vulnerable-calls.md +++ b/translations/es-ES/data/reusables/gated-features/dependency-vulnerable-calls.md @@ -8,6 +8,6 @@ Detection of vulnerable calls is included in {% data variables.product.product_n Detection of vulnerable calls is available for organization-owned repositories in {% data variables.product.product_name %}. Esta característica requiere una licencia para la {% data variables.product.prodname_GH_advanced_security %}. {%- elsif ghae-issue-6076 %} -Detection of vulnerable calls is available for organization-owned repositories in {% data variables.product.product_name %}. Esta es una característica de la {% data variables.product.prodname_GH_advanced_security %} (gratuita durante el lanzamiento beta). +La detección de llamadas vulnerables está disponible para los repositorios que pertenecen a organizaciones de {% data variables.product.product_name %}. Esta es una característica de la {% data variables.product.prodname_GH_advanced_security %} (gratuita durante el lanzamiento beta). {%- endif %} {% data reusables.advanced-security.more-info-ghas %} diff --git a/translations/es-ES/data/reusables/gated-features/security-center.md b/translations/es-ES/data/reusables/gated-features/security-center.md index 1b41c79ffb..b4b60eeba8 100644 --- a/translations/es-ES/data/reusables/gated-features/security-center.md +++ b/translations/es-ES/data/reusables/gated-features/security-center.md @@ -3,4 +3,4 @@ El resumen de seguridad de tu organización se encuentra disponible si tienes un {% elsif ghec or ghes %} El resumen de seguridad de tu organización se encuentra disponible si tienes una licencia para la {% data variables.product.prodname_GH_advanced_security %}. {% data reusables.advanced-security.more-info-ghas %} {% elsif fpt %} -El resumen de seguridad se encuentra disponible para las organizaciones que utilizan {% data variables.product.prodname_enterprise %} y tienen una licencia para {% data variables.product.prodname_GH_advanced_security %}. For more information, see "[About {% data variables.product.prodname_GH_advanced_security %}](/get-started/learning-about-github/about-github-advanced-security)." {% endif %} \ No newline at end of file +El resumen de seguridad se encuentra disponible para las organizaciones que utilizan {% data variables.product.prodname_enterprise %} y tienen una licencia para {% data variables.product.prodname_GH_advanced_security %}. Para obtener más información, consulta la sección "[Acerca de la {% data variables.product.prodname_GH_advanced_security %}](/get-started/learning-about-github/about-github-advanced-security)". {% endif %} \ No newline at end of file diff --git a/translations/es-ES/data/reusables/projects/enable-basic-workflow.md b/translations/es-ES/data/reusables/projects/enable-basic-workflow.md index 17e7ae9a54..a3433bcd38 100644 --- a/translations/es-ES/data/reusables/projects/enable-basic-workflow.md +++ b/translations/es-ES/data/reusables/projects/enable-basic-workflow.md @@ -1,4 +1,6 @@ -1. En tu proyecto, haz clic en {% octicon "workflow" aria-label="the workflow icon" %}. +1. Navegar a tu proyecto. +1. In the top-right, click {% octicon "kebab-horizontal" aria-label="The menu icon" %} to open the menu. +1. In the menu, click {% octicon "workflow" aria-label="The workflow icon" %} **Workflows**. 1. Debajo de **Flujos de trabajo predeterminados**, haz clic en el flujo de trabajo que quieres editar. 1. Si el flujo de trabajo puede aplicarse a ambos resultados y solicitudes de cambio, junto a **Dónde**, verifica el(los) tipo(s) de elemento(s) sobre el(los) cuál(es) quieres actuar. 1. Junto a **Configurar**, elige el valor en el cual quieres configurar al estado. diff --git a/translations/es-ES/data/reusables/projects/project-settings.md b/translations/es-ES/data/reusables/projects/project-settings.md index fcf2725f4d..0e3f9317ea 100644 --- a/translations/es-ES/data/reusables/projects/project-settings.md +++ b/translations/es-ES/data/reusables/projects/project-settings.md @@ -1,2 +1,3 @@ 1. Navegar a tu proyecto. -1. Haz clic en {% octicon "gear" aria-label="the gear icon" %} para acceder a los ajustes del proyecto. +1. In the top-right, click {% octicon "kebab-horizontal" aria-label="The menu icon" %} to open the menu. +1. In the menu, click {% octicon "gear" aria-label="The gear icon" %} **Settings** to access the project settings. diff --git a/translations/es-ES/data/reusables/secret-scanning/secret-list-private-push-protection.md b/translations/es-ES/data/reusables/secret-scanning/secret-list-private-push-protection.md index c93fc2864f..13a1e1c2d5 100644 --- a/translations/es-ES/data/reusables/secret-scanning/secret-list-private-push-protection.md +++ b/translations/es-ES/data/reusables/secret-scanning/secret-list-private-push-protection.md @@ -45,8 +45,8 @@ | Linear | Token de Acceso Oauth de Linear | linear_oauth_access_token | | Midtrans | Midtrans Production Server Key | midtrans_production_server_key | | New Relic | New Relic Personal API Key | new_relic_personal_api_key | -| New Relic | New Relic REST API Key | new_relic_rest_api_key | -| New Relic | New Relic Insights Query Key | new_relic_insights_query_key | +| Reliquia nueva | New Relic REST API Key | new_relic_rest_api_key | +| Reliquia nueva | New Relic Insights Query Key | new_relic_insights_query_key | | npm | Token de Acceso de npm | npm_access_token | | NuGet | Clave de API de NuGet | nuget_api_key | | Onfido | Onfido Live API Token | onfido_live_api_token | diff --git a/translations/ja-JP/content/actions/using-workflows/about-workflows.md b/translations/ja-JP/content/actions/using-workflows/about-workflows.md index 7305560f11..e7a4ad4d86 100644 --- a/translations/ja-JP/content/actions/using-workflows/about-workflows.md +++ b/translations/ja-JP/content/actions/using-workflows/about-workflows.md @@ -28,7 +28,7 @@ A workflow must contain the following basic components: 1. One or more _jobs_, each of which will execute on a _runner_ machine and run a series of one or more _steps_. 1. Each step can either run a script that you define or run an action, which is a reusable extension that can simplify your workflow. -For more information these basic components, see "[Understanding GitHub Actions](/actions/learn-github-actions/understanding-github-actions#the-components-of-github-actions)." +For more information on these basic components, see "[Understanding GitHub Actions](/actions/learn-github-actions/understanding-github-actions#the-components-of-github-actions)." ![ワークフローの概要](/assets/images/help/images/overview-actions-simple.png) diff --git a/translations/ja-JP/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-minio-gateway-for-nas-storage.md b/translations/ja-JP/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-minio-gateway-for-nas-storage.md index 77caf14c10..514ab779d4 100644 --- a/translations/ja-JP/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-minio-gateway-for-nas-storage.md +++ b/translations/ja-JP/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-minio-gateway-for-nas-storage.md @@ -14,9 +14,14 @@ redirect_from: - /admin/github-actions/enabling-github-actions-with-minio-gateway-for-nas-storage shortTitle: MinIO Gateway for NAS storage --- -## Prerequisites -{% data reusables.actions.enterprise-s3-support-warning %} +{% warning %} + +**Warning**: MinIO has announced removal of MinIO Gateways. Starting June 1st, 2022, support and bug fixes for the current MinIO NAS Gateway implementation will only be available for paid customers via their LTS support contract. If you want to continue using MinIO Gateways with {% data variables.product.prodname_actions %}, we recommend moving to MinIO LTS support. For more information, see [Scheduled removal of MinIO Gateway for GCS, Azure, HDFS](https://github.com/minio/minio/issues/14331) in the minio/minio repository. + +{% endwarning %} + +## Prerequisites Before enabling {% data variables.product.prodname_actions %}, make sure you have completed the following steps: diff --git a/translations/ja-JP/content/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise.md b/translations/ja-JP/content/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise.md index b507720da4..b2dca564bc 100644 --- a/translations/ja-JP/content/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise.md +++ b/translations/ja-JP/content/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise.md @@ -48,7 +48,7 @@ Each action is a repository in the `actions` organization, and each action repos **Notes:** - When using setup actions (such as `actions/setup-LANGUAGE`) on {% data variables.product.product_name %} with self-hosted runners, you might need to set up the tools cache on runners that do not have internet access. For more information, see "[Setting up the tool cache on self-hosted runners without internet access](/enterprise/admin/github-actions/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access)." -- Upgrades to {% data variables.product.product_name %} will not result in the bundled actions being updated. +- Bundled actions are automatically updated when {% data variables.product.product_name %} is updated. {% endnote %} diff --git a/translations/ja-JP/content/codespaces/customizing-your-codespace/setting-your-timeout-period-for-codespaces.md b/translations/ja-JP/content/codespaces/customizing-your-codespace/setting-your-timeout-period-for-codespaces.md index 665f00e292..4ffe73ee77 100644 --- a/translations/ja-JP/content/codespaces/customizing-your-codespace/setting-your-timeout-period-for-codespaces.md +++ b/translations/ja-JP/content/codespaces/customizing-your-codespace/setting-your-timeout-period-for-codespaces.md @@ -12,6 +12,8 @@ shortTitle: Set the timeout A codespace will stop running after a period of inactivity. You can specify the length of this timeout period. The updated setting will apply to any newly created codespace. +Some organizations may have a maximum idle timeout policy. If an organization policy sets a maximum timeout which is less than the default timeout you have set, the organization's timeout will be used instead of your setting, and you will be notified of this after the codespace is created. For more information, see "[Restricting the idle timeout period](/codespaces/managing-codespaces-for-your-organization/restricting-the-idle-timeout-period)." + {% warning %} **Warning**: Codespaces are billed per minute. If you are not actively using a codespace but the codespace has not yet timed out, you are still billed for the time that the codespace is running. For more information, see "[About billing for Codespaces](/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces#codespaces-pricing)." diff --git a/translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/index.md b/translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/index.md index 956e9ff777..760a40c7de 100644 --- a/translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/index.md +++ b/translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/index.md @@ -15,6 +15,7 @@ children: - /reviewing-your-organizations-audit-logs-for-codespaces - /restricting-access-to-machine-types - /restricting-the-visibility-of-forwarded-ports + - /restricting-the-idle-timeout-period shortTitle: Managing your organization --- diff --git a/translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types.md b/translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types.md index 9551f05f03..815af79de4 100644 --- a/translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types.md +++ b/translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types.md @@ -1,9 +1,9 @@ --- title: Restricting access to machine types -shortTitle: Machine type access +shortTitle: Restrict machine types intro: You can set constraints on the types of machines users can choose when they create codespaces in your organization. product: '{% data reusables.gated-features.codespaces %}' -permissions: 'To manage access to machine types for the repositories in an organization, you must be an organization owner.' +permissions: 'To manage access to machine types for the repositories in an organization, you must be an owner of the organization.' versions: fpt: '*' ghec: '*' @@ -47,33 +47,22 @@ If you add an organization-wide policy, you should set it to the largest choice {% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} -1. In the "Code, planning, and automation" section of the sidebar, select **{% octicon "codespaces" aria-label="The codespaces icon" %} {% data variables.product.prodname_codespaces %}** then click **Policy**. -2. On the "Codespace policies" page, click **Create Policy**. -3. Enter a name for your new policy. -4. Click **Add constraint** and choose **Machine types**. +{% data reusables.codespaces.codespaces-org-policies %} +1. Click **Add constraint** and choose **Machine types**. ![Add a constraint for machine types](/assets/images/help/codespaces/add-constraint-dropdown.png) -5. Click {% octicon "pencil" aria-label="The edit icon" %} to edit the constraint, then clear the selection of any machine types that you don't want to be available. +1. Click {% octicon "pencil" aria-label="The edit icon" %} to edit the constraint, then clear the selection of any machine types that you don't want to be available. ![Edit the machine type constraint](/assets/images/help/codespaces/edit-machine-constraint.png) -6. In the "Change policy target" area, click the dropdown button. -7. Choose either **All repositories** or **Selected repositories** to determine which repositories this policy will apply to. -8. [**Selected repositories**] を選択した場合、以下の手順に従います。 - 1. {% octicon "gear" aria-label="The settings icon" %} をクリックします。 - - ![Edit the settings for the policy](/assets/images/help/codespaces/policy-edit.png) - - 2. Select the repositories you want this policy to apply to. - 3. At the bottom of the repository list, click **Select repositories**. - - ![Select repositories for this policy](/assets/images/help/codespaces/policy-select-repos.png) - -9. [**Save**] をクリックします。 - +{% data reusables.codespaces.codespaces-policy-targets %} +1. If you want to add another constraint to the policy, click **Add constraint** and choose another constraint. For information about other constraints, see "[Restricting the visibility of forwarded ports](/codespaces/managing-codespaces-for-your-organization/restricting-the-visibility-of-forwarded-ports)" and "[Restricting the idle timeout period](/codespaces/managing-codespaces-for-your-organization/restricting-the-idle-timeout-period)." +1. After you have finished adding constraints to your policy, click **Save**. ## Editing a policy +You can edit an existing policy. For example, you may want to add or remove constraints to or from a policy. + 1. Display the "Codespace policies" page. For more information, see "[Adding a policy to limit the available machine types](#adding-a-policy-to-limit-the-available-machine-types)." 1. Click the name of the policy you want to edit. 1. Make the required changes then click **Save**. diff --git a/translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/restricting-the-idle-timeout-period.md b/translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/restricting-the-idle-timeout-period.md new file mode 100644 index 0000000000..047f6a100b --- /dev/null +++ b/translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/restricting-the-idle-timeout-period.md @@ -0,0 +1,79 @@ +--- +title: Restricting the idle timeout period +shortTitle: Restrict timeout periods +intro: You can set a maximum timeout period for any codespaces owned by your organization. +product: '{% data reusables.gated-features.codespaces %}' +permissions: 'To manage timeout constraints for an organization''s codespaces, you must be an owner of the organization.' +versions: + fpt: '*' + ghec: '*' +type: how_to +topics: + - Codespaces +--- + +## 概要 + +By default, codespaces time out after 30 minutes of inactivity. When a codespace times out it is stopped and will no longer incur charges for compute usage. + +The personal settings of a {% data variables.product.prodname_dotcom %} user allow them to define their own timeout period for codespaces they create. This may be longer than the default 30-minute period. For more information, see "[Setting your timeout period for Codespaces](/codespaces/customizing-your-codespace/setting-your-timeout-period-for-codespaces)." + +As an organization owner, you may want to configure constraints on the maximum idle timeout period for codespaces owned by your organization. This can help you limit costs associated with codespaces that are left to timeout after long periods of inactivity. You can set a maximum timeout for all codespaces owned by your organization, or for the codespaces of specific repositories. + +{% note %} + +**Note**: Maximum idle timeout constraints only apply to codespaces that are owned by your organization. + +{% endnote %} + +For more information about pricing for {% data variables.product.prodname_codespaces %} compute usage, see "[About billing for Codespaces](/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces#codespaces-pricing)." + +### Behavior when you set a maximum idle timeout constraint + +If someone sets the default idle timeout to 90 minutes in their personal settings and they then start a codespace for a repository with a maximum idle timeout constraint of 60 minutes, the codespace will time out after 60 minutes of inactivity. When codespace creation completes, a message explaining this will be displayed: + +> Idle timeout for this codespace is set to 60 minutes in compliance with your organization’s policy. + +### Setting organization-wide and repository-specific policies + +When you create a policy, you choose whether it applies to all repositories in your organization, or only to specified repositories. If you create an organization-wide policy with a timeout constraint, then the timeout constraints in any policies that are targeted at specific repositories must fall within the restriction configured for the entire organization. The shortest timeout period - in an organization-wide policy, a policy targeted at specified repositories, or in someone's personal settings - is applied. + +If you add an organization-wide policy with a timeout constraint, you should set the timeout to the longest acceptable period. You can then add separate policies that set the maximum timeout to a shorter period for specific repositories in your organization. + +## Adding a policy to set a maximum idle timeout period + +{% data reusables.profile.access_org %} +{% data reusables.profile.org_settings %} +{% data reusables.codespaces.codespaces-org-policies %} +1. Click **Add constraint** and choose **Maximum idle timeout**. + + ![Add a constraint for idle timeout](/assets/images/help/codespaces/add-constraint-dropdown-timeout.png) + +1. Click {% octicon "pencil" aria-label="The edit icon" %} to edit the constraint. + + ![Edit the timeout constraint](/assets/images/help/codespaces/edit-timeout-constraint.png) + +1. Enter the maximum number of minutes codespaces can remain inactive before they time out, then click **Save**. + + ![Choose the port visibility options](/assets/images/help/codespaces/maximum-minutes-timeout.png) + +{% data reusables.codespaces.codespaces-policy-targets %} +1. If you want to add another constraint to the policy, click **Add constraint** and choose another constraint. For information about other constraints, see "[Restricting access to machine types](/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types)" and "[Restricting the visibility of forwarded ports](/codespaces/managing-codespaces-for-your-organization/restricting-the-visibility-of-forwarded-ports)." +1. After you have finished adding constraints to your policy, click **Save**. + +The policy will be applied to all new codespaces that are created, and to existing codespaces the next time they are started. + +## Editing a policy + +You can edit an existing policy. For example, you may want to add or remove constraints to or from a policy. + +1. Display the "Codespace policies" page. For more information, see "[Adding a policy to set a maximum idle timeout period](#adding-a-policy-to-set-a-maximum-idle-timeout-period)." +1. Click the name of the policy you want to edit. +1. Make the required changes then click **Save**. + +## Deleting a policy + +1. Display the "Codespace policies" page. For more information, see "[Adding a policy to set a maximum idle timeout period](#adding-a-policy-to-set-a-maximum-idle-timeout-period)." +1. Click the delete button to the right of the policy you want to delete. + + ![The delete button for a policy](/assets/images/help/codespaces/policy-delete.png) diff --git a/translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/restricting-the-visibility-of-forwarded-ports.md b/translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/restricting-the-visibility-of-forwarded-ports.md index 1812b4c0d4..9bf4444787 100644 --- a/translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/restricting-the-visibility-of-forwarded-ports.md +++ b/translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/restricting-the-visibility-of-forwarded-ports.md @@ -1,9 +1,9 @@ --- title: Restricting the visibility of forwarded ports -shortTitle: Restricting port visibility +shortTitle: Restrict port visibility intro: You can set constraints on the visibility options users can choose when they forward ports from codespaces in your organization. product: '{% data reusables.gated-features.codespaces %}' -permissions: 'To manage access to port visibility constraints for the repositories in an organization, you must be an organization owner.' +permissions: 'To manage access to port visibility constraints for the repositories in an organization, you must be an owner of the organization.' versions: fpt: '*' ghec: '*' @@ -40,14 +40,12 @@ If you add an organization-wide policy, you should set it to the most lenient vi {% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} -1. In the "Code, planning, and automation" section of the sidebar, select **{% octicon "codespaces" aria-label="The codespaces icon" %} {% data variables.product.prodname_codespaces %}** then click **Policies**. -1. On the "Codespace policies" page, click **Create Policy**. -1. Enter a name for your new policy. +{% data reusables.codespaces.codespaces-org-policies %} 1. Click **Add constraint** and choose **Port visibility**. ![Add a constraint for port visibility](/assets/images/help/codespaces/add-constraint-dropdown-ports.png) -1. Click {% octicon "pencil" aria-label="The edit icon" %} to edit the constraint +1. Click {% octicon "pencil" aria-label="The edit icon" %} to edit the constraint. ![Edit the port visibility constraint](/assets/images/help/codespaces/edit-port-visibility-constraint.png) @@ -55,22 +53,13 @@ If you add an organization-wide policy, you should set it to the most lenient vi ![Choose the port visibility options](/assets/images/help/codespaces/choose-port-visibility-options.png) -1. In the "Change policy target" area, click the dropdown button. -1. Choose either **All repositories** or **Selected repositories** to determine which repositories this policy will apply to. -1. [**Selected repositories**] を選択した場合、以下の手順に従います。 - 1. {% octicon "gear" aria-label="The settings icon" %} をクリックします。 - - ![Edit the settings for the policy](/assets/images/help/codespaces/policy-edit.png) - - 2. Select the repositories you want this policy to apply to. - 3. At the bottom of the repository list, click **Select repositories**. - - ![Select repositories for this policy](/assets/images/help/codespaces/policy-select-repos.png) - -1. [**Save**] をクリックします。 - +{% data reusables.codespaces.codespaces-policy-targets %} +1. If you want to add another constraint to the policy, click **Add constraint** and choose another constraint. For information about other constraints, see "[Restricting access to machine types](/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types)" and "[Restricting the idle timeout period](/codespaces/managing-codespaces-for-your-organization/restricting-the-idle-timeout-period)." +1. After you have finished adding constraints to your policy, click **Save**. ## Editing a policy +You can edit an existing policy. For example, you may want to add or remove constraints to or from a policy. + 1. Display the "Codespace policies" page. For more information, see "[Adding a policy to limit the port visibility options](#adding-a-policy-to-limit-the-port-visibility-options)." 1. Click the name of the policy you want to edit. 1. Make the required changes then click **Save**. diff --git a/translations/ja-JP/content/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/committing-and-reviewing-changes-to-your-project.md b/translations/ja-JP/content/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/committing-and-reviewing-changes-to-your-project.md index aa27b828ca..74308f5ae4 100644 --- a/translations/ja-JP/content/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/committing-and-reviewing-changes-to-your-project.md +++ b/translations/ja-JP/content/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/committing-and-reviewing-changes-to-your-project.md @@ -123,3 +123,11 @@ If you need to see more of the file than {% data variables.product.prodname_desk ![保護されたブランチの警告](/assets/images/help/desktop/protected-branch-warning.png) {% data reusables.desktop.push-origin %} + +6. If you have a pull request based off the branch you are working on, {% data variables.product.prodname_desktop %} will display the status of the checks that have run for the pull request. For more information about checks, see "[Viewing and re-running checks in GitHub Desktop](/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/viewing-and-re-running-checks-in-github-desktop)." + + ![Checks display next to branch name](/assets/images/help/desktop/checks-dialog.png) + + If a pull request has not been created for the current branch, {% data variables.product.prodname_desktop %} will give you the option to create one. For more information, see "[Creating an issue or pull request](/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/creating-an-issue-or-pull-request)." + + ![プルリクエストの作成方法](/assets/images/help/desktop/mac-create-pull-request.png) diff --git a/translations/ja-JP/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/configuring-notifications-in-github-desktop.md b/translations/ja-JP/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/configuring-notifications-in-github-desktop.md new file mode 100644 index 0000000000..c78cf1fd28 --- /dev/null +++ b/translations/ja-JP/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/configuring-notifications-in-github-desktop.md @@ -0,0 +1,63 @@ +--- +title: Configuring notifications in GitHub Desktop +shortTitle: 通知を設定する +intro: '{% data variables.product.prodname_desktop %} will keep you up-to-date with notifications about events that occur in your pull request branch.' +versions: + fpt: '*' +--- + +## About notifications in {% data variables.product.prodname_desktop %} + +{% data variables.product.prodname_desktop %} will show a system notification for events that occur in the currently selected repository. Notifications will be shown when: + +- Pull request checks have failed. +- A pull request review is left with a comment, approval, or requested changes. + +Clicking the notification will switch application focus to {% data variables.product.prodname_desktop %} and provide more detailed information. + +## Notifications about pull request check failures + +When changes are made to a pull request branch, you will receive a notification if the checks fail. + +![pull request checks failed notification](/assets/images/help/desktop/pull-request-checks-failed-notification.png) + +Clicking the notification will display a dialog with details about the checks. Once you've reviewed why the checks have failed, you can re-run the checks, or quickly switch to the pull request branch to get started on fixing the errors. For more information, see "[Viewing and re-running checks in GitHub Desktop](/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/viewing-and-re-running-checks-in-github-desktop)." + +![checks failed dialog](/assets/images/help/desktop/checks-failed-dialog.png) +## Notifications for pull request reviews + +{% data variables.product.prodname_desktop %} will surface a system notification when a teammate has approved, commented, or requested changes in your pull request. See "[About pull request reviews](/github/collaborating-with-issues-and-pull-requests/about-pull-request-reviews)" for more information on pull request reviews. + +![Pull request review notification](/assets/images/help/desktop/pull-request-review-notification.png) + +Clicking the notification will switch application focus to {% data variables.product.prodname_desktop %} and provide more context for the pull request review comment. + +![pull request review dialog](/assets/images/help/desktop/pull-request-review-dialog.png) +## Enabling notifications + +If system notifications are disabled for {% data variables.product.prodname_desktop %} you can follow the steps below to enable them. + +{% mac %} + +1. Click the **Apple** menu, then select **System Preferences**. +2. Select **Notifications & Focus**. +3. Select **{% data variables.product.prodname_desktop %}** from the list of applications. +4. Click **Allow Notifications**. + +![macOS Notifications & Focus](/assets/images/help/desktop/mac-enable-notifications.png) + +For more information about macOS system notifications, see "[Use notifications on your Mac](https://support.apple.com/en-us/HT204079)." + +{% endmac %} + +{% windows %} + +1. Open the **Start** menu, then select **Settings**. +2. Select **System**, then click **Notifications**. +3. Find **{% data variables.product.prodname_desktop %}** in the application list and click **On**. + +![Enable Windows Notifications](/assets/images/help/desktop/windows-enable-notifications.png) + +For more information about Windows system notifications, see "[Change notification settings in Windows](https://support.microsoft.com/en-us/windows/change-notification-settings-in-windows-8942c744-6198-fe56-4639-34320cf9444e)." + +{% endwindows %} diff --git a/translations/ja-JP/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/index.md b/translations/ja-JP/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/index.md index 99f91e005f..dd855f1d11 100644 --- a/translations/ja-JP/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/index.md +++ b/translations/ja-JP/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/index.md @@ -8,6 +8,8 @@ versions: children: - /creating-an-issue-or-pull-request - /viewing-a-pull-request-in-github-desktop + - /viewing-and-re-running-checks-in-github-desktop + - /configuring-notifications-in-github-desktop - /changing-a-remotes-url-from-github-desktop shortTitle: Work with your remote repo --- diff --git a/translations/ja-JP/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/viewing-a-pull-request-in-github-desktop.md b/translations/ja-JP/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/viewing-a-pull-request-in-github-desktop.md index cbbd24efa4..1bf3e5724a 100644 --- a/translations/ja-JP/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/viewing-a-pull-request-in-github-desktop.md +++ b/translations/ja-JP/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/viewing-a-pull-request-in-github-desktop.md @@ -14,6 +14,8 @@ You can view pull requests that you or your collaborators have proposed in {% da When you view a pull request in {% data variables.product.prodname_desktop %}, you can see a history of commits that contributors made. You can also see which files the commits modified, added, or deleted. From {% data variables.product.prodname_desktop %}, you can open repositories in your preferred text editor to view any changes or make additional changes. After reviewing changes in a pull request, you can give feedback on {% data variables.product.prodname_dotcom %}. For more information, see "[About pull request reviews](/github/collaborating-with-issues-and-pull-requests/about-pull-request-reviews)." +If checks have been enabled in your repository, {% data variables.product.prodname_desktop %} will show the status of the checks on the pull request and allow you to re-run checks. For more information, see "[Viewing and re-running checks in GitHub Desktop](/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/viewing-and-re-running-checks-in-github-desktop)." + ## Viewing a pull request in {% data variables.product.prodname_desktop %} {% data reusables.desktop.current-branch-menu %} {% data reusables.desktop.click-pull-requests %} diff --git a/translations/ja-JP/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/viewing-and-re-running-checks-in-github-desktop.md b/translations/ja-JP/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/viewing-and-re-running-checks-in-github-desktop.md new file mode 100644 index 0000000000..76f5f6393d --- /dev/null +++ b/translations/ja-JP/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/viewing-and-re-running-checks-in-github-desktop.md @@ -0,0 +1,25 @@ +--- +title: Viewing and re-running checks in GitHub Desktop +shortTitle: Viewing and re-running checks +intro: 'You can view the status of checks and re-run them in {% data variables.product.prodname_desktop %}.' +versions: + fpt: '*' +--- + +## About checks in {% data variables.product.prodname_desktop %} + +{% data variables.product.prodname_desktop %} displays the status of checks that have run in your pull request branches. The checks badge next to the branch name will display the *pending, passing,* or *failing* state of the checks. You can also re-run all, failed, or individual checks when viewing the status of the checks in {% data variables.product.prodname_desktop %}. For more information on setting up checks in your repository, see "[About status checks](/github/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks)." + +{% data variables.product.prodname_desktop %} will also show a system notification when checks fail. For more information on enabling notifications, see "[Configuring notifications in GitHub Desktop](/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/configuring-notifications-in-github-desktop)." + +## Viewing and re-running checks + +{% data reusables.desktop.current-branch-menu %} +{% data reusables.desktop.click-pull-requests %} + ![[Current Branch] のドロップダウンメニュー内にある [Pull Requests] タブ](/assets/images/help/desktop/branch-drop-down-pull-request-tab.png) +{% data reusables.desktop.choose-pr-from-list %} + ![リポジトリ内のオープンプルリクエストのリスト](/assets/images/help/desktop/click-pull-request.png) +4. Click on the pull request number, to the right of the pull request branch name. ![Checks display next to branch name](/assets/images/help/desktop/checks-dialog.png) +5. To re-run failed checks, click **{% octicon "sync" aria-label="The sync icon" %} Re-run** and select **Re-run Failed Checks**. ![Re-run failed checks](/assets/images/help/desktop/re-run-failed-checks.png) +6. To re-run individual checks, hover over the individual check you want to re-run and select the {% octicon "sync" aria-label="The sync icon" %} icon to re-run the check. ![Re-run individual checks](/assets/images/help/desktop/re-run-individual-checks.png) +7. You will see a confirmation dialog with the summary of the checks that will be re-run. Click **Re-run Checks** to confirm that you want to perform the re-run. ![Re-run confirmation dialog](/assets/images/help/desktop/re-run-confirmation-dialog.png) diff --git a/translations/ja-JP/content/developers/apps/building-oauth-apps/scopes-for-oauth-apps.md b/translations/ja-JP/content/developers/apps/building-oauth-apps/scopes-for-oauth-apps.md index d8536a2b79..4f279648a5 100644 --- a/translations/ja-JP/content/developers/apps/building-oauth-apps/scopes-for-oauth-apps.md +++ b/translations/ja-JP/content/developers/apps/building-oauth-apps/scopes-for-oauth-apps.md @@ -67,9 +67,9 @@ X-Accepted-OAuth-Scopes: user |  `user:follow` | 他のユーザのフォローあるいはフォロー解除のアクセスを許可します。 | | **`delete_repo`** | 管理可能なリポジトリの削除アクセスを許可します。 | | **`write:discussion`** | Teamのディスカッションの読み書きアクセスを許可します。 | -|  `read:discussion` | Team ディスカッションの読み取りアクセスを許可します。{% ifversion fpt or ghae or ghec %} +|  `read:discussion` | Allows read access for team discussions. | | **`write:packages`** | {% data variables.product.prodname_registry %}でのパッケージのアップロードあるいは公開のアクセスを許可します。 詳しい情報については「[パッケージの公開](/github/managing-packages-with-github-packages/publishing-a-package)」を参照してください。 | -| **`read:packages`** | {% data variables.product.prodname_registry %}からのパッケージのダウンロードあるいはインストールのアクセスを許可します。 詳しい情報については「[パッケージのインストール](/github/managing-packages-with-github-packages/installing-a-package)」を参照してください。 | +| **`read:packages`** | {% data variables.product.prodname_registry %}からのパッケージのダウンロードあるいはインストールのアクセスを許可します。 For more information, see "[Installing a package](/github/managing-packages-with-github-packages/installing-a-package)".{% ifversion fpt or ghec or ghes > 3.1 or ghae %} | **`delete:packages`** | {% data variables.product.prodname_registry %}からのパッケージの削除アクセスを許可します。 詳しい情報については、「[パッケージの削除とリストア](/packages/learn-github-packages/deleting-and-restoring-a-package)」を参照してください。{% endif %} | **`admin:gpg_key`** | GPGキーを完全に管理できます。 | |  `write:gpg_key` | GPGキーの作成、リスト、詳細の表示ができます。 | diff --git a/translations/ja-JP/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md b/translations/ja-JP/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md index 2ee2cfeb0e..070c805e26 100644 --- a/translations/ja-JP/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md +++ b/translations/ja-JP/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md @@ -811,8 +811,6 @@ GitHub Marketplace の購入に関連するアクティビティ。 {% data reus {% endif %} -{% ifversion fpt or ghae or ghec %} - ## package {% data variables.product.prodname_registry %} に関連するアクティビティ。 {% data reusables.webhooks.action_type_desc %} {% data variables.product.prodname_registry %} の詳細については、「[{% data variables.product.prodname_registry %} を使用してパッケージを管理する](/github/managing-packages-with-github-packages)」を参照してください。 @@ -832,7 +830,6 @@ GitHub Marketplace の購入に関連するアクティビティ。 {% data reus ### webhook ペイロードの例 {{ webhookPayloadsForCurrentVersion.package.published }} -{% endif %} ## page_build diff --git a/translations/ja-JP/content/packages/learn-github-packages/introduction-to-github-packages.md b/translations/ja-JP/content/packages/learn-github-packages/introduction-to-github-packages.md index 1ffeed2655..f4716e5ca3 100644 --- a/translations/ja-JP/content/packages/learn-github-packages/introduction-to-github-packages.md +++ b/translations/ja-JP/content/packages/learn-github-packages/introduction-to-github-packages.md @@ -23,7 +23,7 @@ shortTitle: Introduction ## About {% data variables.product.prodname_registry %} -{% data variables.product.prodname_registry %} is a platform for hosting and managing packages, including containers and other dependencies. {% data variables.product.prodname_registry %} combines your source code and packages in one place to provide integrated permissions management{% ifversion not ghae %} and billing{% endif %}, so you can centralize your software development on {% data variables.product.product_name %}. +{% data variables.product.prodname_registry %} is a platform for hosting and managing packages, including containers and other dependencies. {% data variables.product.prodname_registry %} combines your source code and packages in one place to provide integrated permissions management{% ifversion fpt or ghec %} and billing{% endif %}, so you can centralize your software development on {% data variables.product.product_name %}. You can integrate {% data variables.product.prodname_registry %} with {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} APIs, {% data variables.product.prodname_actions %}, and webhooks to create an end-to-end DevOps workflow that includes your code, CI, and deployment solutions. diff --git a/translations/ja-JP/content/packages/quickstart.md b/translations/ja-JP/content/packages/quickstart.md index f0cf7373f2..74558266b7 100644 --- a/translations/ja-JP/content/packages/quickstart.md +++ b/translations/ja-JP/content/packages/quickstart.md @@ -21,7 +21,7 @@ In this guide, you'll create a {% data variables.product.prodname_actions %} wor 1. Create a new repository on {% data variables.product.prodname_dotcom %}, adding the `.gitignore` for Node. For more information, see "[Creating a new repository](/github/creating-cloning-and-archiving-repositories/creating-a-new-repository)." 2. Clone the repository to your local machine. ```shell - $ git clone https://{% ifversion ghae %}YOUR-HOSTNAME{% else %}github.com{% endif %}/YOUR-USERNAME/YOUR-REPOSITORY.git + $ git clone https://{% ifversion ghes or ghae %}YOUR-HOSTNAME{% else %}github.com{% endif %}/YOUR-USERNAME/YOUR-REPOSITORY.git $ cd YOUR-REPOSITORY ``` 3. Create an `index.js` file and add a basic alert to say "Hello world!" @@ -49,7 +49,7 @@ In this guide, you'll create a {% data variables.product.prodname_actions %} wor $ git push ``` 6. Create a `.github/workflows` directory. In that directory, create a file named `release-package.yml`. -7. Copy the following YAML content into the `release-package.yml` file{% ifversion ghae %}, replacing `YOUR-HOSTNAME` with the name of your enterprise{% endif %}. +7. Copy the following YAML content into the `release-package.yml` file{% ifversion ghes or ghae %}, replacing `YOUR-HOSTNAME` with the name of your enterprise{% endif %}. ```yaml{:copy} name: Node.js Package @@ -79,7 +79,7 @@ In this guide, you'll create a {% data variables.product.prodname_actions %} wor - uses: {% data reusables.actions.action-setup-node %} with: node-version: 12 - registry-url: {% ifversion ghae %}https://npm.YOUR-HOSTNAME.com/{% else %}https://npm.pkg.github.com/{% endif %} + registry-url: {% ifversion ghes or ghae %}https://npm.YOUR-HOSTNAME.com/{% else %}https://npm.pkg.github.com/{% endif %} - run: npm ci - run: npm publish env: diff --git a/translations/ja-JP/content/rest/codes-of-conduct.md b/translations/ja-JP/content/rest/codes-of-conduct.md index b73c25e84c..7363ab1f02 100644 --- a/translations/ja-JP/content/rest/codes-of-conduct.md +++ b/translations/ja-JP/content/rest/codes-of-conduct.md @@ -1,5 +1,5 @@ --- -title: Codes of Conduct +title: 行動規範 intro: '' versions: fpt: '*' diff --git a/translations/ja-JP/content/rest/gitignore.md b/translations/ja-JP/content/rest/gitignore.md index 96656cd2db..528e1d9eb7 100644 --- a/translations/ja-JP/content/rest/gitignore.md +++ b/translations/ja-JP/content/rest/gitignore.md @@ -13,7 +13,7 @@ redirect_from: - /rest/reference/gitignore --- -When you create a new repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} via the API, you can specify a [.gitignore template](/github/getting-started-with-github/ignoring-files) to apply to the repository upon creation. .gitignore テンプレート API は、{% data variables.product.product_name %} の [.gitignore リポジトリ](https://github.com/github/gitignore)からテンプレートを一覧表示してフェッチします。 +{% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}上に新しいリポジトリをAPIを介して作成する場合、作成時にリポジトリに適用する[.gitignoreテンプレート](/github/getting-started-with-github/ignoring-files)を指定できます。 .gitignore テンプレート API は、{% data variables.product.product_name %} の [.gitignore リポジトリ](https://github.com/github/gitignore)からテンプレートを一覧表示してフェッチします。 ### gitignore のカスタムメディアタイプ diff --git a/translations/ja-JP/content/rest/licenses.md b/translations/ja-JP/content/rest/licenses.md index 3b3b7312a1..98c4c94833 100644 --- a/translations/ja-JP/content/rest/licenses.md +++ b/translations/ja-JP/content/rest/licenses.md @@ -30,6 +30,6 @@ redirect_from: GitHub にはいろいろなものがありますが、法律事務所ではありません。 そのため、GitHub が法律上の助言をすることはありません。 ライセンス API を使用したり、それに関して当社にメールを送信したりすることは法律上の助言に該当せず、弁護士と依頼人の関係を確立するものでもありません。 特定のライセンスで許可される範囲について疑問がある場合は、先に進む前にそれぞれの顧問弁護士にご相談ください。 むしろ、法的な結果が想定される、あるいは法律上の権利に影響しうる決定を下す場合には、必ずその前に各自の弁護士にご相談ください。 -GitHub は、ユーザがオープンソースライセンスと、それを利用するプロジェクトに関する情報を得るためにライセンス API を作成しました。 お役に立てれば幸いですが、当社は (少なくとも従業員のほとんどは) 弁護士ではなく、他の方と同じように誤りがないとは言えません。 For that reason, GitHub provides the API on an "as-is" basis and makes no warranties regarding any information or licenses provided on or through it, and disclaims liability for damages resulting from using the API. +GitHub は、ユーザがオープンソースライセンスと、それを利用するプロジェクトに関する情報を得るためにライセンス API を作成しました。 お役に立てれば幸いですが、当社は (少なくとも従業員のほとんどは) 弁護士ではなく、他の方と同じように誤りがないとは言えません。 したがって、GitHub は API を「現状のまま」提供するものであり、その API で、または API を通じて提供するいかなる情報またはライセンスに関しても一切の保証をせず、この API の使用に起因する損害についての責任を負いません。 {% endwarning %} diff --git a/translations/ja-JP/content/rest/packages.md b/translations/ja-JP/content/rest/packages.md index 33aea19629..ead5fa8efa 100644 --- a/translations/ja-JP/content/rest/packages.md +++ b/translations/ja-JP/content/rest/packages.md @@ -11,7 +11,7 @@ redirect_from: - /rest/reference/packages --- -The {% data variables.product.prodname_registry %} API enables you to manage packages using the REST API.{% ifversion fpt or ghec or ghes > 3.1 or ghae %} To learn more about restoring or deleting packages, see "[Restoring and deleting packages](/packages/learn-github-packages/deleting-and-restoring-a-package)."{% endif %} +{% data variables.product.prodname_registry %} APIを使用すると、REST APIを利用してパッケージを管理できます。{% ifversion fpt or ghec or ghes > 3.1 or ghae %}パッケージの復元もしくは削除に関してさらに学ぶには、「[パッケージの復元と削除](/packages/learn-github-packages/deleting-and-restoring-a-package)」を参照してください。{% endif %} このAPIを使うには、個人アクセストークンを使って認証を受けなければなりません。 - パッケージメタデータにアクセスするには、トークンに`read:packages`スコープが含まれていなければなりません。 @@ -20,4 +20,4 @@ The {% data variables.product.prodname_registry %} API enables you to manage pac `package_type`が`npm`、`maven`、`rubygems`、`nuget`のいずれかなら、パッケージは{% data variables.product.prodname_dotcom %}リポジトリからの権限を継承するので、トークンには`repo`スコープも含まれていなければなりません。 パッケージが{% data variables.product.prodname_container_registry %}内にあるなら、`package_type`は`container`であり、この`package_type`のアクセスあるいは管理のためにトークンに`repo`スコープが含まれている必要はありません。 `container`パッケージは、リポジトリは別に詳細な権限を提供します。 詳しい情報については「[{% data variables.product.prodname_registry %}の権限について](/packages/learn-github-packages/about-permissions-for-github-packages#about-scopes-and-permissions-for-package-registries)」を参照してください。 -SSOが有効化されたOrganization内のリソースにアクセスするために{% data variables.product.prodname_registry %} APIを使いたい場合は、個人アクセストークンにSSOを有効化しなければなりません。 For more information, see "[Authorizing a personal access token for use with SAML single sign-on](/github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %} +SSOが有効化されたOrganization内のリソースにアクセスするために{% data variables.product.prodname_registry %} APIを使いたい場合は、個人アクセストークンにSSOを有効化しなければなりません。 詳しい情報については{% ifversion fpt %}{% data variables.product.prodname_ghe_cloud %}ドキュメンテーションの{% else %}{% endif %}「[SAMLシングルサインオンで利用する個人アクセストークンの認可](/github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)」を参照してください。 diff --git a/translations/ja-JP/content/rest/rate-limit.md b/translations/ja-JP/content/rest/rate-limit.md index a98a690be3..9e49028f12 100644 --- a/translations/ja-JP/content/rest/rate-limit.md +++ b/translations/ja-JP/content/rest/rate-limit.md @@ -29,4 +29,4 @@ Search APIは[カスタムのレート制限](/rest/reference/search#rate-limit) * `integration_manifest`オブジェクトは、[GitHub App Manifest コード変換](/apps/building-github-apps/creating-github-apps-from-a-manifest/#3-you-exchange-the-temporary-code-to-retrieve-the-app-configuration)エンドポイントに対するレート制限のステータスを提供します。 -For more information on the headers and values in the rate limit response, see "[Resources in the REST API](/rest/overview/resources-in-the-rest-api#rate-limit-http-headers)." +レート制限レスポンス中のヘッダと値に関する詳しい情報については「[REST API中のリソース](/rest/overview/resources-in-the-rest-api#rate-limit-http-headers)」を参照してください。 diff --git a/translations/ja-JP/content/rest/reactions.md b/translations/ja-JP/content/rest/reactions.md index 998c405bfa..3b15226cb9 100644 --- a/translations/ja-JP/content/rest/reactions.md +++ b/translations/ja-JP/content/rest/reactions.md @@ -13,8 +13,8 @@ redirect_from: - /rest/reference/reactions --- -### Reaction types +### リアクションタイプ -When creating a reaction, the allowed values for the `content` parameter are as follows (with the corresponding emoji for reference): +リアクションを作成する際、`content`パラメータで利用可能な値は以下の通りです (参考のため、対応する絵文字も掲載します)。 {% data reusables.repositories.reaction_list %} diff --git a/translations/ja-JP/content/rest/scim.md b/translations/ja-JP/content/rest/scim.md index 654b57d219..1a1f115db1 100644 --- a/translations/ja-JP/content/rest/scim.md +++ b/translations/ja-JP/content/rest/scim.md @@ -1,6 +1,6 @@ --- title: SCIM -intro: You can control and manage your GitHub organization members access using SCIM API. +intro: GitHub Organizationのメンバーのアクセスを、SCIM APIを使って制御及び管理できます。 versions: fpt: '*' ghec: '*' @@ -13,13 +13,13 @@ redirect_from: ### Organization 向け SCIM プロビジョニング -SCIM API は SCIM を有効にしたアイデンティティプロバイダ (IdPs) で、{% data variables.product.product_name %} Organization メンバーシップのプロビジョニングを自動化するために用いられます。 The {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API is based on version 2.0 of the [SCIM standard](http://www.simplecloud.info/). IdP が使用するべき {% data variables.product.product_name %} SCIM エンドポイントは、`{% data variables.product.api_url_code %}/scim/v2/organizations/{org}/` です。 +SCIM API は SCIM を有効にしたアイデンティティプロバイダ (IdPs) で、{% data variables.product.product_name %} Organization メンバーシップのプロビジョニングを自動化するために用いられます。 {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} APIは、[SCIM標準](http://www.simplecloud.info/)バージョン2に基づいています。 IdP が使用するべき {% data variables.product.product_name %} SCIM エンドポイントは、`{% data variables.product.api_url_code %}/scim/v2/organizations/{org}/` です。 {% note %} **ノート:** - - The SCIM API is available only for individual organizations that use [{% data variables.product.prodname_ghe_cloud %}](/billing/managing-billing-for-your-github-account/about-billing-for-github-accounts) with [SAML SSO](/rest/overview/other-authentication-methods#authenticating-for-saml-sso) enabled. For more information about SCIM, see "[About SCIM for organizations](/enterprise-cloud@latest/organizations/managing-saml-single-sign-on-for-your-organization/about-scim-for-organizations)." - - The SCIM API cannot be used with an enterprise account or with an {% data variables.product.prodname_emu_org %}. + - SCIM APIは[SAML SSO](/rest/overview/other-authentication-methods#authenticating-for-saml-sso)が有効化された[{% data variables.product.prodname_ghe_cloud %}](/billing/managing-billing-for-your-github-account/about-billing-for-github-accounts)を利用する個々のOrganizationでのみ利用できます。 SCIMに関する詳しい情報については「[OrganizationのためのSCIMについて](/enterprise-cloud@latest/organizations/managing-saml-single-sign-on-for-your-organization/about-scim-for-organizations)」を参照してください。 + - SCIM APIはEnterpriseアカウントで、あるいは{% data variables.product.prodname_emu_org %}と合わせて使うことはできません。 {% endnote %} diff --git a/translations/ja-JP/content/rest/search.md b/translations/ja-JP/content/rest/search.md index f805a7c0fa..b0e59b9602 100644 --- a/translations/ja-JP/content/rest/search.md +++ b/translations/ja-JP/content/rest/search.md @@ -1,6 +1,6 @@ --- title: 検索 -intro: The GitHub Search API lets you to search for the specific item efficiently. +intro: GitHub Search APIを使うと、特定のアイテムを効率的に検索できます。 versions: fpt: '*' ghes: '*' @@ -69,7 +69,7 @@ Search API は、以下のクエリをサポートしていません。 ### アクセスエラーまたは検索結果の欠落 -You need to successfully authenticate and have access to the repositories in your search queries, otherwise, you'll see a `422 Unprocessable Entry` error with a "Validation Failed" message. たとえば、{% data variables.product.prodname_dotcom %} にサインインしたときにアクセスできないリソースをリクエストする `repo:`、`user:`、または `org:` 修飾子がクエリに含まれている場合、検索は失敗します。 +認証に成功しており、検索クエリ中のリポジトリにアクセスを持っていなければなりません。そうでない場合は、"Validation Failed"というメッセージとともに`422 Unprocessable Entry`が返されます。 たとえば、{% data variables.product.prodname_dotcom %} にサインインしたときにアクセスできないリソースをリクエストする `repo:`、`user:`、または `org:` 修飾子がクエリに含まれている場合、検索は失敗します。 検索クエリで複数のリソースをリクエストする場合、レスポンスにはあなたがアクセスできるリソースのみが含まれ、返されないリソースを一覧表示するようなエラーメッセージは**表示されません**。 diff --git a/translations/ja-JP/content/rest/teams/discussions.md b/translations/ja-JP/content/rest/teams/discussions.md index 0bc46ac947..54ecebe058 100644 --- a/translations/ja-JP/content/rest/teams/discussions.md +++ b/translations/ja-JP/content/rest/teams/discussions.md @@ -1,6 +1,6 @@ --- -title: Discussions -intro: 'The Team Discussions API allows you to get, create, edit, and delete discussion posts on a team''s page.' +title: ディスカッション +intro: Team Discussions APIを使用すると、Teamのページに投稿されたディスカッションを取得、作成、編集、削除できます。 versions: fpt: '*' ghes: '*' diff --git a/translations/ja-JP/content/rest/teams/external-groups.md b/translations/ja-JP/content/rest/teams/external-groups.md index 1a18e8b97a..6d359dbdca 100644 --- a/translations/ja-JP/content/rest/teams/external-groups.md +++ b/translations/ja-JP/content/rest/teams/external-groups.md @@ -1,6 +1,6 @@ --- -title: External Groups -intro: The external groups API allows you to view the external identity provider groups that are available to your organization and manage the connection between external groups and teams in your organization. +title: 外部グループ +intro: 外部グループAPIを使用すると、Organizationで利用できる外部のアイデンティティプロバイダグループを見て、Organization内での外部グループとTeamの接続を管理できます。 versions: fpt: '*' ghae: '*' @@ -17,8 +17,8 @@ miniTocMaxHeadingLevel: 3 **ノート:** -- The external groups API is only available for organizations that are part of a enterprise using {% data variables.product.prodname_emus %}. For more information, see "[About Enterprise Managed Users](/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)." -- If your organization uses team synchronization, you can use the Team Synchronization API. For more information, see "[Team synchronization API](#team-synchronization)." +- 外部グループAPIは、{% data variables.product.prodname_emus %}を使用しているEnterpriseの一部であるOrganizationでのみ利用できます。 詳しい情報については「[Enterpriseが管理しているユーザ](/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)」を参照してください。 +- OrganizationがTeam同期を使用している場合、Team Synchronization APIが利用できます。 詳しい情報については「[Team synchronization API](#team-synchronization)」を参照してください。 {% endnote %} {% endif %} diff --git a/translations/ja-JP/content/rest/teams/team-sync.md b/translations/ja-JP/content/rest/teams/team-sync.md index 650b0825e1..a8f6a635bc 100644 --- a/translations/ja-JP/content/rest/teams/team-sync.md +++ b/translations/ja-JP/content/rest/teams/team-sync.md @@ -1,5 +1,5 @@ --- -title: Team Synchronization +title: Team同期 intro: 'Team Synchronization API では、{% data variables.product.product_name %} Team と外部アイデンティティプロバイダ (IdP) グループとの間の接続を管理できます。' versions: fpt: '*' @@ -16,6 +16,6 @@ Team 同期を使用して、IdPを通じて GitHubTeamメンバーを管理で {% note %} -**Note:** The Team Synchronization API cannot be used with {% data variables.product.prodname_emus %}. To learn more about managing an {% data variables.product.prodname_emu_org %}, see "[External groups API](/enterprise-cloud@latest/rest/reference/teams#external-groups)". +**ノート:** Team Synchronization APIは{% data variables.product.prodname_emus %}とともに利用することはできません。 {% data variables.product.prodname_emu_org %}の管理についてさらに学ぶには、「[外部グループAPI](/enterprise-cloud@latest/rest/reference/teams#external-groups)」を参照してください。 {% endnote %} diff --git a/translations/ja-JP/content/rest/teams/teams.md b/translations/ja-JP/content/rest/teams/teams.md index e7809e0193..239e96d72a 100644 --- a/translations/ja-JP/content/rest/teams/teams.md +++ b/translations/ja-JP/content/rest/teams/teams.md @@ -1,6 +1,6 @@ --- title: Team -intro: 'With the Teams API, you can create and manage teams in your GitHub organization.' +intro: Team APIを使うと、GitHub Organization内のTeamの作成や管理ができます。 versions: fpt: '*' ghes: '*' diff --git a/translations/ja-JP/content/rest/users/blocking.md b/translations/ja-JP/content/rest/users/blocking.md index 78f25ec240..e67d0b9b7d 100644 --- a/translations/ja-JP/content/rest/users/blocking.md +++ b/translations/ja-JP/content/rest/users/blocking.md @@ -1,5 +1,5 @@ --- -title: Blocking Users +title: ユーザのブロック intro: '' versions: fpt: '*' diff --git a/translations/ja-JP/content/rest/users/gpg-keys.md b/translations/ja-JP/content/rest/users/gpg-keys.md index 8e3337e95a..060066f4d2 100644 --- a/translations/ja-JP/content/rest/users/gpg-keys.md +++ b/translations/ja-JP/content/rest/users/gpg-keys.md @@ -1,5 +1,5 @@ --- -title: GPG Keys +title: GPGキー intro: '' versions: fpt: '*' diff --git a/translations/ja-JP/content/rest/users/keys.md b/translations/ja-JP/content/rest/users/keys.md index c0383ea886..c8ec6833fe 100644 --- a/translations/ja-JP/content/rest/users/keys.md +++ b/translations/ja-JP/content/rest/users/keys.md @@ -1,5 +1,5 @@ --- -title: Git SSH Keys +title: Git SSHキー intro: '' versions: fpt: '*' diff --git a/translations/ja-JP/content/rest/webhooks/index.md b/translations/ja-JP/content/rest/webhooks/index.md index 9f292b5c72..c2e630cac6 100644 --- a/translations/ja-JP/content/rest/webhooks/index.md +++ b/translations/ja-JP/content/rest/webhooks/index.md @@ -18,11 +18,11 @@ redirect_from: - /rest/reference/webhooks --- -Repository webhooks allow you to receive HTTP `POST` payloads whenever certain events happen in a repository. {% data reusables.webhooks.webhooks-rest-api-links %} +リポジトリwebhookを使用すると、リポジトリで特定のイベントが発生するとき必ずHTTP `POST` ペイロードを受け取ることができます。 {% data reusables.webhooks.webhooks-rest-api-links %} Organization のすべてのリポジトリからイベントを受信するため単一の webhook を設定する場合は、[Organization Webhooks](/rest/reference/orgs#webhooks) の API ドキュメントを参照してください。 -In addition to the REST API, {% data variables.product.prodname_dotcom %} can also serve as a [PubSubHubbub](#pubsubhubbub) hub for repositories. +REST APIに加えて、{% data variables.product.prodname_dotcom %}はリポジトリの[PubSubHubbub](#pubsubhubbub)ハブとしても動作します。 ## webhook の受信 diff --git a/translations/ja-JP/content/rest/webhooks/repo-config.md b/translations/ja-JP/content/rest/webhooks/repo-config.md index 889e95cdb8..4f46542a1d 100644 --- a/translations/ja-JP/content/rest/webhooks/repo-config.md +++ b/translations/ja-JP/content/rest/webhooks/repo-config.md @@ -1,5 +1,5 @@ --- -title: Repository Webhook Configuration +title: リポジトリwebhookの設定 intro: '' versions: fpt: '*' diff --git a/translations/ja-JP/content/rest/webhooks/repo-deliveries.md b/translations/ja-JP/content/rest/webhooks/repo-deliveries.md index ae159e14a5..7d4791387b 100644 --- a/translations/ja-JP/content/rest/webhooks/repo-deliveries.md +++ b/translations/ja-JP/content/rest/webhooks/repo-deliveries.md @@ -1,5 +1,5 @@ --- -title: Repository Webhook Deliveries +title: リポジトリwebhookのデリバリ intro: '' versions: fpt: '*' diff --git a/translations/ja-JP/content/rest/webhooks/repos.md b/translations/ja-JP/content/rest/webhooks/repos.md index 55bc892fc3..14f018581b 100644 --- a/translations/ja-JP/content/rest/webhooks/repos.md +++ b/translations/ja-JP/content/rest/webhooks/repos.md @@ -1,5 +1,5 @@ --- -title: Repository Webhooks +title: リポジトリwebhook intro: '' versions: fpt: '*' diff --git a/translations/ja-JP/data/release-notes/enterprise-server/3-4/1.yml b/translations/ja-JP/data/release-notes/enterprise-server/3-4/1.yml index 678b57e0df..feafe23ab0 100644 --- a/translations/ja-JP/data/release-notes/enterprise-server/3-4/1.yml +++ b/translations/ja-JP/data/release-notes/enterprise-server/3-4/1.yml @@ -47,7 +47,6 @@ sections: - When "Users can search GitHub.com" is enabled with {% data variables.product.prodname_github_connect %}, issues in private and internal repositories are not included in {% data variables.product.prodname_dotcom_the_website %} search results. - '{% data variables.product.prodname_registry %}のnpmレジストリは、メタデータのレスポンス中で時間の値を返さなくなります。これは、大きなパフォーマンス改善のために行われました。メタデータレスポンスの一部として時間の値を返すために必要なすべてのデータは保持し続け、既存のパフォーマンスの問題を解決した将来に、この値を返すことを再開します。' - pre-receive フックの処理に固有のリソース制限によって、pre-receive フックに失敗するものが生じることがあります。 - - Actions services need to be restarted after restoring appliance from backup taken on a different host. - | When using SAML encrypted assertions with {% data variables.product.prodname_ghe_server %} 3.4.0 and 3.4.1, a new XML attribute `WantAssertionsEncrypted` in the `SPSSODescriptor` contains an invalid attribute for SAML metadata. IdPs that consume this SAML metadata endpoint may encounter errors when validating the SAML metadata XML schema. A fix will be available in the next patch release. [Updated: 2022-04-11] diff --git a/translations/ja-JP/data/release-notes/enterprise-server/3-4/2.yml b/translations/ja-JP/data/release-notes/enterprise-server/3-4/2.yml index 1ff5796d70..3e46593b3b 100644 --- a/translations/ja-JP/data/release-notes/enterprise-server/3-4/2.yml +++ b/translations/ja-JP/data/release-notes/enterprise-server/3-4/2.yml @@ -32,7 +32,6 @@ sections: - When "Users can search GitHub.com" is enabled with {% data variables.product.prodname_github_connect %}, issues in private and internal repositories are not included in {% data variables.product.prodname_dotcom_the_website %} search results. - '{% data variables.product.prodname_registry %}のnpmレジストリは、メタデータのレスポンス中で時間の値を返さなくなります。これは、大きなパフォーマンス改善のために行われました。メタデータレスポンスの一部として時間の値を返すために必要なすべてのデータは保持し続け、既存のパフォーマンスの問題を解決した将来に、この値を返すことを再開します。' - pre-receive フックの処理に固有のリソース制限によって、pre-receive フックに失敗するものが生じることがあります。 - - Actions services need to be restarted after restoring appliance from backup taken on a different host. - | When using SAML encrypted assertions with {% data variables.product.prodname_ghe_server %} 3.4.0 and 3.4.1, a new XML attribute `WantAssertionsEncrypted` in the `SPSSODescriptor` contains an invalid attribute for SAML metadata. IdPs that consume this SAML metadata endpoint may encounter errors when validating the SAML metadata XML schema. A fix will be available in the next patch release. [Updated: 2022-04-11] diff --git a/translations/ja-JP/data/reusables/actions/supported-github-runners.md b/translations/ja-JP/data/reusables/actions/supported-github-runners.md index 1d74c08a3a..57616a96a6 100644 --- a/translations/ja-JP/data/reusables/actions/supported-github-runners.md +++ b/translations/ja-JP/data/reusables/actions/supported-github-runners.md @@ -50,6 +50,17 @@ Ubuntu 18.04 +macOS Monterey 12 + + +macos-12 + + +macOS 12 is currently in public beta. + + + + macOS Big Sur 11 diff --git a/translations/ja-JP/data/reusables/codespaces/codespaces-org-policies.md b/translations/ja-JP/data/reusables/codespaces/codespaces-org-policies.md new file mode 100644 index 0000000000..776a08709f --- /dev/null +++ b/translations/ja-JP/data/reusables/codespaces/codespaces-org-policies.md @@ -0,0 +1,3 @@ +1. In the "Code, planning, and automation" section of the sidebar, select **{% octicon "codespaces" aria-label="The codespaces icon" %} {% data variables.product.prodname_codespaces %}** then click **Policies**. +1. On the "Codespace policies" page, click **Create Policy**. +1. Enter a name for your new policy. \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/codespaces/codespaces-policy-targets.md b/translations/ja-JP/data/reusables/codespaces/codespaces-policy-targets.md new file mode 100644 index 0000000000..04e4a9bfda --- /dev/null +++ b/translations/ja-JP/data/reusables/codespaces/codespaces-policy-targets.md @@ -0,0 +1,11 @@ +1. In the "Change policy target" area, click the dropdown button. +1. Choose either **All repositories** or **Selected repositories** to determine which repositories this policy will apply to. +1. [**Selected repositories**] を選択した場合、以下の手順に従います。 + 1. {% octicon "gear" aria-label="The settings icon" %} をクリックします。 + + ![Edit the settings for the policy](/assets/images/help/codespaces/policy-edit.png) + + 2. Select the repositories you want this policy to apply to. + 3. At the bottom of the repository list, click **Select repositories**. + + ![Select repositories for this policy](/assets/images/help/codespaces/policy-select-repos.png) diff --git a/translations/ja-JP/data/reusables/projects/access-insights.md b/translations/ja-JP/data/reusables/projects/access-insights.md index 4c7cf259d0..07383bb1f0 100644 --- a/translations/ja-JP/data/reusables/projects/access-insights.md +++ b/translations/ja-JP/data/reusables/projects/access-insights.md @@ -1,4 +1,4 @@ -1. Navigate to your project. +1. プロジェクトにアクセスします。 2. In the top-right, to access insights, click {% octicon "graph" aria-label="the graph icon" %}. {% note %} diff --git a/translations/ja-JP/data/reusables/projects/enable-basic-workflow.md b/translations/ja-JP/data/reusables/projects/enable-basic-workflow.md index fa23f9b50d..7fec011d57 100644 --- a/translations/ja-JP/data/reusables/projects/enable-basic-workflow.md +++ b/translations/ja-JP/data/reusables/projects/enable-basic-workflow.md @@ -1,4 +1,6 @@ -1. In your project, click {% octicon "workflow" aria-label="the workflow icon" %}. +1. プロジェクトにアクセスします。 +1. In the top-right, click {% octicon "kebab-horizontal" aria-label="The menu icon" %} to open the menu. +1. In the menu, click {% octicon "workflow" aria-label="The workflow icon" %} **Workflows**. 1. Under **Default workflows**, click on the workflow that you want to edit. 1. If the workflow can apply to both issues and pull requests, next to **When**, check the item type(s) that you want to act on. 1. Next to **Set**, choose the value that you want to set the status to. diff --git a/translations/ja-JP/data/reusables/projects/project-settings.md b/translations/ja-JP/data/reusables/projects/project-settings.md index bee73a5c66..9005046592 100644 --- a/translations/ja-JP/data/reusables/projects/project-settings.md +++ b/translations/ja-JP/data/reusables/projects/project-settings.md @@ -1,2 +1,3 @@ -1. Navigate to your project. -1. Click {% octicon "gear" aria-label="the gear icon" %} to access the project settings. +1. プロジェクトにアクセスします。 +1. In the top-right, click {% octicon "kebab-horizontal" aria-label="The menu icon" %} to open the menu. +1. In the menu, click {% octicon "gear" aria-label="The gear icon" %} **Settings** to access the project settings. diff --git a/translations/log/es-resets.csv b/translations/log/es-resets.csv index 80c49cc626..d3610cf372 100644 --- a/translations/log/es-resets.csv +++ b/translations/log/es-resets.csv @@ -27,7 +27,7 @@ translations/es-ES/content/actions/hosting-your-own-runners/adding-self-hosted-r translations/es-ES/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md,broken liquid tags translations/es-ES/content/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners.md,Listed in localization-support#489 translations/es-ES/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md,Listed in localization-support#489 -translations/es-ES/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md,broken liquid tags +translations/es-ES/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md,rendering error translations/es-ES/content/actions/index.md,Listed in localization-support#489 translations/es-ES/content/actions/learn-github-actions/contexts.md,Listed in localization-support#489 translations/es-ES/content/actions/learn-github-actions/environment-variables.md,Listed in localization-support#489 @@ -312,6 +312,7 @@ translations/es-ES/data/reusables/actions/contacting-support.md,broken liquid ta translations/es-ES/data/reusables/actions/enterprise-marketplace-actions.md,broken liquid tags translations/es-ES/data/reusables/actions/enterprise-storage-ha-backups.md,broken liquid tags translations/es-ES/data/reusables/actions/settings-ui/settings-actions-runner-groups.md,rendering error +translations/es-ES/data/reusables/actions/settings-ui/settings-actions-runners.md,rendering error translations/es-ES/data/reusables/code-scanning/codeql-context-for-actions-and-third-party-tools.md,broken liquid tags translations/es-ES/data/reusables/code-scanning/edit-workflow.md,broken liquid tags translations/es-ES/data/reusables/code-scanning/enabling-options.md,broken liquid tags diff --git a/translations/pt-BR/content/actions/using-workflows/about-workflows.md b/translations/pt-BR/content/actions/using-workflows/about-workflows.md index 3507a49eee..8e8685e4f2 100644 --- a/translations/pt-BR/content/actions/using-workflows/about-workflows.md +++ b/translations/pt-BR/content/actions/using-workflows/about-workflows.md @@ -28,7 +28,7 @@ Um fluxo de trabalho deve conter os seguintes componentes básicos: 1. Um ou mais _trabalhos_, cada uma das quais será executado em uma máquina de _executor_ e executará uma série de uma ou mais _etapas_. 1. Cada etapa pode executar um script que você define ou executa uma ação, que é uma extensão reutilizável que pode simplificar seu fluxo de trabalho. -Para obter mais informações sobre esses componentes básicos, consulte "[Entendendo GitHub Actions](/actions/learn-github-actions/understanding-github-actions#the-components-of-github-actions)". +For more information on these basic components, see "[Understanding GitHub Actions](/actions/learn-github-actions/understanding-github-actions#the-components-of-github-actions)." ![Visão geral do fluxo de trabalho](/assets/images/help/images/overview-actions-simple.png) diff --git a/translations/pt-BR/content/admin/all-releases.md b/translations/pt-BR/content/admin/all-releases.md index 5e14a492e0..c138956f41 100644 --- a/translations/pt-BR/content/admin/all-releases.md +++ b/translations/pt-BR/content/admin/all-releases.md @@ -20,9 +20,9 @@ Você pode ver o que há de novo para cada versão nas [observações da versão {% data variables.product.company_short %} é compatível com as seguintes versões de {% data variables.product.product_name %}. Para obter mais informações sobre a última versão, consulte o [side de {% data variables.product.prodname_enterprise %}](https://github.com/enterprise). -| Versão | Versão | Deprecation | Notas de lançamento | Documentação | -|:------ |:------ |:----------- |:------------------- |:------------ | -| | | | | | +| Versão | Versão | Descontinuação | Notas de lançamento | Documentação | +|:------ |:------ |:-------------- |:------------------- |:------------ | +| | | | | | {%- for version in enterpriseServerReleases.supported %} | {{version}} | {{enterpriseServerReleases.dates[version].releaseDate}} | {{enterpriseServerReleases.dates[version].deprecationDate}} | [{{version}} observações da versão](/enterprise-server@{{version}}/admin/release-notes) | [{{version}} documentation](/enterprise-server@{{version}}) | {%- endfor %} @@ -31,9 +31,9 @@ Você pode ver o que há de novo para cada versão nas [observações da versão {% data variables.product.company_short %} fornece documentação para versões obsoletas, mas não mantém ou atualiza a documentação. -| Versão | Versão | Deprecation | Notas de lançamento | Documentação | -|:------ |:------ |:----------- |:------------------- |:------------ | -| | | | | | +| Versão | Versão | Descontinuação | Notas de lançamento | Documentação | +|:------ |:------ |:-------------- |:------------------- |:------------ | +| | | | | | {%- for version in enterpriseServerReleases.deprecatedReleasesWithNewFormat %} | {{version}} | {{enterpriseServerReleases.dates[version].releaseDate}} | {{enterpriseServerReleases.dates[version].deprecationDate}} | [{{version}} observações da versão](/enterprise-server@{{version}}/admin/release-notes) | [{{version}} documentation](/enterprise-server@{{version}}) | {%- endfor %} @@ -43,11 +43,11 @@ Você pode ver o que há de novo para cada versão nas [observações da versão ### Documentação de desenvolvedor descontinuada -{% data variables.product.company_short %} hosted developer documentation for {% data variables.product.product_name %} on a separate site until the 2.17 release. {% data variables.product.company_short %} continues to provide developer documentation for version 2.16 and earlier, but does not maintain or update the documentation. +{% data variables.product.company_short %} hospedou a documentação do desenvolvedor para {% data variables.product.product_name %} em um site separado até a versão 2.17. {% data variables.product.company_short %} continua fornecendo a documentação de desenvolvedor para a versão 2.16 e anterior, mas não mantém ou atualiza a documentação. -| Versão | Versão | Deprecation | Developer documentation | -|:------ |:------ |:----------- |:----------------------- | -| | | | | +| Versão | Versão | Descontinuação | Documentação do desenvolvedor | +|:------ |:------ |:-------------- |:----------------------------- | +| | | | | {%- for version in enterpriseServerReleases.deprecatedReleasesOnDeveloperSite %} -| {{version}} | {{enterpriseServerReleases.dates[version].releaseDate}} | {{enterpriseServerReleases.dates[version].deprecationDate}} | [{{version}} developer documentation](https://developer.github.com/enterprise/{{version}}) | +| {{version}} | {{enterpriseServerReleases.dates[version].releaseDate}} | {{enterpriseServerReleases.dates[version].deprecationDate}} | [{{version}} documentação do desenvolvedor](https://developer.github.com/enterprise/{{version}}) | {%- endfor %} diff --git a/translations/pt-BR/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/deploying-github-advanced-security-in-your-enterprise.md b/translations/pt-BR/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/deploying-github-advanced-security-in-your-enterprise.md index 416632f7c5..013f62d832 100644 --- a/translations/pt-BR/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/deploying-github-advanced-security-in-your-enterprise.md +++ b/translations/pt-BR/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/deploying-github-advanced-security-in-your-enterprise.md @@ -235,7 +235,7 @@ Com a digitalização de código, você pode encontrar vulnerabilidades e erros Quando a digitalização de código identifica um problema em um pull request, você poderá revisar o código destacado e resolver o alerta. Para obter mais informações, consulte "[Triar alertas de {% data variables.product.prodname_code_scanning %} em pull requests](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests)". -Se você tiver permissão de gravação em um repositório, você poderá gerenciar alertas de digitalização de código para esse repositório. With write permission to a repository, {% if delete-code-scanning-alerts %}you can view, fix, dismiss, or delete alerts {% else %}you can view, fix, or dismiss alerts{% endif %} for potential vulnerabilities or errors in your repository's code. Para obter mais informações, consulte "[Gerenciar alertas de varredura de código para seu repositório](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository). " +Se você tiver permissão de gravação em um repositório, você poderá gerenciar alertas de digitalização de código para esse repositório. Com permissão de gravação em um repositório, {% if delete-code-scanning-alerts %}você pode visualizar, corrigir, descartar ou excluir alertas {% else %}que você pode visualizar, corrigir ou descartar alertas{% endif %} para possíveis vulnerabilidades ou erros no código do seu repositório. Para obter mais informações, consulte "[Gerenciar alertas de varredura de código para seu repositório](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository). " #### Gerar relatórios de alertas de {% data variables.product.prodname_code_scanning %} diff --git a/translations/pt-BR/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-minio-gateway-for-nas-storage.md b/translations/pt-BR/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-minio-gateway-for-nas-storage.md index b1b54f7b98..58a0072745 100644 --- a/translations/pt-BR/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-minio-gateway-for-nas-storage.md +++ b/translations/pt-BR/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-minio-gateway-for-nas-storage.md @@ -15,9 +15,13 @@ redirect_from: shortTitle: MinIO Gateway para armazenamento NAS --- -## Pré-requisitos +{% warning %} -{% data reusables.actions.enterprise-s3-support-warning %} +**Warning**: MinIO has announced removal of MinIO Gateways. Starting June 1st, 2022, support and bug fixes for the current MinIO NAS Gateway implementation will only be available for paid customers via their LTS support contract. If you want to continue using MinIO Gateways with {% data variables.product.prodname_actions %}, we recommend moving to MinIO LTS support. For more information, see [Scheduled removal of MinIO Gateway for GCS, Azure, HDFS](https://github.com/minio/minio/issues/14331) in the minio/minio repository. + +{% endwarning %} + +## Pré-requisitos Antes de habilitar {% data variables.product.prodname_actions %}, certifique-se de que você realizou os seguintes passos: diff --git a/translations/pt-BR/content/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise.md b/translations/pt-BR/content/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise.md index 1c1b8d6783..de1f4ddbbe 100644 --- a/translations/pt-BR/content/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise.md +++ b/translations/pt-BR/content/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise.md @@ -48,7 +48,7 @@ Cada ação é um repositório na organização de `ações`, e cada repositóri **Notas:** - Ao usar ações de configuração (como `actions/setup-LANGUAGE`) em {% data variables.product.product_name %} com executores auto-hospedados, você pode precisar configurar o armazenamento de ferramentas em executores que não possuem acesso à internet. Para obter mais informações, consulte "[Configurar o cache da ferramenta em executores auto-hospedados sem acesso à internet](/enterprise/admin/github-actions/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access)". -- As atualizações para {% data variables.product.product_name %} não a atualização de ações agregadas. +- Bundled actions are automatically updated when {% data variables.product.product_name %} is updated. {% endnote %} diff --git a/translations/pt-BR/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication.md b/translations/pt-BR/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication.md index 2899521bb9..c6a1e83cf8 100644 --- a/translations/pt-BR/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication.md +++ b/translations/pt-BR/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication.md @@ -40,42 +40,42 @@ Se você usar uma empresa com {% data variables.product.prodname_emus %}, os int Os nomes de usuário para contas de usuário em {% ifversion ghes or ghae %}{% data variables.product.product_name %}{% elsif ghec %}{% data variables.product.prodname_dotcom_the_website %}{% endif %} podem conter apenas caracteres alfanuméricos e traços (`-`). -{% ifversion ghec or ghes %}Ao configurar {% ifversion ghes %}autenticação de CAS, LDAP ou {% endif %}SAML, {% endif %}{% data variables.product.product_name %} usa um identificador da conta de usuário em seu provedor de autenticação externa {% ifversion ghes %}{% elsif ghec or ghae %}IdP{% endif %} para determinar o nome de usuário da conta de usuário correspondente em {% ifversion ghes or ghae %}{% data variables.product.product_name %}{% elsif ghec %}{% data variables.product.prodname_dotcom_the_website %}{% endif %}. If the identifier for the account on your provider includes unsupported characters, {% data variables.product.product_name %} will normalize the username per the following rules. +{% ifversion ghec or ghes %}Ao configurar {% ifversion ghes %}autenticação de CAS, LDAP ou {% endif %}SAML, {% endif %}{% data variables.product.product_name %} usa um identificador da conta de usuário em seu provedor de autenticação externa {% ifversion ghes %}{% elsif ghec or ghae %}IdP{% endif %} para determinar o nome de usuário da conta de usuário correspondente em {% ifversion ghes or ghae %}{% data variables.product.product_name %}{% elsif ghec %}{% data variables.product.prodname_dotcom_the_website %}{% endif %}. Se o identificador da conta no seu provedor incluir caracteres não compatíveis, {% data variables.product.product_name %} normalizará o nome de usuário por cada regra a seguir. -1. {% data variables.product.product_name %} will normalize any non-alphanumeric character in your account's username into a dash. For example, a username of `mona.the.octocat` will be normalized to `mona-the-octocat`. Observe que nomes de usuários normalizados também não podem iniciar ou terminar com um traço. Eles também não podem conter dois traços consecutivos. +1. {% data variables.product.product_name %} normalizará qualquer caractere não alfanumérico do nome de usuário da sua conta em um traço. Por exemplo, um nome de usuário de `mona.the.octocat` será normalizado para `mona-the-octocat`. Observe que nomes de usuários normalizados também não podem iniciar ou terminar com um traço. Eles também não podem conter dois traços consecutivos. 1. Nomes de usuário criados a partir de endereços de e-mail são criados a partir dos caracteres normalizados que precedem o caractere `@`. -1. If multiple accounts are normalized into the same {% data variables.product.product_name %} username, only the first user account is created. Usuários subsequentes com o mesmo nome de usuário não serão capazes de fazer o login. +1. Se várias contas forem normalizadas para o mesmo nome de usuário {% data variables.product.product_name %}, será criada apenas a primeira conta de usuário. Usuários subsequentes com o mesmo nome de usuário não serão capazes de fazer o login. -### Examples of username normalization +### Exemplos de normalização de nome de usuário -| Identifier on provider | Normalized username for {% data variables.product.product_location %} | Resultado | -|:----------------------- |:--------------------------------------------------------------------- |:--------------------------------------------------------------------------------------------------- | -| The.Octocat | `the-octocat` | Nome de usuário criado com sucesso. | -| !The.Octocat | `-the-octocat` | Este nome de usuário não é criado, porque começa com um traço. | -| The.Octocat! | `the-octocat-` | Este nome de usuário não é criado, porque termina com um traço. | -| The!!Octocat | `the--octocat` | Este nome de usuário não é criado, porque contém dois traços consecutivos. | -| The!Octocat | `the-octocat` | Este nome de usuário não é criado. Embora o nome de usuário normalizado seja válido, ele já existe. | -| The.Octocat@example.com | `the-octocat` | Este nome de usuário não é criado. Embora o nome de usuário normalizado seja válido, ele já existe. | +| Identificador no provedor | Nome de usuário normalizado para {% data variables.product.product_location %} | Resultado | +|:------------------------- |:------------------------------------------------------------------------------ |:--------------------------------------------------------------------------------------------------- | +| The.Octocat | `the-octocat` | Nome de usuário criado com sucesso. | +| !The.Octocat | `-the-octocat` | Este nome de usuário não é criado, porque começa com um traço. | +| The.Octocat! | `the-octocat-` | Este nome de usuário não é criado, porque termina com um traço. | +| The!!Octocat | `the--octocat` | Este nome de usuário não é criado, porque contém dois traços consecutivos. | +| The!Octocat | `the-octocat` | Este nome de usuário não é criado. Embora o nome de usuário normalizado seja válido, ele já existe. | +| The.Octocat@example.com | `the-octocat` | Este nome de usuário não é criado. Embora o nome de usuário normalizado seja válido, ele já existe. | -### About username normalization with SAML +### Sobre a normalização de usuário com SAML -{% ifversion ghec or ghes %}If you {% ifversion ghec %}use an enterprise with {% data variables.product.prodname_emus %}, you must use SAML authentication. {% else %}configure SAML authentication for {% data variables.product.product_location %}, {% endif %}{% endif %}{% data variables.product.product_name %} determines each person's username by one of the following assertions in the SAML response, ordered by priority. +{% ifversion ghec or ghes %}Se você {% ifversion ghec %}usar uma empresa com {% data variables.product.prodname_emus %}, você deverá usar a autenticação do SAML. {% else %}A configuração da autenticação do SAML para {% data variables.product.product_location %}, {% endif %}{% endif %}{% data variables.product.product_name %} determina o nome de usuário de cada pessoa por uma das seguintes afirmações na resposta SAML, ordenada por prioridade. -1. The custom `username` attribute, if defined and present +1. O atributo `de nome de usuário` personalizado, se definido e presente 1. Declaração `http://schemas.xmlsoap.org/ws/2005/05/identity/claims/name`, se houver; 1. Declaração `http://schemas.xmlsoap.org/ws/2005/05/identity/claims/emailaddress`, se houver; 1. Elemento `NameID`. -{% data variables.product.product_name %} requires the `NameID` element even if other attributes are present. For more information, see "[SAML configuration reference](/admin/identity-and-access-management/using-saml-for-enterprise-iam/saml-configuration-reference#saml-attributes)." +{% data variables.product.product_name %} exige o elemento `NameID` mesmo que outros atributos estejam presentes. Para obter mais informações, consulte "[Referência de configuração do SAML](/admin/identity-and-access-management/using-saml-for-enterprise-iam/saml-configuration-reference#saml-attributes)". -{% data variables.product.product_name %} creates a mapping between the `NameID` from the IdP and the username {% ifversion ghec or ghae %}in{% elsif ghes %}on{% endif %} {% data variables.product.product_location %}, so the `NameID` should be persistent, unique, and not subject to change for the lifecycle of the user. +{% data variables.product.product_name %} cria um mapeamento entre `NameID` do IdP e o nome de usuário {% ifversion ghec or ghae %}em{% elsif ghes %}em{% endif %} {% data variables.product.product_location %}. Portanto, o `NameID` deve ser persistente, único e não sujeito a alterações para o ciclo de vida do usuário. {% ifversion ghes %} {% note %} -**Note**: If the `NameID` for a user does change on the IdP, the person will see an error message when {% ifversion ghec %}authenticating through your IdP to access your resources on{% else %}signing into{% endif} {% data variables.product.product_location %}. To restore the person's access, you'll need to update the user account's `NameID` mapping. For more information, see "[Updating a user's SAML `NameID`](/admin/identity-and-access-management/using-saml-for-enterprise-iam/updating-a-users-saml-nameid)." +**Observação**: Se `NameID` para um usuário for alterado no IdP, a pessoa verá uma mensagem de erro ao {% ifversion ghec %}efetuar a autenticação através do seu IdP para acessar seus recursos ao{% else %}efetuar o login em{% endif} {% data variables.product.product_location %}. Para restaurar o acesso da pessoa, você deverá atualizar o mapeamento de `NameID` da conta do usuário. Para obter mais informações, consulte "[Atualizando `NameID`](/admin/identity-and-access-management/using-saml-for-enterprise-iam/updating-a-users-saml-nameid) do SAML de um usuário." {% endnote %} {% endif %} diff --git a/translations/pt-BR/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-saml-single-sign-on-for-your-enterprise.md b/translations/pt-BR/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-saml-single-sign-on-for-your-enterprise.md index 82fbebae43..8a073129b0 100644 --- a/translations/pt-BR/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-saml-single-sign-on-for-your-enterprise.md +++ b/translations/pt-BR/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-saml-single-sign-on-for-your-enterprise.md @@ -1,7 +1,7 @@ --- title: Configurar o logon único SAML para sua empresa shortTitle: Configurar o SAML SSO -intro: 'You can control and secure access to {% ifversion ghec %}resources like repositories, issues, and pull requests within your enterprise''s organizations{% elsif ghes %}{% data variables.product.product_location %}{% elsif ghae %}your enterprise on {% data variables.product.prodname_ghe_managed %}{% endif %} by {% ifversion ghec %}enforcing{% elsif ghes or ghae %}configuring{% endif %} SAML single sign-on (SSO) through your identity provider (IdP).' +intro: 'Você pode controlar e proteger o acesso a recursos {% ifversion ghec %}, como repositórios, problemas e pull requests dentro das organizações da sua empresa{% elsif ghes %}{% data variables.product.product_location %}{% elsif ghae %}sua empresa em {% data variables.product.prodname_ghe_managed %}{% endif %}, {% ifversion ghec %}{% elsif ghes or ghae %}configurando{% endif %} o logon único SAML (SSO) através do seu provedor de identidade (IdP).' permissions: '{% ifversion ghes %}Site administrators{% elsif ghec or ghae %}Enterprise owners{% endif %} can configure SAML SSO for {% ifversion ghec or ghae %}an enterprise on {% data variables.product.product_name %}{% elsif ghes %}a {% data variables.product.product_name %} instance{% endif %}.' versions: ghec: '*' @@ -65,7 +65,7 @@ Depois que um usuário efetua a autenticação com sucesso no seu IdP, a sessão ## Considerações de nome de usuário no SAML -{% ifversion ghec %}If you use {% data variables.product.prodname_emus %}, {% endif %}{% data reusables.enterprise_user_management.consider-usernames-for-external-authentication %} For more information, see "[Username considerations for external authentication](/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication)." +{% ifversion ghec %}Se você usar {% data variables.product.prodname_emus %}, {% endif %}{% data reusables.enterprise_user_management.consider-usernames-for-external-authentication %} Para obter mais informações, consulte "[Considerações de nome de usuário para autenticação externa](/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication)". ## Aplicar o logon único SAML para organizações na sua conta corporativa @@ -97,7 +97,7 @@ Para obter informações mais detalhadas sobre como habilitar o SAML usando o Ok ## Configurando o SAML SSO -Você pode habilitar ou desabilitar a autenticação do SAML para {% data variables.product.product_location %} ou você pode editar uma configuração existente. You can view and edit authentication settings for {% data variables.product.product_name %} in the management console. Para obter mais informações, consulte "[Acessando o console de gerenciamento](/admin/configuration/configuring-your-enterprise/accessing-the-management-console)". +Você pode habilitar ou desabilitar a autenticação do SAML para {% data variables.product.product_location %} ou você pode editar uma configuração existente. Você pode ver e editar as configurações de autenticação para {% data variables.product.product_name %} no console de gerenciamento. Para obter mais informações, consulte "[Acessando o console de gerenciamento](/admin/configuration/configuring-your-enterprise/accessing-the-management-console)". {% note %} @@ -156,12 +156,12 @@ Você pode habilitar ou desabilitar a autenticação do SAML para {% data variab Os seguintes IdPs fornecem documentação sobre a configuração de do SAML SSO para {% data variables.product.product_name %}. Se seu IdP não estiver listado, entre em contato com seu IdP para solicitar suporte para {% data variables.product.product_name %}. - | IdP | Mais informações | - |:-------- |:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | - | Azure AD | "[Configuring authentication and provisioning for your enterprise using Azure AD](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad)" | - | Okta | "[Configuring authentication and provisioning for your enterprise using Okta](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-okta)" | + | IdP | Mais informações | + |:-------- |:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | + | Azure AD | "[Configurando autenticação e provisionamento para a sua empresa usando o Azure AD](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad)" | + | Okta | "[Configurando a autenticação e o provisionamento para sua empresa usando o Okta](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-okta)" | -During initialization for {% data variables.product.product_name %}, you must configure {% data variables.product.product_name %} as a SAML service provider (SP) on your IdP. Você deve inserir vários valores únicos no seu IdP para configurar {% data variables.product.product_name %} como um SP válido. For more information, see "[SAML configuration reference](/admin/identity-and-access-management/using-saml-for-enterprise-iam/saml-configuration-reference#saml-metadata)." +Durante a inicialização de {% data variables.product.product_name %}, você deve configurar o {% data variables.product.product_name %} como um provedor de serviço SAML (SP) no seu IdP. Você deve inserir vários valores únicos no seu IdP para configurar {% data variables.product.product_name %} como um SP válido. Para obter mais informações, consulte "[Referência de configuração do SAML](/admin/identity-and-access-management/using-saml-for-enterprise-iam/saml-configuration-reference#saml-metadata)". ## Editar a configuração SAML SSO @@ -219,10 +219,10 @@ Se os detalhes para o seu IdP forem alterados, você deverá editar a configura ## Leia mais {%- ifversion ghec %} -- "[Managing SAML single sign-on for your organization](/organizations/managing-saml-single-sign-on-for-your-organization)" +- "[Gerenciando o logon único SAML para sua organização](/organizations/managing-saml-single-sign-on-for-your-organization)" {%- endif %} {%- ifversion ghes %} -- "[Promoting or demoting a site administrator](/admin/user-management/managing-users-in-your-enterprise/promoting-or-demoting-a-site-administrator)" +- "[Promovendo ou rebaixando um administrador do site](/admin/user-management/managing-users-in-your-enterprise/promoting-or-demoting-a-site-administrator)" {%- endif %} {% endif %} diff --git a/translations/pt-BR/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/troubleshooting-saml-authentication.md b/translations/pt-BR/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/troubleshooting-saml-authentication.md index e963d40925..edd6193e65 100644 --- a/translations/pt-BR/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/troubleshooting-saml-authentication.md +++ b/translations/pt-BR/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/troubleshooting-saml-authentication.md @@ -65,7 +65,7 @@ Quando o usuário inicia a sessão novamente, {% data variables.product.prodname > Outro usuário já possui a conta. Solicite ao administrador que verifique o registro de autenticação. -De modo geral, a mensagem indica que o nome de usuário ou endereço de email da pessoa foi alterado no IdP. Certifique-se de que o mapeamento do `NameID` para a conta do usuário no {% data variables.product.prodname_ghe_server %} corresponde ao `NameID` do usuário no seu IdP. For more information, see "[Updating a user's SAML `NameID`](/admin/identity-and-access-management/using-saml-for-enterprise-iam/updating-a-users-saml-nameid)." +De modo geral, a mensagem indica que o nome de usuário ou endereço de email da pessoa foi alterado no IdP. Certifique-se de que o mapeamento do `NameID` para a conta do usuário no {% data variables.product.prodname_ghe_server %} corresponde ao `NameID` do usuário no seu IdP. Para obter mais informações, consulte "[Atualizando `NameID`](/admin/identity-and-access-management/using-saml-for-enterprise-iam/updating-a-users-saml-nameid) do SAML de um usuário." ## Se a resposta SAML não estiver assinada ou se a assinatura não corresponder ao conteúdo, o log de autenticação mostrará a seguinte mensagem de erro: diff --git a/translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise.md b/translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise.md index 95eed7e1ac..64ffa3d00c 100644 --- a/translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise.md +++ b/translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise.md @@ -362,7 +362,7 @@ topics: | `external_identity.update` | As configurações do Okta foram atualizadas. Para obter mais informações, consulte "[Mapeando grupos do Okta nas equipes](/admin/identity-and-access-management/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams)". | {%- endif %} -### `gist` category actions +### Ações da categoria `gist` | Ação | Descrição | | ------------------------ | --------------------------------------- | @@ -386,11 +386,11 @@ topics: | ---- | --------- | | | | {%- ifversion ghes or ghae %} -| `hook.active_changed` | A hook's active status was updated. +| `hook.active_changed` | O status ativo de um hook foi atualizado. {%- endif %} -| `hook.config_changed` | A hook's configuration was changed. | `hook.create` | A new hook was added. | `hook.destroy` | A hook was deleted. | `hook.events_changed` | A hook's configured events were changed. +| `hook.config_changed` | A configuração do hook foi alterada. | `hook.create` | Um novo hook foi adicionado. | `hook.destroy` | Um hook foi excluído. | `hook.events_changed` | Os eventos configurados de um hook foram alterados. -### `integration` category actions +### Ações da categoria `integration` | Ação | Descrição | | ---------------------------------- | ------------------------------------------------------------------------------------------- | @@ -484,8 +484,8 @@ topics: | `marketplace_listing.change_category` | Uma categoria para um anúncio de um aplicativo em {% data variables.product.prodname_marketplace %} foi alterada. | | `marketplace_listing.create` | Um anúncio para um aplicativo em {% data variables.product.prodname_marketplace %} foi criado. | | `marketplace_listing.delist` | Um anúncio foi removido de {% data variables.product.prodname_marketplace %}. | -| `marketplace_listing.redraft` | A listing was sent back to draft state. | -| `marketplace_listing.reject` | A listing was not accepted for inclusion in {% data variables.product.prodname_marketplace %}. | +| `marketplace_listing.redraft` | Uma listagem foi enviada de volta para o estado rascunho. | +| `marketplace_listing.reject` | A inclusão de uma listagem não foi aceita em {% data variables.product.prodname_marketplace %}. | {%- endif %} ### ações de categoria de `members_can_create_pages` @@ -520,9 +520,9 @@ topics: ### Ações da categoria `members_can_view_dependency_insights` -| Ação | Descrição | -| ---------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `members_can_view_dependency_insights.clear` | An enterprise owner{% ifversion ghes %} or site administrator{% endif %} cleared the policy setting for viewing dependency insights in any organizations in an enterprise.{% ifversion ghec %} For more information, see "[Enforcing a policy for visibility of dependency insights](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-dependency-insights-in-your-enterprise)."{% endif %} +| Ação | Descrição | +| ---------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `members_can_view_dependency_insights.clear` | Um proprietário da empresa{% ifversion ghes %} ou administrador do site{% endif %} limpou a configuração da política para visualizar insights de dependência em qualquer organização de uma empresa.{% ifversion ghec %} Para obter mais informações, consulte "[Aplicando uma política de visibilidade de insights de dependência](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-dependency-insights-in-your-enterprise)".{% endif %} | `members_can_view_dependency_insights.disable` | A habilidade para os integrantes da empresa para visualizar insights de dependência foi desativada. Os integrantes não podem ver insights de dependência em qualquer organização de uma empresa.{% ifversion ghec %} Para obter mais informações, consulte "[Aplicando uma política de visibilidade de insights de dependência](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-dependency-insights-in-your-enterprise)"{% endif %} | `members_can_view_dependency_insights.enable` | A habilidade para os integrantes da empresa para visualizar insights de dependência foi habilitada. Os integrantes podem ver insights de dependência em qualquer organização de uma empresa.{% ifversion ghec %} Para obter mais informações, consulte "[Aplicando uma política de visibilidade de insights de dependência](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-dependency-insights-in-your-enterprise)"{% endif %} @@ -557,9 +557,9 @@ topics: {%- ifversion fpt or ghec %} | `oauth_application.revoke_all_tokens` | Solicitou-se que todos os tokens para um [aplicativo OAuth][] fossem revogados. {%- endif %} -| `oauth_application.revoke_tokens` | Token(s) for an [OAuth application][] were revoked. | `oauth_application.transfer` | An [OAuth application][] was transferred from one user or organization account to another. +| `oauth_application.revoke_tokens` | O(s) token(s) para um [aplicativo OAuth ][] were foi(foram) removido(s). | `oauth_application.transfer` | Um [aplicativo OAuth][] foi transferido da conta de um usuário ou organização para outro. {%- ifversion ghes or ghae %} -| `oauth_application.unsuspend` | An [OAuth application][] was unsuspended for a user or organization account. +| `oauth_application.unsuspend` | Um [aplicativo OAuth][] foi suspenso para a conta de um usuário ou organização. {%- endif %} {%- ifversion fpt or ghec %} @@ -582,15 +582,15 @@ topics: | {% ifversion fpt or ghec %}Para obter mais informações, consulte "[Adicionando um gerente de cobrança à sua organização](/organizations/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization)".{% endif %} | | | `org.add_member` | Um usuário entrou em uma organização. | {%- ifversion ghes > 3.0 or ghae or ghec %} -| `org.advanced_security_disabled_for_new_repos` | {% data variables.product.prodname_GH_advanced_security %} foi desabilitado para novos repositórios em uma organização. | `org.advanced_security_disabled_on_all_repos` | {% data variables.product.prodname_GH_advanced_security %} foi desabilitado para todos os repositórios em uma organização. | `org.advanced_security_enabled_for_new_repos` | {% data variables.product.prodname_GH_advanced_security %} foi habilitado para novos repositórios em uma organização. | `org.advanced_security_enabled_on_all_repos` | {% data variables.product.prodname_GH_advanced_security %} foi habilitado para todos os repositórios em uma organização. | `org.advanced_security_policy_selected_member_disabled` | O proprietário de uma empresa evitou que as funcionalidades de {% data variables.product.prodname_GH_advanced_security %} fossem habilitadas para os repositórios pertencentes à organização. {% data reusables.advanced-security.more-information-about-enforcement-policy %} | `org.advanced_security_policy_selected_member_enabled` | An enterprise owner allowed {% data variables.product.prodname_GH_advanced_security %} features to be enabled for repositories owned by the organization. {% data reusables.advanced-security.more-information-about-enforcement-policy %} | `org.advanced_security_policy_update` | An organization owner updated polices for {% data variables.product.prodname_GH_advanced_security %} in an enterprise. {% data reusables.advanced-security.more-information-about-enforcement-policy %} +| `org.advanced_security_disabled_for_new_repos` | {% data variables.product.prodname_GH_advanced_security %} foi desabilitado para novos repositórios em uma organização. | `org.advanced_security_disabled_on_all_repos` | {% data variables.product.prodname_GH_advanced_security %} foi desabilitado para todos os repositórios em uma organização. | `org.advanced_security_enabled_for_new_repos` | {% data variables.product.prodname_GH_advanced_security %} foi habilitado para novos repositórios em uma organização. | `org.advanced_security_enabled_on_all_repos` | {% data variables.product.prodname_GH_advanced_security %} foi habilitado para todos os repositórios em uma organização. | `org.advanced_security_policy_selected_member_disabled` | O proprietário de uma empresa evitou que as funcionalidades de {% data variables.product.prodname_GH_advanced_security %} fossem habilitadas para os repositórios pertencentes à organização. {% data reusables.advanced-security.more-information-about-enforcement-policy %} | `org.advanced_security_policy_selected_member_enabled` | O proprietário de uma empresa permitiu que as funcionalidades de {% data variables.product.prodname_GH_advanced_security %} fossem habilitadas para repositórios pertencentes à organização. {% data reusables.advanced-security.more-information-about-enforcement-policy %} | `org.advanced_security_policy_update` | O proprietário de uma organização atualizou as políticas para {% data variables.product.prodname_GH_advanced_security %} em uma empresa. {% data reusables.advanced-security.more-information-about-enforcement-policy %} {%- endif %} -| `org.async_delete` | A user initiated a background job to delete an organization. +| `org.async_delete` | Um usuário iniciou um trabalho em segundo plano para excluir uma organização. {%- ifversion ghec %} -| `org.audit_log_export` | An organization owner created an export of the organization audit log. Se a exportação incluir uma consulta, o log relacionará a consulta usada e o número de entradas do log de auditoria que correspondem à consulta. For more information, see "[Exporting audit log activity for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/exporting-audit-log-activity-for-your-enterprise)." +| `org.audit_log_export` | O proprietário de uma organização criou uma exportação do log de auditoria da organização. Se a exportação incluir uma consulta, o log relacionará a consulta usada e o número de entradas do log de auditoria que correspondem à consulta. Para obter mais informações, consulte "[Exportando atividades de registro de auditoria para a sua empresa](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/exporting-audit-log-activity-for-your-enterprise)". {%- endif %} -| `org.block_user` | An organization owner blocked a user from accessing the organization's repositories. |{% ifversion fpt or ghec %}For more information, see "[Blocking a user from your organization](/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization)."{% endif %}| | `org.cancel_business_invitation` | An invitation for an organization to join an enterprise was revoked. |{% ifversion ghec %}For more information, see "[Inviting an organization to join your enterprise account](/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise#inviting-an-organization-to-join-your-enterprise-account)."{% endif %}| | `org.cancel_invitation` | An invitation sent to a user to join an organization was revoked. | `org.clear_actions_settings` | An organization owner cleared {% data variables.product.prodname_actions %} policy settings for an organization. For more information, see "[Managing GitHub Actions permissions for your organization](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization#managing-github-actions-permissions-for-your-organization)." | `org.clear_default_repository_permission` | An organization owner cleared the base repository permission policy setting for an organization. For more information, see "[Setting base permissions](/organizations/managing-access-to-your-organizations-repositories/setting-base-permissions-for-an-organization#setting-base-permissions)." | `org.clear_member_team_creation_permission` | An organization owner cleared the new teams creation setting for an organization. Para obter mais informações, consulte "[Configurar permissões de criação de equipes na organização](/organizations/managing-organization-settings/setting-team-creation-permissions-in-your-organization)". | `org.clear_reader_discussion_creation_permission` | An organization owner cleared the new discussion creation setting for an organization. |{% ifversion fpt or ghec %}For more information, see "[Allowing or disallowing users with read access to create discussions](/organizations/managing-organization-settings/managing-discussion-creation-for-repositories-in-your-organization)."{% endif %}| | `org.clear_members_can_create_repos` | An organization owner cleared a restriction on repository creation in an organization. Para obter mais informações, consulte "[Restringir a criação de repositórios na organização](/organizations/managing-organization-settings/restricting-repository-creation-in-your-organization)". | `org.clear_members_can_invite_outside_collaborators` | An organization owner cleared the outside collaborators invitation policy for an organization. Para obter mais informações, consulte "[Configurar permissões para adicionar colaboradores externos](/organizations/managing-organization-settings/setting-permissions-for-adding-outside-collaborators)". | `org.clear_new_repository_default_branch_setting` | An organization owner cleared the default branch name for new repositories setting for an organization. For more information, see "[Setting the default branch name](/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization#setting-the-default-branch-name)." +| `org.block_user` | O proprietário de uma organização bloqueou um usuário de acessar os repositórios da organização. |{% ifversion fpt or ghec %}Para obter mais informações, consulte "[Bloqueando um usuário ds sua organização](/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization)"{% endif %}| | `org.cancel_business_invitation` | Um convite para uma organização juntar-se a uma empresa foi revogado. |{% ifversion ghec %}Para obter mais informações, consulte "[Convidando uma organização para participar da sua conta corporativa](/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise#inviting-an-organization-to-join-your-enterprise-account)"{% endif %}| | `org.cancel_invitation` | Um convite enviado a um usuário para ingressar em uma organização foi revogado. | `org.clear_actions_settings` | O proprietário de uma organização apagou as configurações da política de {% data variables.product.prodname_actions %} para uma organização. Para obter mais informações, consulte "[Gerenciando as permissões do GitHub Actions para sua organização](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization#managing-github-actions-permissions-for-your-organization)". | `org.clear_default_repository_permission` | O proprietário de uma organização limpou a configuração da política de permissão do repositório de base para uma organização. Para obter mais informações, consulte "[Definindo permissões de base](/organizations/managing-access-to-your-organizations-repositories/setting-base-permissions-for-an-organization#setting-base-permissions)". | `org.clear_member_team_creation_permission` | O proprietário de uma organização limpou a configuração de de criação de novas equipes para uma organização. Para obter mais informações, consulte "[Configurar permissões de criação de equipes na organização](/organizations/managing-organization-settings/setting-team-creation-permissions-in-your-organization)". | `org.clear_reader_discussion_creation_permission` | O proprietário de uma organização limpou a criação de novas discussões para uma organização. |{% ifversion fpt or ghec %}Para obter mais informações, consulte "[Permitindo ou proibindo usuários com acesso de leitura de criar discussões](/organizations/managing-organization-settings/managing-discussion-creation-for-repositories-in-your-organization)"{% endif %}| | `org.clear_members_can_create_repos` | O proprietário de uma organização apagou uma restrição à criação de repositórios em uma organização. Para obter mais informações, consulte "[Restringir a criação de repositórios na organização](/organizations/managing-organization-settings/restricting-repository-creation-in-your-organization)". | `org.clear_members_can_invite_outside_collaborators` | O proprietário de uma organização apagou a política de convite de colaboradores externos para uma organização. Para obter mais informações, consulte "[Configurar permissões para adicionar colaboradores externos](/organizations/managing-organization-settings/setting-permissions-for-adding-outside-collaborators)". | `org.clear_new_repository_default_branch_setting` | O proprietário de uma organização apagou o nome do branch padrão para a configuração de novos repositórios para uma organização. Para obter mais informações, consulte "[Definindo o nome padrão do branch](/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization#setting-the-default-branch-name)". {%- ifversion fpt or ghec %} -| `org.codespaces_trusted_repo_access_granted` | {% data variables.product.prodname_codespaces %} was granted trusted repository access to all other repositories in an organization. Para obter mais informações, consulte "[Gerenciar acesso ao repositório para os codespaces da sua organização](/codespaces/managing-codespaces-for-your-organization/managing-repository-access-for-your-organizations-codespaces)". | `org.codespaces_trusted_repo_access_revoked` | {% data variables.product.prodname_codespaces %} trusted repository access to all other repositories in an organization was revoked. Para obter mais informações, consulte "[Gerenciar acesso ao repositório para os codespaces da sua organização](/codespaces/managing-codespaces-for-your-organization/managing-repository-access-for-your-organizations-codespaces)". +| `org.codespaces_trusted_repo_access_granted` | {% data variables.product.prodname_codespaces %} foi concedido acesso confiável ao repositório a todos os outros repositórios em uma organização. Para obter mais informações, consulte "[Gerenciar acesso ao repositório para os codespaces da sua organização](/codespaces/managing-codespaces-for-your-organization/managing-repository-access-for-your-organizations-codespaces)". | `org.codespaces_trusted_repo_access_revoked` | {% data variables.product.prodname_codespaces %} acesso confiável ao repositório para todos os outros repositórios de uma organização foi revogado. Para obter mais informações, consulte "[Gerenciar acesso ao repositório para os codespaces da sua organização](/codespaces/managing-codespaces-for-your-organization/managing-repository-access-for-your-organizations-codespaces)". {%- endif %} | `org.config.disable_collaborators_only` | The interaction limit for collaborators only for an organization was disabled. |{% ifversion fpt or ghec %}For more information, see "[Limiting interactions in your organization](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization#limiting-interactions-in-your-organization)."{% endif %}| | `org.config.disable_contributors_only` | The interaction limit for prior contributors only for an organization was disabled. |{% ifversion fpt or ghec %}For more information, see "[Limiting interactions in your organization](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization#limiting-interactions-in-your-organization)."{% endif %}| | `org.config.disable_sockpuppet_disallowed` | The interaction limit for existing users only for an organization was disabled. |{% ifversion fpt or ghec %}For more information, see "[Limiting interactions in your organization](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization#limiting-interactions-in-your-organization)."{% endif %}| | `org.config.enable_collaborators_only` | The interaction limit for collaborators only for an organization was enabled. |{% ifversion fpt or ghec %}For more information, see "[Limiting interactions in your organization](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization#limiting-interactions-in-your-organization)."{% endif %}| | `org.config.enable_contributors_only` | The interaction limit for prior contributors only for an organization was enabled. |{% ifversion fpt or ghec %}For more information, see "[Limiting interactions in your organization](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization#limiting-interactions-in-your-organization)."{% endif %}| | `org.config.enable_sockpuppet_disallowed` | The interaction limit for existing users only for an organization was enabled. |{% ifversion fpt or ghec %}For more information, see "[Limiting interactions in your organization](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization#limiting-interactions-in-your-organization)."{% endif %}| | `org.confirm_business_invitation` | An invitation for an organization to join an enterprise was confirmed. |{% ifversion ghec %}For more information, see "[Inviting an organization to join your enterprise account](/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise#inviting-an-organization-to-join-your-enterprise-account)."{% endif %}| | `org.create` | An organization was created. Para obter mais informações, consulte "[Criar uma nova organização do zero](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)". {%- ifversion fpt or ghec or ghes %} @@ -676,7 +676,7 @@ topics: {%- endif %} {%- if secret-scanning-audit-log-custom-patterns %} -### `org_secret_scanning_custom_pattern` category actions +### Ações da categoria `org_secret_scanning_custom_pattern` | Ação | Descrição | | ------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | @@ -991,7 +991,7 @@ topics: {%- if secret-scanning-audit-log-custom-patterns %} -### `repository_secret_scanning_custom_pattern` category actions +### Ações da categoria `repository_secret_scanning_custom_pattern` | Ação | Descrição | | -------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | @@ -999,12 +999,12 @@ topics: | `repository_secret_scanning_custom_pattern.delete` | A custom pattern is removed from secret scanning in a repository. Para obter mais informações, consulte "[Definindo padrões personalizados para digitalização de segredo](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning#removing-a-custom-pattern). " | | `repository_secret_scanning_custom_pattern.update` | Changes to a custom pattern are saved for secret scanning in a repository. Para obter mais informações, consulte "[Definindo padrões personalizados para digitalização de segredo](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning#editing-a-custom-pattern). " | -### `repository_secret_scanning_push_protection` category actions +### ações da categoria `repository_secret_scanning_push_protection` -| Ação | Descrição | -| ---------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `repository_secret_scanning_push_protection.disable` | A repository owner or administrator disabled secret scanning for a repository. For more information, see "[Protecting pushes with secret scanning](/code-security/secret-scanning/protecting-pushes-with-secret-scanning)." | -| `repository_secret_scanning_push_protection.enable` | A repository owner or administrator enabled secret scanning for a repository. For more information, see "[Protecting pushes with secret scanning](/code-security/secret-scanning/protecting-pushes-with-secret-scanning)." | +| Ação | Descrição | +| ---------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `repository_secret_scanning_push_protection.disable` | A repository owner or administrator disabled secret scanning for a repository. Para obter mais informações, consulte "[Protegendo pushes com digitalização de segredo](/code-security/secret-scanning/protecting-pushes-with-secret-scanning)". | +| `repository_secret_scanning_push_protection.enable` | A repository owner or administrator enabled secret scanning for a repository. Para obter mais informações, consulte "[Protegendo pushes com digitalização de segredo](/code-security/secret-scanning/protecting-pushes-with-secret-scanning)". | {%- endif %} ### `repository_visibility_change` category actions @@ -1249,7 +1249,7 @@ topics: [aplicativo OAuth application]: /guides/basics-of-authentication/#registering-your-app - [OAuth application]: /guides/basics-of-authentication/#registering-your-app + [aplicativo OAuth ]: /guides/basics-of-authentication/#registering-your-app [add key]: /authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account [deploy key]: /developers/overview/managing-deploy-keys#deploy-keys diff --git a/translations/pt-BR/content/admin/user-management/managing-organizations-in-your-enterprise/managing-your-role-in-an-organization-owned-by-your-enterprise.md b/translations/pt-BR/content/admin/user-management/managing-organizations-in-your-enterprise/managing-your-role-in-an-organization-owned-by-your-enterprise.md index 824c8511bb..eaf6e5e1d6 100644 --- a/translations/pt-BR/content/admin/user-management/managing-organizations-in-your-enterprise/managing-your-role-in-an-organization-owned-by-your-enterprise.md +++ b/translations/pt-BR/content/admin/user-management/managing-organizations-in-your-enterprise/managing-your-role-in-an-organization-owned-by-your-enterprise.md @@ -24,7 +24,7 @@ Você pode optar por participar de uma organização pertencente à sua empresa {% warning %} -**Aviso**: Se uma organização usar o SCIM para fornecer usuários, entrar na organização desta forma poderia ter consequências não desejadas. For more information, see "[About SCIM for organizations](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim-for-organizations)." +**Aviso**: Se uma organização usar o SCIM para fornecer usuários, entrar na organização desta forma poderia ter consequências não desejadas. Para obter mais informações, consulte "[Sobre SCIM para as organizações](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim-for-organizations)". {% endwarning %} diff --git a/translations/pt-BR/content/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on.md b/translations/pt-BR/content/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on.md index c72718c44a..1a7053f70d 100644 --- a/translations/pt-BR/content/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on.md +++ b/translations/pt-BR/content/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on.md @@ -46,13 +46,13 @@ Na falta de um token de acesso pessoal ou uma chave SSH, você poderá criar um Para usar um token novo ou existente de acesso pessoal ou chave SSH com uma organização que usa ou impõe o SSO do SAML, você precisará autorizar o token ou autorizar a chave SSH para uso com uma organização de SSO do SAML. Para obter mais informações consulte "[Autorizar um token de acesso pessoal para usar com logon único SAML](/articles/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)" ou "[Autorizando uma chave SSH para uso com o logon único SAML](/articles/authorizing-an-ssh-key-for-use-with-saml-single-sign-on). -## About {% data variables.product.prodname_oauth_apps %}, {% data variables.product.prodname_github_apps %}, and SAML SSO +## Sobre {% data variables.product.prodname_oauth_apps %}, {% data variables.product.prodname_github_apps %} e SAML SSO -You must have an active SAML session each time you authorize an {% data variables.product.prodname_oauth_app %} or {% data variables.product.prodname_github_app %} to access an organization that uses or enforces SAML SSO. You can create an active SAML session by navigating to `https://github.com/orgs/ORGANIZATION-NAME/sso` in your browser. +Você deve ter uma sessão do SAML ativa toda vez que autorizar um {% data variables.product.prodname_oauth_app %} ou {% data variables.product.prodname_github_app %} para acessar uma organização que usa ou aplica o SAML SSO. Você pode criar uma sessão do SAML ativa, acessando `https://github.com/orgs/ORGANIZATION-NAME/sso` no seu navegador. -After an enterprise or organization owner enables or enforces SAML SSO for an organization, and after you authenticate via SAML for the first time, you must reauthorize any {% data variables.product.prodname_oauth_apps %} or {% data variables.product.prodname_github_apps %} that you previously authorized to access the organization. +Após o proprietário de uma empresa ou organização permitir ou aplicar o SAML SSO para uma organização, e depois de efetuar a autenticação por meio do SAML pela primeira vez, você deverá autorizar novamente todos os {% data variables.product.prodname_oauth_apps %} ou {% data variables.product.prodname_github_apps %} que você autorizou anteriormente a acessar a organização. -To see the {% data variables.product.prodname_oauth_apps %} you've authorized, visit your [{% data variables.product.prodname_oauth_apps %} page](https://github.com/settings/applications). To see the {% data variables.product.prodname_github_apps %} you've authorized, visit your [{% data variables.product.prodname_github_apps %} page](https://github.com/settings/apps/authorizations). +Para ver o {% data variables.product.prodname_oauth_apps %} que você autorizou, acesse a sua [página de {% data variables.product.prodname_oauth_apps %}](https://github.com/settings/applications). Para ver o {% data variables.product.prodname_github_apps %} que você autorizou, acesse a sua [página de {% data variables.product.prodname_github_apps %}](https://github.com/settings/apps/authorizations). {% endif %} diff --git a/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository.md b/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository.md index 033e3e37ea..5da284b01e 100644 --- a/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository.md +++ b/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository.md @@ -1,7 +1,7 @@ --- title: Gerenciar alertas de verificação de código para o seu repositório shortTitle: Gerenciar alertas -intro: 'From the security view, {% if delete-code-scanning-alerts %}you can view, fix, dismiss, or delete alerts {% else %}you can view, fix, or dismiss alerts{% endif %} for potential vulnerabilities or errors in your project''s code.' +intro: 'Na visão de segurança, {% if delete-code-scanning-alerts %}você pode visualizar, corrigir, ignorar ou excluir alertas {% else %}que você pode visualizar, corrigir, ou dispensar alertas{% endif %} de possíveis vulnerabilidades ou erros no código do seu projeto.' product: '{% data reusables.gated-features.code-scanning %}' permissions: 'If you have write permission to a repository you can manage {% data variables.product.prodname_code_scanning %} alerts for that repository.' versions: @@ -169,9 +169,9 @@ Alertas podem ser corrigidos em um branch, mas não em outro. Você pode usar o {% endnote %} {% endif %} -## Dismissing {% if delete-code-scanning-alerts %}or deleting{% endif %} alerts +## Ignorando ou {% if delete-code-scanning-alerts %}ou excluindo{% endif %} alertas -Há duas formas de fechar um alerta. Você pode corrigir o problema no código ou pode ignorar o alerta. {% if delete-code-scanning-alerts %}Alternatively, if you have admin permissions for the repository, you can delete alerts. Excluir alertas é útil em situações em que você configurou uma ferramenta {% data variables.product.prodname_code_scanning %} e, em seguida, decidiu removê-la ou em situações em que você configurou a análise de {% data variables.product.prodname_codeql %} com um conjunto de consultas maior do que você deseja continuar usando, e, em seguida, você removeu algumas consultas da ferramenta. Em ambos os casos, excluir alertas permite limpar os seus resultados de {% data variables.product.prodname_code_scanning %}. You can delete alerts from the summary list within the **Security** tab.{% endif %} +Há duas formas de fechar um alerta. Você pode corrigir o problema no código ou pode ignorar o alerta. {% if delete-code-scanning-alerts %}Como alternativa, se você tiver permissões de administrador para o repositório, será possível excluir alertas. Excluir alertas é útil em situações em que você configurou uma ferramenta {% data variables.product.prodname_code_scanning %} e, em seguida, decidiu removê-la ou em situações em que você configurou a análise de {% data variables.product.prodname_codeql %} com um conjunto de consultas maior do que você deseja continuar usando, e, em seguida, você removeu algumas consultas da ferramenta. Em ambos os casos, excluir alertas permite limpar os seus resultados de {% data variables.product.prodname_code_scanning %}. Você pode excluir alertas da lista de resumo dentro da aba de **Segurança** .{% endif %} Ignorar um alerta é uma maneira de fechar um alerta que você considera que não precisa ser corrigido. {% data reusables.code-scanning.close-alert-examples %} Você pode ignorar alertas de anotações de {% data variables.product.prodname_code_scanning %} no código ou da lista de resumo dentro na aba **Segurança**. @@ -183,14 +183,14 @@ Ao descartar um alerta: - O motivo pelo qual você fechou o alerta foi gravado. - Da próxima vez que {% data variables.product.prodname_code_scanning %} for executado, o mesmo código não gerará um alerta. -{% if delete-code-scanning-alerts %}When you delete an alert: +{% if delete-code-scanning-alerts %}Ao excluir um alerta: - Ele é excluído em todos os branches. - O alerta é removido do número de alertas atuais para o seu projeto. - Ele _não é_ adicionado à lista "Fechado" no resumo dos alertas. -- If the code that generated the alert stays the same, and the same {% data variables.product.prodname_code_scanning %} tool runs again without any configuration changes, the alert will be shown again in your analysis results.{% endif %} +- Se o código que gerou o alerta permanecer o mesmo e a mesma ferramenta {% data variables.product.prodname_code_scanning %} for executada novamente sem qualquer alteração de configuração, o alerta será exibido novamente nos seus resultados das análises.{% endif %} -To dismiss {% if delete-code-scanning-alerts %}or delete{% endif %} alerts: +Para ignorar{% if delete-code-scanning-alerts %}ou excluir{% endif %} alertas: {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} diff --git a/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests.md b/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests.md index 36e1a559e4..d9514a5133 100644 --- a/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests.md +++ b/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests.md @@ -99,4 +99,4 @@ Uma forma alternativa de fechar um alerta é ignorá-lo. Você pode descartar um {% data reusables.code-scanning.false-positive-fix-codeql %} -For more information about dismissing alerts, see {% if delete-code-scanning-alerts %}"[Managing {% data variables.product.prodname_code_scanning %} alerts for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository#dismissing-or-deleting-alerts)."{% else %} "[Managing {% data variables.product.prodname_code_scanning %} alerts for your repository](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository#dismissing--alerts)."{% endif %} +Para obter mais informações sobre ignorar alertas, consulte {% if delete-code-scanning-alerts %}"[Gerenciando alertas de {% data variables.product.prodname_code_scanning %} para o seu repositório](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository#dismissing-or-deleting-alerts).{% else %} "[Gerenciando alertas de {% data variables.product.prodname_code_scanning %} para o seu repositório](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository#dismissing--alerts)".{% endif %} diff --git a/translations/pt-BR/content/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts.md b/translations/pt-BR/content/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts.md index 76d5653c50..fdc0582a50 100644 --- a/translations/pt-BR/content/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts.md +++ b/translations/pt-BR/content/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts.md @@ -55,7 +55,7 @@ Para as linguagens compatíveis, {% data variables.product.prodname_dependabot % {% note %} -**Observação:** Durante a versão beta, esse recurso está disponível apenas para novas consultorias do Python criadas *depois de* 14 de abril de 2022 e para um subconjunto de consultorias históricas do Python. GitHub is working to backfill data across additional historical Python advisories, which are added on a rolling basis. As chamadas vulneráveis são destacadas apenas nas páginas de {% data variables.product.prodname_dependabot_alerts %}. +**Observação:** Durante a versão beta, esse recurso está disponível apenas para novas consultorias do Python criadas *depois de* 14 de abril de 2022 e para um subconjunto de consultorias históricas do Python. O GitHub está trabalhando para preencher dados de backfill através de consultorias históricas no Python, que são adicionadas regularmente. As chamadas vulneráveis são destacadas apenas nas páginas de {% data variables.product.prodname_dependabot_alerts %}. {% endnote %} diff --git a/translations/pt-BR/content/code-security/supply-chain-security/end-to-end-supply-chain/securing-accounts.md b/translations/pt-BR/content/code-security/supply-chain-security/end-to-end-supply-chain/securing-accounts.md index e503bd26d2..ece94a2dd4 100644 --- a/translations/pt-BR/content/code-security/supply-chain-security/end-to-end-supply-chain/securing-accounts.md +++ b/translations/pt-BR/content/code-security/supply-chain-security/end-to-end-supply-chain/securing-accounts.md @@ -31,11 +31,11 @@ A segurança da conta é fundamental para a segurança da sua cadeia de suprimen {% ifversion ghec %} Se você é proprietário de uma empresa ou organização, você pode configurar a autenticação centralizada com SAML. Embora você possa adicionar ou remover integrantes manualmente, é mais simples e mais seguro configurar um logon único (SSO) e SCIM entre {% data variables.product.product_name %} e seu provedor de identidade (IdP) SAML. Isso também simplifica o processo de autenticação para todos os integrantes da sua empresa. -Você pode configurar a autenticação SAML para uma conta corporativa ou da organização. Com o SAML, você pode conceder acesso às contas pessoais dos integrantes da sua empresa ou organização no {% data variables.product.product_location %} por meio do seu IdP, ou você pode criar e controlar as contas que pertencem à sua empresa usando {% data variables.product.prodname_emus %}. For more information, see "[About authentication for your enterprise](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise)." +Você pode configurar a autenticação SAML para uma conta corporativa ou da organização. Com o SAML, você pode conceder acesso às contas pessoais dos integrantes da sua empresa ou organização no {% data variables.product.product_location %} por meio do seu IdP, ou você pode criar e controlar as contas que pertencem à sua empresa usando {% data variables.product.prodname_emus %}. Para obter mais informações, consulte "[Sobre a autenticação para sua empresa](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise)". Depois de configurar a autenticação do SAML, quando os integrantes solicitarem acesso aos seus recursos, eles serão direcionados para o seu fluxo de SSO para garantir que sejam reconhecidos pelo seu IdP. Se não forem reconhecidos, o seu pedido será recusado. -Alguns IdPs são compatíveis com um protocolo denominado SCIM, que pode prover ou desprovisionar automaticamente o acesso em {% data variables.product.product_name %} quando você fizer alterações no seu IdP. Com o SCIM, você pode simplificar a administração à medida que a sua equipe cresce, e você pode revogar rapidamente o acesso às contas. O SCIM está disponível para organizações individuais em {% data variables.product.product_name %}, ou para empresas que usam {% data variables.product.prodname_emus %}. For more information, see "[About SCIM for organizations](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim-for-organizations)." +Alguns IdPs são compatíveis com um protocolo denominado SCIM, que pode prover ou desprovisionar automaticamente o acesso em {% data variables.product.product_name %} quando você fizer alterações no seu IdP. Com o SCIM, você pode simplificar a administração à medida que a sua equipe cresce, e você pode revogar rapidamente o acesso às contas. O SCIM está disponível para organizações individuais em {% data variables.product.product_name %}, ou para empresas que usam {% data variables.product.prodname_emus %}. Para obter mais informações, consulte "[Sobre SCIM para as organizações](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim-for-organizations)". {% endif %} {% ifversion ghes %} diff --git a/translations/pt-BR/content/codespaces/customizing-your-codespace/setting-your-timeout-period-for-codespaces.md b/translations/pt-BR/content/codespaces/customizing-your-codespace/setting-your-timeout-period-for-codespaces.md index ae310c313d..a2f6f49239 100644 --- a/translations/pt-BR/content/codespaces/customizing-your-codespace/setting-your-timeout-period-for-codespaces.md +++ b/translations/pt-BR/content/codespaces/customizing-your-codespace/setting-your-timeout-period-for-codespaces.md @@ -12,6 +12,8 @@ shortTitle: Definir o tempo limite Um codespace irá parar de funcionar após um período de inatividade. Você pode especificar a duração deste período de tempo limite. A configuração atualizada será aplicada a qualquer código recém-criado. +Some organizations may have a maximum idle timeout policy. If an organization policy sets a maximum timeout which is less than the default timeout you have set, the organization's timeout will be used instead of your setting, and you will be notified of this after the codespace is created. For more information, see "[Restricting the idle timeout period](/codespaces/managing-codespaces-for-your-organization/restricting-the-idle-timeout-period)." + {% warning %} **Aviso**: Os codespaces são cobrados por minuto. Se você não está usando ativamente um codepsace, mas o este ainda não expirou, você ainda será cobrado pelo tempo em que o codespace estiver em execução. Para obter mais informações, consulte[Sobre a cobrança dos codespaces](/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces#codespaces-pricing)". diff --git a/translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/index.md b/translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/index.md index c540ecbc9c..9f79449f32 100644 --- a/translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/index.md +++ b/translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/index.md @@ -15,6 +15,7 @@ children: - /reviewing-your-organizations-audit-logs-for-codespaces - /restricting-access-to-machine-types - /restricting-the-visibility-of-forwarded-ports + - /restricting-the-idle-timeout-period shortTitle: Gerenciando sua organização --- diff --git a/translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types.md b/translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types.md index fa3fe372ec..12d9944b12 100644 --- a/translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types.md +++ b/translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types.md @@ -1,9 +1,9 @@ --- title: Restringindo o acesso aos tipos de máquina -shortTitle: Tipo de máquina acesso +shortTitle: Restrict machine types intro: Você pode definir restrições sobre os tipos de máquinas que os usuários podem escolher ao criarem os codespaces na sua organização. product: '{% data reusables.gated-features.codespaces %}' -permissions: 'To manage access to machine types for the repositories in an organization, you must be an organization owner.' +permissions: 'To manage access to machine types for the repositories in an organization, you must be an owner of the organization.' versions: fpt: '*' ghec: '*' @@ -47,33 +47,22 @@ Se você adicionar uma política para toda a organização, você deverá config {% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} -1. Na seção "Código, planejamento e automação" da barra lateral, selecione **{% octicon "codespaces" aria-label="The codespaces icon" %} {% data variables.product.prodname_codespaces %}** e, em seguida, clique em **Política**. -2. Na página "Políticas do codespace", clique em **Criar política**. -3. Insira um nome para sua nova política. -4. Clique **Adicionar restrição** e escolha **Tipos de máquina**. +{% data reusables.codespaces.codespaces-org-policies %} +1. Clique **Adicionar restrição** e escolha **Tipos de máquina**. ![Adicionar uma restrição para os tipos de máquina](/assets/images/help/codespaces/add-constraint-dropdown.png) -5. Clique em {% octicon "pencil" aria-label="The edit icon" %} para editar a restrição e, em seguida, limpe a seleção de todos os tipos de máquina que você não deseja que estejam disponíveis. +1. Clique em {% octicon "pencil" aria-label="The edit icon" %} para editar a restrição e, em seguida, limpe a seleção de todos os tipos de máquina que você não deseja que estejam disponíveis. ![Editar a restrição de tipo de máquina](/assets/images/help/codespaces/edit-machine-constraint.png) -6. Na área "Alterar destino da política", clique no botão suspenso. -7. Selecione **Todos os repositórios** ou **Repositórios selecionados** para determinar em quais repositórios esta política será aplicada. -8. Se você escolheu **repositórios selecionados**: - 1. Clique em {% octicon "gear" aria-label="The settings icon" %}. - - ![Editar as configurações da política](/assets/images/help/codespaces/policy-edit.png) - - 2. Selecione os repositórios aos quais você quer que esta política seja aplicada. - 3. Na parte inferior da lista de repositórios, clique em **Selecionar repositórios**. - - ![Selecionar repositórios para esta política](/assets/images/help/codespaces/policy-select-repos.png) - -9. Clique em **Salvar**. - +{% data reusables.codespaces.codespaces-policy-targets %} +1. If you want to add another constraint to the policy, click **Add constraint** and choose another constraint. For information about other constraints, see "[Restricting the visibility of forwarded ports](/codespaces/managing-codespaces-for-your-organization/restricting-the-visibility-of-forwarded-ports)" and "[Restricting the idle timeout period](/codespaces/managing-codespaces-for-your-organization/restricting-the-idle-timeout-period)." +1. After you have finished adding constraints to your policy, click **Save**. ## Editando uma política +You can edit an existing policy. For example, you may want to add or remove constraints to or from a policy. + 1. Exibir a página "Políticas de codespaces". Para obter mais informações, consulte "[Adicionar uma política para limitar os tipos de máquina disponíveis](#adding-a-policy-to-limit-the-available-machine-types)". 1. Clique no nome da política que você deseja editar. 1. Faça as alterações necessárias e, em seguida, clique em **Salvar**. diff --git a/translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/restricting-the-idle-timeout-period.md b/translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/restricting-the-idle-timeout-period.md new file mode 100644 index 0000000000..15a27bbf8e --- /dev/null +++ b/translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/restricting-the-idle-timeout-period.md @@ -0,0 +1,79 @@ +--- +title: Restricting the idle timeout period +shortTitle: Restrict timeout periods +intro: You can set a maximum timeout period for any codespaces owned by your organization. +product: '{% data reusables.gated-features.codespaces %}' +permissions: 'To manage timeout constraints for an organization''s codespaces, you must be an owner of the organization.' +versions: + fpt: '*' + ghec: '*' +type: how_to +topics: + - Codespaces +--- + +## Visão Geral + +By default, codespaces time out after 30 minutes of inactivity. When a codespace times out it is stopped and will no longer incur charges for compute usage. + +The personal settings of a {% data variables.product.prodname_dotcom %} user allow them to define their own timeout period for codespaces they create. This may be longer than the default 30-minute period. For more information, see "[Setting your timeout period for Codespaces](/codespaces/customizing-your-codespace/setting-your-timeout-period-for-codespaces)." + +As an organization owner, you may want to configure constraints on the maximum idle timeout period for codespaces owned by your organization. This can help you limit costs associated with codespaces that are left to timeout after long periods of inactivity. You can set a maximum timeout for all codespaces owned by your organization, or for the codespaces of specific repositories. + +{% note %} + +**Note**: Maximum idle timeout constraints only apply to codespaces that are owned by your organization. + +{% endnote %} + +For more information about pricing for {% data variables.product.prodname_codespaces %} compute usage, see "[About billing for Codespaces](/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces#codespaces-pricing)." + +### Behavior when you set a maximum idle timeout constraint + +If someone sets the default idle timeout to 90 minutes in their personal settings and they then start a codespace for a repository with a maximum idle timeout constraint of 60 minutes, the codespace will time out after 60 minutes of inactivity. When codespace creation completes, a message explaining this will be displayed: + +> Idle timeout for this codespace is set to 60 minutes in compliance with your organization’s policy. + +### Definindo políticas específicas da organização e do repositório + +When you create a policy, you choose whether it applies to all repositories in your organization, or only to specified repositories. If you create an organization-wide policy with a timeout constraint, then the timeout constraints in any policies that are targeted at specific repositories must fall within the restriction configured for the entire organization. The shortest timeout period - in an organization-wide policy, a policy targeted at specified repositories, or in someone's personal settings - is applied. + +If you add an organization-wide policy with a timeout constraint, you should set the timeout to the longest acceptable period. You can then add separate policies that set the maximum timeout to a shorter period for specific repositories in your organization. + +## Adding a policy to set a maximum idle timeout period + +{% data reusables.profile.access_org %} +{% data reusables.profile.org_settings %} +{% data reusables.codespaces.codespaces-org-policies %} +1. Click **Add constraint** and choose **Maximum idle timeout**. + + ![Add a constraint for idle timeout](/assets/images/help/codespaces/add-constraint-dropdown-timeout.png) + +1. Clique {% octicon "pencil" aria-label="The edit icon" %} para editar a restrição. + + ![Edit the timeout constraint](/assets/images/help/codespaces/edit-timeout-constraint.png) + +1. Enter the maximum number of minutes codespaces can remain inactive before they time out, then click **Save**. + + ![Escolha as opções de visibilidade da porta](/assets/images/help/codespaces/maximum-minutes-timeout.png) + +{% data reusables.codespaces.codespaces-policy-targets %} +1. If you want to add another constraint to the policy, click **Add constraint** and choose another constraint. For information about other constraints, see "[Restricting access to machine types](/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types)" and "[Restricting the visibility of forwarded ports](/codespaces/managing-codespaces-for-your-organization/restricting-the-visibility-of-forwarded-ports)." +1. After you have finished adding constraints to your policy, click **Save**. + +The policy will be applied to all new codespaces that are created, and to existing codespaces the next time they are started. + +## Editando uma política + +You can edit an existing policy. For example, you may want to add or remove constraints to or from a policy. + +1. Exibir a página "Políticas de codespaces". For more information, see "[Adding a policy to set a maximum idle timeout period](#adding-a-policy-to-set-a-maximum-idle-timeout-period)." +1. Clique no nome da política que você deseja editar. +1. Faça as alterações necessárias e, em seguida, clique em **Salvar**. + +## Excluindo uma política + +1. Exibir a página "Políticas de codespaces". For more information, see "[Adding a policy to set a maximum idle timeout period](#adding-a-policy-to-set-a-maximum-idle-timeout-period)." +1. Clique no botão excluir à direita da política que você deseja excluir. + + ![O botão de excluir uma política](/assets/images/help/codespaces/policy-delete.png) diff --git a/translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/restricting-the-visibility-of-forwarded-ports.md b/translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/restricting-the-visibility-of-forwarded-ports.md index 50aabb5dd7..692f0f4887 100644 --- a/translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/restricting-the-visibility-of-forwarded-ports.md +++ b/translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/restricting-the-visibility-of-forwarded-ports.md @@ -1,9 +1,9 @@ --- title: Restringindo a visibilidade das portas encaminhadas -shortTitle: Restringindo visibilidade da porta +shortTitle: Restrict port visibility intro: Você pode definir as restrições das opções de visibilidade que os usuários podem escolher quando encaminham portas em codespaces na sua organização. product: '{% data reusables.gated-features.codespaces %}' -permissions: 'To manage access to port visibility constraints for the repositories in an organization, you must be an organization owner.' +permissions: 'To manage access to port visibility constraints for the repositories in an organization, you must be an owner of the organization.' versions: fpt: '*' ghec: '*' @@ -40,14 +40,12 @@ Se você adicionar uma política para toda a organização, você deverá defini {% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} -1. Na seção "Código, planejamento e automação" da barra lateral, selecione **{% octicon "codespaces" aria-label="The codespaces icon" %} {% data variables.product.prodname_codespaces %}** e, em seguida, clique em **Políticas**. -1. Na página "Políticas do codespace", clique em **Criar política**. -1. Insira um nome para sua nova política. +{% data reusables.codespaces.codespaces-org-policies %} 1. Clique em **Adicionar restrição** e escolha **Visibilidade da porta**. ![Adicionar uma restrição para a visibilidade da porta](/assets/images/help/codespaces/add-constraint-dropdown-ports.png) -1. Clique {% octicon "pencil" aria-label="The edit icon" %} para editar a restrição +1. Clique {% octicon "pencil" aria-label="The edit icon" %} para editar a restrição. ![Editar a restrição de visibilidade da porta](/assets/images/help/codespaces/edit-port-visibility-constraint.png) @@ -55,22 +53,13 @@ Se você adicionar uma política para toda a organização, você deverá defini ![Escolha as opções de visibilidade da porta](/assets/images/help/codespaces/choose-port-visibility-options.png) -1. Na área "Alterar destino da política", clique no botão suspenso. -1. Selecione **Todos os repositórios** ou **Repositórios selecionados** para determinar em quais repositórios esta política será aplicada. -1. Se você escolheu **repositórios selecionados**: - 1. Clique em {% octicon "gear" aria-label="The settings icon" %}. - - ![Editar as configurações da política](/assets/images/help/codespaces/policy-edit.png) - - 2. Selecione os repositórios aos quais você quer que esta política seja aplicada. - 3. Na parte inferior da lista de repositórios, clique em **Selecionar repositórios**. - - ![Selecionar repositórios para esta política](/assets/images/help/codespaces/policy-select-repos.png) - -1. Clique em **Salvar**. - +{% data reusables.codespaces.codespaces-policy-targets %} +1. If you want to add another constraint to the policy, click **Add constraint** and choose another constraint. For information about other constraints, see "[Restricting access to machine types](/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types)" and "[Restricting the idle timeout period](/codespaces/managing-codespaces-for-your-organization/restricting-the-idle-timeout-period)." +1. After you have finished adding constraints to your policy, click **Save**. ## Editando uma política +You can edit an existing policy. For example, you may want to add or remove constraints to or from a policy. + 1. Exibir a página "Políticas de codespaces". Para obter mais informações, consulte "[Adicionando uma política para limitar as opções de visibilidade da porta](#adding-a-policy-to-limit-the-port-visibility-options)". 1. Clique no nome da política que você deseja editar. 1. Faça as alterações necessárias e, em seguida, clique em **Salvar**. diff --git a/translations/pt-BR/content/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/committing-and-reviewing-changes-to-your-project.md b/translations/pt-BR/content/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/committing-and-reviewing-changes-to-your-project.md index 9f5fab001e..ff6925595a 100644 --- a/translations/pt-BR/content/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/committing-and-reviewing-changes-to-your-project.md +++ b/translations/pt-BR/content/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/committing-and-reviewing-changes-to-your-project.md @@ -123,3 +123,11 @@ Ao concluir as alterações que você decidiu fazer no commit, escreva a mensage ![Aviso de branch protegido](/assets/images/help/desktop/protected-branch-warning.png) {% data reusables.desktop.push-origin %} + +6. If you have a pull request based off the branch you are working on, {% data variables.product.prodname_desktop %} will display the status of the checks that have run for the pull request. For more information about checks, see "[Viewing and re-running checks in GitHub Desktop](/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/viewing-and-re-running-checks-in-github-desktop)." + + ![Checks display next to branch name](/assets/images/help/desktop/checks-dialog.png) + + If a pull request has not been created for the current branch, {% data variables.product.prodname_desktop %} will give you the option to create one. Para obter mais informações, consulte "[Criando um problema ou um pull request](/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/creating-an-issue-or-pull-request)." + + ![Criar um pull request](/assets/images/help/desktop/mac-create-pull-request.png) diff --git a/translations/pt-BR/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/configuring-notifications-in-github-desktop.md b/translations/pt-BR/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/configuring-notifications-in-github-desktop.md new file mode 100644 index 0000000000..1532d735b1 --- /dev/null +++ b/translations/pt-BR/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/configuring-notifications-in-github-desktop.md @@ -0,0 +1,63 @@ +--- +title: Configuring notifications in GitHub Desktop +shortTitle: Configurar notificações +intro: '{% data variables.product.prodname_desktop %} will keep you up-to-date with notifications about events that occur in your pull request branch.' +versions: + fpt: '*' +--- + +## About notifications in {% data variables.product.prodname_desktop %} + +{% data variables.product.prodname_desktop %} will show a system notification for events that occur in the currently selected repository. Notifications will be shown when: + +- Pull request checks have failed. +- A pull request review is left with a comment, approval, or requested changes. + +Clicking the notification will switch application focus to {% data variables.product.prodname_desktop %} and provide more detailed information. + +## Notifications about pull request check failures + +When changes are made to a pull request branch, you will receive a notification if the checks fail. + +![pull request checks failed notification](/assets/images/help/desktop/pull-request-checks-failed-notification.png) + +Clicking the notification will display a dialog with details about the checks. Once you've reviewed why the checks have failed, you can re-run the checks, or quickly switch to the pull request branch to get started on fixing the errors. For more information, see "[Viewing and re-running checks in GitHub Desktop](/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/viewing-and-re-running-checks-in-github-desktop)." + +![checks failed dialog](/assets/images/help/desktop/checks-failed-dialog.png) +## Notifications for pull request reviews + +{% data variables.product.prodname_desktop %} will surface a system notification when a teammate has approved, commented, or requested changes in your pull request. See "[About pull request reviews](/github/collaborating-with-issues-and-pull-requests/about-pull-request-reviews)" for more information on pull request reviews. + +![Pull request review notification](/assets/images/help/desktop/pull-request-review-notification.png) + +Clicking the notification will switch application focus to {% data variables.product.prodname_desktop %} and provide more context for the pull request review comment. + +![pull request review dialog](/assets/images/help/desktop/pull-request-review-dialog.png) +## Enabling notifications + +If system notifications are disabled for {% data variables.product.prodname_desktop %} you can follow the steps below to enable them. + +{% mac %} + +1. Click the **Apple** menu, then select **System Preferences**. +2. Select **Notifications & Focus**. +3. Select **{% data variables.product.prodname_desktop %}** from the list of applications. +4. Click **Allow Notifications**. + +![macOS Notifications & Focus](/assets/images/help/desktop/mac-enable-notifications.png) + +For more information about macOS system notifications, see "[Use notifications on your Mac](https://support.apple.com/en-us/HT204079)." + +{% endmac %} + +{% windows %} + +1. Open the **Start** menu, then select **Settings**. +2. Select **System**, then click **Notifications**. +3. Find **{% data variables.product.prodname_desktop %}** in the application list and click **On**. + +![Enable Windows Notifications](/assets/images/help/desktop/windows-enable-notifications.png) + +For more information about Windows system notifications, see "[Change notification settings in Windows](https://support.microsoft.com/en-us/windows/change-notification-settings-in-windows-8942c744-6198-fe56-4639-34320cf9444e)." + +{% endwindows %} diff --git a/translations/pt-BR/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/index.md b/translations/pt-BR/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/index.md index 794baf1c23..dc09221711 100644 --- a/translations/pt-BR/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/index.md +++ b/translations/pt-BR/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/index.md @@ -8,6 +8,8 @@ versions: children: - /creating-an-issue-or-pull-request - /viewing-a-pull-request-in-github-desktop + - /viewing-and-re-running-checks-in-github-desktop + - /configuring-notifications-in-github-desktop - /changing-a-remotes-url-from-github-desktop shortTitle: Trabalhe com seu repositório remoto --- diff --git a/translations/pt-BR/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/viewing-a-pull-request-in-github-desktop.md b/translations/pt-BR/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/viewing-a-pull-request-in-github-desktop.md index e4794455e8..95c25d770f 100644 --- a/translations/pt-BR/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/viewing-a-pull-request-in-github-desktop.md +++ b/translations/pt-BR/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/viewing-a-pull-request-in-github-desktop.md @@ -15,6 +15,8 @@ Você pode visualizar os pull requests que você ou seus colaboradores propusera Ao visualizar um pull request no {% data variables.product.prodname_desktop %}, você poderá ver um histórico de commits feitos pelos contribuidores. Você também pode ver quais arquivos os commits modificaram, adicionaram ou excluíram. A partir do {% data variables.product.prodname_desktop %}, você pode abrir repositórios no seu editor de texto preferido para visualizar quaisquer alterações ou fazer alterações adicionais. Após revisar alterações em um pull request, você poderá dar um feedback em {% data variables.product.prodname_dotcom %}. Para obter mais informações, consulte "[Sobre merges do pull request](/github/collaborating-with-issues-and-pull-requests/about-pull-request-reviews)". +If checks have been enabled in your repository, {% data variables.product.prodname_desktop %} will show the status of the checks on the pull request and allow you to re-run checks. For more information, see "[Viewing and re-running checks in GitHub Desktop](/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/viewing-and-re-running-checks-in-github-desktop)." + ## Visualizar um pull request em {% data variables.product.prodname_desktop %} {% data reusables.desktop.current-branch-menu %} {% data reusables.desktop.click-pull-requests %} diff --git a/translations/pt-BR/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/viewing-and-re-running-checks-in-github-desktop.md b/translations/pt-BR/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/viewing-and-re-running-checks-in-github-desktop.md new file mode 100644 index 0000000000..b64026f492 --- /dev/null +++ b/translations/pt-BR/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/viewing-and-re-running-checks-in-github-desktop.md @@ -0,0 +1,25 @@ +--- +title: Viewing and re-running checks in GitHub Desktop +shortTitle: Viewing and re-running checks +intro: 'You can view the status of checks and re-run them in {% data variables.product.prodname_desktop %}.' +versions: + fpt: '*' +--- + +## About checks in {% data variables.product.prodname_desktop %} + +{% data variables.product.prodname_desktop %} displays the status of checks that have run in your pull request branches. The checks badge next to the branch name will display the *pending, passing,* or *failing* state of the checks. You can also re-run all, failed, or individual checks when viewing the status of the checks in {% data variables.product.prodname_desktop %}. For more information on setting up checks in your repository, see "[About status checks](/github/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks)." + +{% data variables.product.prodname_desktop %} will also show a system notification when checks fail. For more information on enabling notifications, see "[Configuring notifications in GitHub Desktop](/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/configuring-notifications-in-github-desktop)." + +## Viewing and re-running checks + +{% data reusables.desktop.current-branch-menu %} +{% data reusables.desktop.click-pull-requests %} + ![Guia Pull requests no menu suspenso Branch atual](/assets/images/help/desktop/branch-drop-down-pull-request-tab.png) +{% data reusables.desktop.choose-pr-from-list %} + ![Lista de pull requests em aberto no repositório](/assets/images/help/desktop/click-pull-request.png) +4. Click on the pull request number, to the right of the pull request branch name. ![Checks display next to branch name](/assets/images/help/desktop/checks-dialog.png) +5. To re-run failed checks, click **{% octicon "sync" aria-label="The sync icon" %} Re-run** and select **Re-run Failed Checks**. ![Re-run failed checks](/assets/images/help/desktop/re-run-failed-checks.png) +6. To re-run individual checks, hover over the individual check you want to re-run and select the {% octicon "sync" aria-label="The sync icon" %} icon to re-run the check. ![Re-run individual checks](/assets/images/help/desktop/re-run-individual-checks.png) +7. You will see a confirmation dialog with the summary of the checks that will be re-run. Click **Re-run Checks** to confirm that you want to perform the re-run. ![Re-run confirmation dialog](/assets/images/help/desktop/re-run-confirmation-dialog.png) diff --git a/translations/pt-BR/content/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps.md b/translations/pt-BR/content/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps.md index 0468c45121..1a7c1c2f40 100644 --- a/translations/pt-BR/content/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps.md +++ b/translations/pt-BR/content/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps.md @@ -149,7 +149,7 @@ Se um usuário revogar sua autorização de um aplicativo GitHub, o aplicativo r ## Permissões no nível do usuário -Você pode adicionar permissões de nível de usuário ao seu aplicativo GitHub para acessar os recursos de usuários, como, por exemplo, e-mails de usuários, concedidos por usuários individuais como parte do fluxo de autorização do usuário [](#identifying-users-on-your-site). User-level permissions differ from [repository and organization-level permissions](/rest/reference/permissions-required-for-github-apps), which are granted at the time of installation on an organization or personal account. +Você pode adicionar permissões de nível de usuário ao seu aplicativo GitHub para acessar os recursos de usuários, como, por exemplo, e-mails de usuários, concedidos por usuários individuais como parte do fluxo de autorização do usuário [](#identifying-users-on-your-site). As permissões de nível de usuário diferem das [permissões do repositório do nível de organização](/rest/reference/permissions-required-for-github-apps), que são concedidas no momento da instalação em uma conta de organização ou pessoal. Você pode selecionar permissões de nível de usuário nas configurações do seu aplicativo GitHub na seção **Permissões de usuário** na página **Permissões & webhooks**. Para obter mais informações sobre como selecionar permissões, consulte "[Editando permissões de um aplicativo GitHub](/apps/managing-github-apps/editing-a-github-app-s-permissions/)". diff --git a/translations/pt-BR/content/developers/apps/building-oauth-apps/scopes-for-oauth-apps.md b/translations/pt-BR/content/developers/apps/building-oauth-apps/scopes-for-oauth-apps.md index 291beb59ce..e3a6e23d85 100644 --- a/translations/pt-BR/content/developers/apps/building-oauth-apps/scopes-for-oauth-apps.md +++ b/translations/pt-BR/content/developers/apps/building-oauth-apps/scopes-for-oauth-apps.md @@ -67,9 +67,9 @@ X-Accepted-OAuth-Scopes: user |  `user:follow` | Concede acesso para seguir ou deixar de seguir outros usuários. | | **`delete_repo`** | Concede acesso para excluir repositórios administráveis. | | **`write:discussion`** | Permite acesso de leitura e gravação para discussões da equipe. | -|  `leia:discussion` | Permite acesso de leitura para discussões da equipe.{% ifversion fpt or ghae or ghec %} +|  `leia:discussion` | Allows read access for team discussions. | | **`write:packages`** | Concede acesso ao para fazer o upload ou publicação de um pacote no {% data variables.product.prodname_registry %}. Para obter mais informações, consulte "[Publicar um pacote](/github/managing-packages-with-github-packages/publishing-a-package)". | -| **`read:packages`** | Concede acesso ao download ou instalação de pacotes do {% data variables.product.prodname_registry %}. Para obter mais informações, consulte "[Instalando um pacote](/github/managing-packages-with-github-packages/installing-a-package)". | +| **`read:packages`** | Concede acesso ao download ou instalação de pacotes do {% data variables.product.prodname_registry %}. For more information, see "[Installing a package](/github/managing-packages-with-github-packages/installing-a-package)".{% ifversion fpt or ghec or ghes > 3.1 or ghae %} | **`delete:packages`** | Concede acesso para excluir pacotes de {% data variables.product.prodname_registry %}. Para obter mais informações, consulte "[Excluindo e restaurando um pacote](/packages/learn-github-packages/deleting-and-restoring-a-package)."{% endif %} | **`admin:gpg_key`** | Gerenciar totalmente as chaves GPG. | |  `write:gpg_key` | Criar, listar e visualizar informações das chaves GPG. | diff --git a/translations/pt-BR/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md b/translations/pt-BR/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md index eb995be181..05211df4f9 100644 --- a/translations/pt-BR/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md +++ b/translations/pt-BR/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md @@ -811,8 +811,6 @@ O webhook em que este evento está configurado em foi excluído. Este evento só {% endif %} -{% ifversion fpt or ghae or ghec %} - ## pacote Atividade relacionada a {% data variables.product.prodname_registry %}. {% data reusables.webhooks.action_type_desc %} Para obter mais informações, consulte "[Gerenciar pacotes com {% data variables.product.prodname_registry %}](/github/managing-packages-with-github-packages)" para saber mais sobre {% data variables.product.prodname_registry %}. @@ -832,7 +830,6 @@ Atividade relacionada a {% data variables.product.prodname_registry %}. {% data ### Exemplo de carga de webhook {{ webhookPayloadsForCurrentVersion.package.published }} -{% endif %} ## page_build diff --git a/translations/pt-BR/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/reuse-an-assignment.md b/translations/pt-BR/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/reuse-an-assignment.md index 3957465c51..9b682f1f74 100644 --- a/translations/pt-BR/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/reuse-an-assignment.md +++ b/translations/pt-BR/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/reuse-an-assignment.md @@ -11,28 +11,28 @@ shortTitle: Reutilizar uma atividade Você pode reutilizar uma atividade individual ou em grupo existente em qualquer outra sala de aula à qual você tenha acesso, incluindo as salas de aula em uma organização diferente. Se você optar por reutilizar uma atividade, {% data variables.product.prodname_classroom %} irá copiar a atividade para a sala de aula que você escolher. Se a atividade usar um repositório de modelo e você escolher reutilizá-lo em uma sala de aula de uma organização diferente, {% data variables.product.prodname_classroom %} criará uma cópia do repositório e seu conteúdo na organização de destino. -A atribuição copiada inclui detalhes da atividade, como nome, repositório de origem, teste de autoavaliação e editor preferido. You can edit the assignment after it has been copied to make changes. You cannot make changes to the preferred editor. +A atribuição copiada inclui detalhes da atividade, como nome, repositório de origem, teste de autoavaliação e editor preferido. Você pode editar a atividade depois de ela ter sido copiada para realizar alterações. Você não pode fazer alterações no editor preferido. -## Reusing an assignment +## Reutilizando uma atividade 1. Efetue o login em {% data variables.product.prodname_classroom_with_url %}. -1. Navigate to the classroom that has the assignment that you want to reuse. +1. Acesse a sala de aula com a atividade que você deseja reutilizar. ![Sala de aula na lista de salas de aula de uma organização](/assets/images/help/classroom/click-classroom-in-list.png) -1. In the list of assignments, click the assignment you want to reuse. +1. Na lista de atividades, clique na atividade que você deseja reutilizar. ![Atividade na lista de atividades para uma sala de aula](/assets/images/help/classroom/click-assignment-in-list.png) -1. Select the **{% octicon "pencil" aria-label="The pencil icon" %} Edit** dropdown menu in the top right of the page, then click **{% octicon "sync" aria-label="The sync icon" %} Reuse assignment**. +1. Selecione o menu suspenso **{% octicon "pencil" aria-label="The pencil icon" %} Editar** na parte superior direita da página e, em seguida, clique em **{% octicon "sync" aria-label="The sync icon" %} Reutilizar a atribuição**. - ![Reuse assignment button](/assets/images/help/classroom/reuse-assignment-button.png) + ![Botão de reutilizar a atividade](/assets/images/help/classroom/reuse-assignment-button.png) -1. In "Reuse assignment" modal, use the **Choose an organization** dropdown menu to select the organization you want the assignment to be in. Then use the **Choose a classroom** dropdown menu to select the classroom within that organization that you want to copy the assignment to. +1. No módulo "Reutilizar atividade", use o menu suspenso **Escolha uma organização** para selecionar a organização na qual você deseja que a atividade esteja. Em seguida, use o menu suspenso **Escolher uma sala de aula** para selecionar a sala de aula dentro da organização para a qual você deseja copiar a atividade. - ![Reuse assignment modal](/assets/images/help/classroom/reuse-assignment-modal.png) + ![Reutilizar o modo de atividade](/assets/images/help/classroom/reuse-assignment-modal.png) -1. Click **Create assignment**. -1. The assignment is copied to the selected classroom, and a confirmation message is shown. If you chose to reuse an assignment with a template repository, the copying process may take a few minutes to complete, and you may need to refresh the page to see the completed message. +1. Clique em **Criar atividade**. +1. A atividade foi copiada para a sala de aula selecionada e uma mensagem de confirmação foi exibida. Se você optar por reutilizar uma atividaed com um repositório do modelo, o processo de cópia poderá levar alguns minutos para ser concluído, e talvez você precise atualizar a página para ver a mensagem concluída. - ![Completed message for reused assignment](/assets/images/help/classroom/reuse-assignment-completed-message.png) + ![Mensagem concluída para atribuição reutilizada](/assets/images/help/classroom/reuse-assignment-completed-message.png) diff --git a/translations/pt-BR/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-the-git-and-github-starter-assignment.md b/translations/pt-BR/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-the-git-and-github-starter-assignment.md index ff39edad9e..d2940ac711 100644 --- a/translations/pt-BR/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-the-git-and-github-starter-assignment.md +++ b/translations/pt-BR/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-the-git-and-github-starter-assignment.md @@ -96,7 +96,7 @@ A atividade inicial do Git & {% data variables.product.company_short %} só est ## Próximas etapas -- Faça recomendações adicionais personalizadas para seu curso. For more information, see "[Create an individual assignment](/education/manage-coursework-with-github-classroom/create-an-individual-assignment)," "[Create a group assignment](/education/manage-coursework-with-github-classroom/create-a-group-assignment)," and "[Reuse an assignment](/education/manage-coursework-with-github-classroom/teach-with-github-classroom/reuse-an-assignment)." +- Faça recomendações adicionais personalizadas para seu curso. Para obter mais informações, consulte "[Criar uma atividade individual](/education/manage-coursework-with-github-classroom/create-an-individual-assignment), "[Criar uma atividade em grupo](/education/manage-coursework-with-github-classroom/create-a-group-assignment)e "[Reutilizar uma atividade](/education/manage-coursework-with-github-classroom/teach-with-github-classroom/reuse-an-assignment)". ## Leia mais diff --git a/translations/pt-BR/content/get-started/onboarding/getting-started-with-github-enterprise-server.md b/translations/pt-BR/content/get-started/onboarding/getting-started-with-github-enterprise-server.md index ed7a2355e4..a4f2ad7386 100644 --- a/translations/pt-BR/content/get-started/onboarding/getting-started-with-github-enterprise-server.md +++ b/translations/pt-BR/content/get-started/onboarding/getting-started-with-github-enterprise-server.md @@ -67,7 +67,7 @@ Como proprietário corporativo ou administrador, você pode gerenciar configura ## Parte 3: Criando com segurança Para aumentar a segurança de {% data variables.product.product_location %}, você pode configurar a autenticação para integrantes da empresa, usar ferramentas e registro de auditoria para manter a conformidade, configurar recursos de segurança e análise para as suas organizações e, opcionalmente, habilitar {% data variables.product.prodname_GH_advanced_security %}. ### 1. Efetuando a autenticação dos integrantes da empresa -You can use {% data variables.product.product_name %}'s built-in authentication method, or you can choose between an external authentication provider, such as CAS, LDAP, or SAML, to integrate your existing accounts and centrally manage user access to {% data variables.product.product_location %}. For more information, see "[About authentication for your enterprise](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise)." +Você pode usar o método de autenticação interno do {% data variables.product.product_name %} ou você pode escolher entre um provedor de autenticação externo como o CAS, LDAP ou SAML, para integrar suas contas existentes e gerenciar centralmente o acesso do usuário a {% data variables.product.product_location %}. Para obter mais informações, consulte "[Sobre a autenticação para sua empresa](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise)". Você também pode exigir autenticação de dois fatores para cada uma de suas organizações. Para obter mais informações, consulte "[Exigindo a autenticação de dois fatores para uma organização](/admin/user-management/managing-organizations-in-your-enterprise/requiring-two-factor-authentication-for-an-organization)". diff --git a/translations/pt-BR/content/get-started/quickstart/be-social.md b/translations/pt-BR/content/get-started/quickstart/be-social.md index 1863e1c5a1..139c148c3d 100644 --- a/translations/pt-BR/content/get-started/quickstart/be-social.md +++ b/translations/pt-BR/content/get-started/quickstart/be-social.md @@ -5,7 +5,7 @@ redirect_from: - /articles/be-social - /github/getting-started-with-github/be-social - /github/getting-started-with-github/quickstart/be-social -intro: 'Você pode interagir com pessoas, repositórios e organizações no {% data variables.product.prodname_dotcom %}. See what others are working on and who they are connecting with from your personal dashboard.' +intro: 'Você pode interagir com pessoas, repositórios e organizações no {% data variables.product.prodname_dotcom %}. Veja em que outras pessoas estão trabalhando e com quem estão se conectando a partir do seu painel pessoal.' permissions: '{% data reusables.enterprise-accounts.emu-permission-interact %}' versions: fpt: '*' @@ -24,17 +24,17 @@ Para saber mais sobre como acessar o painel pessoal, consulte "[Sobre seu painel ## Seguir pessoas -When you follow someone on {% data variables.product.prodname_dotcom %}, you will get notifications on your personal dashboard about their public activity. If someone you follow creates a new repository, stars a repository, or follows another user, the activity will display in your dashboard. +Ao seguir alguém em {% data variables.product.prodname_dotcom %}, você receberá notificações no seu painel pessoal sobre a atividade pública deles. Se alguém que você segue criar um novo repositório, favoritar um repositório ou seguir outro usuário, a atividade será exibida no seu painel. Clique em **Follow** (Seguir) na página do perfil de uma pessoa para segui-la. ![Botão Follow user (Seguir usuário)](/assets/images/help/profile/follow-user-button.png) -For more information, see "[Following people](/get-started/exploring-projects-on-github/following-people)." +Para obter mais informações, consulte "[Seguindo pessoas](/get-started/exploring-projects-on-github/following-people)". ## Inspecionar um repositório -You can subscribe to a repository to watch it and receive notifications for activity in it. When the owner updates the repository, you will see the changes in your personal dashboard. For more information, see "[Viewing your subscriptions](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions)." +Você pode assinar um repositório para inspecionar e receber notificações de atividade nele. Quando o proprietário atualiza o repositório, você vê as alterações no seu painel pessoal. Para obter mais informações, consulte "[Visualizando suas assinaturas](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions)". Clique em **Watch** (Inspecionar) no topo de um repositório para inspecioná-lo. @@ -46,28 +46,28 @@ Clique em **Watch** (Inspecionar) no topo de um repositório para inspecioná-lo ## Comunicando em {% data variables.product.product_name %} -{% data variables.product.product_name %} provides built-in collaborative communication tools, allowing you to interact closely with your community when building great software. For example, you can contribute to another user's project by creating a pull request, or use issues to track bugs or suggest ideas in a repository. You can also brainstorm new ideas with your team with discussions. +O {% data variables.product.product_name %} fornece ferramentas de comunicação colaborativas integradas, permitindo que você interaja de perto com sua comunidade ao criar um ótimo software. Por exemplo, você pode contribuir para o projeto de outro usuário criando um pull request ou usar problemas para rastrear erros ou sugerir ideias em um repositório. Também é possível levantar hipótses com sua equipe com discussões. -For an overview of these tools, see "[Quickstart for communicating on {% data variables.product.prodname_dotcom %}](/github/collaborating-with-issues-and-pull-requests/quickstart-for-communicating-on-github)." +Para uma visão geral destas ferramentas, consulte "[Início rápido para se comunicar em {% data variables.product.prodname_dotcom %}](/github/collaborating-with-issues-and-pull-requests/quickstart-for-communicating-on-github)". ## Participar em organizações As organizações são contas compartilhadas onde empresas e projetos de código aberto podem colaborar em muitos projetos de uma vez. Os proprietários e administradores podem definir equipes com permissões especiais, ter um perfil público da organização e acompanhar a atividade dentro da organização. Para obter mais informações, consulte "[Sobre organizações](/articles/about-organizations/)". -From your dashboard, click the drop down menu of your username on the left side of your dashboard. Here, you can view organizations that you are a part of and easily switch between them. +No painel de controle, clique no menu suspenso do seu nome de usuário no lado esquerdo do painel. Aqui, você pode ver as organizações das quais você faz parte e facilmente alternar entre elas. ![Menu suspenso de alternância de contexto da conta](/assets/images/help/overview/dashboard-contextswitcher.png) ### Explorar outros projetos no {% data variables.product.prodname_dotcom %} -You can discover new and interesting projects on {% data variables.product.prodname_dotcom %}'s Explore page. You can star interesting projects to make them easy to find again later. Visit your stars page to see all your starred projects. For more information about stars, see "[Saving repositories with stars](/get-started/exploring-projects-on-github/saving-repositories-with-stars)." +Você pode encontrar projetos novos e interessantes na página de explorar de {% data variables.product.prodname_dotcom %}. Você pode favoritar projetos interessantes para torná-los fáceis de encontrar mais tarde. Visite sua página de favoritos para ver todos os seus projetos favoritos. Para obter mais informações sobre estrelas, consulte "[Repositórios salvos com estrelas](/get-started/exploring-projects-on-github/saving-repositories-with-stars)". -Your dashboard feed displays projects based on your interests including repositories you star, people you follow, and your contributions to public repositories. From your dashboard, you can see trending projects, view topics, and check out collections. +Seu painel exibe projetos com base em seus interesses, incluindo repositórios que você favorita, pessoas que você segue e suas contribuições para repositórios públicos. No seu painel, você pode ver projetos em destaque, visualizar tópicos e conferir coleções. -To explore more projects, see "{% data variables.explore.explore_github %}". +Para explorar mais projetos, consulte "{% data variables.explore.explore_github %}". ## Próximas etapas -You are now connected to the {% data variables.product.product_name %} community. There are other ways to interact and build within {% data variables.product.product_name %}. +Agora você está conectado à comunidade de {% data variables.product.product_name %}. Existem outras maneiras de interagir e criar dentro de {% data variables.product.product_name %}. * {% data reusables.getting-started.set-up-git %} diff --git a/translations/pt-BR/content/get-started/quickstart/create-a-repo.md b/translations/pt-BR/content/get-started/quickstart/create-a-repo.md index e57be405a9..3a64933b72 100644 --- a/translations/pt-BR/content/get-started/quickstart/create-a-repo.md +++ b/translations/pt-BR/content/get-started/quickstart/create-a-repo.md @@ -5,7 +5,7 @@ redirect_from: - /articles/create-a-repo - /github/getting-started-with-github/create-a-repo - /github/getting-started-with-github/quickstart/create-a-repo -intro: 'To put your project up on {% data variables.product.prodname_dotcom %}, you will need to create a repository for it to live in.' +intro: 'Para colocar seu projeto no {% data variables.product.prodname_dotcom %}, você deverá criar um repositório para ele ser publicado.' versions: fpt: '*' ghes: '*' @@ -22,7 +22,7 @@ topics: {% ifversion fpt or ghec %} -Você pode armazenar vários projetos nos repositórios do {% data variables.product.prodname_dotcom %}, incluindo projetos de código aberto. With open source projects, you can share code to make better, more reliable software. Você pode usar repositórios para colaborar com outras pessoas e acompanhar seu trabalho. Para obter mais informações, consulte "[Sobre repositórios](/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/about-repositories)". To learn more about open source projects, visit [OpenSource.org](http://opensource.org/about). +Você pode armazenar vários projetos nos repositórios do {% data variables.product.prodname_dotcom %}, incluindo projetos de código aberto. Com projetos de código aberto, você pode compartilhar código para tornar o software melhor e mais confiável. Você pode usar repositórios para colaborar com outras pessoas e acompanhar seu trabalho. Para obter mais informações, consulte "[Sobre repositórios](/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/about-repositories)". Para saber mais sobre projetos de código aberto, acesse [OpenSource.org](http://opensource.org/about). {% elsif ghes or ghae %} @@ -78,7 +78,7 @@ Vamos fazer commit de uma alteração no arquivo *README*. 2. Acima do conteúdo do arquivo, clique em {% octicon "pencil" aria-label="The edit icon" %}. 3. Na guia **Edit file** (Editar arquivo), digite algumas informações sobre si mesmo. ![Novo conteúdo no arquivo](/assets/images/help/repository/edit-readme-light.png) {% data reusables.files.preview_change %} -5. Revise as alterações feitas no arquivo. You will see the new content in green. ![Visualização de arquivo](/assets/images/help/repository/create-commit-review.png) +5. Revise as alterações feitas no arquivo. Você verá o novo conteúdo em verde. ![Visualização de arquivo](/assets/images/help/repository/create-commit-review.png) {% data reusables.files.write_commit_message %} {% data reusables.files.choose_commit_branch %} {% data reusables.files.propose_file_change %} diff --git a/translations/pt-BR/content/get-started/quickstart/fork-a-repo.md b/translations/pt-BR/content/get-started/quickstart/fork-a-repo.md index 93c586c1a4..32d0a03e26 100644 --- a/translations/pt-BR/content/get-started/quickstart/fork-a-repo.md +++ b/translations/pt-BR/content/get-started/quickstart/fork-a-repo.md @@ -22,11 +22,11 @@ topics: ## Sobre bifurcações -Most commonly, forks are used to either propose changes to someone else's project to which you do not have write access, or to use someone else's project as a starting point for your own idea. Você pode bifurcar um repositório para criar uma cópia do repositório e fazer alterações sem afetar o repositório upstream. Para obter mais informações, consulte "[Trabalhando com as bifurcações](/github/collaborating-with-issues-and-pull-requests/working-with-forks)". +Mais comumente, as bifurcações são usadas para propor mudanças no projeto de outra pessoa ao qual você não tem acesso de gravação, ou para usar o projeto de outra pessoa como ponto de partida para sua própria ideia. Você pode bifurcar um repositório para criar uma cópia do repositório e fazer alterações sem afetar o repositório upstream. Para obter mais informações, consulte "[Trabalhando com as bifurcações](/github/collaborating-with-issues-and-pull-requests/working-with-forks)". ### Proponha mudanças no projeto de outra pessoa -Por exemplo, você pode usar bifurcações para propor alterações relacionadas à correção de um bug. Rather than logging an issue for a bug you have found, you can: +Por exemplo, você pode usar bifurcações para propor alterações relacionadas à correção de um bug. Em vez de registrar um problema para um erro que você encontrou, você pode: - Bifurcar o repositório. - Fazer a correção. @@ -48,7 +48,7 @@ Ao criar um repositório público a partir de uma bifurcação do projeto de out ## Pré-requisitos -If you have not yet, you should first [set up Git](/articles/set-up-git). Lembre-se também de [configurar a autenticação para {% data variables.product.product_location %} a partir do Git](/articles/set-up-git#next-steps-authenticating-with-github-from-git). +Se ainda não o fez, primeiro [configure o Git](/articles/set-up-git). Lembre-se também de [configurar a autenticação para {% data variables.product.product_location %} a partir do Git](/articles/set-up-git#next-steps-authenticating-with-github-from-git). ## Bifurcar um repositório @@ -84,7 +84,7 @@ gh repo fork repository --org "octo-org" ## Clonando o seu repositório bifurcado -Right now, you have a fork of the Spoon-Knife repository, but you do not have the files in that repository locally on your computer. +Agora, você tem uma bifurcação do repositório Spoon-Knife, mas você não tem os arquivos nesse repositório localmente no seu computador. {% webui %} @@ -145,7 +145,7 @@ Ao bifurcar um projeto para propor mudanças no repositório original, é possí - Para listar os arquivos e pastas em seu diretório atual, digite `ls`. - Para acessar um dos diretórios listados, digite `cd your_listed_directory`. - Para acessar um diretório, digite `cd ..`. -5. Digite `git remote -v` e pressione **Enter**. You will see the current configured remote repository for your fork. +5. Digite `git remote -v` e pressione **Enter**. Você verá o repositório remote atual configurado para sua bifurcação. ```shell $ git remote -v > origin https://{% data variables.command_line.codeblock %}/YOUR_USERNAME/YOUR_FORK.git (fetch) @@ -157,7 +157,7 @@ Ao bifurcar um projeto para propor mudanças no repositório original, é possí $ git remote add upstream https://{% data variables.command_line.codeblock %}/octocat/Spoon-Knife.git ``` -7. To verify the new upstream repository you have specified for your fork, type `git remote -v` again. Você deverá visualizar a URL da sua bifurcação como `origin` (origem) e a URL do repositório original como `upstream`. +7. Para verificar o novo repositório upstream que você especificou para sua bifurcação, digite novamente `git remote -v`. Você deverá visualizar a URL da sua bifurcação como `origin` (origem) e a URL do repositório original como `upstream`. ```shell $ git remote -v > origin https://{% data variables.command_line.codeblock %}/YOUR_USERNAME/YOUR_FORK.git (fetch) @@ -188,7 +188,7 @@ gh repo fork repository --remote-name "main-remote-repo" {% endcli %} -### Editing a fork +### Editando uma bifurcação Você pode fazer alterações em uma bifurcação, incluindo: @@ -206,10 +206,10 @@ Bifurque um repositório para começar a contribuir com um projeto. {% data reus Você já bifurcou um repositório, treinou clonar sua bifurcação e configurou um repositório upstream. -* For more information about cloning the fork and syncing the changes in a forked repository from your computer, see "[Set up Git](/articles/set-up-git)." +* Para obter mais informações sobre a clonagem da bifurcação e sincronizar as alterações em um repositório bifurcado a partir do seu computador, consulte "[Configurar o Git](/articles/set-up-git)". * Você também pode criar um novo repositório onde você pode colocar todos os seus projetos e compartilhar o código em {% data variables.product.prodname_dotcom %}. {% data reusables.getting-started.create-a-repository %}" -* Cada repositório em {% data variables.product.product_name %} pertence a uma pessoa ou organização. You can interact with users, repositories, and organizations by connecting and following them on {% data variables.product.product_name %}. {% data reusables.getting-started.being-social %} +* Cada repositório em {% data variables.product.product_name %} pertence a uma pessoa ou organização. Você pode interagir com usuários, repositórios e organizações, conectando-os e seguindo-os em {% data variables.product.product_name %}. {% data reusables.getting-started.being-social %} * {% data reusables.support.connect-in-the-forum-bootcamp %} diff --git a/translations/pt-BR/content/get-started/quickstart/github-glossary.md b/translations/pt-BR/content/get-started/quickstart/github-glossary.md index 04e7a7e2e0..e7cc7fbb14 100644 --- a/translations/pt-BR/content/get-started/quickstart/github-glossary.md +++ b/translations/pt-BR/content/get-started/quickstart/github-glossary.md @@ -23,5 +23,5 @@ versions: ## Leia mais - [Glossário oficial do Git](https://www.kernel.org/pub/software/scm/git/docs/gitglossary.html) -- [Git documentation](https://git-scm.com/doc) -- [Git command list](https://git-scm.com/docs) +- [Documentação do Git](https://git-scm.com/doc) +- [Lista de comandos Git](https://git-scm.com/docs) diff --git a/translations/pt-BR/content/get-started/quickstart/set-up-git.md b/translations/pt-BR/content/get-started/quickstart/set-up-git.md index 7afc4fe5c0..2869fa8932 100644 --- a/translations/pt-BR/content/get-started/quickstart/set-up-git.md +++ b/translations/pt-BR/content/get-started/quickstart/set-up-git.md @@ -27,11 +27,11 @@ topics: ## Usar o Git -To use Git on the command line, you will need to download, install, and configure Git on your computer. Você também pode instalar {% data variables.product.prodname_cli %} para usar {% data variables.product.prodname_dotcom %} a partir da linha de comando. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_cli %}](/github-cli/github-cli/about-github-cli)". +Para usar o Git na linha de comando, você precisará fazer download, instalar e configurar o Git no computador. Você também pode instalar {% data variables.product.prodname_cli %} para usar {% data variables.product.prodname_dotcom %} a partir da linha de comando. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_cli %}](/github-cli/github-cli/about-github-cli)". -If you want to work with Git locally, but do not want to use the command line, you can instead download and install the [{% data variables.product.prodname_desktop %}]({% data variables.product.desktop_link %}) client. Para obter mais informações, consulte "[Instalar e configurar o {% data variables.product.prodname_desktop %}](/desktop/installing-and-configuring-github-desktop/)". +Se quiser trabalhar com o Git, mas não quiser usar a linha de comando, você poderá fazer o download e instalar o cliente do [{% data variables.product.prodname_desktop %}]({% data variables.product.desktop_link %}). Para obter mais informações, consulte "[Instalar e configurar o {% data variables.product.prodname_desktop %}](/desktop/installing-and-configuring-github-desktop/)". -If you do not need to work with files locally, {% data variables.product.product_name %} lets you complete many Git-related actions directly in the browser, including: +Se não precisar trabalhar nos arquivos localmente, o {% data variables.product.product_name %} permite a execução de diversas ações relacionadas ao Git diretamente no navegador, incluindo: - [Criar um repositório](/articles/create-a-repo) - [Bifurcar um repositório](/articles/fork-a-repo) @@ -54,9 +54,9 @@ If you do not need to work with files locally, {% data variables.product.product 2. [Configure seu nome de usuário no Git](/github/getting-started-with-github/setting-your-username-in-git). 3. [Configure seu endereço de e-mail de commit no Git](/articles/setting-your-commit-email-address). -## Authenticating with {% data variables.product.prodname_dotcom %} from Git +## Efetuando a autenticação com {% data variables.product.prodname_dotcom %} a partir do Git -When you connect to a {% data variables.product.prodname_dotcom %} repository from Git, you will need to authenticate with {% data variables.product.product_name %} using either HTTPS or SSH. +Quando você se conecta a um repositório do {% data variables.product.prodname_dotcom %} a partir do Git, precisa fazer a autenticação no {% data variables.product.product_name %} usando HTTPS ou SSH. {% note %} @@ -66,15 +66,15 @@ When you connect to a {% data variables.product.prodname_dotcom %} repository fr ### Conexão por HTTPS (recomendada) -If you clone with HTTPS, you can cache your {% data variables.product.prodname_dotcom %} credentials in Git using a credential helper. For more information, see "[Cloning with HTTPS urls](/github/getting-started-with-github/about-remote-repositories/#cloning-with-https-urls)" and "[Caching your {% data variables.product.prodname_dotcom %} credentials in Git](/github/getting-started-with-github/caching-your-github-credentials-in-git)." +Se você fizer a clonagem com HTTPS, você pode armazenar suas credenciais de {% data variables.product.prodname_dotcom %} no Git usando um auxiliar de credenciais. Para obter mais informações, consulte "[Clonando com URLs de HTTPS](/github/getting-started-with-github/about-remote-repositories/#cloning-with-https-urls)" e "[Armazenando as suas credenciais de {% data variables.product.prodname_dotcom %} no cache do Git](/github/getting-started-with-github/caching-your-github-credentials-in-git)". ### Conexão por SSH -If you clone with SSH, you must generate SSH keys on each computer you use to push or pull from {% data variables.product.product_name %}. For more information, see "[Cloning with SSH urls](/github/getting-started-with-github/about-remote-repositories/#cloning-with-ssh-urls)" and "[Generating a new SSH key](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)." +Se você fizer a clonagem com SSH, você deverá gerar chaves SSH em cada computador que usar para fazer push ou pull a partir de {% data variables.product.product_name %}. Para obter mais informações, consulte "[Clonando com URLs de SSH](/github/getting-started-with-github/about-remote-repositories/#cloning-with-ssh-urls)" e "[Gerando uma nova chave SSH](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)". ## Próximas etapas -You now have Git and {% data variables.product.prodname_dotcom %} all set up. Agora você pode optar por criar um repositório onde possa colocar seus projetos. Saving your code in a repository allows you to back up your code and share it around the world. +Agora você o Git e {% data variables.product.prodname_dotcom %} estão configurados. Agora você pode optar por criar um repositório onde possa colocar seus projetos. Salvar seu código em um repositório permite que você faça backup do seu código e o compartilhe no mundo todo. * {% data reusables.getting-started.create-a-repository %}. diff --git a/translations/pt-BR/content/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md b/translations/pt-BR/content/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md index 2b42a6a539..18ae96e01e 100644 --- a/translations/pt-BR/content/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md +++ b/translations/pt-BR/content/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md @@ -318,7 +318,7 @@ A nota de rodapé será interpretada da seguinte forma: **Observação**: A posição de uma nota de rodapé no seu Markdown não influencia o lugar onde a nota de rodapé será interpretada. Você pode escrever uma nota de rodapé logo após sua referência à nota de rodapé, e ela continuará sendo interpretada na parte inferior do Markdown. -Footnotes are not supported in wikis. +Notas de rodapé não são compatíveis nos wikis. {% endtip %} {% endif %} diff --git a/translations/pt-BR/content/organizations/collaborating-with-groups-in-organizations/customizing-your-organizations-profile.md b/translations/pt-BR/content/organizations/collaborating-with-groups-in-organizations/customizing-your-organizations-profile.md index 80fffbd0a3..dca662415b 100644 --- a/translations/pt-BR/content/organizations/collaborating-with-groups-in-organizations/customizing-your-organizations-profile.md +++ b/translations/pt-BR/content/organizations/collaborating-with-groups-in-organizations/customizing-your-organizations-profile.md @@ -47,32 +47,32 @@ Você pode formatar o texto e incluir emoji, imagens e GIFs no README do perfil {% if org-profile-pin-private %} -## Adding a member-only organization profile README +## Adicionando um perfil README de organização somente apenas para membros -1. If your organization does not already have a `.github-private` repository, create a public `.github-private` repository. This action can be performed by any user that has write access to that repository. -2. In your organization's `.github-private` repository, create a `README.md` file in the `profile` folder. -3. Faça o commit das alterações para o arquivo `README.md`. The content of the `README.md` will be displayed in the member view of your organization's profile. +1. Se sua organização ainda não tiver um repositório `.github-private`, crie um repositório público `.github-private`. Esta ação pode ser executada por qualquer usuário que tenha acesso de gravação a esse repositório. +2. No repositório `.github-private` da sua organização, crie um arquivo `README.md` na pasta `perfil`. +3. Faça o commit das alterações para o arquivo `README.md`. O conteúdo do `README.md` será exibido no modo de exibição do integrante do perfil da sua organização. - ![Image of an organization's private README](/assets/images/help/organizations/org_member_readme.png) + ![Imagem do README privado de uma organização](/assets/images/help/organizations/org_member_readme.png) -## Pinning repositories to your organization's profile +## Fixando repositórios no perfil da sua organização -You can pin repositories that you want to feature, such as those that are frequently used, to your organization's profile page. To choose which repositories to pin to your organization's profile, you must be an organization owner or administrator. +Você pode fixar repositórios que deseja destacar, como aqueles que são usados com frequência, na página de perfil da sua organização. Para escolher quais repositórios deseja fixar no perfil da sua organização, você deve ser proprietário ou administrador da organização. -1. Navigate to your organization's profile page. -2. In the right sidebar of the page in the {% octicon "eye" aria-label="The eye octicon" %} "View as" link, choose the **Public** or **Member** profile view from the dropdown menu. +1. Acesse a página de perfil da sua organização. +2. Na barra lateral direita da página no link {% octicon "eye" aria-label="The eye octicon" %} "Visualizar como" escolha o perfil **público** ou **integrante** no menu suspenso. - ![Image of the organization profile view dropdown](/assets/images/help/organizations/org_profile_view.png) + ![Imagem da lista de visualização de perfil da organização](/assets/images/help/organizations/org_profile_view.png) -3. In the pinned repositories section, select **Customize pins**. +3. Na seção de repositórios fixados, selecione **Personalizar fixação**. - ![Image of the customize pins link](/assets/images/help/organizations/customize_pins_link.png) + ![Imagem do link da fixação personalizada](/assets/images/help/organizations/customize_pins_link.png) - - If you haven't yet pinned any repositories to your organization's profile, you'll need to instead click **pin repositories** in the right sidebar of the profile page. ![Image of pin repositories link in right sidebar](/assets/images/help/organizations/pin_repositories_link.png) + - Se você ainda não fixou nenhum repositório no perfil da sua organização. você deverá clicar em **fixar repositórios** na barra lateral direita da página de perfil. ![Imagem do link dos repositórios fixados na barra lateral direita](/assets/images/help/organizations/pin_repositories_link.png) -4. In the "Edit pinned repositories" dialog box, select a combination of up to six public, {% ifversion not fpt %}private, or internal{% else %}or private{% endif %} repositories to display. +4. Na caixa de diálogo "Editar repositórios fixados", selecione uma combinação de até seis repositórios públicos, {% ifversion not fpt %}privados ou internos{% else %}ou{% endif %} privados a serem exibidos. - ![Image of pinned repo dialog](/assets/images/help/organizations/pinned_repo_dialog.png) + ![Imagem de diálogo de repositório fixado](/assets/images/help/organizations/pinned_repo_dialog.png) 5. Clique em **Save pins** (Salvar itens fixos). diff --git a/translations/pt-BR/content/organizations/collaborating-with-your-team/about-team-discussions.md b/translations/pt-BR/content/organizations/collaborating-with-your-team/about-team-discussions.md index 639dcca451..80c453c867 100644 --- a/translations/pt-BR/content/organizations/collaborating-with-your-team/about-team-discussions.md +++ b/translations/pt-BR/content/organizations/collaborating-with-your-team/about-team-discussions.md @@ -44,7 +44,7 @@ Para obter mais informações, consulte {% ifversion fpt or ghae or ghes or ghec {% ifversion fpt or ghec %} -## Organization discussions +## Discussões da organização Você também pode usar discussões da organização para facilitar conversas em toda a sua organização. For more information, see "[Enabling or disabling GitHub Discussions for an organization](/organizations/managing-organization-settings/enabling-or-disabling-github-discussions-for-an-organization)." diff --git a/translations/pt-BR/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization.md b/translations/pt-BR/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization.md index a74ef061ea..3541465814 100644 --- a/translations/pt-BR/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization.md +++ b/translations/pt-BR/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization.md @@ -24,7 +24,7 @@ Você pode visualizar e revogar a identidade vinculada de cada integrante, as se {% data reusables.saml.about-linked-identities %} -Quando disponível, a entrada incluirá dados de SCIM. For more information, see "[About SCIM for organizations](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim-for-organizations)." +Quando disponível, a entrada incluirá dados de SCIM. Para obter mais informações, consulte "[Sobre SCIM para as organizações](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim-for-organizations)". {% warning %} diff --git a/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization.md b/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization.md index af99dcf5fd..f1f09c50f3 100644 --- a/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization.md +++ b/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization.md @@ -29,7 +29,7 @@ O proprietário da organização pode restringir a capacidade de convidar colabo {% endif %} {% ifversion ghes %} -Before you can add someone as an outside collaborator on a repository, the person must have a personal account on {% data variables.product.product_location %}. Se a empresa usa um sistema de autenticação externa, como SAML ou LDAP, a pessoa que você deseja adicionar deverá efetuar o login por meio desse sistema para criar uma conta. If the person does not have access to the authentication system and built-in authentication is enabled for your enterprise, a site administrator can create an account for the person. Para obter mais informações, consulte "[onfigurando a autenticação integrada](/admin/identity-and-access-management/using-built-in-authentication/configuring-built-in-authentication)". +Antes de adicionar alguém como colaborador externo em um repositório, a pessoa deve ter uma conta pessoal em {% data variables.product.product_location %}. Se a empresa usa um sistema de autenticação externa, como SAML ou LDAP, a pessoa que você deseja adicionar deverá efetuar o login por meio desse sistema para criar uma conta. Se a pessoa não tiver acesso ao sistema de autenticação e a autenticação integrada estiver habilitada para a sua empresa, um administrador do site poderá criar uma conta para a pessoa. Para obter mais informações, consulte "[onfigurando a autenticação integrada](/admin/identity-and-access-management/using-built-in-authentication/configuring-built-in-authentication)". {% endif %} {% ifversion not ghae %} diff --git a/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/reinstating-a-former-outside-collaborators-access-to-your-organization.md b/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/reinstating-a-former-outside-collaborators-access-to-your-organization.md index af2a388e89..6df01992b8 100644 --- a/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/reinstating-a-former-outside-collaborators-access-to-your-organization.md +++ b/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/reinstating-a-former-outside-collaborators-access-to-your-organization.md @@ -33,7 +33,7 @@ Ao restabelecer um ex-colaborador externo, você pode restaurar: **Dicas**: - - Only organization owners can reinstate outside collaborators' access to an organization.{% if prevent-org-admin-add-outside-collaborator %} Enterprise owners may further restrict the ability to reinstate outside collaborators' access to enterprise owners only.{% endif %} For more information, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)." + - Apenas proprietários da organização podem reinserir o acesso dos colaboradores externos à organização.{% if prevent-org-admin-add-outside-collaborator %} Os proprietários de empresas podem restringir ainda mais a capacidade de restabelecer o acesso dos colaboradores externos apenas a proprietários das empresas.{% endif %} Para obter mais informações, consulte "[Funções em uma organização](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)". - O fluxo de restabelecimento de um integrante no {% data variables.product.product_location %} pode usar o termo "integrante" para descrever o restabelecimento de um colaborador externo, mas se você restabelecer o usuário e mantiver os privilégios anteriores, ele terá apenas as [permissões anteriores de colaborador externo](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#outside-collaborators).{% ifversion fpt or ghec %} - Se a organização tiver uma assinatura paga por usuário, ela deverá ter uma licença não utilizada disponível para você poder convidar um integrante para participar da organização ou restabelecer um ex-integrante da organização. Para obter mais informações, consulte "[Sobre preços por usuário](/articles/about-per-user-pricing)."{% endif %} diff --git a/translations/pt-BR/content/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization.md b/translations/pt-BR/content/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization.md index b18bb6c5cc..48d55e3393 100644 --- a/translations/pt-BR/content/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization.md +++ b/translations/pt-BR/content/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization.md @@ -23,7 +23,7 @@ Se a organização tiver uma assinatura paga por usuário, ela deverá ter uma l Se a sua organização exige que os integrantes usem a autenticação de dois fatores, os usuários que você convidar deverão ativar a autenticação de dois fatores antes de aceitar o convite. Para mais informações, consulte "[Exigir a autenticação de dois fatores na sua organização](/organizations/keeping-your-organization-secure/requiring-two-factor-authentication-in-your-organization)" e[Proteger a sua conta com a autenticação de dois fatores (2FA)](/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa)". -{% ifversion fpt %}As organizações que usam {% data variables.product.prodname_ghe_cloud %}{% else %}Você{% endif %} podem implementar o SCIM para adicionar, gerenciar e remover o acesso dos integrantes da organização a {% data variables.product.prodname_dotcom_the_website %} por meio de um provedor de identidade (IdP). For more information, see "[About SCIM for organizations](/enterprise-cloud@latest/organizations/managing-saml-single-sign-on-for-your-organization/about-scim-for-organizations){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %} +{% ifversion fpt %}As organizações que usam {% data variables.product.prodname_ghe_cloud %}{% else %}Você{% endif %} podem implementar o SCIM para adicionar, gerenciar e remover o acesso dos integrantes da organização a {% data variables.product.prodname_dotcom_the_website %} por meio de um provedor de identidade (IdP). Para obter mais informações, consulte "[Sobre o SCIM para organizações](/enterprise-cloud@latest/organizations/managing-saml-single-sign-on-for-your-organization/about-scim-for-organizations){% ifversion fpt %}" na documentação de {% data variables.product.prodname_ghe_cloud %}.{% else %}."{% endif %} ## Convidando um usuário para participar da sua organização diff --git a/translations/pt-BR/content/organizations/managing-organization-settings/enabling-or-disabling-github-discussions-for-an-organization.md b/translations/pt-BR/content/organizations/managing-organization-settings/enabling-or-disabling-github-discussions-for-an-organization.md index e93b972e45..f40bac8152 100644 --- a/translations/pt-BR/content/organizations/managing-organization-settings/enabling-or-disabling-github-discussions-for-an-organization.md +++ b/translations/pt-BR/content/organizations/managing-organization-settings/enabling-or-disabling-github-discussions-for-an-organization.md @@ -1,25 +1,25 @@ --- -title: Enabling or disabling GitHub Discussions for an organization -intro: 'You can use {% data variables.product.prodname_discussions %} in a organization as a place for your organization to have conversations that aren''t specific to a single repository within your organization.' +title: Habilitando ou desabilitando as discussões no GitHub para uma organização +intro: 'Você pode usar o {% data variables.product.prodname_discussions %} em uma organização como um local para a sua organização ter conversas que não são específicas para um único repositório dentro da sua organização.' permissions: 'Organization owners can enable {% data variables.product.prodname_discussions %} for their organization.' versions: fpt: '*' ghec: '*' topics: - Organizations -shortTitle: Organization discussions +shortTitle: Discussões da organização --- -## About organization discussions +## Sobre as discussões na organização {% data reusables.discussions.about-organization-discussions %} -You can also manage repository discussions. For more information, see "[Enabling or disabling GitHub Discussions for a repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/enabling-or-disabling-github-discussions-for-a-repository)" and "[Managing discussion creation for repositories in your organization](/organizations/managing-organization-settings/managing-discussion-creation-for-repositories-in-your-organization)." +Você também pode gerenciar as discussões do repositório. Para obter mais informações, consulte "[Habilitando ou desabilitando discussões do GitHub para um repositório](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/enabling-or-disabling-github-discussions-for-a-repository)" e "[Gerenciando a criação de discussões para repositórios na sua organização](/organizations/managing-organization-settings/managing-discussion-creation-for-repositories-in-your-organization)". -## Enabling or disabling {% data variables.product.prodname_discussions %} for your organization +## Habilitando ou desabilitando {% data variables.product.prodname_discussions %} para a sua organização {% data reusables.discussions.enabling-or-disabling-github-discussions-for-your-organization %} -1. To disable discussions, under "Discussions", unselect **Enable discussions for this organization**. +1. Para desabilitar as discussões, em "Discussões", desmarque **Permitir discussões para esta organização**. ## Leia mais diff --git a/translations/pt-BR/content/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization.md b/translations/pt-BR/content/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization.md index 6ae0e9a448..47935b8e4c 100644 --- a/translations/pt-BR/content/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization.md +++ b/translations/pt-BR/content/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization.md @@ -42,7 +42,7 @@ A função não administrativa por padrão para as pessoas de uma organização {% ifversion fpt or ghec %} ### Moderadores da organização -Moderators are organization members who, in addition to their permissions as members, are allowed to block and unblock non-member contributors, set interaction limits, and hide comments in public repositories owned by the organization. Para obter mais informações, consulte "[Gerenciando os moderadores na sua organização](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-moderators-in-your-organization)". +Os moderadores são integrantes da organização que, além de suas permissões como integrantes, podem bloquear e desbloquear contribuidores não integrantes, definir limites de interação e ocultar comentários em repositórios públicos pertencentes à organização. Para obter mais informações, consulte "[Gerenciando os moderadores na sua organização](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-moderators-in-your-organization)". ### Gerentes de cobrança Os gerentes de cobrança são usuários que podem gerenciar as configurações de cobrança para a sua organização, como informações de pagamento. Essa é uma opção útil se os integrantes da sua organização geralmente não têm acesso aos recursos de cobrança. Para obter mais informações, consulte "[Adicionar um gerente de cobrança à sua organização](/organizations/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization)." @@ -78,121 +78,121 @@ Algumas das funcionalidades listadas abaixo estão limitadas a organizações qu {% ifversion fpt or ghec %} -| Permissão da organização | Proprietários | Integrantes | Moderadores | Gerentes de cobrança | Gerentes de segurança | -|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:-------------:|:-----------:|:-----------:|:--------------------:|:---------------------------:| -| Crie repositórios (consulte "[Restringir a criação de repositório na sua organização](/articles/restricting-repository-creation-in-your-organization)") | **X** | **X** | **X** | | **X** | -| Visualizar e editar informações de cobrança | **X** | | | **X** | | -| Convidar pessoas para integrar a organização | **X** | | | | | -| Editar e cancelar convites para integrar a organização | **X** | | | | | -| Remover integrantes da organização | **X** | | | | | -| Restabelecer ex-integrantes da organização | **X** | | | | | -| Adicionar e remover pessoas de **todas as equipes** | **X** | | | | | -| Promover integrantes da organização a *mantenedor de equipe* | **X** | | | | | -| Configurar as atribuições de revisão de código (consulte "[Gerenciar a atribuição de revisão de código para a sua equipe](/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team)") | **X** | | | | | -| Definir lembretes agendados (consulte "[Gerenciar lembretes agendados para pull requests](/github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-pull-requests)") | **X** | | | | | -| Adicionar colaboradores em **todos os repositórios** | **X** | | | | | -| Acessar o log de auditoria da organização | **X** | | | | | -| Edit the organization's profile page (see "[About your organization's profile](/github/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-organizations-profile)") | **X** | | | | |{% ifversion ghec %} -| Verify the organization's domains (see "[Verifying your organization's domain](/articles/verifying-your-organization-s-domain)") | **X** | | | | | -| Restrict email notifications to verified or approved domains (see "[Restricting email notifications for your organization](/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization)") | **X** | | | | +| Permissão da organização | Proprietários | Integrantes | Moderadores | Gerentes de cobrança | Gerentes de segurança | +|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:-------------:|:-----------:|:-----------:|:--------------------:|:---------------------------:| +| Crie repositórios (consulte "[Restringir a criação de repositório na sua organização](/articles/restricting-repository-creation-in-your-organization)") | **X** | **X** | **X** | | **X** | +| Visualizar e editar informações de cobrança | **X** | | | **X** | | +| Convidar pessoas para integrar a organização | **X** | | | | | +| Editar e cancelar convites para integrar a organização | **X** | | | | | +| Remover integrantes da organização | **X** | | | | | +| Restabelecer ex-integrantes da organização | **X** | | | | | +| Adicionar e remover pessoas de **todas as equipes** | **X** | | | | | +| Promover integrantes da organização a *mantenedor de equipe* | **X** | | | | | +| Configurar as atribuições de revisão de código (consulte "[Gerenciar a atribuição de revisão de código para a sua equipe](/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team)") | **X** | | | | | +| Definir lembretes agendados (consulte "[Gerenciar lembretes agendados para pull requests](/github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-pull-requests)") | **X** | | | | | +| Adicionar colaboradores em **todos os repositórios** | **X** | | | | | +| Acessar o log de auditoria da organização | **X** | | | | | +| Edite a página de perfil da organização (consulte "[Sobre o perfil da sua organização](/github/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-organizations-profile)") | **X** | | | | |{% ifversion ghec %} +| Verifique os domínios da organização (consulte "[verificando o domínio](/articles/verifying-your-organization-s-domain) da sua organização") | **X** | | | | | +| Restringir notificações de e-mail a domínios verificados ou aprovados (ver "[Restringindo notificações de e-mail para sua organização](/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization)") | **X** | | | | {% endif %} -| Excluir **todas as equipes** | **X** | | | | | -| Excluir a conta da organização, inclusive todos os repositórios | **X** | | | | | -| Create teams (see "[Setting team creation permissions in your organization](/articles/setting-team-creation-permissions-in-your-organization)") | **X** | **X** | **X** | | **X** | -| [Mover equipes na hierarquia da organização](/articles/moving-a-team-in-your-organization-s-hierarchy) | **X** | | | | | -| Create project boards (see "[Project board permissions for an organization](/articles/project-board-permissions-for-an-organization)") | **X** | **X** | **X** | | **X** | -| Ver todos os integrantes e equipes da organização | **X** | **X** | **X** | | **X** | -| @mencionar qualquer equipe visível | **X** | **X** | **X** | | **X** | -| Poder se tornar um *mantenedor de equipe* | **X** | **X** | **X** | | **X** |{% ifversion ghec %} -| View organization insights (see "[Viewing insights for your organization](/articles/viewing-insights-for-your-organization)") | **X** | **X** | **X** | | **X** +| Excluir **todas as equipes** | **X** | | | | | +| Excluir a conta da organização, inclusive todos os repositórios | **X** | | | | | +| Criar equipes (consulte "[Configurando permissões de criação de equipe na sua organização](/articles/setting-team-creation-permissions-in-your-organization)") | **X** | **X** | **X** | | **X** | +| [Mover equipes na hierarquia da organização](/articles/moving-a-team-in-your-organization-s-hierarchy) | **X** | | | | | +| Criar quadros de projetos (consulte "[Permissões para o quadro de projetos para uam organização](/articles/project-board-permissions-for-an-organization)") | **X** | **X** | **X** | | **X** | +| Ver todos os integrantes e equipes da organização | **X** | **X** | **X** | | **X** | +| @mencionar qualquer equipe visível | **X** | **X** | **X** | | **X** | +| Poder se tornar um *mantenedor de equipe* | **X** | **X** | **X** | | **X** |{% ifversion ghec %} +| Visualizar os insights da organização (consulte "[Visualizando informações para a sua organização](/articles/viewing-insights-for-your-organization)") | **X** | **X** | **X** | | **X** {% endif %} -| View and post public team discussions to **all teams** (see "[About team discussions](/organizations/collaborating-with-your-team/about-team-discussions)") | **X** | **X** | **X** | | **X** | -| View and post private team discussions to **all teams** (see "[About team discussions](/organizations/collaborating-with-your-team/about-team-discussions)") | **X** | | | | | -| Edit and delete team discussions in **all teams** (see "[Managing disruptive comments](/communities/moderating-comments-and-conversations/managing-disruptive-comments)") | **X** | | | | | -| Disable team discussions for an organization (see "[Disabling team discussions for your organization](/articles/disabling-team-discussions-for-your-organization)") | **X** | | | | | -| Hide comments on writable commits, pull requests, and issues (see "[Managing disruptive comments](/communities/moderating-comments-and-conversations/managing-disruptive-comments/#hiding-a-comment)") | **X** | **X** | **X** | | **X** | -| Hide comments on _all_ commits, pull requests, and issues (see "[Managing disruptive comments](/communities/moderating-comments-and-conversations/managing-disruptive-comments/#hiding-a-comment)") | **X** | | **X** | | **X** | -| Block and unblock non-member contributors (see "[Blocking a user from your organization](/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization)") | **X** | | **X** | | | -| Limit interactions for certain users in public repositories (see "[Limiting interactions in your organization](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization)") | **X** | | **X** | | |{% ifversion ghec %} -| Manage viewing of organization dependency insights (see "[Changing the visibility of your organization's dependency insights](/articles/changing-the-visibility-of-your-organizations-dependency-insights)") | **X** | | | | +| Visualize e publique discussões públicas de equipes para **todas as equipes** (Consulte "[Sobre discussões de equipes](/organizations/collaborating-with-your-team/about-team-discussions)") | **X** | **X** | **X** | | **X** | +| Visualize e publique discussões privadas em equipe para **todas as equipes** (veja "[Sobre discussões em equipes](/organizations/collaborating-with-your-team/about-team-discussions)") | **X** | | | | | +| Edite e exclua as discussões em equipe em **todas as equipes** (consulte "[Gerenciando comentários disruptivos](/communities/moderating-comments-and-conversations/managing-disruptive-comments)") | **X** | | | | | +| desabilite as discussões de equipe para uma organização (consulte "[Desabilitando discussões em equipe para a sua organização](/articles/disabling-team-discussions-for-your-organization)") | **X** | | | | | +| Ocultar comentários em commits, pull requests e problemas graváveis (consulte "[Gerenciando comentários disruptivos](/communities/moderating-comments-and-conversations/managing-disruptive-comments/#hiding-a-comment)") | **X** | **X** | **X** | | **X** | +| Ocultar comentários em _todos_ os commits, pull requests e problemas (consulte "[Gerenciando comentários disruptivos](/communities/moderating-comments-and-conversations/managing-disruptive-comments/#hiding-a-comment)") | **X** | | **X** | | **X** | +| Bloquear e desbloquear contribuidores que não são integrantes (consulte "[Bloquear um usuário da sua organização](/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization)") | **X** | | **X** | | | +| Limitar interações para certos usuários em repositórios públicos (consulte "[Limitando interações na sua organização](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization)") | **X** | | **X** | | |{% ifversion ghec %} +| Gerenciar a visualização dos insights de dependência da organização (consulte "[Alterando a visibilidade dos insights de dependências da sua organização](/articles/changing-the-visibility-of-your-organizations-dependency-insights)") | **X** | | | | {% endif %} -| Set a team profile picture in **all teams** (see "[Setting your team's profile picture](/articles/setting-your-team-s-profile-picture)") | **X** | | | | | -| Sponsor accounts and manage the organization's sponsorships (see "[Sponsoring open-source contributors](/sponsors/sponsoring-open-source-contributors)") | **X** | | | **X** | **X** | -| Manage email updates from sponsored accounts (see "[Managing updates from accounts your organization's sponsors](/organizations/managing-organization-settings/managing-updates-from-accounts-your-organization-sponsors)") | **X** | | | | | -| Atribuir seus patrocínios a outra organização (consulte "[Atribuir de patrocínios à sua organização](/sponsors/sponsoring-open-source-contributors/attributing-sponsorships-to-your-organization)" para obter mais detalhes) | **X** | | | | | -| Manage the publication of {% data variables.product.prodname_pages %} sites from repositories in the organization (see "[Managing the publication of {% data variables.product.prodname_pages %} sites for your organization](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)") | **X** | | | | | -| Manage security and analysis settings (see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)") | **X** | | | | **X** | -| View the security overview for the organization (see "[About the security overview](/code-security/security-overview/about-the-security-overview)") | **X** | | | | **X** |{% ifversion ghec %} -| Habilitar e executar [logon único SAML](/articles/about-identity-and-access-management-with-saml-single-sign-on) | **X** | | | | | -| [Gerenciar o acesso de SAML de um usuário à sua organização](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization) | **X** | | | | | -| Manage an organization's SSH certificate authorities (see "[Managing your organization's SSH certificate authorities](/articles/managing-your-organizations-ssh-certificate-authorities)") | **X** | | | | +| Definir a forot de um perfil da equipe em **todas as equipes** (consulte "[Configurando a foto de perfil da sua equipe](/articles/setting-your-team-s-profile-picture)") | **X** | | | | | +| Patrocinar contas e gerenciar os patrocínios da organização (consulte "[Patrocinando colaboradores de código aberto](/sponsors/sponsoring-open-source-contributors)") | **X** | | | **X** | **X** | +| Gerenciar atualizações de e-mail de contas patrocinadas (consulte "[Gerenciando atualizações a partir de contas que a sua organização patrocinou](/organizations/managing-organization-settings/managing-updates-from-accounts-your-organization-sponsors)") | **X** | | | | | +| Atribuir seus patrocínios a outra organização (consulte "[Atribuir de patrocínios à sua organização](/sponsors/sponsoring-open-source-contributors/attributing-sponsorships-to-your-organization)" para obter mais detalhes) | **X** | | | | | +| Gerenciar a publicação de sites de {% data variables.product.prodname_pages %} de repositórios na organização (consulte "[Gerenciando a publicação de sites de {% data variables.product.prodname_pages %} da sua organização](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)") | **X** | | | | | +| Gerenciar as configurações de segurança e análise (consulte "[Gerenciando as configurações de segurança e análise para sua organização](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)") | **X** | | | | **X** | +| Visualizar a visão geral de segurança da organização (consulte "[Sobre a visão geral de segurança](/code-security/security-overview/about-the-security-overview)") | **X** | | | | **X** |{% ifversion ghec %} +| Habilitar e executar [logon único SAML](/articles/about-identity-and-access-management-with-saml-single-sign-on) | **X** | | | | | +| [Gerenciar o acesso de SAML de um usuário à sua organização](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization) | **X** | | | | | +| Gerenciar as autoridades de certificado SSH de uma organização (consulte "["Gerenciando as autoridades de certificado SSH da sua organização](/articles/managing-your-organizations-ssh-certificate-authorities)") | **X** | | | | {% endif %} -| Transferir repósitórios | **X** | | | | | -| Comprar, instalar, gerenciar cobranças e cancelar aplicativos do {% data variables.product.prodname_marketplace %} | **X** | | | | | -| Listar aplicativos no {% data variables.product.prodname_marketplace %} | **X** | | | | | -| Recebe [{% data variables.product.prodname_dependabot_alerts %} sobre dependências vulneráveis](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies) para todos os repositórios de uma organização | **X** | | | | **X** | -| Gerenciar {% data variables.product.prodname_dependabot_security_updates %} (ver "[Sobre {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)") | **X** | | | | **X** | -| [Gerenciar a política de bifurcação](/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization) | **X** | | | | | -| [Limitar a atividade em repositórios públicos na organização](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization) | **X** | | | | | -| Pull (leitura) *todos os repositórios* na organização | **X** | | | | **X** | -| Push (gravação) e clonar (cópia) *todos os repositórios* na organização | **X** | | | | | -| Converter integrantes da organização em [colaboradores externos](#outside-collaborators) | **X** | | | | | -| [Exibir as pessoas com acesso a um repositório da organização](/articles/viewing-people-with-access-to-your-repository) | **X** | | | | |{% ifversion ghec %} -| [Exportar uma lista das pessoas com acesso a um repositório da organização](/articles/viewing-people-with-access-to-your-repository/#exporting-a-list-of-people-with-access-to-your-repository) | **X** | | | | +| Transferir repósitórios | **X** | | | | | +| Comprar, instalar, gerenciar cobranças e cancelar aplicativos do {% data variables.product.prodname_marketplace %} | **X** | | | | | +| Listar aplicativos no {% data variables.product.prodname_marketplace %} | **X** | | | | | +| Recebe [{% data variables.product.prodname_dependabot_alerts %} sobre dependências vulneráveis](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies) para todos os repositórios de uma organização | **X** | | | | **X** | +| Gerenciar {% data variables.product.prodname_dependabot_security_updates %} (ver "[Sobre {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)") | **X** | | | | **X** | +| [Gerenciar a política de bifurcação](/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization) | **X** | | | | | +| [Limitar a atividade em repositórios públicos na organização](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization) | **X** | | | | | +| Pull (leitura) *todos os repositórios* na organização | **X** | | | | **X** | +| Push (gravação) e clonar (cópia) *todos os repositórios* na organização | **X** | | | | | +| Converter integrantes da organização em [colaboradores externos](#outside-collaborators) | **X** | | | | | +| [Exibir as pessoas com acesso a um repositório da organização](/articles/viewing-people-with-access-to-your-repository) | **X** | | | | |{% ifversion ghec %} +| [Exportar uma lista das pessoas com acesso a um repositório da organização](/articles/viewing-people-with-access-to-your-repository/#exporting-a-list-of-people-with-access-to-your-repository) | **X** | | | | {% endif %} -| Gerenciar o nome do branch-padrão (consulte "[Gerenciar o nome do branch-padrão para repositórios na sua organização](/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization)") | **X** | | | | | -| Gerenciar etiquetas padrão (consulte "[Gerenciar etiquetas padrão nos repositórios da organização](/articles/managing-default-labels-for-repositories-in-your-organization)") | **X** | | | | |{% ifversion ghec %} -| Enable team synchronization (see "[Managing team synchronization for your organization](/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization)") | **X** | | | | +| Gerenciar o nome do branch-padrão (consulte "[Gerenciar o nome do branch-padrão para repositórios na sua organização](/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization)") | **X** | | | | | +| Gerenciar etiquetas padrão (consulte "[Gerenciar etiquetas padrão nos repositórios da organização](/articles/managing-default-labels-for-repositories-in-your-organization)") | **X** | | | | |{% ifversion ghec %} +| Habilitar a sincronização de equipes (consulte "[Gerenciando a sincronização de equipe para a sua organização](/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization)") | **X** | | | | {% endif %} -| Gerenciar revisões de pull request na organização (consulte "[Gerenciando revisões de pull request na sua organização](/organizations/managing-organization-settings/managing-pull-request-reviews-in-your-organization)") | **X** | | | | | +| Gerenciar revisões de pull request na organização (consulte "[Gerenciando revisões de pull request na sua organização](/organizations/managing-organization-settings/managing-pull-request-reviews-in-your-organization)") | **X** | | | | | {% elsif ghes > 3.2 or ghae-issue-4999 %} -| Ação da organização | Proprietários | Integrantes | Gerentes de segurança | -|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:-------------:|:-----------:|:--------------------------------------------:| -| Convidar pessoas para integrar a organização | **X** | | | -| Editar e cancelar convites para integrar a organização | **X** | | | -| Remover integrantes da organização | **X** | | | | -| Restabelecer ex-integrantes da organização | **X** | | | | -| Adicionar e remover pessoas de **todas as equipes** | **X** | | | -| Promover integrantes da organização a *mantenedor de equipe* | **X** | | | -| Configurar as atribuições de revisão de código (consulte "[Gerenciar a atribuição de revisão de código para a sua equipe](/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team)") | **X** | | | -| Adicionar colaboradores em **todos os repositórios** | **X** | | | -| Acessar o log de auditoria da organização | **X** | | | -| Edit the organization's profile page (see "[About your organization's profile](/github/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-organizations-profile)") | **X** | | |{% ifversion ghes > 3.1 %} -| Verify the organization's domains (see "[Verifying your organization's domain](/articles/verifying-your-organization-s-domain)") | **X** | | | -| Restrict email notifications to verified or approved domains (see "[Restricting email notifications for your organization](/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization)") | **X** | | +| Ação da organização | Proprietários | Integrantes | Gerentes de segurança | +|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:-------------:|:-----------:|:--------------------------------------------:| +| Convidar pessoas para integrar a organização | **X** | | | +| Editar e cancelar convites para integrar a organização | **X** | | | +| Remover integrantes da organização | **X** | | | | +| Restabelecer ex-integrantes da organização | **X** | | | | +| Adicionar e remover pessoas de **todas as equipes** | **X** | | | +| Promover integrantes da organização a *mantenedor de equipe* | **X** | | | +| Configurar as atribuições de revisão de código (consulte "[Gerenciar a atribuição de revisão de código para a sua equipe](/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team)") | **X** | | | +| Adicionar colaboradores em **todos os repositórios** | **X** | | | +| Acessar o log de auditoria da organização | **X** | | | +| Edite a página de perfil da organização (consulte "[Sobre o perfil da sua organização](/github/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-organizations-profile)") | **X** | | |{% ifversion ghes > 3.1 %} +| Verifique os domínios da organização (consulte "[verificando o domínio](/articles/verifying-your-organization-s-domain) da sua organização") | **X** | | | +| Restringir notificações de e-mail a domínios verificados ou aprovados (ver "[Restringindo notificações de e-mail para sua organização](/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization)") | **X** | | {% endif %} -| Excluir **todas as equipes** | **X** | | | -| Excluir a conta da organização, inclusive todos os repositórios | **X** | | | -| Create teams (see "[Setting team creation permissions in your organization](/articles/setting-team-creation-permissions-in-your-organization)") | **X** | **X** | **X** | -| Ver todos os integrantes e equipes da organização | **X** | **X** | **X** | -| @mencionar qualquer equipe visível | **X** | **X** | **X** | -| Poder se tornar um *mantenedor de equipe* | **X** | **X** | **X** | -| Transferir repósitórios | **X** | | | -| Manage security and analysis settings (see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)") | **X** | | **X** |{% ifversion ghes > 3.1 %} -| View the security overview for the organization (see "[About the security overview](/code-security/security-overview/about-the-security-overview)") | **X** | | **X** |{% endif %}{% ifversion ghes > 3.2 %} -| Gerenciar {% data variables.product.prodname_dependabot_security_updates %} (ver "[Sobre {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)") | **X** | | **X** +| Excluir **todas as equipes** | **X** | | | +| Excluir a conta da organização, inclusive todos os repositórios | **X** | | | +| Criar equipes (consulte "[Configurando permissões de criação de equipe na sua organização](/articles/setting-team-creation-permissions-in-your-organization)") | **X** | **X** | **X** | +| Ver todos os integrantes e equipes da organização | **X** | **X** | **X** | +| @mencionar qualquer equipe visível | **X** | **X** | **X** | +| Poder se tornar um *mantenedor de equipe* | **X** | **X** | **X** | +| Transferir repósitórios | **X** | | | +| Gerenciar as configurações de segurança e análise (consulte "[Gerenciando as configurações de segurança e análise para sua organização](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)") | **X** | | **X** |{% ifversion ghes > 3.1 %} +| Visualizar a visão geral de segurança da organização (consulte "[Sobre a visão geral de segurança](/code-security/security-overview/about-the-security-overview)") | **X** | | **X** |{% endif %}{% ifversion ghes > 3.2 %} +| Gerenciar {% data variables.product.prodname_dependabot_security_updates %} (ver "[Sobre {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)") | **X** | | **X** {% endif %} -| Manage an organization's SSH certificate authorities (see "[Managing your organization's SSH certificate authorities](/articles/managing-your-organizations-ssh-certificate-authorities)") | **X** | | | -| Create project boards (see "[Project board permissions for an organization](/articles/project-board-permissions-for-an-organization)") | **X** | **X** | **X** | -| View and post public team discussions to **all teams** (see "[About team discussions](/organizations/collaborating-with-your-team/about-team-discussions)") | **X** | **X** | **X** | -| View and post private team discussions to **all teams** (see "[About team discussions](/organizations/collaborating-with-your-team/about-team-discussions)") | **X** | | | -| Editar e excluir discussões de equipe em **todas as equipes** (para obter mais informações, consulte "[Gerenciar comentários conflituosos](/communities/moderating-comments-and-conversations/managing-disruptive-comments)) | **X** | | | | -| Hide comments on commits, pull requests, and issues (see "[Managing disruptive comments](/communities/moderating-comments-and-conversations/managing-disruptive-comments/#hiding-a-comment)") | **X** | **X** | **X** | -| Disable team discussions for an organization (see "[Disabling team discussions for your organization](/articles/disabling-team-discussions-for-your-organization)") | **X** | | | -| Set a team profile picture in **all teams** (see "[Setting your team's profile picture](/articles/setting-your-team-s-profile-picture)") | **X** | | |{% ifversion ghes > 3.0 %} -| Manage the publication of {% data variables.product.prodname_pages %} sites from repositories in the organization (see "[Managing the publication of {% data variables.product.prodname_pages %} sites for your organization](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)") | **X** | | +| Gerenciar as autoridades de certificado SSH de uma organização (consulte "["Gerenciando as autoridades de certificado SSH da sua organização](/articles/managing-your-organizations-ssh-certificate-authorities)") | **X** | | | +| Criar quadros de projetos (consulte "[Permissões para o quadro de projetos para uam organização](/articles/project-board-permissions-for-an-organization)") | **X** | **X** | **X** | +| Visualize e publique discussões públicas de equipes para **todas as equipes** (Consulte "[Sobre discussões de equipes](/organizations/collaborating-with-your-team/about-team-discussions)") | **X** | **X** | **X** | +| Visualize e publique discussões privadas em equipe para **todas as equipes** (veja "[Sobre discussões em equipes](/organizations/collaborating-with-your-team/about-team-discussions)") | **X** | | | +| Editar e excluir discussões de equipe em **todas as equipes** (para obter mais informações, consulte "[Gerenciar comentários conflituosos](/communities/moderating-comments-and-conversations/managing-disruptive-comments)) | **X** | | | | +| Ocultar comentários em commits, pull requests e problemas (consulte "[Gerenciando comentários disruptivos](/communities/moderating-comments-and-conversations/managing-disruptive-comments/#hiding-a-comment)") | **X** | **X** | **X** | +| desabilite as discussões de equipe para uma organização (consulte "[Desabilitando discussões em equipe para a sua organização](/articles/disabling-team-discussions-for-your-organization)") | **X** | | | +| Definir a forot de um perfil da equipe em **todas as equipes** (consulte "[Configurando a foto de perfil da sua equipe](/articles/setting-your-team-s-profile-picture)") | **X** | | |{% ifversion ghes > 3.0 %} +| Gerenciar a publicação de sites de {% data variables.product.prodname_pages %} de repositórios na organização (consulte "[Gerenciando a publicação de sites de {% data variables.product.prodname_pages %} da sua organização](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)") | **X** | | {% endif %} -| [Mover equipes na hierarquia da organização](/articles/moving-a-team-in-your-organization-s-hierarchy) | **X** | | | -| Pull (leitura) *todos os repositórios* na organização | **X** | | **X** | -| Push (gravação) e clonar (cópia) *todos os repositórios* na organização | **X** | | | -| Converter integrantes da organização em [colaboradores externos](#outside-collaborators) | **X** | | | -| [Exibir as pessoas com acesso a um repositório da organização](/articles/viewing-people-with-access-to-your-repository) | **X** | | | -| [Exportar uma lista das pessoas com acesso a um repositório da organização](/articles/viewing-people-with-access-to-your-repository/#exporting-a-list-of-people-with-access-to-your-repository) | **X** | | | -| Gerenciar etiquetas padrão (consulte "[Gerenciar etiquetas padrão nos repositórios da organização](/articles/managing-default-labels-for-repositories-in-your-organization)") | **X** | | |{% if pull-request-approval-limit %} -| Gerenciar revisões de pull request na organização (consulte "[Gerenciando revisões de pull request na sua organização](/organizations/managing-organization-settings/managing-pull-request-reviews-in-your-organization)") | **X** | | | +| [Mover equipes na hierarquia da organização](/articles/moving-a-team-in-your-organization-s-hierarchy) | **X** | | | +| Pull (leitura) *todos os repositórios* na organização | **X** | | **X** | +| Push (gravação) e clonar (cópia) *todos os repositórios* na organização | **X** | | | +| Converter integrantes da organização em [colaboradores externos](#outside-collaborators) | **X** | | | +| [Exibir as pessoas com acesso a um repositório da organização](/articles/viewing-people-with-access-to-your-repository) | **X** | | | +| [Exportar uma lista das pessoas com acesso a um repositório da organização](/articles/viewing-people-with-access-to-your-repository/#exporting-a-list-of-people-with-access-to-your-repository) | **X** | | | +| Gerenciar etiquetas padrão (consulte "[Gerenciar etiquetas padrão nos repositórios da organização](/articles/managing-default-labels-for-repositories-in-your-organization)") | **X** | | |{% if pull-request-approval-limit %} +| Gerenciar revisões de pull request na organização (consulte "[Gerenciando revisões de pull request na sua organização](/organizations/managing-organization-settings/managing-pull-request-reviews-in-your-organization)") | **X** | | | {% endif %} {% ifversion ghae %}| Gerenciar listas de permissão de IP (consulte "[Restringir tráfego de rede para a sua empresa](/admin/configuration/restricting-network-traffic-to-your-enterprise)") | **X** | | |{% endif %} @@ -200,44 +200,44 @@ Algumas das funcionalidades listadas abaixo estão limitadas a organizações qu {% else %} -| Ação da organização | Proprietários | Integrantes | -|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:-------------:|:------------------------------:| -| Convidar pessoas para integrar a organização | **X** | | -| Editar e cancelar convites para integrar a organização | **X** | | -| Remover integrantes da organização | **X** | | | -| Restabelecer ex-integrantes da organização | **X** | | | -| Adicionar e remover pessoas de **todas as equipes** | **X** | | -| Promover integrantes da organização a *mantenedor de equipe* | **X** | | -| Configure as atribuições de revisão de código (consulte "[Gerenciando as configurações de revisão de código da sua equipe](/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team)")) | **X** | | -| Adicionar colaboradores em **todos os repositórios** | **X** | | -| Acessar o log de auditoria da organização | **X** | | -| Edit the organization's profile page (see "[About your organization's profile](/github/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-organizations-profile)") | **X** | | |{% ifversion ghes > 3.1 %} -| Verify the organization's domains (see "[Verifying your organization's domain](/articles/verifying-your-organization-s-domain)") | **X** | | -| Restrict email notifications to verified or approved domains (see "[Restricting email notifications for your organization](/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization)") | **X** | +| Ação da organização | Proprietários | Integrantes | +|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:-------------:|:------------------------------:| +| Convidar pessoas para integrar a organização | **X** | | +| Editar e cancelar convites para integrar a organização | **X** | | +| Remover integrantes da organização | **X** | | | +| Restabelecer ex-integrantes da organização | **X** | | | +| Adicionar e remover pessoas de **todas as equipes** | **X** | | +| Promover integrantes da organização a *mantenedor de equipe* | **X** | | +| Configure as atribuições de revisão de código (consulte "[Gerenciando as configurações de revisão de código da sua equipe](/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team)")) | **X** | | +| Adicionar colaboradores em **todos os repositórios** | **X** | | +| Acessar o log de auditoria da organização | **X** | | +| Edite a página de perfil da organização (consulte "[Sobre o perfil da sua organização](/github/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-organizations-profile)") | **X** | | |{% ifversion ghes > 3.1 %} +| Verifique os domínios da organização (consulte "[verificando o domínio](/articles/verifying-your-organization-s-domain) da sua organização") | **X** | | +| Restringir notificações de e-mail a domínios verificados ou aprovados (ver "[Restringindo notificações de e-mail para sua organização](/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization)") | **X** | {% endif %} -| Excluir **todas as equipes** | **X** | | -| Excluir a conta da organização, inclusive todos os repositórios | **X** | | -| Create teams (see "[Setting team creation permissions in your organization](/articles/setting-team-creation-permissions-in-your-organization)") | **X** | **X** | -| Ver todos os integrantes e equipes da organização | **X** | **X** | -| @mencionar qualquer equipe visível | **X** | **X** | -| Poder se tornar um *mantenedor de equipe* | **X** | **X** | -| Transferir repósitórios | **X** | | -| Manage an organization's SSH certificate authorities (see "[Managing your organization's SSH certificate authorities](/articles/managing-your-organizations-ssh-certificate-authorities)") | **X** | | -| Create project boards (see "[Project board permissions for an organization](/articles/project-board-permissions-for-an-organization)") | **X** | **X** | | -| View and post public team discussions to **all teams** (see "[About team discussions](/organizations/collaborating-with-your-team/about-team-discussions)") | **X** | **X** | | -| View and post private team discussions to **all teams** (see "[About team discussions](/organizations/collaborating-with-your-team/about-team-discussions)") | **X** | | | -| Editar e excluir discussões de equipe em **todas as equipes** (para obter mais informações, consulte "[Gerenciar comentários conflituosos](/communities/moderating-comments-and-conversations/managing-disruptive-comments)) | **X** | | | -| Hide comments on commits, pull requests, and issues (see "[Managing disruptive comments](/communities/moderating-comments-and-conversations/managing-disruptive-comments/#hiding-a-comment)") | **X** | **X** | **X** | -| Disable team discussions for an organization (see "[Disabling team discussions for your organization](/articles/disabling-team-discussions-for-your-organization)") | **X** | | | -| Set a team profile picture in **all teams** (see "[Setting your team's profile picture](/articles/setting-your-team-s-profile-picture)") | **X** | | |{% ifversion ghes > 3.0 %} -| Manage the publication of {% data variables.product.prodname_pages %} sites from repositories in the organization (see "[Managing the publication of {% data variables.product.prodname_pages %} sites for your organization](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)") | **X** | +| Excluir **todas as equipes** | **X** | | +| Excluir a conta da organização, inclusive todos os repositórios | **X** | | +| Criar equipes (consulte "[Configurando permissões de criação de equipe na sua organização](/articles/setting-team-creation-permissions-in-your-organization)") | **X** | **X** | +| Ver todos os integrantes e equipes da organização | **X** | **X** | +| @mencionar qualquer equipe visível | **X** | **X** | +| Poder se tornar um *mantenedor de equipe* | **X** | **X** | +| Transferir repósitórios | **X** | | +| Gerenciar as autoridades de certificado SSH de uma organização (consulte "["Gerenciando as autoridades de certificado SSH da sua organização](/articles/managing-your-organizations-ssh-certificate-authorities)") | **X** | | +| Criar quadros de projetos (consulte "[Permissões para o quadro de projetos para uam organização](/articles/project-board-permissions-for-an-organization)") | **X** | **X** | | +| Visualize e publique discussões públicas de equipes para **todas as equipes** (Consulte "[Sobre discussões de equipes](/organizations/collaborating-with-your-team/about-team-discussions)") | **X** | **X** | | +| Visualize e publique discussões privadas em equipe para **todas as equipes** (veja "[Sobre discussões em equipes](/organizations/collaborating-with-your-team/about-team-discussions)") | **X** | | | +| Editar e excluir discussões de equipe em **todas as equipes** (para obter mais informações, consulte "[Gerenciar comentários conflituosos](/communities/moderating-comments-and-conversations/managing-disruptive-comments)) | **X** | | | +| Ocultar comentários em commits, pull requests e problemas (consulte "[Gerenciando comentários disruptivos](/communities/moderating-comments-and-conversations/managing-disruptive-comments/#hiding-a-comment)") | **X** | **X** | **X** | +| desabilite as discussões de equipe para uma organização (consulte "[Desabilitando discussões em equipe para a sua organização](/articles/disabling-team-discussions-for-your-organization)") | **X** | | | +| Definir a forot de um perfil da equipe em **todas as equipes** (consulte "[Configurando a foto de perfil da sua equipe](/articles/setting-your-team-s-profile-picture)") | **X** | | |{% ifversion ghes > 3.0 %} +| Gerenciar a publicação de sites de {% data variables.product.prodname_pages %} de repositórios na organização (consulte "[Gerenciando a publicação de sites de {% data variables.product.prodname_pages %} da sua organização](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)") | **X** | {% endif %} -| [Mover equipes na hierarquia da organização](/articles/moving-a-team-in-your-organization-s-hierarchy) | **X** | | | -| Fazer pull (ler), fazer push (gravar) e clonar (copiar) *todos os repositórios* na organização | **X** | | -| Converter integrantes da organização em [colaboradores externos](#outside-collaborators) | **X** | | -| [Exibir as pessoas com acesso a um repositório da organização](/articles/viewing-people-with-access-to-your-repository) | **X** | | -| [Exportar uma lista das pessoas com acesso a um repositório da organização](/articles/viewing-people-with-access-to-your-repository/#exporting-a-list-of-people-with-access-to-your-repository) | **X** | | -| Gerenciar etiquetas padrão (consulte "[Gerenciar etiquetas padrão nos repositórios da organização](/articles/managing-default-labels-for-repositories-in-your-organization)") | **X** | | +| [Mover equipes na hierarquia da organização](/articles/moving-a-team-in-your-organization-s-hierarchy) | **X** | | | +| Fazer pull (ler), fazer push (gravar) e clonar (copiar) *todos os repositórios* na organização | **X** | | +| Converter integrantes da organização em [colaboradores externos](#outside-collaborators) | **X** | | +| [Exibir as pessoas com acesso a um repositório da organização](/articles/viewing-people-with-access-to-your-repository) | **X** | | +| [Exportar uma lista das pessoas com acesso a um repositório da organização](/articles/viewing-people-with-access-to-your-repository/#exporting-a-list-of-people-with-access-to-your-repository) | **X** | | +| Gerenciar etiquetas padrão (consulte "[Gerenciar etiquetas padrão nos repositórios da organização](/articles/managing-default-labels-for-repositories-in-your-organization)") | **X** | | {% ifversion ghae %}| Gerenciar listas de permissão de IP (consulte "[Restringir tráfego de rede para a sua empresa](/admin/configuration/restricting-network-traffic-to-your-enterprise)") | **X** | |{% endif %} {% endif %} diff --git a/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md b/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md index 5f12d6bda9..99a807cfd9 100644 --- a/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md +++ b/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md @@ -46,7 +46,7 @@ Os integrantes da organização também devem ter uma sessão de SAML ativa para {% data reusables.saml.saml-supported-idps %} -Alguns IdPs são compatíveis com o o provisionamento de acesso a uma organização {% data variables.product.prodname_dotcom %} via SCIM. For more information, see "[About SCIM for organizations](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim-for-organizations)." +Alguns IdPs são compatíveis com o o provisionamento de acesso a uma organização {% data variables.product.prodname_dotcom %} via SCIM. Para obter mais informações, consulte "[Sobre SCIM para as organizações](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim-for-organizations)". {% data reusables.scim.enterprise-account-scim %} @@ -56,7 +56,7 @@ Depois que o SAML SSO é habilitado, há várias maneiras possíveis de adiciona Para provisionar novos usuários sem o convite de um proprietário da organização, você pode usar a URL `https://github.com/orgs/ORGANIZATION/sso/sign_up`, substituindo _ORGANIZATION_ pelo nome da sua organização. Por exemplo, é possível configurar o IdP para que qualquer pessoa que tenha acesso possa clicar em um link no painel do IdP para ingressar na sua organização do {% data variables.product.prodname_dotcom %}. -Se o seu IdP é compatível com o SCIM, o {% data variables.product.prodname_dotcom %} poderá convidar automaticamente integrantes para participarem da sua organização ao conceder acesso no seu IdP. Se você remover o acesso de um integrante à organização do seu {% data variables.product.prodname_dotcom %} no seu IdP de SAML, o integrante será removido automaticamente da organização de {% data variables.product.prodname_dotcom %}. For more information, see "[About SCIM for organizations](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim-for-organizations)." +Se o seu IdP é compatível com o SCIM, o {% data variables.product.prodname_dotcom %} poderá convidar automaticamente integrantes para participarem da sua organização ao conceder acesso no seu IdP. Se você remover o acesso de um integrante à organização do seu {% data variables.product.prodname_dotcom %} no seu IdP de SAML, o integrante será removido automaticamente da organização de {% data variables.product.prodname_dotcom %}. Para obter mais informações, consulte "[Sobre SCIM para as organizações](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim-for-organizations)". {% data reusables.organizations.team-synchronization %} diff --git a/translations/pt-BR/content/packages/learn-github-packages/about-permissions-for-github-packages.md b/translations/pt-BR/content/packages/learn-github-packages/about-permissions-for-github-packages.md index 5d74d99975..75784ab4e3 100644 --- a/translations/pt-BR/content/packages/learn-github-packages/about-permissions-for-github-packages.md +++ b/translations/pt-BR/content/packages/learn-github-packages/about-permissions-for-github-packages.md @@ -43,7 +43,7 @@ Para obter mais informações, consulte "[Configurar o controle de acesso e visi ## Sobre escopos e permissões para registros de pacotes -To use or manage a package hosted by a package registry, you must use a token with the appropriate scope, and your personal account must have appropriate permissions. +Para usar ou gerenciar um pacote hospedado por um registro de pacotes, você deve usar um token com o escopo apropriado, e sua conta pessoal deve ter as permissões necessárias. Por exemplo: - Para fazer o download e instalar pacotes de um repositório, seu token deve ter o escopo `read:packages` e sua conta de usuário deve ter permissão de leitura. diff --git a/translations/pt-BR/content/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility.md b/translations/pt-BR/content/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility.md index 5a29530561..ad82344cae 100644 --- a/translations/pt-BR/content/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility.md +++ b/translations/pt-BR/content/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility.md @@ -23,12 +23,12 @@ Para obter mais informações sobre permissões para pacotes com escopo de repos ## Configurar acesso a imagens de contêiner para sua conta pessoal -If you have admin permissions to a container image that's owned by a personal account, you can assign read, write, or admin roles to other users. Para obter mais informações sobre essas funções de permissão, consulte "[Visibilidade e permissões de acesso para imagens de contêiner](#visibility-and-access-permissions-for-container-images)". +Se você tiver permissões de administrador para uma imagem de contêiner que pertence a uma conta pessoal, você pode atribuir funções de leitura, gravação ou administração a outros usuários. Para obter mais informações sobre essas funções de permissão, consulte "[Visibilidade e permissões de acesso para imagens de contêiner](#visibility-and-access-permissions-for-container-images)". Se o seu pacote for privado ou interno e pertencer a uma organização, você somente poderá dar acesso a outros integrantes ou equipes da organização. {% data reusables.package_registry.package-settings-from-user-level %} -1. Na página de configurações do pacote, clique em **Convidar equipes ou pessoas** e digite o nome, nome de usuário ou e-mail da pessoa à qual você deseja conceder acesso. Teams cannot be given access to a container image owned by a personal account. ![Botão de convite de acesso ao contêiner](/assets/images/help/package-registry/container-access-invite.png) +1. Na página de configurações do pacote, clique em **Convidar equipes ou pessoas** e digite o nome, nome de usuário ou e-mail da pessoa à qual você deseja conceder acesso. As equipes não podem ter acesso a uma imagem de contêiner de uma conta pessoal. ![Botão de convite de acesso ao contêiner](/assets/images/help/package-registry/container-access-invite.png) 1. Ao lado do nome de usuário ou nome de equipe, use o menu suspenso "Função" para selecionar um nível de permissão desejado. ![Opções de acesso ao contêiner](/assets/images/help/package-registry/container-access-control-options.png) Os usuários selecionados receberão acesso automaticamente e não precisarão aceitar um convite primeiro. diff --git a/translations/pt-BR/content/packages/learn-github-packages/deleting-and-restoring-a-package.md b/translations/pt-BR/content/packages/learn-github-packages/deleting-and-restoring-a-package.md index 1fac8a1db5..d87cea97d4 100644 --- a/translations/pt-BR/content/packages/learn-github-packages/deleting-and-restoring-a-package.md +++ b/translations/pt-BR/content/packages/learn-github-packages/deleting-and-restoring-a-package.md @@ -181,7 +181,7 @@ Por exemplo, se você tem um pacote de RubyGems excluído denominado `octo-packa {% ifversion fpt or ghec %} Para restaurar um pacote excluído, você também deve atender a um desses requisitos de permissão: - Para pacotes com escopo de repositório: Você tem permissões de administrador no repositório ao qual o pacote excluído pertence.{% ifversion fpt or ghec %} - - For user-account scoped packages: Your personal account owns the deleted package. + - Para pacotes com escopo de conta de usuário: Sua conta pessoal é proprietária do pacote excluído. - Para os pacotes com escopo da organização: Você tem permissões de administrador para o pacote excluído na organização que é proprietário do pacote.{% endif %} {% endif %} @@ -209,7 +209,7 @@ Para revisar quem pode restaurar um pacote em uma organização, consulte "[Perm ### Restaurar um pacote com escopo de conta de usuário -You can restore a deleted package through your personal account settings, if the package was in one of your repositories or scoped to your personal account. Para obter mais informações, consulte "[Permissões necessárias](#required-permissions-to-delete-or-restore-a-package)". +Você pode restaurar um pacote excluído por meio das configurações da sua conta pessoal, se o pacote estiver em um de seus repositórios ou escopo para sua conta pessoal. Para obter mais informações, consulte "[Permissões necessárias](#required-permissions-to-delete-or-restore-a-package)". {% data reusables.user-settings.access_settings %} 2. À esquerda, clique em **Pacotes**. diff --git a/translations/pt-BR/content/packages/learn-github-packages/introduction-to-github-packages.md b/translations/pt-BR/content/packages/learn-github-packages/introduction-to-github-packages.md index 1ffeed2655..f4716e5ca3 100644 --- a/translations/pt-BR/content/packages/learn-github-packages/introduction-to-github-packages.md +++ b/translations/pt-BR/content/packages/learn-github-packages/introduction-to-github-packages.md @@ -23,7 +23,7 @@ shortTitle: Introduction ## About {% data variables.product.prodname_registry %} -{% data variables.product.prodname_registry %} is a platform for hosting and managing packages, including containers and other dependencies. {% data variables.product.prodname_registry %} combines your source code and packages in one place to provide integrated permissions management{% ifversion not ghae %} and billing{% endif %}, so you can centralize your software development on {% data variables.product.product_name %}. +{% data variables.product.prodname_registry %} is a platform for hosting and managing packages, including containers and other dependencies. {% data variables.product.prodname_registry %} combines your source code and packages in one place to provide integrated permissions management{% ifversion fpt or ghec %} and billing{% endif %}, so you can centralize your software development on {% data variables.product.product_name %}. You can integrate {% data variables.product.prodname_registry %} with {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} APIs, {% data variables.product.prodname_actions %}, and webhooks to create an end-to-end DevOps workflow that includes your code, CI, and deployment solutions. diff --git a/translations/pt-BR/content/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions.md b/translations/pt-BR/content/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions.md index d0ae4d6d60..27ad078626 100644 --- a/translations/pt-BR/content/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions.md +++ b/translations/pt-BR/content/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions.md @@ -51,7 +51,7 @@ Quando você habilita o GitHub Actions, o GitHub instala um aplicativo GitHub no {% ifversion fpt or ghec %} ## Sobre permissões e acesso de pacote para {% data variables.product.prodname_container_registry %} -O {% data variables.product.prodname_container_registry %} (`ghcr.io`) permite aos usuários criar e administrar contêineres como recursos independentes no nível da organização. Containers can be owned by an organization or personal account and you can customize access to each of your containers separately from repository permissions. +O {% data variables.product.prodname_container_registry %} (`ghcr.io`) permite aos usuários criar e administrar contêineres como recursos independentes no nível da organização. Os contêineres podem pertencer a uma conta pessoal ou organização e você pode personalizar o acesso a cada um dos seus contêineres separadamente das permissões de repositório. Todos os workflows que acessam o {% data variables.product.prodname_container_registry %} devem usar o `GITHUB_TOKEN` em vez de um token de acesso pessoal. Para obter mais informações sobre as melhores práticas de segurança, consulte "[Enrijecimento de segurança para o GitHub Actions](/actions/learn-github-actions/security-hardening-for-github-actions#using-secrets)". diff --git a/translations/pt-BR/content/packages/quickstart.md b/translations/pt-BR/content/packages/quickstart.md index e640a31936..9fdedf04a7 100644 --- a/translations/pt-BR/content/packages/quickstart.md +++ b/translations/pt-BR/content/packages/quickstart.md @@ -21,7 +21,7 @@ Neste guia, você criará um fluxo de trabalho de {% data variables.product.prod 1. Crie um novo repositório em {% data variables.product.prodname_dotcom %}, adicionando o `.gitignore` ao Node. Para obter mais informações, consulte "[Criando um novo repositório](/github/creating-cloning-and-archiving-repositories/creating-a-new-repository)." 2. Clone o repositório para a sua máquina local. ```shell - $ git clone https://{% ifversion ghae %}YOUR-HOSTNAME{% else %}github.com{% endif %}/YOUR-USERNAME/YOUR-REPOSITORY.git + $ git clone https://{% ifversion ghes or ghae %}YOUR-HOSTNAME{% else %}github.com{% endif %}/YOUR-USERNAME/YOUR-REPOSITORY.git $ cd YOUR-REPOSITORY ``` 3. Crie um arquivo `index.js` e adicione um alerta básico que diga "Hello world!" @@ -49,7 +49,7 @@ Neste guia, você criará um fluxo de trabalho de {% data variables.product.prod $ git push ``` 6. Crie um diretório `.github/workflows`. Nesse diretório, crie um arquivo denominado `release-package.yml`. -7. Copiar o conteúdo YAML a seguir no arquivo `release-package.yml`{% ifversion ghae %}, substituindo `YOUR-HOSTNAME` pelo nome da sua empresa{% endif %}. +7. Copiar o conteúdo YAML a seguir no arquivo `release-package.yml`{% ifversion ghes or ghae %}, substituindo `YOUR-HOSTNAME` pelo nome da sua empresa{% endif %}. ```yaml{:copy} name: Node.js Package @@ -79,7 +79,7 @@ Neste guia, você criará um fluxo de trabalho de {% data variables.product.prod - uses: {% data reusables.actions.action-setup-node %} with: node-version: 12 - registry-url: {% ifversion ghae %}https://npm.YOUR-HOSTNAME.com/{% else %}https://npm.pkg.github.com/{% endif %} + registry-url: {% ifversion ghes or ghae %}https://npm.YOUR-HOSTNAME.com/{% else %}https://npm.pkg.github.com/{% endif %} - run: npm ci - run: npm publish env: diff --git a/translations/pt-BR/content/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry.md b/translations/pt-BR/content/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry.md index 6d7f0fb3bf..96778cb296 100644 --- a/translations/pt-BR/content/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry.md +++ b/translations/pt-BR/content/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry.md @@ -30,7 +30,7 @@ Depois que suas imagens do Docker forem transferidas para o {% data variables.pr O {% data variables.product.prodname_container_registry %} é otimizado para dar suporte a algumas das necessidades únicas dos contêineres. Com o {% data variables.product.prodname_container_registry %}, você pode: -- Store container images within your organization and personal account, or connect them to a repository. +- Armazene imagens de contêiner na sua organização e conta pessoal, ou conecte-as a um repositório. - Escolha se deve herdar permissões de um repositório ou definir permissões granulares, independentemente de um repositório. - Acessar imagens de contêineres públicos anonimamente. diff --git a/translations/pt-BR/content/pages/configuring-a-custom-domain-for-your-github-pages-site/verifying-your-custom-domain-for-github-pages.md b/translations/pt-BR/content/pages/configuring-a-custom-domain-for-your-github-pages-site/verifying-your-custom-domain-for-github-pages.md index 1e86500e63..1b1c0e553e 100644 --- a/translations/pt-BR/content/pages/configuring-a-custom-domain-for-your-github-pages-site/verifying-your-custom-domain-for-github-pages.md +++ b/translations/pt-BR/content/pages/configuring-a-custom-domain-for-your-github-pages-site/verifying-your-custom-domain-for-github-pages.md @@ -12,7 +12,7 @@ shortTitle: Verificar um domínio personalizado ## Sobre a verificação de domínio para o GitHub Pages -When you verify your custom domain for your personal account or organization, only repositories owned by your personal account or organization may be used to publish a {% data variables.product.prodname_pages %} site to the verified custom domain or the domain's immediate subdomains. +Ao verificar seu domínio personalizado para sua conta pessoal ou organização, somente os repositórios pertencentes à sua conta pessoal ou organização podem ser usados para publicar um site de {% data variables.product.prodname_pages %} para o domínio personalizado verificado ou os subdomínios imediatos do domínio. Verificar seu domínio impede que outros usuários do GitHub de assumir seu domínio personalizado e usá-lo para publicar seu próprio site de {% data variables.product.prodname_pages %}. As tomadas de domínio podem acontecer quando você excluir seu repositório, quando seu plano de cobrança é rebaixado, ou após qualquer outra alteração que desvincula o domínio personalizado ou quando você desabilita {% data variables.product.prodname_pages %} enquanto o domínio permanece configurado para {% data variables.product.prodname_pages %} e não é verificado. diff --git a/translations/pt-BR/content/pages/getting-started-with-github-pages/about-github-pages.md b/translations/pt-BR/content/pages/getting-started-with-github-pages/about-github-pages.md index ee2af9e341..2adb324b7c 100644 --- a/translations/pt-BR/content/pages/getting-started-with-github-pages/about-github-pages.md +++ b/translations/pt-BR/content/pages/getting-started-with-github-pages/about-github-pages.md @@ -29,7 +29,7 @@ O {% data variables.product.prodname_pages %} é um serviço de hospedagem de si {% endif %} {% ifversion fpt or ghec %} -{% data reusables.pages.about-private-publishing %} For more information, see "[Changing the visibility of your {% data variables.product.prodname_pages %} site]({% ifversion fpt %}/enterprise-cloud@latest{% endif %}/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %} +{% data reusables.pages.about-private-publishing %} Para obter mais informações, consulte "[Alterando a visibilidade do seu site de {% data variables.product.prodname_pages %}]({% ifversion fpt %}/enterprise-cloud@latest{% endif %}/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site){% ifversion fpt %}" na documentação de {% data variables.product.prodname_ghe_cloud %}.{% else %}{% endif %} {% endif %} Para começar, consulte "[Criar um site do {% data variables.product.prodname_pages %}](/articles/creating-a-github-pages-site)". @@ -42,7 +42,7 @@ Os proprietários da organização podem desabilitar a publicação de sites do Há três tipos de site do {% data variables.product.prodname_pages %}: projeto, usuário e organização. Os sites de projeto são conectados a um projeto específico hospedado no {% data variables.product.product_name %}, como uma biblioteca do JavaScript ou um conjunto de receitas. Os sites de usuário e organização estão conectados a uma conta específica em {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}. -To publish a user site, you must create a repository owned by your personal account that's named {% ifversion fpt or ghec %}`.github.io`{% else %}`.`{% endif %}. Para publicar um site de organização, você deve criar um repositório pertencente a uma organização que se chama {% ifversion fpt or ghec %}`.github.io`{% else %}`.`{% endif %}. {% ifversion fpt or ghec %}A menos que você esteja usando um domínio personalizado, os sites de usuário e organização estarão disponíveis em `http(s)://.github.io` ou `http(s)://.github.io`.{% elsif ghae %}Sites de usuário e organização estão disponíveis em `http(s)://pages./` ou `http(s)://pages./`.{% endif %} +Para publicar um site de usuário, você deve criar um repositório pertencente à sua conta pessoal denominada {% ifversion fpt or ghec %}`. ithub.io`{% else %}`.`{% endif %}. Para publicar um site de organização, você deve criar um repositório pertencente a uma organização que se chama {% ifversion fpt or ghec %}`.github.io`{% else %}`.`{% endif %}. {% ifversion fpt or ghec %}A menos que você esteja usando um domínio personalizado, os sites de usuário e organização estarão disponíveis em `http(s)://.github.io` ou `http(s)://.github.io`.{% elsif ghae %}Sites de usuário e organização estão disponíveis em `http(s)://pages./` ou `http(s)://pages./`.{% endif %} Os arquivos de origem de um site de projeto são armazenados no mesmo repositório que o respectivo projeto. {% ifversion fpt or ghec %}A menos que você esteja usando um domínio personalizado, os sites de projeto estão disponíveis em `http(s)://.github.io/` ou `http(s)://.github.io/`.{% elsif ghae %}Os sites de projeto estão disponíveis em `http(s)://pages.///` ou `http(s)://pages.///`.{% endif %} @@ -54,7 +54,7 @@ Se você publicar seu site em particularmente, a URL do seu site será diferente Para obter mais informações sobre como os domínios personalizados afetam o URL do seu site, consulte "[Sobre domínios personalizados e {% data variables.product.prodname_pages %}](/articles/about-custom-domains-and-github-pages)". {% endif %} -Você só pode criar um site de usuário ou organização para cada conta em {% data variables.product.product_name %}. Project sites, whether owned by an organization or a personal account, are unlimited. +Você só pode criar um site de usuário ou organização para cada conta em {% data variables.product.product_name %}. Os sites de projeto, sejam eles de uma conta de organização ou pessoal , são ilimitados. {% ifversion ghes %} O URL onde o site estará disponível depende da habilitação do isolamento do subdomínio para o {% data variables.product.product_location %}. @@ -62,9 +62,9 @@ O URL onde o site estará disponível depende da habilitação do isolamento do | Tipo de site | Isolamento de subdomínio habilitado | Isolamento de subdomínio desabilitado | | ------------ | ----------------------------------- | ------------------------------------- | | | | | - User | + Usuário | -`http(s)://pages./` | `http(s):///pages/` | Organization | `http(s)://pages./` | `http(s):///pages/` | Project site owned by personal account | `http(s)://pages.///` | `http(s):///pages///` Project site owned by organization account | `http(s)://pages.///` | `http(s):///pages///` +`http(s)://pages./` | `http(s):///pages/` | Organização | `http(s)://pages./` | `http(s):///pages/` | Site do projeto pertencente à conta pessoal | `http(s)://pages.///` | `http(s):///pages///` Site do projeto pertencente à conta da organização | `http(s)://pages.///` | `http(s):///pages///` Para obter mais informações, consulte "[Habilitar isolamento de subdomínio](/enterprise/{{ currentVersion }}/admin/installation/enabling-subdomain-isolation)" ou entre em contato com o administrador do site. {% endif %} @@ -79,7 +79,7 @@ Se existir uma fonte de publicação padrão no repositório, o {% data variable Se você desejar manter os arquivos de origem do seu site em outro local, você poderá alterar a fonte de publicação do seu site. É possível publicar o site a partir de qualquer branch no repositório, a partir da raiz do repositório nesse branch, `/` ou a partir da pasta `/docs` nesse branch. Para obter mais informações, consulte "[Configurar uma fonte de publicação para seu site do {% data variables.product.prodname_pages %}](/articles/configuring-a-publishing-source-for-your-github-pages-site#choosing-a-publishing-source)". -If you choose the `/docs` folder of any branch as your publishing source, {% data variables.product.prodname_pages %} will read everything to publish your site{% ifversion fpt or ghec %}, including the _CNAME_ file,{% endif %} from the `/docs` folder.{% ifversion fpt or ghec %} For example, when you edit your custom domain through the {% data variables.product.prodname_pages %} settings, the custom domain will write to `/docs/CNAME`. Para obter mais informações sobre arquivos _CNAME_, consulte "[Gerenciar um domínio personalizado para seu site do {% data variables.product.prodname_pages %}](/articles/managing-a-custom-domain-for-your-github-pages-site)".{% endif %} +Se você escolher a pasta `/docs` de qualquer branch como a fonte de publicação, o {% data variables.product.prodname_pages %} lerá tudo a ser publicado no seu site{% ifversion fpt or ghec %}, inclusive o arquivo _CNAME_,{% endif %} na pasta `/docs`.{% ifversion fpt or ghec %} Por exemplo, quando você edita o domínio personalizado usando as configurações do {% data variables.product.prodname_pages %}, o domínio personalizado grava em `/docs/CNAME`. Para obter mais informações sobre arquivos _CNAME_, consulte "[Gerenciar um domínio personalizado para seu site do {% data variables.product.prodname_pages %}](/articles/managing-a-custom-domain-for-your-github-pages-site)".{% endif %} ## Geradores de site estáticos diff --git a/translations/pt-BR/content/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site.md b/translations/pt-BR/content/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site.md index 6ca906feda..0bd196aef0 100644 --- a/translations/pt-BR/content/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site.md +++ b/translations/pt-BR/content/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site.md @@ -19,16 +19,16 @@ Se sua empresa usar {% data variables.product.prodname_emus %}, todos os sites d Se a sua organização usar {% data variables.product.prodname_ghe_cloud %} sem {% data variables.product.prodname_emus %}, você poderá optar por publicar seus sites em particular ou publicamente para qualquer pessoa na internet. O controle de acesso está disponível para os sites de projeto publicados a partir de um repositório privado ou interno que pertencem à organização. Você não pode gerenciar o controle de acesso para um site da organização. Para obter mais informações sobre os tipos de sites do {% data variables.product.prodname_pages %}, consulte "[Sobre {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages#types-of-github-pages-sites)". -## About subdomains for privately published sites +## Sobre subdomínios para sites publicados em particular Os sites publicados em particular estão disponíveis em um subdomínio diferente dos sites publicados em modo público. Isso garante que seu site do {% data variables.product.prodname_pages %} esteja seguro a partir do momento em que for publicado: - Protegemos automaticamente todos os subdomínios de `*.pages.github.io` com um certificado TLS e aplicamos HSTS para garantir que os navegadores sempre servem a página por meio de HTTPS. -- We use a unique subdomain for the privately published site to ensure that other repositories in your organization cannot publish content on the same origin as the site. This protects your site from "[cookie tossing](https://github.blog/2013-04-09-yummy-cookies-across-domains/)". É por isso que também não hospedamos sites de {% data variables.product.prodname_pages %} no domínio do `github.com`. +- Usamos um subdomínio exclusivo para o site publicado de forma privada, para garantir que outros repositórios na organização não possam publicar conteúdo na mesma origem do site. Isso protege seu site contra "[cookies](https://github.blog/2013-04-09-yummy-cookies-across-domains/)". É por isso que também não hospedamos sites de {% data variables.product.prodname_pages %} no domínio do `github.com`. -You can see your site's unique subdomain in the "Pages" tab of your repository settings. Se você estiver usando um gerador de site estático configurado para criar o site com o nome do repositório como um caminho, talvez seja necessário atualizar as configurações para o gerador do site estático ao alterar o site para privado. Para obter mais informações, consulte "[Configurar o Jekyll no seu site de {% data variables.product.prodname_pages %}](/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site#configuring-a-subdomain)" ou a documentação para o gerador do seu site estático. +Você pode visualizar o subdomínio único do site na aba "Pages" das configurações do seu repositório. Se você estiver usando um gerador de site estático configurado para criar o site com o nome do repositório como um caminho, talvez seja necessário atualizar as configurações para o gerador do site estático ao alterar o site para privado. Para obter mais informações, consulte "[Configurar o Jekyll no seu site de {% data variables.product.prodname_pages %}](/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site#configuring-a-subdomain)" ou a documentação para o gerador do seu site estático. -To use a shorter and more memorable domain for your privately published site, you can configure a custom domain. Para obter mais informações, consulte "[Configurar um domínio personalizado para seu site do {% data variables.product.prodname_pages %}](/pages/configuring-a-custom-domain-for-your-github-pages-site)"" +Para usar um domínio mais curto e mais memorável para seu site publicado com privacidade, você pode configurar um domínio personalizado. Para obter mais informações, consulte "[Configurar um domínio personalizado para seu site do {% data variables.product.prodname_pages %}](/pages/configuring-a-custom-domain-for-your-github-pages-site)"" ## Alterar a visibilidade do seu site de {% data variables.product.prodname_pages %} diff --git a/translations/pt-BR/content/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site.md b/translations/pt-BR/content/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site.md index 03568f159d..918a8499f2 100644 --- a/translations/pt-BR/content/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site.md +++ b/translations/pt-BR/content/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site.md @@ -38,7 +38,7 @@ Se você escolher a pasta `docs` em qualquer branch como fonte de publicação e {% ifversion fpt %} -O seu sitede {% data variables.product.prodname_pages %} será sempre implantado com a execução de um fluxo de trabalho {% data variables.product.prodname_actions %}, mesmo que você tenha configurado seu site {% data variables.product.prodname_pages %} para ser criado usando uma ferramenta de CI diferente. A maioria dos fluxos de trabalho de CI externos fazem "implantação" no GitHub Pages, fazendo commit da saída da compilação no branch de `gh-pages` do repositório, e normalmente, incluem um arquivo `.nojekyll`. When this happens, the {% data variables.product.prodname_actions %} workflow will detect the state that the branch does not need a build step, and will execute only the steps necessary to deploy the site to {% data variables.product.prodname_pages %} servers. +O seu sitede {% data variables.product.prodname_pages %} será sempre implantado com a execução de um fluxo de trabalho {% data variables.product.prodname_actions %}, mesmo que você tenha configurado seu site {% data variables.product.prodname_pages %} para ser criado usando uma ferramenta de CI diferente. A maioria dos fluxos de trabalho de CI externos fazem "implantação" no GitHub Pages, fazendo commit da saída da compilação no branch de `gh-pages` do repositório, e normalmente, incluem um arquivo `.nojekyll`. Quando isso acontecer, o fluxo de trabalho de {% data variables.product.prodname_actions %} detectará o estado de que o branch não precisa de uma etapa de criação e seguirá as etapas necessárias para implantar o site em servidores de {% data variables.product.prodname_pages %}. Para encontrar possíveis erros com a compilação ou implantação, você pode verificar a execução do fluxo de trabalho para o seu site de {% data variables.product.prodname_pages %} revisando a execução do fluxo de trabalho do seu repositório. Para obter mais informações, consulte "[Visualizar histórico de execução de fluxo de trabalho](/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history)". Para obter mais informações sobre como executar novamente o fluxo de trabalho em caso de erro, consulte "[Executar novamente fluxos de trabalho e trabalhos](/actions/managing-workflow-runs/re-running-workflows-and-jobs)". diff --git a/translations/pt-BR/data/release-notes/enterprise-server/3-4/1.yml b/translations/pt-BR/data/release-notes/enterprise-server/3-4/1.yml index 5e6fc57e13..2abebda14d 100644 --- a/translations/pt-BR/data/release-notes/enterprise-server/3-4/1.yml +++ b/translations/pt-BR/data/release-notes/enterprise-server/3-4/1.yml @@ -47,7 +47,6 @@ sections: - When "Users can search GitHub.com" is enabled with {% data variables.product.prodname_github_connect %}, issues in private and internal repositories are not included in {% data variables.product.prodname_dotcom_the_website %} search results. - O registro npm de {% data variables.product.prodname_registry %} não retorna mais o valor de tempo em respostas de metadados. Isso foi feito para permitir melhorias substanciais de desempenho. Continuamos a ter todos os dados necessários para devolver um valor de tempo como parte da resposta aos metadados e retomaremos o retorno desse valor no futuro, assim que tivermos resolvido os problemas de desempenho existentes. - Os limites de recursos que são específicos para processamento de hooks pre-receive podem causar falha em alguns hooks pre-receive. - - Actions services need to be restarted after restoring appliance from backup taken on a different host. - | When using SAML encrypted assertions with {% data variables.product.prodname_ghe_server %} 3.4.0 and 3.4.1, a new XML attribute `WantAssertionsEncrypted` in the `SPSSODescriptor` contains an invalid attribute for SAML metadata. IdPs that consume this SAML metadata endpoint may encounter errors when validating the SAML metadata XML schema. A fix will be available in the next patch release. [Updated: 2022-04-11] diff --git a/translations/pt-BR/data/release-notes/enterprise-server/3-4/2.yml b/translations/pt-BR/data/release-notes/enterprise-server/3-4/2.yml index 49d597e0db..35e9aa7ad0 100644 --- a/translations/pt-BR/data/release-notes/enterprise-server/3-4/2.yml +++ b/translations/pt-BR/data/release-notes/enterprise-server/3-4/2.yml @@ -32,7 +32,6 @@ sections: - When "Users can search GitHub.com" is enabled with {% data variables.product.prodname_github_connect %}, issues in private and internal repositories are not included in {% data variables.product.prodname_dotcom_the_website %} search results. - O registro npm de {% data variables.product.prodname_registry %} não retorna mais o valor de tempo em respostas de metadados. Isso foi feito para permitir melhorias substanciais de desempenho. Continuamos a ter todos os dados necessários para devolver um valor de tempo como parte da resposta aos metadados e retomaremos o retorno desse valor no futuro, assim que tivermos resolvido os problemas de desempenho existentes. - Os limites de recursos que são específicos para processamento de hooks pre-receive podem causar falha em alguns hooks pre-receive. - - Actions services need to be restarted after restoring appliance from backup taken on a different host. - | When using SAML encrypted assertions with {% data variables.product.prodname_ghe_server %} 3.4.0 and 3.4.1, a new XML attribute `WantAssertionsEncrypted` in the `SPSSODescriptor` contains an invalid attribute for SAML metadata. IdPs that consume this SAML metadata endpoint may encounter errors when validating the SAML metadata XML schema. A fix will be available in the next patch release. [Updated: 2022-04-11] diff --git a/translations/pt-BR/data/reusables/actions/supported-github-runners.md b/translations/pt-BR/data/reusables/actions/supported-github-runners.md index cb541947bb..00d9f521ef 100644 --- a/translations/pt-BR/data/reusables/actions/supported-github-runners.md +++ b/translations/pt-BR/data/reusables/actions/supported-github-runners.md @@ -50,6 +50,17 @@ Ubuntu 18.04 +macOS Monterey 12 + + +macos-12 + + +macOS 12 is currently in public beta. + + + + macOS Big Sur 11 diff --git a/translations/pt-BR/data/reusables/audit_log/audit-log-action-categories.md b/translations/pt-BR/data/reusables/audit_log/audit-log-action-categories.md index 1e5f15386b..f3688c32aa 100644 --- a/translations/pt-BR/data/reusables/audit_log/audit-log-action-categories.md +++ b/translations/pt-BR/data/reusables/audit_log/audit-log-action-categories.md @@ -76,7 +76,7 @@ | `org_credential_authorization` | Contains activities related to authorizing credentials for use with SAML single sign-on. {%- endif %} {%- if secret-scanning-audit-log-custom-patterns %} -| `org_secret_scanning_custom_pattern` | Contains activities related to custom patterns for secret scanning in an organization. Para obter mais informações, consulte "[Definindo padrões personalizados para digitalização de segredo](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning). " | `org.secret_scanning_push_protection` | Contains activities related to secret scanning custom patterns in an organization. For more information, see "[Protecting pushes with secret scanning](/code-security/secret-scanning/protecting-pushes-with-secret-scanning)." +| `org_secret_scanning_custom_pattern` | Contains activities related to custom patterns for secret scanning in an organization. Para obter mais informações, consulte "[Definindo padrões personalizados para digitalização de segredo](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning). " | `org.secret_scanning_push_protection` | Contains activities related to secret scanning custom patterns in an organization. Para obter mais informações, consulte "[Protegendo pushes com digitalização de segredo](/code-security/secret-scanning/protecting-pushes-with-secret-scanning)". {%- endif %} | `organization_default_label` | Contains activities related to default labels for repositories in an organization. {%- ifversion fpt or ghec or ghes > 3.1 %} @@ -111,7 +111,7 @@ | `repository_secret_scanning` | Contains repository-level activities related to secret scanning. Para obter mais informações, consulte "[Sobre a varredura de segredos](/github/administering-a-repository/about-secret-scanning)." {%- endif %} {%- if secret-scanning-audit-log-custom-patterns %} -| `repository_secret_scanning_custom_pattern` | Contains activities related to secret scanning custom patterns in a repository. Para obter mais informações, consulte "[Definindo padrões personalizados para digitalização de segredo](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning). " |{% endif %}{% if secret-scanning-audit-log-custom-patterns %}| | `repository_secret_scanning_push_protection` | Contains activities related to secret scanning custom patterns in a repository. For more information, see "[Protecting pushes with secret scanning](/code-security/secret-scanning/protecting-pushes-with-secret-scanning)." +| `repository_secret_scanning_custom_pattern` | Contains activities related to secret scanning custom patterns in a repository. Para obter mais informações, consulte "[Definindo padrões personalizados para digitalização de segredo](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning). " |{% endif %}{% if secret-scanning-audit-log-custom-patterns %}| | `repository_secret_scanning_push_protection` | Contains activities related to secret scanning custom patterns in a repository. Para obter mais informações, consulte "[Protegendo pushes com digitalização de segredo](/code-security/secret-scanning/protecting-pushes-with-secret-scanning)". {%- endif %} {%- ifversion fpt or ghec %} | `repository_visibility_change` | Contains activities related to allowing organization members to change repository visibilities for the organization. diff --git a/translations/pt-BR/data/reusables/codespaces/codespaces-org-policies.md b/translations/pt-BR/data/reusables/codespaces/codespaces-org-policies.md new file mode 100644 index 0000000000..8302bdc4bf --- /dev/null +++ b/translations/pt-BR/data/reusables/codespaces/codespaces-org-policies.md @@ -0,0 +1,3 @@ +1. Na seção "Código, planejamento e automação" da barra lateral, selecione **{% octicon "codespaces" aria-label="The codespaces icon" %} {% data variables.product.prodname_codespaces %}** e, em seguida, clique em **Políticas**. +1. Na página "Políticas do codespace", clique em **Criar política**. +1. Insira um nome para sua nova política. \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/codespaces/codespaces-policy-targets.md b/translations/pt-BR/data/reusables/codespaces/codespaces-policy-targets.md new file mode 100644 index 0000000000..d0e2cf2fc3 --- /dev/null +++ b/translations/pt-BR/data/reusables/codespaces/codespaces-policy-targets.md @@ -0,0 +1,11 @@ +1. Na área "Alterar destino da política", clique no botão suspenso. +1. Selecione **Todos os repositórios** ou **Repositórios selecionados** para determinar em quais repositórios esta política será aplicada. +1. Se você escolheu **repositórios selecionados**: + 1. Clique em {% octicon "gear" aria-label="The settings icon" %}. + + ![Editar as configurações da política](/assets/images/help/codespaces/policy-edit.png) + + 2. Selecione os repositórios aos quais você quer que esta política seja aplicada. + 3. Na parte inferior da lista de repositórios, clique em **Selecionar repositórios**. + + ![Selecionar repositórios para esta política](/assets/images/help/codespaces/policy-select-repos.png) diff --git a/translations/pt-BR/data/reusables/projects/enable-basic-workflow.md b/translations/pt-BR/data/reusables/projects/enable-basic-workflow.md index fa23f9b50d..92bb137381 100644 --- a/translations/pt-BR/data/reusables/projects/enable-basic-workflow.md +++ b/translations/pt-BR/data/reusables/projects/enable-basic-workflow.md @@ -1,4 +1,6 @@ -1. In your project, click {% octicon "workflow" aria-label="the workflow icon" %}. +1. Navigate to your project. +1. In the top-right, click {% octicon "kebab-horizontal" aria-label="The menu icon" %} to open the menu. +1. In the menu, click {% octicon "workflow" aria-label="The workflow icon" %} **Workflows**. 1. Under **Default workflows**, click on the workflow that you want to edit. 1. If the workflow can apply to both issues and pull requests, next to **When**, check the item type(s) that you want to act on. 1. Next to **Set**, choose the value that you want to set the status to. diff --git a/translations/pt-BR/data/reusables/projects/project-settings.md b/translations/pt-BR/data/reusables/projects/project-settings.md index bee73a5c66..4c244857b3 100644 --- a/translations/pt-BR/data/reusables/projects/project-settings.md +++ b/translations/pt-BR/data/reusables/projects/project-settings.md @@ -1,2 +1,3 @@ 1. Navigate to your project. -1. Click {% octicon "gear" aria-label="the gear icon" %} to access the project settings. +1. In the top-right, click {% octicon "kebab-horizontal" aria-label="The menu icon" %} to open the menu. +1. In the menu, click {% octicon "gear" aria-label="The gear icon" %} **Settings** to access the project settings. diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/setting-your-profile-to-private.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/setting-your-profile-to-private.md index 6d236d1cd1..59b535a581 100644 --- a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/setting-your-profile-to-private.md +++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/setting-your-profile-to-private.md @@ -1,63 +1,63 @@ --- -title: Setting your profile to private -intro: 'A private profile displays only limited information, and hides some activity.' +title: 将您的个人资料设置为私密 +intro: 私密个人资料仅显示有限的信息，并隐藏某些活动。 versions: fpt: '*' topics: - Profiles -shortTitle: Set profile to private +shortTitle: 将个人资料设置为私密 --- -## About private profiles +## 关于私密个人资料 {% note %} -**Note:** Private profiles are currently in beta and are subject to change. +**注意：**私密个人资料目前处于测试阶段，可能会有所变化。 {% endnote %} -To hide parts of your profile page, you can make your profile private. This also hides your activity in various social features on {% data variables.product.prodname_dotcom_the_website %}. A private profile hides information from all users, and there is currently no option to allow specified users to see your activity. +要隐藏部分个人资料页面，您可以将个人资料设为私密。 这也会隐藏您在 {% data variables.product.prodname_dotcom_the_website %} 上的各种社交功能中的活动。 私密个人资料会隐藏所有用户的信息，并且当前没有允许指定用户查看您的活动的选项。 -After making your profile private, you can still view all your information when you visit your own profile. +将个人资料设为私密后，您仍然可以在访问自己的个人资料时查看所有信息。 -Private profiles cannot receive sponsorships under [{% data variables.product.prodname_sponsors %}](/sponsors/getting-started-with-github-sponsors/about-github-sponsors). To be eligible for {% data variables.product.prodname_sponsors %}, your profile cannot be private. +私密个人资料在 [{% data variables.product.prodname_sponsors %}](/sponsors/getting-started-with-github-sponsors/about-github-sponsors) 下不能获得赞助。 要获得 {% data variables.product.prodname_sponsors %} 资格，您的个人资料不能是私密的。 -## Differences between private and public profiles +## 私密个人资料与公共个人资料之间的差异 -When your profile is private, the following content is hidden from your profile page: +当您的个人资料为私密时，您的个人资料页面中会隐藏以下内容： -- Achievements and highlights. -- Activity overview and activity feed. -- Contribution graph. -- Follower and following counts. -- Follow and Sponsor buttons. -- Organization memberships. -- Stars, projects, packages, and sponsoring tabs. +- 成就和亮点。 +- 活动概述和活动源。 +- 贡献图。 +- 关注者和关注数。 +- 关注和赞助者按钮。 +- 组织成员资格。 +- 星标、项目、包和赞助标签。 {% note %} -**Note**: When your profile is private, some optional fields are still publicly visible, such as the README, biography, and profile photo. +**注意**：当您的个人资料为私密时，某些可选字段仍可公开显示，例如自述文件、传记和头像。 {% endnote %} -## Changes to reporting on your activities +## 更改活动报告 -By making your profile private, you will not remove or hide past activity; this setting only applies to your activity while the private setting is enabled. +通过将个人资料设为私密，您无法删除或隐藏过去的活动；此设置仅适用于启用私密设置时的活动。 -When your profile is private, your {% data variables.product.prodname_dotcom_the_website %} activity will not appear in the following locations: +当您的个人资料为私密时，您的 {% data variables.product.prodname_dotcom_the_website %} 活动将不会显示在以下位置： -- Activity feeds for other users. -- Discussions leaderboards. -- The [Trending](https://github.com/trending) page. +- 其他用户的活动源。 +- 讨论排行榜。 +- [热门](https://github.com/trending)页面。 {% note %} -**Note**: Your activity on public repositories will still be publicly visible to anyone viewing those repositories, and some activity data may still be available through the {% data variables.product.prodname_dotcom %} API. +**注意**：您在公共仓库上的活动仍将对查看这些仓库的任何人公开可见，并且某些活动数据可能仍可通过 {% data variables.product.prodname_dotcom %} API 获得。 {% endnote %} -## Changing your profile's privacy settings +## 更改个人资料的隐私设置 {% data reusables.user-settings.access_settings %} -1. Under "Contributions & Activity", select the checkbox next to **Make profile private and hide activity**. +1. 在“Contributions & Activity（贡献和活动）”下，选中 **Make profile private and hide activity（将个人资料设为私密并隐藏活动）**旁边的复选框。 {% data reusables.user-settings.update-preferences %} diff --git a/translations/zh-CN/content/actions/using-workflows/about-workflows.md b/translations/zh-CN/content/actions/using-workflows/about-workflows.md index 34f7c968d4..14e5cb9929 100644 --- a/translations/zh-CN/content/actions/using-workflows/about-workflows.md +++ b/translations/zh-CN/content/actions/using-workflows/about-workflows.md @@ -1,7 +1,7 @@ --- title: 关于工作流程 shortTitle: 关于工作流程 -intro: 'Get a high level overview {% data variables.product.prodname_actions %} workflows, including triggers, syntax, and advanced features.' +intro: '获取 {% data variables.product.prodname_actions %} 工作流程的高级概述，包括触发器、语法和高级功能。' versions: fpt: '*' ghes: '*' @@ -20,15 +20,15 @@ miniTocMaxHeadingLevel: 3 {% data reusables.actions.about-workflows-long %} -## Workflow basics +## 工作流程基础知识 -A workflow must contain the following basic components: +工作流程必须包含以下基本组件： -1. One or more _events_ that will trigger the workflow. -1. One or more _jobs_, each of which will execute on a _runner_ machine and run a series of one or more _steps_. -1. Each step can either run a script that you define or run an action, which is a reusable extension that can simplify your workflow. +1. 将触发工作流程的一个或多个_事件_。 +1. 一个或多个_作业_，每个作业将在_运行器_计算机上执行，并运行一系列一个或多个_步骤_。 +1. 每个步骤都可以运行您定义的脚本，也可以运行操作，这是一个可重用的扩展，可以简化您的工作流程。 -For more information these basic components, see "[Understanding GitHub Actions](/actions/learn-github-actions/understanding-github-actions#the-components-of-github-actions)." +For more information on these basic components, see "[Understanding GitHub Actions](/actions/learn-github-actions/understanding-github-actions#the-components-of-github-actions)." ![工作流程概述](/assets/images/help/images/overview-actions-simple.png) @@ -36,32 +36,32 @@ For more information these basic components, see "[Understanding GitHub Actions] {% data reusables.actions.about-triggers %} -For more information, see "[Triggering a workflow](/actions/using-workflows/triggering-a-workflow)", and for a full list of events, see "[Events that trigger workflows](/actions/using-workflows/events-that-trigger-workflows)." +更多信息请参阅“[触发工作流程](/actions/using-workflows/triggering-a-workflow)”，有关事件的完整列表，请参阅“[触发工作流程的事件](/actions/using-workflows/events-that-trigger-workflows)”。 ## 工作流程语法 -Workflow are defined using YAML. For the full reference of the YAML syntax for authoring workflows, see "[Workflow syntax for GitHub Actions](/actions/using-workflows/workflow-syntax-for-github-actions#about-yaml-syntax-for-workflows)." +工作流程是使用 YAML 定义的。 有关用于创建工作流程的 YAML 语法的完整参考，请参阅“[GitHub Actions 的工作流程语法](/actions/using-workflows/workflow-syntax-for-github-actions#about-yaml-syntax-for-workflows)”。 {% data reusables.actions.workflow-basic-example-and-explanation %} -For more on managing workflow runs, such as re-running, cancelling, or deleting a workflow run, see "[Managing workflow runs](/actions/managing-workflow-runs)." +有关管理工作流程运行（如重新运行、取消或删除工作流程运行）的详细信息，请参阅“[管理工作流程运行](/actions/managing-workflow-runs)”。 ## 使用入门工作流程 {% data reusables.actions.workflow-template-overview %} -For more information on using and creating starter workflows, see "[Using starter workflows](/actions/using-workflows/using-starter-workflows)" and "[Creating starter workflows for your organization](/actions/using-workflows/creating-starter-workflows-for-your-organization)." +有关使用和创建入门工作流程的详细信息，请参阅“[使用入门工作流程](/actions/using-workflows/using-starter-workflows)”和“[为组织创建入门工作流程](/actions/using-workflows/creating-starter-workflows-for-your-organization)”。 ## 高级工作流程功能 -This section briefly describes some of the advanced features of {% data variables.product.prodname_actions %} that help you create more complex workflows. +本节简介了 {% data variables.product.prodname_actions %} 的一些高级功能，可帮助您创建更复杂的工作流程。 ### 存储密码 -如果您的工作流程使用敏感数据，例如密码或证书， 您可以将这些信息在 {% data variables.product.prodname_dotcom %} 中保存为 _机密_，然后在工作流中将它们用作环境变量。 This means that you will be able to create and share workflows without having to embed sensitive values directly in the workflow's YAML source. +如果您的工作流程使用敏感数据，例如密码或证书， 您可以将这些信息在 {% data variables.product.prodname_dotcom %} 中保存为 _机密_，然后在工作流中将它们用作环境变量。 这意味着您将能够创建和共享工作流程，而无需直接在工作流程的 YAML 源中嵌入敏感值。 -This example job demonstrates how to reference an existing secret as an environment variable, and send it as a parameter to an example command. +此示例作业演示如何将现有机密引用为环境变量，并将其作为参数发送到示例命令。 {% raw %} ```yaml @@ -81,7 +81,7 @@ jobs: ### 创建依赖的作业 -默认情况下，工作流程中的作业同时并行运行。 If you have a job that must only run after another job has completed, you can use the `needs` keyword to create this dependency. If one of the jobs fails, all dependent jobs are skipped; however, if you need the jobs to continue, you can define this using the `if` conditional statement. +默认情况下，工作流程中的作业同时并行运行。 如果您有一个作业必须在另一个作业完成后运行，可以使用 `needs` 关键字来创建此依赖项。 如果其中一个作业失败，则跳过所有从属作业；但如果您需要作业继续，可以使用条件语句 `if` 来定义。 在此示例中，`setup`、`build` 和 `test` 作业连续运行，`build` 和 `test` 取决于其前面的作业成功完成： @@ -107,7 +107,7 @@ jobs: ### 使用构建矩阵 -You can use a build matrix if you want your workflow to run tests across multiple combinations of parameters, such as operating systems, platforms, and languages. 构建矩阵是使用 `strategy` 关键字创建的，它接收构建选项作为数组。 例如，此构建矩阵将使用不同版本的 Node.js 多次运行作业： +如果您希望工作流程跨参数（如操作系统、平台和语言）的多个组合运行测试，可以使用构建矩阵。 构建矩阵是使用 `strategy` 关键字创建的，它接收构建选项作为数组。 例如，此构建矩阵将使用不同版本的 Node.js 多次运行作业： ```yaml jobs: @@ -173,7 +173,7 @@ jobs: POSTGRES_PORT: 5432 ``` -For more information, see "[Using containerized services](/actions/using-containerized-services)." +更多信息请参阅“[使用容器化服务](/actions/using-containerized-services)”。 ### 使用标签路由工作流程 @@ -187,12 +187,12 @@ jobs: runs-on: [self-hosted, linux, x64, gpu] ``` -工作流程只能在一个所有标签处于 `runs-on` 数组中的运行器上运行。 作业将优先转到具有指定标签的空闲自托管运行器。 {% ifversion fpt or ghec %}If none are available and a {% data variables.product.prodname_dotcom %}-hosted runner with the specified labels exists, the job will go to a {% data variables.product.prodname_dotcom %}-hosted runner.{% endif %} +工作流程只能在一个所有标签处于 `runs-on` 数组中的运行器上运行。 作业将优先转到具有指定标签的空闲自托管运行器。 {% ifversion fpt or ghec %}如果没有可用且具有指定标签的 {% data variables.product.prodname_dotcom %} 托管运行器存在，作业将转到 {% data variables.product.prodname_dotcom %} 托管的运行器。{% endif %} -To learn more about self-hosted runner labels, see "[Using labels with self-hosted runners](/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners)." +要了解自托管运行器标签的更多信息，请参阅“[将标签与自托管运行器一起使用](/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners)”。 {% ifversion fpt or ghec %} -To learn more about {% data variables.product.prodname_dotcom %}-hosted runner labels, see "[Supported runners and hardware resources](/actions/using-github-hosted-runners/about-github-hosted-runners#supported-runners-and-hardware-resources)." +要详细了解 {% data variables.product.prodname_dotcom %} 托管的运行器标签，请参阅[“支持的运行器和硬件资源”](/actions/using-github-hosted-runners/about-github-hosted-runners#supported-runners-and-hardware-resources)。 {% endif %} {% ifversion fpt or ghes > 3.3 or ghae-issue-4757 or ghec %} @@ -202,4 +202,4 @@ To learn more about {% data variables.product.prodname_dotcom %}-hosted runner l ### 使用环境 -You can configure environments with protection rules and secrets to control the execution of jobs in a workflow. 工作流程中的每个作业都可以引用单个环境。 在将引用环境的作业发送到运行器之前，必须通过为环境配置的任何保护规则。 更多信息请参阅“[使用环境进行部署](/actions/deployment/using-environments-for-deployment)”。 +您可以使用保护规则和机密配置环境，以控制工作流程中作业的执行。 工作流程中的每个作业都可以引用单个环境。 在将引用环境的作业发送到运行器之前，必须通过为环境配置的任何保护规则。 更多信息请参阅“[使用环境进行部署](/actions/deployment/using-environments-for-deployment)”。 diff --git a/translations/zh-CN/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-minio-gateway-for-nas-storage.md b/translations/zh-CN/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-minio-gateway-for-nas-storage.md index 77caf14c10..514ab779d4 100644 --- a/translations/zh-CN/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-minio-gateway-for-nas-storage.md +++ b/translations/zh-CN/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-minio-gateway-for-nas-storage.md @@ -14,9 +14,14 @@ redirect_from: - /admin/github-actions/enabling-github-actions-with-minio-gateway-for-nas-storage shortTitle: MinIO Gateway for NAS storage --- -## Prerequisites -{% data reusables.actions.enterprise-s3-support-warning %} +{% warning %} + +**Warning**: MinIO has announced removal of MinIO Gateways. Starting June 1st, 2022, support and bug fixes for the current MinIO NAS Gateway implementation will only be available for paid customers via their LTS support contract. If you want to continue using MinIO Gateways with {% data variables.product.prodname_actions %}, we recommend moving to MinIO LTS support. For more information, see [Scheduled removal of MinIO Gateway for GCS, Azure, HDFS](https://github.com/minio/minio/issues/14331) in the minio/minio repository. + +{% endwarning %} + +## Prerequisites Before enabling {% data variables.product.prodname_actions %}, make sure you have completed the following steps: diff --git a/translations/zh-CN/content/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise.md b/translations/zh-CN/content/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise.md index b507720da4..b2dca564bc 100644 --- a/translations/zh-CN/content/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise.md +++ b/translations/zh-CN/content/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise.md @@ -48,7 +48,7 @@ Each action is a repository in the `actions` organization, and each action repos **Notes:** - When using setup actions (such as `actions/setup-LANGUAGE`) on {% data variables.product.product_name %} with self-hosted runners, you might need to set up the tools cache on runners that do not have internet access. For more information, see "[Setting up the tool cache on self-hosted runners without internet access](/enterprise/admin/github-actions/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access)." -- Upgrades to {% data variables.product.product_name %} will not result in the bundled actions being updated. +- Bundled actions are automatically updated when {% data variables.product.product_name %} is updated. {% endnote %} diff --git a/translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/exporting-audit-log-activity-for-your-enterprise.md b/translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/exporting-audit-log-activity-for-your-enterprise.md index cd2d65eab8..f8318d3f89 100644 --- a/translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/exporting-audit-log-activity-for-your-enterprise.md +++ b/translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/exporting-audit-log-activity-for-your-enterprise.md @@ -1,7 +1,7 @@ --- -title: Exporting audit log activity for your enterprise -intro: You can export audit and Git events data to a file for offline analysis. -shortTitle: Export audit logs +title: 导出企业的审核日志活动 +intro: 可以将审核和 Git 事件数据导出到文件以进行脱机分析。 +shortTitle: 导出审核日志 permissions: Enterprise owners can export the audit log. miniTocMaxHeadingLevel: 3 versions: @@ -13,38 +13,38 @@ topics: - Logging --- -## About exports of audit log and Git events data +## 关于审核日志和 Git 事件数据的导出 -You can export the audit log by downloading a JSON or CSV file from your enterprise on {% data variables.product.product_name %}. When you export audit log events, you can query by one or more of these supported qualifiers to filter for specific log events to export. For more information about search qualifiers, see "[Search based on the action performed](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/searching-the-audit-log-for-your-enterprise#search-based-on-the-action-performed)." +您可以通过在 {% data variables.product.product_name %} 上从企业下载 JSON 或 CSV 文件来导出审核日志。 导出审核日志事件时，可以按一个或多个受支持的限定符进行查询，以筛选要导出的特定日志事件。 有关搜索限定符的更多信息，请参阅“[根据执行的操作进行搜索](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/searching-the-audit-log-for-your-enterprise#search-based-on-the-action-performed)”。 -You can export Git events data by downloading a JSON file from your enterprise audit log. Unlike audit log data, you cannot query for specific Git events to filter and export in the audit log user interface. +可以通过从企业审核日志下载 JSON 文件来导出 Git 事件数据。 与审核日志数据不同，您无法在审核日志用户界面中查询要筛选和导出的特定 Git 事件。 {% data reusables.audit_log.exported-log-keys-and-values %} -As an alternative to exporting log events, you can use the API to retrieve audit log events, or set up {% data variables.product.product_name %} to stream audit data as events are logged. For more information, see "[Using the audit log API for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/using-the-audit-log-api-for-your-enterprise)" and "[Streaming the audit log for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise)." +作为导出日志事件的替代方法，您可以使用 API 检索审核日志事件，或设置 {% data variables.product.product_name %} 以在记录事件时流式传输审核数据。 更多信息请参阅“[对企业使用审核日志 API](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/using-the-audit-log-api-for-your-enterprise)”和“[流式传输企业的审核日志](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise)”。 -## Exporting audit log data +## 导出审核日志数据 {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.audit-log-tab %} -1. Optionally, to only export filtered results, search by one or more supported qualifiers or log filters. -2. Select the {% octicon "download" aria-label="The Download icon" %} **Export** dropdown menu, and choose the file format (JSON or CSV) to export log events in. +1. （可选）若要仅导出筛选的结果，请按一个或多个受支持的限定符或日志筛选器进行搜索。 +2. 选择 {% octicon "download" aria-label="The Download icon" %} **Export（导出）**下拉菜单，然后选择要将日志事件导出到的文件格式（JSON 或 CSV）。 ![导出按钮](/assets/images/help/organizations/org-audit-log-export.png) -## Exporting Git events data +## 导出 Git 事件数据 -You can also export Git events data by date range. +您还可以按日期范围导出 Git 事件数据。 {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.audit-log-tab %} -1. Select the {% octicon "download" aria-label="The Download icon" %} **Export Git Events** dropdown menu and choose a date range to export log events for. +1. 选择 {% octicon "download" aria-label="The Download icon" %} **Export Git Events（导出 Git 事件）**下拉菜单，然后选择要为其导出日志事件的日期范围。 - ![Export Git events button](/assets/images/help/organizations/org-audit-log-export-git-events.png) -1. Click {% octicon "file-zip" aria-label="The File-zip icon" %} **Download Results** to download the file. -1. The data is exported as a compressed JSON file. To extract the JSON data, uncompress the file using an archive utility client or command. 例如： + ![“导出 Git 事件”按钮](/assets/images/help/organizations/org-audit-log-export-git-events.png) +1. 单击 {% octicon "file-zip" aria-label="The File-zip icon" %} **Download Results（下载结果）**以下载文件。 +1. 数据将导出为压缩的 JSON 文件。 要提取 JSON 数据，请使用归档实用程序客户端或命令解压缩文件。 例如： ``` gunzip export-avocado-corp-1642896556.json.gz diff --git a/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests.md b/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests.md index 706a63f2da..b91352a273 100644 --- a/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests.md +++ b/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests.md @@ -99,4 +99,4 @@ topics: {% data reusables.code-scanning.false-positive-fix-codeql %} -For more information about dismissing alerts, see {% if delete-code-scanning-alerts %}"[Managing {% data variables.product.prodname_code_scanning %} alerts for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository#dismissing-or-deleting-alerts)."{% else %} "[Managing {% data variables.product.prodname_code_scanning %} alerts for your repository](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository#dismissing--alerts)."{% endif %} +有关消除警报的详细信息，请参阅 {% if delete-code-scanning-alerts %}“[管理存储库的 {% data variables.product.prodname_code_scanning %} 警报](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository#dismissing-or-deleting-alerts)”。{% else %} “[管理存储库的 {% data variables.product.prodname_code_scanning %} 警报](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository#dismissing--alerts)”。{% endif %} diff --git a/translations/zh-CN/content/codespaces/customizing-your-codespace/setting-your-timeout-period-for-codespaces.md b/translations/zh-CN/content/codespaces/customizing-your-codespace/setting-your-timeout-period-for-codespaces.md index 7f0ecd93fc..cd30442c20 100644 --- a/translations/zh-CN/content/codespaces/customizing-your-codespace/setting-your-timeout-period-for-codespaces.md +++ b/translations/zh-CN/content/codespaces/customizing-your-codespace/setting-your-timeout-period-for-codespaces.md @@ -12,6 +12,8 @@ shortTitle: 设置超时 代码空间将在一段时间不活动后停止运行。 您可以指定此超时期限的长度。 更新后的设置将应用于任何新创建的代码空间。 +Some organizations may have a maximum idle timeout policy. If an organization policy sets a maximum timeout which is less than the default timeout you have set, the organization's timeout will be used instead of your setting, and you will be notified of this after the codespace is created. For more information, see "[Restricting the idle timeout period](/codespaces/managing-codespaces-for-your-organization/restricting-the-idle-timeout-period)." + {% warning %} **警告**：代码空间按分钟计费。 如果您未主动使用代码空间，但代码空间尚未超时，则仍需为代码空间运行的时间付费。 更多信息请参阅“[关于代码空间的计费](/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces#codespaces-pricing)”。 diff --git a/translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/index.md b/translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/index.md index 35b017f6c8..c682023d96 100644 --- a/translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/index.md +++ b/translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/index.md @@ -15,6 +15,7 @@ children: - /reviewing-your-organizations-audit-logs-for-codespaces - /restricting-access-to-machine-types - /restricting-the-visibility-of-forwarded-ports + - /restricting-the-idle-timeout-period shortTitle: 管理组织 --- diff --git a/translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types.md b/translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types.md index 5cac049ef6..4408f9395b 100644 --- a/translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types.md +++ b/translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types.md @@ -1,9 +1,9 @@ --- title: 限制对计算机类型的访问 -shortTitle: 计算机类型访问 +shortTitle: Restrict machine types intro: 您可以对用户在组织中创建代码空间时可以选择的计算机类型设置约束。 product: '{% data reusables.gated-features.codespaces %}' -permissions: 'To manage access to machine types for the repositories in an organization, you must be an organization owner.' +permissions: 'To manage access to machine types for the repositories in an organization, you must be an owner of the organization.' versions: fpt: '*' ghec: '*' @@ -47,33 +47,22 @@ topics: {% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} -1. 在边栏的“Code, planning, and automation（代码、规划和自动化）”部分中，选择 **{% octicon "codespaces" aria-label="The codespaces icon" %}{% data variables.product.prodname_codespaces %}**，然后单击 **Policy（策略）**。 -2. 在“Codespace policies（代码空间策略）”页面上，单击 **Create Policy（创建策略）**。 -3. 输入新策略的名称。 -4. 单击 **Add constraint（添加约束）** ，然后选择 **Machine types（计算机类型）**。 +{% data reusables.codespaces.codespaces-org-policies %} +1. 单击 **Add constraint（添加约束）** ，然后选择 **Machine types（计算机类型）**。 ![为计算机类型添加约束](/assets/images/help/codespaces/add-constraint-dropdown.png) -5. 单击 {% octicon "pencil" aria-label="The edit icon" %} 以编辑约束，然后清除您不希望可用的任何计算机类型的选择。 +1. 单击 {% octicon "pencil" aria-label="The edit icon" %} 以编辑约束，然后清除您不希望可用的任何计算机类型的选择。 ![编辑计算机类型约束](/assets/images/help/codespaces/edit-machine-constraint.png) -6. 在“Change policy target（更改策略目标）”区域中，单击下拉按钮。 -7. 选择 **All repositories（所有存储库）** 或 **Selected repositories（选定的存储库）**，以确定此策略将应用于哪些存储库。 -8. 如果选择了 **Selected repositories（所选仓库）**： - 1. 单击 {% octicon "gear" aria-label="The settings icon" %}。 - - ![编辑策略的设置](/assets/images/help/codespaces/policy-edit.png) - - 2. 选择要应用此策略的存储库。 - 3. 在存储库列表的底部，单击 **Select repositories（选择存储库）**。 - - ![为此策略选择存储库](/assets/images/help/codespaces/policy-select-repos.png) - -9. 单击 **Save（保存）**。 - +{% data reusables.codespaces.codespaces-policy-targets %} +1. If you want to add another constraint to the policy, click **Add constraint** and choose another constraint. For information about other constraints, see "[Restricting the visibility of forwarded ports](/codespaces/managing-codespaces-for-your-organization/restricting-the-visibility-of-forwarded-ports)" and "[Restricting the idle timeout period](/codespaces/managing-codespaces-for-your-organization/restricting-the-idle-timeout-period)." +1. After you have finished adding constraints to your policy, click **Save**. ## 编辑策略 +You can edit an existing policy. For example, you may want to add or remove constraints to or from a policy. + 1. 显示“Codespace policies（代码空间策略）”页。 更多信息请参阅“[添加策略以限制可用计算机类型](#adding-a-policy-to-limit-the-available-machine-types)”。 1. 单击要编辑的策略的名称。 1. 进行所需的更改，然后单击 **Save（保存）**。 diff --git a/translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/restricting-the-idle-timeout-period.md b/translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/restricting-the-idle-timeout-period.md new file mode 100644 index 0000000000..0ead7424d6 --- /dev/null +++ b/translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/restricting-the-idle-timeout-period.md @@ -0,0 +1,79 @@ +--- +title: Restricting the idle timeout period +shortTitle: Restrict timeout periods +intro: You can set a maximum timeout period for any codespaces owned by your organization. +product: '{% data reusables.gated-features.codespaces %}' +permissions: 'To manage timeout constraints for an organization''s codespaces, you must be an owner of the organization.' +versions: + fpt: '*' + ghec: '*' +type: how_to +topics: + - Codespaces +--- + +## 概览 + +By default, codespaces time out after 30 minutes of inactivity. When a codespace times out it is stopped and will no longer incur charges for compute usage. + +The personal settings of a {% data variables.product.prodname_dotcom %} user allow them to define their own timeout period for codespaces they create. This may be longer than the default 30-minute period. For more information, see "[Setting your timeout period for Codespaces](/codespaces/customizing-your-codespace/setting-your-timeout-period-for-codespaces)." + +As an organization owner, you may want to configure constraints on the maximum idle timeout period for codespaces owned by your organization. This can help you limit costs associated with codespaces that are left to timeout after long periods of inactivity. You can set a maximum timeout for all codespaces owned by your organization, or for the codespaces of specific repositories. + +{% note %} + +**Note**: Maximum idle timeout constraints only apply to codespaces that are owned by your organization. + +{% endnote %} + +For more information about pricing for {% data variables.product.prodname_codespaces %} compute usage, see "[About billing for Codespaces](/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces#codespaces-pricing)." + +### Behavior when you set a maximum idle timeout constraint + +If someone sets the default idle timeout to 90 minutes in their personal settings and they then start a codespace for a repository with a maximum idle timeout constraint of 60 minutes, the codespace will time out after 60 minutes of inactivity. When codespace creation completes, a message explaining this will be displayed: + +> Idle timeout for this codespace is set to 60 minutes in compliance with your organization’s policy. + +### 设置组织范围和存储库特定的策略 + +When you create a policy, you choose whether it applies to all repositories in your organization, or only to specified repositories. If you create an organization-wide policy with a timeout constraint, then the timeout constraints in any policies that are targeted at specific repositories must fall within the restriction configured for the entire organization. The shortest timeout period - in an organization-wide policy, a policy targeted at specified repositories, or in someone's personal settings - is applied. + +If you add an organization-wide policy with a timeout constraint, you should set the timeout to the longest acceptable period. You can then add separate policies that set the maximum timeout to a shorter period for specific repositories in your organization. + +## Adding a policy to set a maximum idle timeout period + +{% data reusables.profile.access_org %} +{% data reusables.profile.org_settings %} +{% data reusables.codespaces.codespaces-org-policies %} +1. Click **Add constraint** and choose **Maximum idle timeout**. + + ![Add a constraint for idle timeout](/assets/images/help/codespaces/add-constraint-dropdown-timeout.png) + +1. Click {% octicon "pencil" aria-label="The edit icon" %} to edit the constraint. + + ![Edit the timeout constraint](/assets/images/help/codespaces/edit-timeout-constraint.png) + +1. Enter the maximum number of minutes codespaces can remain inactive before they time out, then click **Save**. + + ![选择端口可见性选项](/assets/images/help/codespaces/maximum-minutes-timeout.png) + +{% data reusables.codespaces.codespaces-policy-targets %} +1. If you want to add another constraint to the policy, click **Add constraint** and choose another constraint. For information about other constraints, see "[Restricting access to machine types](/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types)" and "[Restricting the visibility of forwarded ports](/codespaces/managing-codespaces-for-your-organization/restricting-the-visibility-of-forwarded-ports)." +1. After you have finished adding constraints to your policy, click **Save**. + +The policy will be applied to all new codespaces that are created, and to existing codespaces the next time they are started. + +## 编辑策略 + +You can edit an existing policy. For example, you may want to add or remove constraints to or from a policy. + +1. 显示“Codespace policies（代码空间策略）”页。 For more information, see "[Adding a policy to set a maximum idle timeout period](#adding-a-policy-to-set-a-maximum-idle-timeout-period)." +1. 单击要编辑的策略的名称。 +1. 进行所需的更改，然后单击 **Save（保存）**。 + +## 删除策略 + +1. 显示“Codespace policies（代码空间策略）”页。 For more information, see "[Adding a policy to set a maximum idle timeout period](#adding-a-policy-to-set-a-maximum-idle-timeout-period)." +1. 单击要删除的策略右侧的删除按钮。 + + ![策略的删除按钮](/assets/images/help/codespaces/policy-delete.png) diff --git a/translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/restricting-the-visibility-of-forwarded-ports.md b/translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/restricting-the-visibility-of-forwarded-ports.md index e7f154ad6a..c63ab405cc 100644 --- a/translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/restricting-the-visibility-of-forwarded-ports.md +++ b/translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/restricting-the-visibility-of-forwarded-ports.md @@ -1,9 +1,9 @@ --- title: 限制转发端口的可见性 -shortTitle: 限制端口可见性 +shortTitle: Restrict port visibility intro: 您可以对用户在从组织中的代码空间转发端口时可以选择的可见性选项设置约束。 product: '{% data reusables.gated-features.codespaces %}' -permissions: 'To manage access to port visibility constraints for the repositories in an organization, you must be an organization owner.' +permissions: 'To manage access to port visibility constraints for the repositories in an organization, you must be an owner of the organization.' versions: fpt: '*' ghec: '*' @@ -40,14 +40,12 @@ topics: {% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} -1. 在边栏的“Code, planning, and automation（代码、规划和自动化）”部分中，选择 **{% octicon "codespaces" aria-label="The codespaces icon" %}{% data variables.product.prodname_codespaces %}**，然后单击 **Policies（策略）**。 -1. 在“Codespace policies（代码空间策略）”页面上，单击 **Create Policy（创建策略）**。 -1. 输入新策略的名称。 +{% data reusables.codespaces.codespaces-org-policies %} 1. 单击 **Add constraint（添加约束）** ，然后选择 **Port visibility（端口可见性）**。 ![为端口可见性添加约束](/assets/images/help/codespaces/add-constraint-dropdown-ports.png) -1. 单击 {% octicon "pencil" aria-label="The edit icon" %} 编辑约束。 +1. Click {% octicon "pencil" aria-label="The edit icon" %} to edit the constraint. ![编辑端口可见性约束](/assets/images/help/codespaces/edit-port-visibility-constraint.png) @@ -55,22 +53,13 @@ topics: ![选择端口可见性选项](/assets/images/help/codespaces/choose-port-visibility-options.png) -1. 在“Change policy target（更改策略目标）”区域中，单击下拉按钮。 -1. 选择 **All repositories（所有存储库）** 或 **Selected repositories（选定的存储库）**，以确定此策略将应用于哪些存储库。 -1. 如果选择了 **Selected repositories（所选仓库）**： - 1. 单击 {% octicon "gear" aria-label="The settings icon" %}。 - - ![编辑策略的设置](/assets/images/help/codespaces/policy-edit.png) - - 2. 选择要应用此策略的存储库。 - 3. 在存储库列表的底部，单击 **Select repositories（选择存储库）**。 - - ![为此策略选择存储库](/assets/images/help/codespaces/policy-select-repos.png) - -1. 单击 **Save（保存）**。 - +{% data reusables.codespaces.codespaces-policy-targets %} +1. If you want to add another constraint to the policy, click **Add constraint** and choose another constraint. For information about other constraints, see "[Restricting access to machine types](/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types)" and "[Restricting the idle timeout period](/codespaces/managing-codespaces-for-your-organization/restricting-the-idle-timeout-period)." +1. After you have finished adding constraints to your policy, click **Save**. ## 编辑策略 +You can edit an existing policy. For example, you may want to add or remove constraints to or from a policy. + 1. 显示“Codespace policies（代码空间策略）”页。 更多信息请参阅“[添加策略以限制端口可见性选项](#adding-a-policy-to-limit-the-port-visibility-options)”。 1. 单击要编辑的策略的名称。 1. 进行所需的更改，然后单击 **Save（保存）**。 diff --git a/translations/zh-CN/content/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/committing-and-reviewing-changes-to-your-project.md b/translations/zh-CN/content/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/committing-and-reviewing-changes-to-your-project.md index bf36d4e7ae..de1c355e36 100644 --- a/translations/zh-CN/content/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/committing-and-reviewing-changes-to-your-project.md +++ b/translations/zh-CN/content/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/committing-and-reviewing-changes-to-your-project.md @@ -123,3 +123,11 @@ shortTitle: 提交和审核更改 ![受保护分支警告](/assets/images/help/desktop/protected-branch-warning.png) {% data reusables.desktop.push-origin %} + +6. If you have a pull request based off the branch you are working on, {% data variables.product.prodname_desktop %} will display the status of the checks that have run for the pull request. For more information about checks, see "[Viewing and re-running checks in GitHub Desktop](/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/viewing-and-re-running-checks-in-github-desktop)." + + ![Checks display next to branch name](/assets/images/help/desktop/checks-dialog.png) + + If a pull request has not been created for the current branch, {% data variables.product.prodname_desktop %} will give you the option to create one. For more information, see "[Creating an issue or pull request](/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/creating-an-issue-or-pull-request)." + + ![创建拉取请求](/assets/images/help/desktop/mac-create-pull-request.png) diff --git a/translations/zh-CN/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/configuring-notifications-in-github-desktop.md b/translations/zh-CN/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/configuring-notifications-in-github-desktop.md new file mode 100644 index 0000000000..bf122e88a8 --- /dev/null +++ b/translations/zh-CN/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/configuring-notifications-in-github-desktop.md @@ -0,0 +1,63 @@ +--- +title: Configuring notifications in GitHub Desktop +shortTitle: 配置通知 +intro: '{% data variables.product.prodname_desktop %} will keep you up-to-date with notifications about events that occur in your pull request branch.' +versions: + fpt: '*' +--- + +## About notifications in {% data variables.product.prodname_desktop %} + +{% data variables.product.prodname_desktop %} will show a system notification for events that occur in the currently selected repository. Notifications will be shown when: + +- Pull request checks have failed. +- A pull request review is left with a comment, approval, or requested changes. + +Clicking the notification will switch application focus to {% data variables.product.prodname_desktop %} and provide more detailed information. + +## Notifications about pull request check failures + +When changes are made to a pull request branch, you will receive a notification if the checks fail. + +![pull request checks failed notification](/assets/images/help/desktop/pull-request-checks-failed-notification.png) + +Clicking the notification will display a dialog with details about the checks. Once you've reviewed why the checks have failed, you can re-run the checks, or quickly switch to the pull request branch to get started on fixing the errors. For more information, see "[Viewing and re-running checks in GitHub Desktop](/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/viewing-and-re-running-checks-in-github-desktop)." + +![checks failed dialog](/assets/images/help/desktop/checks-failed-dialog.png) +## Notifications for pull request reviews + +{% data variables.product.prodname_desktop %} will surface a system notification when a teammate has approved, commented, or requested changes in your pull request. See "[About pull request reviews](/github/collaborating-with-issues-and-pull-requests/about-pull-request-reviews)" for more information on pull request reviews. + +![Pull request review notification](/assets/images/help/desktop/pull-request-review-notification.png) + +Clicking the notification will switch application focus to {% data variables.product.prodname_desktop %} and provide more context for the pull request review comment. + +![pull request review dialog](/assets/images/help/desktop/pull-request-review-dialog.png) +## Enabling notifications + +If system notifications are disabled for {% data variables.product.prodname_desktop %} you can follow the steps below to enable them. + +{% mac %} + +1. Click the **Apple** menu, then select **System Preferences**. +2. Select **Notifications & Focus**. +3. Select **{% data variables.product.prodname_desktop %}** from the list of applications. +4. Click **Allow Notifications**. + +![macOS Notifications & Focus](/assets/images/help/desktop/mac-enable-notifications.png) + +For more information about macOS system notifications, see "[Use notifications on your Mac](https://support.apple.com/en-us/HT204079)." + +{% endmac %} + +{% windows %} + +1. Open the **Start** menu, then select **Settings**. +2. Select **System**, then click **Notifications**. +3. Find **{% data variables.product.prodname_desktop %}** in the application list and click **On**. + +![Enable Windows Notifications](/assets/images/help/desktop/windows-enable-notifications.png) + +For more information about Windows system notifications, see "[Change notification settings in Windows](https://support.microsoft.com/en-us/windows/change-notification-settings-in-windows-8942c744-6198-fe56-4639-34320cf9444e)." + +{% endwindows %} diff --git a/translations/zh-CN/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/index.md b/translations/zh-CN/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/index.md index 31e883ecb2..84155ee5c7 100644 --- a/translations/zh-CN/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/index.md +++ b/translations/zh-CN/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/index.md @@ -8,6 +8,8 @@ versions: children: - /creating-an-issue-or-pull-request - /viewing-a-pull-request-in-github-desktop + - /viewing-and-re-running-checks-in-github-desktop + - /configuring-notifications-in-github-desktop - /changing-a-remotes-url-from-github-desktop shortTitle: 使用远程仓库 --- diff --git a/translations/zh-CN/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/viewing-a-pull-request-in-github-desktop.md b/translations/zh-CN/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/viewing-a-pull-request-in-github-desktop.md index 8df68191a4..cd6f7bb271 100644 --- a/translations/zh-CN/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/viewing-a-pull-request-in-github-desktop.md +++ b/translations/zh-CN/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/viewing-a-pull-request-in-github-desktop.md @@ -15,6 +15,8 @@ versions: 在 {% data variables.product.prodname_desktop %} 中查看拉取请求时，您可以看到贡献者的提交历史记录。 您还可以查看修改、添加或删除了提交的文件。 从 {% data variables.product.prodname_desktop %} 可以在首选文本编辑器中打开仓库以查看任何更改或进行其他更改。 在审查拉取请求中的更改后，您可以对 {% data variables.product.prodname_dotcom %} 提供反馈。 更多信息请参阅“[关于拉取请求审查](/github/collaborating-with-issues-and-pull-requests/about-pull-request-reviews)”。 +If checks have been enabled in your repository, {% data variables.product.prodname_desktop %} will show the status of the checks on the pull request and allow you to re-run checks. For more information, see "[Viewing and re-running checks in GitHub Desktop](/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/viewing-and-re-running-checks-in-github-desktop)." + ## 在 {% data variables.product.prodname_desktop %} 中查看拉取请求 {% data reusables.desktop.current-branch-menu %} {% data reusables.desktop.click-pull-requests %} diff --git a/translations/zh-CN/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/viewing-and-re-running-checks-in-github-desktop.md b/translations/zh-CN/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/viewing-and-re-running-checks-in-github-desktop.md new file mode 100644 index 0000000000..d022a660b2 --- /dev/null +++ b/translations/zh-CN/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/viewing-and-re-running-checks-in-github-desktop.md @@ -0,0 +1,25 @@ +--- +title: Viewing and re-running checks in GitHub Desktop +shortTitle: Viewing and re-running checks +intro: 'You can view the status of checks and re-run them in {% data variables.product.prodname_desktop %}.' +versions: + fpt: '*' +--- + +## About checks in {% data variables.product.prodname_desktop %} + +{% data variables.product.prodname_desktop %} displays the status of checks that have run in your pull request branches. The checks badge next to the branch name will display the *pending, passing,* or *failing* state of the checks. You can also re-run all, failed, or individual checks when viewing the status of the checks in {% data variables.product.prodname_desktop %}. For more information on setting up checks in your repository, see "[About status checks](/github/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks)." + +{% data variables.product.prodname_desktop %} will also show a system notification when checks fail. For more information on enabling notifications, see "[Configuring notifications in GitHub Desktop](/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/configuring-notifications-in-github-desktop)." + +## Viewing and re-running checks + +{% data reusables.desktop.current-branch-menu %} +{% data reusables.desktop.click-pull-requests %} + ![Current Branch（当前分支）下拉菜单中的 Pull Requests（拉取请求）选项卡](/assets/images/help/desktop/branch-drop-down-pull-request-tab.png) +{% data reusables.desktop.choose-pr-from-list %} + ![仓库中打开的拉取请求列表](/assets/images/help/desktop/click-pull-request.png) +4. Click on the pull request number, to the right of the pull request branch name. ![Checks display next to branch name](/assets/images/help/desktop/checks-dialog.png) +5. To re-run failed checks, click **{% octicon "sync" aria-label="The sync icon" %} Re-run** and select **Re-run Failed Checks**. ![Re-run failed checks](/assets/images/help/desktop/re-run-failed-checks.png) +6. To re-run individual checks, hover over the individual check you want to re-run and select the {% octicon "sync" aria-label="The sync icon" %} icon to re-run the check. ![Re-run individual checks](/assets/images/help/desktop/re-run-individual-checks.png) +7. You will see a confirmation dialog with the summary of the checks that will be re-run. Click **Re-run Checks** to confirm that you want to perform the re-run. ![Re-run confirmation dialog](/assets/images/help/desktop/re-run-confirmation-dialog.png) diff --git a/translations/zh-CN/content/developers/apps/building-oauth-apps/scopes-for-oauth-apps.md b/translations/zh-CN/content/developers/apps/building-oauth-apps/scopes-for-oauth-apps.md index bff87eeeb2..b6380c31a4 100644 --- a/translations/zh-CN/content/developers/apps/building-oauth-apps/scopes-for-oauth-apps.md +++ b/translations/zh-CN/content/developers/apps/building-oauth-apps/scopes-for-oauth-apps.md @@ -67,9 +67,9 @@ X-Accepted-OAuth-Scopes: user |  `user:follow` | 授予关注或取消关注其他用户的权限。 | | **`delete_repo`** | 授予删除可管理仓库的权限。 | | **`write:discussion`** | 授予对团队讨论的读取和写入权限。 | -|  `read:discussion` | 授予对团队讨论的读取权限。{% ifversion fpt or ghae or ghec %} +|  `read:discussion` | Allows read access for team discussions. | | **`write:packages`** | 授予在 {% data variables.product.prodname_registry %} 中上传或发布包的权限。 更多信息请参阅“[发布包](/github/managing-packages-with-github-packages/publishing-a-package)”。 | -| **`read:packages`** | 授予从 {% data variables.product.prodname_registry %} 下载或安装包的权限。 更多信息请参阅“[安装包](/github/managing-packages-with-github-packages/installing-a-package)”。 | +| **`read:packages`** | 授予从 {% data variables.product.prodname_registry %} 下载或安装包的权限。 For more information, see "[Installing a package](/github/managing-packages-with-github-packages/installing-a-package)".{% ifversion fpt or ghec or ghes > 3.1 or ghae %} | **`delete:packages`** | 授予从 {% data variables.product.prodname_registry %} 删除包的权限。 更多信息请参阅“[删除和恢复软件包](/packages/learn-github-packages/deleting-and-restoring-a-package)”。{% endif %} | **`admin:gpg_key`** | 全面管理 GPG 密钥。 | |  `write:gpg_key` | 创建、列出和查看 GPG 密钥的详细信息。 | diff --git a/translations/zh-CN/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md b/translations/zh-CN/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md index 5be52770de..8d2c487aa3 100644 --- a/translations/zh-CN/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md +++ b/translations/zh-CN/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md @@ -811,8 +811,6 @@ Web 挂钩事件是基于您注册的域的特异性而触发的。 例如，如 {% endif %} -{% ifversion fpt or ghae or ghec %} - ## package 与 {% data variables.product.prodname_registry %} 有关的活动。 {% data reusables.webhooks.action_type_desc %}更多信息请参阅“[使用 {% data variables.product.prodname_registry %} 管理包](/github/managing-packages-with-github-packages)”以详细了解 {% data variables.product.prodname_registry %}。 @@ -832,7 +830,6 @@ Web 挂钩事件是基于您注册的域的特异性而触发的。 例如，如 ### Web 挂钩有效负载示例 {{ webhookPayloadsForCurrentVersion.package.published }} -{% endif %} ## page_build diff --git a/translations/zh-CN/content/get-started/quickstart/be-social.md b/translations/zh-CN/content/get-started/quickstart/be-social.md index a2d74c8ca8..496c283694 100644 --- a/translations/zh-CN/content/get-started/quickstart/be-social.md +++ b/translations/zh-CN/content/get-started/quickstart/be-social.md @@ -5,7 +5,7 @@ redirect_from: - /articles/be-social - /github/getting-started-with-github/be-social - /github/getting-started-with-github/quickstart/be-social -intro: '您可以在 {% data variables.product.prodname_dotcom %} 上与人员、仓库及组织进行互动。 See what others are working on and who they are connecting with from your personal dashboard.' +intro: '您可以在 {% data variables.product.prodname_dotcom %} 上与人员、仓库及组织进行互动。 从您的个人仪表板查看其他人正在做什么，在跟谁联系。' permissions: '{% data reusables.enterprise-accounts.emu-permission-interact %}' versions: fpt: '*' @@ -24,17 +24,17 @@ topics: ## 关注他人 -When you follow someone on {% data variables.product.prodname_dotcom %}, you will get notifications on your personal dashboard about their public activity. If someone you follow creates a new repository, stars a repository, or follows another user, the activity will display in your dashboard. +在 {% data variables.product.prodname_dotcom %} 上关注某人后，您将会在您的个人仪表板中收到有关其公共活动的通知。 如果您关注的某人创建了一个新存储库、为存储库添加星标或关注其他用户，则该活动将显示在您的仪表板中。 在某人的个人资料页面上单击 **Follow（关注）**可关注他们。 ![关注用户按钮](/assets/images/help/profile/follow-user-button.png) -For more information, see "[Following people](/get-started/exploring-projects-on-github/following-people)." +更多信息请参阅“[关注人员](/get-started/exploring-projects-on-github/following-people)”。 ## 关注仓库 -You can subscribe to a repository to watch it and receive notifications for activity in it. When the owner updates the repository, you will see the changes in your personal dashboard. For more information, see "[Viewing your subscriptions](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions)." +您可以订阅存储库以关注它并接收其中活动的通知。 当所有者更新仓库时，您将在个人仪表板中看到其更改。 更多信息请参阅“[查看订阅](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions)”。 在仓库顶部单击 **Watch（关注）**可关注它。 @@ -46,28 +46,28 @@ You can subscribe to a repository to watch it and receive notifications for acti ## {% data variables.product.product_name %} 上的通信 -{% data variables.product.product_name %} provides built-in collaborative communication tools, allowing you to interact closely with your community when building great software. For example, you can contribute to another user's project by creating a pull request, or use issues to track bugs or suggest ideas in a repository. You can also brainstorm new ideas with your team with discussions. +{% data variables.product.product_name %} 提供内置的协作通信工具，让您在构建出色的软件时与社区密切互动。 例如，您可以通过创建拉取请求来为其他用户的项目做出贡献，或者使用议题来跟踪 Bug 或在存储库中提出想法。 您还可以通过讨论与您的团队一起集思广益。 -For an overview of these tools, see "[Quickstart for communicating on {% data variables.product.prodname_dotcom %}](/github/collaborating-with-issues-and-pull-requests/quickstart-for-communicating-on-github)." +有关这些工具的概述，请参阅“[{% data variables.product.prodname_dotcom %} 通信快速入门](/github/collaborating-with-issues-and-pull-requests/quickstart-for-communicating-on-github)”。 ## 参与组织 组织是共享帐户，其中业务和开源项目可一次协助处理多个项目。 所有者和管理员可建立具有特殊权限的团队、拥有公共组织资料以及跟踪组织内的活动。 更多信息请参阅“[关于组织](/articles/about-organizations/)”。 -From your dashboard, click the drop down menu of your username on the left side of your dashboard. Here, you can view organizations that you are a part of and easily switch between them. +在仪表板中，单击仪表板左侧用户名的下拉菜单。 在这里，您可以查看您所属的组织，并在它们之间轻松切换。 ![切换帐户上下文下拉列表](/assets/images/help/overview/dashboard-contextswitcher.png) ### 在 {% data variables.product.prodname_dotcom %} 上探索其他项目 -You can discover new and interesting projects on {% data variables.product.prodname_dotcom %}'s Explore page. You can star interesting projects to make them easy to find again later. Visit your stars page to see all your starred projects. For more information about stars, see "[Saving repositories with stars](/get-started/exploring-projects-on-github/saving-repositories-with-stars)." +您可以在 {% data variables.product.prodname_dotcom %} 的 Explore（探索）页面上发现新的和有趣的项目。 您可以为有趣的项目加注星标，以便以后再次轻松找到它们。 访问您的星标页面，查看所有已加星标的项目。 有关星标的更多信息，请参阅“[使用星标保存仓库](/get-started/exploring-projects-on-github/saving-repositories-with-stars)”。 -Your dashboard feed displays projects based on your interests including repositories you star, people you follow, and your contributions to public repositories. From your dashboard, you can see trending projects, view topics, and check out collections. +您的仪表板源会根据您的兴趣显示项目，包括您关注的存储库、您关注的人员以及您对公共存储库的贡献。 在仪表板中，您可以查看热门项目、查看主题和查看集合。 -To explore more projects, see "{% data variables.explore.explore_github %}". +要探索更多项目，请参阅“{% data variables.explore.explore_github %}”。 ## 后续步骤 -You are now connected to the {% data variables.product.product_name %} community. There are other ways to interact and build within {% data variables.product.product_name %}. +您现在已连接到 {% data variables.product.product_name %} 社区。 还有其他方法可以在 {% data variables.product.product_name %} 中进行交互和构建。 * {% data reusables.getting-started.set-up-git %} diff --git a/translations/zh-CN/content/get-started/quickstart/create-a-repo.md b/translations/zh-CN/content/get-started/quickstart/create-a-repo.md index 5b63548dc8..36c11ca399 100644 --- a/translations/zh-CN/content/get-started/quickstart/create-a-repo.md +++ b/translations/zh-CN/content/get-started/quickstart/create-a-repo.md @@ -5,7 +5,7 @@ redirect_from: - /articles/create-a-repo - /github/getting-started-with-github/create-a-repo - /github/getting-started-with-github/quickstart/create-a-repo -intro: 'To put your project up on {% data variables.product.prodname_dotcom %}, you will need to create a repository for it to live in.' +intro: '要将项目放在 {% data variables.product.prodname_dotcom %} 上，您需要创建一个仓库来存放它。' versions: fpt: '*' ghes: '*' @@ -22,7 +22,7 @@ topics: {% ifversion fpt or ghec %} -您可以在 {% data variables.product.prodname_dotcom %} 仓库中存储各种项目，包括开源项目。 With open source projects, you can share code to make better, more reliable software. 您可以使用仓库与他人协作并跟踪您的工作。 更多信息请参阅“[关于仓库](/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/about-repositories)”。 To learn more about open source projects, visit [OpenSource.org](http://opensource.org/about). +您可以在 {% data variables.product.prodname_dotcom %} 仓库中存储各种项目，包括开源项目。 通过开源项目，您可以共享代码以开发更好、更可靠的软件。 您可以使用仓库与他人协作并跟踪您的工作。 更多信息请参阅“[关于仓库](/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/about-repositories)”。 要了解有关开源项目的更多信息，请访问 [OpenSource.org](http://opensource.org/about)。 {% elsif ghes or ghae %} @@ -78,7 +78,7 @@ A *[提交](/articles/github-glossary#commit)*就像是项目中所有文件在 2. 在文件内容的上方，单击 {% octicon "pencil" aria-label="The edit icon" %}。 3. 在 **Edit file（编辑文件）**选项卡上，键入一些关于您自己的信息。 ![文件中的新内容](/assets/images/help/repository/edit-readme-light.png) {% data reusables.files.preview_change %} -5. 查看您对文件所做的更改。 You will see the new content in green. ![文件预览视图](/assets/images/help/repository/create-commit-review.png) +5. 查看您对文件所做的更改。 您将看到绿色的新内容。 ![文件预览视图](/assets/images/help/repository/create-commit-review.png) {% data reusables.files.write_commit_message %} {% data reusables.files.choose_commit_branch %} {% data reusables.files.propose_file_change %} diff --git a/translations/zh-CN/content/get-started/quickstart/fork-a-repo.md b/translations/zh-CN/content/get-started/quickstart/fork-a-repo.md index 2985fa71bd..ef0e6f3013 100644 --- a/translations/zh-CN/content/get-started/quickstart/fork-a-repo.md +++ b/translations/zh-CN/content/get-started/quickstart/fork-a-repo.md @@ -22,11 +22,11 @@ topics: ## 关于复刻 -Most commonly, forks are used to either propose changes to someone else's project to which you do not have write access, or to use someone else's project as a starting point for your own idea. 您可以复刻仓库以创建仓库的副本，并在不影响上游仓库的情况下进行更改。 更多信息请参阅“[使用复刻](/github/collaborating-with-issues-and-pull-requests/working-with-forks)”。 +最常见的是，复刻用于对其他人的项目提出您没有写入权限的项目的更改，或者使用其他人的项目作为您自己想法的起点。 您可以复刻仓库以创建仓库的副本，并在不影响上游仓库的情况下进行更改。 更多信息请参阅“[使用复刻](/github/collaborating-with-issues-and-pull-requests/working-with-forks)”。 ### 对其他人的项目提出更改 -例如，可以使用复刻提出与修复 Bug 相关的更改。 Rather than logging an issue for a bug you have found, you can: +例如，可以使用复刻提出与修复 Bug 相关的更改。 无需为您发现的漏洞创建议题，您可以： - 复刻仓库 - 进行修复 @@ -48,7 +48,7 @@ Most commonly, forks are used to either propose changes to someone else's projec ## 基本要求 -If you have not yet, you should first [set up Git](/articles/set-up-git). 不要忘记[从 Git 设置向 {% data variables.product.product_location %} 验证](/articles/set-up-git#next-steps-authenticating-with-github-from-git)。 +如果尚未[设置 Git](/articles/set-up-git)，您应该先设置它。 不要忘记[从 Git 设置向 {% data variables.product.product_location %} 验证](/articles/set-up-git#next-steps-authenticating-with-github-from-git)。 ## 复刻仓库 @@ -84,7 +84,7 @@ gh repo fork repository --org "octo-org" ## 克隆复刻的仓库 -Right now, you have a fork of the Spoon-Knife repository, but you do not have the files in that repository locally on your computer. +现在，您有了 Spoon-Knife 仓库的复刻，但您的计算机本地还没有该仓库中的文件。 {% webui %} @@ -145,7 +145,7 @@ gh repo fork repository --clone=true - 要列出当前目录中的文件和文件夹，请键入 `ls`。 - 要进入列出的某个目录，请键入 `cd your_listed_directory`。 - 要回到上一个目录，请键入 `cd ..`。 -5. 键入 `git remote -v`，然后按 **Enter** 键。 You will see the current configured remote repository for your fork. +5. 键入 `git remote -v`，然后按 **Enter** 键。 您将看到当前为复刻配置的远程仓库。 ```shell $ git remote -v > origin https://{% data variables.command_line.codeblock %}/YOUR_USERNAME/YOUR_FORK.git (fetch) @@ -157,7 +157,7 @@ gh repo fork repository --clone=true $ git remote add upstream https://{% data variables.command_line.codeblock %}/octocat/Spoon-Knife.git ``` -7. To verify the new upstream repository you have specified for your fork, type `git remote -v` again. 您应该看到复刻的 URL 为 `origin`，原始仓库的 URL 为 `upstream`。 +7. 要验证为复刻指定的新上游仓库，请再次键入 `git remote -v`。 您应该看到复刻的 URL 为 `origin`，原始仓库的 URL 为 `upstream`。 ```shell $ git remote -v > origin https://{% data variables.command_line.codeblock %}/YOUR_USERNAME/YOUR_FORK.git (fetch) @@ -188,7 +188,7 @@ gh repo fork repository --remote-name "main-remote-repo" {% endcli %} -### Editing a fork +### 编辑复刻 您可以对复刻进行任何更改，包括： @@ -206,10 +206,10 @@ gh repo fork repository --remote-name "main-remote-repo" 您现在已经复刻了仓库、练习了克隆复刻并配置了上游仓库。 -* For more information about cloning the fork and syncing the changes in a forked repository from your computer, see "[Set up Git](/articles/set-up-git)." +* 有关克隆复刻和从计算机同步复刻仓库更改的更多信息，请参阅“[设置 Git](/articles/set-up-git)”。 * 您也可以创建一个新的仓库，以将所有项目放在 {% data variables.product.prodname_dotcom %} 上并共享代码。 {% data reusables.getting-started.create-a-repository %}" -* {% data variables.product.product_name %} 中的每个仓库均归个人或组织所有。 You can interact with users, repositories, and organizations by connecting and following them on {% data variables.product.product_name %}. {% data reusables.getting-started.being-social %} +* {% data variables.product.product_name %} 中的每个仓库均归个人或组织所有。 您可以在 {% data variables.product.product_name %} 上连接和关注用户、仓库和组织以与之进行交互。 {% data reusables.getting-started.being-social %} * {% data reusables.support.connect-in-the-forum-bootcamp %} diff --git a/translations/zh-CN/content/get-started/quickstart/github-glossary.md b/translations/zh-CN/content/get-started/quickstart/github-glossary.md index 92b0c4905f..ce157b72ae 100644 --- a/translations/zh-CN/content/get-started/quickstart/github-glossary.md +++ b/translations/zh-CN/content/get-started/quickstart/github-glossary.md @@ -23,5 +23,5 @@ versions: ## 延伸阅读 - [官方 Git 术语表](https://www.kernel.org/pub/software/scm/git/docs/gitglossary.html) -- [Git documentation](https://git-scm.com/doc) -- [Git command list](https://git-scm.com/docs) +- [Git 文档](https://git-scm.com/doc) +- [Git 命令列表](https://git-scm.com/docs) diff --git a/translations/zh-CN/content/packages/learn-github-packages/introduction-to-github-packages.md b/translations/zh-CN/content/packages/learn-github-packages/introduction-to-github-packages.md index 1ffeed2655..f4716e5ca3 100644 --- a/translations/zh-CN/content/packages/learn-github-packages/introduction-to-github-packages.md +++ b/translations/zh-CN/content/packages/learn-github-packages/introduction-to-github-packages.md @@ -23,7 +23,7 @@ shortTitle: Introduction ## About {% data variables.product.prodname_registry %} -{% data variables.product.prodname_registry %} is a platform for hosting and managing packages, including containers and other dependencies. {% data variables.product.prodname_registry %} combines your source code and packages in one place to provide integrated permissions management{% ifversion not ghae %} and billing{% endif %}, so you can centralize your software development on {% data variables.product.product_name %}. +{% data variables.product.prodname_registry %} is a platform for hosting and managing packages, including containers and other dependencies. {% data variables.product.prodname_registry %} combines your source code and packages in one place to provide integrated permissions management{% ifversion fpt or ghec %} and billing{% endif %}, so you can centralize your software development on {% data variables.product.product_name %}. You can integrate {% data variables.product.prodname_registry %} with {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} APIs, {% data variables.product.prodname_actions %}, and webhooks to create an end-to-end DevOps workflow that includes your code, CI, and deployment solutions. diff --git a/translations/zh-CN/content/packages/quickstart.md b/translations/zh-CN/content/packages/quickstart.md index f0cf7373f2..74558266b7 100644 --- a/translations/zh-CN/content/packages/quickstart.md +++ b/translations/zh-CN/content/packages/quickstart.md @@ -21,7 +21,7 @@ In this guide, you'll create a {% data variables.product.prodname_actions %} wor 1. Create a new repository on {% data variables.product.prodname_dotcom %}, adding the `.gitignore` for Node. For more information, see "[Creating a new repository](/github/creating-cloning-and-archiving-repositories/creating-a-new-repository)." 2. Clone the repository to your local machine. ```shell - $ git clone https://{% ifversion ghae %}YOUR-HOSTNAME{% else %}github.com{% endif %}/YOUR-USERNAME/YOUR-REPOSITORY.git + $ git clone https://{% ifversion ghes or ghae %}YOUR-HOSTNAME{% else %}github.com{% endif %}/YOUR-USERNAME/YOUR-REPOSITORY.git $ cd YOUR-REPOSITORY ``` 3. Create an `index.js` file and add a basic alert to say "Hello world!" @@ -49,7 +49,7 @@ In this guide, you'll create a {% data variables.product.prodname_actions %} wor $ git push ``` 6. Create a `.github/workflows` directory. In that directory, create a file named `release-package.yml`. -7. Copy the following YAML content into the `release-package.yml` file{% ifversion ghae %}, replacing `YOUR-HOSTNAME` with the name of your enterprise{% endif %}. +7. Copy the following YAML content into the `release-package.yml` file{% ifversion ghes or ghae %}, replacing `YOUR-HOSTNAME` with the name of your enterprise{% endif %}. ```yaml{:copy} name: Node.js Package @@ -79,7 +79,7 @@ In this guide, you'll create a {% data variables.product.prodname_actions %} wor - uses: {% data reusables.actions.action-setup-node %} with: node-version: 12 - registry-url: {% ifversion ghae %}https://npm.YOUR-HOSTNAME.com/{% else %}https://npm.pkg.github.com/{% endif %} + registry-url: {% ifversion ghes or ghae %}https://npm.YOUR-HOSTNAME.com/{% else %}https://npm.pkg.github.com/{% endif %} - run: npm ci - run: npm publish env: diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-4/1.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-4/1.yml index 542ec1716f..9e2abde51d 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-4/1.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/3-4/1.yml @@ -47,7 +47,6 @@ sections: - When "Users can search GitHub.com" is enabled with {% data variables.product.prodname_github_connect %}, issues in private and internal repositories are not included in {% data variables.product.prodname_dotcom_the_website %} search results. - '{% data variables.product.prodname_registry %} npm 注册表不再返回元数据响应的时间值。这样做是为了大幅改善性能。作为元数据响应的一部分，我们继续拥有返回时间值所需的所有数据，并将在我们解决现有性能问题后恢复返回这个值。' - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail. - - Actions services need to be restarted after restoring appliance from backup taken on a different host. - | When using SAML encrypted assertions with {% data variables.product.prodname_ghe_server %} 3.4.0 and 3.4.1, a new XML attribute `WantAssertionsEncrypted` in the `SPSSODescriptor` contains an invalid attribute for SAML metadata. IdPs that consume this SAML metadata endpoint may encounter errors when validating the SAML metadata XML schema. A fix will be available in the next patch release. [Updated: 2022-04-11] diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-4/2.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-4/2.yml index d548034cac..0f28e72b91 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-4/2.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/3-4/2.yml @@ -32,7 +32,6 @@ sections: - When "Users can search GitHub.com" is enabled with {% data variables.product.prodname_github_connect %}, issues in private and internal repositories are not included in {% data variables.product.prodname_dotcom_the_website %} search results. - '{% data variables.product.prodname_registry %} npm 注册表不再返回元数据响应的时间值。这样做是为了大幅改善性能。作为元数据响应的一部分，我们继续拥有返回时间值所需的所有数据，并将在我们解决现有性能问题后恢复返回这个值。' - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail. - - Actions services need to be restarted after restoring appliance from backup taken on a different host. - | When using SAML encrypted assertions with {% data variables.product.prodname_ghe_server %} 3.4.0 and 3.4.1, a new XML attribute `WantAssertionsEncrypted` in the `SPSSODescriptor` contains an invalid attribute for SAML metadata. IdPs that consume this SAML metadata endpoint may encounter errors when validating the SAML metadata XML schema. A fix will be available in the next patch release. [Updated: 2022-04-11] diff --git a/translations/zh-CN/data/reusables/actions/supported-github-runners.md b/translations/zh-CN/data/reusables/actions/supported-github-runners.md index 437f235fcb..6382a882d0 100644 --- a/translations/zh-CN/data/reusables/actions/supported-github-runners.md +++ b/translations/zh-CN/data/reusables/actions/supported-github-runners.md @@ -50,6 +50,17 @@ Ubuntu 18.04 +macOS Monterey 12 + + +macos-12 + + +macOS 12 is currently in public beta. + + + + macOS Big Sur 11 diff --git a/translations/zh-CN/data/reusables/codespaces/codespaces-org-policies.md b/translations/zh-CN/data/reusables/codespaces/codespaces-org-policies.md new file mode 100644 index 0000000000..4efd0161d9 --- /dev/null +++ b/translations/zh-CN/data/reusables/codespaces/codespaces-org-policies.md @@ -0,0 +1,3 @@ +1. 在边栏的“Code, planning, and automation（代码、规划和自动化）”部分中，选择 **{% octicon "codespaces" aria-label="The codespaces icon" %}{% data variables.product.prodname_codespaces %}**，然后单击 **Policies（策略）**。 +1. 在“Codespace policies（代码空间策略）”页面上，单击 **Create Policy（创建策略）**。 +1. 输入新策略的名称。 \ No newline at end of file diff --git a/translations/zh-CN/data/reusables/codespaces/codespaces-policy-targets.md b/translations/zh-CN/data/reusables/codespaces/codespaces-policy-targets.md new file mode 100644 index 0000000000..0b3e4855b8 --- /dev/null +++ b/translations/zh-CN/data/reusables/codespaces/codespaces-policy-targets.md @@ -0,0 +1,11 @@ +1. 在“Change policy target（更改策略目标）”区域中，单击下拉按钮。 +1. 选择 **All repositories（所有存储库）** 或 **Selected repositories（选定的存储库）**，以确定此策略将应用于哪些存储库。 +1. 如果选择了 **Selected repositories（所选仓库）**： + 1. 单击 {% octicon "gear" aria-label="The settings icon" %}。 + + ![编辑策略的设置](/assets/images/help/codespaces/policy-edit.png) + + 2. 选择要应用此策略的存储库。 + 3. 在存储库列表的底部，单击 **Select repositories（选择存储库）**。 + + ![为此策略选择存储库](/assets/images/help/codespaces/policy-select-repos.png) diff --git a/translations/zh-CN/data/reusables/projects/enable-basic-workflow.md b/translations/zh-CN/data/reusables/projects/enable-basic-workflow.md index fa23f9b50d..92bb137381 100644 --- a/translations/zh-CN/data/reusables/projects/enable-basic-workflow.md +++ b/translations/zh-CN/data/reusables/projects/enable-basic-workflow.md @@ -1,4 +1,6 @@ -1. In your project, click {% octicon "workflow" aria-label="the workflow icon" %}. +1. Navigate to your project. +1. In the top-right, click {% octicon "kebab-horizontal" aria-label="The menu icon" %} to open the menu. +1. In the menu, click {% octicon "workflow" aria-label="The workflow icon" %} **Workflows**. 1. Under **Default workflows**, click on the workflow that you want to edit. 1. If the workflow can apply to both issues and pull requests, next to **When**, check the item type(s) that you want to act on. 1. Next to **Set**, choose the value that you want to set the status to. diff --git a/translations/zh-CN/data/reusables/projects/project-settings.md b/translations/zh-CN/data/reusables/projects/project-settings.md index bee73a5c66..4c244857b3 100644 --- a/translations/zh-CN/data/reusables/projects/project-settings.md +++ b/translations/zh-CN/data/reusables/projects/project-settings.md @@ -1,2 +1,3 @@ 1. Navigate to your project. -1. Click {% octicon "gear" aria-label="the gear icon" %} to access the project settings. +1. In the top-right, click {% octicon "kebab-horizontal" aria-label="The menu icon" %} to open the menu. +1. In the menu, click {% octicon "gear" aria-label="The gear icon" %} **Settings** to access the project settings.