diff --git a/.github/workflows/check-all-english-links.yml b/.github/workflows/check-all-english-links.yml index 75294e403d..baae8c5bd6 100644 --- a/.github/workflows/check-all-english-links.yml +++ b/.github/workflows/check-all-english-links.yml @@ -17,7 +17,7 @@ jobs: check_all_english_links: name: Check all links if: github.repository == 'github/docs-internal' - runs-on: ${{ fromJSON('["ubuntu-latest", "self-hosted"]')[github.repository == 'github/docs-internal'] }} + runs-on: self-hosted env: GITHUB_TOKEN: ${{ secrets.DOCUBOT_READORG_REPO_WORKFLOW_SCOPES }} FIRST_RESPONDER_PROJECT: Docs content first responder @@ -56,9 +56,8 @@ jobs: # The default is 10s. But because this runs overnight, we can # be a lot more patient. REQUEST_TIMEOUT: 20000 - # The default is 300 which works OK on a fast macbook pro - # but so well in Actions. - LINKINATOR_CONCURRENCY: 100 + # Don't care about CDN caching image URLs + DISABLE_REWRITE_ASSET_URLS: true run: | node server.mjs > /tmp/stdout.log 2> /tmp/stderr.log & sleep 5 @@ -73,6 +72,10 @@ jobs: cat /tmp/stderr.log - name: Run script + env: + # The default is 300 which works OK on a fast macbook pro + # but not so well in Actions. + LINKINATOR_CONCURRENCY: 100 run: | script/check-english-links.js > broken_links.md @@ -84,11 +87,6 @@ jobs: # # https://docs.github.com/actions/reference/context-and-expression-syntax-for-github-actions#job-status-check-functions - - if: ${{ failure() }} - name: Debug broken_links.md - run: | - ls -lh broken_links.md - wc -l broken_links.md - uses: actions/upload-artifact@6673cd052c4cd6fcf4b4e6e60ea986c889389535 if: ${{ failure() }} with: diff --git a/.github/workflows/link-check-all.yml b/.github/workflows/link-check-all.yml index c8fa5c9075..8cbdac109d 100644 --- a/.github/workflows/link-check-all.yml +++ b/.github/workflows/link-check-all.yml @@ -49,6 +49,9 @@ jobs: run: cat $HOME/files.json - name: Link check (warnings, changed files) + env: + # Don't care about CDN caching image URLs + DISABLE_REWRITE_ASSET_URLS: true run: | ./script/rendered-content-link-checker.mjs \ --language en \ @@ -59,6 +62,9 @@ jobs: --list $HOME/files.json - name: Link check (critical, all files) + env: + # Don't care about CDN caching image URLs + DISABLE_REWRITE_ASSET_URLS: true run: | ./script/rendered-content-link-checker.mjs \ --language en \ diff --git a/assets/images/help/graphs/click-alert-in-alerts-list-ungrouped.png b/assets/images/enterprise/3.5/dependabot/click-alert-in-alerts-list-ungrouped.png similarity index 100% rename from assets/images/help/graphs/click-alert-in-alerts-list-ungrouped.png rename to assets/images/enterprise/3.5/dependabot/click-alert-in-alerts-list-ungrouped.png diff --git a/assets/images/help/graphs/dependabot-alerts-filters.png b/assets/images/enterprise/3.5/dependabot/dependabot-alerts-filters.png similarity index 100% rename from assets/images/help/graphs/dependabot-alerts-filters.png rename to assets/images/enterprise/3.5/dependabot/dependabot-alerts-filters.png diff --git a/assets/images/help/classroom/classroom-reuse-assignment-modal.png b/assets/images/help/classroom/classroom-reuse-assignment-modal.png new file mode 100644 index 0000000000..bbb1a214ec Binary files /dev/null and b/assets/images/help/classroom/classroom-reuse-assignment-modal.png differ diff --git a/assets/images/help/classroom/multiple-assignments-selected.png b/assets/images/help/classroom/multiple-assignments-selected.png new file mode 100644 index 0000000000..a7f39b572e Binary files /dev/null and b/assets/images/help/classroom/multiple-assignments-selected.png differ diff --git a/assets/images/help/classroom/reuse-multiple-assignments-modal.png b/assets/images/help/classroom/reuse-multiple-assignments-modal.png new file mode 100644 index 0000000000..3c1cd1e851 Binary files /dev/null and b/assets/images/help/classroom/reuse-multiple-assignments-modal.png differ diff --git a/assets/images/help/graphs/click-alert-in-alerts-list-checkbox.png b/assets/images/help/graphs/click-alert-in-alerts-list-checkbox.png new file mode 100644 index 0000000000..ea7b5dfe56 Binary files /dev/null and b/assets/images/help/graphs/click-alert-in-alerts-list-checkbox.png differ diff --git a/assets/images/help/graphs/dependabot-alerts-filters-checkbox.png b/assets/images/help/graphs/dependabot-alerts-filters-checkbox.png new file mode 100644 index 0000000000..64b0c87bba Binary files /dev/null and b/assets/images/help/graphs/dependabot-alerts-filters-checkbox.png differ diff --git a/assets/images/help/graphs/dismiss-multiple-alerts.png b/assets/images/help/graphs/dismiss-multiple-alerts.png new file mode 100644 index 0000000000..fac5924a48 Binary files /dev/null and b/assets/images/help/graphs/dismiss-multiple-alerts.png differ diff --git a/assets/images/help/graphs/reopen-multiple-alerts.png b/assets/images/help/graphs/reopen-multiple-alerts.png new file mode 100644 index 0000000000..f6ee4da291 Binary files /dev/null and b/assets/images/help/graphs/reopen-multiple-alerts.png differ diff --git a/assets/images/help/graphs/select-all-alerts.png b/assets/images/help/graphs/select-all-alerts.png new file mode 100644 index 0000000000..2998fbd531 Binary files /dev/null and b/assets/images/help/graphs/select-all-alerts.png differ diff --git a/assets/images/help/graphs/select-all-closed-alerts.png b/assets/images/help/graphs/select-all-closed-alerts.png new file mode 100644 index 0000000000..bc39035d0c Binary files /dev/null and b/assets/images/help/graphs/select-all-closed-alerts.png differ diff --git a/assets/images/help/graphs/select-multiple-alerts.png b/assets/images/help/graphs/select-multiple-alerts.png new file mode 100644 index 0000000000..d362434743 Binary files /dev/null and b/assets/images/help/graphs/select-multiple-alerts.png differ diff --git a/assets/images/help/repository/dependabot-alerts-closed-checkbox.png b/assets/images/help/repository/dependabot-alerts-closed-checkbox.png new file mode 100644 index 0000000000..09553e4318 Binary files /dev/null and b/assets/images/help/repository/dependabot-alerts-closed-checkbox.png differ diff --git a/assets/images/help/repository/dependabot-alerts-open-checkbox.png b/assets/images/help/repository/dependabot-alerts-open-checkbox.png new file mode 100644 index 0000000000..4a8b314e87 Binary files /dev/null and b/assets/images/help/repository/dependabot-alerts-open-checkbox.png differ diff --git a/assets/images/help/repository/dependabot-alerts-select-closed-alert-checkbox.png b/assets/images/help/repository/dependabot-alerts-select-closed-alert-checkbox.png new file mode 100644 index 0000000000..5402e08629 Binary files /dev/null and b/assets/images/help/repository/dependabot-alerts-select-closed-alert-checkbox.png differ diff --git a/assets/images/help/repository/reopen-dismissed-alert.png b/assets/images/help/repository/reopen-dismissed-alert.png index 07a1cd9495..22da2719c4 100644 Binary files a/assets/images/help/repository/reopen-dismissed-alert.png and b/assets/images/help/repository/reopen-dismissed-alert.png differ diff --git a/components/rest/ParameterRow.tsx b/components/rest/ParameterRow.tsx index 6cd63c1faa..7088d9d927 100644 --- a/components/rest/ParameterRow.tsx +++ b/components/rest/ParameterRow.tsx @@ -55,7 +55,7 @@ export function ParameterRow({ )}
- {defaultValue && ( + {defaultValue !== undefined && (

{t('rest.reference.default')}: {defaultValue.toString()} diff --git a/content/actions/learn-github-actions/contexts.md b/content/actions/learn-github-actions/contexts.md index fbfb1b80c7..38680b5982 100644 --- a/content/actions/learn-github-actions/contexts.md +++ b/content/actions/learn-github-actions/contexts.md @@ -193,7 +193,7 @@ The `github` context contains information about the workflow run and the event t | `github.graphql_url` | `string` | The URL of the {% data variables.product.prodname_dotcom %} GraphQL API. | | `github.head_ref` | `string` | The `head_ref` or source branch of the pull request in a workflow run. This property is only available when the event that triggers a workflow run is either `pull_request` or `pull_request_target`. | | `github.job` | `string` | The [`job_id`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_id) of the current job.
Note: This context property is set by the Actions runner, and is only available within the execution `steps` of a job. Otherwise, the value of this property will be `null`. | -| `github.ref` | `string` | The branch or tag ref that triggered the workflow run. For branches this is the format `refs/heads/`, and for tags it is `refs/tags/`. | +| `github.ref` | `string` | {% data reusables.actions.ref-description %} | {%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5338 %} | `github.ref_name` | `string` | {% data reusables.actions.ref_name-description %} | | `github.ref_protected` | `string` | {% data reusables.actions.ref_protected-description %} | diff --git a/content/actions/learn-github-actions/environment-variables.md b/content/actions/learn-github-actions/environment-variables.md index 413200337a..d583c01805 100644 --- a/content/actions/learn-github-actions/environment-variables.md +++ b/content/actions/learn-github-actions/environment-variables.md @@ -143,7 +143,7 @@ We strongly recommend that actions use environment variables to access the files | `GITHUB_HEAD_REF` | The head ref or source branch of the pull request in a workflow run. This property is only set when the event that triggers a workflow run is either `pull_request` or `pull_request_target`. For example, `feature-branch-1`. | | `GITHUB_JOB` | The [job_id](/actions/reference/workflow-syntax-for-github-actions#jobsjob_id) of the current job. For example, `greeting_job`. | | `GITHUB_PATH` | The path on the runner to the file that sets system `PATH` variables from workflow commands. This file is unique to the current step and changes for each step in a job. For example, `/home/runner/work/_temp/_runner_file_commands/add_path_899b9445-ad4a-400c-aa89-249f18632cf5`. For more information, see "[Workflow commands for {% data variables.product.prodname_actions %}](/actions/using-workflows/workflow-commands-for-github-actions#adding-a-system-path)." | -| `GITHUB_REF` | The branch or tag ref that triggered the workflow run. For branches this is the format `refs/heads/`, for tags it is `refs/tags/`, and for pull requests it is `refs/pull//merge`. This variable is only set if a branch or tag is available for the event type. For example, `refs/heads/feature-branch-1`. | +| `GITHUB_REF` | {% data reusables.actions.ref-description %} | {%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5338 %} | `GITHUB_REF_NAME` | {% data reusables.actions.ref_name-description %} For example, `feature-branch-1`.| | `GITHUB_REF_PROTECTED` | {% data reusables.actions.ref_protected-description %} | diff --git a/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/enabling-the-dependency-graph-for-your-enterprise.md b/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/enabling-the-dependency-graph-for-your-enterprise.md index 2a7654c146..fb5faac0de 100644 --- a/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/enabling-the-dependency-graph-for-your-enterprise.md +++ b/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/enabling-the-dependency-graph-for-your-enterprise.md @@ -50,7 +50,7 @@ If your {% data variables.product.product_location %} uses clustering, you canno ```{% endif %} {% note %} - **Note**: For more information about enabling access to the administrative shell via SSH, see "[Accessing the administrative shell (SSH)](/enterprise/{{ currentVersion }}/admin/configuration/accessing-the-administrative-shell-ssh)." + **Note**: For more information about enabling access to the administrative shell via SSH, see "[Accessing the administrative shell (SSH)](/enterprise/admin/configuration/accessing-the-administrative-shell-ssh)." {% endnote %} 2. Apply the configuration. diff --git a/content/admin/configuration/configuring-github-connect/managing-github-connect.md b/content/admin/configuration/configuring-github-connect/managing-github-connect.md index 6989f4d264..b3559ba542 100644 --- a/content/admin/configuration/configuring-github-connect/managing-github-connect.md +++ b/content/admin/configuration/configuring-github-connect/managing-github-connect.md @@ -43,7 +43,7 @@ To use {% data variables.product.prodname_github_connect %}, you must have an or {% ifversion ghes %} If your organization or enterprise account on {% data variables.product.prodname_dotcom_the_website %} uses IP allow lists, you must add the IP address or network for {% data variables.product.product_location %} to your IP allow list on {% data variables.product.prodname_dotcom_the_website %}. For more information, see "[Managing allowed IP addresses for your organization](/enterprise-cloud@latest/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-allowed-ip-addresses-for-your-organization)" and "[Enforcing policies for security settings in your enterprise](/enterprise-cloud@latest/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise#managing-allowed-ip-addresses-for-organizations-in-your-enterprise)" in the {% data variables.product.prodname_ghe_cloud %} documentation. -To configure a connection, your proxy configuration must allow connectivity to `github.com`, `api.github.com`, and `uploads.github.com`. For more information, see "[Configuring an outbound web proxy server](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-an-outbound-web-proxy-server)." +To configure a connection, your proxy configuration must allow connectivity to `github.com`, `api.github.com`, and `uploads.github.com`. For more information, see "[Configuring an outbound web proxy server](/enterprise/admin/guides/installation/configuring-an-outbound-web-proxy-server)." {% endif %} ## Enabling {% data variables.product.prodname_github_connect %} diff --git a/content/admin/configuration/configuring-network-settings/configuring-a-hostname.md b/content/admin/configuration/configuring-network-settings/configuring-a-hostname.md index 4c374cc4df..1a9f6ec53b 100644 --- a/content/admin/configuration/configuring-network-settings/configuring-a-hostname.md +++ b/content/admin/configuration/configuring-network-settings/configuring-a-hostname.md @@ -18,7 +18,7 @@ If you configure a hostname instead of a hard-coded IP address, you will be able The hostname setting in the {% data variables.enterprise.management_console %} should be set to an appropriate fully qualified domain name (FQDN) which is resolvable on the internet or within your internal network. For example, your hostname setting could be `github.companyname.com.` Web and API requests will automatically redirect to the hostname configured in the {% data variables.enterprise.management_console %}. -After you configure a hostname, you can enable subdomain isolation to further increase the security of {% data variables.product.product_location %}. For more information, see "[Enabling subdomain isolation](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-subdomain-isolation/)." +After you configure a hostname, you can enable subdomain isolation to further increase the security of {% data variables.product.product_location %}. For more information, see "[Enabling subdomain isolation](/enterprise/admin/guides/installation/enabling-subdomain-isolation/)." For more information on the supported hostname types, see [Section 2.1 of the HTTP RFC](https://tools.ietf.org/html/rfc1123#section-2). @@ -34,4 +34,4 @@ For more information on the supported hostname types, see [Section 2.1 of the HT {% data reusables.enterprise_management_console.test-domain-settings-failure %} {% data reusables.enterprise_management_console.save-settings %} -To help mitigate various cross-site scripting vulnerabilities, we recommend that you enable subdomain isolation for {% data variables.product.product_location %} after you configure a hostname. For more information, see "[Enabling subdomain isolation](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-subdomain-isolation/)." +To help mitigate various cross-site scripting vulnerabilities, we recommend that you enable subdomain isolation for {% data variables.product.product_location %} after you configure a hostname. For more information, see "[Enabling subdomain isolation](/enterprise/admin/guides/installation/enabling-subdomain-isolation/)." diff --git a/content/admin/configuration/configuring-network-settings/configuring-tls.md b/content/admin/configuration/configuring-network-settings/configuring-tls.md index 33ebb49248..979b62cc0f 100644 --- a/content/admin/configuration/configuring-network-settings/configuring-tls.md +++ b/content/admin/configuration/configuring-network-settings/configuring-tls.md @@ -31,9 +31,9 @@ To allow users to use FIDO U2F for two-factor authentication, you must enable TL To use TLS in production, you must have a certificate in an unencrypted PEM format signed by a trusted certificate authority. -Your certificate will also need Subject Alternative Names configured for the subdomains listed in "[Enabling subdomain isolation](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-subdomain-isolation#about-subdomain-isolation)" and will need to include the full certificate chain if it has been signed by an intermediate certificate authority. For more information, see "[Subject Alternative Name](http://en.wikipedia.org/wiki/SubjectAltName)" on Wikipedia. +Your certificate will also need Subject Alternative Names configured for the subdomains listed in "[Enabling subdomain isolation](/enterprise/admin/guides/installation/enabling-subdomain-isolation#about-subdomain-isolation)" and will need to include the full certificate chain if it has been signed by an intermediate certificate authority. For more information, see "[Subject Alternative Name](http://en.wikipedia.org/wiki/SubjectAltName)" on Wikipedia. -You can generate a certificate signing request (CSR) for your instance using the `ghe-ssl-generate-csr` command. For more information, see "[Command-line utilities](/enterprise/{{ currentVersion }}/admin/guides/installation/command-line-utilities/#ghe-ssl-generate-csr)." +You can generate a certificate signing request (CSR) for your instance using the `ghe-ssl-generate-csr` command. For more information, see "[Command-line utilities](/enterprise/admin/guides/installation/command-line-utilities/#ghe-ssl-generate-csr)." ## Uploading a custom TLS certificate @@ -65,7 +65,7 @@ Let's Encrypt is a public certificate authority that issues free, automated TLS When you enable automation of TLS certificate management using Let's Encrypt, {% data variables.product.product_location %} will contact the Let's Encrypt servers to obtain a certificate. To renew a certificate, Let's Encrypt servers must validate control of the configured domain name with inbound HTTP requests. -You can also use the `ghe-ssl-acme` command line utility on {% data variables.product.product_location %} to automatically generate a Let's Encrypt certificate. For more information, see "[Command-line utilities](/enterprise/{{ currentVersion }}/admin/guides/installation/command-line-utilities#ghe-ssl-acme)." +You can also use the `ghe-ssl-acme` command line utility on {% data variables.product.product_location %} to automatically generate a Let's Encrypt certificate. For more information, see "[Command-line utilities](/enterprise/admin/guides/installation/command-line-utilities#ghe-ssl-acme)." ## Configuring TLS using Let's Encrypt diff --git a/content/admin/configuration/configuring-network-settings/enabling-subdomain-isolation.md b/content/admin/configuration/configuring-network-settings/enabling-subdomain-isolation.md index d8a36f5d3b..a939afbea7 100644 --- a/content/admin/configuration/configuring-network-settings/enabling-subdomain-isolation.md +++ b/content/admin/configuration/configuring-network-settings/enabling-subdomain-isolation.md @@ -48,13 +48,13 @@ When subdomain isolation is enabled, {% data variables.product.prodname_ghe_serv Before you enable subdomain isolation, you must configure your network settings for your new domain. -- Specify a valid domain name as your hostname, instead of an IP address. For more information, see "[Configuring a hostname](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-a-hostname)." +- Specify a valid domain name as your hostname, instead of an IP address. For more information, see "[Configuring a hostname](/enterprise/admin/guides/installation/configuring-a-hostname)." {% data reusables.enterprise_installation.changing-hostname-not-supported %} - Set up a wildcard Domain Name System (DNS) record or individual DNS records for the subdomains listed above. We recommend creating an A record for `*.HOSTNAME` that points to your server's IP address so you don't have to create multiple records for each subdomain. - Get a wildcard Transport Layer Security (TLS) certificate for `*.HOSTNAME` with a Subject Alternative Name (SAN) for both `HOSTNAME` and the wildcard domain `*.HOSTNAME`. For example, if your hostname is `github.octoinc.com`, get a certificate with the Common Name value set to `*.github.octoinc.com` and a SAN value set to both `github.octoinc.com` and `*.github.octoinc.com`. -- Enable TLS on your appliance. For more information, see "[Configuring TLS](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-tls/)." +- Enable TLS on your appliance. For more information, see "[Configuring TLS](/enterprise/admin/guides/installation/configuring-tls/)." ## Enabling subdomain isolation diff --git a/content/admin/configuration/configuring-network-settings/using-github-enterprise-server-with-a-load-balancer.md b/content/admin/configuration/configuring-network-settings/using-github-enterprise-server-with-a-load-balancer.md index 8f247f7d7b..95bfa9e7ef 100644 --- a/content/admin/configuration/configuring-network-settings/using-github-enterprise-server-with-a-load-balancer.md +++ b/content/admin/configuration/configuring-network-settings/using-github-enterprise-server-with-a-load-balancer.md @@ -69,7 +69,7 @@ We strongly recommend enabling PROXY protocol support for both your instance and ## Configuring health checks -Health checks allow a load balancer to stop sending traffic to a node that is not responding if a pre-configured check fails on that node. If the instance is offline due to maintenance or unexpected failure, the load balancer can display a status page. In a High Availability (HA) configuration, a load balancer can be used as part of a failover strategy. However, automatic failover of HA pairs is not supported. You must manually promote the replica instance before it will begin serving requests. For more information, see "[Configuring {% data variables.product.prodname_ghe_server %} for High Availability](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-github-enterprise-server-for-high-availability/)." +Health checks allow a load balancer to stop sending traffic to a node that is not responding if a pre-configured check fails on that node. If the instance is offline due to maintenance or unexpected failure, the load balancer can display a status page. In a High Availability (HA) configuration, a load balancer can be used as part of a failover strategy. However, automatic failover of HA pairs is not supported. You must manually promote the replica instance before it will begin serving requests. For more information, see "[Configuring {% data variables.product.prodname_ghe_server %} for High Availability](/enterprise/admin/guides/installation/configuring-github-enterprise-server-for-high-availability/)." {% data reusables.enterprise_clustering.health_checks %} {% data reusables.enterprise_site_admin_settings.maintenance-mode-status %} diff --git a/content/admin/configuration/configuring-your-enterprise/accessing-the-management-console.md b/content/admin/configuration/configuring-your-enterprise/accessing-the-management-console.md index 93b08d2844..e484ec6513 100644 --- a/content/admin/configuration/configuring-your-enterprise/accessing-the-management-console.md +++ b/content/admin/configuration/configuring-your-enterprise/accessing-the-management-console.md @@ -54,7 +54,7 @@ The first time that you access the {% data variables.enterprise.management_conso The {% data variables.enterprise.management_console %} locks after ten failed login attempts are made in the span of ten minutes. You must wait for the login screen to automatically unlock before attempting to log in again. The login screen automatically unlocks as soon as the previous ten minute period contains fewer than ten failed login attempts. The counter resets after a successful login occurs. -To immediately unlock the {% data variables.enterprise.management_console %}, use the `ghe-reactivate-admin-login` command via the administrative shell. For more information, see "[Command line utilities](/enterprise/{{ currentVersion }}/admin/guides/installation/command-line-utilities#ghe-reactivate-admin-login)" and "[Accessing the administrative shell (SSH)](/enterprise/{{ currentVersion }}/admin/guides/installation/accessing-the-administrative-shell-ssh/)." +To immediately unlock the {% data variables.enterprise.management_console %}, use the `ghe-reactivate-admin-login` command via the administrative shell. For more information, see "[Command line utilities](/enterprise/admin/guides/installation/command-line-utilities#ghe-reactivate-admin-login)" and "[Accessing the administrative shell (SSH)](/enterprise/admin/guides/installation/accessing-the-administrative-shell-ssh/)." ## Troubleshooting failed connections to the {% data variables.enterprise.management_console %} diff --git a/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md b/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md index 3335f4cc4d..a2f233ddf6 100644 --- a/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md +++ b/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md @@ -15,7 +15,7 @@ topics: - Enterprise - SSH --- -You can execute these commands from anywhere on the VM after signing in as an SSH admin user. For more information, see "[Accessing the administrative shell (SSH)](/enterprise/{{ currentVersion }}/admin/guides/installation/accessing-the-administrative-shell-ssh/)." +You can execute these commands from anywhere on the VM after signing in as an SSH admin user. For more information, see "[Accessing the administrative shell (SSH)](/enterprise/admin/guides/installation/accessing-the-administrative-shell-ssh/)." ## General @@ -124,7 +124,7 @@ $ ghe-config app.github.rate-limiting-exempt-users "hubot github-ac ### ghe-config-apply -This utility applies {% data variables.enterprise.management_console %} settings, reloads system services, prepares a storage device, reloads application services, and runs any pending database migrations. It is equivalent to clicking **Save settings** in the {% data variables.enterprise.management_console %}'s web UI or to sending a POST request to [the `/setup/api/configure` endpoint](/enterprise/{{ currentVersion }}/user/rest/reference/enterprise-admin#management-console). +This utility applies {% data variables.enterprise.management_console %} settings, reloads system services, prepares a storage device, reloads application services, and runs any pending database migrations. It is equivalent to clicking **Save settings** in the {% data variables.enterprise.management_console %}'s web UI or to sending a POST request to [the `/setup/api/configure` endpoint](/enterprise/user/rest/reference/enterprise-admin#management-console). You will probably never need to run this manually, but it's available if you want to automate the process of saving your settings via SSH. @@ -352,7 +352,7 @@ stop/waiting ### ghe-set-password -With `ghe-set-password`, you can set a new password to authenticate into the [{% data variables.enterprise.management_console %}](/enterprise/{{ currentVersion }}/admin/guides/installation/accessing-the-management-console). +With `ghe-set-password`, you can set a new password to authenticate into the [{% data variables.enterprise.management_console %}](/enterprise/admin/guides/installation/accessing-the-management-console). ```shell ghe-set-password @@ -394,7 +394,7 @@ existing keys in /etc/ssh/ssh_host_* and generate new ones. [y/N] ### ghe-ssh-weak-fingerprints -This utility returns a report of known weak SSH keys stored on the {% data variables.product.prodname_enterprise %} appliance. You can optionally revoke user keys as a bulk action. The utility will report weak system keys, which you must manually revoke in the [{% data variables.enterprise.management_console %}](/enterprise/{{ currentVersion }}/admin/guides/installation/accessing-the-management-console). +This utility returns a report of known weak SSH keys stored on the {% data variables.product.prodname_enterprise %} appliance. You can optionally revoke user keys as a bulk action. The utility will report weak system keys, which you must manually revoke in the [{% data variables.enterprise.management_console %}](/enterprise/admin/guides/installation/accessing-the-management-console). ```shell # Print a report of weak user and system SSH keys @@ -406,7 +406,7 @@ $ ghe-ssh-weak-fingerprints --revoke ### ghe-ssl-acme -This utility allows you to install a Let's Encrypt certificate on your {% data variables.product.prodname_enterprise %} appliance. For more information, see "[Configuring TLS](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-tls)." +This utility allows you to install a Let's Encrypt certificate on your {% data variables.product.prodname_enterprise %} appliance. For more information, see "[Configuring TLS](/enterprise/admin/guides/installation/configuring-tls)." You can use the `-x` flag to remove the ACME configuration. @@ -418,7 +418,7 @@ ghe-ssl-acme -e This utility allows you to install a custom root CA certificate on your {% data variables.product.prodname_enterprise %} server. The certificate must be in PEM format. Furthermore, if your certificate provider includes multiple CA certificates in a single file, you must separate them into individual files that you then pass to `ghe-ssl-ca-certificate-install` one at a time. -Run this utility to add a certificate chain for S/MIME commit signature verification. For more information, see "[About commit signature verification](/enterprise/{{ currentVersion }}/user/articles/about-commit-signature-verification/)." +Run this utility to add a certificate chain for S/MIME commit signature verification. For more information, see "[About commit signature verification](/enterprise/user/articles/about-commit-signature-verification/)." Run this utility when {% data variables.product.product_location %} is unable to connect to another server because the latter is using a self-signed SSL certificate or an SSL certificate for which it doesn't provide the necessary CA bundle. One way to confirm this is to run `openssl s_client -connect host:port -verify 0 -CApath /etc/ssl/certs` from {% data variables.product.product_location %}. If the remote server's SSL certificate can be verified, your `SSL-Session` should have a return code of 0, as shown below. @@ -470,7 +470,7 @@ ghe-ssl-certificate-setup ### ghe-ssl-generate-csr -This utility allows you to generate a private key and certificate signing request (CSR), which you can share with a commercial or private certificate authority to get a valid certificate to use with your instance. For more information, see "[Configuring TLS](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-tls)." +This utility allows you to generate a private key and certificate signing request (CSR), which you can share with a commercial or private certificate authority to get a valid certificate to use with your instance. For more information, see "[Configuring TLS](/enterprise/admin/guides/installation/configuring-tls)." For more information about this command or for additional options, use the `-h` flag. @@ -812,7 +812,7 @@ In this example, `ghe-repl-status -vv` sends verbose status information from a r ### ghe-upgrade -This utility installs or verifies an upgrade package. You can also use this utility to roll back a patch release if an upgrade fails or is interrupted. For more information, see "[Upgrading {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/guides/installation/upgrading-github-enterprise-server/)." +This utility installs or verifies an upgrade package. You can also use this utility to roll back a patch release if an upgrade fails or is interrupted. For more information, see "[Upgrading {% data variables.product.prodname_ghe_server %}](/enterprise/admin/guides/installation/upgrading-github-enterprise-server/)." To verify an upgrade package: ```shell @@ -872,7 +872,7 @@ ghe-license-usage ### ghe-org-membership-update -This utility will enforce the default organization membership visibility setting on all members in your instance. For more information, see "[Configuring visibility for organization membership](/enterprise/{{ currentVersion }}/admin/guides/user-management/configuring-visibility-for-organization-membership)." Setting options are `public` or `private`. +This utility will enforce the default organization membership visibility setting on all members in your instance. For more information, see "[Configuring visibility for organization membership](/enterprise/admin/guides/user-management/configuring-visibility-for-organization-membership)." Setting options are `public` or `private`. ```shell ghe-org-membership-update --visibility=SETTING diff --git a/content/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance.md b/content/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance.md index dd064138a6..75a747021b 100644 --- a/content/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance.md +++ b/content/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance.md @@ -72,7 +72,7 @@ More resources may be required depending on your usage, such as user activity an {% endnote %} 4. Set the `GHE_DATA_DIR` value to the filesystem location where you want to store backup snapshots. -5. Open your primary instance's settings page at `https://HOSTNAME/setup/settings` and add the backup host's SSH key to the list of authorized SSH keys. For more information, see [Accessing the administrative shell (SSH)](/enterprise/{{ currentVersion }}/admin/guides/installation/accessing-the-administrative-shell-ssh/). +5. Open your primary instance's settings page at `https://HOSTNAME/setup/settings` and add the backup host's SSH key to the list of authorized SSH keys. For more information, see [Accessing the administrative shell (SSH)](/enterprise/admin/guides/installation/accessing-the-administrative-shell-ssh/). 6. Verify SSH connectivity with {% data variables.product.product_location %} with the `ghe-host-check` command. ```shell $ bin/ghe-host-check diff --git a/content/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications.md b/content/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications.md index a9f03fb889..64fd2b7f45 100644 --- a/content/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications.md +++ b/content/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications.md @@ -98,7 +98,7 @@ If you want to allow email replies to notifications, you must configure your DNS ### Create a Support Bundle -If you cannot determine what is wrong from the displayed error message, you can download a [support bundle](/enterprise/{{ currentVersion }}/admin/guides/enterprise-support/providing-data-to-github-support) containing the entire SMTP conversation between your mail server and {% data variables.product.prodname_ghe_server %}. Once you've downloaded and extracted the bundle, check the entries in *enterprise-manage-logs/unicorn.log* for the entire SMTP conversation log and any related errors. +If you cannot determine what is wrong from the displayed error message, you can download a [support bundle](/enterprise/admin/guides/enterprise-support/providing-data-to-github-support) containing the entire SMTP conversation between your mail server and {% data variables.product.prodname_ghe_server %}. Once you've downloaded and extracted the bundle, check the entries in *enterprise-manage-logs/unicorn.log* for the entire SMTP conversation log and any related errors. The unicorn log should show a transaction similar to the following: diff --git a/content/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode.md b/content/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode.md index a19eed6c19..bd182830a8 100644 --- a/content/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode.md +++ b/content/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode.md @@ -86,7 +86,7 @@ You can also use a command-line utility to configure the IP exception list. For ## Scheduling maintenance mode with {% data variables.product.prodname_enterprise_api %} -You can schedule maintenance for different times or dates with {% data variables.product.prodname_enterprise_api %}. For more information, see "[Management Console](/enterprise/{{ currentVersion }}/user/rest/reference/enterprise-admin#enable-or-disable-maintenance-mode)." +You can schedule maintenance for different times or dates with {% data variables.product.prodname_enterprise_api %}. For more information, see "[Management Console](/enterprise/user/rest/reference/enterprise-admin#enable-or-disable-maintenance-mode)." ## Enabling or disabling maintenance mode for all nodes in a cluster diff --git a/content/admin/configuration/configuring-your-enterprise/enabling-private-mode.md b/content/admin/configuration/configuring-your-enterprise/enabling-private-mode.md index 1b3ad8c95e..d3a0fe6c9f 100644 --- a/content/admin/configuration/configuring-your-enterprise/enabling-private-mode.md +++ b/content/admin/configuration/configuring-your-enterprise/enabling-private-mode.md @@ -25,7 +25,7 @@ You must enable private mode if {% data variables.product.product_location %} is {% data reusables.enterprise_installation.image-urls-viewable-warning %} -With private mode enabled, you can allow unauthenticated Git operations (and anyone with network access to {% data variables.product.product_location %}) to read a public repository's code on your instance with anonymous Git read access enabled. For more information, see "[Allowing admins to enable anonymous Git read access to public repositories](/enterprise/{{ currentVersion }}/admin/guides/user-management/allowing-admins-to-enable-anonymous-git-read-access-to-public-repositories)." +With private mode enabled, you can allow unauthenticated Git operations (and anyone with network access to {% data variables.product.product_location %}) to read a public repository's code on your instance with anonymous Git read access enabled. For more information, see "[Allowing admins to enable anonymous Git read access to public repositories](/enterprise/admin/guides/user-management/allowing-admins-to-enable-anonymous-git-read-access-to-public-repositories)." {% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} diff --git a/content/admin/configuration/configuring-your-enterprise/site-admin-dashboard.md b/content/admin/configuration/configuring-your-enterprise/site-admin-dashboard.md index 3871535de8..e074b64fd8 100644 --- a/content/admin/configuration/configuring-your-enterprise/site-admin-dashboard.md +++ b/content/admin/configuration/configuring-your-enterprise/site-admin-dashboard.md @@ -215,21 +215,21 @@ Refer to this section of the site admin dashboard to manage organizations, peopl This is a list of the repositories on {% data variables.product.product_location %}. You can click on a repository name and access functions for administering the repository. -- [Blocking force pushes to a repository](/enterprise/{{ currentVersion }}/admin/guides/developer-workflow/blocking-force-pushes-to-a-repository/) -- [Configuring {% data variables.large_files.product_name_long %}](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-git-large-file-storage/#configuring-git-large-file-storage-for-an-individual-repository) -- [Archiving and unarchiving repositories](/enterprise/{{ currentVersion }}/admin/guides/user-management/archiving-and-unarchiving-repositories/) +- [Blocking force pushes to a repository](/enterprise/admin/guides/developer-workflow/blocking-force-pushes-to-a-repository/) +- [Configuring {% data variables.large_files.product_name_long %}](/enterprise/admin/guides/installation/configuring-git-large-file-storage/#configuring-git-large-file-storage-for-an-individual-repository) +- [Archiving and unarchiving repositories](/enterprise/admin/guides/user-management/archiving-and-unarchiving-repositories/) ## All users -Here you can see all of the users on {% data variables.product.product_location %}, and [initiate an SSH key audit](/enterprise/{{ currentVersion }}/admin/guides/user-management/auditing-ssh-keys). +Here you can see all of the users on {% data variables.product.product_location %}, and [initiate an SSH key audit](/enterprise/admin/guides/user-management/auditing-ssh-keys). ## Site admins -Here you can see all of the administrators on {% data variables.product.product_location %}, and [initiate an SSH key audit](/enterprise/{{ currentVersion }}/admin/guides/user-management/auditing-ssh-keys). +Here you can see all of the administrators on {% data variables.product.product_location %}, and [initiate an SSH key audit](/enterprise/admin/guides/user-management/auditing-ssh-keys). ## Dormant users {% ifversion ghes %} -Here you can see and [suspend](/enterprise/{{ currentVersion }}/admin/guides/user-management/suspending-and-unsuspending-users) all of the inactive users on {% data variables.product.product_location %}. A user account is considered to be inactive ("dormant") when it: +Here you can see and [suspend](/enterprise/admin/guides/user-management/suspending-and-unsuspending-users) all of the inactive users on {% data variables.product.product_location %}. A user account is considered to be inactive ("dormant") when it: {% endif %} {% ifversion ghae %} Here you can see and suspend all of the inactive users on {% data variables.product.product_location %}. A user account is considered to be inactive ("dormant") when it: @@ -239,8 +239,8 @@ Here you can see and suspend all of the inactive users on {% data variables.prod - Has not generated any activity within that time period. - Is not a site administrator. -{% data reusables.enterprise_site_admin_settings.dormancy-threshold %} For more information, see "[Managing dormant users](/enterprise/{{ currentVersion }}/admin/guides/user-management/managing-dormant-users/#configuring-the-dormancy-threshold)." +{% data reusables.enterprise_site_admin_settings.dormancy-threshold %} For more information, see "[Managing dormant users](/enterprise/admin/guides/user-management/managing-dormant-users/#configuring-the-dormancy-threshold)." ## Suspended users -Here you can see all of the users who have been suspended on {% data variables.product.product_location %}, and [initiate an SSH key audit](/enterprise/{{ currentVersion }}/admin/guides/user-management/auditing-ssh-keys). +Here you can see all of the users who have been suspended on {% data variables.product.product_location %}, and [initiate an SSH key audit](/enterprise/admin/guides/user-management/auditing-ssh-keys). diff --git a/content/admin/enterprise-management/caching-repositories/configuring-a-repository-cache.md b/content/admin/enterprise-management/caching-repositories/configuring-a-repository-cache.md index 00fe89ba84..ca4f7f0bfd 100644 --- a/content/admin/enterprise-management/caching-repositories/configuring-a-repository-cache.md +++ b/content/admin/enterprise-management/caching-repositories/configuring-a-repository-cache.md @@ -62,10 +62,10 @@ Then, when told to fetch `https://github.example.com/myorg/myrepo`, Git will ins $ ghe-repl-setup PRIMARY IP ``` -1. Set a `cache_location` for the repository cache, replacing *CACHE-LOCATION* with an alphanumeric identifier, such as the region where the cache is deployed. +1. Set a `cache_location` for the repository cache, replacing *CACHE-LOCATION* with an alphanumeric identifier, such as the region where the cache is deployed. Also set a datacenter name for this cache; new caches will attempt to seed from another cache in the same datacenter. ```shell - $ ghe-repl-node --cache CACHE-LOCATION + $ ghe-repl-node --cache CACHE-LOCATION --datacenter REPLICA-DC-NAME ``` {% data reusables.enterprise_installation.replication-command %} diff --git a/content/admin/enterprise-management/configuring-clustering/about-clustering.md b/content/admin/enterprise-management/configuring-clustering/about-clustering.md index 77aa3f9b25..030322cf6e 100644 --- a/content/admin/enterprise-management/configuring-clustering/about-clustering.md +++ b/content/admin/enterprise-management/configuring-clustering/about-clustering.md @@ -18,7 +18,7 @@ topics: {% data variables.product.prodname_ghe_server %} is comprised of a set of services. In a cluster, these services run across multiple nodes and requests are load balanced between them. Changes are automatically stored with redundant copies on separate nodes. Most of the services are equal peers with other instances of the same service. The exceptions to this are the `mysql-server` and `redis-server` services. These operate with a single _primary_ node with one or more _replica_ nodes. -Learn more about [services required for clustering](/enterprise/{{ currentVersion }}/admin/enterprise-management/about-cluster-nodes#services-required-for-clustering). +Learn more about [services required for clustering](/enterprise/admin/enterprise-management/about-cluster-nodes#services-required-for-clustering). ## Is clustering right for my organization? @@ -26,7 +26,7 @@ Learn more about [services required for clustering](/enterprise/{{ currentVersio {% data variables.product.prodname_ghe_server %} requires low latency between nodes and is not intended for redundancy across geographic locations. -Clustering provides redundancy, but it is not intended to replace a High Availability configuration. For more information, see [High Availability configuration](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-github-enterprise-server-for-high-availability). A primary/secondary failover configuration is far simpler than clustering and will serve the needs of many organizations. For more information, see [Differences between Clustering and High Availability](/enterprise/{{ currentVersion }}/admin/guides/clustering/differences-between-clustering-and-high-availability-ha/). +Clustering provides redundancy, but it is not intended to replace a High Availability configuration. For more information, see [High Availability configuration](/enterprise/admin/guides/installation/configuring-github-enterprise-server-for-high-availability). A primary/secondary failover configuration is far simpler than clustering and will serve the needs of many organizations. For more information, see [Differences between Clustering and High Availability](/enterprise/admin/guides/clustering/differences-between-clustering-and-high-availability-ha/). {% data reusables.package_registry.packages-cluster-support %} diff --git a/content/admin/enterprise-management/configuring-clustering/differences-between-clustering-and-high-availability-ha.md b/content/admin/enterprise-management/configuring-clustering/differences-between-clustering-and-high-availability-ha.md index 31a26cb6ef..23cae5fc7c 100644 --- a/content/admin/enterprise-management/configuring-clustering/differences-between-clustering-and-high-availability-ha.md +++ b/content/admin/enterprise-management/configuring-clustering/differences-between-clustering-and-high-availability-ha.md @@ -38,8 +38,8 @@ Neither HA nor Clustering should be considered a replacement for regular backups ## Monitoring -Availability features, especially ones with automatic failover such as Clustering, can mask a failure since service is usually not disrupted when something fails. Whether you are using HA or Clustering, monitoring the health of each instance is important so that you are aware when a failure occurs. For more information on monitoring, see "[Recommended alert thresholds](/enterprise/{{ currentVersion }}/admin/guides/installation/recommended-alert-thresholds/)" and "[Monitoring cluster nodes](/enterprise/{{ currentVersion}}/admin/guides/clustering/monitoring-cluster-nodes/)." +Availability features, especially ones with automatic failover such as Clustering, can mask a failure since service is usually not disrupted when something fails. Whether you are using HA or Clustering, monitoring the health of each instance is important so that you are aware when a failure occurs. For more information on monitoring, see "[Recommended alert thresholds](/enterprise/admin/guides/installation/recommended-alert-thresholds/)" and "[Monitoring cluster nodes](/enterprise/{{ currentVersion}}/admin/guides/clustering/monitoring-cluster-nodes/)." ## Further reading - For more information about {% data variables.product.prodname_ghe_server %} Clustering, see "[About clustering](/enterprise/{{ currentVersion}}/admin/guides/clustering/about-clustering/)." -- For more information about HA, see "[Configuring {% data variables.product.prodname_ghe_server %} for High Availability](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-github-enterprise-server-for-high-availability/)." +- For more information about HA, see "[Configuring {% data variables.product.prodname_ghe_server %} for High Availability](/enterprise/admin/guides/installation/configuring-github-enterprise-server-for-high-availability/)." diff --git a/content/admin/enterprise-management/configuring-clustering/initializing-the-cluster.md b/content/admin/enterprise-management/configuring-clustering/initializing-the-cluster.md index 421f0633d0..414cd71df6 100644 --- a/content/admin/enterprise-management/configuring-clustering/initializing-the-cluster.md +++ b/content/admin/enterprise-management/configuring-clustering/initializing-the-cluster.md @@ -16,12 +16,12 @@ topics: ## Installing {% data variables.product.prodname_ghe_server %} -1. On each cluster node, provision and install {% data variables.product.prodname_ghe_server %}. For more information, see "[Setting up a {% data variables.product.prodname_ghe_server %} instance](/enterprise/{{ currentVersion }}/admin/guides/installation/setting-up-a-github-enterprise-server-instance)." +1. On each cluster node, provision and install {% data variables.product.prodname_ghe_server %}. For more information, see "[Setting up a {% data variables.product.prodname_ghe_server %} instance](/enterprise/admin/guides/installation/setting-up-a-github-enterprise-server-instance)." 2. Using the administrative shell or DHCP, **only** configure the IP address of each node. Don't configure any other settings. ## Configuring the first node -1. Connect to the node that will be designated as MySQL primary in `cluster.conf`. For more information, see "[About the cluster configuration file](/enterprise/{{ currentVersion }}/admin/guides/clustering/initializing-the-cluster/#about-the-cluster-configuration-file)." +1. Connect to the node that will be designated as MySQL primary in `cluster.conf`. For more information, see "[About the cluster configuration file](/enterprise/admin/guides/clustering/initializing-the-cluster/#about-the-cluster-configuration-file)." 2. In your web browser, visit `https://:8443/setup/`. {% data reusables.enterprise_installation.upload-a-license-file %} {% data reusables.enterprise_installation.save-settings-in-web-based-mgmt-console %} @@ -29,7 +29,7 @@ topics: ## Initializing the cluster -To initialize the cluster, you need a cluster configuration file (`cluster.conf`). For more information, see "[About the cluster configuration file](/enterprise/{{ currentVersion }}/admin/guides/clustering/initializing-the-cluster/#about-the-cluster-configuration-file)". +To initialize the cluster, you need a cluster configuration file (`cluster.conf`). For more information, see "[About the cluster configuration file](/enterprise/admin/guides/clustering/initializing-the-cluster/#about-the-cluster-configuration-file)". 1. From the first node that was configured, run `ghe-cluster-config-init`. This will initialize the cluster if there are nodes in the cluster configuration file that are not configured. 2. Run `ghe-cluster-config-apply`. This will validate the `cluster.conf` file, apply the configuration to each node file and bring up the configured services on each node. @@ -39,7 +39,7 @@ To check the status of a running cluster use the `ghe-cluster-status` command. ## About the cluster configuration file The cluster configuration file (`cluster.conf`) defines the nodes in the cluster, and what services they run. -For more information, see "[About cluster nodes](/enterprise/{{ currentVersion }}/admin/guides/clustering/about-cluster-nodes)." +For more information, see "[About cluster nodes](/enterprise/admin/guides/clustering/about-cluster-nodes)." This example `cluster.conf` defines a cluster with five nodes. diff --git a/content/admin/enterprise-management/configuring-high-availability/about-geo-replication.md b/content/admin/enterprise-management/configuring-high-availability/about-geo-replication.md index ce17d8a050..f23dfde2a8 100644 --- a/content/admin/enterprise-management/configuring-high-availability/about-geo-replication.md +++ b/content/admin/enterprise-management/configuring-high-availability/about-geo-replication.md @@ -33,4 +33,4 @@ Geo-replication will not add capacity to a {% data variables.product.prodname_gh {% data reusables.enterprise_installation.monitoring-replicas %} ## Further reading -- "[Creating geo-replication replicas](/enterprise/{{ currentVersion }}/admin/guides/installation/creating-a-high-availability-replica/#creating-geo-replication-replicas)" +- "[Creating geo-replication replicas](/enterprise/admin/guides/installation/creating-a-high-availability-replica/#creating-geo-replication-replicas)" diff --git a/content/admin/enterprise-management/configuring-high-availability/about-high-availability-configuration.md b/content/admin/enterprise-management/configuring-high-availability/about-high-availability-configuration.md index 484caf1eac..22d33d5a3b 100644 --- a/content/admin/enterprise-management/configuring-high-availability/about-high-availability-configuration.md +++ b/content/admin/enterprise-management/configuring-high-availability/about-high-availability-configuration.md @@ -29,7 +29,7 @@ Use a high availability configuration for protection against: A high availability configuration is not a good solution for: - - **Scaling-out**. While you can distribute traffic geographically using geo-replication, the performance of writes is limited to the speed and availability of the primary appliance. For more information, see "[About geo-replication](/enterprise/{{ currentVersion }}/admin/guides/installation/about-geo-replication/)."{% ifversion ghes > 3.2 %} + - **Scaling-out**. While you can distribute traffic geographically using geo-replication, the performance of writes is limited to the speed and availability of the primary appliance. For more information, see "[About geo-replication](/enterprise/admin/guides/installation/about-geo-replication/)."{% ifversion ghes > 3.2 %} - **CI/CD load**. If you have a large number of CI clients that are geographically distant from your primary instance, you may benefit from configuring a repository cache. For more information, see "[About repository caching](/admin/enterprise-management/caching-repositories/about-repository-caching)."{% endif %} - **Backing up your primary appliance**. A high availability replica does not replace off-site backups in your disaster recovery plan. Some forms of data corruption or loss may be replicated immediately from the primary to the replica. To ensure safe rollback to a stable past state, you must perform regular backups with historical snapshots. - **Zero downtime upgrades**. To prevent data loss and split-brain situations in controlled promotion scenarios, place the primary appliance in maintenance mode and wait for all writes to complete before promoting the replica. @@ -44,13 +44,13 @@ With DNS failover, use short TTL values in the DNS records that point to the pri During failover, you must place the primary into maintenance mode and redirect its DNS records to the replica appliance's IP address. The time needed to redirect traffic from primary to replica will depend on the TTL configuration and time required to update the DNS records. -If you are using geo-replication, you must configure Geo DNS to direct traffic to the nearest replica. For more information, see "[About geo-replication](/enterprise/{{ currentVersion }}/admin/guides/installation/about-geo-replication/)." +If you are using geo-replication, you must configure Geo DNS to direct traffic to the nearest replica. For more information, see "[About geo-replication](/enterprise/admin/guides/installation/about-geo-replication/)." ### Load balancer {% data reusables.enterprise_clustering.load_balancer_intro %} {% data reusables.enterprise_clustering.load_balancer_dns %} -During failover, you must place the primary appliance into maintenance mode. You can configure the load balancer to automatically detect when the replica has been promoted to primary, or it may require a manual configuration change. You must manually promote the replica to primary before it will respond to user traffic. For more information, see "[Using {% data variables.product.prodname_ghe_server %} with a load balancer](/enterprise/{{ currentVersion }}/admin/guides/installation/using-github-enterprise-server-with-a-load-balancer/)." +During failover, you must place the primary appliance into maintenance mode. You can configure the load balancer to automatically detect when the replica has been promoted to primary, or it may require a manual configuration change. You must manually promote the replica to primary before it will respond to user traffic. For more information, see "[Using {% data variables.product.prodname_ghe_server %} with a load balancer](/enterprise/admin/guides/installation/using-github-enterprise-server-with-a-load-balancer/)." {% data reusables.enterprise_installation.monitoring-replicas %} @@ -186,5 +186,5 @@ The `ghe-repl-teardown` command disables replication mode completely, removing t ## Further reading -- "[Creating a high availability replica](/enterprise/{{ currentVersion }}/admin/guides/installation/creating-a-high-availability-replica)" +- "[Creating a high availability replica](/enterprise/admin/guides/installation/creating-a-high-availability-replica)" - "[Network ports](/admin/configuration/configuring-network-settings/network-ports)" diff --git a/content/admin/enterprise-management/configuring-high-availability/creating-a-high-availability-replica.md b/content/admin/enterprise-management/configuring-high-availability/creating-a-high-availability-replica.md index 31d4dbeb3f..ccf5272e1b 100644 --- a/content/admin/enterprise-management/configuring-high-availability/creating-a-high-availability-replica.md +++ b/content/admin/enterprise-management/configuring-high-availability/creating-a-high-availability-replica.md @@ -18,7 +18,7 @@ shortTitle: Create HA replica ## Creating a high availability replica -1. Set up a new {% data variables.product.prodname_ghe_server %} appliance on your desired platform. The replica appliance should mirror the primary appliance's CPU, RAM, and storage settings. We recommend that you install the replica appliance in an independent environment. The underlying hardware, software, and network components should be isolated from those of the primary appliance. If you are a using a cloud provider, use a separate region or zone. For more information, see ["Setting up a {% data variables.product.prodname_ghe_server %} instance"](/enterprise/{{ currentVersion }}/admin/guides/installation/setting-up-a-github-enterprise-server-instance). +1. Set up a new {% data variables.product.prodname_ghe_server %} appliance on your desired platform. The replica appliance should mirror the primary appliance's CPU, RAM, and storage settings. We recommend that you install the replica appliance in an independent environment. The underlying hardware, software, and network components should be isolated from those of the primary appliance. If you are a using a cloud provider, use a separate region or zone. For more information, see ["Setting up a {% data variables.product.prodname_ghe_server %} instance"](/enterprise/admin/guides/installation/setting-up-a-github-enterprise-server-instance). 1. Ensure that both the primary appliance and the new replica appliance can communicate with each other over ports 122/TCP and 1194/UDP. For more information, see "[Network ports](/admin/configuration/configuring-network-settings/network-ports#administrative-ports)." 1. In a browser, navigate to the new replica appliance's IP address and upload your {% data variables.product.prodname_enterprise %} license. {% data reusables.enterprise_installation.replica-steps %} @@ -37,7 +37,7 @@ shortTitle: Create HA replica ## Creating geo-replication replicas -This example configuration uses a primary and two replicas, which are located in three different geographic regions. While the three nodes can be in different networks, all nodes are required to be reachable from all the other nodes. At the minimum, the required administrative ports should be open to all the other nodes. For more information about the port requirements, see "[Network Ports](/enterprise/{{ currentVersion }}/admin/guides/installation/network-ports/#administrative-ports)." +This example configuration uses a primary and two replicas, which are located in three different geographic regions. While the three nodes can be in different networks, all nodes are required to be reachable from all the other nodes. At the minimum, the required administrative ports should be open to all the other nodes. For more information about the port requirements, see "[Network Ports](/enterprise/admin/guides/installation/network-ports/#administrative-ports)." 1. Create the first replica the same way you would for a standard two node configuration by running `ghe-repl-setup` on the first replica. ```shell @@ -97,6 +97,6 @@ For testing, you can add entries to the local workstation's `hosts` file (for ex ## Further reading -- "[About high availability configuration](/enterprise/{{ currentVersion }}/admin/guides/installation/about-high-availability-configuration)" -- "[Utilities for replication management](/enterprise/{{ currentVersion }}/admin/guides/installation/about-high-availability-configuration/#utilities-for-replication-management)" -- "[About geo-replication](/enterprise/{{ currentVersion }}/admin/guides/installation/about-geo-replication/)" +- "[About high availability configuration](/enterprise/admin/guides/installation/about-high-availability-configuration)" +- "[Utilities for replication management](/enterprise/admin/guides/installation/about-high-availability-configuration/#utilities-for-replication-management)" +- "[About geo-replication](/enterprise/admin/guides/installation/about-geo-replication/)" diff --git a/content/admin/enterprise-management/configuring-high-availability/initiating-a-failover-to-your-replica-appliance.md b/content/admin/enterprise-management/configuring-high-availability/initiating-a-failover-to-your-replica-appliance.md index fc91e87d76..ef175af08a 100644 --- a/content/admin/enterprise-management/configuring-high-availability/initiating-a-failover-to-your-replica-appliance.md +++ b/content/admin/enterprise-management/configuring-high-availability/initiating-a-failover-to-your-replica-appliance.md @@ -49,7 +49,7 @@ The time required to failover depends on how long it takes to manually promote t ``` 5. Update the DNS record to point to the IP address of the replica. Traffic is directed to the replica after the TTL period elapses. If you are using a load balancer, ensure it is configured to send traffic to the replica. 6. Notify users that they can resume normal operations. -7. If desired, set up replication from the new primary to existing appliances and the previous primary. For more information, see "[About high availability configuration](/enterprise/{{ currentVersion }}/admin/guides/installation/about-high-availability-configuration/#utilities-for-replication-management)." +7. If desired, set up replication from the new primary to existing appliances and the previous primary. For more information, see "[About high availability configuration](/enterprise/admin/guides/installation/about-high-availability-configuration/#utilities-for-replication-management)." 8. Appliances you do not intend to setup replication to that were part of the high availability configuration prior the failover, need to be removed from the high availability configuration by UUID. - On the former appliances, get their UUID via `cat /data/user/common/uuid`. ```shell @@ -62,4 +62,4 @@ The time required to failover depends on how long it takes to manually promote t ## Further reading -- "[Utilities for replication management](/enterprise/{{ currentVersion }}/admin/guides/installation/about-high-availability-configuration/#utilities-for-replication-management)" +- "[Utilities for replication management](/enterprise/admin/guides/installation/about-high-availability-configuration/#utilities-for-replication-management)" diff --git a/content/admin/enterprise-management/configuring-high-availability/recovering-a-high-availability-configuration.md b/content/admin/enterprise-management/configuring-high-availability/recovering-a-high-availability-configuration.md index 225fbaf927..a9c5eb633b 100644 --- a/content/admin/enterprise-management/configuring-high-availability/recovering-a-high-availability-configuration.md +++ b/content/admin/enterprise-management/configuring-high-availability/recovering-a-high-availability-configuration.md @@ -17,7 +17,7 @@ shortTitle: Recover a HA configuration ## About recovery for a high availability configuration -You can use the former primary appliance as the new replica appliance if the failover was planned or was not related to the health of the appliance. If the failover was related to an issue with the primary appliance, you may prefer to create a new replica appliance. For more information, see "[Creating a high availability replica](/enterprise/{{ currentVersion }}/admin/guides/installation/creating-a-high-availability-replica/)." +You can use the former primary appliance as the new replica appliance if the failover was planned or was not related to the health of the appliance. If the failover was related to an issue with the primary appliance, you may prefer to create a new replica appliance. For more information, see "[Creating a high availability replica](/enterprise/admin/guides/installation/creating-a-high-availability-replica/)." {% warning %} diff --git a/content/admin/enterprise-management/monitoring-your-appliance/accessing-the-monitor-dashboard.md b/content/admin/enterprise-management/monitoring-your-appliance/accessing-the-monitor-dashboard.md index 2fec6d4b35..2172cbd34b 100644 --- a/content/admin/enterprise-management/monitoring-your-appliance/accessing-the-monitor-dashboard.md +++ b/content/admin/enterprise-management/monitoring-your-appliance/accessing-the-monitor-dashboard.md @@ -27,7 +27,7 @@ shortTitle: Access the monitor dashboard {% note %} -**Note**: Because regularly polling {% data variables.product.product_location %} with continuous integration (CI) or build servers can effectively cause a denial of service attack that results in problems, we recommend using webhooks to push updates. For more information, see "[About webhooks](/enterprise/{{ currentVersion }}/user/articles/about-webhooks/)". +**Note**: Because regularly polling {% data variables.product.product_location %} with continuous integration (CI) or build servers can effectively cause a denial of service attack that results in problems, we recommend using webhooks to push updates. For more information, see "[About webhooks](/enterprise/user/articles/about-webhooks/)". {% endnote %} @@ -35,8 +35,8 @@ Use the monitor dashboard to stay informed on your appliance's resource health a | Problem | Possible cause(s) | Recommendations | | -------- | ----------------- | --------------- | -| High CPU usage | VM contention from other services or programs running on the same host | If possible, reconfigure other services or programs to use fewer CPU resources. To increase total CPU resources for the VM, see "[Increasing CPU or memory resources](/enterprise/{{ currentVersion }}/admin/guides/installation/increasing-cpu-or-memory-resources/)." | -| High memory usage | VM contention from other services or programs running on the same host | If possible, reconfigure other services or programs to use less memory. To increase the total memory available on the VM, see "[Increasing CPU or memory resources](/enterprise/{{ currentVersion }}/admin/guides/installation/increasing-cpu-or-memory-resources/)." | -| Low disk space availability | Large binaries or log files consuming disk space | If possible, host large binaries on a separate server, and compress or archive log files. If necessary, increase disk space on the VM by following the steps for your platform in "[Increasing storage capacity](/enterprise/{{ currentVersion }}/admin/guides/installation/increasing-storage-capacity/)." | +| High CPU usage | VM contention from other services or programs running on the same host | If possible, reconfigure other services or programs to use fewer CPU resources. To increase total CPU resources for the VM, see "[Increasing CPU or memory resources](/enterprise/admin/guides/installation/increasing-cpu-or-memory-resources/)." | +| High memory usage | VM contention from other services or programs running on the same host | If possible, reconfigure other services or programs to use less memory. To increase the total memory available on the VM, see "[Increasing CPU or memory resources](/enterprise/admin/guides/installation/increasing-cpu-or-memory-resources/)." | +| Low disk space availability | Large binaries or log files consuming disk space | If possible, host large binaries on a separate server, and compress or archive log files. If necessary, increase disk space on the VM by following the steps for your platform in "[Increasing storage capacity](/enterprise/admin/guides/installation/increasing-storage-capacity/)." | | Higher than usual response times | Often caused by one of the above issues | Identify and fix the underlying issues. If response times remain high, contact {% data variables.contact.contact_ent_support %}. | | Elevated error rates | Software issues | Contact {% data variables.contact.contact_ent_support %} and include your support bundle. For more information, see "[Providing data to {% data variables.product.prodname_enterprise %} Support](/enterprise/{{ currentVersion}}/admin/guides/enterprise-support/providing-data-to-github-support#creating-and-sharing-support-bundles)." | diff --git a/content/admin/enterprise-management/monitoring-your-appliance/setting-up-external-monitoring.md b/content/admin/enterprise-management/monitoring-your-appliance/setting-up-external-monitoring.md index 251912feb1..6dbca90226 100644 --- a/content/admin/enterprise-management/monitoring-your-appliance/setting-up-external-monitoring.md +++ b/content/admin/enterprise-management/monitoring-your-appliance/setting-up-external-monitoring.md @@ -17,10 +17,10 @@ shortTitle: Set up external monitoring --- ## About SNMP -Simple Network Management Protocol (SNMP) is a widely supported method of monitoring network devices and servers. SNMP is disabled by default but can be configured through the {% data variables.product.prodname_enterprise %} monitor dashboard. UDP port 161 must be open and reachable from your network management station. For more information, see "[Monitoring using SNMP](/enterprise/{{ currentVersion }}/admin/guides/installation/monitoring-using-snmp/)." +Simple Network Management Protocol (SNMP) is a widely supported method of monitoring network devices and servers. SNMP is disabled by default but can be configured through the {% data variables.product.prodname_enterprise %} monitor dashboard. UDP port 161 must be open and reachable from your network management station. For more information, see "[Monitoring using SNMP](/enterprise/admin/guides/installation/monitoring-using-snmp/)." ## About collectd -collectd is an open source statistics collection and reporting daemon with built-in support for writing to RRD files. Statistics on CPU utilization, memory and disk consumption, network interface traffic and errors, and system load can be forwarded to an external collectd server where graphs, analysis, and alerting may be configured using a wide range of available tools and plugins. To configure `collectd` forwarding, see "[Configuring collectd](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-collectd/)". +collectd is an open source statistics collection and reporting daemon with built-in support for writing to RRD files. Statistics on CPU utilization, memory and disk consumption, network interface traffic and errors, and system load can be forwarded to an external collectd server where graphs, analysis, and alerting may be configured using a wide range of available tools and plugins. To configure `collectd` forwarding, see "[Configuring collectd](/enterprise/admin/guides/installation/configuring-collectd/)". Additionally, the monitoring tools built into underlying virtualization platforms may also be used for basic monitoring and alerting of system resources. For more information, see [Amazon CloudWatch](http://aws.amazon.com/cloudwatch/) and [VMware vSphere Monitoring](http://pubs.vmware.com/vsphere-50/topic/com.vmware.ICbase/PDF/vsphere-esxi-vcenter-server-50-monitoring-performance-guide.pdf) documentation. diff --git a/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/enabling-automatic-update-checks.md b/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/enabling-automatic-update-checks.md index c4577aa5a0..c482927560 100644 --- a/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/enabling-automatic-update-checks.md +++ b/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/enabling-automatic-update-checks.md @@ -13,9 +13,9 @@ topics: - Upgrades shortTitle: Enable automatic update checks --- -When an upgrade package is automatically downloaded for {% data variables.product.product_location %}, you'll receive a message letting you know you can upgrade {% data variables.product.prodname_ghe_server %}. Packages download to the `/var/lib/ghe-updates` directory on {% data variables.product.product_location %}. For more information, see "[Upgrading {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/guides/installation/upgrading-github-enterprise-server)." +When an upgrade package is automatically downloaded for {% data variables.product.product_location %}, you'll receive a message letting you know you can upgrade {% data variables.product.prodname_ghe_server %}. Packages download to the `/var/lib/ghe-updates` directory on {% data variables.product.product_location %}. For more information, see "[Upgrading {% data variables.product.prodname_ghe_server %}](/enterprise/admin/guides/installation/upgrading-github-enterprise-server)." -If a hotpatch is available for an upgrade, the `.hpkg` will download automatically. In the management console you can choose to install the hotpatch immediately or schedule installation for a later time. For more information, see "[Upgrading with a hotpatch](/enterprise/{{ currentVersion }}/admin/guides/installation/upgrading-github-enterprise-server#upgrading-with-a-hotpatch)." +If a hotpatch is available for an upgrade, the `.hpkg` will download automatically. In the management console you can choose to install the hotpatch immediately or schedule installation for a later time. For more information, see "[Upgrading with a hotpatch](/enterprise/admin/guides/installation/upgrading-github-enterprise-server#upgrading-with-a-hotpatch)." {% tip %} diff --git a/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-cpu-or-memory-resources.md b/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-cpu-or-memory-resources.md index 05428a11ca..d117fdaf09 100644 --- a/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-cpu-or-memory-resources.md +++ b/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-cpu-or-memory-resources.md @@ -18,7 +18,7 @@ shortTitle: Increase CPU or memory {% note %} -**Note:** Before increasing CPU or memory resources, put your instance in maintenance mode.{% ifversion ip-exception-list %} You can validate changes by configuring an IP exception list to allow access from specified IP addresses. {% endif %} For more information, see "[Enabling and scheduling maintenance mode](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-and-scheduling-maintenance-mode)." +**Note:** Before increasing CPU or memory resources, put your instance in maintenance mode.{% ifversion ip-exception-list %} You can validate changes by configuring an IP exception list to allow access from specified IP addresses. {% endif %} For more information, see "[Enabling and scheduling maintenance mode](/enterprise/admin/guides/installation/enabling-and-scheduling-maintenance-mode)." {% endnote %} diff --git a/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-storage-capacity.md b/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-storage-capacity.md index 8018b9e894..f97776bf1c 100644 --- a/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-storage-capacity.md +++ b/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-storage-capacity.md @@ -23,7 +23,7 @@ As more users join {% data variables.product.product_location %}, you may need t {% note %} -**Note:** Before resizing any storage volume, put your instance in maintenance mode.{% ifversion ip-exception-list %} You can validate changes by configuring an IP exception list to allow access from specified IP addresses. {% endif %} For more information, see "[Enabling and scheduling maintenance mode](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-and-scheduling-maintenance-mode)." +**Note:** Before resizing any storage volume, put your instance in maintenance mode.{% ifversion ip-exception-list %} You can validate changes by configuring an IP exception list to allow access from specified IP addresses. {% endif %} For more information, see "[Enabling and scheduling maintenance mode](/enterprise/admin/guides/installation/enabling-and-scheduling-maintenance-mode)." {% endnote %} @@ -35,7 +35,7 @@ As more users join {% data variables.product.product_location %}, you may need t 1. Resize the existing user volume disk using your virtualization platform's tools. {% data reusables.enterprise_installation.ssh-into-instance %} -3. Put the appliance in maintenance mode. For more information, see "[Enabling and scheduling maintenance mode](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-and-scheduling-maintenance-mode)." +3. Put the appliance in maintenance mode. For more information, see "[Enabling and scheduling maintenance mode](/enterprise/admin/guides/installation/enabling-and-scheduling-maintenance-mode)." 4. Reboot the appliance to detect the new storage allocation: ```shell $ sudo reboot @@ -47,7 +47,7 @@ As more users join {% data variables.product.product_location %}, you may need t ## Increasing the root partition size using a new appliance -1. Set up a new {% data variables.product.prodname_ghe_server %} instance with a larger root disk using the same version as your current appliance. For more information, see "[Setting up a {% data variables.product.prodname_ghe_server %} instance](/enterprise/{{ currentVersion }}/admin/guides/installation/setting-up-a-github-enterprise-server-instance)." +1. Set up a new {% data variables.product.prodname_ghe_server %} instance with a larger root disk using the same version as your current appliance. For more information, see "[Setting up a {% data variables.product.prodname_ghe_server %} instance](/enterprise/admin/guides/installation/setting-up-a-github-enterprise-server-instance)." 2. Shut down the current appliance: ```shell $ sudo poweroff @@ -59,7 +59,7 @@ As more users join {% data variables.product.product_location %}, you may need t {% warning %} -**Warning:** Before increasing the root partition size, you must put your instance in maintenance mode. For more information, see "[Enabling and scheduling maintenance mode](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-and-scheduling-maintenance-mode)." +**Warning:** Before increasing the root partition size, you must put your instance in maintenance mode. For more information, see "[Enabling and scheduling maintenance mode](/enterprise/admin/guides/installation/enabling-and-scheduling-maintenance-mode)." {% endwarning %} diff --git a/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/index.md b/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/index.md index 126dce06e2..3f1f55d5a1 100644 --- a/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/index.md +++ b/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/index.md @@ -2,8 +2,8 @@ title: Updating the virtual machine and physical resources intro: 'Upgrading the virtual software and virtual hardware requires some downtime for your instance, so be sure to plan your upgrade in advance.' redirect_from: - - '/enterprise/{{ currentVersion }}/admin/guides/installation/upgrading-the-vm' - - '/enterprise/{{ currentVersion }}/admin/guides/installation/upgrading-physical-resources' + - '/enterprise/admin/guides/installation/upgrading-the-vm' + - '/enterprise/admin/guides/installation/upgrading-physical-resources' - /enterprise/admin/installation/updating-the-virtual-machine-and-physical-resources - /enterprise/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources versions: diff --git a/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/migrating-from-github-enterprise-1110x-to-2123.md b/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/migrating-from-github-enterprise-1110x-to-2123.md index 912f655881..ffb7743610 100644 --- a/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/migrating-from-github-enterprise-1110x-to-2123.md +++ b/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/migrating-from-github-enterprise-1110x-to-2123.md @@ -56,7 +56,7 @@ To upgrade to the latest version of {% data variables.product.prodname_enterpris 7. Click **Add key** and then click **Continue**. 8. Copy the `ghe-restore` command that you'll run on the backup host to migrate data to the new instance. ![Starting a migration](/assets/images/enterprise/migration/migration-restore-start.png) -9. Enable maintenance mode on the old instance and wait for all active processes to complete. For more information, see "[Enabling and scheduling maintenance mode](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-and-scheduling-maintenance-mode)." +9. Enable maintenance mode on the old instance and wait for all active processes to complete. For more information, see "[Enabling and scheduling maintenance mode](/enterprise/admin/guides/installation/enabling-and-scheduling-maintenance-mode)." {% note %} @@ -99,4 +99,4 @@ To upgrade to the latest version of {% data variables.product.prodname_enterpris {% endnote %} 15. Switch user network traffic from the old instance to the new instance using either DNS or IP address assignment. -16. Upgrade to the latest patch release of {{ currentVersion }}. For more information, see "[Upgrading {% data variables.product.prodname_ghe_server %}](/enterprise/admin/guides/installation/upgrading-github-enterprise-server/)." +16. Upgrade to the latest patch release of {% data variables.product.prodname_ghe_server %}. For more information, see "[Upgrading {% data variables.product.prodname_ghe_server %}](/enterprise/admin/guides/installation/upgrading-github-enterprise-server/)." diff --git a/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrade-requirements.md b/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrade-requirements.md index fa32f2c3f2..b4956310b7 100644 --- a/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrade-requirements.md +++ b/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrade-requirements.md @@ -18,7 +18,7 @@ topics: **Notes:** {% ifversion ghes < 3.3 %}- Features such as {% data variables.product.prodname_actions %}, {% data variables.product.prodname_registry %}, {% data variables.product.prodname_mobile %} and {% data variables.product.prodname_GH_advanced_security %} are available on {% data variables.product.prodname_ghe_server %} 3.0 or higher. We highly recommend upgrading to 3.0 or later releases to take advantage of critical security updates, bug fixes and feature enhancements.{% endif %} - Upgrade packages are available at [enterprise.github.com](https://enterprise.github.com/releases) for supported versions. Verify the availability of the upgrade packages you will need to complete the upgrade. If a package is not available, contact {% data variables.contact.contact_ent_support %} for assistance. -- If you're using {% data variables.product.prodname_ghe_server %} Clustering, see "[Upgrading a cluster](/enterprise/{{ currentVersion }}/admin/guides/clustering/upgrading-a-cluster/)" in the {% data variables.product.prodname_ghe_server %} Clustering Guide for specific instructions unique to clustering. +- If you're using {% data variables.product.prodname_ghe_server %} Clustering, see "[Upgrading a cluster](/enterprise/admin/guides/clustering/upgrading-a-cluster/)" in the {% data variables.product.prodname_ghe_server %} Clustering Guide for specific instructions unique to clustering. - The release notes for {% data variables.product.prodname_ghe_server %} provide a comprehensive list of new features for every version of {% data variables.product.prodname_ghe_server %}. For more information, see the [releases page](https://enterprise.github.com/releases). {% endnote %} @@ -28,7 +28,7 @@ topics: - Include as few upgrades as possible in your upgrade process. For example, instead of upgrading from {% data variables.product.prodname_enterprise %} {{ enterpriseServerReleases.supported[2] }} to {{ enterpriseServerReleases.supported[1] }} to {{ enterpriseServerReleases.latest }}, you could upgrade from {% data variables.product.prodname_enterprise %} {{ enterpriseServerReleases.supported[2] }} to {{ enterpriseServerReleases.latest }}. Use the [{% data variables.enterprise.upgrade_assistant %}](https://support.github.com/enterprise/server-upgrade) to find the upgrade path from your current release version. - If you’re several versions behind, upgrade {% data variables.product.product_location %} as far forward as possible with each step of your upgrade process. Using the latest version possible on each upgrade allows you to take advantage of performance improvements and bug fixes. For example, you could upgrade from {% data variables.product.prodname_enterprise %} 2.7 to 2.8 to 2.10, but upgrading from {% data variables.product.prodname_enterprise %} 2.7 to 2.9 to 2.10 uses a later version in the second step. - Use the latest patch release when upgrading. {% data reusables.enterprise_installation.enterprise-download-upgrade-pkg %} -- Use a staging instance to test the upgrade steps. For more information, see "[Setting up a staging instance](/enterprise/{{ currentVersion }}/admin/guides/installation/setting-up-a-staging-instance/)." +- Use a staging instance to test the upgrade steps. For more information, see "[Setting up a staging instance](/enterprise/admin/guides/installation/setting-up-a-staging-instance/)." - When running multiple upgrades, wait at least 24 hours between feature upgrades to allow data migrations and upgrade tasks running in the background to fully complete. - Take a snapshot before upgrading your virtual machine. For more information, see "[Taking a snapshot](/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server#taking-a-snapshot)." - Ensure you have a recent, successful backup of your instance. For more information, see the [{% data variables.product.prodname_enterprise_backup_utilities %} README.md file](https://github.com/github/backup-utils#readme). @@ -51,4 +51,4 @@ Use the number to estimate the amount of disk space the MySQL audit logs will ne ## Next steps -After reviewing these recommendations and requirements, you can upgrade {% data variables.product.prodname_ghe_server %}. For more information, see "[Upgrading {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/guides/installation/upgrading-github-enterprise-server/)." +After reviewing these recommendations and requirements, you can upgrade {% data variables.product.prodname_ghe_server %}. For more information, see "[Upgrading {% data variables.product.prodname_ghe_server %}](/enterprise/admin/guides/installation/upgrading-github-enterprise-server/)." diff --git a/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server.md b/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server.md index 21f91636c9..240fbe1fc9 100644 --- a/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server.md +++ b/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server.md @@ -27,14 +27,14 @@ shortTitle: Upgrading GHES ## Preparing to upgrade -1. Determine an upgrade strategy and choose a version to upgrade to. For more information, see "[Upgrade requirements](/enterprise/{{ currentVersion }}/admin/guides/installation/upgrade-requirements/)" and refer to the [{% data variables.enterprise.upgrade_assistant %}](https://support.github.com/enterprise/server-upgrade) to find the upgrade path from your current release version. +1. Determine an upgrade strategy and choose a version to upgrade to. For more information, see "[Upgrade requirements](/enterprise/admin/guides/installation/upgrade-requirements/)" and refer to the [{% data variables.enterprise.upgrade_assistant %}](https://support.github.com/enterprise/server-upgrade) to find the upgrade path from your current release version. 1. Create a fresh backup of your primary instance with the {% data variables.product.prodname_enterprise_backup_utilities %}. For more information, see the [{% data variables.product.prodname_enterprise_backup_utilities %} README.md file](https://github.com/github/backup-utils#readme). 1. If {% data variables.product.product_location %} uses ephemeral self-hosted runners for {% data variables.product.prodname_actions %} and you've disabled automatic updates, upgrade your runners to the version of the runner application that your upgraded instance will run. 1. If you are upgrading using an upgrade package, schedule a maintenance window for {% data variables.product.prodname_ghe_server %} end users. If you are using a hotpatch, maintenance mode is not required. {% note %} - **Note:** The maintenance window depends on the type of upgrade you perform. Upgrades using a hotpatch usually don't require a maintenance window. Sometimes a reboot is required, which you can perform at a later time. Following the versioning scheme of MAJOR.FEATURE.PATCH, patch releases using an upgrade package typically require less than five minutes of downtime. Feature releases that include data migrations take longer depending on storage performance and the amount of data that's migrated. For more information, see "[Enabling and scheduling maintenance mode](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-and-scheduling-maintenance-mode)." + **Note:** The maintenance window depends on the type of upgrade you perform. Upgrades using a hotpatch usually don't require a maintenance window. Sometimes a reboot is required, which you can perform at a later time. Following the versioning scheme of MAJOR.FEATURE.PATCH, patch releases using an upgrade package typically require less than five minutes of downtime. Feature releases that include data migrations take longer depending on storage performance and the amount of data that's migrated. For more information, see "[Enabling and scheduling maintenance mode](/enterprise/admin/guides/installation/enabling-and-scheduling-maintenance-mode)." {% endnote %} @@ -72,7 +72,7 @@ There are two types of snapshots: {% data reusables.enterprise_installation.hotpatching-explanation %} -Using the {% data variables.enterprise.management_console %}, you can install a hotpatch immediately or schedule it for later installation. You can use the administrative shell to install a hotpatch with the `ghe-upgrade` utility. For more information, see "[Upgrade requirements](/enterprise/{{ currentVersion }}/admin/guides/installation/upgrade-requirements/)." +Using the {% data variables.enterprise.management_console %}, you can install a hotpatch immediately or schedule it for later installation. You can use the administrative shell to install a hotpatch with the `ghe-upgrade` utility. For more information, see "[Upgrade requirements](/enterprise/admin/guides/installation/upgrade-requirements/)." {% note %} @@ -81,7 +81,7 @@ Using the {% data variables.enterprise.management_console %}, you can install a {% ifversion ghes %} - If {% data variables.product.product_location %} is running a release candidate build, you can't upgrade with a hotpatch. -- {% endif %}Installing a hotpatch using the {% data variables.enterprise.management_console %} is not available in clustered environments. To install a hotpatch in a clustered environment, see "[Upgrading a cluster](/enterprise/{{ currentVersion }}/admin/clustering/upgrading-a-cluster#upgrading-with-a-hotpatch)." +- {% endif %}Installing a hotpatch using the {% data variables.enterprise.management_console %} is not available in clustered environments. To install a hotpatch in a clustered environment, see "[Upgrading a cluster](/enterprise/admin/clustering/upgrading-a-cluster#upgrading-with-a-hotpatch)." {% endnote %} @@ -93,7 +93,7 @@ You can use the {% data variables.enterprise.management_console %} to upgrade wi If the upgrade target you're presented with is a feature release instead of a patch release, you cannot use the {% data variables.enterprise.management_console %} to install a hotpatch. You must install the hotpatch using the administrative shell instead. For more information, see "[Installing a hotpatch using the administrative shell](#installing-a-hotpatch-using-the-administrative-shell)." -1. Enable automatic updates. For more information, see "[Enabling automatic updates](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-automatic-update-checks/)." +1. Enable automatic updates. For more information, see "[Enabling automatic updates](/enterprise/admin/guides/installation/enabling-automatic-update-checks/)." {% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_management_console.updates-tab %} @@ -146,7 +146,7 @@ Appliances configured for high-availability and geo-replication use replica inst ## Upgrading with an upgrade package -While you can use a hotpatch to upgrade to the latest patch release within a feature series, you must use an upgrade package to upgrade to a newer feature release. For example to upgrade from `2.11.10` to `2.12.4` you must use an upgrade package since these are in different feature series. For more information, see "[Upgrade requirements](/enterprise/{{ currentVersion }}/admin/guides/installation/upgrade-requirements/)." +While you can use a hotpatch to upgrade to the latest patch release within a feature series, you must use an upgrade package to upgrade to a newer feature release. For example to upgrade from `2.11.10` to `2.12.4` you must use an upgrade package since these are in different feature series. For more information, see "[Upgrade requirements](/enterprise/admin/guides/installation/upgrade-requirements/)." ### Upgrading a single appliance with an upgrade package @@ -155,7 +155,7 @@ While you can use a hotpatch to upgrade to the latest patch release within a fea {% data reusables.enterprise_installation.ssh-into-instance %} 2. {% data reusables.enterprise_installation.enterprise-download-upgrade-pkg %} Select the appropriate platform and copy the URL for the upgrade package (*.pkg* file). {% data reusables.enterprise_installation.download-package %} -4. Enable maintenance mode and wait for all active processes to complete on the {% data variables.product.prodname_ghe_server %} instance. For more information, see "[Enabling and scheduling maintenance mode](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-and-scheduling-maintenance-mode)." +4. Enable maintenance mode and wait for all active processes to complete on the {% data variables.product.prodname_ghe_server %} instance. For more information, see "[Enabling and scheduling maintenance mode](/enterprise/admin/guides/installation/enabling-and-scheduling-maintenance-mode)." {% note %} @@ -199,7 +199,7 @@ Appliances configured for high-availability and geo-replication use replica inst {% endwarning %} -1. On the primary instance, enable maintenance mode and wait for all active processes to complete. For more information, see "[Enabling maintenance mode](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-and-scheduling-maintenance-mode/)." +1. On the primary instance, enable maintenance mode and wait for all active processes to complete. For more information, see "[Enabling maintenance mode](/enterprise/admin/guides/installation/enabling-and-scheduling-maintenance-mode/)." {% data reusables.enterprise_installation.replica-ssh %} 3. On the replica instance, or on all replica instances if you're running multiple replica instances as part of geo-replication, run `ghe-repl-stop` to stop replication. 4. Upgrade the primary instance by following the instructions in "[Upgrading a single appliance with an upgrade package](#upgrading-a-single-appliance-with-an-upgrade-package)." @@ -241,7 +241,7 @@ To roll back a patch release, use the `ghe-upgrade` command with the `--allow-pa Once the rollback is complete, restart replication by running `ghe-repl-start` on all replicas. -For more information, see "[Command-line utilities](/enterprise/{{ currentVersion }}/admin/guides/installation/command-line-utilities/#ghe-upgrade)." +For more information, see "[Command-line utilities](/enterprise/admin/guides/installation/command-line-utilities/#ghe-upgrade)." ### Rolling back a feature release diff --git a/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/allowing-built-in-authentication-for-users-outside-your-provider.md b/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/allowing-built-in-authentication-for-users-outside-your-provider.md index daa01b5339..dd7e3fb554 100644 --- a/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/allowing-built-in-authentication-for-users-outside-your-provider.md +++ b/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/allowing-built-in-authentication-for-users-outside-your-provider.md @@ -28,7 +28,7 @@ If you configure built-in authentication and a person successfully authenticates {% warning %} -**Warning:** If you disable built-in authentication, you must individually suspend any users that should no longer have access to the instance. For more information, see "[Suspending and unsuspending users](/enterprise/{{ currentVersion }}/admin/guides/user-management/suspending-and-unsuspending-users)." +**Warning:** If you disable built-in authentication, you must individually suspend any users that should no longer have access to the instance. For more information, see "[Suspending and unsuspending users](/enterprise/admin/guides/user-management/suspending-and-unsuspending-users)." {% endwarning %} diff --git a/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-oidc-for-enterprise-managed-users.md b/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-oidc-for-enterprise-managed-users.md index 1b18092f7f..14ea2d5367 100644 --- a/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-oidc-for-enterprise-managed-users.md +++ b/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-oidc-for-enterprise-managed-users.md @@ -28,7 +28,9 @@ If you currently use SAML SSO for authentication and would prefer to use OIDC an ## Identity provider support -Support for OIDC is in public beta and available for customers using Azure Active Directory (Azure AD). +Support for OIDC is in public beta and available for customers using Azure Active Directory (Azure AD). + +Each Azure AD tenant can support only one OIDC integration with {% data variables.product.prodname_emus %}. If you want to connect Azure AD to more than one enterprise on {% data variables.product.prodname_dotcom %}, use SAML instead. For more information, see "[Configuring SAML single sign-on for {% data variables.product.prodname_emus %}](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-saml-single-sign-on-for-enterprise-managed-users)." ## Configuring OIDC for Enterprise Managed Users @@ -44,4 +46,4 @@ Support for OIDC is in public beta and available for customers using Azure Activ ## Enabling provisioning -After you enable OIDC SSO, enable provisioning. For more information, see "[Configuring SCIM provisioning for enterprise managed users](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/configuring-scim-provisioning-for-enterprise-managed-users)." \ No newline at end of file +After you enable OIDC SSO, enable provisioning. For more information, see "[Configuring SCIM provisioning for enterprise managed users](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/configuring-scim-provisioning-for-enterprise-managed-users)." diff --git a/content/admin/identity-and-access-management/using-ldap-for-enterprise-iam/using-ldap.md b/content/admin/identity-and-access-management/using-ldap-for-enterprise-iam/using-ldap.md index 8974095835..732d5fc72e 100644 --- a/content/admin/identity-and-access-management/using-ldap-for-enterprise-iam/using-ldap.md +++ b/content/admin/identity-and-access-management/using-ldap-for-enterprise-iam/using-ldap.md @@ -114,7 +114,7 @@ When this option is selected, the certificate is validated to make sure: {% endnote %} -LDAP Sync lets you synchronize {% data variables.product.prodname_ghe_server %} users and team membership against your established LDAP groups. This lets you establish role-based access control for users from your LDAP server instead of manually within {% data variables.product.prodname_ghe_server %}. For more information, see "[Creating teams](/enterprise/{{ currentVersion }}/admin/guides/user-management/creating-teams#creating-teams-with-ldap-sync-enabled)." +LDAP Sync lets you synchronize {% data variables.product.prodname_ghe_server %} users and team membership against your established LDAP groups. This lets you establish role-based access control for users from your LDAP server instead of manually within {% data variables.product.prodname_ghe_server %}. For more information, see "[Creating teams](/enterprise/admin/guides/user-management/creating-teams#creating-teams-with-ldap-sync-enabled)." To enable LDAP Sync, in your LDAP settings, select **Synchronize Emails**, **Synchronize SSH Keys**, or **Synchronize GPG Keys** . @@ -190,8 +190,8 @@ You can view the full list of LDAP users who have access to your instance and pr Unless [LDAP Sync is enabled](#enabling-ldap-sync), changes to LDAP accounts are not automatically synchronized with {% data variables.product.prodname_ghe_server %}. * To use a new LDAP admin group, users must be manually promoted and demoted on {% data variables.product.prodname_ghe_server %} to reflect changes in LDAP. -* To add or remove LDAP accounts in LDAP admin groups, [promote or demote the accounts on {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/guides/user-management/promoting-or-demoting-a-site-administrator). -* To remove LDAP accounts, [suspend the {% data variables.product.prodname_ghe_server %} accounts](/enterprise/{{ currentVersion }}/admin/guides/user-management/suspending-and-unsuspending-users). +* To add or remove LDAP accounts in LDAP admin groups, [promote or demote the accounts on {% data variables.product.prodname_ghe_server %}](/enterprise/admin/guides/user-management/promoting-or-demoting-a-site-administrator). +* To remove LDAP accounts, [suspend the {% data variables.product.prodname_ghe_server %} accounts](/enterprise/admin/guides/user-management/suspending-and-unsuspending-users). ### Manually syncing LDAP accounts @@ -204,10 +204,10 @@ Unless [LDAP Sync is enabled](#enabling-ldap-sync), changes to LDAP accounts are 5. Under "LDAP," click **Sync now** to manually update the account with data from your LDAP server. ![LDAP sync now button](/assets/images/enterprise/site-admin-settings/ldap-sync-now-button.png) -You can also [use the API to trigger a manual sync](/enterprise/{{ currentVersion }}/user/rest/reference/enterprise-admin#ldap). +You can also [use the API to trigger a manual sync](/enterprise/user/rest/reference/enterprise-admin#ldap). ## Revoking access to {% data variables.product.product_location %} If [LDAP Sync is enabled](#enabling-ldap-sync), removing a user's LDAP credentials will suspend their account after the next synchronization run. -If LDAP Sync is **not** enabled, you must manually suspend the {% data variables.product.prodname_ghe_server %} account after you remove the LDAP credentials. For more information, see "[Suspending and unsuspending users](/enterprise/{{ currentVersion }}/admin/guides/user-management/suspending-and-unsuspending-users)". +If LDAP Sync is **not** enabled, you must manually suspend the {% data variables.product.prodname_ghe_server %} account after you remove the LDAP credentials. For more information, see "[Suspending and unsuspending users](/enterprise/admin/guides/user-management/suspending-and-unsuspending-users)". diff --git a/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-saml-single-sign-on-for-your-enterprise.md b/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-saml-single-sign-on-for-your-enterprise.md index b8afbf3028..be095b071c 100644 --- a/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-saml-single-sign-on-for-your-enterprise.md +++ b/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-saml-single-sign-on-for-your-enterprise.md @@ -137,7 +137,7 @@ You can enable or disable SAML authentication for {% data variables.product.prod ![Screenshot of "Enable encrypted assertions" checkbox within management console's "Authentication" section](/assets/images/help/saml/management-console-enable-encrypted-assertions.png) {%- endif %} -1. In the **Single sign-on URL** field, type the HTTP or HTTPS endpoint on your IdP for single sign-on requests. This value is provided by your IdP configuration. If the host is only available from your internal network, you may need to [configure {% data variables.product.product_location %} to use internal nameservers](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-dns-nameservers/). +1. In the **Single sign-on URL** field, type the HTTP or HTTPS endpoint on your IdP for single sign-on requests. This value is provided by your IdP configuration. If the host is only available from your internal network, you may need to [configure {% data variables.product.product_location %} to use internal nameservers](/enterprise/admin/guides/installation/configuring-dns-nameservers/). ![Screenshot of text field for single sign-on URL](/assets/images/enterprise/management-console/saml-single-sign-url.png) 1. Optionally, in the **Issuer** field, type your SAML issuer's name. This verifies the authenticity of messages sent to {% data variables.product.product_location %}. diff --git a/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-aws.md b/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-aws.md index 26009b8f3d..f770fafed1 100644 --- a/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-aws.md +++ b/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-aws.md @@ -124,7 +124,7 @@ aws ec2 run-instances \ If this is a production instance, we strongly recommend allocating an Elastic IP (EIP) and associating it with the instance before proceeding to {% data variables.product.prodname_ghe_server %} configuration. Otherwise, the public IP address of the instance will not be retained after instance restarts. For more information, see "[Allocating an Elastic IP Address](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/elastic-ip-addresses-eip.html#using-instance-addressing-eips-allocating)" and "[Associating an Elastic IP Address with a Running Instance](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/elastic-ip-addresses-eip.html#using-instance-addressing-eips-associating)" in the Amazon documentation. -Both primary and replica instances should be assigned separate EIPs in production High Availability configurations. For more information, see "[Configuring {% data variables.product.prodname_ghe_server %} for High Availability](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-github-enterprise-server-for-high-availability/)." +Both primary and replica instances should be assigned separate EIPs in production High Availability configurations. For more information, see "[Configuring {% data variables.product.prodname_ghe_server %} for High Availability](/enterprise/admin/guides/installation/configuring-github-enterprise-server-for-high-availability/)." ## Configuring the {% data variables.product.prodname_ghe_server %} instance diff --git a/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise.md b/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise.md index fad869426b..5914f200a2 100644 --- a/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise.md +++ b/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise.md @@ -1010,7 +1010,7 @@ Action | Description | `repo.code_scanning_analysis_deleted` | Code scanning analysis for a repository was deleted. For more information, see "[Delete a code scanning analysis from a repository](/rest/reference/code-scanning#delete-a-code-scanning-analysis-from-a-repository)." | `repo.change_merge_setting` | Pull request merge options were changed for a repository. | `repo.clear_actions_settings` | A repository administrator cleared {% data variables.product.prodname_actions %} policy settings for a repository. -| `repo.config` | A repository administrator blocked force pushes. For more information, see [Blocking force pushes to a repository](/enterprise/{{ currentVersion }}/admin/guides/developer-workflow/blocking-force-pushes-to-a-repository/) to a repository. +| `repo.config` | A repository administrator blocked force pushes. For more information, see [Blocking force pushes to a repository](/enterprise/admin/guides/developer-workflow/blocking-force-pushes-to-a-repository/) to a repository. {%- ifversion fpt or ghec %} | `repo.config.disable_collaborators_only` | The interaction limit for collaborators only was disabled. For more information, see "[Limiting interactions in your repository](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository)." | `repo.config.disable_contributors_only` | The interaction limit for prior contributors only was disabled in a repository. For more information, see "[Limiting interactions in your repository](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository)." diff --git a/content/admin/overview/about-the-github-enterprise-api.md b/content/admin/overview/about-the-github-enterprise-api.md index 13c1255fff..afc43bd7ae 100644 --- a/content/admin/overview/about-the-github-enterprise-api.md +++ b/content/admin/overview/about-the-github-enterprise-api.md @@ -19,8 +19,8 @@ shortTitle: GitHub Enterprise API With the APIs, you can automate many administrative tasks. Some examples include: {% ifversion ghes %} -- Perform changes to the {% data variables.enterprise.management_console %}. For more information, see "[{% data variables.enterprise.management_console %}](/enterprise/{{ currentVersion }}/user/rest/reference/enterprise-admin#management-console)." -- Configure LDAP sync. For more information, see "[LDAP](/enterprise/{{ currentVersion }}/user/rest/reference/enterprise-admin#ldap)."{% endif %} +- Perform changes to the {% data variables.enterprise.management_console %}. For more information, see "[{% data variables.enterprise.management_console %}](/enterprise/user/rest/reference/enterprise-admin#management-console)." +- Configure LDAP sync. For more information, see "[LDAP](/enterprise/user/rest/reference/enterprise-admin#ldap)."{% endif %} - Collect statistics about your enterprise. For more information, see "[Admin stats](/rest/reference/enterprise-admin#admin-stats)." - Manage your enterprise account. For more information, see "[Enterprise accounts](/graphql/guides/managing-enterprise-accounts)." diff --git a/content/admin/policies/enforcing-policy-with-pre-receive-hooks/creating-a-pre-receive-hook-script.md b/content/admin/policies/enforcing-policy-with-pre-receive-hooks/creating-a-pre-receive-hook-script.md index ab45abcb90..07184c4299 100644 --- a/content/admin/policies/enforcing-policy-with-pre-receive-hooks/creating-a-pre-receive-hook-script.md +++ b/content/admin/policies/enforcing-policy-with-pre-receive-hooks/creating-a-pre-receive-hook-script.md @@ -145,7 +145,7 @@ We recommend consolidating hooks to a single repository. If the consolidated hoo $ git push ``` -3. [Create the pre-receive hook](/enterprise/{{ currentVersion }}/admin/guides/developer-workflow/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance/#creating-pre-receive-hooks) on the {% data variables.product.prodname_ghe_server %} instance. +3. [Create the pre-receive hook](/enterprise/admin/guides/developer-workflow/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance/#creating-pre-receive-hooks) on the {% data variables.product.prodname_ghe_server %} instance. ## Testing pre-receive scripts locally You can test a pre-receive hook script locally before you create or update it on {% data variables.product.product_location %}. One method is to create a local Docker environment to act as a remote repository that can execute the pre-receive hook. diff --git a/content/admin/user-management/managing-organizations-in-your-enterprise/configuring-visibility-for-organization-membership.md b/content/admin/user-management/managing-organizations-in-your-enterprise/configuring-visibility-for-organization-membership.md index c1d37a455d..2f609ca713 100644 --- a/content/admin/user-management/managing-organizations-in-your-enterprise/configuring-visibility-for-organization-membership.md +++ b/content/admin/user-management/managing-organizations-in-your-enterprise/configuring-visibility-for-organization-membership.md @@ -29,4 +29,4 @@ You can also enforce your default setting on all current organization members in ![Drop-down menu with option to configure default organization membership visibility as public or private](/assets/images/enterprise/site-admin-settings/default-organization-membership-visibility-drop-down-menu.png) 4. Optionally, to prevent members from changing their membership visibility from the default, select **Enforce on organization members**. ![Checkbox to enforce the default setting on all members](/assets/images/enterprise/site-admin-settings/enforce-default-org-membership-visibility-setting.png){% ifversion ghes %} -5. If you'd like to enforce your new visibility setting on all existing members, use the `ghe-org-membership-update` command-line utility. For more information, see "[Command-line utilities](/enterprise/{{ currentVersion }}/admin/guides/installation/command-line-utilities#ghe-org-membership-update)."{% endif %} +5. If you'd like to enforce your new visibility setting on all existing members, use the `ghe-org-membership-update` command-line utility. For more information, see "[Command-line utilities](/enterprise/admin/guides/installation/command-line-utilities#ghe-org-membership-update)."{% endif %} diff --git a/content/admin/user-management/managing-organizations-in-your-enterprise/creating-teams.md b/content/admin/user-management/managing-organizations-in-your-enterprise/creating-teams.md index e59701591a..0e51eb9d2d 100644 --- a/content/admin/user-management/managing-organizations-in-your-enterprise/creating-teams.md +++ b/content/admin/user-management/managing-organizations-in-your-enterprise/creating-teams.md @@ -18,7 +18,7 @@ Teams are central to many of {% data variables.product.prodname_dotcom %}'s coll A team can represent a group within your company or include people with certain interests or expertise. For example, a team of accessibility experts on {% data variables.product.product_location %} could comprise of people from several different departments. Teams can represent functional concerns that complement a company's existing divisional hierarchy. -Organizations can create multiple levels of nested teams to reflect a company or group's hierarchy structure. For more information, see "[About teams](/enterprise/{{ currentVersion }}/user/articles/about-teams/#nested-teams)." +Organizations can create multiple levels of nested teams to reflect a company or group's hierarchy structure. For more information, see "[About teams](/enterprise/user/articles/about-teams/#nested-teams)." ## Creating a team diff --git a/content/admin/user-management/managing-organizations-in-your-enterprise/requiring-two-factor-authentication-for-an-organization.md b/content/admin/user-management/managing-organizations-in-your-enterprise/requiring-two-factor-authentication-for-an-organization.md index efd44fccd8..c98de35177 100644 --- a/content/admin/user-management/managing-organizations-in-your-enterprise/requiring-two-factor-authentication-for-an-organization.md +++ b/content/admin/user-management/managing-organizations-in-your-enterprise/requiring-two-factor-authentication-for-an-organization.md @@ -23,19 +23,19 @@ For more information, see "[About two-factor authentication](/github/authenticat ## Requirements for enforcing two-factor authentication -Before you can require organization members and outside collaborators to use 2FA, you must [enable two-factor authentication](/enterprise/{{ currentVersion }}/user/articles/securing-your-account-with-two-factor-authentication-2fa/) for your own personal account. +Before you can require organization members and outside collaborators to use 2FA, you must [enable two-factor authentication](/enterprise/user/articles/securing-your-account-with-two-factor-authentication-2fa/) for your own personal account. {% warning %} **Warnings:** -- When your require two-factor authentication, members and outside collaborators (including bot accounts) who do not use 2FA will be removed from the organization and lose access to its repositories, including their forks of private repositories. If they enable 2FA for their personal account within three months of being removed from the organization, you can [reinstate their access privileges and settings](/enterprise/{{ currentVersion }}/user/articles/reinstating-a-former-member-of-your-organization). +- When your require two-factor authentication, members and outside collaborators (including bot accounts) who do not use 2FA will be removed from the organization and lose access to its repositories, including their forks of private repositories. If they enable 2FA for their personal account within three months of being removed from the organization, you can [reinstate their access privileges and settings](/enterprise/user/articles/reinstating-a-former-member-of-your-organization). - When 2FA is required, organization members or outside collaborators who disable 2FA will automatically be removed from the organization. - If you're the sole owner of an organization that requires two-factor authentication, you won't be able to disable 2FA for your personal account without disabling required two-factor authentication for the organization. {% endwarning %} -Before you require use of two-factor authentication, we recommend notifying organization members and outside collaborators and asking them to set up 2FA for their accounts. You can [see if members and outside collaborators already use 2FA](/enterprise/{{ currentVersion }}/user/articles/viewing-whether-users-in-your-organization-have-2fa-enabled) on an organization's People tab. +Before you require use of two-factor authentication, we recommend notifying organization members and outside collaborators and asking them to set up 2FA for their accounts. You can [see if members and outside collaborators already use 2FA](/enterprise/user/articles/viewing-whether-users-in-your-organization-have-2fa-enabled) on an organization's People tab. {% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} @@ -45,7 +45,7 @@ Before you require use of two-factor authentication, we recommend notifying orga ## Viewing people who were removed from your organization -To view people who were automatically removed from your organization for non-compliance when you required two-factor authentication, you can [search the audit log](/enterprise/{{ currentVersion }}/admin/guides/installation/searching-the-audit-log/) using `reason:two_factor_requirement_non_compliance` in the search field. +To view people who were automatically removed from your organization for non-compliance when you required two-factor authentication, you can [search the audit log](/enterprise/admin/guides/installation/searching-the-audit-log/) using `reason:two_factor_requirement_non_compliance` in the search field. {% data reusables.audit_log.octicon_icon %} {% data reusables.enterprise_site_admin_settings.access-settings %} @@ -66,7 +66,7 @@ If any members or outside collaborators are removed from the organization when y ## Further reading -- "[Viewing whether users in your organization have 2FA enabled](/enterprise/{{ currentVersion }}/user/articles/viewing-whether-users-in-your-organization-have-2fa-enabled)" -- "[Securing your account with two-factor authentication (2FA)](/enterprise/{{ currentVersion }}/user/articles/securing-your-account-with-two-factor-authentication-2fa)" -- "[Reinstating a former member of your organization](/enterprise/{{ currentVersion }}/user/articles/reinstating-a-former-member-of-your-organization)" -- "[Reinstating a former outside collaborator's access to your organization](/enterprise/{{ currentVersion }}/user/articles/reinstating-a-former-outside-collaborator-s-access-to-your-organization)" +- "[Viewing whether users in your organization have 2FA enabled](/enterprise/user/articles/viewing-whether-users-in-your-organization-have-2fa-enabled)" +- "[Securing your account with two-factor authentication (2FA)](/enterprise/user/articles/securing-your-account-with-two-factor-authentication-2fa)" +- "[Reinstating a former member of your organization](/enterprise/user/articles/reinstating-a-former-member-of-your-organization)" +- "[Reinstating a former outside collaborator's access to your organization](/enterprise/user/articles/reinstating-a-former-outside-collaborator-s-access-to-your-organization)" diff --git a/content/admin/user-management/managing-users-in-your-enterprise/auditing-users-across-your-enterprise.md b/content/admin/user-management/managing-users-in-your-enterprise/auditing-users-across-your-enterprise.md index e9a1f50b4a..6755919c6b 100644 --- a/content/admin/user-management/managing-users-in-your-enterprise/auditing-users-across-your-enterprise.md +++ b/content/admin/user-management/managing-users-in-your-enterprise/auditing-users-across-your-enterprise.md @@ -112,7 +112,7 @@ The `country` qualifier filters actions by the originating country. The `created` qualifier filters actions by the time they occurred. - Define dates using the format of `YYYY-MM-DD`--that's year, followed by month, followed by day. -- Dates support [greater than, less than, and range qualifiers](/enterprise/{{ currentVersion }}/user/articles/search-syntax). For example: +- Dates support [greater than, less than, and range qualifiers](/enterprise/user/articles/search-syntax). For example: * `created:2014-07-08` finds all events that occurred on July 8th, 2014. * `created:>=2014-07-01` finds all events that occurred on or after July 8th, 2014. * `created:<=2014-07-01` finds all events that occurred on or before July 8th, 2014. diff --git a/content/admin/user-management/managing-users-in-your-enterprise/best-practices-for-user-security.md b/content/admin/user-management/managing-users-in-your-enterprise/best-practices-for-user-security.md index 731713061c..394f244bfe 100644 --- a/content/admin/user-management/managing-users-in-your-enterprise/best-practices-for-user-security.md +++ b/content/admin/user-management/managing-users-in-your-enterprise/best-practices-for-user-security.md @@ -19,7 +19,7 @@ shortTitle: User security best practices Two-factor authentication (2FA) is a way of logging in to websites and services that requires a second factor beyond a password for authentication. In {% data variables.product.prodname_ghe_server %}'s case, this second factor is a one time authentication code generated by an application on a user's smartphone. We strongly recommend requiring your users to enable two-factor authentication on their accounts. With two-factor authentication, both a user's password and their smartphone would have to be compromised to allow the account itself to be compromised. -For more information on configuring two-factor authentication, see "[About two-factor authentication](/enterprise/{{ currentVersion }}/user/articles/about-two-factor-authentication)". +For more information on configuring two-factor authentication, see "[About two-factor authentication](/enterprise/user/articles/about-two-factor-authentication)". {% endif %} ## Requiring a password manager diff --git a/content/admin/user-management/managing-users-in-your-enterprise/promoting-or-demoting-a-site-administrator.md b/content/admin/user-management/managing-users-in-your-enterprise/promoting-or-demoting-a-site-administrator.md index 0227145d68..2ca2fcfec5 100644 --- a/content/admin/user-management/managing-users-in-your-enterprise/promoting-or-demoting-a-site-administrator.md +++ b/content/admin/user-management/managing-users-in-your-enterprise/promoting-or-demoting-a-site-administrator.md @@ -22,7 +22,7 @@ shortTitle: Manage administrators {% endtip %} -For information about promoting a user to an organization owner, see the `ghe-org-admin-promote` section of "[Command-line utilities](/enterprise/{{ currentVersion }}/admin/guides/installation/command-line-utilities#ghe-org-admin-promote)." +For information about promoting a user to an organization owner, see the `ghe-org-admin-promote` section of "[Command-line utilities](/enterprise/admin/guides/installation/command-line-utilities#ghe-org-admin-promote)." ## Promoting a user from the enterprise settings @@ -47,16 +47,16 @@ For information about promoting a user to an organization owner, see the `ghe-or ## Promoting a user from the command line -1. [SSH](/enterprise/{{ currentVersion }}/admin/guides/installation/accessing-the-administrative-shell-ssh/) into your appliance. -2. Run [ghe-user-promote](/enterprise/{{ currentVersion }}/admin/guides/installation/command-line-utilities#ghe-user-promote) with the username to promote. +1. [SSH](/enterprise/admin/guides/installation/accessing-the-administrative-shell-ssh/) into your appliance. +2. Run [ghe-user-promote](/enterprise/admin/guides/installation/command-line-utilities#ghe-user-promote) with the username to promote. ```shell $ ghe-user-promote username ``` ## Demoting a site administrator from the command line -1. [SSH](/enterprise/{{ currentVersion }}/admin/guides/installation/accessing-the-administrative-shell-ssh/) into your appliance. -2. Run [ghe-user-demote](/enterprise/{{ currentVersion }}/admin/guides/installation/command-line-utilities#ghe-user-demote) with the username to demote. +1. [SSH](/enterprise/admin/guides/installation/accessing-the-administrative-shell-ssh/) into your appliance. +2. Run [ghe-user-demote](/enterprise/admin/guides/installation/command-line-utilities#ghe-user-demote) with the username to demote. ```shell $ ghe-user-demote username ``` diff --git a/content/admin/user-management/managing-users-in-your-enterprise/suspending-and-unsuspending-users.md b/content/admin/user-management/managing-users-in-your-enterprise/suspending-and-unsuspending-users.md index f64cdf6334..eee374e9ef 100644 --- a/content/admin/user-management/managing-users-in-your-enterprise/suspending-and-unsuspending-users.md +++ b/content/admin/user-management/managing-users-in-your-enterprise/suspending-and-unsuspending-users.md @@ -69,7 +69,7 @@ As when suspending a user, unsuspending a user takes effect immediately. The use ## Suspending a user from the command line {% data reusables.enterprise_installation.ssh-into-instance %} -2. Run [ghe-user-suspend](/enterprise/{{ currentVersion }}/admin/guides/installation/command-line-utilities#ghe-user-suspend) with the username to suspend. +2. Run [ghe-user-suspend](/enterprise/admin/guides/installation/command-line-utilities#ghe-user-suspend) with the username to suspend. ```shell $ ghe-user-suspend username ``` @@ -94,7 +94,7 @@ You can create a custom message that suspended users will see when attempting to ## Unsuspending a user from the command line {% data reusables.enterprise_installation.ssh-into-instance %} -2. Run [ghe-user-unsuspend](/enterprise/{{ currentVersion }}/admin/guides/installation/command-line-utilities#ghe-user-unsuspend) with the username to unsuspend. +2. Run [ghe-user-unsuspend](/enterprise/admin/guides/installation/command-line-utilities#ghe-user-unsuspend) with the username to unsuspend. ```shell $ ghe-user-unsuspend username ``` diff --git a/content/admin/user-management/migrating-data-to-and-from-your-enterprise/importing-data-from-third-party-version-control-systems.md b/content/admin/user-management/migrating-data-to-and-from-your-enterprise/importing-data-from-third-party-version-control-systems.md index 9baa46aca3..8dc2956555 100644 --- a/content/admin/user-management/migrating-data-to-and-from-your-enterprise/importing-data-from-third-party-version-control-systems.md +++ b/content/admin/user-management/migrating-data-to-and-from-your-enterprise/importing-data-from-third-party-version-control-systems.md @@ -26,7 +26,7 @@ shortTitle: Import from another VCS ```shell $ git-import-rewrite --flavor hg --authors /PATH/AUTHORS-MAP-FILE.csv /PATH/REPO-NAME.git ``` -5. If you haven't yet, [create a new empty repository on {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/user/articles/creating-a-new-repository). +5. If you haven't yet, [create a new empty repository on {% data variables.product.prodname_ghe_server %}](/enterprise/user/articles/creating-a-new-repository). {% data reusables.command_line.switching_directories_procedural %} 7. Push the imported repository to {% data variables.product.prodname_ghe_server %}: ```shell @@ -46,7 +46,7 @@ shortTitle: Import from another VCS ```shell $ git-import-rewrite --flavor svn --authors /PATH/AUTHORS-MAP-FILE.csv /PATH/REPO-NAME.git ``` -5. If you haven't yet, [create a new empty repository on {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/user/articles/creating-a-new-repository). +5. If you haven't yet, [create a new empty repository on {% data variables.product.prodname_ghe_server %}](/enterprise/user/articles/creating-a-new-repository). {% data reusables.command_line.switching_directories_procedural %} 7. Push the imported repository to {% data variables.product.prodname_ghe_server %}: ```shell @@ -66,7 +66,7 @@ shortTitle: Import from another VCS ```shell $ git-import-rewrite --flavor tfs --authors /PATH/AUTHORS-MAP-FILE.csv /PATH/REPO-NAME.git ``` -5. If you haven't yet, [create a new empty repository on {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/user/articles/creating-a-new-repository). +5. If you haven't yet, [create a new empty repository on {% data variables.product.prodname_ghe_server %}](/enterprise/user/articles/creating-a-new-repository). {% data reusables.command_line.switching_directories_procedural %} 7. Push the imported repository to {% data variables.product.prodname_ghe_server %}: ```shell @@ -75,4 +75,4 @@ shortTitle: Import from another VCS ## Further reading -- "[Command-line-utilities](/enterprise/{{ currentVersion }}/admin/guides/installation/command-line-utilities/#import-and-export)" +- "[Command-line-utilities](/enterprise/admin/guides/installation/command-line-utilities/#import-and-export)" diff --git a/content/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log.md b/content/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log.md index b0dbde83b1..f4a0553c13 100644 --- a/content/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log.md +++ b/content/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log.md @@ -155,10 +155,10 @@ An overview of some of the most common actions that are recorded as events in th | `add_member` | Triggered when a {% data variables.product.product_name %} user is {% ifversion fpt or ghec %}[invited to have collaboration access](/articles/inviting-collaborators-to-a-personal-repository){% else %}[given collaboration access](/articles/inviting-collaborators-to-a-personal-repository){% endif %} to a repository. | `add_topic` | Triggered when a repository owner [adds a topic](/articles/classifying-your-repository-with-topics) to a repository. | `archived` | Triggered when a repository owner [archives a repository](/articles/about-archiving-repositories).{% ifversion ghes %} -| `config.disable_anonymous_git_access` | Triggered when [anonymous Git read access is disabled](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository) in a public repository. -| `config.enable_anonymous_git_access` | Triggered when [anonymous Git read access is enabled](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository) in a public repository. -| `config.lock_anonymous_git_access` | Triggered when a repository's [anonymous Git read access setting is locked](/enterprise/{{ currentVersion }}/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access). -| `config.unlock_anonymous_git_access` | Triggered when a repository's [anonymous Git read access setting is unlocked](/enterprise/{{ currentVersion }}/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access).{% endif %} +| `config.disable_anonymous_git_access` | Triggered when [anonymous Git read access is disabled](/enterprise/user/articles/enabling-anonymous-git-read-access-for-a-repository) in a public repository. +| `config.enable_anonymous_git_access` | Triggered when [anonymous Git read access is enabled](/enterprise/user/articles/enabling-anonymous-git-read-access-for-a-repository) in a public repository. +| `config.lock_anonymous_git_access` | Triggered when a repository's [anonymous Git read access setting is locked](/enterprise/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access). +| `config.unlock_anonymous_git_access` | Triggered when a repository's [anonymous Git read access setting is unlocked](/enterprise/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access).{% endif %} | `create` | Triggered when [a new repository is created](/articles/creating-a-new-repository). | `destroy` | Triggered when [a repository is deleted](/articles/deleting-a-repository).{% ifversion fpt or ghec %} | `disable` | Triggered when a repository is disabled (e.g., for [insufficient funds](/articles/unlocking-a-locked-account)).{% endif %}{% ifversion fpt or ghec %} diff --git a/content/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts.md b/content/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts.md index e9dd4c9033..0fdf2235fd 100644 --- a/content/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts.md +++ b/content/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts.md @@ -26,14 +26,12 @@ topics: {% data reusables.dependabot.beta-security-and-version-updates %} {% data reusables.dependabot.enterprise-enable-dependabot %} -Your repository's {% data variables.product.prodname_dependabot_alerts %} tab lists all open and closed {% data variables.product.prodname_dependabot_alerts %}{% ifversion fpt or ghec or ghes > 3.2 %} and corresponding {% data variables.product.prodname_dependabot_security_updates %}{% endif %}. You can{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5638 %} filter alerts by package, ecosystem, or manifest. You can also{% endif %} sort the list of alerts, and you can click into specific alerts for more details. For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)." +Your repository's {% data variables.product.prodname_dependabot_alerts %} tab lists all open and closed {% data variables.product.prodname_dependabot_alerts %}{% ifversion fpt or ghec or ghes > 3.2 %} and corresponding {% data variables.product.prodname_dependabot_security_updates %}{% endif %}. You can{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5638 %} filter alerts by package, ecosystem, or manifest. You can {% endif %} sort the list of alerts, and you can click into specific alerts for more details. {% ifversion dependabot-bulk-alerts %}You can also dismiss or reopen alerts, either one by one or by selecting multiple alerts at once.{% else %}You can also dismiss or reopen alerts. {% endif %} For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)." {% ifversion fpt or ghec or ghes > 3.2 %} You can enable automatic security updates for any repository that uses {% data variables.product.prodname_dependabot_alerts %} and the dependency graph. For more information, see "[About {% data variables.product.prodname_dependabot_security_updates %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-dependabot-security-updates)." {% endif %} -{% data reusables.repositories.dependency-review %} - {% ifversion fpt or ghec or ghes > 3.2 %} ## About updates for vulnerable dependencies in your repository @@ -70,20 +68,22 @@ For alerts where vulnerable calls are detected, the alert details page shows add ![Screenshot showing the alert details page for an alert with a "Vulnerable call" label](/assets/images/help/repository/review-calls-to-vulnerable-functions.png) -For more information, see "[Reviewing and fixing vulnerable dependencies](#reviewing-and-fixing-vulnerable-dependencies)" below. +For more information, see "[Reviewing and fixing alerts](#reviewing-and-fixing-alerts)" below. {% endif %} -## Viewing vulnerable dependencies +## Viewing {% data variables.product.prodname_dependabot_alerts %} {% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5638 %} {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} {% data reusables.repositories.sidebar-dependabot-alerts %} -1. Optionally, to filter alerts, select the **Repository**, **Package**, **Ecosystem**, or **Manifest** dropdown menu then click the filter that you would like to apply. You can also type filters into the search bar. For example, `ecosystem:npm` or `has:patch`. To sort alerts, select the **Sort** dropdown menu then click the option that you would like to sort by. - ![Screenshot of the filter and sort menus in the {% data variables.product.prodname_dependabot_alerts %} tab](/assets/images/help/graphs/dependabot-alerts-filters.png) -1. Click the alert that you would like to view. - ![Alert selected in list of alerts](/assets/images/help/graphs/click-alert-in-alerts-list-ungrouped.png) +1. Optionally, to filter alerts, select the **Repository**, **Package**, **Ecosystem**, or **Manifest** dropdown menu then click the filter that you would like to apply. You can also type filters into the search bar. For example, `ecosystem:npm` or `has:patch`. To sort alerts, select the **Sort** dropdown menu then click the option that you would like to sort by.{% ifversion dependabot-bulk-alerts %} + ![Screenshot of the filter and sort menus in the {% data variables.product.prodname_dependabot_alerts %} tab](/assets/images/help/graphs/dependabot-alerts-filters-checkbox.png){% else %} + ![Screenshot of the filter and sort menus in the {% data variables.product.prodname_dependabot_alerts %} tab](/assets/images/enterprise/3.5/dependabot/dependabot-alerts-filters.png){% endif %} +2. Click the alert that you would like to view.{% ifversion dependabot-bulk-alerts %} + ![Alert selected in list of alerts](/assets/images/help/graphs/click-alert-in-alerts-list-checkbox.png){% else %} + ![Alert selected in list of alerts](/assets/images/enterprise/3.5/dependabot/click-alert-in-alerts-list-ungrouped.png){% endif %} {% else %} {% data reusables.repositories.navigate-to-repo %} @@ -93,7 +93,7 @@ For more information, see "[Reviewing and fixing vulnerable dependencies](#revie ![Alert selected in list of alerts](/assets/images/help/graphs/click-alert-in-alerts-list.png) {% endif %} -## Reviewing and fixing vulnerable dependencies +## Reviewing and fixing alerts It’s important to ensure that all of your dependencies are clean of any security weaknesses. When {% data variables.product.prodname_dependabot %} discovers vulnerabilities in your dependencies, you should assess your project’s level of exposure and determine what remediation steps to take to secure your application. @@ -109,7 +109,7 @@ For supported languages, {% data variables.product.prodname_dependabot %} detect ### Fixing vulnerable dependencies -1. View the details for an alert. For more information, see "[Viewing vulnerable dependencies](#viewing-vulnerable-dependencies)" (above). +1. View the details for an alert. For more information, see "[Viewing {% data variables.product.prodname_dependabot_alerts %}](#viewing-dependabot-alerts)" (above). {% ifversion fpt or ghec or ghes > 3.2 %} 1. If you have {% data variables.product.prodname_dependabot_security_updates %} enabled, there may be a link to a pull request that will fix the dependency. Alternatively, you can click **Create {% data variables.product.prodname_dependabot %} security update** at the top of the alert details page to create a pull request. ![Create {% data variables.product.prodname_dependabot %} security update button](/assets/images/help/repository/create-dependabot-security-update-button-ungrouped.png) @@ -123,26 +123,66 @@ For supported languages, {% data variables.product.prodname_dependabot %} detect Each pull request raised by {% data variables.product.prodname_dependabot %} includes information on commands you can use to control {% data variables.product.prodname_dependabot %}. For more information, see "[Managing pull requests for dependency updates](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-pull-requests-for-dependency-updates#managing-dependabot-pull-requests-with-comment-commands)." {% endif %} -### Dismissing {% data variables.product.prodname_dependabot_alerts %} +## Dismissing {% data variables.product.prodname_dependabot_alerts %} + +{% tip %} + +**Tip:** You can only dismiss open alerts. +{% endtip %} 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. View the details for an alert. For more information, see "[Viewing vulnerable dependencies](#viewing-dependabot-alerts)" (above). 1. Select the "Dismiss" dropdown, and click a reason for dismissing the alert.{% ifversion reopen-dependabot-alerts %} Unfixed dismissed alerts can be reopened later.{% endif %} ![Choosing reason for dismissing the alert via the "Dismiss" drop-down](/assets/images/help/repository/dependabot-alert-dismiss-drop-down-ungrouped.png) +{% ifversion dependabot-bulk-alerts %} + +### Dismissing multiple alerts at once + +1. View the open {% data variables.product.prodname_dependabot_alerts %}. For more information, see "[Viewing {% data variables.product.prodname_dependabot_alerts %}](/en/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts#viewing-dependabot-alerts)". +2. Optionally, filter the list of alerts by selecting a dropdown menu, then clicking the filter that you would like to apply. You can also type filters into the search bar. +3. To the left of each alert title, select the alerts that you want to dismiss. + ![Screenshot of open alerts with checkboxes emphasized](/assets/images/help/graphs/select-multiple-alerts.png) +4. Optionally, at the top of the list of alerts, select all alerts on the page. + ![Screenshot of all open alerts selected](/assets/images/help/graphs/select-all-alerts.png) +5. Select the "Dismiss alerts" dropdown, and click a reason for dismissing the alerts. + ![Screenshot of open alerts page with "Dismiss alerts" drop-down emphasized](/assets/images/help/graphs/dismiss-multiple-alerts.png) + +{% endif %} {% ifversion reopen-dependabot-alerts %} ## Viewing and updating closed alerts +{% tip %} + +**Tip:** You can only reopen alerts that have been previously dismissed. Closed alerts that have already been fixed cannot be reopened. +{% endtip %} + {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} {% data reusables.repositories.sidebar-dependabot-alerts %} -1. To just view closed alerts, click **Closed**. - ![Screenshot showing the "Closed" option](/assets/images/help/repository/dependabot-alerts-closed.png) -1. Click the alert that you would like to view or update. - ![Screenshot showing a highlighted dependabot alert](/assets/images/help/repository/dependabot-alerts-select-closed-alert.png) -2. Optionally, if the alert was dismissed and you wish to reopen it, click **Reopen**. +1. To just view closed alerts, click **Closed**.{% ifversion dependabot-bulk-alerts %} + ![Screenshot showing the "Closed" option](/assets/images/help/repository/dependabot-alerts-closed-checkbox.png){% else %} + ![Screenshot showing the "Closed" option](/assets/images/help/repository/dependabot-alerts-closed.png){% endif %} +1. Click the alert that you would like to view or update.{% ifversion dependabot-bulk-alerts %} + ![Screenshot showing a highlighted dependabot alert](/assets/images/help/repository/dependabot-alerts-select-closed-alert-checkbox.png){% else %} + ![Screenshot showing a highlighted dependabot alert](/assets/images/help/repository/dependabot-alerts-select-closed-alert.png){% endif %} +2. Optionally, if the alert was dismissed and you wish to reopen it, click **Reopen**. Alerts that have already been fixed cannot be reopened. ![Screenshot showing the "Reopen" button](/assets/images/help/repository/reopen-dismissed-alert.png) {% endif %} + +{% ifversion dependabot-bulk-alerts %} + +### Reopening multiple alerts at once + +1. View the closed {% data variables.product.prodname_dependabot_alerts %}. For more information, see "[Viewing and updating closed alerts](/en/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts#viewing-and-updating-closed-alerts)" (above). +2. To the left of each alert title, select the alerts that you want to reopen. + ![Screenshot of closed alerts with checkboxes emphasized](/assets/images/help/repository/dependabot-alerts-open-checkbox.png) +3. Optionally, at the top of the list of alerts, select all closed alerts on the page. + ![Screenshot of closed alerts with all alerts selected](/assets/images/help/graphs/select-all-closed-alerts.png) +4. Click **Reopen** to reopen the alerts. Alerts that have already been fixed cannot be reopened. + ![Screenshot of closed alerts with "Reopen" button emphasized](/assets/images/help/graphs/reopen-multiple-alerts.png) + +{% endif %} \ No newline at end of file diff --git a/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/reuse-an-assignment.md b/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/reuse-an-assignment.md index 0a5e72968b..15e9b6b07c 100644 --- a/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/reuse-an-assignment.md +++ b/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/reuse-an-assignment.md @@ -1,6 +1,6 @@ --- title: Reuse an assignment -intro: You can reuse an existing assignment in more than one classroom, including classrooms in a different organization. +intro: You can reuse existing assignments in more than one classroom, including classrooms in a different organization. versions: fpt: '*' permissions: 'Organization owners who are admins for a classroom can reuse assignments from a classroom. {% data reusables.classroom.classroom-admins-link %}' @@ -8,7 +8,7 @@ shortTitle: Reuse an assignment --- ## About reusing assignments -You can reuse an existing individual or group assignment in any other classroom you have access to, including classrooms in a different organization. If you choose to reuse an assignment, {% data variables.product.prodname_classroom %} will copy the assignment to the classroom you choose. If the assignment uses a template repository and you choose to reuse it in a classroom from a different organization, {% data variables.product.prodname_classroom %} will create a copy of the repository and its contents in the target organization. +You can reuse an existing individual or group assignment in any other classroom you have access to, including classrooms in a different organization. You can also reuse multiple assignments at once from a classroom. If you choose to reuse an assignment, {% data variables.product.prodname_classroom %} will copy the assignment to the classroom you choose. If the assignment uses a template repository and you choose to reuse it in a classroom from a different organization, {% data variables.product.prodname_classroom %} will create a copy of the repository and its contents in the target organization. The copied assignment includes assignment details such as the name, source repository, autograding test, and preferred editor. You can edit the assignment after it has been copied to make changes. You cannot make changes to the preferred editor. @@ -27,7 +27,7 @@ The copied assignment includes assignment details such as the name, source repos ![Reuse assignment button](/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. In the "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. ![Reuse assignment modal](/assets/images/help/classroom/reuse-assignment-modal.png) @@ -35,3 +35,21 @@ The copied assignment includes assignment details such as the name, source repos 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. ![Completed message for reused assignment](/assets/images/help/classroom/reuse-assignment-completed-message.png) + +## Reusing multiple assignments from a classroom + +1. Sign into {% data variables.product.prodname_classroom_with_url %}. +2. To the right of a classroom's name, select the {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} drop-down menu, then click **Reuse assignment**. + + ![Screenshot of classroom overview page with dropdown emphasized](/assets/images/help/classroom/classroom-reuse-assignment-modal.png) + +3. In the "Reuse assignments" modal, use the **Choose an organization** dropdown menu to select the organization you want the assignments to be in. Then use the **Choose a classroom** dropdown menu to select the classroom within that organization that you want to copy the assignments to. + + ![Screenshot of reuse assignments modal](/assets/images/help/classroom/reuse-multiple-assignments-modal.png) + +4. To the left of each assignment, select the assignment you want to reuse. + + ![Screenshot of multiple selected assignments](/assets/images/help/classroom/multiple-assignments-selected.png) + +5. Click **Create assignments**. +6. The assignments are copied to the selected classroom. If you chose to reuse an assignment with a template repository, the copying process may take a few minutes to complete. diff --git a/content/get-started/quickstart/create-a-repo.md b/content/get-started/quickstart/create-a-repo.md index 4dd809ee09..5a16b75e9e 100644 --- a/content/get-started/quickstart/create-a-repo.md +++ b/content/get-started/quickstart/create-a-repo.md @@ -33,7 +33,10 @@ You can store a variety of projects in {% data variables.product.product_name %} {% note %} -**Note:** You can create public repositories for an open source project. When creating your public repository, make sure to include a [license file](https://choosealicense.com/) that determines how you want your project to be shared with others. {% data reusables.open-source.open-source-guide-repositories %} {% data reusables.open-source.open-source-learning %} +**Notes:** +- You can create public repositories for an open source project. When creating your public repository, make sure to include a [license file](https://choosealicense.com/) that determines how you want your project to be shared with others. {% data reusables.open-source.open-source-guide-repositories %} +- {% data reusables.open-source.open-source-learning %} +- You can also add community health files to your repositories, to set guidelines on how to contribute, keep your repositories safe, and much more. For more information, see "[Creating a default community health file](/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file)." {% endnote %} diff --git a/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md b/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md index c22493a223..baf35fadbf 100644 --- a/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md +++ b/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md @@ -622,10 +622,10 @@ For more information, see "[Managing the publication of {% data variables.produc | `advanced_security_disabled` | Triggered when a repository administrator disables {% data variables.product.prodname_GH_advanced_security %} features for the repository. For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)." | `advanced_security_enabled` | Triggered when a repository administrator enables {% data variables.product.prodname_GH_advanced_security %} features for the repository. For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository).". | `archived` | Triggered when a repository admin [archives a repository](/articles/about-archiving-repositories).{% ifversion ghes %} -| `config.disable_anonymous_git_access` | Triggered when [anonymous Git read access is disabled](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository) in a public repository. -| `config.enable_anonymous_git_access` | Triggered when [anonymous Git read access is enabled](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository) in a public repository. -| `config.lock_anonymous_git_access` | Triggered when a repository's [anonymous Git read access setting is locked](/enterprise/{{ currentVersion }}/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access). -| `config.unlock_anonymous_git_access` | Triggered when a repository's [anonymous Git read access setting is unlocked](/enterprise/{{ currentVersion }}/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access).{% endif %} +| `config.disable_anonymous_git_access` | Triggered when [anonymous Git read access is disabled](/enterprise/user/articles/enabling-anonymous-git-read-access-for-a-repository) in a public repository. +| `config.enable_anonymous_git_access` | Triggered when [anonymous Git read access is enabled](/enterprise/user/articles/enabling-anonymous-git-read-access-for-a-repository) in a public repository. +| `config.lock_anonymous_git_access` | Triggered when a repository's [anonymous Git read access setting is locked](/enterprise/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access). +| `config.unlock_anonymous_git_access` | Triggered when a repository's [anonymous Git read access setting is unlocked](/enterprise/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access).{% endif %} | `create` | Triggered when [a new repository is created](/articles/creating-a-new-repository).{% ifversion fpt or ghes or ghec %} | `create_actions_secret` |Triggered when a {% data variables.product.prodname_actions %} secret is created for a repository. For more information, see "[Creating encrypted secrets for a repository](/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-a-repository)."{% endif %} | `destroy` | Triggered when [a repository is deleted](/articles/deleting-a-repository).{% ifversion fpt or ghec %} diff --git a/content/pages/getting-started-with-github-pages/about-github-pages.md b/content/pages/getting-started-with-github-pages/about-github-pages.md index 5d0a1ff8c7..6e8072ac21 100644 --- a/content/pages/getting-started-with-github-pages/about-github-pages.md +++ b/content/pages/getting-started-with-github-pages/about-github-pages.md @@ -66,7 +66,7 @@ Organization | `http(s)://pages./` | `http(s)://///` | `http(s):///pages///` Project site owned by organization account | `http(s)://pages.///` | `http(s):///pages///` -For more information, see "[Enabling subdomain isolation](/enterprise/{{ currentVersion }}/admin/installation/enabling-subdomain-isolation)" or contact your site administrator. +For more information, see "[Enabling subdomain isolation](/enterprise/admin/installation/enabling-subdomain-isolation)" or contact your site administrator. {% endif %} ## Publishing sources for {% data variables.product.prodname_pages %} sites diff --git a/content/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/working-with-pre-receive-hooks.md b/content/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/working-with-pre-receive-hooks.md index 8fd606db96..7a511c014f 100644 --- a/content/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/working-with-pre-receive-hooks.md +++ b/content/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/working-with-pre-receive-hooks.md @@ -30,4 +30,4 @@ error: failed to push some refs to 'https://54.204.174.51/hodor/nope.git' ![Error message for failed pre-receive hook](/assets/images/help/pull_requests/pre-receive-hook-failed-error.png) -Your {% data variables.product.product_name %} site administrator can create and remove pre-receive hooks for your organization or repository, and may allow organization or repository administrators to enable or disable pre-receive hooks. For more information, see "[Using pre-receive hooks to enforce policy](/enterprise/{{ currentVersion }}/admin/guides/developer-workflow/using-pre-receive-hooks-to-enforce-policy)." +Your {% data variables.product.product_name %} site administrator can create and remove pre-receive hooks for your organization or repository, and may allow organization or repository administrators to enable or disable pre-receive hooks. For more information, see "[Using pre-receive hooks to enforce policy](/enterprise/admin/guides/developer-workflow/using-pre-receive-hooks-to-enforce-policy)." diff --git a/content/pull-requests/collaborating-with-pull-requests/working-with-forks/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility.md b/content/pull-requests/collaborating-with-pull-requests/working-with-forks/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility.md index 746627d43f..9ef3f23067 100644 --- a/content/pull-requests/collaborating-with-pull-requests/working-with-forks/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility.md +++ b/content/pull-requests/collaborating-with-pull-requests/working-with-forks/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility.md @@ -43,7 +43,7 @@ If a public repository is made private, its public forks are split off into a ne In other words, a public repository's forks will remain public in their own separate repository network even after the parent repository is made private. This allows the fork owners to continue to work and collaborate without interruption. If public forks were not moved into a separate network in this way, the owners of those forks would need to get the appropriate [access permissions](/articles/access-permissions-on-github) to pull changes from and submit pull requests to the (now private) parent repository—even though they didn't need those permissions before. {% ifversion ghes or ghae %} -If a public repository has anonymous Git read access enabled and the repository is made private, all of the repository's forks will lose anonymous Git read access and return to the default disabled setting. If a forked repository is made public, repository administrators can re-enable anonymous Git read access. For more information, see "[Enabling anonymous Git read access for a repository](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository)." +If a public repository has anonymous Git read access enabled and the repository is made private, all of the repository's forks will lose anonymous Git read access and return to the default disabled setting. If a forked repository is made public, repository administrators can re-enable anonymous Git read access. For more information, see "[Enabling anonymous Git read access for a repository](/enterprise/user/articles/enabling-anonymous-git-read-access-for-a-repository)." {% endif %} ### Deleting the private repository diff --git a/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches.md b/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches.md index d8ba4d90a6..41a80df54d 100644 --- a/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches.md +++ b/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches.md @@ -185,7 +185,7 @@ By default, {% data variables.product.product_name %} blocks force pushes on all Enabling force pushes will not override any other branch protection rules. For example, if a branch requires a linear commit history, you cannot force push merge commits to that branch. -{% ifversion ghes or ghae %}You cannot enable force pushes for a protected branch if a site administrator has blocked force pushes to all branches in your repository. For more information, see "[Blocking force pushes to repositories owned by a personal account or organization](/enterprise/{{ currentVersion }}/admin/developer-workflow/blocking-force-pushes-to-repositories-owned-by-a-user-account-or-organization)." +{% ifversion ghes or ghae %}You cannot enable force pushes for a protected branch if a site administrator has blocked force pushes to all branches in your repository. For more information, see "[Blocking force pushes to repositories owned by a personal account or organization](/enterprise/admin/developer-workflow/blocking-force-pushes-to-repositories-owned-by-a-user-account-or-organization)." If a site administrator has blocked force pushes to the default branch only, you can still enable force pushes for any other protected branch.{% endif %} diff --git a/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility.md b/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility.md index 3e7da4146c..711e4c8357 100644 --- a/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility.md +++ b/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility.md @@ -60,7 +60,7 @@ We recommend reviewing the following caveats before you change the visibility of {%- endif %} {%- ifversion ghes %} -* Anonymous Git read access is no longer available. For more information, see "[Enabling anonymous Git read access for a repository](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository)." +* Anonymous Git read access is no longer available. For more information, see "[Enabling anonymous Git read access for a repository](/enterprise/user/articles/enabling-anonymous-git-read-access-for-a-repository)." {%- endif %} {% ifversion ghes or ghec or ghae %} diff --git a/content/repositories/working-with-files/managing-large-files/about-large-files-on-github.md b/content/repositories/working-with-files/managing-large-files/about-large-files-on-github.md index 575108e57e..02fbcd36ad 100644 --- a/content/repositories/working-with-files/managing-large-files/about-large-files-on-github.md +++ b/content/repositories/working-with-files/managing-large-files/about-large-files-on-github.md @@ -40,7 +40,7 @@ shortTitle: Large files {% endnote %} -{% ifversion ghes %}By default, {% endif %}{% data variables.product.product_name %} blocks pushes that exceed {% data variables.large_files.max_github_size %}. {% ifversion ghes %}However, a site administrator can configure a different limit for {% data variables.product.product_location %}. For more information, see "[Setting Git push limits](/enterprise/{{ currentVersion }}/admin/guides/installation/setting-git-push-limits)."{% endif %} +{% ifversion ghes %}By default, {% endif %}{% data variables.product.product_name %} blocks pushes that exceed {% data variables.large_files.max_github_size %}. {% ifversion ghes %}However, a site administrator can configure a different limit for {% data variables.product.product_location %}. For more information, see "[Setting Git push limits](/enterprise/admin/guides/installation/setting-git-push-limits)."{% endif %} To track files beyond this limit, you must use {% data variables.large_files.product_name_long %} ({% data variables.large_files.product_name_short %}). For more information, see "[About {% data variables.large_files.product_name_long %}](/repositories/working-with-files/managing-large-files/about-git-large-file-storage)." diff --git a/content/repositories/working-with-files/managing-large-files/configuring-git-large-file-storage.md b/content/repositories/working-with-files/managing-large-files/configuring-git-large-file-storage.md index 57a8bd42c3..2a4187d8ce 100644 --- a/content/repositories/working-with-files/managing-large-files/configuring-git-large-file-storage.md +++ b/content/repositories/working-with-files/managing-large-files/configuring-git-large-file-storage.md @@ -21,7 +21,7 @@ If there are existing files in your repository that you'd like to use {% data va {% tip %} -**Note:** Before trying to push a large file to {% data variables.product.product_name %}, make sure that you've enabled {% data variables.large_files.product_name_short %} on your enterprise. For more information, see "[Configuring Git Large File Storage on GitHub Enterprise Server](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-git-large-file-storage-on-github-enterprise-server/)." +**Note:** Before trying to push a large file to {% data variables.product.product_name %}, make sure that you've enabled {% data variables.large_files.product_name_short %} on your enterprise. For more information, see "[Configuring Git Large File Storage on GitHub Enterprise Server](/enterprise/admin/guides/installation/configuring-git-large-file-storage-on-github-enterprise-server/)." {% endtip %} diff --git a/content/rest/overview/endpoints-available-for-github-apps.md b/content/rest/overview/endpoints-available-for-github-apps.md index ee73c0d87f..be7e0b568b 100644 --- a/content/rest/overview/endpoints-available-for-github-apps.md +++ b/content/rest/overview/endpoints-available-for-github-apps.md @@ -1,6 +1,7 @@ --- title: Endpoints available for GitHub Apps intro: Your app can make requests to the following REST endpoints. +permissions: You must use an installation access token to access endpoints using your {% data variables.product.prodname_github_app %}. For more information, see "[Authenticating with {% data variables.product.prodname_github_apps %}](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation)." redirect_from: - /v3/apps/available-endpoints - /rest/reference/endpoints-available-for-github-apps diff --git a/content/site-policy/privacy-policies/github-privacy-statement.md b/content/site-policy/privacy-policies/github-privacy-statement.md index f649e9062f..0471adc506 100644 --- a/content/site-policy/privacy-policies/github-privacy-statement.md +++ b/content/site-policy/privacy-policies/github-privacy-statement.md @@ -179,7 +179,7 @@ We retain and use your information as described in this Privacy Statement, but b If GitHub processes Personal Data other than your profile information, such as information about you GitHub receives from [third parties](/github/site-policy/github-privacy-statement#information-we-collect-from-third-parties), then you may, subject to applicable law, access, update, alter, delete, object to or restrict the processing of your Personal Data by contacting [GitHub Support](https://support.github.com/contact) or [GitHub Premium Support](https://enterprise.githubsupport.com/hc/en-us). -You can adjust the settings on your Account regarding the display of your Personal Data in private or public repositories or Personal Data processed in connection with Community Features (such as the GitHub Feed, the GitHub Globe, GitHub Explore, the GitHub Discussion Leaderboard) through [profile settings](https://github.com/settings/profile). +You can adjust the settings on your Account regarding the display of your Personal Data in private or public repositories or Personal Data processed in connection with Community Features (such as GitHub Feed, GitHub Sponsors, and GitHub Explore) through [profile settings](https://github.com/settings/profile). Additionally, if you are unable to access certain Personal Data we have via the means described above, you can request access by contacting us as described at the bottom of this privacy statement. diff --git a/content/support/contacting-github-support/providing-data-to-github-support.md b/content/support/contacting-github-support/providing-data-to-github-support.md index 287af110c4..c2966bf474 100644 --- a/content/support/contacting-github-support/providing-data-to-github-support.md +++ b/content/support/contacting-github-support/providing-data-to-github-support.md @@ -68,7 +68,7 @@ You can use this method if you don't have your SSH key readily available. You can use this method without signing into the {% data variables.enterprise.management_console %}. -Use the [ghe-diagnostics](/enterprise/{{ currentVersion }}/admin/guides/installation/command-line-utilities#ghe-diagnostics) command-line utility to retrieve the diagnostics for your instance. +Use the [ghe-diagnostics](/enterprise/admin/guides/installation/command-line-utilities#ghe-diagnostics) command-line utility to retrieve the diagnostics for your instance. ```shell $ ssh -p122 admin@hostname -- 'ghe-diagnostics' > diagnostics.txt diff --git a/data/features/dependabot-bulk-alerts.yml b/data/features/dependabot-bulk-alerts.yml new file mode 100644 index 0000000000..df64f29646 --- /dev/null +++ b/data/features/dependabot-bulk-alerts.yml @@ -0,0 +1,6 @@ +# Reference: Issue #6076 ability to dismiss or re-open multiple Dependabot alerts +versions: + fpt: '*' + ghec: '*' + ghes: '>3.5' + ghae: 'issue-6628' diff --git a/data/release-notes/enterprise-server/3-4/2.yml b/data/release-notes/enterprise-server/3-4/2.yml index f3a3aee274..e38ab7cd47 100644 --- a/data/release-notes/enterprise-server/3-4/2.yml +++ b/data/release-notes/enterprise-server/3-4/2.yml @@ -27,12 +27,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. - The {% data variables.product.prodname_registry %} npm registry no longer returns a time value in metadata responses. This was done to allow for substantial performance improvements. We continue to have all the data necessary to return a time value as part of the metadata response and will resume returning this value in the future once we have solved the existing performance issues. - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail. - - | - 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. deprecations: - heading: Deprecation of GitHub Enterprise Server 3.0 diff --git a/data/release-notes/enterprise-server/3-4/3.yml b/data/release-notes/enterprise-server/3-4/3.yml index 2ec92d6680..5c409fc4aa 100644 --- a/data/release-notes/enterprise-server/3-4/3.yml +++ b/data/release-notes/enterprise-server/3-4/3.yml @@ -33,9 +33,3 @@ 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. - The {% data variables.product.prodname_registry %} npm registry no longer returns a time value in metadata responses. This was done to allow for substantial performance improvements. We continue to have all the data necessary to return a time value as part of the metadata response and will resume returning this value in the future once we have solved the existing performance issues. - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail. - - | - 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. diff --git a/data/reusables/actions/ref-description.md b/data/reusables/actions/ref-description.md new file mode 100644 index 0000000000..470f425265 --- /dev/null +++ b/data/reusables/actions/ref-description.md @@ -0,0 +1 @@ +The branch or tag ref that triggered the workflow run. For workflows triggered by `push`, this is the branch or tag ref that was pushed. For workflows triggered by `pull_request`, this is the pull request merge branch. For workflows triggered by `release`, this is the release tag created. For other triggers, this is the branch or tag ref that triggered the workflow run. This is only set if a branch or tag is available for the event type. The ref given is fully-formed, meaning that for branches the format is `refs/heads/`, for pull requests it is `refs/pull//merge`, and for tags it is `refs/tags/`. For example, `refs/heads/feature-branch-1`. diff --git a/data/reusables/actions/supported-github-runners.md b/data/reusables/actions/supported-github-runners.md index 74c9c364c1..15a6e8b73b 100644 --- a/data/reusables/actions/supported-github-runners.md +++ b/data/reusables/actions/supported-github-runners.md @@ -63,10 +63,7 @@ macOS Monterey 12 macos-12 - - -macOS 12 is currently in public beta. - + diff --git a/data/reusables/classroom/reuse-assignment-link.md b/data/reusables/classroom/reuse-assignment-link.md index 73b7419440..00ef9154a9 100644 --- a/data/reusables/classroom/reuse-assignment-link.md +++ b/data/reusables/classroom/reuse-assignment-link.md @@ -1 +1 @@ -You can reuse an existing assignment in any other classroom you have admin access to, including classrooms in a different organization. For more information, see "[Reuse an assignment](/education/manage-coursework-with-github-classroom/teach-with-github-classroom/reuse-an-assignment)." \ No newline at end of file +You can reuse existing assignments in any other classroom you have admin access to, including classrooms in a different organization. For more information, see "[Reuse an assignment](/education/manage-coursework-with-github-classroom/teach-with-github-classroom/reuse-an-assignment)." \ No newline at end of file diff --git a/data/reusables/developer-site/limit_workflow_to_activity_types.md b/data/reusables/developer-site/limit_workflow_to_activity_types.md index 58e9db3306..652e1dcc27 100644 --- a/data/reusables/developer-site/limit_workflow_to_activity_types.md +++ b/data/reusables/developer-site/limit_workflow_to_activity_types.md @@ -1 +1 @@ -By default, all activity types trigger a workflow to run. You can limit your workflow runs to specific activity types using the `types` keyword. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/articles/workflow-syntax-for-github-actions#onevent_nametypes)." +By default, all activity types trigger workflows that run on this event. You can limit your workflow runs to specific activity types using the `types` keyword. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/articles/workflow-syntax-for-github-actions#onevent_nametypes)." diff --git a/data/reusables/enterprise_clustering/load_balancer_dns.md b/data/reusables/enterprise_clustering/load_balancer_dns.md index 6d94081ac3..c034dcc7a0 100644 --- a/data/reusables/enterprise_clustering/load_balancer_dns.md +++ b/data/reusables/enterprise_clustering/load_balancer_dns.md @@ -1 +1 @@ -DNS lookups for the {% data variables.product.prodname_ghe_server %} hostname should resolve to the load balancer. We recommend that you enable subdomain isolation. If subdomain isolation is enabled, an additional wildcard record (`*.HOSTNAME`) should also resolve to the load balancer. For more information, see "[Enabling subdomain isolation](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-subdomain-isolation/)." +DNS lookups for the {% data variables.product.prodname_ghe_server %} hostname should resolve to the load balancer. We recommend that you enable subdomain isolation. If subdomain isolation is enabled, an additional wildcard record (`*.HOSTNAME`) should also resolve to the load balancer. For more information, see "[Enabling subdomain isolation](/enterprise/admin/guides/installation/enabling-subdomain-isolation/)." diff --git a/data/reusables/enterprise_clustering/replacing-a-cluster-node-mark-offline.md b/data/reusables/enterprise_clustering/replacing-a-cluster-node-mark-offline.md index 042cb67e10..5e81d28832 100644 --- a/data/reusables/enterprise_clustering/replacing-a-cluster-node-mark-offline.md +++ b/data/reusables/enterprise_clustering/replacing-a-cluster-node-mark-offline.md @@ -1,4 +1,4 @@ -1. To mark the failed node offline, on any node, modify the [cluster configuration file](/enterprise/{{ currentVersion }}/admin/guides/clustering/initializing-the-cluster/#about-the-cluster-configuration-file) (`cluster.conf`) in the relevant node section to include the text `offline = true`. +1. To mark the failed node offline, on any node, modify the [cluster configuration file](/enterprise/admin/guides/clustering/initializing-the-cluster/#about-the-cluster-configuration-file) (`cluster.conf`) in the relevant node section to include the text `offline = true`. For example, this modified `cluster.conf` will mark the `ghe-data-node-3` node as offline: diff --git a/data/reusables/enterprise_clustering/replacing-a-cluster-node-need-three-nodes.md b/data/reusables/enterprise_clustering/replacing-a-cluster-node-need-three-nodes.md index 70825534bd..136bd91ee1 100644 --- a/data/reusables/enterprise_clustering/replacing-a-cluster-node-need-three-nodes.md +++ b/data/reusables/enterprise_clustering/replacing-a-cluster-node-need-three-nodes.md @@ -1 +1 @@ -1. If you're taking a node offline that has `git-server = true` set in cluster.conf, evacuate the node. For more information, see "[Evacuating a cluster node](/enterprise/{{ currentVersion }}/admin/clustering/evacuating-a-cluster-node)." +1. If you're taking a node offline that has `git-server = true` set in cluster.conf, evacuate the node. For more information, see "[Evacuating a cluster node](/enterprise/admin/clustering/evacuating-a-cluster-node)." diff --git a/data/reusables/enterprise_clustering/replacing-a-cluster-node-provision.md b/data/reusables/enterprise_clustering/replacing-a-cluster-node-provision.md index 53f9ecc20e..1f39fcdf1d 100644 --- a/data/reusables/enterprise_clustering/replacing-a-cluster-node-provision.md +++ b/data/reusables/enterprise_clustering/replacing-a-cluster-node-provision.md @@ -1 +1 @@ -1. [Provision and install {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/guides/installation/setting-up-a-github-enterprise-server-instance) with a unique hostname on the replacement node. +1. [Provision and install {% data variables.product.prodname_ghe_server %}](/enterprise/admin/guides/installation/setting-up-a-github-enterprise-server-instance) with a unique hostname on the replacement node. diff --git a/data/reusables/enterprise_enterprise_support/use_ghe_cluster_support_bundle.md b/data/reusables/enterprise_enterprise_support/use_ghe_cluster_support_bundle.md index 1ce0dbfddd..ba7e7209cc 100644 --- a/data/reusables/enterprise_enterprise_support/use_ghe_cluster_support_bundle.md +++ b/data/reusables/enterprise_enterprise_support/use_ghe_cluster_support_bundle.md @@ -1,5 +1,5 @@ {% note %} -**Note:** If you are using a Geo-replication configuration, or {% data variables.product.prodname_enterprise %} Clustering, you should use the `ghe-cluster-support-bundle` command to retrieve the support bundle. For more information, see "[Command-line utilities](/enterprise/{{ currentVersion }}/admin/guides/installation/command-line-utilities/#ghe-cluster-support-bundle)." +**Note:** If you are using a Geo-replication configuration, or {% data variables.product.prodname_enterprise %} Clustering, you should use the `ghe-cluster-support-bundle` command to retrieve the support bundle. For more information, see "[Command-line utilities](/enterprise/admin/guides/installation/command-line-utilities/#ghe-cluster-support-bundle)." {% endnote %} diff --git a/data/reusables/enterprise_installation/download-note.md b/data/reusables/enterprise_installation/download-note.md index 5914c3b575..7a891ad844 100644 --- a/data/reusables/enterprise_installation/download-note.md +++ b/data/reusables/enterprise_installation/download-note.md @@ -1,5 +1,5 @@ {% note %} -**Note:** If you've enabled automatic update checks, you don't need to download the upgrade package and can use the file that was automatically downloaded. For more information, see "[Enabling automatic update checks](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-automatic-update-checks/)." +**Note:** If you've enabled automatic update checks, you don't need to download the upgrade package and can use the file that was automatically downloaded. For more information, see "[Enabling automatic update checks](/enterprise/admin/guides/installation/enabling-automatic-update-checks/)." {% endnote %} diff --git a/data/reusables/enterprise_installation/hardware-considerations-all-platforms.md b/data/reusables/enterprise_installation/hardware-considerations-all-platforms.md index 46612c6d05..aa4ac2b3e6 100644 --- a/data/reusables/enterprise_installation/hardware-considerations-all-platforms.md +++ b/data/reusables/enterprise_installation/hardware-considerations-all-platforms.md @@ -20,7 +20,7 @@ To configure {% data variables.product.prodname_actions %}, you must provide ext {% endif %} -The available space on the root filesystem will be 50% of the total disk size. You can resize your instance's root disk by building a new instance or using an existing instance. For more information, see "[System overview](/enterprise/admin/guides/installation/system-overview#storage-architecture)" and "[Increasing storage capacity](/enterprise/{{ currentVersion }}/admin/guides/installation/increasing-storage-capacity)." +The available space on the root filesystem will be 50% of the total disk size. You can resize your instance's root disk by building a new instance or using an existing instance. For more information, see "[System overview](/enterprise/admin/guides/installation/system-overview#storage-architecture)" and "[Increasing storage capacity](/enterprise/admin/guides/installation/increasing-storage-capacity)." ### CPU and memory diff --git a/data/reusables/enterprise_installation/save-settings-in-web-based-mgmt-console.md b/data/reusables/enterprise_installation/save-settings-in-web-based-mgmt-console.md index 23ccf91ebf..cf0b18bf35 100644 --- a/data/reusables/enterprise_installation/save-settings-in-web-based-mgmt-console.md +++ b/data/reusables/enterprise_installation/save-settings-in-web-based-mgmt-console.md @@ -1 +1 @@ -3. In the [{% data variables.enterprise.management_console %}](/enterprise/{{ currentVersion }}/admin/guides/installation/accessing-the-management-console/), configure and save your desired settings. +3. In the [{% data variables.enterprise.management_console %}](/enterprise/admin/guides/installation/accessing-the-management-console/), configure and save your desired settings. diff --git a/data/reusables/enterprise_installation/warning-on-upgrading-physical-resources.md b/data/reusables/enterprise_installation/warning-on-upgrading-physical-resources.md index 55fa4dea6b..d5e1b215ef 100644 --- a/data/reusables/enterprise_installation/warning-on-upgrading-physical-resources.md +++ b/data/reusables/enterprise_installation/warning-on-upgrading-physical-resources.md @@ -1,5 +1,5 @@ {% warning %} -**Warning:** The process for allocating new system resources varies by virtualization platform and resource type. You should always configure the monitoring and alerting of key system resources. For more information, see "[Monitoring your {% data variables.product.prodname_ghe_server %} appliance](/enterprise/{{ currentVersion }}/admin/guides/installation/monitoring-your-github-enterprise-server-appliance/)." +**Warning:** The process for allocating new system resources varies by virtualization platform and resource type. You should always configure the monitoring and alerting of key system resources. For more information, see "[Monitoring your {% data variables.product.prodname_ghe_server %} appliance](/enterprise/admin/guides/installation/monitoring-your-github-enterprise-server-appliance/)." {% endwarning %} diff --git a/data/reusables/enterprise_management_console/test-domain-settings-failure.md b/data/reusables/enterprise_management_console/test-domain-settings-failure.md index b596544d3d..47d1bb55c1 100644 --- a/data/reusables/enterprise_management_console/test-domain-settings-failure.md +++ b/data/reusables/enterprise_management_console/test-domain-settings-failure.md @@ -1,2 +1,2 @@ -1. If you don't receive a green checkmark next to all entries, review your configuration for the setting that failed. For more information, see "[Configuring DNS nameservers](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-dns-nameservers/)." +1. If you don't receive a green checkmark next to all entries, review your configuration for the setting that failed. For more information, see "[Configuring DNS nameservers](/enterprise/admin/guides/installation/configuring-dns-nameservers/)." ![Table showing status of DNS and SSL configurations](/assets/images/enterprise/management-console/domain-dns-ssl-settings-check.png) diff --git a/data/reusables/enterprise_site_admin_settings/maintenance-mode-status.md b/data/reusables/enterprise_site_admin_settings/maintenance-mode-status.md index 1302317d59..45cc5aeab5 100644 --- a/data/reusables/enterprise_site_admin_settings/maintenance-mode-status.md +++ b/data/reusables/enterprise_site_admin_settings/maintenance-mode-status.md @@ -1,5 +1,5 @@ {% note %} -**Note:** When the appliance is in maintenance mode, the `https://HOSTNAME/status` URL will return status code `503` (Service Unavailable). For more information, see "[Enabling and scheduling maintenance mode](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-and-scheduling-maintenance-mode)." +**Note:** When the appliance is in maintenance mode, the `https://HOSTNAME/status` URL will return status code `503` (Service Unavailable). For more information, see "[Enabling and scheduling maintenance mode](/enterprise/admin/guides/installation/enabling-and-scheduling-maintenance-mode)." {% endnote %} diff --git a/data/reusables/enterprise_user_management/external_auth_disables_2fa.md b/data/reusables/enterprise_user_management/external_auth_disables_2fa.md index 6d7316352f..49eeb050a4 100644 --- a/data/reusables/enterprise_user_management/external_auth_disables_2fa.md +++ b/data/reusables/enterprise_user_management/external_auth_disables_2fa.md @@ -1 +1 @@ -When using SAML or CAS, two-factor authentication is not supported or managed on the {% data variables.product.prodname_ghe_server %} appliance, but may be supported by the external authentication provider. Two-factor authentication enforcement on organizations is not available. For more information about enforcing two-factor authentication on organizations, see "[Requiring two-factor authentication in your organization](/enterprise/{{ currentVersion }}/user/articles/requiring-two-factor-authentication-in-your-organization/)." +When using SAML or CAS, two-factor authentication is not supported or managed on the {% data variables.product.prodname_ghe_server %} appliance, but may be supported by the external authentication provider. Two-factor authentication enforcement on organizations is not available. For more information about enforcing two-factor authentication on organizations, see "[Requiring two-factor authentication in your organization](/enterprise/user/articles/requiring-two-factor-authentication-in-your-organization/)." diff --git a/data/reusables/enterprise_user_management/ldap-sync-nested-teams.md b/data/reusables/enterprise_user_management/ldap-sync-nested-teams.md index 3883c61f72..26a34ff14d 100644 --- a/data/reusables/enterprise_user_management/ldap-sync-nested-teams.md +++ b/data/reusables/enterprise_user_management/ldap-sync-nested-teams.md @@ -1,3 +1,3 @@ {% ifversion ghes %} -As part of its optimization configuration, LDAP Sync will not transfer your nested team structure. To create child and parent team relationships, you must manually recreate the nested team structure and sync it with the corresponding LDAP group. For more information, see "[Creating teams](/enterprise/{{ currentVersion }}/admin/guides/user-management/creating-teams/#creating-teams-with-ldap-sync-enabled)" +As part of its optimization configuration, LDAP Sync will not transfer your nested team structure. To create child and parent team relationships, you must manually recreate the nested team structure and sync it with the corresponding LDAP group. For more information, see "[Creating teams](/enterprise/admin/guides/user-management/creating-teams/#creating-teams-with-ldap-sync-enabled)" {% endif %} diff --git a/data/reusables/notifications/access_watching.md b/data/reusables/notifications/access_watching.md index 14e652ba15..3d25dc2a4d 100644 --- a/data/reusables/notifications/access_watching.md +++ b/data/reusables/notifications/access_watching.md @@ -1,2 +1,2 @@ -1. In the upper-right corner of any page, click {% octicon "bell" aria-label="The notifications bell" %}. If you've [disabled web notifications](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications) and you don't see the bell icon, you can navigate to . +1. In the upper-right corner of any page, click {% octicon "bell" aria-label="The notifications bell" %}. If you've [disabled web notifications](/enterprise/user/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications) and you don't see the bell icon, you can navigate to . ![Notification indicating any unread message](/assets/images/help/notifications/notifications_general_existence_indicator.png) diff --git a/data/reusables/secret-scanning/partner-secret-list-private-repo.md b/data/reusables/secret-scanning/partner-secret-list-private-repo.md index 88d6afb8fa..f50e6594b8 100644 --- a/data/reusables/secret-scanning/partner-secret-list-private-repo.md +++ b/data/reusables/secret-scanning/partner-secret-list-private-repo.md @@ -194,6 +194,8 @@ Proctorio | Proctorio Secret Key | proctorio_secret_key Pulumi | Pulumi Access Token | pulumi_access_token {%- ifversion fpt or ghec or ghes > 3.1 or ghae %} PyPI | PyPI API Token | pypi_api_token{% endif %} +{%- ifversion fpt or ghec or ghes > 3.5 or ghae-issue-7375 %} +redirect.pizza | redirect.pizza API Token | redirect_pizza_api_token{% endif %} {%- ifversion fpt or ghec or ghes > 3.1 or ghae %} RubyGems | RubyGems API Key | rubygems_api_key{% endif %} Samsara | Samsara API Token | samsara_api_token diff --git a/data/reusables/secret-scanning/partner-secret-list-public-repo.md b/data/reusables/secret-scanning/partner-secret-list-public-repo.md index 927b97e47c..5dddf2dc68 100644 --- a/data/reusables/secret-scanning/partner-secret-list-public-repo.md +++ b/data/reusables/secret-scanning/partner-secret-list-public-repo.md @@ -77,6 +77,7 @@ Proctorio | Proctorio Registration Key Proctorio | Proctorio Secret Key Pulumi | Pulumi Access Token PyPI | PyPI API Token +redirect.pizza | redirect.pizza API Token RubyGems | RubyGems API Key Samsara | Samsara API Token Samsara | Samsara OAuth Access Token diff --git a/data/reusables/secret-scanning/secret-list-private-push-protection.md b/data/reusables/secret-scanning/secret-list-private-push-protection.md index cc4412df2a..0c668dbc6e 100644 --- a/data/reusables/secret-scanning/secret-list-private-push-protection.md +++ b/data/reusables/secret-scanning/secret-list-private-push-protection.md @@ -60,6 +60,8 @@ PlanetScale | PlanetScale OAuth Token | planetscale_oauth_token PlanetScale | PlanetScale Service Token | planetscale_service_token Postman | Postman API Key | postman_api_key Proctorio | Proctorio Secret Key | proctorio_secret_key +{%- ifversion fpt or ghec or ghes > 3.5 or ghae-issue-7375 %} +redirect.pizza | redirect.pizza API Token | redirect_pizza_api_token{% endif %} Samsara | Samsara API Token | samsara_api_token Samsara | Samsara OAuth Access Token | samsara_oauth_access_token SendGrid | SendGrid API Key | sendgrid_api_key diff --git a/lib/read-json-file.js b/lib/read-json-file.js index c37fe2e73c..6f4ae86adc 100644 --- a/lib/read-json-file.js +++ b/lib/read-json-file.js @@ -31,6 +31,10 @@ export function readCompressedJsonFileFallback(xpath) { } } +// This is used to make sure the `readCompressedJsonFileFallbackLazily()` +// function isn't used with the same exact first argument more than once. +const globalCacheCounter = {} + // Wrapper on readCompressedJsonFileFallback that initially only checks // if the file exists but doesn't read the content till you call it. export function readCompressedJsonFileFallbackLazily(xpath) { @@ -57,7 +61,18 @@ export function readCompressedJsonFileFallbackLazily(xpath) { } } return () => { - if (!cache.has(xpath)) cache.set(xpath, readCompressedJsonFileFallback(xpath)) + if (!cache.has(xpath)) { + cache.set(xpath, readCompressedJsonFileFallback(xpath)) + if (globalCacheCounter[xpath]) { + console.warn( + "If this happens it's because the readCompressedJsonFileFallbackLazily " + + 'function has been called non-globally. Only use ' + + 'readCompressedJsonFileFallback once at module-level.' + ) + throw new Error(`Globally reading the same file more than once (${xpath})`) + } + globalCacheCounter[xpath] = 1 + } return cache.get(xpath) } } diff --git a/lib/render-content/create-processor.js b/lib/render-content/create-processor.js index 4adafd2169..1bb588a24a 100644 --- a/lib/render-content/create-processor.js +++ b/lib/render-content/create-processor.js @@ -25,6 +25,14 @@ import wrapInElement from './plugins/wrap-in-element.js' import doctocatLinkIcon from './doctocat-link-icon.js' const graphql = HighlightjsGraphql.definer +// The rewrite-asset-urls plugin is nice because it makes the `` +// tags use unique URLs so they can be aggressively cached in the +// CDN. But it might not always make sense to bother. For example, in +// some CI where you're rendering lots of content and don't care +// about aggressive CDN caching at all. E.g. Actions that do link checking +// on rendered HTML. +const DISABLE_REWRITE_ASSET_URLS = JSON.parse(process.env.DISABLE_REWRITE_ASSET_URLS || 'false') + export default function createProcessor(context) { return unified() .use(process.env.COMMONMARK ? markdownNext : markdown) @@ -46,7 +54,7 @@ export default function createProcessor(context) { .use(raw) .use(rewriteLegacyAssetPaths, context) .use(wrapInElement, { selector: 'ol > li img', wrapper: 'span.procedural-image-wrapper' }) - .use(rewriteImgSources) + .use(DISABLE_REWRITE_ASSET_URLS ? null : rewriteImgSources) .use(rewriteLocalLinks, { languageCode: context.currentLanguage, version: context.currentVersion, diff --git a/lib/rest/static/decorated/api.github.com.json b/lib/rest/static/decorated/api.github.com.json index 631fdfec97..81030d30c9 100644 --- a/lib/rest/static/decorated/api.github.com.json +++ b/lib/rest/static/decorated/api.github.com.json @@ -94815,25 +94815,25 @@ "type": "integer", "description": "Total minutes used on Windows runner machines." }, - "linux_4_core": { + "ubuntu_4_core": { "type": "integer", - "description": "Total minutes used on Linux 4 core runner machines." + "description": "Total minutes used on Ubuntu 4 core runner machines." }, - "linux_8_core": { + "ubuntu_8_core": { "type": "integer", - "description": "Total minutes used on Linux 8 core runner machines." + "description": "Total minutes used on Ubuntu 8 core runner machines." }, - "linux_16_core": { + "ubuntu_16_core": { "type": "integer", - "description": "Total minutes used on Linux 16 core runner machines." + "description": "Total minutes used on Ubuntu 16 core runner machines." }, - "linux_32_core": { + "ubuntu_32_core": { "type": "integer", - "description": "Total minutes used on Linux 32 core runner machines." + "description": "Total minutes used on Ubuntu 32 core runner machines." }, - "linux_64_core": { + "ubuntu_64_core": { "type": "integer", - "description": "Total minutes used on Linux 64 core runner machines." + "description": "Total minutes used on Ubuntu 64 core runner machines." }, "windows_4_core": { "type": "integer", @@ -95258,25 +95258,25 @@ "type": "integer", "description": "Total minutes used on Windows runner machines." }, - "linux_4_core": { + "ubuntu_4_core": { "type": "integer", - "description": "Total minutes used on Linux 4 core runner machines." + "description": "Total minutes used on Ubuntu 4 core runner machines." }, - "linux_8_core": { + "ubuntu_8_core": { "type": "integer", - "description": "Total minutes used on Linux 8 core runner machines." + "description": "Total minutes used on Ubuntu 8 core runner machines." }, - "linux_16_core": { + "ubuntu_16_core": { "type": "integer", - "description": "Total minutes used on Linux 16 core runner machines." + "description": "Total minutes used on Ubuntu 16 core runner machines." }, - "linux_32_core": { + "ubuntu_32_core": { "type": "integer", - "description": "Total minutes used on Linux 32 core runner machines." + "description": "Total minutes used on Ubuntu 32 core runner machines." }, - "linux_64_core": { + "ubuntu_64_core": { "type": "integer", - "description": "Total minutes used on Linux 64 core runner machines." + "description": "Total minutes used on Ubuntu 64 core runner machines." }, "windows_4_core": { "type": "integer", @@ -228204,25 +228204,25 @@ "type": "integer", "description": "Total minutes used on Windows runner machines." }, - "linux_4_core": { + "ubuntu_4_core": { "type": "integer", - "description": "Total minutes used on Linux 4 core runner machines." + "description": "Total minutes used on Ubuntu 4 core runner machines." }, - "linux_8_core": { + "ubuntu_8_core": { "type": "integer", - "description": "Total minutes used on Linux 8 core runner machines." + "description": "Total minutes used on Ubuntu 8 core runner machines." }, - "linux_16_core": { + "ubuntu_16_core": { "type": "integer", - "description": "Total minutes used on Linux 16 core runner machines." + "description": "Total minutes used on Ubuntu 16 core runner machines." }, - "linux_32_core": { + "ubuntu_32_core": { "type": "integer", - "description": "Total minutes used on Linux 32 core runner machines." + "description": "Total minutes used on Ubuntu 32 core runner machines." }, - "linux_64_core": { + "ubuntu_64_core": { "type": "integer", - "description": "Total minutes used on Linux 64 core runner machines." + "description": "Total minutes used on Ubuntu 64 core runner machines." }, "windows_4_core": { "type": "integer", @@ -359503,8 +359503,14 @@ "key": "default", "request": { "contentType": "application/json", - "description": "Example", + "description": "Update an existing webhook", "acceptHeader": "application/vnd.github.v3+json", + "bodyParameters": { + "url": "http://example.com/webhook", + "content_type": "json", + "insecure_ssl": "0", + "secret": "********" + }, "parameters": { "org": "ORG", "hook_id": "HOOK_ID" @@ -490336,7 +490342,29 @@ "subscribers_count": 42, "network_count": 0 } - } + }, + "push_protection_bypassed_by": { + "login": "monalisa", + "id": 2, + "node_id": "MDQ6VXNlcjI=", + "avatar_url": "https://alambic.github.com/avatars/u/2?", + "gravatar_id": "", + "url": "https://api.github.com/users/monalisa", + "html_url": "https://github.com/monalisa", + "followers_url": "https://api.github.com/users/monalisa/followers", + "following_url": "https://api.github.com/users/monalisa/following{/other_user}", + "gists_url": "https://api.github.com/users/monalisa/gists{/gist_id}", + "starred_url": "https://api.github.com/users/monalisa/starred{/owner}{/repo}", + "subscriptions_url": "https://api.github.com/users/monalisa/subscriptions", + "organizations_url": "https://api.github.com/users/monalisa/orgs", + "repos_url": "https://api.github.com/users/monalisa/repos", + "events_url": "https://api.github.com/users/monalisa/events{/privacy}", + "received_events_url": "https://api.github.com/users/monalisa/received_events", + "type": "User", + "site_admin": true + }, + "push_protection_bypassed": true, + "push_protection_bypassed_at": "2020-11-06T21:48:51Z" }, { "number": 1, @@ -490575,7 +490603,10 @@ "subscribers_count": 42, "network_count": 0 } - } + }, + "push_protection_bypassed_by": null, + "push_protection_bypassed": false, + "push_protection_bypassed_at": null } ], "schema": { @@ -492950,6 +492981,189 @@ "trees_url", "url" ] + }, + "push_protection_bypassed": { + "type": [ + "boolean", + "null" + ], + "description": "Whether push protection was bypassed for the detected secret." + }, + "push_protection_bypassed_by": { + "anyOf": [ + { + "type": "null" + }, + { + "title": "Simple User", + "description": "Simple User", + "type": "object", + "properties": { + "name": { + "type": [ + "string", + "null" + ] + }, + "email": { + "type": [ + "string", + "null" + ] + }, + "login": { + "type": "string", + "examples": [ + "octocat" + ] + }, + "id": { + "type": "integer", + "examples": [ + 1 + ] + }, + "node_id": { + "type": "string", + "examples": [ + "MDQ6VXNlcjE=" + ] + }, + "avatar_url": { + "type": "string", + "format": "uri", + "examples": [ + "https://github.com/images/error/octocat_happy.gif" + ] + }, + "gravatar_id": { + "type": [ + "string", + "null" + ], + "examples": [ + "41d064eb2195891e12d0413f63227ea7" + ] + }, + "url": { + "type": "string", + "format": "uri", + "examples": [ + "https://api.github.com/users/octocat" + ] + }, + "html_url": { + "type": "string", + "format": "uri", + "examples": [ + "https://github.com/octocat" + ] + }, + "followers_url": { + "type": "string", + "format": "uri", + "examples": [ + "https://api.github.com/users/octocat/followers" + ] + }, + "following_url": { + "type": "string", + "examples": [ + "https://api.github.com/users/octocat/following{/other_user}" + ] + }, + "gists_url": { + "type": "string", + "examples": [ + "https://api.github.com/users/octocat/gists{/gist_id}" + ] + }, + "starred_url": { + "type": "string", + "examples": [ + "https://api.github.com/users/octocat/starred{/owner}{/repo}" + ] + }, + "subscriptions_url": { + "type": "string", + "format": "uri", + "examples": [ + "https://api.github.com/users/octocat/subscriptions" + ] + }, + "organizations_url": { + "type": "string", + "format": "uri", + "examples": [ + "https://api.github.com/users/octocat/orgs" + ] + }, + "repos_url": { + "type": "string", + "format": "uri", + "examples": [ + "https://api.github.com/users/octocat/repos" + ] + }, + "events_url": { + "type": "string", + "examples": [ + "https://api.github.com/users/octocat/events{/privacy}" + ] + }, + "received_events_url": { + "type": "string", + "format": "uri", + "examples": [ + "https://api.github.com/users/octocat/received_events" + ] + }, + "type": { + "type": "string", + "examples": [ + "User" + ] + }, + "site_admin": { + "type": "boolean" + }, + "starred_at": { + "type": "string", + "examples": [ + "\"2020-07-09T00:17:55Z\"" + ] + } + }, + "required": [ + "avatar_url", + "events_url", + "followers_url", + "following_url", + "gists_url", + "gravatar_id", + "html_url", + "id", + "node_id", + "login", + "organizations_url", + "received_events_url", + "repos_url", + "site_admin", + "starred_url", + "subscriptions_url", + "type", + "url" + ] + } + ] + }, + "push_protection_bypassed_at": { + "type": [ + "string", + "null" + ], + "format": "date-time", + "description": "The time that push protection was bypassed in ISO 8601 format: `YYYY-MM-DDTHH:MM:SSZ`." } } } @@ -493342,7 +493556,29 @@ "subscribers_count": 42, "network_count": 0 } - } + }, + "push_protection_bypassed_by": { + "login": "monalisa", + "id": 2, + "node_id": "MDQ6VXNlcjI=", + "avatar_url": "https://alambic.github.com/avatars/u/2?", + "gravatar_id": "", + "url": "https://api.github.com/users/monalisa", + "html_url": "https://github.com/monalisa", + "followers_url": "https://api.github.com/users/monalisa/followers", + "following_url": "https://api.github.com/users/monalisa/following{/other_user}", + "gists_url": "https://api.github.com/users/monalisa/gists{/gist_id}", + "starred_url": "https://api.github.com/users/monalisa/starred{/owner}{/repo}", + "subscriptions_url": "https://api.github.com/users/monalisa/subscriptions", + "organizations_url": "https://api.github.com/users/monalisa/orgs", + "repos_url": "https://api.github.com/users/monalisa/repos", + "events_url": "https://api.github.com/users/monalisa/events{/privacy}", + "received_events_url": "https://api.github.com/users/monalisa/received_events", + "type": "User", + "site_admin": true + }, + "push_protection_bypassed": true, + "push_protection_bypassed_at": "2020-11-06T21:48:51Z" }, { "number": 1, @@ -493581,7 +493817,10 @@ "subscribers_count": 42, "network_count": 0 } - } + }, + "push_protection_bypassed_by": null, + "push_protection_bypassed": false, + "push_protection_bypassed_at": null } ], "schema": { @@ -495956,6 +496195,189 @@ "trees_url", "url" ] + }, + "push_protection_bypassed": { + "type": [ + "boolean", + "null" + ], + "description": "Whether push protection was bypassed for the detected secret." + }, + "push_protection_bypassed_by": { + "anyOf": [ + { + "type": "null" + }, + { + "title": "Simple User", + "description": "Simple User", + "type": "object", + "properties": { + "name": { + "type": [ + "string", + "null" + ] + }, + "email": { + "type": [ + "string", + "null" + ] + }, + "login": { + "type": "string", + "examples": [ + "octocat" + ] + }, + "id": { + "type": "integer", + "examples": [ + 1 + ] + }, + "node_id": { + "type": "string", + "examples": [ + "MDQ6VXNlcjE=" + ] + }, + "avatar_url": { + "type": "string", + "format": "uri", + "examples": [ + "https://github.com/images/error/octocat_happy.gif" + ] + }, + "gravatar_id": { + "type": [ + "string", + "null" + ], + "examples": [ + "41d064eb2195891e12d0413f63227ea7" + ] + }, + "url": { + "type": "string", + "format": "uri", + "examples": [ + "https://api.github.com/users/octocat" + ] + }, + "html_url": { + "type": "string", + "format": "uri", + "examples": [ + "https://github.com/octocat" + ] + }, + "followers_url": { + "type": "string", + "format": "uri", + "examples": [ + "https://api.github.com/users/octocat/followers" + ] + }, + "following_url": { + "type": "string", + "examples": [ + "https://api.github.com/users/octocat/following{/other_user}" + ] + }, + "gists_url": { + "type": "string", + "examples": [ + "https://api.github.com/users/octocat/gists{/gist_id}" + ] + }, + "starred_url": { + "type": "string", + "examples": [ + "https://api.github.com/users/octocat/starred{/owner}{/repo}" + ] + }, + "subscriptions_url": { + "type": "string", + "format": "uri", + "examples": [ + "https://api.github.com/users/octocat/subscriptions" + ] + }, + "organizations_url": { + "type": "string", + "format": "uri", + "examples": [ + "https://api.github.com/users/octocat/orgs" + ] + }, + "repos_url": { + "type": "string", + "format": "uri", + "examples": [ + "https://api.github.com/users/octocat/repos" + ] + }, + "events_url": { + "type": "string", + "examples": [ + "https://api.github.com/users/octocat/events{/privacy}" + ] + }, + "received_events_url": { + "type": "string", + "format": "uri", + "examples": [ + "https://api.github.com/users/octocat/received_events" + ] + }, + "type": { + "type": "string", + "examples": [ + "User" + ] + }, + "site_admin": { + "type": "boolean" + }, + "starred_at": { + "type": "string", + "examples": [ + "\"2020-07-09T00:17:55Z\"" + ] + } + }, + "required": [ + "avatar_url", + "events_url", + "followers_url", + "following_url", + "gists_url", + "gravatar_id", + "html_url", + "id", + "node_id", + "login", + "organizations_url", + "received_events_url", + "repos_url", + "site_admin", + "starred_url", + "subscriptions_url", + "type", + "url" + ] + } + ] + }, + "push_protection_bypassed_at": { + "type": [ + "string", + "null" + ], + "format": "date-time", + "description": "The time that push protection was bypassed in ISO 8601 format: `YYYY-MM-DDTHH:MM:SSZ`." } } } @@ -496133,7 +496555,29 @@ }, "secret_type": "adafruit_io_key", "secret_type_display_name": "Adafruit IO Key", - "secret": "aio_XXXXXXXXXXXXXXXXXXXXXXXXXXXX" + "secret": "aio_XXXXXXXXXXXXXXXXXXXXXXXXXXXX", + "push_protection_bypassed_by": { + "login": "monalisa", + "id": 2, + "node_id": "MDQ6VXNlcjI=", + "avatar_url": "https://alambic.github.com/avatars/u/2?", + "gravatar_id": "", + "url": "https://api.github.com/users/monalisa", + "html_url": "https://github.com/monalisa", + "followers_url": "https://api.github.com/users/monalisa/followers", + "following_url": "https://api.github.com/users/monalisa/following{/other_user}", + "gists_url": "https://api.github.com/users/monalisa/gists{/gist_id}", + "starred_url": "https://api.github.com/users/monalisa/starred{/owner}{/repo}", + "subscriptions_url": "https://api.github.com/users/monalisa/subscriptions", + "organizations_url": "https://api.github.com/users/monalisa/orgs", + "repos_url": "https://api.github.com/users/monalisa/repos", + "events_url": "https://api.github.com/users/monalisa/events{/privacy}", + "received_events_url": "https://api.github.com/users/monalisa/received_events", + "type": "User", + "site_admin": true + }, + "push_protection_bypassed": true, + "push_protection_bypassed_at": "2020-11-06T21:48:51Z" }, { "number": 1, @@ -496147,7 +496591,10 @@ "resolved_by": null, "secret_type": "mailchimp_api_key", "secret_type_display_name": "Mailchimp API Key", - "secret": "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX-us2" + "secret": "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX-us2", + "push_protection_bypassed_by": null, + "push_protection_bypassed": false, + "push_protection_bypassed_at": null } ], "schema": { @@ -496398,6 +496845,189 @@ "secret": { "type": "string", "description": "The secret that was detected." + }, + "push_protection_bypassed": { + "type": [ + "boolean", + "null" + ], + "description": "Whether push protection was bypassed for the detected secret." + }, + "push_protection_bypassed_by": { + "anyOf": [ + { + "type": "null" + }, + { + "title": "Simple User", + "description": "Simple User", + "type": "object", + "properties": { + "name": { + "type": [ + "string", + "null" + ] + }, + "email": { + "type": [ + "string", + "null" + ] + }, + "login": { + "type": "string", + "examples": [ + "octocat" + ] + }, + "id": { + "type": "integer", + "examples": [ + 1 + ] + }, + "node_id": { + "type": "string", + "examples": [ + "MDQ6VXNlcjE=" + ] + }, + "avatar_url": { + "type": "string", + "format": "uri", + "examples": [ + "https://github.com/images/error/octocat_happy.gif" + ] + }, + "gravatar_id": { + "type": [ + "string", + "null" + ], + "examples": [ + "41d064eb2195891e12d0413f63227ea7" + ] + }, + "url": { + "type": "string", + "format": "uri", + "examples": [ + "https://api.github.com/users/octocat" + ] + }, + "html_url": { + "type": "string", + "format": "uri", + "examples": [ + "https://github.com/octocat" + ] + }, + "followers_url": { + "type": "string", + "format": "uri", + "examples": [ + "https://api.github.com/users/octocat/followers" + ] + }, + "following_url": { + "type": "string", + "examples": [ + "https://api.github.com/users/octocat/following{/other_user}" + ] + }, + "gists_url": { + "type": "string", + "examples": [ + "https://api.github.com/users/octocat/gists{/gist_id}" + ] + }, + "starred_url": { + "type": "string", + "examples": [ + "https://api.github.com/users/octocat/starred{/owner}{/repo}" + ] + }, + "subscriptions_url": { + "type": "string", + "format": "uri", + "examples": [ + "https://api.github.com/users/octocat/subscriptions" + ] + }, + "organizations_url": { + "type": "string", + "format": "uri", + "examples": [ + "https://api.github.com/users/octocat/orgs" + ] + }, + "repos_url": { + "type": "string", + "format": "uri", + "examples": [ + "https://api.github.com/users/octocat/repos" + ] + }, + "events_url": { + "type": "string", + "examples": [ + "https://api.github.com/users/octocat/events{/privacy}" + ] + }, + "received_events_url": { + "type": "string", + "format": "uri", + "examples": [ + "https://api.github.com/users/octocat/received_events" + ] + }, + "type": { + "type": "string", + "examples": [ + "User" + ] + }, + "site_admin": { + "type": "boolean" + }, + "starred_at": { + "type": "string", + "examples": [ + "\"2020-07-09T00:17:55Z\"" + ] + } + }, + "required": [ + "avatar_url", + "events_url", + "followers_url", + "following_url", + "gists_url", + "gravatar_id", + "html_url", + "id", + "node_id", + "login", + "organizations_url", + "received_events_url", + "repos_url", + "site_admin", + "starred_url", + "subscriptions_url", + "type", + "url" + ] + } + ] + }, + "push_protection_bypassed_at": { + "type": [ + "string", + "null" + ], + "format": "date-time", + "description": "The time that push protection was bypassed in ISO 8601 format: `YYYY-MM-DDTHH:MM:SSZ`." } } } @@ -496490,7 +497120,10 @@ "resolved_by": null, "secret_type": "mailchimp_api_key", "secret_type_display_name": "Mailchimp API Key", - "secret": "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX-us2" + "secret": "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX-us2", + "push_protection_bypassed_by": null, + "push_protection_bypassed": false, + "push_protection_bypassed_at": null }, "schema": { "type": "object", @@ -496738,6 +497371,189 @@ "secret": { "type": "string", "description": "The secret that was detected." + }, + "push_protection_bypassed": { + "type": [ + "boolean", + "null" + ], + "description": "Whether push protection was bypassed for the detected secret." + }, + "push_protection_bypassed_by": { + "anyOf": [ + { + "type": "null" + }, + { + "title": "Simple User", + "description": "Simple User", + "type": "object", + "properties": { + "name": { + "type": [ + "string", + "null" + ] + }, + "email": { + "type": [ + "string", + "null" + ] + }, + "login": { + "type": "string", + "examples": [ + "octocat" + ] + }, + "id": { + "type": "integer", + "examples": [ + 1 + ] + }, + "node_id": { + "type": "string", + "examples": [ + "MDQ6VXNlcjE=" + ] + }, + "avatar_url": { + "type": "string", + "format": "uri", + "examples": [ + "https://github.com/images/error/octocat_happy.gif" + ] + }, + "gravatar_id": { + "type": [ + "string", + "null" + ], + "examples": [ + "41d064eb2195891e12d0413f63227ea7" + ] + }, + "url": { + "type": "string", + "format": "uri", + "examples": [ + "https://api.github.com/users/octocat" + ] + }, + "html_url": { + "type": "string", + "format": "uri", + "examples": [ + "https://github.com/octocat" + ] + }, + "followers_url": { + "type": "string", + "format": "uri", + "examples": [ + "https://api.github.com/users/octocat/followers" + ] + }, + "following_url": { + "type": "string", + "examples": [ + "https://api.github.com/users/octocat/following{/other_user}" + ] + }, + "gists_url": { + "type": "string", + "examples": [ + "https://api.github.com/users/octocat/gists{/gist_id}" + ] + }, + "starred_url": { + "type": "string", + "examples": [ + "https://api.github.com/users/octocat/starred{/owner}{/repo}" + ] + }, + "subscriptions_url": { + "type": "string", + "format": "uri", + "examples": [ + "https://api.github.com/users/octocat/subscriptions" + ] + }, + "organizations_url": { + "type": "string", + "format": "uri", + "examples": [ + "https://api.github.com/users/octocat/orgs" + ] + }, + "repos_url": { + "type": "string", + "format": "uri", + "examples": [ + "https://api.github.com/users/octocat/repos" + ] + }, + "events_url": { + "type": "string", + "examples": [ + "https://api.github.com/users/octocat/events{/privacy}" + ] + }, + "received_events_url": { + "type": "string", + "format": "uri", + "examples": [ + "https://api.github.com/users/octocat/received_events" + ] + }, + "type": { + "type": "string", + "examples": [ + "User" + ] + }, + "site_admin": { + "type": "boolean" + }, + "starred_at": { + "type": "string", + "examples": [ + "\"2020-07-09T00:17:55Z\"" + ] + } + }, + "required": [ + "avatar_url", + "events_url", + "followers_url", + "following_url", + "gists_url", + "gravatar_id", + "html_url", + "id", + "node_id", + "login", + "organizations_url", + "received_events_url", + "repos_url", + "site_admin", + "starred_url", + "subscriptions_url", + "type", + "url" + ] + } + ] + }, + "push_protection_bypassed_at": { + "type": [ + "string", + "null" + ], + "format": "date-time", + "description": "The time that push protection was bypassed in ISO 8601 format: `YYYY-MM-DDTHH:MM:SSZ`." } } } @@ -496892,7 +497708,10 @@ }, "secret_type": "mailchimp_api_key", "secret_type_display_name": "Mailchimp API Key", - "secret": "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX-us2" + "secret": "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX-us2", + "push_protection_bypassed": false, + "push_protection_bypassed_by": null, + "push_protection_bypassed_at": null }, "schema": { "type": "object", @@ -497140,6 +497959,189 @@ "secret": { "type": "string", "description": "The secret that was detected." + }, + "push_protection_bypassed": { + "type": [ + "boolean", + "null" + ], + "description": "Whether push protection was bypassed for the detected secret." + }, + "push_protection_bypassed_by": { + "anyOf": [ + { + "type": "null" + }, + { + "title": "Simple User", + "description": "Simple User", + "type": "object", + "properties": { + "name": { + "type": [ + "string", + "null" + ] + }, + "email": { + "type": [ + "string", + "null" + ] + }, + "login": { + "type": "string", + "examples": [ + "octocat" + ] + }, + "id": { + "type": "integer", + "examples": [ + 1 + ] + }, + "node_id": { + "type": "string", + "examples": [ + "MDQ6VXNlcjE=" + ] + }, + "avatar_url": { + "type": "string", + "format": "uri", + "examples": [ + "https://github.com/images/error/octocat_happy.gif" + ] + }, + "gravatar_id": { + "type": [ + "string", + "null" + ], + "examples": [ + "41d064eb2195891e12d0413f63227ea7" + ] + }, + "url": { + "type": "string", + "format": "uri", + "examples": [ + "https://api.github.com/users/octocat" + ] + }, + "html_url": { + "type": "string", + "format": "uri", + "examples": [ + "https://github.com/octocat" + ] + }, + "followers_url": { + "type": "string", + "format": "uri", + "examples": [ + "https://api.github.com/users/octocat/followers" + ] + }, + "following_url": { + "type": "string", + "examples": [ + "https://api.github.com/users/octocat/following{/other_user}" + ] + }, + "gists_url": { + "type": "string", + "examples": [ + "https://api.github.com/users/octocat/gists{/gist_id}" + ] + }, + "starred_url": { + "type": "string", + "examples": [ + "https://api.github.com/users/octocat/starred{/owner}{/repo}" + ] + }, + "subscriptions_url": { + "type": "string", + "format": "uri", + "examples": [ + "https://api.github.com/users/octocat/subscriptions" + ] + }, + "organizations_url": { + "type": "string", + "format": "uri", + "examples": [ + "https://api.github.com/users/octocat/orgs" + ] + }, + "repos_url": { + "type": "string", + "format": "uri", + "examples": [ + "https://api.github.com/users/octocat/repos" + ] + }, + "events_url": { + "type": "string", + "examples": [ + "https://api.github.com/users/octocat/events{/privacy}" + ] + }, + "received_events_url": { + "type": "string", + "format": "uri", + "examples": [ + "https://api.github.com/users/octocat/received_events" + ] + }, + "type": { + "type": "string", + "examples": [ + "User" + ] + }, + "site_admin": { + "type": "boolean" + }, + "starred_at": { + "type": "string", + "examples": [ + "\"2020-07-09T00:17:55Z\"" + ] + } + }, + "required": [ + "avatar_url", + "events_url", + "followers_url", + "following_url", + "gists_url", + "gravatar_id", + "html_url", + "id", + "node_id", + "login", + "organizations_url", + "received_events_url", + "repos_url", + "site_admin", + "starred_url", + "subscriptions_url", + "type", + "url" + ] + } + ] + }, + "push_protection_bypassed_at": { + "type": [ + "string", + "null" + ], + "format": "date-time", + "description": "The time that push protection was bypassed in ISO 8601 format: `YYYY-MM-DDTHH:MM:SSZ`." } } } diff --git a/lib/rest/static/decorated/ghes-3.1.json b/lib/rest/static/decorated/ghes-3.1.json index c4883b8a94..f965b0fb7c 100644 --- a/lib/rest/static/decorated/ghes-3.1.json +++ b/lib/rest/static/decorated/ghes-3.1.json @@ -271066,8 +271066,14 @@ "key": "default", "request": { "contentType": "application/json", - "description": "Example", + "description": "Update an existing webhook", "acceptHeader": "application/vnd.github.v3+json", + "bodyParameters": { + "url": "http://example.com/webhook", + "content_type": "json", + "insecure_ssl": "0", + "secret": "********" + }, "parameters": { "org": "ORG", "hook_id": "HOOK_ID" @@ -382376,6 +382382,7 @@ "created_at": "2020-11-06T18:48:51Z", "url": "https://api.github.com/repos/owner/private-repo/secret-scanning/alerts/2", "html_url": "https://github.com/owner/private-repo/security/secret-scanning/2", + "locations_url": "https://api.github.com/repos/owner/private-repo/secret-scanning/alerts/2/locations", "state": "resolved", "resolution": "false_positive", "resolved_at": "2020-11-07T02:47:13Z", @@ -382400,6 +382407,7 @@ "site_admin": true }, "secret_type": "adafruit_io_key", + "secret_type_display_name": "Adafruit IO Key", "secret": "aio_XXXXXXXXXXXXXXXXXXXXXXXXXXXX" }, { @@ -382407,11 +382415,13 @@ "created_at": "2020-11-06T18:18:30Z", "url": "https://api.github.com/repos/owner/repo/secret-scanning/alerts/1", "html_url": "https://github.com/owner/repo/security/secret-scanning/1", + "locations_url": "https://api.github.com/repos/owner/private-repo/secret-scanning/alerts/1/locations", "state": "open", "resolution": null, "resolved_at": null, "resolved_by": null, "secret_type": "mailchimp_api_key", + "secret_type_display_name": "Mailchimp API Key", "secret": "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX-us2" } ], diff --git a/lib/rest/static/decorated/ghes-3.2.json b/lib/rest/static/decorated/ghes-3.2.json index 2117790c26..30f4c6973a 100644 --- a/lib/rest/static/decorated/ghes-3.2.json +++ b/lib/rest/static/decorated/ghes-3.2.json @@ -277039,8 +277039,14 @@ "key": "default", "request": { "contentType": "application/json", - "description": "Example", + "description": "Update an existing webhook", "acceptHeader": "application/vnd.github.v3+json", + "bodyParameters": { + "url": "http://example.com/webhook", + "content_type": "json", + "insecure_ssl": "0", + "secret": "********" + }, "parameters": { "org": "ORG", "hook_id": "HOOK_ID" @@ -390873,6 +390879,7 @@ "created_at": "2020-11-06T18:48:51Z", "url": "https://api.github.com/repos/owner/private-repo/secret-scanning/alerts/2", "html_url": "https://github.com/owner/private-repo/security/secret-scanning/2", + "locations_url": "https://api.github.com/repos/owner/private-repo/secret-scanning/alerts/2/locations", "state": "resolved", "resolution": "false_positive", "resolved_at": "2020-11-07T02:47:13Z", @@ -390897,6 +390904,7 @@ "site_admin": true }, "secret_type": "adafruit_io_key", + "secret_type_display_name": "Adafruit IO Key", "secret": "aio_XXXXXXXXXXXXXXXXXXXXXXXXXXXX" }, { @@ -390904,11 +390912,13 @@ "created_at": "2020-11-06T18:18:30Z", "url": "https://api.github.com/repos/owner/repo/secret-scanning/alerts/1", "html_url": "https://github.com/owner/repo/security/secret-scanning/1", + "locations_url": "https://api.github.com/repos/owner/private-repo/secret-scanning/alerts/1/locations", "state": "open", "resolution": null, "resolved_at": null, "resolved_by": null, "secret_type": "mailchimp_api_key", + "secret_type_display_name": "Mailchimp API Key", "secret": "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX-us2" } ], diff --git a/lib/rest/static/decorated/ghes-3.3.json b/lib/rest/static/decorated/ghes-3.3.json index 7c28765e3d..9b9114999b 100644 --- a/lib/rest/static/decorated/ghes-3.3.json +++ b/lib/rest/static/decorated/ghes-3.3.json @@ -277985,8 +277985,14 @@ "key": "default", "request": { "contentType": "application/json", - "description": "Example", + "description": "Update an existing webhook", "acceptHeader": "application/vnd.github.v3+json", + "bodyParameters": { + "url": "http://example.com/webhook", + "content_type": "json", + "insecure_ssl": "0", + "secret": "********" + }, "parameters": { "org": "ORG", "hook_id": "HOOK_ID" @@ -386576,6 +386582,7 @@ "created_at": "2020-11-06T18:48:51Z", "url": "https://api.github.com/repos/owner/private-repo/secret-scanning/alerts/2", "html_url": "https://github.com/owner/private-repo/security/secret-scanning/2", + "locations_url": "https://api.github.com/repos/owner/private-repo/secret-scanning/alerts/2/locations", "state": "resolved", "resolution": "false_positive", "resolved_at": "2020-11-07T02:47:13Z", @@ -386600,6 +386607,7 @@ "site_admin": true }, "secret_type": "adafruit_io_key", + "secret_type_display_name": "Adafruit IO Key", "secret": "aio_XXXXXXXXXXXXXXXXXXXXXXXXXXXX", "repository": { "id": 1296269, @@ -386832,11 +386840,13 @@ "created_at": "2020-11-06T18:18:30Z", "url": "https://api.github.com/repos/owner/repo/secret-scanning/alerts/1", "html_url": "https://github.com/owner/repo/security/secret-scanning/1", + "locations_url": "https://api.github.com/repos/owner/private-repo/secret-scanning/alerts/1/locations", "state": "open", "resolution": null, "resolved_at": null, "resolved_by": null, "secret_type": "mailchimp_api_key", + "secret_type_display_name": "Mailchimp API Key", "secret": "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX-us2", "repository": { "id": 1296269, @@ -387081,6 +387091,19 @@ "format": "date-time", "readOnly": true }, + "updated_at": { + "anyOf": [ + { + "type": "null" + }, + { + "type": "string", + "description": "The time that the alert was last updated in ISO 8601 format: `YYYY-MM-DDTHH:MM:SSZ`.", + "format": "date-time", + "readOnly": true + } + ] + }, "url": { "type": "string", "description": "The REST API URL of the alert resource.", @@ -389529,6 +389552,7 @@ "created_at": "2020-11-06T18:48:51Z", "url": "https://api.github.com/repos/owner/private-repo/secret-scanning/alerts/2", "html_url": "https://github.com/owner/private-repo/security/secret-scanning/2", + "locations_url": "https://api.github.com/repos/owner/private-repo/secret-scanning/alerts/2/locations", "state": "resolved", "resolution": "false_positive", "resolved_at": "2020-11-07T02:47:13Z", @@ -389553,6 +389577,7 @@ "site_admin": true }, "secret_type": "adafruit_io_key", + "secret_type_display_name": "Adafruit IO Key", "secret": "aio_XXXXXXXXXXXXXXXXXXXXXXXXXXXX" }, { @@ -389560,11 +389585,13 @@ "created_at": "2020-11-06T18:18:30Z", "url": "https://api.github.com/repos/owner/repo/secret-scanning/alerts/1", "html_url": "https://github.com/owner/repo/security/secret-scanning/1", + "locations_url": "https://api.github.com/repos/owner/private-repo/secret-scanning/alerts/1/locations", "state": "open", "resolution": null, "resolved_at": null, "resolved_by": null, "secret_type": "mailchimp_api_key", + "secret_type_display_name": "Mailchimp API Key", "secret": "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX-us2" } ], diff --git a/lib/rest/static/decorated/ghes-3.4.json b/lib/rest/static/decorated/ghes-3.4.json index f38da448e7..793c65e404 100644 --- a/lib/rest/static/decorated/ghes-3.4.json +++ b/lib/rest/static/decorated/ghes-3.4.json @@ -297870,8 +297870,14 @@ "key": "default", "request": { "contentType": "application/json", - "description": "Example", + "description": "Update an existing webhook", "acceptHeader": "application/vnd.github.v3+json", + "bodyParameters": { + "url": "http://example.com/webhook", + "content_type": "json", + "insecure_ssl": "0", + "secret": "********" + }, "parameters": { "org": "ORG", "hook_id": "HOOK_ID" @@ -406620,6 +406626,7 @@ "created_at": "2020-11-06T18:48:51Z", "url": "https://api.github.com/repos/owner/private-repo/secret-scanning/alerts/2", "html_url": "https://github.com/owner/private-repo/security/secret-scanning/2", + "locations_url": "https://api.github.com/repos/owner/private-repo/secret-scanning/alerts/2/locations", "state": "resolved", "resolution": "false_positive", "resolved_at": "2020-11-07T02:47:13Z", @@ -406644,6 +406651,7 @@ "site_admin": true }, "secret_type": "adafruit_io_key", + "secret_type_display_name": "Adafruit IO Key", "secret": "aio_XXXXXXXXXXXXXXXXXXXXXXXXXXXX", "repository": { "id": 1296269, @@ -406876,11 +406884,13 @@ "created_at": "2020-11-06T18:18:30Z", "url": "https://api.github.com/repos/owner/repo/secret-scanning/alerts/1", "html_url": "https://github.com/owner/repo/security/secret-scanning/1", + "locations_url": "https://api.github.com/repos/owner/private-repo/secret-scanning/alerts/1/locations", "state": "open", "resolution": null, "resolved_at": null, "resolved_by": null, "secret_type": "mailchimp_api_key", + "secret_type_display_name": "Mailchimp API Key", "secret": "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX-us2", "repository": { "id": 1296269, @@ -407125,6 +407135,19 @@ "format": "date-time", "readOnly": true }, + "updated_at": { + "anyOf": [ + { + "type": "null" + }, + { + "type": "string", + "description": "The time that the alert was last updated in ISO 8601 format: `YYYY-MM-DDTHH:MM:SSZ`.", + "format": "date-time", + "readOnly": true + } + ] + }, "url": { "type": "string", "description": "The REST API URL of the alert resource.", @@ -409563,6 +409586,7 @@ "created_at": "2020-11-06T18:48:51Z", "url": "https://api.github.com/repos/owner/private-repo/secret-scanning/alerts/2", "html_url": "https://github.com/owner/private-repo/security/secret-scanning/2", + "locations_url": "https://api.github.com/repos/owner/private-repo/secret-scanning/alerts/2/locations", "state": "resolved", "resolution": "false_positive", "resolved_at": "2020-11-07T02:47:13Z", @@ -409587,6 +409611,7 @@ "site_admin": true }, "secret_type": "adafruit_io_key", + "secret_type_display_name": "Adafruit IO Key", "secret": "aio_XXXXXXXXXXXXXXXXXXXXXXXXXXXX", "repository": { "id": 1296269, @@ -409819,11 +409844,13 @@ "created_at": "2020-11-06T18:18:30Z", "url": "https://api.github.com/repos/owner/repo/secret-scanning/alerts/1", "html_url": "https://github.com/owner/repo/security/secret-scanning/1", + "locations_url": "https://api.github.com/repos/owner/private-repo/secret-scanning/alerts/1/locations", "state": "open", "resolution": null, "resolved_at": null, "resolved_by": null, "secret_type": "mailchimp_api_key", + "secret_type_display_name": "Mailchimp API Key", "secret": "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX-us2", "repository": { "id": 1296269, @@ -410068,6 +410095,19 @@ "format": "date-time", "readOnly": true }, + "updated_at": { + "anyOf": [ + { + "type": "null" + }, + { + "type": "string", + "description": "The time that the alert was last updated in ISO 8601 format: `YYYY-MM-DDTHH:MM:SSZ`.", + "format": "date-time", + "readOnly": true + } + ] + }, "url": { "type": "string", "description": "The REST API URL of the alert resource.", @@ -412516,6 +412556,7 @@ "created_at": "2020-11-06T18:48:51Z", "url": "https://api.github.com/repos/owner/private-repo/secret-scanning/alerts/2", "html_url": "https://github.com/owner/private-repo/security/secret-scanning/2", + "locations_url": "https://api.github.com/repos/owner/private-repo/secret-scanning/alerts/2/locations", "state": "resolved", "resolution": "false_positive", "resolved_at": "2020-11-07T02:47:13Z", @@ -412540,6 +412581,7 @@ "site_admin": true }, "secret_type": "adafruit_io_key", + "secret_type_display_name": "Adafruit IO Key", "secret": "aio_XXXXXXXXXXXXXXXXXXXXXXXXXXXX" }, { @@ -412547,11 +412589,13 @@ "created_at": "2020-11-06T18:18:30Z", "url": "https://api.github.com/repos/owner/repo/secret-scanning/alerts/1", "html_url": "https://github.com/owner/repo/security/secret-scanning/1", + "locations_url": "https://api.github.com/repos/owner/private-repo/secret-scanning/alerts/1/locations", "state": "open", "resolution": null, "resolved_at": null, "resolved_by": null, "secret_type": "mailchimp_api_key", + "secret_type_display_name": "Mailchimp API Key", "secret": "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX-us2" } ], diff --git a/lib/rest/static/decorated/ghes-3.5.json b/lib/rest/static/decorated/ghes-3.5.json index 6405be4aee..fdca6225a9 100644 --- a/lib/rest/static/decorated/ghes-3.5.json +++ b/lib/rest/static/decorated/ghes-3.5.json @@ -309715,8 +309715,14 @@ "key": "default", "request": { "contentType": "application/json", - "description": "Example", + "description": "Update an existing webhook", "acceptHeader": "application/vnd.github.v3+json", + "bodyParameters": { + "url": "http://example.com/webhook", + "content_type": "json", + "insecure_ssl": "0", + "secret": "********" + }, "parameters": { "org": "ORG", "hook_id": "HOOK_ID" @@ -419433,6 +419439,19 @@ "format": "date-time", "readOnly": true }, + "updated_at": { + "anyOf": [ + { + "type": "null" + }, + { + "type": "string", + "description": "The time that the alert was last updated in ISO 8601 format: `YYYY-MM-DDTHH:MM:SSZ`.", + "format": "date-time", + "readOnly": true + } + ] + }, "url": { "type": "string", "description": "The REST API URL of the alert resource.", @@ -422390,6 +422409,19 @@ "format": "date-time", "readOnly": true }, + "updated_at": { + "anyOf": [ + { + "type": "null" + }, + { + "type": "string", + "description": "The time that the alert was last updated in ISO 8601 format: `YYYY-MM-DDTHH:MM:SSZ`.", + "format": "date-time", + "readOnly": true + } + ] + }, "url": { "type": "string", "description": "The REST API URL of the alert resource.", @@ -425226,9 +425258,6 @@ "html_url": "https://github.com/owner/private-repo/security/secret-scanning/42", "locations_url": "https://api.github.com/repos/owner/private-repo/secret-scanning/alerts/42/locations", "state": "open", - "resolution": null, - "resolved_at": null, - "resolved_by": null, "secret_type": "mailchimp_api_key", "secret_type_display_name": "Mailchimp API Key", "secret": "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX-us2" diff --git a/lib/rest/static/decorated/github.ae.json b/lib/rest/static/decorated/github.ae.json index 966935c080..bb2749a424 100644 --- a/lib/rest/static/decorated/github.ae.json +++ b/lib/rest/static/decorated/github.ae.json @@ -278575,8 +278575,14 @@ "key": "default", "request": { "contentType": "application/json", - "description": "Example", + "description": "Update an existing webhook", "acceptHeader": "application/vnd.github.v3+json", + "bodyParameters": { + "url": "http://example.com/webhook", + "content_type": "json", + "insecure_ssl": "0", + "secret": "********" + }, "parameters": { "org": "ORG", "hook_id": "HOOK_ID" diff --git a/lib/rest/static/dereferenced/api.github.com.deref.json b/lib/rest/static/dereferenced/api.github.com.deref.json index 1e9f6fa6a3..78386081d6 100644 --- a/lib/rest/static/dereferenced/api.github.com.deref.json +++ b/lib/rest/static/dereferenced/api.github.com.deref.json @@ -31156,6 +31156,189 @@ "trees_url", "url" ] + }, + "push_protection_bypassed": { + "type": [ + "boolean", + "null" + ], + "description": "Whether push protection was bypassed for the detected secret." + }, + "push_protection_bypassed_by": { + "anyOf": [ + { + "type": "null" + }, + { + "title": "Simple User", + "description": "Simple User", + "type": "object", + "properties": { + "name": { + "type": [ + "string", + "null" + ] + }, + "email": { + "type": [ + "string", + "null" + ] + }, + "login": { + "type": "string", + "examples": [ + "octocat" + ] + }, + "id": { + "type": "integer", + "examples": [ + 1 + ] + }, + "node_id": { + "type": "string", + "examples": [ + "MDQ6VXNlcjE=" + ] + }, + "avatar_url": { + "type": "string", + "format": "uri", + "examples": [ + "https://github.com/images/error/octocat_happy.gif" + ] + }, + "gravatar_id": { + "type": [ + "string", + "null" + ], + "examples": [ + "41d064eb2195891e12d0413f63227ea7" + ] + }, + "url": { + "type": "string", + "format": "uri", + "examples": [ + "https://api.github.com/users/octocat" + ] + }, + "html_url": { + "type": "string", + "format": "uri", + "examples": [ + "https://github.com/octocat" + ] + }, + "followers_url": { + "type": "string", + "format": "uri", + "examples": [ + "https://api.github.com/users/octocat/followers" + ] + }, + "following_url": { + "type": "string", + "examples": [ + "https://api.github.com/users/octocat/following{/other_user}" + ] + }, + "gists_url": { + "type": "string", + "examples": [ + "https://api.github.com/users/octocat/gists{/gist_id}" + ] + }, + "starred_url": { + "type": "string", + "examples": [ + "https://api.github.com/users/octocat/starred{/owner}{/repo}" + ] + }, + "subscriptions_url": { + "type": "string", + "format": "uri", + "examples": [ + "https://api.github.com/users/octocat/subscriptions" + ] + }, + "organizations_url": { + "type": "string", + "format": "uri", + "examples": [ + "https://api.github.com/users/octocat/orgs" + ] + }, + "repos_url": { + "type": "string", + "format": "uri", + "examples": [ + "https://api.github.com/users/octocat/repos" + ] + }, + "events_url": { + "type": "string", + "examples": [ + "https://api.github.com/users/octocat/events{/privacy}" + ] + }, + "received_events_url": { + "type": "string", + "format": "uri", + "examples": [ + "https://api.github.com/users/octocat/received_events" + ] + }, + "type": { + "type": "string", + "examples": [ + "User" + ] + }, + "site_admin": { + "type": "boolean" + }, + "starred_at": { + "type": "string", + "examples": [ + "\"2020-07-09T00:17:55Z\"" + ] + } + }, + "required": [ + "avatar_url", + "events_url", + "followers_url", + "following_url", + "gists_url", + "gravatar_id", + "html_url", + "id", + "node_id", + "login", + "organizations_url", + "received_events_url", + "repos_url", + "site_admin", + "starred_url", + "subscriptions_url", + "type", + "url" + ] + } + ] + }, + "push_protection_bypassed_at": { + "type": [ + "string", + "null" + ], + "format": "date-time", + "description": "The time that push protection was bypassed in ISO 8601 format: `YYYY-MM-DDTHH:MM:SSZ`." } } } @@ -31419,7 +31602,29 @@ "subscribers_count": 42, "network_count": 0 } - } + }, + "push_protection_bypassed_by": { + "login": "monalisa", + "id": 2, + "node_id": "MDQ6VXNlcjI=", + "avatar_url": "https://alambic.github.com/avatars/u/2?", + "gravatar_id": "", + "url": "https://api.github.com/users/monalisa", + "html_url": "https://github.com/monalisa", + "followers_url": "https://api.github.com/users/monalisa/followers", + "following_url": "https://api.github.com/users/monalisa/following{/other_user}", + "gists_url": "https://api.github.com/users/monalisa/gists{/gist_id}", + "starred_url": "https://api.github.com/users/monalisa/starred{/owner}{/repo}", + "subscriptions_url": "https://api.github.com/users/monalisa/subscriptions", + "organizations_url": "https://api.github.com/users/monalisa/orgs", + "repos_url": "https://api.github.com/users/monalisa/repos", + "events_url": "https://api.github.com/users/monalisa/events{/privacy}", + "received_events_url": "https://api.github.com/users/monalisa/received_events", + "type": "User", + "site_admin": true + }, + "push_protection_bypassed": true, + "push_protection_bypassed_at": "2020-11-06T21:48:51Z" }, { "number": 1, @@ -31658,7 +31863,10 @@ "subscribers_count": 42, "network_count": 0 } - } + }, + "push_protection_bypassed_by": null, + "push_protection_bypassed": false, + "push_protection_bypassed_at": null } ] } @@ -31788,25 +31996,25 @@ "type": "integer", "description": "Total minutes used on Windows runner machines." }, - "linux_4_core": { + "ubuntu_4_core": { "type": "integer", - "description": "Total minutes used on Linux 4 core runner machines." + "description": "Total minutes used on Ubuntu 4 core runner machines." }, - "linux_8_core": { + "ubuntu_8_core": { "type": "integer", - "description": "Total minutes used on Linux 8 core runner machines." + "description": "Total minutes used on Ubuntu 8 core runner machines." }, - "linux_16_core": { + "ubuntu_16_core": { "type": "integer", - "description": "Total minutes used on Linux 16 core runner machines." + "description": "Total minutes used on Ubuntu 16 core runner machines." }, - "linux_32_core": { + "ubuntu_32_core": { "type": "integer", - "description": "Total minutes used on Linux 32 core runner machines." + "description": "Total minutes used on Ubuntu 32 core runner machines." }, - "linux_64_core": { + "ubuntu_64_core": { "type": "integer", - "description": "Total minutes used on Linux 64 core runner machines." + "description": "Total minutes used on Ubuntu 64 core runner machines." }, "windows_4_core": { "type": "integer", @@ -94652,14 +94860,18 @@ } ] } - }, - "example": { - "content_type": "json", - "insecure_ssl": "0", - "secret": "********", - "url": "https://example.com/webhook" - }, - "additionalProperties": false + } + }, + "examples": { + "default": { + "summary": "Update an existing webhook", + "value": { + "url": "http://example.com/webhook", + "content_type": "json", + "insecure_ssl": "0", + "secret": "********" + } + } } } } @@ -127334,6 +127546,189 @@ "trees_url", "url" ] + }, + "push_protection_bypassed": { + "type": [ + "boolean", + "null" + ], + "description": "Whether push protection was bypassed for the detected secret." + }, + "push_protection_bypassed_by": { + "anyOf": [ + { + "type": "null" + }, + { + "title": "Simple User", + "description": "Simple User", + "type": "object", + "properties": { + "name": { + "type": [ + "string", + "null" + ] + }, + "email": { + "type": [ + "string", + "null" + ] + }, + "login": { + "type": "string", + "examples": [ + "octocat" + ] + }, + "id": { + "type": "integer", + "examples": [ + 1 + ] + }, + "node_id": { + "type": "string", + "examples": [ + "MDQ6VXNlcjE=" + ] + }, + "avatar_url": { + "type": "string", + "format": "uri", + "examples": [ + "https://github.com/images/error/octocat_happy.gif" + ] + }, + "gravatar_id": { + "type": [ + "string", + "null" + ], + "examples": [ + "41d064eb2195891e12d0413f63227ea7" + ] + }, + "url": { + "type": "string", + "format": "uri", + "examples": [ + "https://api.github.com/users/octocat" + ] + }, + "html_url": { + "type": "string", + "format": "uri", + "examples": [ + "https://github.com/octocat" + ] + }, + "followers_url": { + "type": "string", + "format": "uri", + "examples": [ + "https://api.github.com/users/octocat/followers" + ] + }, + "following_url": { + "type": "string", + "examples": [ + "https://api.github.com/users/octocat/following{/other_user}" + ] + }, + "gists_url": { + "type": "string", + "examples": [ + "https://api.github.com/users/octocat/gists{/gist_id}" + ] + }, + "starred_url": { + "type": "string", + "examples": [ + "https://api.github.com/users/octocat/starred{/owner}{/repo}" + ] + }, + "subscriptions_url": { + "type": "string", + "format": "uri", + "examples": [ + "https://api.github.com/users/octocat/subscriptions" + ] + }, + "organizations_url": { + "type": "string", + "format": "uri", + "examples": [ + "https://api.github.com/users/octocat/orgs" + ] + }, + "repos_url": { + "type": "string", + "format": "uri", + "examples": [ + "https://api.github.com/users/octocat/repos" + ] + }, + "events_url": { + "type": "string", + "examples": [ + "https://api.github.com/users/octocat/events{/privacy}" + ] + }, + "received_events_url": { + "type": "string", + "format": "uri", + "examples": [ + "https://api.github.com/users/octocat/received_events" + ] + }, + "type": { + "type": "string", + "examples": [ + "User" + ] + }, + "site_admin": { + "type": "boolean" + }, + "starred_at": { + "type": "string", + "examples": [ + "\"2020-07-09T00:17:55Z\"" + ] + } + }, + "required": [ + "avatar_url", + "events_url", + "followers_url", + "following_url", + "gists_url", + "gravatar_id", + "html_url", + "id", + "node_id", + "login", + "organizations_url", + "received_events_url", + "repos_url", + "site_admin", + "starred_url", + "subscriptions_url", + "type", + "url" + ] + } + ] + }, + "push_protection_bypassed_at": { + "type": [ + "string", + "null" + ], + "format": "date-time", + "description": "The time that push protection was bypassed in ISO 8601 format: `YYYY-MM-DDTHH:MM:SSZ`." } } } @@ -127597,7 +127992,29 @@ "subscribers_count": 42, "network_count": 0 } - } + }, + "push_protection_bypassed_by": { + "login": "monalisa", + "id": 2, + "node_id": "MDQ6VXNlcjI=", + "avatar_url": "https://alambic.github.com/avatars/u/2?", + "gravatar_id": "", + "url": "https://api.github.com/users/monalisa", + "html_url": "https://github.com/monalisa", + "followers_url": "https://api.github.com/users/monalisa/followers", + "following_url": "https://api.github.com/users/monalisa/following{/other_user}", + "gists_url": "https://api.github.com/users/monalisa/gists{/gist_id}", + "starred_url": "https://api.github.com/users/monalisa/starred{/owner}{/repo}", + "subscriptions_url": "https://api.github.com/users/monalisa/subscriptions", + "organizations_url": "https://api.github.com/users/monalisa/orgs", + "repos_url": "https://api.github.com/users/monalisa/repos", + "events_url": "https://api.github.com/users/monalisa/events{/privacy}", + "received_events_url": "https://api.github.com/users/monalisa/received_events", + "type": "User", + "site_admin": true + }, + "push_protection_bypassed": true, + "push_protection_bypassed_at": "2020-11-06T21:48:51Z" }, { "number": 1, @@ -127836,7 +128253,10 @@ "subscribers_count": 42, "network_count": 0 } - } + }, + "push_protection_bypassed_by": null, + "push_protection_bypassed": false, + "push_protection_bypassed_at": null } ] } @@ -127966,25 +128386,25 @@ "type": "integer", "description": "Total minutes used on Windows runner machines." }, - "linux_4_core": { + "ubuntu_4_core": { "type": "integer", - "description": "Total minutes used on Linux 4 core runner machines." + "description": "Total minutes used on Ubuntu 4 core runner machines." }, - "linux_8_core": { + "ubuntu_8_core": { "type": "integer", - "description": "Total minutes used on Linux 8 core runner machines." + "description": "Total minutes used on Ubuntu 8 core runner machines." }, - "linux_16_core": { + "ubuntu_16_core": { "type": "integer", - "description": "Total minutes used on Linux 16 core runner machines." + "description": "Total minutes used on Ubuntu 16 core runner machines." }, - "linux_32_core": { + "ubuntu_32_core": { "type": "integer", - "description": "Total minutes used on Linux 32 core runner machines." + "description": "Total minutes used on Ubuntu 32 core runner machines." }, - "linux_64_core": { + "ubuntu_64_core": { "type": "integer", - "description": "Total minutes used on Linux 64 core runner machines." + "description": "Total minutes used on Ubuntu 64 core runner machines." }, "windows_4_core": { "type": "integer", @@ -444707,6 +445127,189 @@ "secret": { "type": "string", "description": "The secret that was detected." + }, + "push_protection_bypassed": { + "type": [ + "boolean", + "null" + ], + "description": "Whether push protection was bypassed for the detected secret." + }, + "push_protection_bypassed_by": { + "anyOf": [ + { + "type": "null" + }, + { + "title": "Simple User", + "description": "Simple User", + "type": "object", + "properties": { + "name": { + "type": [ + "string", + "null" + ] + }, + "email": { + "type": [ + "string", + "null" + ] + }, + "login": { + "type": "string", + "examples": [ + "octocat" + ] + }, + "id": { + "type": "integer", + "examples": [ + 1 + ] + }, + "node_id": { + "type": "string", + "examples": [ + "MDQ6VXNlcjE=" + ] + }, + "avatar_url": { + "type": "string", + "format": "uri", + "examples": [ + "https://github.com/images/error/octocat_happy.gif" + ] + }, + "gravatar_id": { + "type": [ + "string", + "null" + ], + "examples": [ + "41d064eb2195891e12d0413f63227ea7" + ] + }, + "url": { + "type": "string", + "format": "uri", + "examples": [ + "https://api.github.com/users/octocat" + ] + }, + "html_url": { + "type": "string", + "format": "uri", + "examples": [ + "https://github.com/octocat" + ] + }, + "followers_url": { + "type": "string", + "format": "uri", + "examples": [ + "https://api.github.com/users/octocat/followers" + ] + }, + "following_url": { + "type": "string", + "examples": [ + "https://api.github.com/users/octocat/following{/other_user}" + ] + }, + "gists_url": { + "type": "string", + "examples": [ + "https://api.github.com/users/octocat/gists{/gist_id}" + ] + }, + "starred_url": { + "type": "string", + "examples": [ + "https://api.github.com/users/octocat/starred{/owner}{/repo}" + ] + }, + "subscriptions_url": { + "type": "string", + "format": "uri", + "examples": [ + "https://api.github.com/users/octocat/subscriptions" + ] + }, + "organizations_url": { + "type": "string", + "format": "uri", + "examples": [ + "https://api.github.com/users/octocat/orgs" + ] + }, + "repos_url": { + "type": "string", + "format": "uri", + "examples": [ + "https://api.github.com/users/octocat/repos" + ] + }, + "events_url": { + "type": "string", + "examples": [ + "https://api.github.com/users/octocat/events{/privacy}" + ] + }, + "received_events_url": { + "type": "string", + "format": "uri", + "examples": [ + "https://api.github.com/users/octocat/received_events" + ] + }, + "type": { + "type": "string", + "examples": [ + "User" + ] + }, + "site_admin": { + "type": "boolean" + }, + "starred_at": { + "type": "string", + "examples": [ + "\"2020-07-09T00:17:55Z\"" + ] + } + }, + "required": [ + "avatar_url", + "events_url", + "followers_url", + "following_url", + "gists_url", + "gravatar_id", + "html_url", + "id", + "node_id", + "login", + "organizations_url", + "received_events_url", + "repos_url", + "site_admin", + "starred_url", + "subscriptions_url", + "type", + "url" + ] + } + ] + }, + "push_protection_bypassed_at": { + "type": [ + "string", + "null" + ], + "format": "date-time", + "description": "The time that push protection was bypassed in ISO 8601 format: `YYYY-MM-DDTHH:MM:SSZ`." } } } @@ -444745,7 +445348,29 @@ }, "secret_type": "adafruit_io_key", "secret_type_display_name": "Adafruit IO Key", - "secret": "aio_XXXXXXXXXXXXXXXXXXXXXXXXXXXX" + "secret": "aio_XXXXXXXXXXXXXXXXXXXXXXXXXXXX", + "push_protection_bypassed_by": { + "login": "monalisa", + "id": 2, + "node_id": "MDQ6VXNlcjI=", + "avatar_url": "https://alambic.github.com/avatars/u/2?", + "gravatar_id": "", + "url": "https://api.github.com/users/monalisa", + "html_url": "https://github.com/monalisa", + "followers_url": "https://api.github.com/users/monalisa/followers", + "following_url": "https://api.github.com/users/monalisa/following{/other_user}", + "gists_url": "https://api.github.com/users/monalisa/gists{/gist_id}", + "starred_url": "https://api.github.com/users/monalisa/starred{/owner}{/repo}", + "subscriptions_url": "https://api.github.com/users/monalisa/subscriptions", + "organizations_url": "https://api.github.com/users/monalisa/orgs", + "repos_url": "https://api.github.com/users/monalisa/repos", + "events_url": "https://api.github.com/users/monalisa/events{/privacy}", + "received_events_url": "https://api.github.com/users/monalisa/received_events", + "type": "User", + "site_admin": true + }, + "push_protection_bypassed": true, + "push_protection_bypassed_at": "2020-11-06T21:48:51Z" }, { "number": 1, @@ -444759,7 +445384,10 @@ "resolved_by": null, "secret_type": "mailchimp_api_key", "secret_type_display_name": "Mailchimp API Key", - "secret": "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX-us2" + "secret": "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX-us2", + "push_protection_bypassed_by": null, + "push_protection_bypassed": false, + "push_protection_bypassed_at": null } ] } @@ -445094,6 +445722,189 @@ "secret": { "type": "string", "description": "The secret that was detected." + }, + "push_protection_bypassed": { + "type": [ + "boolean", + "null" + ], + "description": "Whether push protection was bypassed for the detected secret." + }, + "push_protection_bypassed_by": { + "anyOf": [ + { + "type": "null" + }, + { + "title": "Simple User", + "description": "Simple User", + "type": "object", + "properties": { + "name": { + "type": [ + "string", + "null" + ] + }, + "email": { + "type": [ + "string", + "null" + ] + }, + "login": { + "type": "string", + "examples": [ + "octocat" + ] + }, + "id": { + "type": "integer", + "examples": [ + 1 + ] + }, + "node_id": { + "type": "string", + "examples": [ + "MDQ6VXNlcjE=" + ] + }, + "avatar_url": { + "type": "string", + "format": "uri", + "examples": [ + "https://github.com/images/error/octocat_happy.gif" + ] + }, + "gravatar_id": { + "type": [ + "string", + "null" + ], + "examples": [ + "41d064eb2195891e12d0413f63227ea7" + ] + }, + "url": { + "type": "string", + "format": "uri", + "examples": [ + "https://api.github.com/users/octocat" + ] + }, + "html_url": { + "type": "string", + "format": "uri", + "examples": [ + "https://github.com/octocat" + ] + }, + "followers_url": { + "type": "string", + "format": "uri", + "examples": [ + "https://api.github.com/users/octocat/followers" + ] + }, + "following_url": { + "type": "string", + "examples": [ + "https://api.github.com/users/octocat/following{/other_user}" + ] + }, + "gists_url": { + "type": "string", + "examples": [ + "https://api.github.com/users/octocat/gists{/gist_id}" + ] + }, + "starred_url": { + "type": "string", + "examples": [ + "https://api.github.com/users/octocat/starred{/owner}{/repo}" + ] + }, + "subscriptions_url": { + "type": "string", + "format": "uri", + "examples": [ + "https://api.github.com/users/octocat/subscriptions" + ] + }, + "organizations_url": { + "type": "string", + "format": "uri", + "examples": [ + "https://api.github.com/users/octocat/orgs" + ] + }, + "repos_url": { + "type": "string", + "format": "uri", + "examples": [ + "https://api.github.com/users/octocat/repos" + ] + }, + "events_url": { + "type": "string", + "examples": [ + "https://api.github.com/users/octocat/events{/privacy}" + ] + }, + "received_events_url": { + "type": "string", + "format": "uri", + "examples": [ + "https://api.github.com/users/octocat/received_events" + ] + }, + "type": { + "type": "string", + "examples": [ + "User" + ] + }, + "site_admin": { + "type": "boolean" + }, + "starred_at": { + "type": "string", + "examples": [ + "\"2020-07-09T00:17:55Z\"" + ] + } + }, + "required": [ + "avatar_url", + "events_url", + "followers_url", + "following_url", + "gists_url", + "gravatar_id", + "html_url", + "id", + "node_id", + "login", + "organizations_url", + "received_events_url", + "repos_url", + "site_admin", + "starred_url", + "subscriptions_url", + "type", + "url" + ] + } + ] + }, + "push_protection_bypassed_at": { + "type": [ + "string", + "null" + ], + "format": "date-time", + "description": "The time that push protection was bypassed in ISO 8601 format: `YYYY-MM-DDTHH:MM:SSZ`." } } }, @@ -445111,7 +445922,10 @@ "resolved_by": null, "secret_type": "mailchimp_api_key", "secret_type_display_name": "Mailchimp API Key", - "secret": "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX-us2" + "secret": "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX-us2", + "push_protection_bypassed_by": null, + "push_protection_bypassed": false, + "push_protection_bypassed_at": null } } } @@ -445491,6 +446305,189 @@ "secret": { "type": "string", "description": "The secret that was detected." + }, + "push_protection_bypassed": { + "type": [ + "boolean", + "null" + ], + "description": "Whether push protection was bypassed for the detected secret." + }, + "push_protection_bypassed_by": { + "anyOf": [ + { + "type": "null" + }, + { + "title": "Simple User", + "description": "Simple User", + "type": "object", + "properties": { + "name": { + "type": [ + "string", + "null" + ] + }, + "email": { + "type": [ + "string", + "null" + ] + }, + "login": { + "type": "string", + "examples": [ + "octocat" + ] + }, + "id": { + "type": "integer", + "examples": [ + 1 + ] + }, + "node_id": { + "type": "string", + "examples": [ + "MDQ6VXNlcjE=" + ] + }, + "avatar_url": { + "type": "string", + "format": "uri", + "examples": [ + "https://github.com/images/error/octocat_happy.gif" + ] + }, + "gravatar_id": { + "type": [ + "string", + "null" + ], + "examples": [ + "41d064eb2195891e12d0413f63227ea7" + ] + }, + "url": { + "type": "string", + "format": "uri", + "examples": [ + "https://api.github.com/users/octocat" + ] + }, + "html_url": { + "type": "string", + "format": "uri", + "examples": [ + "https://github.com/octocat" + ] + }, + "followers_url": { + "type": "string", + "format": "uri", + "examples": [ + "https://api.github.com/users/octocat/followers" + ] + }, + "following_url": { + "type": "string", + "examples": [ + "https://api.github.com/users/octocat/following{/other_user}" + ] + }, + "gists_url": { + "type": "string", + "examples": [ + "https://api.github.com/users/octocat/gists{/gist_id}" + ] + }, + "starred_url": { + "type": "string", + "examples": [ + "https://api.github.com/users/octocat/starred{/owner}{/repo}" + ] + }, + "subscriptions_url": { + "type": "string", + "format": "uri", + "examples": [ + "https://api.github.com/users/octocat/subscriptions" + ] + }, + "organizations_url": { + "type": "string", + "format": "uri", + "examples": [ + "https://api.github.com/users/octocat/orgs" + ] + }, + "repos_url": { + "type": "string", + "format": "uri", + "examples": [ + "https://api.github.com/users/octocat/repos" + ] + }, + "events_url": { + "type": "string", + "examples": [ + "https://api.github.com/users/octocat/events{/privacy}" + ] + }, + "received_events_url": { + "type": "string", + "format": "uri", + "examples": [ + "https://api.github.com/users/octocat/received_events" + ] + }, + "type": { + "type": "string", + "examples": [ + "User" + ] + }, + "site_admin": { + "type": "boolean" + }, + "starred_at": { + "type": "string", + "examples": [ + "\"2020-07-09T00:17:55Z\"" + ] + } + }, + "required": [ + "avatar_url", + "events_url", + "followers_url", + "following_url", + "gists_url", + "gravatar_id", + "html_url", + "id", + "node_id", + "login", + "organizations_url", + "received_events_url", + "repos_url", + "site_admin", + "starred_url", + "subscriptions_url", + "type", + "url" + ] + } + ] + }, + "push_protection_bypassed_at": { + "type": [ + "string", + "null" + ], + "format": "date-time", + "description": "The time that push protection was bypassed in ISO 8601 format: `YYYY-MM-DDTHH:MM:SSZ`." } } }, @@ -445527,7 +446524,10 @@ }, "secret_type": "mailchimp_api_key", "secret_type_display_name": "Mailchimp API Key", - "secret": "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX-us2" + "secret": "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX-us2", + "push_protection_bypassed": false, + "push_protection_bypassed_by": null, + "push_protection_bypassed_at": null } } } @@ -592557,25 +593557,25 @@ "type": "integer", "description": "Total minutes used on Windows runner machines." }, - "linux_4_core": { + "ubuntu_4_core": { "type": "integer", - "description": "Total minutes used on Linux 4 core runner machines." + "description": "Total minutes used on Ubuntu 4 core runner machines." }, - "linux_8_core": { + "ubuntu_8_core": { "type": "integer", - "description": "Total minutes used on Linux 8 core runner machines." + "description": "Total minutes used on Ubuntu 8 core runner machines." }, - "linux_16_core": { + "ubuntu_16_core": { "type": "integer", - "description": "Total minutes used on Linux 16 core runner machines." + "description": "Total minutes used on Ubuntu 16 core runner machines." }, - "linux_32_core": { + "ubuntu_32_core": { "type": "integer", - "description": "Total minutes used on Linux 32 core runner machines." + "description": "Total minutes used on Ubuntu 32 core runner machines." }, - "linux_64_core": { + "ubuntu_64_core": { "type": "integer", - "description": "Total minutes used on Linux 64 core runner machines." + "description": "Total minutes used on Ubuntu 64 core runner machines." }, "windows_4_core": { "type": "integer", diff --git a/lib/rest/static/dereferenced/ghes-3.1.deref.json b/lib/rest/static/dereferenced/ghes-3.1.deref.json index d9939bf246..8028b38367 100644 --- a/lib/rest/static/dereferenced/ghes-3.1.deref.json +++ b/lib/rest/static/dereferenced/ghes-3.1.deref.json @@ -85419,14 +85419,18 @@ } ] } - }, - "example": { - "content_type": "json", - "insecure_ssl": "0", - "secret": "********", - "url": "https://example.com/webhook" - }, - "additionalProperties": false + } + }, + "examples": { + "default": { + "summary": "Update an existing webhook", + "value": { + "url": "http://example.com/webhook", + "content_type": "json", + "insecure_ssl": "0", + "secret": "********" + } + } } } } @@ -372197,6 +372201,7 @@ "created_at": "2020-11-06T18:48:51Z", "url": "https://api.github.com/repos/owner/private-repo/secret-scanning/alerts/2", "html_url": "https://github.com/owner/private-repo/security/secret-scanning/2", + "locations_url": "https://api.github.com/repos/owner/private-repo/secret-scanning/alerts/2/locations", "state": "resolved", "resolution": "false_positive", "resolved_at": "2020-11-07T02:47:13Z", @@ -372221,6 +372226,7 @@ "site_admin": true }, "secret_type": "adafruit_io_key", + "secret_type_display_name": "Adafruit IO Key", "secret": "aio_XXXXXXXXXXXXXXXXXXXXXXXXXXXX" }, { @@ -372228,11 +372234,13 @@ "created_at": "2020-11-06T18:18:30Z", "url": "https://api.github.com/repos/owner/repo/secret-scanning/alerts/1", "html_url": "https://github.com/owner/repo/security/secret-scanning/1", + "locations_url": "https://api.github.com/repos/owner/private-repo/secret-scanning/alerts/1/locations", "state": "open", "resolution": null, "resolved_at": null, "resolved_by": null, "secret_type": "mailchimp_api_key", + "secret_type_display_name": "Mailchimp API Key", "secret": "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX-us2" } ] diff --git a/lib/rest/static/dereferenced/ghes-3.2.deref.json b/lib/rest/static/dereferenced/ghes-3.2.deref.json index 6c8cc52b5b..85f8f3c229 100644 --- a/lib/rest/static/dereferenced/ghes-3.2.deref.json +++ b/lib/rest/static/dereferenced/ghes-3.2.deref.json @@ -86676,14 +86676,18 @@ } ] } - }, - "example": { - "content_type": "json", - "insecure_ssl": "0", - "secret": "********", - "url": "https://example.com/webhook" - }, - "additionalProperties": false + } + }, + "examples": { + "default": { + "summary": "Update an existing webhook", + "value": { + "url": "http://example.com/webhook", + "content_type": "json", + "insecure_ssl": "0", + "secret": "********" + } + } } } } @@ -381496,6 +381500,7 @@ "created_at": "2020-11-06T18:48:51Z", "url": "https://api.github.com/repos/owner/private-repo/secret-scanning/alerts/2", "html_url": "https://github.com/owner/private-repo/security/secret-scanning/2", + "locations_url": "https://api.github.com/repos/owner/private-repo/secret-scanning/alerts/2/locations", "state": "resolved", "resolution": "false_positive", "resolved_at": "2020-11-07T02:47:13Z", @@ -381520,6 +381525,7 @@ "site_admin": true }, "secret_type": "adafruit_io_key", + "secret_type_display_name": "Adafruit IO Key", "secret": "aio_XXXXXXXXXXXXXXXXXXXXXXXXXXXX" }, { @@ -381527,11 +381533,13 @@ "created_at": "2020-11-06T18:18:30Z", "url": "https://api.github.com/repos/owner/repo/secret-scanning/alerts/1", "html_url": "https://github.com/owner/repo/security/secret-scanning/1", + "locations_url": "https://api.github.com/repos/owner/private-repo/secret-scanning/alerts/1/locations", "state": "open", "resolution": null, "resolved_at": null, "resolved_by": null, "secret_type": "mailchimp_api_key", + "secret_type_display_name": "Mailchimp API Key", "secret": "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX-us2" } ] diff --git a/lib/rest/static/dereferenced/ghes-3.3.deref.json b/lib/rest/static/dereferenced/ghes-3.3.deref.json index a1732ffd77..752bc07b2f 100644 --- a/lib/rest/static/dereferenced/ghes-3.3.deref.json +++ b/lib/rest/static/dereferenced/ghes-3.3.deref.json @@ -87297,14 +87297,18 @@ } ] } - }, - "example": { - "content_type": "json", - "insecure_ssl": "0", - "secret": "********", - "url": "https://example.com/webhook" - }, - "additionalProperties": false + } + }, + "examples": { + "default": { + "summary": "Update an existing webhook", + "value": { + "url": "http://example.com/webhook", + "content_type": "json", + "insecure_ssl": "0", + "secret": "********" + } + } } } } @@ -101777,6 +101781,19 @@ "format": "date-time", "readOnly": true }, + "updated_at": { + "anyOf": [ + { + "type": "null" + }, + { + "type": "string", + "description": "The time that the alert was last updated in ISO 8601 format: `YYYY-MM-DDTHH:MM:SSZ`.", + "format": "date-time", + "readOnly": true + } + ] + }, "url": { "type": "string", "description": "The REST API URL of the alert resource.", @@ -104114,6 +104131,7 @@ "created_at": "2020-11-06T18:48:51Z", "url": "https://api.github.com/repos/owner/private-repo/secret-scanning/alerts/2", "html_url": "https://github.com/owner/private-repo/security/secret-scanning/2", + "locations_url": "https://api.github.com/repos/owner/private-repo/secret-scanning/alerts/2/locations", "state": "resolved", "resolution": "false_positive", "resolved_at": "2020-11-07T02:47:13Z", @@ -104138,6 +104156,7 @@ "site_admin": true }, "secret_type": "adafruit_io_key", + "secret_type_display_name": "Adafruit IO Key", "secret": "aio_XXXXXXXXXXXXXXXXXXXXXXXXXXXX", "repository": { "id": 1296269, @@ -104370,11 +104389,13 @@ "created_at": "2020-11-06T18:18:30Z", "url": "https://api.github.com/repos/owner/repo/secret-scanning/alerts/1", "html_url": "https://github.com/owner/repo/security/secret-scanning/1", + "locations_url": "https://api.github.com/repos/owner/private-repo/secret-scanning/alerts/1/locations", "state": "open", "resolution": null, "resolved_at": null, "resolved_by": null, "secret_type": "mailchimp_api_key", + "secret_type_display_name": "Mailchimp API Key", "secret": "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX-us2", "repository": { "id": 1296269, @@ -385065,6 +385086,7 @@ "created_at": "2020-11-06T18:48:51Z", "url": "https://api.github.com/repos/owner/private-repo/secret-scanning/alerts/2", "html_url": "https://github.com/owner/private-repo/security/secret-scanning/2", + "locations_url": "https://api.github.com/repos/owner/private-repo/secret-scanning/alerts/2/locations", "state": "resolved", "resolution": "false_positive", "resolved_at": "2020-11-07T02:47:13Z", @@ -385089,6 +385111,7 @@ "site_admin": true }, "secret_type": "adafruit_io_key", + "secret_type_display_name": "Adafruit IO Key", "secret": "aio_XXXXXXXXXXXXXXXXXXXXXXXXXXXX" }, { @@ -385096,11 +385119,13 @@ "created_at": "2020-11-06T18:18:30Z", "url": "https://api.github.com/repos/owner/repo/secret-scanning/alerts/1", "html_url": "https://github.com/owner/repo/security/secret-scanning/1", + "locations_url": "https://api.github.com/repos/owner/private-repo/secret-scanning/alerts/1/locations", "state": "open", "resolution": null, "resolved_at": null, "resolved_by": null, "secret_type": "mailchimp_api_key", + "secret_type_display_name": "Mailchimp API Key", "secret": "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX-us2" } ] diff --git a/lib/rest/static/dereferenced/ghes-3.4.deref.json b/lib/rest/static/dereferenced/ghes-3.4.deref.json index ba5b75f2f6..5add377814 100644 --- a/lib/rest/static/dereferenced/ghes-3.4.deref.json +++ b/lib/rest/static/dereferenced/ghes-3.4.deref.json @@ -35692,6 +35692,19 @@ "format": "date-time", "readOnly": true }, + "updated_at": { + "anyOf": [ + { + "type": "null" + }, + { + "type": "string", + "description": "The time that the alert was last updated in ISO 8601 format: `YYYY-MM-DDTHH:MM:SSZ`.", + "format": "date-time", + "readOnly": true + } + ] + }, "url": { "type": "string", "description": "The REST API URL of the alert resource.", @@ -38029,6 +38042,7 @@ "created_at": "2020-11-06T18:48:51Z", "url": "https://api.github.com/repos/owner/private-repo/secret-scanning/alerts/2", "html_url": "https://github.com/owner/private-repo/security/secret-scanning/2", + "locations_url": "https://api.github.com/repos/owner/private-repo/secret-scanning/alerts/2/locations", "state": "resolved", "resolution": "false_positive", "resolved_at": "2020-11-07T02:47:13Z", @@ -38053,6 +38067,7 @@ "site_admin": true }, "secret_type": "adafruit_io_key", + "secret_type_display_name": "Adafruit IO Key", "secret": "aio_XXXXXXXXXXXXXXXXXXXXXXXXXXXX", "repository": { "id": 1296269, @@ -38285,11 +38300,13 @@ "created_at": "2020-11-06T18:18:30Z", "url": "https://api.github.com/repos/owner/repo/secret-scanning/alerts/1", "html_url": "https://github.com/owner/repo/security/secret-scanning/1", + "locations_url": "https://api.github.com/repos/owner/private-repo/secret-scanning/alerts/1/locations", "state": "open", "resolution": null, "resolved_at": null, "resolved_by": null, "secret_type": "mailchimp_api_key", + "secret_type_display_name": "Mailchimp API Key", "secret": "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX-us2", "repository": { "id": 1296269, @@ -93330,14 +93347,18 @@ } ] } - }, - "example": { - "content_type": "json", - "insecure_ssl": "0", - "secret": "********", - "url": "https://example.com/webhook" - }, - "additionalProperties": false + } + }, + "examples": { + "default": { + "summary": "Update an existing webhook", + "value": { + "url": "http://example.com/webhook", + "content_type": "json", + "insecure_ssl": "0", + "secret": "********" + } + } } } } @@ -113603,6 +113624,19 @@ "format": "date-time", "readOnly": true }, + "updated_at": { + "anyOf": [ + { + "type": "null" + }, + { + "type": "string", + "description": "The time that the alert was last updated in ISO 8601 format: `YYYY-MM-DDTHH:MM:SSZ`.", + "format": "date-time", + "readOnly": true + } + ] + }, "url": { "type": "string", "description": "The REST API URL of the alert resource.", @@ -115940,6 +115974,7 @@ "created_at": "2020-11-06T18:48:51Z", "url": "https://api.github.com/repos/owner/private-repo/secret-scanning/alerts/2", "html_url": "https://github.com/owner/private-repo/security/secret-scanning/2", + "locations_url": "https://api.github.com/repos/owner/private-repo/secret-scanning/alerts/2/locations", "state": "resolved", "resolution": "false_positive", "resolved_at": "2020-11-07T02:47:13Z", @@ -115964,6 +115999,7 @@ "site_admin": true }, "secret_type": "adafruit_io_key", + "secret_type_display_name": "Adafruit IO Key", "secret": "aio_XXXXXXXXXXXXXXXXXXXXXXXXXXXX", "repository": { "id": 1296269, @@ -116196,11 +116232,13 @@ "created_at": "2020-11-06T18:18:30Z", "url": "https://api.github.com/repos/owner/repo/secret-scanning/alerts/1", "html_url": "https://github.com/owner/repo/security/secret-scanning/1", + "locations_url": "https://api.github.com/repos/owner/private-repo/secret-scanning/alerts/1/locations", "state": "open", "resolution": null, "resolved_at": null, "resolved_by": null, "secret_type": "mailchimp_api_key", + "secret_type_display_name": "Mailchimp API Key", "secret": "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX-us2", "repository": { "id": 1296269, @@ -403611,6 +403649,7 @@ "created_at": "2020-11-06T18:48:51Z", "url": "https://api.github.com/repos/owner/private-repo/secret-scanning/alerts/2", "html_url": "https://github.com/owner/private-repo/security/secret-scanning/2", + "locations_url": "https://api.github.com/repos/owner/private-repo/secret-scanning/alerts/2/locations", "state": "resolved", "resolution": "false_positive", "resolved_at": "2020-11-07T02:47:13Z", @@ -403635,6 +403674,7 @@ "site_admin": true }, "secret_type": "adafruit_io_key", + "secret_type_display_name": "Adafruit IO Key", "secret": "aio_XXXXXXXXXXXXXXXXXXXXXXXXXXXX" }, { @@ -403642,11 +403682,13 @@ "created_at": "2020-11-06T18:18:30Z", "url": "https://api.github.com/repos/owner/repo/secret-scanning/alerts/1", "html_url": "https://github.com/owner/repo/security/secret-scanning/1", + "locations_url": "https://api.github.com/repos/owner/private-repo/secret-scanning/alerts/1/locations", "state": "open", "resolution": null, "resolved_at": null, "resolved_by": null, "secret_type": "mailchimp_api_key", + "secret_type_display_name": "Mailchimp API Key", "secret": "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX-us2" } ] diff --git a/lib/rest/static/dereferenced/ghes-3.5.deref.json b/lib/rest/static/dereferenced/ghes-3.5.deref.json index b837b24882..6d6c2f0c52 100644 --- a/lib/rest/static/dereferenced/ghes-3.5.deref.json +++ b/lib/rest/static/dereferenced/ghes-3.5.deref.json @@ -36058,6 +36058,19 @@ "format": "date-time", "readOnly": true }, + "updated_at": { + "anyOf": [ + { + "type": "null" + }, + { + "type": "string", + "description": "The time that the alert was last updated in ISO 8601 format: `YYYY-MM-DDTHH:MM:SSZ`.", + "format": "date-time", + "readOnly": true + } + ] + }, "url": { "type": "string", "description": "The REST API URL of the alert resource.", @@ -97575,14 +97588,18 @@ } ] } - }, - "example": { - "content_type": "json", - "insecure_ssl": "0", - "secret": "********", - "url": "https://example.com/webhook" - }, - "additionalProperties": false + } + }, + "examples": { + "default": { + "summary": "Update an existing webhook", + "value": { + "url": "http://example.com/webhook", + "content_type": "json", + "insecure_ssl": "0", + "secret": "********" + } + } } } } @@ -117854,6 +117871,19 @@ "format": "date-time", "readOnly": true }, + "updated_at": { + "anyOf": [ + { + "type": "null" + }, + { + "type": "string", + "description": "The time that the alert was last updated in ISO 8601 format: `YYYY-MM-DDTHH:MM:SSZ`.", + "format": "date-time", + "readOnly": true + } + ] + }, "url": { "type": "string", "description": "The REST API URL of the alert resource.", @@ -416017,9 +416047,6 @@ "html_url": "https://github.com/owner/private-repo/security/secret-scanning/42", "locations_url": "https://api.github.com/repos/owner/private-repo/secret-scanning/alerts/42/locations", "state": "open", - "resolution": null, - "resolved_at": null, - "resolved_by": null, "secret_type": "mailchimp_api_key", "secret_type_display_name": "Mailchimp API Key", "secret": "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX-us2" diff --git a/lib/rest/static/dereferenced/github.ae.deref.json b/lib/rest/static/dereferenced/github.ae.deref.json index ba1a496f54..9eacfff43a 100644 --- a/lib/rest/static/dereferenced/github.ae.deref.json +++ b/lib/rest/static/dereferenced/github.ae.deref.json @@ -60091,14 +60091,18 @@ } ] } - }, - "example": { - "content_type": "json", - "insecure_ssl": "0", - "secret": "********", - "url": "https://example.com/webhook" - }, - "additionalProperties": false + } + }, + "examples": { + "default": { + "summary": "Update an existing webhook", + "value": { + "url": "http://example.com/webhook", + "content_type": "json", + "insecure_ssl": "0", + "secret": "********" + } + } } } } 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 1a18e7c806..29dd50f4dd 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:ed16c36428997cd7d3705f1edf1dc967122e8f8a73e7f67538ada3e092230c95 -size 741390 +oid sha256:0dbf9bce6d3e100a538b370185fe547c1f3ecb35241e843b96b0c08978bc0358 +size 741123 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 3f39518e17..affb98d414 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:05687c572244244f212bab3c96d7bd34384231189cce239da4a27af099f10c7f -size 1564131 +oid sha256:72b2ec54eacf9d6cfb275ec1af8fe8bfe2e02594b06c922fe220399563cdd87e +size 1564304 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 87eb31e962..625c5ab4cb 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:a74e09658956a04ed2b1ef295901d568c1b0d6f325563b03d796c1acaf0b75ca -size 997473 +oid sha256:c95afb1ecf48c84baf33ea23c4f0329f7f3d637be11709f6871f239cb9728c4e +size 997744 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 c95fe0d734..9d4ce07d37 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:e2aab6c24aedbb022f481af59327b37e1f7c7fd519b537700c4df47ee00de36d -size 3999078 +oid sha256:275590f9a9800ccaff6262763c65ce5ffb872ab237b491a6b17358dfbe0af264 +size 4000757 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 366fc24330..4dcfbf7b96 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:65bca0d4a84256ba99bcd5db49734f4f5bf829a4d80c1a2c8f6c8c4ce5c5d8b1 -size 684016 +oid sha256:70306e3c1570eae90a306bf8a5bba362d79ed93b31849f2df9d950f3fc7a134c +size 684166 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 ad7a2ba8e4..68a329bbd7 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:0a0890b67da67f4e5a925b4c438c2d2a46ddec1cc33b8d8ef132883d6c46f9b8 -size 2977641 +oid sha256:e052cf70e11e839bb7f2e391cf8afe2fce4de4150703dd8810d397b63bb94c30 +size 2975039 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 3b32541963..1ff97e8ca2 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:33eec6bb91fc50e5b8c1e5d345bd63accae647f59d784b40a606a52329ad420d -size 751177 +oid sha256:b26ce0c7000e831285414db4a76f52ccc8fc271892c6c03cc257d500a3c45de7 +size 751277 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 39980b2ad5..c3b8b18d5b 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:d67cd7b1e2159f1788f06ecea7a3b515fa2cf4eee530a175d88cfeb6ef0dd3a7 -size 4132138 +oid sha256:2c0628e6b78f88a86a65bd142104fe2b44c5a9d620b5fd68303fa71aba3ad430 +size 4132315 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 e61eb623b5..c7432c1871 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:b20acefb708485b8d3fb05a980043869755eded56fe5dae258d982e9b3fe00ca -size 674167 +oid sha256:18142405b7699e3b14b40d7c43a80c5c260f3df5e397200baa20f4486d18ebb4 +size 674288 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 af860bacc8..742e948f71 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:af9b685fd415c935dc8a62d48bff533587856c82d63dbfcd9e01d9a8bd8cd070 -size 2872232 +oid sha256:b45306a96f45b518d7bc853d7464d138edd00d9b01bbfd471b767ee86127da3e +size 2872923 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 97af2dc38c..16611de5a9 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:18eb70226514e7df2b93138aaf3d7f2a9a2d4c1206355160fa33b0be4292bb67 -size 762832 +oid sha256:20995221907ce72f1b715ac964f43fc8b5ff363d6bdc04d792dee8801688f7f4 +size 762877 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 26986f6674..31868cf92c 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:2309f5d8e501f3b6dc0dea93662abcbdb228f4c1505eef5e84f8491661c99851 -size 1603179 +oid sha256:493256167d4d236f0941082c97948bb0c234a1cb8064168035bde0fff14beb96 +size 1602875 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 a0235a6e12..d0c48eab91 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:5a8a5e0ae631b3fe13f9879e87e01a3fd185f7c7455b23e99cd4d4e1e72c8011 -size 1029404 +oid sha256:4a4a436b325170eb6dab0afb9fd10d0c7e9ce075eb31761b16689953a1f4968a +size 1034749 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 f1a6d6be7f..ccce422b19 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:33152250353b001ad857a875d09e8ff980a4fc30c43b81b895b33fbb5278088e -size 4153253 +oid sha256:4a9b42b67dcf646a5c2a493e4baddd9f80329508c5cfbcd9cd60875ff46d8a66 +size 4154100 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 0266247be1..0b9f5ad026 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:2d22854b15fa8733458d21f22acfa2269021d9454d44144509390d66d1aa9c32 -size 704177 +oid sha256:18016023410ccb3eac5071ef503539b161817a5cf99fe5e32c2f50217da7bf97 +size 704103 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 8e9223e4b9..c0733dd7d2 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:bf22e0629a42470a8ccd8e797533905f02492f64d89cc102c65bb233df59d90c -size 3064331 +oid sha256:752a4921454faaf822b25b38aee33f740109b441510a7506a7464dae63960bf8 +size 3062366 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 7c61534341..99f390d0ee 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:76f870980470e63cd73046a0f15e213b9d2025af2d545d2c529266ba80acbe0b -size 772138 +oid sha256:f1307e36aed5ed6b4d6c04db9025073462b5acea8300e94c3cd91537917e239a +size 772342 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 1e5838d09a..dee76d3458 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:af7d62972e8176ea180e371b3cd668630cb045c60df045d9fed42a3dc259799e -size 4248929 +oid sha256:e6640d6675d349dbfedcaefcb0cb0e5b3997bfef38234aebb420e1855fb440ef +size 4249386 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 40f304ae16..23ad052cb5 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:59e37d3335ca21d3a01bb7f083d72b2dd5a46ac9fa524c2706cbe82f583df2bb -size 693832 +oid sha256:7f1e1f4278a054175c5086212168ec58149b68d95d6cd9dcefc538603802cb6b +size 693876 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 4b2e48738e..b2a5444d5a 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:73e44759e0eef7340a043480095654638e571aef88f99e6420d689e436a3d180 -size 2951774 +oid sha256:955aaea5ad5a505b5949ef37784fc3a69f61b59796b98adbb9bb7a5a1e2ed824 +size 2952591 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 beb7f8148e..737dc4b2da 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:eed40546088c5a77abe919758eac26d479874a81be20fd856748e07ea22857ef -size 786269 +oid sha256:6411f8d20a51b4906547f4ca9b4c6c75d8a21f6a5400b6c10f6c0bbc43ad6127 +size 786168 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 6644e87da1..86d82bd4da 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:9a3979979e8533dc6662b6661775c137ed7106b5485fdf86572745e0a6eb84c0 -size 1644473 +oid sha256:b217c31e76bd7042107c78936a5caff970b1bea704adad6d0eb571fcaae4d732 +size 1643938 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 f48158d0eb..3ca93601b7 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:cf9fafb39dbeaa43ace15f63eb33fd980cf8f11e0c6b0ad653879a9c801bcaa5 -size 1069443 +oid sha256:875fcc375591377140f36a0f33cc80a225ab5b8bc1c8d7b38a3cf2c535c900be +size 1069517 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 3d5514ad96..8c7a812e50 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:81943fb2b60b96315eb049bc7ae8d83c7bbd49b8f109fb2b8b8dbd5409bd2229 -size 4248168 +oid sha256:e47fa8b3ae7e5fd389ed332084380f62598176bdeb93d726fea6f92c6e711047 +size 4249870 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 0b8596f7ba..fe8e73532a 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:a98de964c1c8c21c1ca9788ce96e5dd48df639864db7352e1610f4ba570dca3f -size 723663 +oid sha256:8dbfe0350f4cafe1d4ebd5ec3680c5265c786dd9d934295a40a96056f13f0358 +size 723559 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 54428e59c3..8e607b0765 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:9d046b4be22d2a2fc464213917008a49a9ff02006ee96dc1dfd387f744613938 -size 3144603 +oid sha256:910e76a15eb178b268a07051fdb029b1f69a1c55a8c2a62bf2200ba923ef3013 +size 3142790 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 b859cf80bf..6362b40118 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:6c926750a068904a411ff4dc407d96299c51e88fbd4dfcffb7d52cbfd6c51819 -size 795575 +oid sha256:33811a7d4b02ba58f18b8b5da70848fe78579677d0695f7afa0994cab8c63f44 +size 795624 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 391684bac3..3cf5984dd0 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:92513dd056eaa8e7ebb6dc25f35a16dc11dd50e515c75b0d5f2ae7884453dd4f -size 4368715 +oid sha256:8cc4563dd45d19e051aaf4a8cedcee4f7c9baa5a96666ebd1feb2ed361f2b1b5 +size 4369636 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 ba535c4891..6151c12227 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:47f4456fdf481e2d4253b3ad3ca983b8b6cb5009e619b5ccb6c9f5f7bb8e8cb4 -size 713348 +oid sha256:450c6d38ee706a83fd98edc736d0c4e601a4e35a534871056a4a2b4502530a11 +size 713446 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 841f672650..47476d12ae 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:9ba97781afbff9ef001e9304b65840c3016b771117bd1adfa2e2259a8ef4969f -size 3029192 +oid sha256:2b115df79ff93815f1e14bec97714fefd250fe8611ed3bf3034c1a191f86eed8 +size 3030435 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 fb6a97c7de..2697faabba 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:3bd228d0bcc359094f9b03681764417e90c2f82197dd320a6a3e5040ed0d8ccc -size 788288 +oid sha256:f55c4a363c9b84fe2d85cd141703217f484560a2797d11d1286460d83ee1067f +size 788350 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 4d0309ae9a..8df2002169 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:ebc5ae3230dd1056aefbcc7eb62715461a55f69d3d5e224767da628f697b1ab6 -size 1655568 +oid sha256:07ceb08ae858e3557c337d43034abae0ea9e2250d0d7007c9eb5ce7e0ee8081f +size 1655961 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 38600c95f2..cb68e5c680 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:e067b9a435715515456e2622dc14c5003e2197658375604442dd55d8a2dadfe3 -size 1078158 +oid sha256:44a53af1135d07bc6e4497fbc4f216805cd4a7dd4c80d4c4d3b276dc0dadea1f +size 1078695 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 00b0e9f542..dcf82c21e3 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:bf2b3f19d5f62131d71fa7b35df389c0acc220968aaa801bd9c5c02d4fcfa089 -size 4287698 +oid sha256:53a7ffb8eff52bcdb7de29e00bdf1712cc2e66a6e135692beee64b7fccf23995 +size 4291469 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 1a738aa213..883f014e1b 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:0164bba81aa772152acd17ae6ef8b168d2d6ea4e3e792624ed081928cfe8abaf -size 727317 +oid sha256:b3cd53e2259965b2ecb45b44700c8338d66f237662bc7c04dfaeacd2981ac6e4 +size 727184 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 987418c042..c97cacc362 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:bbbaf4a4654c9b125c405175a9e27da517d97757b58e4f03b1cbac852f9132e2 -size 3163740 +oid sha256:32365db9b6c0b8b338cf6374045e70ec4074a1bc5a02cecd8af87bc84375e301 +size 3162039 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 b27bac9266..518d1e2bcc 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:f5380367fb510ceb49a8ea04f77d61dfa7794d3280d169c5555c34381d4c2488 -size 798326 +oid sha256:5791ce0f1e99d9ddeb1b13d0f1b5727862c1b665cc220a3339190a1782aec551 +size 798352 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 e408a50007..bad25ff4c2 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:5c0214be8221470f2f8e6769ca83bf867eb83ec33e2be8fa18e91bf12dab9919 -size 4392976 +oid sha256:3e842cc2f339f2b6ef69ca9a7e537c197cd90709765b2237275fabf0effbc62b +size 4393449 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 b21d4150f3..6763ff4df1 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:38dbae095966093cfbe0a73896bc12a78cde87d4614b1c27c89b31b28ef587cc -size 716515 +oid sha256:bb32dbdaf3e0a1a128491a325b2121074651f2da748da96274ce2484419509d4 +size 716717 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 1d804657df..028adca9d8 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:fc1fc6604e37cf0540ba9502737a11751d654a775c61e6451b8926b47633ddf0 -size 3050203 +oid sha256:7ff11080354569e9d5311a1c615cc3c56a0ddfa3279b45f8407ddf661006a3f6 +size 3050093 diff --git a/lib/search/indexes/github-docs-3.5-cn-records.json.br b/lib/search/indexes/github-docs-3.5-cn-records.json.br index bf5efdf7e7..a3efb47dbb 100644 --- a/lib/search/indexes/github-docs-3.5-cn-records.json.br +++ b/lib/search/indexes/github-docs-3.5-cn-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:6c57babfa4fdaf0e94fa5ec296879714ce5b6ac231d9903883ecd5c525e1cd20 -size 816596 +oid sha256:49426c9ccbe097ce1ecc86c14d516bad8439a56ac29312eebef500447669b3ca +size 816774 diff --git a/lib/search/indexes/github-docs-3.5-cn.json.br b/lib/search/indexes/github-docs-3.5-cn.json.br index fcb0fa533d..9db8ca11c6 100644 --- a/lib/search/indexes/github-docs-3.5-cn.json.br +++ b/lib/search/indexes/github-docs-3.5-cn.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:3257878334e5f9e0a9391a6167949a11bb359ce50fbd56184db84efb80099d19 -size 1722700 +oid sha256:bba45f08cc24e290f879ead0789165de32356379cfcd2f7598841e3c119c958b +size 1723424 diff --git a/lib/search/indexes/github-docs-3.5-en-records.json.br b/lib/search/indexes/github-docs-3.5-en-records.json.br index f65b22c1f2..a77cdde9dc 100644 --- a/lib/search/indexes/github-docs-3.5-en-records.json.br +++ b/lib/search/indexes/github-docs-3.5-en-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:b92282f5cc18e4048a960df90ab8e2077f78ce1fe79fdbfb42bf3750f1a72978 -size 1116592 +oid sha256:b38a22ba4cf2101435de7017630d4d05c2c5308e8da67baffd34827c3cf43648 +size 1116683 diff --git a/lib/search/indexes/github-docs-3.5-en.json.br b/lib/search/indexes/github-docs-3.5-en.json.br index 1b50cf4cf7..1acbb77e6c 100644 --- a/lib/search/indexes/github-docs-3.5-en.json.br +++ b/lib/search/indexes/github-docs-3.5-en.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:d4b23c7d5c1cd9ad9735cbd5f56f6dd758f771205a65dccf27eea36bcea97626 -size 4448424 +oid sha256:f71d1084b46c6023d961caf68d95facd1f6e1c837ab7853c70e29c3aeca8718c +size 4450243 diff --git a/lib/search/indexes/github-docs-3.5-es-records.json.br b/lib/search/indexes/github-docs-3.5-es-records.json.br index c6a1552a95..a149e98002 100644 --- a/lib/search/indexes/github-docs-3.5-es-records.json.br +++ b/lib/search/indexes/github-docs-3.5-es-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:0c08c3fc936b6ad1bd6b79d55ddd7450b36c501564665e08fb9a5275bb3e82ae -size 749938 +oid sha256:1c395a071f17ef835c66ec93db66855535b492b5c86cf0f930c8a60429a3223b +size 749922 diff --git a/lib/search/indexes/github-docs-3.5-es.json.br b/lib/search/indexes/github-docs-3.5-es.json.br index 39a1a8e904..1cda202716 100644 --- a/lib/search/indexes/github-docs-3.5-es.json.br +++ b/lib/search/indexes/github-docs-3.5-es.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:40d9010b959a0ef2887895ce19de835eaa389c0ba302b91f7d2a2cda5feb6f93 -size 3277194 +oid sha256:dd7c1e8d78cbbe033da660d82592e5777ff8b6990a37f49b1e86fe883d44931e +size 3275943 diff --git a/lib/search/indexes/github-docs-3.5-ja-records.json.br b/lib/search/indexes/github-docs-3.5-ja-records.json.br index 206cdaeafc..a2257225fe 100644 --- a/lib/search/indexes/github-docs-3.5-ja-records.json.br +++ b/lib/search/indexes/github-docs-3.5-ja-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:561c60c65502cb768911cc157ba7ca17df507a68de4bd432623364f1a7b293de -size 823527 +oid sha256:bacb7da25c217f4da56b29ad7e845e19dca265642fbf961c799f9df7fe9efc9d +size 823641 diff --git a/lib/search/indexes/github-docs-3.5-ja.json.br b/lib/search/indexes/github-docs-3.5-ja.json.br index b03636a361..34647b8ae2 100644 --- a/lib/search/indexes/github-docs-3.5-ja.json.br +++ b/lib/search/indexes/github-docs-3.5-ja.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:5bf779133385c7f0f215f6c04d12c98ba00440acab1c8b0cf3cd081762838f75 -size 4552062 +oid sha256:fb46d9b891c1ddb0e137d856739783546eb6b997abdd2d59637320fa2b9eaa28 +size 4552807 diff --git a/lib/search/indexes/github-docs-3.5-pt-records.json.br b/lib/search/indexes/github-docs-3.5-pt-records.json.br index 925faead03..552530a747 100644 --- a/lib/search/indexes/github-docs-3.5-pt-records.json.br +++ b/lib/search/indexes/github-docs-3.5-pt-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:048d23617ca3c58e68cfa056f73234438a9d074c7e940bc318209f14760ae145 -size 738394 +oid sha256:9b43be8372fb3c3ab3bcbd457e838abc04d54cef6896c3332b7e46fda697c2a0 +size 738498 diff --git a/lib/search/indexes/github-docs-3.5-pt.json.br b/lib/search/indexes/github-docs-3.5-pt.json.br index 623a2fd60d..3880b3a3bc 100644 --- a/lib/search/indexes/github-docs-3.5-pt.json.br +++ b/lib/search/indexes/github-docs-3.5-pt.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:e94d635e64e4003c54f412f6f62e9a4e9e87550011a60f891e9abaea92804186 -size 3156135 +oid sha256:1a60fdefe76fe32a4831ad9369f2486341963d1deb474faa3571849c82580394 +size 3157200 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 384f51f59f..7dc8b64d92 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:990a8742728b40d5e80adfb32006d471a05eebaf3fb0760ab9c2ec827532c889 -size 982694 +oid sha256:12f2cff007bd5fed20533c08f3e4d19faf132dc1f359230630b68b6362ab2fc0 +size 983314 diff --git a/lib/search/indexes/github-docs-dotcom-cn.json.br b/lib/search/indexes/github-docs-dotcom-cn.json.br index 30956a10fc..594a52621c 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:d6cfaf023105b9ed18ca6acb60ccc57868d7314ca6d2b1be4531125f77e5357e -size 1720007 +oid sha256:52c3209db8f5a994b79eef0efb581f8a0e477ddc7664fb7e90bb477e37e6a337 +size 1720728 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 f9e5f3d7bc..140c830876 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:323fc871c08f611c55778a643977d966e056d8726701d6521fb8a78a0e4755a4 -size 1344735 +oid sha256:80adb24720c636c67ecc720241eeb773f7847e00cad697e62ad47d34be47ff71 +size 1345577 diff --git a/lib/search/indexes/github-docs-dotcom-en.json.br b/lib/search/indexes/github-docs-dotcom-en.json.br index a1d5c4558d..437baf7238 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:effd75d511eb75a851198e362255d438dd8e170e5c18e591d5274acc8bfbf613 -size 5079957 +oid sha256:e3491a70840d3113999dc0a3435930501e7784fbd83547133f52374cb8713c57 +size 5080814 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 f4a4d4d6e9..e4a0203517 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:0150788c9232174e003e377c84aafc0bb18e049a57bc1fd47529309eec7a6afa -size 886608 +oid sha256:c6f4f082d8b079b764e3bd32a8f60b194fd3bdbf349eaaeeee0b0b54bd41931a +size 886538 diff --git a/lib/search/indexes/github-docs-dotcom-es.json.br b/lib/search/indexes/github-docs-dotcom-es.json.br index e2886c910b..ad69e26e7e 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:9cf0471a7854d403a2c2e3ea1dab34e263a5b911811fc0d958c55b6c18e65302 -size 3685258 +oid sha256:c9765664a8f057a762cda54069551f7d0c760cd90d3636c9bcad7adfc3a23899 +size 3680996 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 99ad775fcf..d0fcaff9ab 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:bf86097b75818d44cacd6a9f9b1993bb520a0f553064916b62cec62408f2922b -size 985672 +oid sha256:93cc5153d273197df153a188e7e0dd72286526d0ba63621419f1b55056dc396d +size 985821 diff --git a/lib/search/indexes/github-docs-dotcom-ja.json.br b/lib/search/indexes/github-docs-dotcom-ja.json.br index 18645ed046..95f259052d 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:f071fd9f4c7ca32339cd51fe19201519d146dfd82f7b4dec97430c3d73a3fe68 -size 5226526 +oid sha256:152ef82e12dac8ff0c3d72617e77a04cf818bb76d90f90df2d07d82958857201 +size 5225693 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 70f9f8cc9d..739a191c3b 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:2b2b0ec92ff33af77f09121bd01545e6be75e01973be4712951d91fcc2b9c4b2 -size 873411 +oid sha256:ed9532a680a49406d1073220dc14edc68a4af0ba942c4a0175a773e06ffa684f +size 873572 diff --git a/lib/search/indexes/github-docs-dotcom-pt.json.br b/lib/search/indexes/github-docs-dotcom-pt.json.br index 9fb58bb861..e0634fe36d 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:08dc1b8c844d7885a304318b721ba989cd5d4b0bca8b7a983819c9bc0c60a471 -size 3566519 +oid sha256:59d69a54873a356fab46d7b298141ce24bbc9d7d0911fb0ba23a54e86c1808f4 +size 3567427 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 f27b6ad2a8..0562dd910f 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:8be5e91959903c4debce4a3ff7aaf7d7cc0bab554f62562dd1ebda467f602211 -size 625416 +oid sha256:271c085436c5d401b83bdd119e50521ae3ca54ffa6efd1686abecdf1d2b3e4a1 +size 625778 diff --git a/lib/search/indexes/github-docs-ghae-cn.json.br b/lib/search/indexes/github-docs-ghae-cn.json.br index dcf9f548c5..13dae183b5 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:d41f660ab40cb3cacb37950a786b5ff67437fac2e2642ac692901b79fc65ab74 -size 1268271 +oid sha256:0e60989a165ae82baa89d10b9de4a894f07b9b24c9e2e80e5183350d23be9da6 +size 1268396 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 50430a1b44..164c994ff4 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:e4e36420e388df8fac8a095eb5691730766d7967403db0b2ef80d894d74962f0 -size 867340 +oid sha256:afdcca2d3c282991752d8b89adff4751d3af0f063cbbfcac05d19de06aebe16a +size 867737 diff --git a/lib/search/indexes/github-docs-ghae-en.json.br b/lib/search/indexes/github-docs-ghae-en.json.br index 4f88c7f3dd..939ddb3dce 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:0b2515505149ab536c37f2e397e453ec645ef1d08ceb90f1387c475d5a684b39 -size 3406428 +oid sha256:ffff76f0515d11d0ba3fb240e5c5c1813f4b224e2f4163291e84e7414ea4242f +size 3407445 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 d1f062447b..f3733d066a 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:e0cefbc6d49a28d39e41a6d7df2066c52685b682024947eaa79456c6890eadc6 -size 582746 +oid sha256:026ec26bf72a141f72dace204cb221abe77ff4194f4e112b1fbf49df65a5ad8a +size 582715 diff --git a/lib/search/indexes/github-docs-ghae-es.json.br b/lib/search/indexes/github-docs-ghae-es.json.br index fb0f15b5b6..8aad0c2fe7 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:e464beb621f2f8534fbeb0f472c2659b6e3492551845abf92be034577c83ce47 -size 2462887 +oid sha256:2b11347e71335696d8b16377e7c73b25d6bd22a6e44211e595ae2548e1bd567b +size 2461622 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 01cdcad25b..6de68cc70c 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:4fe21fe987ac1608da1a6c47cfea8de1413aa4fe6495c7a175d3baceb5ac0d94 -size 635314 +oid sha256:628b994efbc6f9c4f38eeed8b5cfe301cfb3bd4dfc6cae7896181b062438d854 +size 635356 diff --git a/lib/search/indexes/github-docs-ghae-ja.json.br b/lib/search/indexes/github-docs-ghae-ja.json.br index 9efaa5b398..f9177ef68e 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:20d36c012861e81092a5d6a164c8cfd3384028694fbf7f424c0193f2379a2b9c -size 3375622 +oid sha256:36cdb19baac6f22973d4aef044753627e30deba1d4511453f6f14bf885abbc00 +size 3376215 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 5dce2ea989..c8c9c8da11 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:c43cb9c64b92a4ee03e24c2fe4b618696c609ff8e5a980b323887de6acde4175 -size 574771 +oid sha256:cc84d57609d7b94955341e14561a7d87e1bc4e4074ef7a48079acef975f9d886 +size 574797 diff --git a/lib/search/indexes/github-docs-ghae-pt.json.br b/lib/search/indexes/github-docs-ghae-pt.json.br index a293a5ed1b..14312982ef 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:4e612717f355693106415e865b0915c8d1191bc2d0103ede674997488bbfc5c7 -size 2352397 +oid sha256:cf00c70381ae7b280755399d1d7f389f7f09d62a4820c4974c34bdeeef05d1ee +size 2352732 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 5b1088c35c..cb271d8850 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:f8ecabfc74e1b66786205946fafc097687ca288765e60b50cdb07fdfb8be0829 -size 946539 +oid sha256:6459069c42bf4bf45e5b8003b11055ca9bf9a81fb09bf07a0cdd57b02392ae63 +size 947247 diff --git a/lib/search/indexes/github-docs-ghec-cn.json.br b/lib/search/indexes/github-docs-ghec-cn.json.br index f39fe82385..8607a0613f 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:29466009c78538e721494f520cc85d8481c217ae5c28aaec683599cd4a229933 -size 1840147 +oid sha256:abfdd3b7d2030c7ba84eddcd40926e2c4896141aee73add1c3004c97e0cf232d +size 1840447 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 d039d9d5f9..88fbd69fed 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:aad22d2e5cd5f4a7783763d510ce234d28a383d1067f49b9bf4a9034bd978c8d -size 1274444 +oid sha256:9ead62b8dd9c6e5b5aaa165f763b364434d326e0cb3789b9fc0f65f53b64c587 +size 1275208 diff --git a/lib/search/indexes/github-docs-ghec-en.json.br b/lib/search/indexes/github-docs-ghec-en.json.br index b3de29f2e2..7d3216d043 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:d92f88f0fcfbab67ba9874040be3debefe6f324d3006bfad8aefc383723969e8 -size 5056083 +oid sha256:800a56d1b444974e334145b00e7b105a4848827a50dd47552e5a6f941b0383ed +size 5057281 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 7574e4d24d..2bb635ac78 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:cd20b5d99d2cc29cafbdfea52110e09957837400bd76d76463e828202d4502c6 -size 874194 +oid sha256:0bc366337dcfb1097d09e272398477ff98835d19295d21c67a7f0e3be8c48c76 +size 874076 diff --git a/lib/search/indexes/github-docs-ghec-es.json.br b/lib/search/indexes/github-docs-ghec-es.json.br index 4afde16660..349ec8a236 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:2eec4f1a377c548cacdbd28505db61cc7aa8eedd49ce525d9fa2de020f6e07e5 -size 3777845 +oid sha256:1c5bd9625c2404fbbfeea0c53ea00c016b4533b0ef21e3436549108ce581632b +size 3775855 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 6efd2fbf93..29c6ee9f56 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:e73291fc6365e308da37bdeac31243005b30cd3d5e456bd95cd66836f2e3bdd5 -size 953706 +oid sha256:4074bd7034f4ac6e831a754a6d1d3732a735a9031cdc78af509ed0dd1a1cb0d7 +size 953749 diff --git a/lib/search/indexes/github-docs-ghec-ja.json.br b/lib/search/indexes/github-docs-ghec-ja.json.br index 74f49101b1..fb82f36b5d 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:33423912d1999907bf9b3f1de7a2bf8ced68aa4ed25f804e826cd5bae3ea15fa -size 5273408 +oid sha256:445a86088523697cb7e0fa3052a7fffce29b3374e4d8c1210ac4b5d9e42c6d18 +size 5273188 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 7c254e16f4..41fadf9418 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:055953431bbeec50bf2a69c90c9bdd7ef69176d3da0f903c6d2287a3bd52a5b6 -size 861900 +oid sha256:4b6966355e250a4914b9c004c8544fb37af0e95d7d62350307bdb7309ed7d030 +size 862032 diff --git a/lib/search/indexes/github-docs-ghec-pt.json.br b/lib/search/indexes/github-docs-ghec-pt.json.br index 7a5de26f72..6caeb721f5 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:e1d395d4cd3b1f3d3971108cfb7f54fe16959428eb16f0529d95f511ada8e01d -size 3657764 +oid sha256:0b3b986c5caca3e8d002b327c2a83320bd64d59d673f779b9f354bffd64113ea +size 3657972 diff --git a/middleware/contextualizers/graphql.js b/middleware/contextualizers/graphql.js index cfaa047234..14822dcdb5 100644 --- a/middleware/contextualizers/graphql.js +++ b/middleware/contextualizers/graphql.js @@ -1,4 +1,7 @@ -import { readCompressedJsonFileFallbackLazily } from '../../lib/read-json-file.js' +import { + readCompressedJsonFileFallbackLazily, + readCompressedJsonFileFallback, +} from '../../lib/read-json-file.js' import { allVersions } from '../../lib/all-versions.js' const previews = readCompressedJsonFileFallbackLazily('./lib/graphql/static/previews.json') const upcomingChanges = readCompressedJsonFileFallbackLazily( @@ -20,6 +23,17 @@ const explorerUrl = ? 'https://graphql.github.com/explorer' : 'http://localhost:3000' +const graphQLVersionSchemaCache = new Map() +function readGraphQLVersionSchema(graphqlVersion) { + if (!graphQLVersionSchemaCache.has(graphqlVersion)) { + graphQLVersionSchemaCache.set( + graphqlVersion, + readCompressedJsonFileFallback(`lib/graphql/static/schema-${graphqlVersion}.json`) + ) + } + return graphQLVersionSchemaCache.get(graphqlVersion) +} + export default function graphqlContext(req, res, next) { const currentVersionObj = allVersions[req.context.currentVersion] // ignore requests to non-GraphQL reference paths @@ -34,9 +48,7 @@ export default function graphqlContext(req, res, next) { const graphqlVersion = currentVersionObj.miscVersionName req.context.graphql = { - schemaForCurrentVersion: readCompressedJsonFileFallbackLazily( - `lib/graphql/static/schema-${graphqlVersion}.json` - )(), + schemaForCurrentVersion: readGraphQLVersionSchema(graphqlVersion), previewsForCurrentVersion: previews()[graphqlVersion], upcomingChangesForCurrentVersion: upcomingChanges()[graphqlVersion], prerenderedObjectsForCurrentVersion: prerenderedObjects()[graphqlVersion], diff --git a/script/README.md b/script/README.md index c156ae0fd5..4d1c9c813b 100644 --- a/script/README.md +++ b/script/README.md @@ -313,7 +313,7 @@ This script is intended to be used as a git "prepush" hook. If the current branc ### [`prevent-translation-commits.js`](prevent-translation-commits.js) -This script is run as a git precommit hook (installed by husky after npm install). It detects changes to files the in the translations folder and prevents the commit if any changes exist. +This script is run as a git precommit hook (installed by husky after npm install). It detects changes to the files in the translations folder and prevents the commit if any changes exist. --- diff --git a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-profile.md b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-profile.md index cd9ec2833b..bbdf8468ee 100644 --- a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-profile.md +++ b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-profile.md @@ -33,7 +33,7 @@ Las personas que visitan tu perfil también pueden ver la siguiente información - Repositorios y gists que te pertenezcan o en los que contribuyas. {% ifversion fpt or ghes or ghec %}Puedes exhibir lo mejor de tu trabajo si fijas los repositorios y gists en tu perfil. Para obtener más información, consulta la sección "[Anclar elementos en tu perfil](/github/setting-up-and-managing-your-github-profile/pinning-items-to-your-profile)".{% endif %} - Los repositorios que hayas marcado como favoritos{% ifversion fpt or ghec %} y organizado en listas.{% endif %} Para obtener más información, consulta la sección "[Guardar los repositorios marcados como favoritos](/articles/saving-repositories-with-stars/)". - Una descripción general de tu actividad en organizaciones, repositorios y equipos en los que eres más activo. Para obtener más información, consulta la sección "[Mostrar un resumen de tu actividad en tu perfil](/articles/showing-an-overview-of-your-activity-on-your-profile).{% ifversion fpt or ghec %} -- Badges and Achievements that highlight your activity and show if you use {% data variables.product.prodname_pro %} or participate in programs like the {% data variables.product.prodname_arctic_vault %}, {% data variables.product.prodname_sponsors %}, or the {% data variables.product.company_short %} Developer Program. Para obtener más información, consulta la sección "[Personalizar tu perfil](/github/setting-up-and-managing-your-github-profile/personalizing-your-profile#displaying-badges-on-your-profile)".{% endif %} +- Las insignias y los logros que resaltan tu actividad y muestran si utilizas {% data variables.product.prodname_pro %} o si participas en programas como el de la {% data variables.product.prodname_arctic_vault %}, {% data variables.product.prodname_sponsors %} o el Programa de Desarrollador de {% data variables.product.company_short %}. Para obtener más información, consulta la sección "[Personalizar tu perfil](/github/setting-up-and-managing-your-github-profile/personalizing-your-profile#displaying-badges-on-your-profile)".{% endif %} También puedes establecer un estado en tu perfil para brindar información sobre tu disponibilidad. Para obtener más información, consulta "[Configurar un estado](/articles/personalizing-your-profile/#setting-a-status)". diff --git a/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-java-with-gradle.md b/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-java-with-gradle.md index 039b2e471e..a154f8a02a 100644 --- a/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-java-with-gradle.md +++ b/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-java-with-gradle.md @@ -22,7 +22,7 @@ shortTitle: Crear & probar con Java & Gradle ## Introducción -Esta guía te muestra cómo crear un flujo de trabajo que realiza la integración continua (CI) para tu proyecto Java usando el sistema de construcción Gradle. El flujo de trabajo que creas te permitirá ver cuándo las confirmaciones de una solicitud de extracción causan la construcción o las fallas de prueba en tu rama por defecto; este enfoque puede ayudar a garantizar que tu código siempre sea correcto. You can extend your CI workflow to {% ifversion actions-caching %}cache files and{% endif %} upload artifacts from a workflow run. +Esta guía te muestra cómo crear un flujo de trabajo que realiza la integración continua (CI) para tu proyecto Java usando el sistema de construcción Gradle. El flujo de trabajo que creas te permitirá ver cuándo las confirmaciones de una solicitud de extracción causan la construcción o las fallas de prueba en tu rama por defecto; este enfoque puede ayudar a garantizar que tu código siempre sea correcto. Puedes extender tu flujo de IC a {% ifversion actions-caching %}los archivos de caché y{% endif %} cargar artefactos desde una ejecución de grupo de trabajo. {% ifversion ghae %} {% data reusables.actions.self-hosted-runners-software %} diff --git a/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-java-with-maven.md b/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-java-with-maven.md index d666ef58f2..1c55fd1e0a 100644 --- a/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-java-with-maven.md +++ b/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-java-with-maven.md @@ -22,7 +22,7 @@ shortTitle: Crear & probar en Java con Maven ## Introducción -Esta guía te muestra cómo crear un flujo de trabajo que realiza la integración continua (CI) para tu proyecto Java utilizando la herramienta de gestión de proyectos de software Maven. El flujo de trabajo que creas te permitirá ver cuándo las confirmaciones de una solicitud de extracción causan la construcción o las fallas de prueba en tu rama por defecto; este enfoque puede ayudar a garantizar que tu código siempre sea correcto. You can extend your CI workflow to {% ifversion actions-caching %}cache files and{% endif %} upload artifacts from a workflow run. +Esta guía te muestra cómo crear un flujo de trabajo que realiza la integración continua (CI) para tu proyecto Java utilizando la herramienta de gestión de proyectos de software Maven. El flujo de trabajo que creas te permitirá ver cuándo las confirmaciones de una solicitud de extracción causan la construcción o las fallas de prueba en tu rama por defecto; este enfoque puede ayudar a garantizar que tu código siempre sea correcto. Puedes extender tu flujo de IC a {% ifversion actions-caching %}los archivos de caché y{% endif %} cargar artefactos desde una ejecución de grupo de trabajo. {% ifversion ghae %} {% data reusables.actions.self-hosted-runners-software %} diff --git a/translations/es-ES/content/actions/learn-github-actions/expressions.md b/translations/es-ES/content/actions/learn-github-actions/expressions.md index 2f9a532623..693a269693 100644 --- a/translations/es-ES/content/actions/learn-github-actions/expressions.md +++ b/translations/es-ES/content/actions/learn-github-actions/expressions.md @@ -324,9 +324,9 @@ steps: if: {% raw %}${{ failure() }}{% endraw %} ``` -#### failure with conditions +#### falla con las condiciones -You can include extra conditions for a step to run after a failure, but you must still include `failure()` to override the default status check of `success()` that is automatically applied to `if` conditions that don't contain a status check function. +Puedes incluir condiciones adicionales para que un paso se ejecute después de una falla, pero aún debes incluir `failure()` para omitir la verificación de estado predeterminada de `success()` que se aplica automáticamente a las condiciones `if` que no contienen una función de verificación de estado. ##### Ejemplo diff --git a/translations/es-ES/content/actions/learn-github-actions/understanding-github-actions.md b/translations/es-ES/content/actions/learn-github-actions/understanding-github-actions.md index fc5365c0ad..e269783393 100644 --- a/translations/es-ES/content/actions/learn-github-actions/understanding-github-actions.md +++ b/translations/es-ES/content/actions/learn-github-actions/understanding-github-actions.md @@ -86,7 +86,7 @@ Para obtener más información, consulta la sección "[Crear acciones](/actions/ {% data reusables.actions.workflow-basic-example-and-explanation %} -## More complex examples +## Ejemplos más complejos {% data reusables.actions.link-to-example-library %} ## Pasos siguientes diff --git a/translations/es-ES/content/actions/managing-workflow-runs/re-running-workflows-and-jobs.md b/translations/es-ES/content/actions/managing-workflow-runs/re-running-workflows-and-jobs.md index c1ed12e1b1..664305b99c 100644 --- a/translations/es-ES/content/actions/managing-workflow-runs/re-running-workflows-and-jobs.md +++ b/translations/es-ES/content/actions/managing-workflow-runs/re-running-workflows-and-jobs.md @@ -17,7 +17,7 @@ versions: ## Acerca de volver a ejecutar flujos de trabajo y jobs -Volver a ejecutar un flujo de tabajo{% ifversion re-run-jobs %} o los jobs dentro de este{% endif %} utiliza los mismos `GITHUB_SHA` (SHA de confirmación) y `GITHUB_REF` (Git ref) del evento original que activó la ejecución de flujo de trabajo. You can re-run a workflow{% ifversion re-run-jobs %} or jobs in a workflow{% endif %} for up to 30 days after the initial run.{% ifversion re-run-jobs %} You cannot re-run jobs in a workflow once its logs have passed their retention limits. For more information, see "[Usage limits, billing, and administration](/actions/learn-github-actions/usage-limits-billing-and-administration#artifact-and-log-retention-policy)."{% endif %}{% ifversion debug-reruns %} When you re-run a workflow or jobs in a workflow, you can enable debug logging for the re-run. Esto habilitará el registro de diagnóstico del ejecutor y el registro de depuración de pasos para la re-ejecución. Para obtener más información sobre el registro de depuración, consulta la sección "[Habilitar el registro de depuración](/actions/monitoring-and-troubleshooting-workflows/enabling-debug-logging)".{% endif %} +Volver a ejecutar un flujo de tabajo{% ifversion re-run-jobs %} o los jobs dentro de este{% endif %} utiliza los mismos `GITHUB_SHA` (SHA de confirmación) y `GITHUB_REF` (Git ref) del evento original que activó la ejecución de flujo de trabajo. You can re-run a workflow{% ifversion re-run-jobs %} or jobs in a workflow{% endif %} for up to 30 days after the initial run.{% ifversion re-run-jobs %} You cannot re-run jobs in a workflow once its logs have passed their retention limits. Para obtener más información, consulta la sección "[Límites de uso, facturación y adminsitración](/actions/learn-github-actions/usage-limits-billing-and-administration#artifact-and-log-retention-policy)".{% endif %}{% ifversion debug-reruns %} Cuando vuelves a ejecutar un flujo de trabajo o jobs en alguno de ellos, puedes habilitar el registro de depuración para la re-ejecución. Esto habilitará el registro de diagnóstico del ejecutor y el registro de depuración de pasos para la re-ejecución. Para obtener más información sobre el registro de depuración, consulta la sección "[Habilitar el registro de depuración](/actions/monitoring-and-troubleshooting-workflows/enabling-debug-logging)".{% endif %} ## Volver a ejecutar todos los jobs en un flujo de trabajo @@ -139,7 +139,7 @@ gh run rerun --job job-id --debug {% ifversion partial-reruns-with-reusable %} -## Re-running workflows and jobs with reusable workflows +## Volver a ejecutar los flujos de trabajo y los jobs con flujos de trabajo reutilizables {% data reusables.actions.partial-reruns-with-reusable %} diff --git a/translations/es-ES/content/actions/managing-workflow-runs/removing-workflow-artifacts.md b/translations/es-ES/content/actions/managing-workflow-runs/removing-workflow-artifacts.md index 1e8e911b70..320018ff95 100644 --- a/translations/es-ES/content/actions/managing-workflow-runs/removing-workflow-artifacts.md +++ b/translations/es-ES/content/actions/managing-workflow-runs/removing-workflow-artifacts.md @@ -16,7 +16,7 @@ shortTitle: Eliminar los artefactos de un flujo de trabajo {% warning %} -**Warning:** Once you delete an artifact, it cannot be restored. +**Advertencia:** Una vez que borres un artefacto, este no se puede restablecer. {% endwarning %} diff --git a/translations/es-ES/content/actions/using-workflows/events-that-trigger-workflows.md b/translations/es-ES/content/actions/using-workflows/events-that-trigger-workflows.md index f5f491d817..0a0ae0d64a 100644 --- a/translations/es-ES/content/actions/using-workflows/events-that-trigger-workflows.md +++ b/translations/es-ES/content/actions/using-workflows/events-that-trigger-workflows.md @@ -1250,12 +1250,12 @@ on: workflow_dispatch #### Proporcionar entradas -Puedes configurar propiedades de entrada definidas personalmente, valores de entrada predeterminados y entradas requeridas para el evento directamente en tu flujo de trabajo. Cuando activas el evento, puedes proporcionar el `ref` y cualquier `inputs`. When the workflow runs, you can access the input values in the {% ifversion actions-unified-inputs %}`inputs`{% else %}`github.event.inputs`{% endif %} context. Para obtener más información, consulta "[Contextos](/actions/learn-github-actions/contexts)". +Puedes configurar propiedades de entrada definidas personalmente, valores de entrada predeterminados y entradas requeridas para el evento directamente en tu flujo de trabajo. Cuando activas el evento, puedes proporcionar el `ref` y cualquier `inputs`. Cuando el flujo de trabajo se ejecuta, puedes acceder a los valores de entrada en el contexto {% ifversion actions-unified-inputs %}`inputs`{% else %}`github.event.inputs`{% endif %}. Para obtener más información, consulta "[Contextos](/actions/learn-github-actions/contexts)". {% data reusables.actions.inputs-vs-github-event-inputs %} {% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5511 %} -Este ejemplo define las entradas llamadas `logLevel`, `tags` y `environment`. Pasarás los valores para estas entradas al flujo de trabajo cuando lo ejecutes. This workflow then prints the values to the log, using the {% ifversion actions-unified-inputs %}`inputs.logLevel`, `inputs.tags`, and `inputs.environment`{% else %}`github.event.inputs.logLevel`, `github.event.inputs.tags`, and `github.event.inputs.environment`{% endif %} context properties. +Este ejemplo define las entradas llamadas `logLevel`, `tags` y `environment`. Pasarás los valores para estas entradas al flujo de trabajo cuando lo ejecutes. Entonces, este flujo de trabajo imprime los valores en la bitácora, utilizando las propiedades de contexto {% ifversion actions-unified-inputs %}`inputs.logLevel`, `inputs.tags` y `inputs.environment`{% else %}`github.event.inputs.logLevel`, `github.event.inputs.tags` y `github.event.inputs.environment`{% endif %}. ```yaml on: @@ -1306,7 +1306,7 @@ gh workflow run run-tests.yml -f logLevel=warning -f tags=false -f environment=s Para obtener más información, consulta la información del {% data variables.product.prodname_cli %} en la sección "[Ejecutar un flujo de trabajo manualmente](/actions/managing-workflow-runs/manually-running-a-workflow)". {% else %} -This example defines the `name` and `home` inputs and prints them using the {% ifversion actions-unified-inputs %}`inputs.name` and `inputs.home`{% else %}`github.event.inputs.name` and `github.event.inputs.home`{% endif %} contexts. Si no se proporciona un `home`, se imprime el valor predeterminado 'The Octoverse'. +Este ejemplo define las entradas de `name` y `home` y las imprime utilizando los contextos de {% ifversion actions-unified-inputs %}`inputs.name` y `inputs.home`{% else %}`github.event.inputs.name` y `github.event.inputs.home`{% endif %}. Si no se proporciona un `home`, se imprime el valor predeterminado 'The Octoverse'. ```yaml name: Manually triggered workflow diff --git a/translations/es-ES/content/actions/using-workflows/reusing-workflows.md b/translations/es-ES/content/actions/using-workflows/reusing-workflows.md index 17e11fb44d..d672e978a3 100644 --- a/translations/es-ES/content/actions/using-workflows/reusing-workflows.md +++ b/translations/es-ES/content/actions/using-workflows/reusing-workflows.md @@ -48,8 +48,8 @@ Para obtener más información, consulta la sección "[Crear flujos de trabajo i Un flujo de trabajo reutilizable puede utilizar otro de ellos si {% ifversion ghes or ghec or ghae %}alguna{% else %}cualquiera{% endif %} de las siguientes condiciones es verdadera: * Ambos flujos de trabajo están en el mismo repositorio. -* The called workflow is stored in a public repository{% ifversion actions-workflow-policy %}, and your {% ifversion ghec %}enterprise{% else %}organization{% endif %} allows you to use public reusable workflows{% endif %}.{% ifversion ghes or ghec or ghae %} -* El flujo de trabajo llamado se almacena en un repositorio interno y los ajustes de dicho repositorio permiten que se acceda a él. For more information, see {% ifversion internal-actions %}"[Sharing actions and workflows with your enterprise](/actions/creating-actions/sharing-actions-and-workflows-with-your-enterprise){% else %}"[Managing {% data variables.product.prodname_actions %} settings for a repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#allowing-access-to-components-in-an-internal-repository){% endif %}."{% endif %} +* El flujo de trabajo llamado se almacena en un repositorio público{% ifversion actions-workflow-policy %} y tu {% ifversion ghec %}empresa{% else %}organización{% endif %} te permite utilizar flujos de trabajo reutilizables y públicos{% endif %}.{% ifversion ghes or ghec or ghae %} +* El flujo de trabajo llamado se almacena en un repositorio interno y los ajustes de dicho repositorio permiten que se acceda a él. Para obtener más información, consulta la sección {% ifversion internal-actions %}"[Compartir acciones y flujos de trabajo con tu empresa](/actions/creating-actions/sharing-actions-and-workflows-with-your-enterprise){% else %}"[Administrar los ajustes de las {% data variables.product.prodname_actions %} en un repositorio](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#allowing-access-to-components-in-an-internal-repository){% endif %}".{% endif %} ## Utilizar ejecutores @@ -312,7 +312,7 @@ Para obtener más información sobre cómo utilizar la API de REST para consulta {% ifversion partial-reruns-with-reusable %} -## Re-running workflows and jobs with reusable workflows +## Volver a ejecutar los flujos de trabajo y los jobs con flujos de trabajo reutilizables {% data reusables.actions.partial-reruns-with-reusable %} @@ -322,4 +322,4 @@ Para obtener más información sobre cómo utilizar la API de REST para consulta Para seguir aprendiendo sobre las {% data variables.product.prodname_actions %}, consulta la sección "[Eventos que activan flujos de trabajo](/actions/learn-github-actions/events-that-trigger-workflows)". -{% ifversion restrict-groups-to-workflows %}You can standardize deployments by creating a self-hosted runner group that can only execute a specific reusable workflow. Para obtener más información, consulta la sección "[Administrar acceso a los ejecutores auto-hospedados utilizando grupos](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups)".{% endif %} +{% ifversion restrict-groups-to-workflows %}Puedes estandarizar los despliegues creando un grupo de ejecutores auto-hospedados que solo ejecute un flujo de trabajo reutilizable. Para obtener más información, consulta la sección "[Administrar acceso a los ejecutores auto-hospedados utilizando grupos](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups)".{% endif %} diff --git a/translations/es-ES/content/admin/configuration/configuring-github-connect/about-github-connect.md b/translations/es-ES/content/admin/configuration/configuring-github-connect/about-github-connect.md index 1ce19079d9..60eb4f8481 100644 --- a/translations/es-ES/content/admin/configuration/configuring-github-connect/about-github-connect.md +++ b/translations/es-ES/content/admin/configuration/configuring-github-connect/about-github-connect.md @@ -26,14 +26,14 @@ Después de habilitar {% data variables.product.prodname_github_connect %}, podr Después de que configuras la conexión entre {% data variables.product.product_location %} y {% data variables.product.prodname_ghe_cloud %}, puedes habilitar las características individuales de {% data variables.product.prodname_github_connect %} para tu empresa. -| Característica | Descripción | Más información | -| ---------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |{% ifversion ghes %} +| Característica | Descripción | Más información | +| ---------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |{% ifversion ghes %} | Sincronización automática de licencias de usuario | Administra el uso de licencias en todos los despliegues de tu {% data variables.product.prodname_enterprise %} sincronizando las licencias de usuario automáticamente desde {% data variables.product.product_location %} hacia {% data variables.product.prodname_ghe_cloud %}. | "[Habilitar la sincronización automática de licencias de usuario para tu empresa](/admin/configuration/configuring-github-connect/enabling-automatic-user-license-sync-for-your-enterprise)"{% endif %}{% ifversion ghes or ghae %} | {% data variables.product.prodname_dependabot %} | Permitir que los usuarios encuentren y corrijan vulnerabilidades en las dependencias de código. | "[Habilitar el {% data variables.product.prodname_dependabot %} en tu empresa](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)"{% endif %} -| Acciones de {% data variables.product.prodname_dotcom_the_website %} | Permite que los usuarios utilicen acciones desde {% data variables.product.prodname_dotcom_the_website %} en los archivos de flujo de trabajo. | "[Enabling automatic access to {% data variables.product.prodname_dotcom_the_website %} actions using {% data variables.product.prodname_github_connect %}](/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect)"{% ifversion server-statistics %} +| Acciones de {% data variables.product.prodname_dotcom_the_website %} | Permite que los usuarios utilicen acciones desde {% data variables.product.prodname_dotcom_the_website %} en los archivos de flujo de trabajo. | "[Habilitar el acceso automático a las acciones de {% data variables.product.prodname_dotcom_the_website %} utilizando {% data variables.product.prodname_github_connect %}](/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect)"{% ifversion server-statistics %} | {% data variables.product.prodname_server_statistics %} | Analiza tus propios datos agregados de GitHub Enterprise Server y ayúdanos a mejorar los productos de GitHub. | "[Habilitar el {% data variables.product.prodname_server_statistics %} en tu empresa](/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise)"{% endif %} -| Búsqueda unificada | Permite que los usuarios incluyan repositorios en {% data variables.product.prodname_dotcom_the_website %} en los resultados de la bùsqueda cuando buscas desde {% data variables.product.product_location %}. | "[Habilitar la {% data variables.product.prodname_unified_search %} para tu empresa](/admin/configuration/configuring-github-connect/enabling-unified-search-for-your-enterprise)" | -| Contribuciones unificadas | Permitir que los usuarios incluyan conteos de contribuciones anonimizadas para su trabajo en {% data variables.product.product_location %} en su gráfica de contribuciones en{% data variables.product.prodname_dotcom_the_website %}. | "[Habilitar las {% data variables.product.prodname_unified_contributions %} para tu empresa](/admin/configuration/configuring-github-connect/enabling-unified-contributions-for-your-enterprise)" | +| Búsqueda unificada | Permite que los usuarios incluyan repositorios en {% data variables.product.prodname_dotcom_the_website %} en los resultados de la bùsqueda cuando buscas desde {% data variables.product.product_location %}. | "[Habilitar la {% data variables.product.prodname_unified_search %} para tu empresa](/admin/configuration/configuring-github-connect/enabling-unified-search-for-your-enterprise)" | +| Contribuciones unificadas | Permitir que los usuarios incluyan conteos de contribuciones anonimizadas para su trabajo en {% data variables.product.product_location %} en su gráfica de contribuciones en{% data variables.product.prodname_dotcom_the_website %}. | "[Habilitar las {% data variables.product.prodname_unified_contributions %} para tu empresa](/admin/configuration/configuring-github-connect/enabling-unified-contributions-for-your-enterprise)" | ## Transmisión de datos para {% data variables.product.prodname_github_connect %} diff --git a/translations/es-ES/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md b/translations/es-ES/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md index 71d0d7f911..076efb9082 100644 --- a/translations/es-ES/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md +++ b/translations/es-ES/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md @@ -26,9 +26,9 @@ Antes de que incluyas las {% data variables.product.prodname_actions %} en una e Deberías crear un plan que rija el uso de las {% data variables.product.prodname_actions %} en tu empersa y logre tus obligaciones de cumplimiento. -Determine which actions {% ifversion actions-workflow-policy %}and reusable workflows{% endif %} your developers will be allowed to use. {% ifversion ghes %}First, decide whether you'll enable access to actions {% ifversion actions-workflow-policy %}and reusable workflows{% endif %} from outside your instance. {% data reusables.actions.access-actions-on-dotcom %} Para obtener más información, consulta la sección "[Acerca de utilizar acciones en tu empresa](/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise)". +Determina qué acciones {% ifversion actions-workflow-policy %}y flujos de trabajo reutilizables{% endif %} se permitirán para que las utilicen tus desarrolladores. {% ifversion ghes %}Primero, decide si habilitarás el acceso a las acciones {% ifversion actions-workflow-policy %}y flujos de trabajo reutilizables{% endif %} desde fuera de tu instancia. {% data reusables.actions.access-actions-on-dotcom %} Para obtener más información, consulta la sección "[Acerca de utilizar acciones en tu empresa](/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise)". -Then,{% else %}First,{% endif %} decide whether you'll allow third-party actions {% ifversion actions-workflow-policy %}and reusable workflows{% endif %} that were not created by {% data variables.product.company_short %}. You can configure the actions {% ifversion actions-workflow-policy %}and reusable workflows{% endif %} that are allowed to run at the repository, organization, and enterprise levels and can choose to only allow actions that are created by {% data variables.product.company_short %}. If you do allow third-party actions{% ifversion actions-workflow-policy %} and reusable workflows{% endif %}, you can limit allowed actions to those created by verified creators or a list of specific actions{% ifversion actions-workflow-policy %} and reusable workflows{% endif %}. Para obtener más información, consulta las secciones "[Administrar los ajustes de {% data variables.product.prodname_actions %} para un repositorio](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#managing-github-actions-permissions-for-your-repository)", "[Inhabilitar o limitar las {% data variables.product.prodname_actions %} para tu organización](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization#managing-github-actions-permissions-for-your-organization)" y "[Requerir políticas para las {% data variables.product.prodname_actions %} en tu empresa](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise#enforcing-a-policy-to-restrict-the-use-of-github-actions-in-your-enterprise)". +Después, {% else %}Primero,{% endif %} decide si permitirás acciones {% ifversion actions-workflow-policy %}y flujos de trabajo reutilizables{% endif %} de terceros que no haya creado {% data variables.product.company_short %}. Puedes configurar las acciones {% ifversion actions-workflow-policy %}y flujos de trabajo reutilizables{% endif %} que se permitirán para ejecutar a nivel de repositorio, organización y empresa y elegir únicamente las acciones que haya creado {% data variables.product.company_short %}. Si permites acciones{% ifversion actions-workflow-policy %} y flujos de trabajo reutilizables{% endif %} de terceros, puedes limitar las acciones permitidas a aquellas de los creadores verificados o una lista de acciones{% ifversion actions-workflow-policy %} y flujos de trabajo reutilizables{% endif %} específicos. Para obtener más información, consulta las secciones "[Administrar los ajustes de {% data variables.product.prodname_actions %} para un repositorio](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#managing-github-actions-permissions-for-your-repository)", "[Inhabilitar o limitar las {% data variables.product.prodname_actions %} para tu organización](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization#managing-github-actions-permissions-for-your-organization)" y "[Requerir políticas para las {% data variables.product.prodname_actions %} en tu empresa](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise#enforcing-a-policy-to-restrict-the-use-of-github-actions-in-your-enterprise)". {% ifversion actions-workflow-policy %} ![Captura de pantalla de las políticas de {% data variables.product.prodname_actions %}](/assets/images/help/organizations/enterprise-actions-policy-with-workflows.png) @@ -111,15 +111,15 @@ Finalmente, deberías considerar el fortalecimiento de seguridad para los ejecut {% data reusables.actions.about-artifacts %} Para obtener más información, consulta la sección "[Almacenar datos de flujo de trabajo como artefactos](/actions/advanced-guides/storing-workflow-data-as-artifacts)". -{% ifversion actions-caching %}{% data variables.product.prodname_actions %} also has a caching system that you can use to cache dependencies to speed up workflow runs. Para obtener más información, consulta la sección "[Almacenar las dependencias en caché para agilizar los flujos de trabajo](/actions/using-workflows/caching-dependencies-to-speed-up-workflows)".{% endif %} +{% ifversion actions-caching %}{% data variables.product.prodname_actions %} tambièn tiene un sistema de almacenamiento en cachè que puedes utilizar para almacenar las dependencias en caché para agilizar las ejecuciones de flujo de trabajo. Para obtener más información, consulta la sección "[Almacenar las dependencias en caché para agilizar los flujos de trabajo](/actions/using-workflows/caching-dependencies-to-speed-up-workflows)".{% endif %} {% ifversion ghes %} -You must configure external blob storage for workflow artifacts{% ifversion actions-caching %}, caches,{% endif %} and other workflow logs. Decide qué proveedor de almacenamiento compatible utilizará tu empresa. Para obtener más información, consulta la sección "[Iniciar con las {% data variables.product.prodname_actions %} para {% data variables.product.product_name %}](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server#external-storage-requirements)". +Debes configurar el almacenamiento de blobs externo para los artefactos de flujos de trabajo{% ifversion actions-caching %}, cachés, {% endif %} y otras bitácoras de flujo de trabajo. Decide qué proveedor de almacenamiento compatible utilizará tu empresa. Para obtener más información, consulta la sección "[Iniciar con las {% data variables.product.prodname_actions %} para {% data variables.product.product_name %}](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server#external-storage-requirements)". {% endif %} {% ifversion ghec or ghes %} -You can use policy settings for {% data variables.product.prodname_actions %} to customize the storage of workflow artifacts{% ifversion actions-caching %}, caches,{% endif %} and log retention. Para obtener más información, consulta la sección "[Requerir políticas para las {% data variables.product.prodname_actions %} en tu empresa](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise)". +Puedes utilizar los ajustes de política para que {% data variables.product.prodname_actions %} personalice el almacenamiento de los artefactos de flujo de trabajo{% ifversion actions-caching %}, cachés{% endif %} y retención de bitácoras. Para obtener más información, consulta la sección "[Requerir políticas para las {% data variables.product.prodname_actions %} en tu empresa](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise)". {% endif %} diff --git a/translations/es-ES/content/admin/user-management/managing-organizations-in-your-enterprise/restoring-a-deleted-organization.md b/translations/es-ES/content/admin/user-management/managing-organizations-in-your-enterprise/restoring-a-deleted-organization.md index 19f7890644..212aa607bd 100644 --- a/translations/es-ES/content/admin/user-management/managing-organizations-in-your-enterprise/restoring-a-deleted-organization.md +++ b/translations/es-ES/content/admin/user-management/managing-organizations-in-your-enterprise/restoring-a-deleted-organization.md @@ -25,15 +25,15 @@ You can also use the audit log to help you manually re-add teams and organizatio {% data reusables.enterprise_site_admin_settings.access-settings %} 1. Under "Search users, organizations, enterprises, teams, repositories, gists, and applications", search for the organization. - ![Screenshot of the search field and Search button](/assets/images/enterprise/stafftools/search-field.png) + ![Captura de pantalla del campo y botón de búsqueda](/assets/images/enterprise/stafftools/search-field.png) -1. Under "Deleted accounts", to the right of the organization you want to restore, select the {% octicon "kebab-horizontal" aria-label="The edit icon" %} dropdown menu, then click **Recreate**. +1. Deabjo de "Cuentas borradas", a la derecha de la organización que quieres restablecer, selecciona el menú desplegable {% octicon "kebab-horizontal" aria-label="The edit icon" %} y luego haz clic en **Recrear**. - ![Screenshot of the dropdown menu for a deleted organization](/assets/images/enterprise/stafftools/recreate-organization.png) + ![Captura de pantalla del menú desplegable para una organización borrada](/assets/images/enterprise/stafftools/recreate-organization.png) -## Restoring members and teams +## Restablecer miembros y equipos -You can use the audit log to find a list of the previous members and teams of the organization, then recreate them manually. For more information about using the audit log, see "[Auditing users across your enterprise](/admin/user-management/managing-users-in-your-enterprise/auditing-users-across-your-enterprise)." +Puedes utilizar la bitácora de auditoría para encontrar una lista de los miembros y equipos anteriores de la organización y luego recrearlos manualmente. Para obtener más información sobre cómo utilizar la bitácora de auditoría, consulta la sección "[Auditar a los usuarios en toda tu empresa](/admin/user-management/managing-users-in-your-enterprise/auditing-users-across-your-enterprise)". En todas las frases de búsqueda siguientes, reemplaza a ORGANIZATION con el nombre de la organizacióny a TEAM con el del equipo. diff --git a/translations/es-ES/content/admin/user-management/managing-repositories-in-your-enterprise/restoring-a-deleted-repository.md b/translations/es-ES/content/admin/user-management/managing-repositories-in-your-enterprise/restoring-a-deleted-repository.md index 98148a4601..cc100ed98b 100644 --- a/translations/es-ES/content/admin/user-management/managing-repositories-in-your-enterprise/restoring-a-deleted-repository.md +++ b/translations/es-ES/content/admin/user-management/managing-repositories-in-your-enterprise/restoring-a-deleted-repository.md @@ -1,6 +1,6 @@ --- title: Restaurando un repositorio eliminado -intro: You can restore deleted repositories to recover their contents. +intro: Puedes restablecer los repositorios borrados para recuperar su contenido. permissions: Enterprise owners can restore a deleted repository. versions: ghes: '*' diff --git a/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/updating-your-github-access-credentials.md b/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/updating-your-github-access-credentials.md index f4d1f6669d..c6eb16217d 100644 --- a/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/updating-your-github-access-credentials.md +++ b/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/updating-your-github-access-credentials.md @@ -25,11 +25,11 @@ shortTitle: Actualizar las credenciales de acceso 2. Ingresa la dirección de correo electrónico asociada con tu cuenta de {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} y luego haz clic en **Enviar correo electrónico para restablecer contraseña.** El correo electrónico se enviará a la dirección de respaldo en caso de que la hayas configurado. ![Diálogo de solicitud de correo electrónico de restablecimiento de contraseña](/assets/images/help/settings/password-recovery-email-request.png) 3. Te enviaremos por correo electrónico un enlace que te permitirá restablecer la contraseña. Debes hacer clic en este enlace dentro de las 3 horas posteriores a haber recibido el correo electrónico. Si no recibiste un correo electrónico de nuestra parte, asegúrate de revisar la carpeta de spam. 4. Si habilitaste la autenticación bifactorial, se te pedirán tus credenciales de 2FA: - * If you have {% data variables.product.prodname_mobile %}, you will be sent a push notification to verify your identity. Open the push notification or the {% data variables.product.prodname_mobile %} app and enter the two-digit code shown to you on the password reset page in your browser. ![Two-factor {% data variables.product.prodname_mobile %} authentication prompt](/assets/images/help/2fa/2fa-mobile-challenge-password-reset.png) - * To skip using GitHub Mobile to verify, click **Enter two-factor authentication or recovery code**. ![Two-factor GitHub Mobile authentication prompt on {% data variables.product.product_name %} with "Enter two-factor authentication or recovery code" highlighted](/assets/images/help/2fa/2fa-github-mobile-password-reset.png) + * Si tienes {% data variables.product.prodname_mobile %}, se te enviará una notificación de subida para verificar tu identidad. Abre la notificación de subida o la app de {% data variables.product.prodname_mobile %} e ingresa el código de dos dígitos que se muestra en la página de restablecimiento de contraseña en tu buscador. ![Mensaje de autenticación bifactorial de {% data variables.product.prodname_mobile %}](/assets/images/help/2fa/2fa-mobile-challenge-password-reset.png) + * Para omitir el uso de GitHub Mobile para la verificación, haz clic en **Ingresar autenticación bifactorial o código de recuperación**. ![Mensaje de autenticación bifactorial de GitHub Mobile en {% data variables.product.product_name %} con el mensaje de "ingresar autenticación bifactorial o código de recuperación" resaltado](/assets/images/help/2fa/2fa-github-mobile-password-reset.png) * Teclea tu código de autenticación o uno de tus códigos de recuperación y haz clic en **Verificar**. ![Mensaje de autenticación bifactorial](/assets/images/help/2fa/2fa-password-reset.png) - * If you have added a security key to your account, click **Use security key** instead of typing an authentication code. - * If you have set up [{% data variables.product.prodname_mobile %}](https://github.com/mobile), click **Authenticate with GitHub Mobile** instead. + * Si agregaste una clave de seguridad a tu cuenta, haz clic en **Utilizar llave de seguridad** en vez de teclear un código de autenticación. + * Si configuraste [{% data variables.product.prodname_mobile %}](https://github.com/mobile), haz clic en **Autenticarse con GitHub Mobile** en su lugar. 5. Teclea una contraseña nueva, confírmala y haz clic en **Cambiar contraseña**. Para recibir ayuda para crear una contraseña segura, consulta "[Crear una contraseña segura](/articles/creating-a-strong-password)." {% ifversion fpt or ghec %}![Password recovery box](/assets/images/help/settings/password-recovery-page.png){% else %} ![Casilla de recuperación de contraseña](/assets/images/enterprise/settings/password-recovery-page.png){% endif %} diff --git a/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/running-codeql-code-scanning-in-a-container.md b/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/running-codeql-code-scanning-in-a-container.md index fe87597306..54eb1e760e 100644 --- a/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/running-codeql-code-scanning-in-a-container.md +++ b/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/running-codeql-code-scanning-in-a-container.md @@ -30,7 +30,7 @@ topics: Si estás configurando el {% data variables.product.prodname_code_scanning %} para un lenguaje compilado, y estás compilando el código en un ambiente contenido, el análisis podría fallar con el mensaje de error "No source code was seen during the build". Esto indica que {% data variables.product.prodname_codeql %} no fue capaz de monitorear tu código mientras se compilaba. -Debes ejecutar a {% data variables.product.prodname_codeql %} dentro del mismo contenedor en el que compilaste tu código. This applies whether you are using the {% data variables.product.prodname_codeql_cli %}{% ifversion codeql-runner-supported %}, the {% data variables.product.prodname_codeql_runner %},{% endif %} or {% data variables.product.prodname_actions %}. For the {% data variables.product.prodname_codeql_cli %} {% ifversion codeql-runner-supported %}or the {% data variables.product.prodname_codeql_runner %}{% endif %}, see "[Installing {% data variables.product.prodname_codeql_cli %} in your CI system](/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system)"{% ifversion codeql-runner-supported %} or "[Running {% data variables.product.prodname_codeql_runner %} in your CI system](/code-security/secure-coding/running-codeql-runner-in-your-ci-system)"{% endif %} for more information. Si estás utilizando {% data variables.product.prodname_actions %}, configura tu flujo de trabajo para ejecutar todas las acciones en el mismo contenedor. Para obtener más información, consulta la sección "[Ejemplo de flujo de trabajo](#example-workflow)". +Debes ejecutar a {% data variables.product.prodname_codeql %} dentro del mismo contenedor en el que compilaste tu código. Esto aplica a cuando utilizas el {% data variables.product.prodname_codeql_cli %}{% ifversion codeql-runner-supported %}, el {% data variables.product.prodname_codeql_runner %},{% endif %} o {% data variables.product.prodname_actions %}. Para el {% data variables.product.prodname_codeql_cli %} {% ifversion codeql-runner-supported %}o el {% data variables.product.prodname_codeql_runner %}{% endif %}, consulta la sección "[Instalar el {% data variables.product.prodname_codeql_cli %} en tu sistema de IC](/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system)"{% ifversion codeql-runner-supported %} o "[Ejecutar el {% data variables.product.prodname_codeql_runner %} en tu sistema de IC](/code-security/secure-coding/running-codeql-runner-in-your-ci-system)"{% endif %} para obtener más información. Si estás utilizando {% data variables.product.prodname_actions %}, configura tu flujo de trabajo para ejecutar todas las acciones en el mismo contenedor. Para obtener más información, consulta la sección "[Ejemplo de flujo de trabajo](#example-workflow)". ## Dependencias diff --git a/translations/es-ES/content/desktop/index.md b/translations/es-ES/content/desktop/index.md index b77c0e6ebf..67f039c407 100644 --- a/translations/es-ES/content/desktop/index.md +++ b/translations/es-ES/content/desktop/index.md @@ -1,7 +1,7 @@ --- title: GitHub Desktop shortTitle: GitHub Desktop -intro: 'With GitHub Desktop, you can interact with GitHub using a GUI instead of the command line or a web browser. You can use GitHub Desktop to complete most Git commands from your desktop, such as pushing to, pulling from, and cloning remote repositories, attributing commits, and creating pull requests, with visual confirmation of changes.' +intro: 'Con GitHub Desktop, puedes interactuar con GitHub utilizando la IUG en vez de la línea de comandos o un buscador web. Puedes utilizar GitHub Desktop para completar la mayoría de los comandos de Git desde tu escritorio, tal como subir información, extraerla y clonar repositorios remotos, atribuir confirmaciones y crear solicitudes de cambio, todo esto con una confirmación visual de los cambios.' introLinks: overview: /desktop/installing-and-configuring-github-desktop/overview/getting-started-with-github-desktop featuredLinks: diff --git a/translations/es-ES/content/desktop/installing-and-configuring-github-desktop/configuring-and-customizing-github-desktop/configuring-git-for-github-desktop.md b/translations/es-ES/content/desktop/installing-and-configuring-github-desktop/configuring-and-customizing-github-desktop/configuring-git-for-github-desktop.md index e9e4d271b4..2a46e2a7a3 100644 --- a/translations/es-ES/content/desktop/installing-and-configuring-github-desktop/configuring-and-customizing-github-desktop/configuring-git-for-github-desktop.md +++ b/translations/es-ES/content/desktop/installing-and-configuring-github-desktop/configuring-and-customizing-github-desktop/configuring-git-for-github-desktop.md @@ -17,17 +17,17 @@ versions: Si la dirección de correo electrónico que se ajustó en tu configuración de Git no coincide con aquella asociada con la cuenta de {% data variables.product.product_name %} en la que estás actualmente, {% data variables.product.prodname_desktop %} mostrará una advertencia antes de realizar las confirmaciones. -{% data variables.product.prodname_desktop %} también te permite cambiar el nombre de la rama predeterminada que te gustaría utilizar cuando crees repositorios nuevos. By default, {% data variables.product.prodname_desktop %} uses `main` as the default branch name in any new repositories you create. +{% data variables.product.prodname_desktop %} también te permite cambiar el nombre de la rama predeterminada que te gustaría utilizar cuando crees repositorios nuevos. Predeterminadamente, {% data variables.product.prodname_desktop %} utiliza `main` como su nombre de rama predeterminado en cualquier repositorio que crees. {% tip %} -**Tip**: Cualquiera podrá ver la dirección de correo electrónico en tu configuración de Git si haces confirmaciones públicas. For more information, see "[Setting your commit email address](/articles/setting-your-commit-email-address/)." +**Tip**: Cualquiera podrá ver la dirección de correo electrónico en tu configuración de Git si haces confirmaciones públicas. Para obtener más información, consulta la sección "[Establecer tu dirección de correo electrónico de confirmación](/articles/setting-your-commit-email-address/)." {% endtip %} -## Configuring your global author information +## Configurar tu información de autor global -Configuring your global author information in {% data variables.product.prodname_desktop %} will update the name and email address in your global Git configuration. This will be the default name and email address for all new local repositories you create in {% data variables.product.prodname_desktop %}. +El configurar tu información de autor global en {% data variables.product.prodname_desktop %} actualizará el nombre y la dirección de correo electrónico en tu configuración global de Git. Esto será el nombre y dirección de correo electrónico predeterminados para cualquier repositorio local nuevo que crees en {% data variables.product.prodname_desktop %}. {% mac %} @@ -36,7 +36,7 @@ Configuring your global author information in {% data variables.product.prodname {% data reusables.desktop.name-field-git-config %} ![El campo con el nombre de la configuración de Git](/assets/images/help/desktop/mac-name-git-config.png) {% data reusables.desktop.select-email-git-config %} - ![Select email address in Git configuration field](/assets/images/help/desktop/mac-email-git-config.png) + ![Selecciona la dirección de correo electrónico en el campo de configuración de Git](/assets/images/help/desktop/mac-email-git-config.png) {% data reusables.desktop.click-save-git-config %} ![Botón de guardar en el campo de configuración de Git](/assets/images/help/desktop/mac-save-git-config.png) @@ -49,15 +49,15 @@ Configuring your global author information in {% data variables.product.prodname {% data reusables.desktop.name-field-git-config %} ![El campo con el nombre de la configuración de Git](/assets/images/help/desktop/windows-name-git-config.png) {% data reusables.desktop.select-email-git-config %} - ![Select email address in Git configuration field](/assets/images/help/desktop/windows-email-git-config.png) + ![Selecciona la dirección de correo electrónico en el campo de configuración de Git](/assets/images/help/desktop/windows-email-git-config.png) {% data reusables.desktop.click-save-git-config %} ![Botón de guardar en el campo de configuración de Git](/assets/images/help/desktop/windows-save-git-config.png) {% endwindows %} -## Configuring different author information for an individual repository +## Configurar información de autor diferente para un repositorio individual -You can change the name and email address used to author commits in a specific repository. This local Git configuration will override your global Git configuration settings for this one repository only. +Puedes cambiar el nombre y dirección de correo electrónico que se utilizan para crear confirmaciones en un repositorio específico. Esta configuración local de Git anulará los ajustes de configuración globales de Git únicamente para este repositorio. {% mac %} @@ -82,15 +82,15 @@ You can change the name and email address used to author commits in a specific r {% endwindows %} -## Configuring your default branch for new repositories +## Configurar tu rama predeterminada para repositorios nuevos -You can configure the default branch that will be used when you create a new repository in {% data variables.product.prodname_desktop %}. For more information about the default branch, see "[About the default branch](/github/collaborating-with-issues-and-pull-requests/about-branches#about-the-default-branch)." +Puedes configurar una rama predeterminada que se utilizará cuando crees un repositorio en {% data variables.product.prodname_desktop %}. Para obtener más información sobre la rama predeterminada, consulta la sección "[Acerca de la rama predeterminada](/github/collaborating-with-issues-and-pull-requests/about-branches#about-the-default-branch)". {% mac %} {% data reusables.desktop.mac-select-desktop-menu %} 1. En la ventana de preferencias, da clic en **Git**. ![El panel de Git en el menú Preferences (Preferencias)](/assets/images/help/desktop/mac-select-git-pane.png) -1. Under "Default branch name for new repositories", select the default branch name you would like to use, or, to enter a custom name, select "Other...". ![Default branch name selection options](/assets/images/help/desktop/mac-select-default-branch-name.png) +1. Debajo de "Nombre de rama predeterminado para los repositorios nuevos", selecciona el nombre de rama predeterminado que te gustaría utilizar o, para ingresar un nombre personalizado, selecciona "Otro...". ![Opciones de selección del nombre para la rama predeterminada](/assets/images/help/desktop/mac-select-default-branch-name.png) {% data reusables.desktop.click-save-git-config %} ![Botón de guardar en el campo de configuración de Git](/assets/images/help/desktop/repository-settings-git-config-save.png) @@ -100,7 +100,7 @@ You can configure the default branch that will be used when you create a new rep {% data reusables.desktop.windows-choose-options %} 1. En la ventana de Opciones, da clic en **Git**. ![El panel de Git en el menú Options (Opciones)](/assets/images/help/desktop/windows-select-git-pane.png) -1. Under "Default branch name for new repositories", select the default branch name you would like to use, or select "Other..." to enter a custom name. ![Default branch name selection options](/assets/images/help/desktop/windows-select-default-branch-name.png) +1. Debajo de "Nombre de rama predeterminado para los repositorios nuevos", selecciona el nombre de rama predeterminado que te gustaría utilizar o selecciona "Otro..." para ingresar un nombre personalizado. ![Opciones de selección del nombre para la rama predeterminada](/assets/images/help/desktop/windows-select-default-branch-name.png) {% data reusables.desktop.click-save-git-config %} ![Botón de guardar en el campo de configuración de Git](/assets/images/help/desktop/repository-settings-git-config-save.png) diff --git a/translations/es-ES/content/developers/webhooks-and-events/events/github-event-types.md b/translations/es-ES/content/developers/webhooks-and-events/events/github-event-types.md index da083ca248..0046f7e279 100644 --- a/translations/es-ES/content/developers/webhooks-and-events/events/github-event-types.md +++ b/translations/es-ES/content/developers/webhooks-and-events/events/github-event-types.md @@ -39,8 +39,8 @@ Los objetos de los eventos que se devuelven de las terminales de la API de Event | `repo.name` | El nombre del repositorio, el cual incluye también al nombre del propietario. Por ejemplo, `octocat/hello-world` es el nombre del repositorio `hello-world` que pertenece a la cuenta personal `octocat`. | | `repo.url` | La URL de la API de REST que se utiliza para recuperar el objeto del repositorio, el cual incluye información adicional sobre dicho repositorio. | | `payload` | El objeto de la carga útil del evento que es exclusivo para el tipo de evento. En el siguiente ejemplo puedes ver el tipo de evento para el objeto de `payload` de la API de eventos. | -| `public` | Whether the event is visible to all users. | -| `created_at (creado en)` | The date and time when the event was triggered. It is formatted according to ISO 8601. | +| `public` | Si todos los usuarios pueden ver el evento. | +| `created_at (creado en)` | La fecha y hora cuando se activó el evento. Se formatea de acuerdo con el ISO 8601. | | `org` | The organization that was chosen by the actor to perform action that triggers the event.
_The property appears in the event object only if it is applicable._ | | `org.id` | The unique identifier for the organization. | | `org.login` | The name of the organization. | diff --git a/translations/es-ES/content/get-started/onboarding/getting-started-with-your-github-account.md b/translations/es-ES/content/get-started/onboarding/getting-started-with-your-github-account.md index 2a81fa2f62..e489674246 100644 --- a/translations/es-ES/content/get-started/onboarding/getting-started-with-your-github-account.md +++ b/translations/es-ES/content/get-started/onboarding/getting-started-with-your-github-account.md @@ -81,7 +81,7 @@ Para obtener más información sobre cómo autenticarte en {% data variables.pro ### 4. Escribir en {% data variables.product.product_name %} Para que tus comunicaciones sean más claras y organizadas en propuestas y solicitudes de cambios, puedes utilizar el Lenguaje de Marcado Enriquecido de {% data variables.product.prodname_dotcom %} para formatearlas, el cual combina una sintaxis fácil de escribir y de leer con algunas funcionalidades personalizadas. Para obtener más información, consulta "[Acerca de la escritura y el formato en {% data variables.product.prodname_dotcom %}](/github/writing-on-github/about-writing-and-formatting-on-github)." -You can learn {% data variables.product.prodname_dotcom %} Flavored Markdown with the "[Communicate using Markdown](https://github.com/skills/communicate-using-markdown)" course on {% data variables.product.prodname_learning %}. +Puedes aprender el lenguaje de marcado enriquecido de {% data variables.product.prodname_dotcom %} con el curso de "[Comunícate utilizando el lenguaje de marcado](https://github.com/skills/communicate-using-markdown)" que está en {% data variables.product.prodname_learning %}. ### 5. Buscar en {% data variables.product.product_name %} Nuestra búsqueda integrada te permite encontrar lo que estás buscando de entre los muchos repositorios, usuarios y líneas de código que hay en {% data variables.product.product_name %}. Puedes buscar globalmente a través de todo {% data variables.product.product_name %} o limitar tu búsqueda a un repositorio u organización en particular. Para obtener más información sobre los tipos de búsqueda que puedes hacer en {% data variables.product.product_name %}, consulta la sección "[Acerca de buscar en {% data variables.product.prodname_dotcom %}](/github/searching-for-information-on-github/getting-started-with-searching-on-github/about-searching-on-github)". diff --git a/translations/es-ES/content/get-started/quickstart/create-a-repo.md b/translations/es-ES/content/get-started/quickstart/create-a-repo.md index 9c70de0787..4fb42c54ba 100644 --- a/translations/es-ES/content/get-started/quickstart/create-a-repo.md +++ b/translations/es-ES/content/get-started/quickstart/create-a-repo.md @@ -34,7 +34,10 @@ Puedes almacenar varios proyectos en los repositorios de {% data variables.produ {% note %} -**Nota:** Puedes crear repositorios públicos para un proyecto de código abierto. Cuando crees un repositorio público, asegúrate de incluir un [archivo de licencia](https://choosealicense.com/) que determine cómo deseas que se comparta tu proyecto con otros usuarios. {% data reusables.open-source.open-source-guide-repositories %} {% data reusables.open-source.open-source-learning %} +**Notas:** +- You can create public repositories for an open source project. Cuando crees un repositorio público, asegúrate de incluir un [archivo de licencia](https://choosealicense.com/) que determine cómo deseas que se comparta tu proyecto con otros usuarios. {% data reusables.open-source.open-source-guide-repositories %} +- {% data reusables.open-source.open-source-learning %} +- You can also add community health files to your repositories, to set guidelines on how to contribute, keep your repositories safe, and much more. Para obtener más información, consulta "[Crear un archivo de salud predeterminado para la comunidad](/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file)." {% endnote %} diff --git a/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md b/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md index 3f0bf51d40..3f3ecf19a9 100644 --- a/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md +++ b/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md @@ -29,11 +29,11 @@ miniTocMaxHeadingLevel: 3 Puedes habilitar {% data variables.product.prodname_actions %} para tu repositorio. {% data reusables.actions.enabled-actions-description %} Puedes inhabilitar {% data variables.product.prodname_actions %} totalmente para tu repositorio. {% data reusables.actions.disabled-actions-description %} -Alternatively, you can enable {% data variables.product.prodname_actions %} in your repository but limit the actions {% ifversion actions-workflow-policy %}and reusable workflows{% endif %} a workflow can run. +Como alternativa, puedes habilitar las {% data variables.product.prodname_actions %} en tu repositorio pero limitar las acciones {% ifversion actions-workflow-policy %}y flujos de trabajo reutilizables{% endif %} que puede ejecutar un flujo de trabajo. ## Administrar los permisos de {% data variables.product.prodname_actions %} para tu repositorio -You can disable {% data variables.product.prodname_actions %} for a repository, or set a policy that configures which actions{% ifversion actions-workflow-policy %} and reusable workflows{% endif %} can be used in the repository. +Puedes inhabilitar las {% data variables.product.prodname_actions %} para un repositorio o ajustar una política que configure qué acciones{% ifversion actions-workflow-policy %} y flujos de trabajo reutilizables{% endif %} pueden utilizarse en el repositorio. {% note %} @@ -72,7 +72,7 @@ You can disable {% data variables.product.prodname_actions %} for a repository, 1. Haz clic en **Save ** (guardar). {% ifversion fpt or ghec %} -## Controlling changes from forks to workflows in public repositories +## Controlar los cambios de las bifurcaciones para los flujos de trabajo en los repositorios públicos {% data reusables.actions.workflow-run-approve-public-fork %} @@ -86,7 +86,7 @@ Puedes configurar este comportamiento para un repositorio si utilizas el siguien {% data reusables.actions.workflow-run-approve-link %} {% endif %} -## Enabling workflows for forks of private repositories +## Habilitar los flujos de trabajo de los repositorios privados {% data reusables.actions.private-repository-forks-overview %} @@ -94,7 +94,7 @@ Si se inhabilita una política para una {% ifversion ghec or ghae or ghes %}empr {% data reusables.actions.private-repository-forks-options %} -### Configuring the fork policy for a private repository +### Configurar la política de bifurcación de un repositorio privado {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} @@ -147,7 +147,7 @@ Predeterminadamente, cuando creas un repositorio nuevo en tu cuenta personal, no Los miembros de tu empresa pueden utilizar repositorios internos para trabajar en proyectos sin compartir información públicamente. Para obtener más información, consulta la sección "[Acerca de los repositorios](/repositories/creating-and-managing-repositories/about-repositories#about-internal-repositories)". -You can use the steps below to configure whether {% ifversion internal-actions%}actions and {% endif %}workflows in an internal repository can be accessed from outside the repository.{% ifversion internal-actions %} For more information, see "[Sharing actions and workflows with your enterprise](/actions/creating-actions/sharing-actions-and-workflows-with-your-enterprise)." Como alternativa, puedes utilizar la API de REST para configurar u obtener detalles del nivel de acceso. Para obtener más información, consulta las secciones "[Obtener el nivel de acceso para los flujos de trabajo fuera del repositorio](/rest/reference/actions#get-the-level-of-access-for-workflows-outside-of-the-repository#get-the-level-of-access-for-workflows-outside-of-the-repository)" y "[Configurar el nivel de acceso para los flujos de trabajo fuera del repositorio](/rest/reference/actions#get-the-level-of-access-for-workflows-outside-of-the-repository#set-the-level-of-access-for-workflows-outside-of-the-repository)".{% endif %} +Puedes utilizar los siguientes pasos para configurar si se puede acceder a {% ifversion internal-actions%}las acciones y {% endif %}los flujos de trabajo en un repositorio interno desde fuera del mismo.{% ifversion internal-actions %} Para obtener más información, consulta la sección "[Compartir las acciones y los flujos de trabajo con tu empresa](/actions/creating-actions/sharing-actions-and-workflows-with-your-enterprise)". Como alternativa, puedes utilizar la API de REST para configurar u obtener detalles del nivel de acceso. Para obtener más información, consulta las secciones "[Obtener el nivel de acceso para los flujos de trabajo fuera del repositorio](/rest/reference/actions#get-the-level-of-access-for-workflows-outside-of-the-repository#get-the-level-of-access-for-workflows-outside-of-the-repository)" y "[Configurar el nivel de acceso para los flujos de trabajo fuera del repositorio](/rest/reference/actions#get-the-level-of-access-for-workflows-outside-of-the-repository#set-the-level-of-access-for-workflows-outside-of-the-repository)".{% endif %} 1. En {% data variables.product.prodname_dotcom %}, navega hasta la página principal del repositorio interno. 1. Debajo de tu nombre de repositorio, haz clic en {% octicon "gear" aria-label="The gear icon" %}**Configuración**. diff --git a/translations/es-ES/content/rest/guides/index.md b/translations/es-ES/content/rest/guides/index.md index 675a23f225..c416b4bb95 100644 --- a/translations/es-ES/content/rest/guides/index.md +++ b/translations/es-ES/content/rest/guides/index.md @@ -25,4 +25,4 @@ children: - /getting-started-with-the-checks-api --- -Se pretende que esta sección de la documentación te inicie con las aplicaciones reales de la API de {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %}. We'll go over everything you need to know, from authentication to results manipulation to integrating results with other apps. Every tutorial will include a project, and each project will be saved and documented in our public [platform-samples](https://github.com/github/platform-samples) repository. ![El Octocat](/assets/images/electrocat.png) +Se pretende que esta sección de la documentación te inicie con las aplicaciones reales de la API de {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %}. Explicaremos todo lo que necesitas saber, desde la autenticación hasta la manipulación de resultados y cómo integrarlos con otras apps. Cada tutorial incluirá un proyecto y cada proyecto se guardará y documentará en neustro repositorio público de [platform-samples](https://github.com/github/platform-samples). ![El Octocat](/assets/images/electrocat.png) diff --git a/translations/es-ES/content/site-policy/privacy-policies/github-privacy-statement.md b/translations/es-ES/content/site-policy/privacy-policies/github-privacy-statement.md index 832abd6c92..be3895273c 100644 --- a/translations/es-ES/content/site-policy/privacy-policies/github-privacy-statement.md +++ b/translations/es-ES/content/site-policy/privacy-policies/github-privacy-statement.md @@ -177,7 +177,7 @@ We retain and use your information as described in this Privacy Statement, but b If GitHub processes Personal Data other than your profile information, such as information about you GitHub receives from [third parties](/github/site-policy/github-privacy-statement#information-we-collect-from-third-parties), then you may, subject to applicable law, access, update, alter, delete, object to or restrict the processing of your Personal Data by contacting [GitHub Support](https://support.github.com/contact) or [GitHub Premium Support](https://enterprise.githubsupport.com/hc/en-us). -You can adjust the settings on your Account regarding the display of your Personal Data in private or public repositories or Personal Data processed in connection with Community Features (such as the GitHub Feed, the GitHub Globe, GitHub Explore, the GitHub Discussion Leaderboard) through [profile settings](https://github.com/settings/profile). +You can adjust the settings on your Account regarding the display of your Personal Data in private or public repositories or Personal Data processed in connection with Community Features (such as GitHub Feed, GitHub Sponsors, and GitHub Explore) through [profile settings](https://github.com/settings/profile). Additionally, if you are unable to access certain Personal Data we have via the means described above, you can request access by contacting us as described at the bottom of this privacy statement. diff --git a/translations/es-ES/data/features/README.md b/translations/es-ES/data/features/README.md index ff05786031..4e3c55ad3f 100644 --- a/translations/es-ES/data/features/README.md +++ b/translations/es-ES/data/features/README.md @@ -45,7 +45,7 @@ versions: ## Imposición del modelado -El modelo para validar la característica de versionamiento vive en [`tests/helpers/schemas/feature-versions-schema.js`](/tests/helpers/schemas/feature-versions-schema.js) y la ejecuta [`tests/linting/lint-files.js`](/tests/linting/lint-files.js). +El modelo para validar la característica de versionamiento vive en [`tests/helpers/schemas/feature-versions-schema.js`](/tests/helpers/schemas/feature-versions-schema.js) y la ejecuta [`tests/linting/lint-versioning.js`](/tests/linting/lint-versioning.js). ## Script para eliminar las etiquetas de característica diff --git a/translations/es-ES/data/reusables/actions/jobs/section-using-jobs-in-a-workflow-name.md b/translations/es-ES/data/reusables/actions/jobs/section-using-jobs-in-a-workflow-name.md index ac788fb978..f5faa01e05 100644 --- a/translations/es-ES/data/reusables/actions/jobs/section-using-jobs-in-a-workflow-name.md +++ b/translations/es-ES/data/reusables/actions/jobs/section-using-jobs-in-a-workflow-name.md @@ -1 +1 @@ -Use `jobs..name` to set a name for the job, which is displayed in the {% data variables.product.prodname_dotcom %} UI. +Utiliza `jobs..name` para configurar un nombre para el job, lo cuál se muestra en la IU {% data variables.product.prodname_dotcom %}. diff --git a/translations/es-ES/data/reusables/actions/workflows/section-triggering-a-workflow-branches.md b/translations/es-ES/data/reusables/actions/workflows/section-triggering-a-workflow-branches.md index bd48e77bf9..ee1b47e923 100644 --- a/translations/es-ES/data/reusables/actions/workflows/section-triggering-a-workflow-branches.md +++ b/translations/es-ES/data/reusables/actions/workflows/section-triggering-a-workflow-branches.md @@ -29,7 +29,7 @@ on: Cuando un patrón empata con el de `branches-ignore`, el flujo de trabajo no se ejecutará. Los patrones que se definen en `branches` se evalúan contra el nombre de ref de Git. Por ejemplo, el siguiente flujo de trabajo se ejecutaría siempre que haya un evento de `pull_request` a menos de que la solicitud de cambios apunte a: - Una rama de nombre `mona/octocat` (`refs/heads/mona/octocat`) -- A branch whose name matches `releases/**-alpha`, like `releases/beta/3-alpha` (`refs/heads/releases/beta/3-alpha`) +- Una rama cuyo nombre empata con `releases/**-alpha`, como `releases/beta/3-alpha` (`refs/heads/releases/beta/3-alpha`) ```yaml on: diff --git a/translations/es-ES/data/reusables/education/about-github-education-link.md b/translations/es-ES/data/reusables/education/about-github-education-link.md index e81b34c9ae..3293a369bf 100644 --- a/translations/es-ES/data/reusables/education/about-github-education-link.md +++ b/translations/es-ES/data/reusables/education/about-github-education-link.md @@ -1,3 +1,3 @@ -As a student or faculty member at an accredited educational institution, you can apply for {% data variables.product.prodname_education %} benefits, which includes access to {% data variables.product.prodname_global_campus %}. {% data variables.product.prodname_global_campus %} is a portal that allows the GitHub Education Community to access their education benefits—all in one place! The {% data variables.product.prodname_global_campus %} portal includes access to {% data variables.product.prodname_education_community_with_url %}, industry tools used by professional developers, events, [Campus TV](https://www.twitch.tv/githubeducation) content, {% data variables.product.prodname_classroom_with_url %}, and other exclusive features to help students and teachers shape the next generation of software development. +Como alumno o miembro de facultad en una institución educativa acreditada, puedes aplicar para obtener los beneficios de {% data variables.product.prodname_education %}, los cuales incluyen el acceso a {% data variables.product.prodname_global_campus %}. {% data variables.product.prodname_global_campus %} es un portal que permite que la Comunidad de GitHub Education acceda a sus beneficios educativos; ¡todo en un solo lugar! El portal de {% data variables.product.prodname_global_campus %} incluye el acceso a {% data variables.product.prodname_education_community_with_url %}, las herramientas de la industria que utilizan los desarrolladores profesionales, los eventos, el contenido de [Campus TV](https://www.twitch.tv/githubeducation), {% data variables.product.prodname_classroom_with_url %}, y otras características exclusivas para ayudar a los alumnos y profesores a formar la siguiente generación de desarrollo de software. Antes de solicitar un descuento individual, comprueba si tu comunidad de aprendizaje ya está asociada con nosotros como escuela de {% data variables.product.prodname_campus_program %}. Para obtener más información, consulta la sección "[Acerca de la {% data variables.product.prodname_campus_program %}](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-campus-program)". diff --git a/translations/es-ES/data/reusables/getting-started/learning-enterprise.md b/translations/es-ES/data/reusables/getting-started/learning-enterprise.md index bd6e9f26d2..3c96a3e80c 100644 --- a/translations/es-ES/data/reusables/getting-started/learning-enterprise.md +++ b/translations/es-ES/data/reusables/getting-started/learning-enterprise.md @@ -1,3 +1,3 @@ -Los miembros de tu empresa pueden aprender habilidades nuevas completando proyectos divertidos y realistas en su propio repositorio de GitHub con [{% data variables.product.prodname_learning %}](https://skills.github.com/). Each course is a hands-on lesson created by the GitHub community and taught by a friendly bot. +Los miembros de tu empresa pueden aprender habilidades nuevas completando proyectos divertidos y realistas en su propio repositorio de GitHub con [{% data variables.product.prodname_learning %}](https://skills.github.com/). Cada curso es una lección interactiva que creó la comunidad de GitHub, la cual imparte un bot amigable. Para obtener más información, consulta la sección "[Recursos de aprendizaje de Git y de {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/quickstart/git-and-github-learning-resources)". diff --git a/translations/es-ES/data/reusables/getting-started/learning.md b/translations/es-ES/data/reusables/getting-started/learning.md index d7f932f56f..2bec3ae36f 100644 --- a/translations/es-ES/data/reusables/getting-started/learning.md +++ b/translations/es-ES/data/reusables/getting-started/learning.md @@ -1,3 +1,3 @@ -Puedes aprender habilidades nuevas completando proyectos divertidos y realistas en tu propio repositorio de GitHub con [{% data variables.product.prodname_learning %}](https://skills.github.com/). Each course is a hands-on lesson created by the GitHub community and taught by a friendly bot. +Puedes aprender habilidades nuevas completando proyectos divertidos y realistas en tu propio repositorio de GitHub con [{% data variables.product.prodname_learning %}](https://skills.github.com/). Cada curso es una lección interactiva que creó la comunidad de GitHub, la cual imparte un bot amigable. Para obtener más información, consulta la sección "[Recursos de aprendizaje de Git y de {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/quickstart/git-and-github-learning-resources)". diff --git a/translations/es-ES/data/reusables/projects/create-project.md b/translations/es-ES/data/reusables/projects/create-project.md index 2bd6b3aecd..ace958f360 100644 --- a/translations/es-ES/data/reusables/projects/create-project.md +++ b/translations/es-ES/data/reusables/projects/create-project.md @@ -3,6 +3,6 @@ 1. Selecciona el menú desplegable de **Proyecto nuevo** y haz clic en **Proyecto nuevo (Beta)**. ![Proyecto nueuvo](/assets/images/help/issues/new_project_beta.png) -1. When prompted to select a template, click a template or, to start with an empty project, click "Table" or "Board". Then, click **Create**. +1. Cuando se pide seleccionar una plantilla, haz clic en alguna o, para iniciar un proyecto vacío, haz clic en "Tabla" o "Tablero". Luego, haz clic en **Crear**. - ![Screenshot showing template selection modal](/assets/images/help/issues/projects-select-template.png) \ No newline at end of file + ![Captura de pantalla que muestra el modo de selección de plantilla](/assets/images/help/issues/projects-select-template.png) \ No newline at end of file diff --git a/translations/es-ES/data/reusables/projects/create-user-project.md b/translations/es-ES/data/reusables/projects/create-user-project.md index ce33a6bccf..1df7f55db5 100644 --- a/translations/es-ES/data/reusables/projects/create-user-project.md +++ b/translations/es-ES/data/reusables/projects/create-user-project.md @@ -2,6 +2,6 @@ 1. Selecciona el menú desplegable de **Proyecto nuevo** y haz clic en **Proyecto nuevo (Beta)**. ![Proyecto nueuvo](/assets/images/help/issues/new_project_beta.png) -1. When prompted to select a template, click a template or, to start with an empty project, click "Table" or "Board". Then, click **Create**. +1. Cuando se pide seleccionar una plantilla, haz clic en alguna o, para iniciar un proyecto vacío, haz clic en "Tabla" o "Tablero". Luego, haz clic en **Crear**. - ![Screenshot showing template selection modal](/assets/images/help/issues/projects-select-template.png) \ No newline at end of file + ![Captura de pantalla que muestra el modo de selección de plantilla](/assets/images/help/issues/projects-select-template.png) \ No newline at end of file diff --git a/translations/es-ES/data/reusables/secret-scanning/partner-secret-list-private-repo.md b/translations/es-ES/data/reusables/secret-scanning/partner-secret-list-private-repo.md index 1752782d1c..2f3d835100 100644 --- a/translations/es-ES/data/reusables/secret-scanning/partner-secret-list-private-repo.md +++ b/translations/es-ES/data/reusables/secret-scanning/partner-secret-list-private-repo.md @@ -1,4 +1,4 @@ -| Proveedor | Secreto compatible | Secret type | +| Proveedor | Secreto compatible | Tipo de secreto | | ----------- | ----------------------- | ----------------- | | Adafruit IO | Clave de IO de Adafruit | adafruit_io_key | {%- ifversion fpt or ghec or ghes > 3.1 or ghae %} @@ -147,6 +147,8 @@ Plivo | ID de Auth de Plivo | plivo_auth_id{% endif %} Plivo | Token de Autenticación a Plivo | plivo_auth_token{% endif %} Postman | Llave de la API de Postman | postman_api_key Proctorio | Llave de Consumidor de Proctorio | proctorio_consumer_key Proctorio | Llave de Vinculación de Proctorio | proctorio_linkage_key Proctorio | Llave de Registro de Proctorio | proctorio_registration_key Proctorio | Llave de Secreto de Proctorio | proctorio_secret_key Pulumi | Toekn de Acceso a Pulumi | pulumi_access_token {%- ifversion fpt or ghec or ghes > 3.1 or ghae %} PyPI | Token de la API de PyPI | pypi_api_token{% endif %} +{%- ifversion fpt or ghec or ghes > 3.5 or ghae-issue-7375 %} +redirect.pizza | Token de la API de redirect.pizza | redirect_pizza_api_token{% endif %} {%- ifversion fpt or ghec or ghes > 3.1 or ghae %} RubyGems | Llave de la API de RubyGems | rubygems_api_key{% endif %} Samsara | Token de la API de Samsara | samsara_api_token Samsara | Token de Acceso OAuth a Samsara | samsara_oauth_access_token {%- ifversion fpt or ghec or ghes > 3.4 or ghae-issue-6944 %} diff --git a/translations/es-ES/data/reusables/secret-scanning/partner-secret-list-public-repo.md b/translations/es-ES/data/reusables/secret-scanning/partner-secret-list-public-repo.md index 0a69101524..ae81ed1488 100644 --- a/translations/es-ES/data/reusables/secret-scanning/partner-secret-list-public-repo.md +++ b/translations/es-ES/data/reusables/secret-scanning/partner-secret-list-public-repo.md @@ -22,10 +22,10 @@ | Sistemas Contribuidos | Credenciales de los sistemas contribuidos | | Databricks | Token de Acceso de Databricks | | Datadog | Clave de API de Datadog | -| DigitalOcean | DigitalOcean Personal Access Token | -| DigitalOcean | DigitalOcean OAuth Token | -| DigitalOcean | DigitalOcean Refresh Token | -| DigitalOcean | DigitalOcean System Token | +| DigitalOcean | Token de Acceso Personal de DigitalOcean | +| DigitalOcean | Token OAuth de DigitalOcean | +| DigitalOcean | Token de Actualización de DigitalOcean | +| DigitalOcean | Token de Sistema de DigitalOcean | | Discord | Token de Bot de Discord | | Doppler | Token Personal de Doppler | | Doppler | Token de Servicio de Doppler | @@ -77,6 +77,7 @@ | Proctorio | Clave de Secreto de Proctorio | | Pulumi | Token de Acceso de Pulumi | | PyPI | Token de la API de PyPI | +| redirect.pizza | Token de la API de redirect.pizza | | RubyGems | Clave de la API de RubyGems | | Samsara | Token de API de Samsara | | Samsara | Token de Acceso de OAuth de Samsara | 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 62fd51000f..78ba14c3e8 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 @@ -1,4 +1,4 @@ -| Proveedor | Secreto compatible | Secret type | +| Proveedor | Secreto compatible | Tipo de secreto | | ------------------------- | -------------------------------------------------- | -------------------------------------------------------- | | Adafruit IO | Clave de IO de Adafruit | adafruit_io_key | | Alibaba Cloud | ID de Clave de Acceso a la Nube de Alibaba | alibaba_cloud_access_key_id | @@ -17,10 +17,10 @@ | Checkout.com | Clave secreta de productión de Checkout.com | checkout_production_secret_key | | Clojars | Token de Despliegue de Clojars | clojars_deploy_token | | Databricks | Token de Acceso de Databricks | databricks_access_token | -| DigitalOcean | DigitalOcean Personal Access Token | digitalocean_personal_access_token | -| DigitalOcean | DigitalOcean OAuth Token | digitalocean_oauth_token | -| DigitalOcean | DigitalOcean Refresh Token | digitalocean_refresh_token | -| DigitalOcean | DigitalOcean System Token | digitalocean_system_token | +| DigitalOcean | Token de Acceso Personal de DigitalOcean | digitalocean_personal_access_token | +| DigitalOcean | Token OAuth de DigitalOcean | digitalocean_oauth_token | +| DigitalOcean | Token de Actualización de DigitalOcean | digitalocean_refresh_token | +| DigitalOcean | Token de Sistema de DigitalOcean | digitalocean_system_token | | Discord | Token de Bot de Discord | discord_bot_token | | Doppler | Token Personal de Doppler | doppler_personal_token | | Doppler | Token de Servicio de Doppler | doppler_service_token | @@ -60,16 +60,5 @@ | PlanetScale | Token de Servicio de PlanetScale | planetscale_service_token | | Postman | Clave de API de Postman | postman_api_key | | Proctorio | Clave de Secreto de Proctorio | proctorio_secret_key | -| Samsara | Token de API de Samsara | samsara_api_token | -| Samsara | Token de Acceso de OAuth de Samsara | samsara_oauth_access_token | -| SendGrid | Clave de la API de SendGrid | sendgrid_api_key | -| Sendinblue | Llave de la API de Sendinblue | sendinblue_api_key | -| Sendinblue | Llave SMTP de Sendinblue | sendinblue_smtp_key | -| Shippo | Shippo Live API Token | shippo_live_api_token | -| Shopify | Secreto Compartid de la App de Shopify | shopify_app_shared_secret | -| Shopify | Token de Acceso de Shopify | shopify_access_token | -| Slack | Token de la API de Slack | slack_api_token | -| Stripe | Clave de Secreto Stripe Live | stripe_api_key | -| Tencent Cloud | ID de Secreto de Tencent Cloud | tencent_cloud_secret_id | -| Typeform | Token de acceso personal a Typeform | typeform_personal_access_token | -| WorkOS | WorkOS Production API Key | workos_production_api_key | +{%- ifversion fpt or ghec or ghes > 3.5 or ghae-issue-7375 %} +redirect.pizza | redirect.pizza API Token | redirect_pizza_api_token{% endif %} Samsara | Samsara API Token | samsara_api_token Samsara | Samsara OAuth Access Token | samsara_oauth_access_token SendGrid | SendGrid API Key | sendgrid_api_key Sendinblue | Sendinblue API Key | sendinblue_api_key Sendinblue | Sendinblue SMTP Key | sendinblue_smtp_key Shippo | Shippo Live API Token | shippo_live_api_token Shopify | Shopify App Shared Secret | shopify_app_shared_secret Shopify | Shopify Access Token | shopify_access_token Slack | Slack API Token | slack_api_token Stripe | Stripe Live API Secret Key | stripe_api_key Tencent Cloud | Tencent Cloud Secret ID | tencent_cloud_secret_id Typeform | Typeform Personal Access Token | typeform_personal_access_token WorkOS | WorkOS Production API Key | workos_production_api_key diff --git a/translations/ja-JP/data/features/README.md b/translations/ja-JP/data/features/README.md index d4ffe1dc35..d42b91f594 100644 --- a/translations/ja-JP/data/features/README.md +++ b/translations/ja-JP/data/features/README.md @@ -45,7 +45,7 @@ versions: ## スキーマの適用 -機能のバージョン管理の検証のためのスキーマは[`tests/helpers/schemas/feature-versions-schema.js`](/tests/helpers/schemas/feature-versions-schema.js)にあり、[`tests/linting/lint-files.js`](/tests/linting/lint-files.js)によって実行されます。 +機能のバージョン管理の検証のためのスキーマは[`tests/helpers/schemas/feature-versions-schema.js`](/tests/helpers/schemas/feature-versions-schema.js)にあり、[`tests/linting/lint-versioning.js`](/tests/linting/lint-versioning.js)によって実行されます。 ## 機能タグを削除するためのスクリプト diff --git a/translations/ja-JP/data/release-notes/enterprise-server/3-5/0-rc1.yml b/translations/ja-JP/data/release-notes/enterprise-server/3-5/0-rc1.yml index 43131f5cac..0f1477c856 100644 --- a/translations/ja-JP/data/release-notes/enterprise-server/3-5/0-rc1.yml +++ b/translations/ja-JP/data/release-notes/enterprise-server/3-5/0-rc1.yml @@ -191,34 +191,34 @@ sections: heading: アラートの場所に関するSecret scanningのwebhook notes: - | - GitHub Advanced Security customers using secret scanning can now opt to receive a webhook each time a secret is detected in a new location. The `secret_scanning_alert_location` webhook event includes location details, like the commit SHA, and the associated alert for the detection. A location is created for every new file path containing the detected secret. For more information, see "[Webhook events and payloads](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#secret_scanning_alert_location)." + Secret scanningをお使いのGitHub Advanced Securityのお客様は、新しい場所でシークレットが検出されるたびにwebhookを受信することを選択できるようになりました。`secret_scanning_alert_location` webhookイベントには、コミットSHAといった場所の詳細、検出に関連づけられたアラートが含まれます。場所は、検出されたシークレットを含むすべての新しいファイルパスに対して作成されます。詳しい情報については「[webhookイベントとペイロード](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#secret_scanning_alert_location)」を参照してください。 - - heading: View Dependabot alerts across an organization + heading: Organization全体のDependabotアラートの表示 notes: - | - GitHub Advanced Security customers can now view Dependabot alerts in in an organization's **Security** tab. This view is available to organization owners and members of teams with the [security manager role](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization). For more information, see "[About the security overview](/code-security/security-overview/about-the-security-overview)." + GitHub Advanced Securityのお客様は、Organizatonの**Security**タブでDependabotアラートを表示できるようになりました。この表示ができるのは、Organizationのオーナーと[セキュリティ管理者のロール](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization)を持つTeamのメンバーです。詳しい情報については「[セキュリティの概要について](/code-security/security-overview/about-the-security-overview)」を参照してください。 - - heading: Configure permissions for Dependabot alerts with custom repository roles + heading: カスタムリポジトリロールでのDependabotアラートの権限設定 notes: - | - You can now configure two new permissions for Dependabot alerts when managing custom repository roles. + カスタムリポジトリロールを管理する際に、Dependabotアラートに対する2つの新しい権限を設定できるようになりました。 - - View Dependabot alerts - - Dismiss or reopen Dependabot alerts + - Dependabotアラートの表示 + - Dependabotアラートの却下もしくは再オープン - For more information, see "[Managing custom repository roles for an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization)." + 詳しい情報については「[Organizationのカスタムリポジトリロールの管理](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization)」を参照してください。 - - heading: Reopen dismissed Dependabot alerts + heading: 却下されたDependabotアラートの再オープン notes: - | - You can now reopen dismissed Dependabot alerts through the UI page for a closed alert. This does not affect Dependabot pull requests or the GraphQL API. For more information, see "[About Dependabot alerts](/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." + 却下されたDependabotアラートを、クローズされたアラートのUIページを通じて再オープンできるようになりました。これはDependabotのPull RequestやGraphQL APIには影響しません。詳しい情報については「[Dependabotアラートについて](/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)」を参照してください。 - - heading: Pub support for Dependabot version updates is in public beta + heading: DependabotバージョンアップデートのPubサポートのパブリックベータ notes: - | - Users of Dependabot version updates can now proactively update dependencies for Flutter or Dart projects that use the Pub package manager. + Dependabotバージョンアップデートのユーザは、Pubパッケージマネージャーを使っているFlutterもしくはDartプロジェクトの依存関係を積極的にアップデートできるようになりました。 - To test [version updates](/code-security/dependabot/dependabot-version-updates/about-dependabot-version-updates) on your own Dart or Flutter repository, add the following configuration file in [.github/dependabot.yaml](/code-security/dependabot/dependabot-version-updates/configuring-dependabot-version-updates#enabling-dependabot-version-updates). Note the `package-ecosystem: "pub"` and `enable-beta-ecosystems: true` flags. + [バージョンアップデート](/code-security/dependabot/dependabot-version-updates/about-dependabot-version-updates)を独自のDartもしくはFlutterリポジトリでテストするには、[.github/dependabot.yaml](/code-security/dependabot/dependabot-version-updates/configuring-dependabot-version-updates#enabling-dependabot-version-updates)中の以下の設定ファイルを追加してください。`package-ecosystem: "pub"`及び`enable-beta-ecosystems: true`フラグに注意してください。 ```yaml version: 2 enable-beta-ecosystems: true @@ -229,112 +229,112 @@ sections: interval: "weekly" ``` - - heading: See pull request associated with a repository's Dependabot alerts via GraphQL API + heading: リポジトリのDependabotアラートに関連するPull RequestをGraph APIを通じて参照 notes: - | - The new `DependabotUpdate` GraphQL object lets you view information about what happens to your repository's security updates. When GitHub Enterprise Server detects that a dependency in your repository is vulnerable, Dependabot will attempt to open a pull request to update that dependency to a non-vulnerable version. You can now see the pull request that fixes the vulnerability. In some cases, Dependabot fails to open a pull request. Previously, the error message that Dependabot generated was only visible in the "Dependabot Alerts" section of the **Security** tab. Now, if Dependabot runs into an error when trying to open a pull request for a security alert, you can determine the reason using the GraphQL API. For more information, see "[Objects](/graphql/reference/objects#dependabotupdate)" in the GraphQL API documentation. + 新しい`DependabotUpdate` GraphQLオブジェクトを使うと、リポジトリのセキュリティアップデートで起きたことに関する情報を見ることができます。GitHub Enterprise Serverが、リポジトリ中の依存関係に脆弱性があることを検出すると、Dependabotはその依存関係を脆弱性のないバージョンにアップデートするPull Requestをオープンしようとします。脆弱性を修正するこのPull Requestを見ることができるようになりました。場合によっては、DependabotはPull Requestのオープンに失敗することがあります。以前は、Dependabotが生成したエラーメッセージは**Security**タブの"Dependabot Alerts"セクションでのみ見ることができました。現在は、Dependabotがセキュリティアラートに対するPull Requestをオープンしようとした際にエラーが生じた場合、その理由をGraph APIを使って判断できます。詳しい情報については、GraphQL APIドキュメンテーションの「[Objects](/graphql/reference/objects#dependabotupdate)」を参照してください。 - - heading: Access more information about Dependabot alerts via GraphQL API + heading: GraphQL APIを通じたDependabotアラートに関する詳細情報へのアクセス notes: - | - You can now view fixed alerts from Dependabot with the GraphQL API. You can also access and filter by state, as well as by unique numeric identifier, and you can filter by state on the vulnerability alert object. The following fields now exist for a `RepositoryVulnerabilityAlert`. + GraphQL APIで、Dependabotから修復されたアラートを見ることができるようになりました。状態や、一意の数値識別子でのアクセスやフィルタリングもできるようになり、脆弱性アラート尾p部ジェクトの状態でもフィルタリングできるようになりました。`RepositoryVulnerabilityAlert`には以下のフィールドがあります。 - `number` - `fixed_at` - `fix_reason` - `state` - For more information, see "[Objects](/graphql/reference/objects#repositoryvulnerabilityalert)" in the GraphQL API documentation. + 詳しい情報については、GraphQL APIドキュメンテーションの「[Objects](/graphql/reference/objects#repositoryvulnerabilityalert)」を参照してください。 - - heading: Git events in the enterprise audit log + heading: EnterpriseのAudit log内のGitイベント notes: - | - The following Git-related events can now appear in the enterprise audit log. If you enable the feature and set an audit log retention period, the new events will be available for search via the UI and API, or export via JSON or CSV. + 以下のGit関連のイベントが、EnterpriseのAudit logに現れるようになりました。この機能を有効化し、Audit logの保存期間を設定すると、新しいイベントはUIやAPI経由で検索したり、JSONあるいはCSVにエクスポートしたりできるようになります。 - `git.clone` - `git.fetch` - `git.push` - Due to the large number of Git events logged, we recommend you monitor your instance's file storage and review your related alert configurations. For more information, see "[Audit log events for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise#git-category-actions)" and "[Monitoring storage](/admin/enterprise-management/monitoring-your-appliance/recommended-alert-thresholds#monitoring-storage)." + 記録されるGitイベント数は大量なので、インスタンスのファイルストレージをモニタリングし、関連するアラート設定をレビューすることをおすすめします。詳しい情報については「[EnterpriseのAudit logイベント(/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise#git-category-actions)」及び「[ストレージのモニタリング](/admin/enterprise-management/monitoring-your-appliance/recommended-alert-thresholds#monitoring-storage)」を参照してください。 - - heading: Improvements to CODEOWNERS + heading: CODEOWNERSの改善 notes: - | - This release includes improvements to CODEOWNERS. + このリリースにはCODEOWNERSへの改善が含まれています。 - - Syntax errors are now surfaced when viewing a CODEOWNERS file from the web. Previously, when a line in a CODEOWNERS file had a syntax error, the error would be ignored or in some cases cause the entire CODEOWNERS file to not load. GitHub Apps and Actions can access the same list of errors using new REST and GraphQL APIs. For more information, see "[Repositories](/rest/repos/repos#list-codeowners-errors)" in the REST API documentation or "[Objects](/graphql/reference/objects#repositorycodeowners)" in the GraphQL API documentation. - - After someone creates a new pull request or pushes new changes to a draft pull request, any code owners that will be requested for review are now listed in the pull request under "Reviewers". This feature gives you an early look at who will be requested to review once the pull request is marked ready for review. - - Comments in CODEOWNERS files can now appear at the end of a line, not just on dedicated lines. + - CODEOWNERSファイルをWebで表示する際に、構文エラーが表示されます。以前は、CODEOWNERSファイルの行に構文エラーがあった場合、　そのエラーは無視されるか、場合によってはCODEOWNERSファイル全体がロードされないこともありました。GitHub App及びActionsは、新しいREST及びGraphQL APIを使って同じエラーのリストにアクセスできます。詳しい情報についてはREST APIドキュメンテーションの「[リポジトリ](/rest/repos/repos#list-codeowners-errors)」あるいはGraphQL APIドキュメンテーションの「[オブジェクト](/rest/repos/repos#list-codeowners-errors)」を参照してください。 + - 誰かが新しいPull Requestを作成するか、ドラフトのPull Requestに新しい変更をプッシュすると、レビューをリクエストされたコードオーナーはPull Requestの"Reviewers（レビュー担当者）"の下にリストされます。この機能によって、Pull Requestがレビューの準備ができたとしてマークされると、レビューをリクエストされた人を素早く見ることができるようになります。 + - CODEOWNERSファイルへのコメントは、専用の行だけにではなく、行の終わりにも表示されるようになりました。 - For more information, see "[About code owners](/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners)." + 詳しい情報については「[コードオーナーについて](/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners)」を参照してください。 - - heading: More ways to keep a pull request's topic branch up to date + heading: Pull Requestのトピックブランチを最新に保つ他の方法 notes: - | - The **Update branch** button on the pull request page lets you update your pull request's branch with the latest changes from the base branch. This is useful for verifying your changes are compatible with the current version of the base branch before you merge. Two enhancements now give you more ways to keep your branch up-to-date. + Pull Requestページの**Update branch（ブランチ更新）**ボタンを使うと、Pull Requestのブランチをベースブランチの最新の変更で更新できます。これは、変更がベースブランチの現在のバージョンと互換性があるかをマージ前に検証するのに役立ちます。2つの拡張によって、ブランチを最貧の状態に保つ方法がさらに増えます。 - - When your pull request's topic branch is out of date with the base branch, you now have the option to update it by rebasing on the latest version of the base branch. Rebasing applies the changes from your branch onto the latest version of the base branch, resulting in a branch with a linear history since no merge commit is created. To update by rebasing, click the drop down menu next to the **Update Branch** button, click **Update with rebase**, and then click **Rebase branch**. Previously, **Update branch** performed a traditional merge that always resulted in a merge commit in your pull request branch. This option is still available, but now you have the choice. For more information, see "[Keeping your pull request in sync with the base branch](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/keeping-your-pull-request-in-sync-with-the-base-branch)." + - Pull Requestのトピックブランチがベースブランチよりも古くなってしまっている場合、ベースブランチの最新バージョンでリベースすることによって更新できるようになりました。リベースによって自分のブランチの変更がベースブランチの最新バージョンに適用されるので、マージコミットが作成されないことからブランチは直線的な履歴を持つことになります。リベースによって更新を行うには、**Update Branch（ブランチの更新）**ボタンの隣にあるドロップダウンメニューをクリックし、**Update with rebase（リベースして更新）**をクリックし、続いて**Rebase branch（ブランチをリベース）**をクリックしてください。以前は、**Update branch**は旧来のマージを行い、常にPull Requestのブランチにマージコミットが生じました。この選択肢も引き続き利用できますが、選択をできるようになりました。詳しい情報については「[Pull Requestとベースブランチとの同期を保つ](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/keeping-your-pull-request-in-sync-with-the-base-branch)」を参照してください。 - - A new repository setting allows the **Update branch** button to always be available when a pull request's topic branch is not up to date with the base branch. Previously, this button was only available when the **Require branches to be up to date before merging** branch protection setting was enabled. People with admin or maintainer access can manage the **Always suggest updating pull request branches** setting from the **Pull Requests** section in repository settings. For more information, see "[Managing suggestions to update pull request branches](/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-suggestions-to-update-pull-request-branches)." + - 新しいリポジトリ設定によって、Pull Requestのトピックブランチがベースブランチよりも古くなっている場合に**Update branch**ボタンを常に利用できるようにすることができます。以前は、このボタンが利用できるのは**Require branches to be up to date before merging（マージの際にはブランチが最新であることが必須）**ブランチ保護設定が有効化されている場合のみでした。管理もしくはメンテナアクセスを持つ人は、 リポジトリの設定の**Pull Requests**セクションの**Always suggest updating pull request branches（常にPull Requestブランチの更新を提案）**設定を管理できます。詳しい情報については「[Pull Requestブランチの更新提案の管理](/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-suggestions-to-update-pull-request-branches)」を参照してください。 - - heading: Configure custom HTTP headers for GitHub Pages sites + heading: GitHub PagesサイトのカスタムHTTPヘッダの設定 notes: - | - You can now configure custom HTTP headers that apply to all GitHub Pages sites served from your GitHub Enterprise Server instance. For more information, see "[Configuring GitHub Pages for your enterprise](/admin/configuration/configuring-your-enterprise/configuring-github-pages-for-your-enterprise#configuring-github-pages-response-headers-for-your-enterprise)." + GitHub Enterprise Serverインスタンスから提供されるすべてのGitHub Pagesサイトに適用されるカスタムHTTPヘッダを設定できるようになりました。詳しい情報については「[EnterpriseでのGitHub Pagesの設定](/admin/configuration/configuring-your-enterprise/configuring-github-pages-for-your-enterprise#configuring-github-pages-response-headers-for-your-enterprise)」を参照してください。 - - heading: Ignore commits in blame view + heading: blameビューでのコミットの無視 notes: - | - It's now possible to ignore revisions in the blame view by creating a _.git-blame-ignore-revs_ file in the root of your repository. For more information, see "[Viewing a file](/repositories/working-with-files/using-files/viewing-a-file#ignore-commits-in-the-blame-view)." + リポジトリのルートに_.git-blame-ignore-revs_ファイルを作成することによって、blameビューでリビジョンを無視できるようになりました。詳しい情報については「[ファイルの表示](/repositories/working-with-files/using-files/viewing-a-file#ignore-commits-in-the-blame-view)」を参照してください。 - - heading: Light high contrast theme is generally available + heading: 軽量高コントラストテーマが一般提供になりました notes: - | - A light high contrast theme, with greater contrast between foreground and background elements, is now generally available. For more information, see "[Managing your theme settings](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings)." + 前面要素と背景要素間のコントラストが大きい軽量高コントラストテーマが一般提供になりました。詳しい情報については「[テーマ設定の管理](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings)」を参照してください。 - heading: Tag protection rules notes: - | - Repository owners can now configure tag protection rules to protect a repository's tags. Once protected by a tag protection rule, tags matching a specified name pattern can only be created and deleted by users with the Maintain or Admin role in the repository. For more information, see "[Configuring tag protection rules](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-tag-protection-rules)." + リポジトリオーナーは、リポジトリのタグを保護するためのタグ保護ルールを設定できるようになりました。タグ保護ルールで保護されると、特定の名前のパターンにマッチするタグは、リポジトリのMaintainもしくはAdminロールを持つユーザだけが作成及び削除できるようになります。詳しい情報については「[タグ保護ルールの設定](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-tag-protection-rules)」を参照してください。 bugs: - | - It is now possible for GitHub Apps to upload release assets. + GitHub Appがリリースアセットをアップロードできるようになりました。 changes: - | - To use the device authorization flow for OAuth and GitHub Apps, you must manually enable the feature. This change reduces the likelihood of apps being used in phishing attacks against GitHub Enterprise Server users by ensuring integrators are aware of the risks and make a conscious choice to support this form of authentication. If you own or manage an OAuth App or GitHub App and you want to use the device flow, you can enable it for your app via the app's settings page. The device flow API endpoints will respond with status code `400` to apps that have not enabled this feature. For more information, see "[Authorizing OAuth Apps](/developers/apps/building-oauth-apps/authorizing-oauth-apps#device-flow)." + OAuth及びGitHub Appsでデバイス認可フローを使うためには、この機能を手動で有効化しなければなりません。この変更は、アプリケーションがGitHub Enterprise Serverのユーザに対するフィッシング攻撃に使われる可能性を、インテグレーターがそのリスクを認識し、この形態の認証をサポートする意識的な選択を確実に行うことによって下げるものです。OAuth AppもしくはGitHub Appを所有もしくは管理していて、デバイスフローを使いたいのであれば、アプリケーションの設定ページからアプリケーションに対して有効化できます。デバイスフローAPIのエンドポイントは、この機能が有効化されていないアプリケーションに対してはステータスコード`400`を返します。詳しい情報については「[OAuth Appsの認可](/developers/apps/building-oauth-apps/authorizing-oauth-apps#device-flow)」を参照してください。 - | - The code scanning alert page now always shows the alert status and information for the default branch. There is a new "Affected branches" panel in the sidebar where you can see the status of the alert in other branches. If the alert does not exist in your default branch, the alert page will show the status as "In branch" or "In pull request" for the location where the alert was last seen. This improvement makes it easier to understand the status of alerts which have been introduced into your code base. For more information, see "[About code scanning alerts](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts#about-alert-details)." + Code scanningのアラートページは、デフォルトブランチに対するアラートのステータスと情報を常に表示するようになりました。サイドバーには新しい"Affected branches（影響を受けるブランチ）"パネルがあり、他のブランチでのアラートのステータスを見ることができます。デフォルトブランチにアラートがない場合には、アラートページは最後にアラートが見られた場所について"In branch（ブランチ内）"あるいは"In pull request（Pull Request内）"というステータスを表示します。この開演によって、コードベースに持ち込まれたアラートのステータスを理解しやすくなります。詳しい情報については「[Code scanningアラートについて](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts#about-alert-details)」を参照してください。 - The alert list page is not changed and can be filtered by `branch`. You can use the code scanning API to retrieve more detailed branch information for alerts. For more information, see "[Code Scanning](/rest/code-scanning)" in the REST API documentation. + アラートのリストページは変更されておらず、`branch`でフィルタリングできます。Code scanning APIを使ってアラートに関する詳細なブランチ情報を取得できます。詳しい情報については、REST APIドキュメンテーションの「[Code scanning](/rest/code-scanning)」を参照してください。 - | - Code scanning now shows the details of the analysis origin of an alert. If an alert has more than one analysis origin, it is shown in the "Affected branches" sidebar and in the alert timeline. You can hover over the analysis origin icon in the "Affected branches" sidebar to see the alert status in each analysis origin. If an alert only has a single analysis origin, no information about analysis origins is displayed on the alert page. These improvements will make it easier to understand your alerts. In particular, it will help you understand those that have multiple analysis origins. This is especially useful for setups with multiple analysis configurations, such as monorepos. For more information, see "[About code scanning alerts](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts#about-analysis-origins)." + Code scanningは、アラートの分析元の詳細を表示するようになりました。アラートが複数の分析元を持つ場合、それは"Affected branches（影響されるブランチ）"及びアラートのタイムラインに表示されます。"Affected branches"サイドバー内の分析元のアイコンにカーソルを乗せると、それぞれの分析元のアラートステータスが表示されます。アラートが1つの分析元だけを持つ場合、アラートページには分析元に関する情報は表示されません。これらの改善によって、アラートを理解しやすくなります。特に、複数の分析元を持つアラートを理解するために役立ちます。これは、モノリポジトリのように複数の分析設定を持つ構成で役に立ちます。詳しい情報については「[Code scanningアラートについて](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts#about-analysis-origins)」を参照してください。 - | - Lists of repositories owned by a user or organization now have an additional filter option, "Templates", making it easier to find template repositories. + ユーザもしくはOrganizationが所有するリポジトリのリストに追加のフィルタオプションの"Templates"が追加され、テンプレートリポジトリを見つけやすくなりました。 - | - GitHub Enterprise Server can display several common image formats, including PNG, JPG, GIF, PSD, and SVG, and provides several ways to compare differences between versions. Now when reviewing added or changed images in a pull request, previews of those images are shown by default. Previously, you would see a message indicating that binary files could not be shown and you would need to toggle the "Display rich diff" option. For more information, see "[Working with non-code files](/repositories/working-with-files/using-files/working-with-non-code-files)." + GitHub Enterprise Serverは、PNG、JPG、GIF、PSD、SVGを含む一般的な画像フォーマットを表示でき、バージョン間の差異を比較する複数の方法を提供します。Pull Requestで追加もしくは変更された画像をレビューする際に、それらの画像のプレビューがデフォルトで表示されるようになりました。以前は、バイナリファイルは表示できないことを示すメッセージが表示され、"Display rich diff（リッチdiffの表示）"オプションを切り替える必要がありました。詳しい情報については「[コード以外のファイルの扱い](/repositories/working-with-files/using-files/working-with-non-code-files)」を参照してください。 - | - New gists are now created with a default branch name of either `main` or the alternative default branch name defined in your user settings. This matches how other repositories are created on GitHub Enterprise Server. For more information, see "[About branches](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches#about-the-default-branch)" and "[Managing the default branch name for your repositories](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-the-default-branch-name-for-your-repositories)." + 新しいGistは、デフォルトのブランチ名を`main`もしくはユーザ設定で定義された代替のデフォルトブランチ名として作成されるようになりました。これは、GitHub Enterprise Serverで他のリポジトリが作成されるのと同様になります。詳しい情報については「[ブランチについて](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches#about-the-default-branch)」及び「[リポジトリのデフォルトブランチ名の管理](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-the-default-branch-name-for-your-repositories)」を参照してください。 - | - Gists now only show the 30 most recent comments when first displayed. You can click **Load earlier comments...** to view more. This allows gists that have many comments to appear more quickly. For more information, see "[Editing and sharing content with gists](/get-started/writing-on-github/editing-and-sharing-content-with-gists)." + Gistは、最初に表示される際に最近の30のコメントだけを表示するようになりました。**Load earlier comments...（以前のコメントのロード）**をクリックすれば、もっと多くのコメントを見ることができます。これによって、多くのコメントを持つGistが素早く表示されるようになります。詳しい情報については「[Gistでのコメントの編集と共有](/get-started/writing-on-github/editing-and-sharing-content-with-gists)」を参照してください。 - | - Settings pages for users, organizations, repositories, and teams have been redesigned, grouping similar settings pages into sections for improved information architecture and discoverability. For more information, see the [GitHub changelog](https://github.blog/changelog/2022-02-02-redesign-of-githubs-settings-pages/). + ユーザ、Organization、リポジトリ、Teamの設定ページは再設計され、情報アーキテクチャと発見性を改善するため、同じような設定ページがセクションにグループ化されました。詳しい情報については[GitHub changelog](https://github.blog/changelog/2022-02-02-redesign-of-githubs-settings-pages/)を参照してください。 - | - Focusing or hovering over a label now displays the label description in a tooltip. + ラベルにフォーカスやカーソルを当てると、ツールチップにラベルの説明が表示されるようになりました。 - | - Creating and removing repository invitations, whether done through the API or web interface, are now subject to rate limits that may be enabled on your GitHub Enterprise Server instance. For more information about rate limits, see "[Configuring rate limits](/admin/configuration/configuring-your-enterprise/configuring-rate-limits)." + リポジトリへの招待の作成と削除は、それがAPIで行われているかWebインターフェースで行われているかにかかわらず、GitHub Enterprise Serverインスタンスで有効化されていることがあるレート制限の対象になります。レート制限に関する詳しい情報については「[レート制限の設定](/admin/configuration/configuring-your-enterprise/configuring-rate-limits)」を参照してください。 - | - MinIO has announced the removal of the MinIO Gateways starting June 1st, 2022. While MinIO Gateway for NAS continues to be one of the supported storage providers for Github Actions and Github Packages, we recommend moving to MinIO LTS support to avail support and bug fixes from MinIO. For more information about rate limits, see "[Scheduled removal of MinIO Gateway for GCS, Azure, HDFS in the minio/minio repository](https://github.com/minio/minio/issues/14331)." + MinIOは、2022年6月1日からのMinIO Gatewaysの廃止をアナウンスしました。MinIO Gateway for NASは、引き続きGitHub Actions及びGitHub Packagesのサポート対象ストレージプロバイダの1つであり続けますが、MinIOからのサポートとバグ修正を利用し続けるために、MinIO LTSサポートへの移行をおすすめします。レート制限に関する詳しい情報については「[minio/minioリポジトリでのGCS、Azure、HDFS用のMinIO Gatewayの予定された廃止](https://github.com/minio/minio/issues/14331)」を参照してください。 deprecations: - - heading: Change to the format of authentication tokens + heading: 認証トークンのフォーマット変更 notes: - | - GitHub Connect will no longer work after June 3rd for instances running GitHub Enterprise Server 3.1 or older, due to the format of GitHub authentication tokens changing. For more information, see the [GitHub changelog](https://github.blog/changelog/2021-03-31-authentication-token-format-updates-are-generally-available/). + GitHub認証トークンのフォーマット変更により、GitHub Enterprise Server 3.1以前を動作させているインスタンスでは、6月3日以降GitHub Connectは動作しなくなります。詳しい情報については[GitHub changelog](https://github.blog/changelog/2021-03-31-authentication-token-format-updates-are-generally-available/)を参照してください。 - - heading: CodeQL runner deprecated in favor of CodeQL CLI + heading: CodeQL runnerはCodeQL CLIを代替として非推奨になりました notes: - | - The CodeQL runner is deprecated in favor of the CodeQL CLI. GitHub Enterprise Server 3.4 and later no longer include the CodeQL runner. This deprecation only affects users who use CodeQL code scanning in 3rd party CI/CD systems. GitHub Actions users are not affected. GitHub strongly recommends that customers migrate to the CodeQL CLI, which is a feature-complete replacement for the CodeQL runner and has many additional features. For more information, see "[Migrating from the CodeQL runner to CodeQL CLI](/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/migrating-from-the-codeql-runner-to-codeql-cli)." + CodeQLランナーは、CodeQL CLIを代替として非推奨になりました。GitHub Enterprise Server 3.4以降には、CodeQLランナーは含まれなくなります。この非推奨化は、CodeQLコードスキャンニングをサードパーティのCI/CDシステムで利用しているユーザにのみ影響します。GitHub Actionsのユーザは影響されません。GitHubは、CodeQLランナーと機能的に互換であり、多くの追加機能を持つ代替製品であるCodeQL CLIへの移行をお客様に強くおすすめします。詳しい情報については「[CodeQLランナーからCodeQL CLIへの移行(/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/migrating-from-the-codeql-runner-to-codeql-cli)」を参照してください。 - heading: GitHub Pagesのテーマピッカーの削除 notes: @@ -348,4 +348,4 @@ sections: - GitHub Connectで"Users can search GitHub.com"が有効化されている場合、GitHub.comの検索結果にプライベート及びインターナルリポジトリのIssueが含まれません。 - '{% data variables.product.prodname_registry %}のnpmレジストリは、メタデータのレスポンス中で時間の値を返さなくなります。これは、大きなパフォーマンス改善のために行われました。メタデータレスポンスの一部として時間の値を返すために必要なすべてのデータは保持し続け、既存のパフォーマンスの問題を解決した将来に、この値を返すことを再開します。' - pre-receive フックの処理に固有のリソース制限によって、pre-receive フックに失敗するものが生じることがあります。 - - Actions services need to be restarted after restoring an appliance from a backup taken on a different host. + - 別のホスト上で取られたバックアップからのアプライアンスのリストア後、Actionsサービスを再起動する必要があります。 diff --git a/translations/ja-JP/data/release-notes/enterprise-server/3-5/0.yml b/translations/ja-JP/data/release-notes/enterprise-server/3-5/0.yml index 99a590fa49..fb402a7062 100644 --- a/translations/ja-JP/data/release-notes/enterprise-server/3-5/0.yml +++ b/translations/ja-JP/data/release-notes/enterprise-server/3-5/0.yml @@ -2,7 +2,7 @@ date: '2022-05-31' intro: | - For upgrade instructions, see "[Upgrading {% data variables.product.prodname_ghe_server %}](/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server)." + アップグレードの手順については「[{% data variables.product.prodname_ghe_server %} のアップグレード](/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server)」を参照してください。 sections: features: - @@ -184,34 +184,34 @@ sections: heading: アラートの場所に関するSecret scanningのwebhook notes: - | - GitHub Advanced Security customers using secret scanning can now opt to receive a webhook each time a secret is detected in a new location. The `secret_scanning_alert_location` webhook event includes location details, like the commit SHA, and the associated alert for the detection. A location is created for every new file path containing the detected secret. For more information, see "[Webhook events and payloads](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#secret_scanning_alert_location)." + Secret scanningをお使いのGitHub Advanced Securityのお客様は、新しい場所でシークレットが検出されるたびにwebhookを受信することを選択できるようになりました。`secret_scanning_alert_location` webhookイベントには、コミットSHAといった場所の詳細、検出に関連づけられたアラートが含まれます。場所は、検出されたシークレットを含むすべての新しいファイルパスに対して作成されます。詳しい情報については「[webhookイベントとペイロード](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#secret_scanning_alert_location)」を参照してください。 - - heading: View Dependabot alerts across an organization + heading: Organization全体のDependabotアラートの表示 notes: - | - GitHub Advanced Security customers can now view Dependabot alerts in in an organization's **Security** tab. This view is available to organization owners and members of teams with the [security manager role](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization). For more information, see "[About the security overview](/code-security/security-overview/about-the-security-overview)." + GitHub Advanced Securityのお客様は、Organizatonの**Security**タブでDependabotアラートを表示できるようになりました。この表示ができるのは、Organizationのオーナーと[セキュリティ管理者のロール](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization)を持つTeamのメンバーです。詳しい情報については「[セキュリティの概要について](/code-security/security-overview/about-the-security-overview)」を参照してください。 - - heading: Configure permissions for Dependabot alerts with custom repository roles + heading: カスタムリポジトリロールでのDependabotアラートの権限設定 notes: - | - You can now configure two new permissions for Dependabot alerts when managing custom repository roles. + カスタムリポジトリロールを管理する際に、Dependabotアラートに対する2つの新しい権限を設定できるようになりました。 - - View Dependabot alerts - - Dismiss or reopen Dependabot alerts + - Dependabotアラートの表示 + - Dependabotアラートの却下もしくは再オープン - For more information, see "[Managing custom repository roles for an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization)." + 詳しい情報については「[Organizationのカスタムリポジトリロールの管理](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization)」を参照してください。 - - heading: Reopen dismissed Dependabot alerts + heading: 却下されたDependabotアラートの再オープン notes: - | - You can now reopen dismissed Dependabot alerts through the UI page for a closed alert. This does not affect Dependabot pull requests or the GraphQL API. For more information, see "[About Dependabot alerts](/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." + 却下されたDependabotアラートを、クローズされたアラートのUIページを通じて再オープンできるようになりました。これはDependabotのPull RequestやGraphQL APIには影響しません。詳しい情報については「[Dependabotアラートについて](/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)」を参照してください。 - - heading: Pub support for Dependabot version updates is in public beta + heading: DependabotバージョンアップデートのPubサポートのパブリックベータ notes: - | - Users of Dependabot version updates can now proactively update dependencies for Flutter or Dart projects that use the Pub package manager. + Dependabotバージョンアップデートのユーザは、Pubパッケージマネージャーを使っているFlutterもしくはDartプロジェクトの依存関係を積極的にアップデートできるようになりました。 - To test [version updates](/code-security/dependabot/dependabot-version-updates/about-dependabot-version-updates) on your own Dart or Flutter repository, add the following configuration file in [.github/dependabot.yaml](/code-security/dependabot/dependabot-version-updates/configuring-dependabot-version-updates#enabling-dependabot-version-updates). Note the `package-ecosystem: "pub"` and `enable-beta-ecosystems: true` flags. + [バージョンアップデート](/code-security/dependabot/dependabot-version-updates/about-dependabot-version-updates)を独自のDartもしくはFlutterリポジトリでテストするには、[.github/dependabot.yaml](/code-security/dependabot/dependabot-version-updates/configuring-dependabot-version-updates#enabling-dependabot-version-updates)中の以下の設定ファイルを追加してください。`package-ecosystem: "pub"`及び`enable-beta-ecosystems: true`フラグに注意してください。 ```yaml version: 2 enable-beta-ecosystems: true @@ -222,112 +222,112 @@ sections: interval: "weekly" ``` - - heading: See pull request associated with a repository's Dependabot alerts via GraphQL API + heading: リポジトリのDependabotアラートに関連するPull RequestをGraph APIを通じて参照 notes: - | - The new `DependabotUpdate` GraphQL object lets you view information about what happens to your repository's security updates. When GitHub Enterprise Server detects that a dependency in your repository is vulnerable, Dependabot will attempt to open a pull request to update that dependency to a non-vulnerable version. You can now see the pull request that fixes the vulnerability. In some cases, Dependabot fails to open a pull request. Previously, the error message that Dependabot generated was only visible in the "Dependabot Alerts" section of the **Security** tab. Now, if Dependabot runs into an error when trying to open a pull request for a security alert, you can determine the reason using the GraphQL API. For more information, see "[Objects](/graphql/reference/objects#dependabotupdate)" in the GraphQL API documentation. + 新しい`DependabotUpdate` GraphQLオブジェクトを使うと、リポジトリのセキュリティアップデートで起きたことに関する情報を見ることができます。GitHub Enterprise Serverが、リポジトリ中の依存関係に脆弱性があることを検出すると、Dependabotはその依存関係を脆弱性のないバージョンにアップデートするPull Requestをオープンしようとします。脆弱性を修正するこのPull Requestを見ることができるようになりました。場合によっては、DependabotはPull Requestのオープンに失敗することがあります。以前は、Dependabotが生成したエラーメッセージは**Security**タブの"Dependabot Alerts"セクションでのみ見ることができました。現在は、Dependabotがセキュリティアラートに対するPull Requestをオープンしようとした際にエラーが生じた場合、その理由をGraph APIを使って判断できます。詳しい情報については、GraphQL APIドキュメンテーションの「[Objects](/graphql/reference/objects#dependabotupdate)」を参照してください。 - - heading: Access more information about Dependabot alerts via GraphQL API + heading: GraphQL APIを通じたDependabotアラートに関する詳細情報へのアクセス notes: - | - You can now view fixed alerts from Dependabot with the GraphQL API. You can also access and filter by state, as well as by unique numeric identifier, and you can filter by state on the vulnerability alert object. The following fields now exist for a `RepositoryVulnerabilityAlert`. + GraphQL APIで、Dependabotから修復されたアラートを見ることができるようになりました。状態や、一意の数値識別子でのアクセスやフィルタリングもできるようになり、脆弱性アラート尾p部ジェクトの状態でもフィルタリングできるようになりました。`RepositoryVulnerabilityAlert`には以下のフィールドがあります。 - `number` - `fixed_at` - `fix_reason` - `state` - For more information, see "[Objects](/graphql/reference/objects#repositoryvulnerabilityalert)" in the GraphQL API documentation. + 詳しい情報については、GraphQL APIドキュメンテーションの「[Objects](/graphql/reference/objects#repositoryvulnerabilityalert)」を参照してください。 - - heading: Git events in the enterprise audit log + heading: EnterpriseのAudit log内のGitイベント notes: - | - The following Git-related events can now appear in the enterprise audit log. If you enable the feature and set an audit log retention period, the new events will be available for search via the UI and API, or export via JSON or CSV. + 以下のGit関連のイベントが、EnterpriseのAudit logに現れるようになりました。この機能を有効化し、Audit logの保存期間を設定すると、新しいイベントはUIやAPI経由で検索したり、JSONあるいはCSVにエクスポートしたりできるようになります。 - `git.clone` - `git.fetch` - `git.push` - Due to the large number of Git events logged, we recommend you monitor your instance's file storage and review your related alert configurations. For more information, see "[Audit log events for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise#git-category-actions)" and "[Monitoring storage](/admin/enterprise-management/monitoring-your-appliance/recommended-alert-thresholds#monitoring-storage)." + 記録されるGitイベント数は大量なので、インスタンスのファイルストレージをモニタリングし、関連するアラート設定をレビューすることをおすすめします。詳しい情報については「[EnterpriseのAudit logイベント(/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise#git-category-actions)」及び「[ストレージのモニタリング](/admin/enterprise-management/monitoring-your-appliance/recommended-alert-thresholds#monitoring-storage)」を参照してください。 - - heading: Improvements to CODEOWNERS + heading: CODEOWNERSの改善 notes: - | - This release includes improvements to CODEOWNERS. + このリリースにはCODEOWNERSへの改善が含まれています。 - - Syntax errors are now surfaced when viewing a CODEOWNERS file from the web. Previously, when a line in a CODEOWNERS file had a syntax error, the error would be ignored or in some cases cause the entire CODEOWNERS file to not load. GitHub Apps and Actions can access the same list of errors using new REST and GraphQL APIs. For more information, see "[Repositories](/rest/repos/repos#list-codeowners-errors)" in the REST API documentation or "[Objects](/graphql/reference/objects#repositorycodeowners)" in the GraphQL API documentation. - - After someone creates a new pull request or pushes new changes to a draft pull request, any code owners that will be requested for review are now listed in the pull request under "Reviewers". This feature gives you an early look at who will be requested to review once the pull request is marked ready for review. - - Comments in CODEOWNERS files can now appear at the end of a line, not just on dedicated lines. + - CODEOWNERSファイルをWebで表示する際に、構文エラーが表示されます。以前は、CODEOWNERSファイルの行に構文エラーがあった場合、　そのエラーは無視されるか、場合によってはCODEOWNERSファイル全体がロードされないこともありました。GitHub App及びActionsは、新しいREST及びGraphQL APIを使って同じエラーのリストにアクセスできます。詳しい情報についてはREST APIドキュメンテーションの「[リポジトリ](/rest/repos/repos#list-codeowners-errors)」あるいはGraphQL APIドキュメンテーションの「[オブジェクト](/rest/repos/repos#list-codeowners-errors)」を参照してください。 + - 誰かが新しいPull Requestを作成するか、ドラフトのPull Requestに新しい変更をプッシュすると、レビューをリクエストされたコードオーナーはPull Requestの"Reviewers（レビュー担当者）"の下にリストされます。この機能によって、Pull Requestがレビューの準備ができたとしてマークされると、レビューをリクエストされた人を素早く見ることができるようになります。 + - CODEOWNERSファイルへのコメントは、専用の行だけにではなく、行の終わりにも表示されるようになりました。 - For more information, see "[About code owners](/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners)." + 詳しい情報については「[コードオーナーについて](/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners)」を参照してください。 - - heading: More ways to keep a pull request's topic branch up to date + heading: Pull Requestのトピックブランチを最新に保つ他の方法 notes: - | - The **Update branch** button on the pull request page lets you update your pull request's branch with the latest changes from the base branch. This is useful for verifying your changes are compatible with the current version of the base branch before you merge. Two enhancements now give you more ways to keep your branch up-to-date. + Pull Requestページの**Update branch（ブランチ更新）**ボタンを使うと、Pull Requestのブランチをベースブランチの最新の変更で更新できます。これは、変更がベースブランチの現在のバージョンと互換性があるかをマージ前に検証するのに役立ちます。2つの拡張によって、ブランチを最貧の状態に保つ方法がさらに増えます。 - - When your pull request's topic branch is out of date with the base branch, you now have the option to update it by rebasing on the latest version of the base branch. Rebasing applies the changes from your branch onto the latest version of the base branch, resulting in a branch with a linear history since no merge commit is created. To update by rebasing, click the drop down menu next to the **Update Branch** button, click **Update with rebase**, and then click **Rebase branch**. Previously, **Update branch** performed a traditional merge that always resulted in a merge commit in your pull request branch. This option is still available, but now you have the choice. For more information, see "[Keeping your pull request in sync with the base branch](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/keeping-your-pull-request-in-sync-with-the-base-branch)." + - Pull Requestのトピックブランチがベースブランチよりも古くなってしまっている場合、ベースブランチの最新バージョンでリベースすることによって更新できるようになりました。リベースによって自分のブランチの変更がベースブランチの最新バージョンに適用されるので、マージコミットが作成されないことからブランチは直線的な履歴を持つことになります。リベースによって更新を行うには、**Update Branch（ブランチの更新）**ボタンの隣にあるドロップダウンメニューをクリックし、**Update with rebase（リベースして更新）**をクリックし、続いて**Rebase branch（ブランチをリベース）**をクリックしてください。以前は、**Update branch**は旧来のマージを行い、常にPull Requestのブランチにマージコミットが生じました。この選択肢も引き続き利用できますが、選択をできるようになりました。詳しい情報については「[Pull Requestとベースブランチとの同期を保つ](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/keeping-your-pull-request-in-sync-with-the-base-branch)」を参照してください。 - - A new repository setting allows the **Update branch** button to always be available when a pull request's topic branch is not up to date with the base branch. Previously, this button was only available when the **Require branches to be up to date before merging** branch protection setting was enabled. People with admin or maintainer access can manage the **Always suggest updating pull request branches** setting from the **Pull Requests** section in repository settings. For more information, see "[Managing suggestions to update pull request branches](/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-suggestions-to-update-pull-request-branches)." + - 新しいリポジトリ設定によって、Pull Requestのトピックブランチがベースブランチよりも古くなっている場合に**Update branch**ボタンを常に利用できるようにすることができます。以前は、このボタンが利用できるのは**Require branches to be up to date before merging（マージの際にはブランチが最新であることが必須）**ブランチ保護設定が有効化されている場合のみでした。管理もしくはメンテナアクセスを持つ人は、 リポジトリの設定の**Pull Requests**セクションの**Always suggest updating pull request branches（常にPull Requestブランチの更新を提案）**設定を管理できます。詳しい情報については「[Pull Requestブランチの更新提案の管理](/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-suggestions-to-update-pull-request-branches)」を参照してください。 - - heading: Configure custom HTTP headers for GitHub Pages sites + heading: GitHub PagesサイトのカスタムHTTPヘッダの設定 notes: - | - You can now configure custom HTTP headers that apply to all GitHub Pages sites served from your GitHub Enterprise Server instance. For more information, see "[Configuring GitHub Pages for your enterprise](/admin/configuration/configuring-your-enterprise/configuring-github-pages-for-your-enterprise#configuring-github-pages-response-headers-for-your-enterprise)." + GitHub Enterprise Serverインスタンスから提供されるすべてのGitHub Pagesサイトに適用されるカスタムHTTPヘッダを設定できるようになりました。詳しい情報については「[EnterpriseでのGitHub Pagesの設定](/admin/configuration/configuring-your-enterprise/configuring-github-pages-for-your-enterprise#configuring-github-pages-response-headers-for-your-enterprise)」を参照してください。 - - heading: Ignore commits in blame view + heading: blameビューでのコミットの無視 notes: - | - It's now possible to ignore revisions in the blame view by creating a _.git-blame-ignore-revs_ file in the root of your repository. For more information, see "[Viewing a file](/repositories/working-with-files/using-files/viewing-a-file#ignore-commits-in-the-blame-view)." + リポジトリのルートに_.git-blame-ignore-revs_ファイルを作成することによって、blameビューでリビジョンを無視できるようになりました。詳しい情報については「[ファイルの表示](/repositories/working-with-files/using-files/viewing-a-file#ignore-commits-in-the-blame-view)」を参照してください。 - - heading: Light high contrast theme is generally available + heading: 軽量高コントラストテーマが一般提供になりました notes: - | - A light high contrast theme, with greater contrast between foreground and background elements, is now generally available. For more information, see "[Managing your theme settings](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings)." + 前面要素と背景要素間のコントラストが大きい軽量高コントラストテーマが一般提供になりました。詳しい情報については「[テーマ設定の管理](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings)」を参照してください。 - heading: Tag protection rules notes: - | - Repository owners can now configure tag protection rules to protect a repository's tags. Once protected by a tag protection rule, tags matching a specified name pattern can only be created and deleted by users with the Maintain or Admin role in the repository. For more information, see "[Configuring tag protection rules](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-tag-protection-rules)." + リポジトリオーナーは、リポジトリのタグを保護するためのタグ保護ルールを設定できるようになりました。タグ保護ルールで保護されると、特定の名前のパターンにマッチするタグは、リポジトリのMaintainもしくはAdminロールを持つユーザだけが作成及び削除できるようになります。詳しい情報については「[タグ保護ルールの設定](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-tag-protection-rules)」を参照してください。 bugs: - | - It is now possible for GitHub Apps to upload release assets. + GitHub Appがリリースアセットをアップロードできるようになりました。 changes: - | - To use the device authorization flow for OAuth and GitHub Apps, you must manually enable the feature. This change reduces the likelihood of apps being used in phishing attacks against GitHub Enterprise Server users by ensuring integrators are aware of the risks and make a conscious choice to support this form of authentication. If you own or manage an OAuth App or GitHub App and you want to use the device flow, you can enable it for your app via the app's settings page. The device flow API endpoints will respond with status code `400` to apps that have not enabled this feature. For more information, see "[Authorizing OAuth Apps](/developers/apps/building-oauth-apps/authorizing-oauth-apps#device-flow)." + OAuth及びGitHub Appsでデバイス認可フローを使うためには、この機能を手動で有効化しなければなりません。この変更は、アプリケーションがGitHub Enterprise Serverのユーザに対するフィッシング攻撃に使われる可能性を、インテグレーターがそのリスクを認識し、この形態の認証をサポートする意識的な選択を確実に行うことによって下げるものです。OAuth AppもしくはGitHub Appを所有もしくは管理していて、デバイスフローを使いたいのであれば、アプリケーションの設定ページからアプリケーションに対して有効化できます。デバイスフローAPIのエンドポイントは、この機能が有効化されていないアプリケーションに対してはステータスコード`400`を返します。詳しい情報については「[OAuth Appsの認可](/developers/apps/building-oauth-apps/authorizing-oauth-apps#device-flow)」を参照してください。 - | - The code scanning alert page now always shows the alert status and information for the default branch. There is a new "Affected branches" panel in the sidebar where you can see the status of the alert in other branches. If the alert does not exist in your default branch, the alert page will show the status as "In branch" or "In pull request" for the location where the alert was last seen. This improvement makes it easier to understand the status of alerts which have been introduced into your code base. For more information, see "[About code scanning alerts](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts#about-alert-details)." + Code scanningのアラートページは、デフォルトブランチに対するアラートのステータスと情報を常に表示するようになりました。サイドバーには新しい"Affected branches（影響を受けるブランチ）"パネルがあり、他のブランチでのアラートのステータスを見ることができます。デフォルトブランチにアラートがない場合には、アラートページは最後にアラートが見られた場所について"In branch（ブランチ内）"あるいは"In pull request（Pull Request内）"というステータスを表示します。この開演によって、コードベースに持ち込まれたアラートのステータスを理解しやすくなります。詳しい情報については「[Code scanningアラートについて](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts#about-alert-details)」を参照してください。 - The alert list page is not changed and can be filtered by `branch`. You can use the code scanning API to retrieve more detailed branch information for alerts. For more information, see "[Code Scanning](/rest/code-scanning)" in the REST API documentation. + アラートのリストページは変更されておらず、`branch`でフィルタリングできます。Code scanning APIを使ってアラートに関する詳細なブランチ情報を取得できます。詳しい情報については、REST APIドキュメンテーションの「[Code scanning](/rest/code-scanning)」を参照してください。 - | - Code scanning now shows the details of the analysis origin of an alert. If an alert has more than one analysis origin, it is shown in the "Affected branches" sidebar and in the alert timeline. You can hover over the analysis origin icon in the "Affected branches" sidebar to see the alert status in each analysis origin. If an alert only has a single analysis origin, no information about analysis origins is displayed on the alert page. These improvements will make it easier to understand your alerts. In particular, it will help you understand those that have multiple analysis origins. This is especially useful for setups with multiple analysis configurations, such as monorepos. For more information, see "[About code scanning alerts](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts#about-analysis-origins)." + Code scanningは、アラートの分析元の詳細を表示するようになりました。アラートが複数の分析元を持つ場合、それは"Affected branches（影響されるブランチ）"及びアラートのタイムラインに表示されます。"Affected branches"サイドバー内の分析元のアイコンにカーソルを乗せると、それぞれの分析元のアラートステータスが表示されます。アラートが1つの分析元だけを持つ場合、アラートページには分析元に関する情報は表示されません。これらの改善によって、アラートを理解しやすくなります。特に、複数の分析元を持つアラートを理解するために役立ちます。これは、モノリポジトリのように複数の分析設定を持つ構成で役に立ちます。詳しい情報については「[Code scanningアラートについて](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts#about-analysis-origins)」を参照してください。 - | - Lists of repositories owned by a user or organization now have an additional filter option, "Templates", making it easier to find template repositories. + ユーザもしくはOrganizationが所有するリポジトリのリストに追加のフィルタオプションの"Templates"が追加され、テンプレートリポジトリを見つけやすくなりました。 - | - GitHub Enterprise Server can display several common image formats, including PNG, JPG, GIF, PSD, and SVG, and provides several ways to compare differences between versions. Now when reviewing added or changed images in a pull request, previews of those images are shown by default. Previously, you would see a message indicating that binary files could not be shown and you would need to toggle the "Display rich diff" option. For more information, see "[Working with non-code files](/repositories/working-with-files/using-files/working-with-non-code-files)." + GitHub Enterprise Serverは、PNG、JPG、GIF、PSD、SVGを含む一般的な画像フォーマットを表示でき、バージョン間の差異を比較する複数の方法を提供します。Pull Requestで追加もしくは変更された画像をレビューする際に、それらの画像のプレビューがデフォルトで表示されるようになりました。以前は、バイナリファイルは表示できないことを示すメッセージが表示され、"Display rich diff（リッチdiffの表示）"オプションを切り替える必要がありました。詳しい情報については「[コード以外のファイルの扱い](/repositories/working-with-files/using-files/working-with-non-code-files)」を参照してください。 - | - New gists are now created with a default branch name of either `main` or the alternative default branch name defined in your user settings. This matches how other repositories are created on GitHub Enterprise Server. For more information, see "[About branches](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches#about-the-default-branch)" and "[Managing the default branch name for your repositories](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-the-default-branch-name-for-your-repositories)." + 新しいGistは、デフォルトのブランチ名を`main`もしくはユーザ設定で定義された代替のデフォルトブランチ名として作成されるようになりました。これは、GitHub Enterprise Serverで他のリポジトリが作成されるのと同様になります。詳しい情報については「[ブランチについて](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches#about-the-default-branch)」及び「[リポジトリのデフォルトブランチ名の管理](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-the-default-branch-name-for-your-repositories)」を参照してください。 - | - Gists now only show the 30 most recent comments when first displayed. You can click **Load earlier comments...** to view more. This allows gists that have many comments to appear more quickly. For more information, see "[Editing and sharing content with gists](/get-started/writing-on-github/editing-and-sharing-content-with-gists)." + Gistは、最初に表示される際に最近の30のコメントだけを表示するようになりました。**Load earlier comments...（以前のコメントのロード）**をクリックすれば、もっと多くのコメントを見ることができます。これによって、多くのコメントを持つGistが素早く表示されるようになります。詳しい情報については「[Gistでのコメントの編集と共有](/get-started/writing-on-github/editing-and-sharing-content-with-gists)」を参照してください。 - | - Settings pages for users, organizations, repositories, and teams have been redesigned, grouping similar settings pages into sections for improved information architecture and discoverability. For more information, see the [GitHub changelog](https://github.blog/changelog/2022-02-02-redesign-of-githubs-settings-pages/). + ユーザ、Organization、リポジトリ、Teamの設定ページは再設計され、情報アーキテクチャと発見性を改善するため、同じような設定ページがセクションにグループ化されました。詳しい情報については[GitHub changelog](https://github.blog/changelog/2022-02-02-redesign-of-githubs-settings-pages/)を参照してください。 - | - Focusing or hovering over a label now displays the label description in a tooltip. + ラベルにフォーカスやカーソルを当てると、ツールチップにラベルの説明が表示されるようになりました。 - | - Creating and removing repository invitations, whether done through the API or web interface, are now subject to rate limits that may be enabled on your GitHub Enterprise Server instance. For more information about rate limits, see "[Configuring rate limits](/admin/configuration/configuring-your-enterprise/configuring-rate-limits)." + リポジトリへの招待の作成と削除は、それがAPIで行われているかWebインターフェースで行われているかにかかわらず、GitHub Enterprise Serverインスタンスで有効化されていることがあるレート制限の対象になります。レート制限に関する詳しい情報については「[レート制限の設定](/admin/configuration/configuring-your-enterprise/configuring-rate-limits)」を参照してください。 - | - MinIO has announced the removal of the MinIO Gateways starting June 1st, 2022. While MinIO Gateway for NAS continues to be one of the supported storage providers for Github Actions and Github Packages, we recommend moving to MinIO LTS support to avail support and bug fixes from MinIO. For more information about rate limits, see "[Scheduled removal of MinIO Gateway for GCS, Azure, HDFS in the minio/minio repository](https://github.com/minio/minio/issues/14331)." + MinIOは、2022年6月1日からのMinIO Gatewaysの廃止をアナウンスしました。MinIO Gateway for NASは、引き続きGitHub Actions及びGitHub Packagesのサポート対象ストレージプロバイダの1つであり続けますが、MinIOからのサポートとバグ修正を利用し続けるために、MinIO LTSサポートへの移行をおすすめします。レート制限に関する詳しい情報については「[minio/minioリポジトリでのGCS、Azure、HDFS用のMinIO Gatewayの予定された廃止](https://github.com/minio/minio/issues/14331)」を参照してください。 deprecations: - - heading: Change to the format of authentication tokens + heading: 認証トークンのフォーマット変更 notes: - | - GitHub Connect will no longer work after June 3rd for instances running GitHub Enterprise Server 3.1 or older, due to the format of GitHub authentication tokens changing. For more information, see the [GitHub changelog](https://github.blog/changelog/2021-03-31-authentication-token-format-updates-are-generally-available/). + GitHub認証トークンのフォーマット変更により、GitHub Enterprise Server 3.1以前を動作させているインスタンスでは、6月3日以降GitHub Connectは動作しなくなります。詳しい情報については[GitHub changelog](https://github.blog/changelog/2021-03-31-authentication-token-format-updates-are-generally-available/)を参照してください。 - - heading: CodeQL runner deprecated in favor of CodeQL CLI + heading: CodeQL runnerはCodeQL CLIを代替として非推奨になりました notes: - | - The CodeQL runner is deprecated in favor of the CodeQL CLI. GitHub Enterprise Server 3.4 and later no longer include the CodeQL runner. This deprecation only affects users who use CodeQL code scanning in 3rd party CI/CD systems. GitHub Actions users are not affected. GitHub strongly recommends that customers migrate to the CodeQL CLI, which is a feature-complete replacement for the CodeQL runner and has many additional features. For more information, see "[Migrating from the CodeQL runner to CodeQL CLI](/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/migrating-from-the-codeql-runner-to-codeql-cli)." + CodeQLランナーは、CodeQL CLIを代替として非推奨になりました。GitHub Enterprise Server 3.4以降には、CodeQLランナーは含まれなくなります。この非推奨化は、CodeQLコードスキャンニングをサードパーティのCI/CDシステムで利用しているユーザにのみ影響します。GitHub Actionsのユーザは影響されません。GitHubは、CodeQLランナーと機能的に互換であり、多くの追加機能を持つ代替製品であるCodeQL CLIへの移行をお客様に強くおすすめします。詳しい情報については「[CodeQLランナーからCodeQL CLIへの移行(/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/migrating-from-the-codeql-runner-to-codeql-cli)」を参照してください。 - heading: GitHub Pagesのテーマピッカーの削除 notes: @@ -341,5 +341,5 @@ sections: - GitHub Connectで"Users can search GitHub.com"が有効化されている場合、GitHub.comの検索結果にプライベート及びインターナルリポジトリのIssueが含まれません。 - '{% data variables.product.prodname_registry %}のnpmレジストリは、メタデータのレスポンス中で時間の値を返さなくなります。これは、大きなパフォーマンス改善のために行われました。メタデータレスポンスの一部として時間の値を返すために必要なすべてのデータは保持し続け、既存のパフォーマンスの問題を解決した将来に、この値を返すことを再開します。' - pre-receive フックの処理に固有のリソース制限によって、pre-receive フックに失敗するものが生じることがあります。 - - Actions services need to be restarted after restoring an appliance from a backup taken on a different host. - - 'Deleted repositories will not be purged from disk automatically after the 90-day retention period ends. [Updated: 2022-06-08]' + - 別のホスト上で取られたバックアップからのアプライアンスのリストア後、Actionsサービスを再起動する必要があります。 + - '削除されたリポジトリは、90日の保存期間が終了したあとに自動的にディスクから削除されません。[2022年06月08日更新]' diff --git a/translations/ja-JP/data/reusables/secret-scanning/partner-secret-list-private-repo.md b/translations/ja-JP/data/reusables/secret-scanning/partner-secret-list-private-repo.md index 8895e000e5..b1f855cb90 100644 --- a/translations/ja-JP/data/reusables/secret-scanning/partner-secret-list-private-repo.md +++ b/translations/ja-JP/data/reusables/secret-scanning/partner-secret-list-private-repo.md @@ -147,6 +147,8 @@ Plivo | Plivo Auth ID | plivo_auth_id{% endif %} Plivo | Plivo Auth Token | plivo_auth_token{% endif %} Postman | Postman API Key | postman_api_key Proctorio | Proctorio Consumer Key | proctorio_consumer_key Proctorio | Proctorio Linkage Key | proctorio_linkage_key Proctorio | Proctorio Registration Key | proctorio_registration_key Proctorio | Proctorio Secret Key | proctorio_secret_key Pulumi | Pulumi Access Token | pulumi_access_token {%- ifversion fpt or ghec or ghes > 3.1 or ghae %} PyPI | PyPI API Token | pypi_api_token{% endif %} +{%- ifversion fpt or ghec or ghes > 3.5 or ghae-issue-7375 %} +redirect.pizza | redirect.pizza API Token | redirect_pizza_api_token{% endif %} {%- ifversion fpt or ghec or ghes > 3.1 or ghae %} RubyGems | RubyGems API Key | rubygems_api_key{% endif %} Samsara | Samsara API Token | samsara_api_token Samsara | Samsara OAuth Access Token | samsara_oauth_access_token {%- ifversion fpt or ghec or ghes > 3.4 or ghae-issue-6944 %} diff --git a/translations/ja-JP/data/reusables/secret-scanning/partner-secret-list-public-repo.md b/translations/ja-JP/data/reusables/secret-scanning/partner-secret-list-public-repo.md index 03b36846f3..3cbc4ef740 100644 --- a/translations/ja-JP/data/reusables/secret-scanning/partner-secret-list-public-repo.md +++ b/translations/ja-JP/data/reusables/secret-scanning/partner-secret-list-public-repo.md @@ -77,6 +77,7 @@ | Proctorio | Proctorio Secret Key | | Pulumi | Pulumi Access Token | | PyPI | PyPI API Token | +| redirect.pizza | redirect.pizza API Token | | RubyGems | RubyGems API Key | | Samsara | Samsara API Token | | Samsara | Samsara OAuth Access Token | diff --git a/translations/ja-JP/data/reusables/secret-scanning/secret-list-private-push-protection.md b/translations/ja-JP/data/reusables/secret-scanning/secret-list-private-push-protection.md index 53fad59f40..0351b6a168 100644 --- a/translations/ja-JP/data/reusables/secret-scanning/secret-list-private-push-protection.md +++ b/translations/ja-JP/data/reusables/secret-scanning/secret-list-private-push-protection.md @@ -60,16 +60,5 @@ | PlanetScale | PlanetScale Service Token | planetscale_service_token | | Postman | Postman API Key | postman_api_key | | Proctorio | Proctorio Secret Key | proctorio_secret_key | -| Samsara | Samsara API Token | samsara_api_token | -| Samsara | Samsara OAuth Access Token | samsara_oauth_access_token | -| SendGrid | SendGrid API Key | sendgrid_api_key | -| Sendinblue | Sendinblue API Key | sendinblue_api_key | -| Sendinblue | Sendinblue SMTP Key | sendinblue_smtp_key | -| Shippo | Shippo Live API Token | shippo_live_api_token | -| Shopify | Shopify App Shared Secret | shopify_app_shared_secret | -| Shopify | Shopify Access Token | shopify_access_token | -| Slack | Slack API Token | slack_api_token | -| Stripe | Stripe Live API Secret Key | stripe_api_key | -| Tencent Cloud | Tencent Cloud Secret ID | tencent_cloud_secret_id | -| Typeform | Typeform Personal Access Token | typeform_personal_access_token | -| WorkOS | WorkOS Production API Key | workos_production_api_key | +{%- ifversion fpt or ghec or ghes > 3.5 or ghae-issue-7375 %} +redirect.pizza | redirect.pizza API Token | redirect_pizza_api_token{% endif %} Samsara | Samsara API Token | samsara_api_token Samsara | Samsara OAuth Access Token | samsara_oauth_access_token SendGrid | SendGrid API Key | sendgrid_api_key Sendinblue | Sendinblue API Key | sendinblue_api_key Sendinblue | Sendinblue SMTP Key | sendinblue_smtp_key Shippo | Shippo Live API Token | shippo_live_api_token Shopify | Shopify App Shared Secret | shopify_app_shared_secret Shopify | Shopify Access Token | shopify_access_token Slack | Slack API Token | slack_api_token Stripe | Stripe Live API Secret Key | stripe_api_key Tencent Cloud | Tencent Cloud Secret ID | tencent_cloud_secret_id Typeform | Typeform Personal Access Token | typeform_personal_access_token WorkOS | WorkOS Production API Key | workos_production_api_key diff --git a/translations/log/cn-resets.csv b/translations/log/cn-resets.csv index 2363885af4..691c388a60 100644 --- a/translations/log/cn-resets.csv +++ b/translations/log/cn-resets.csv @@ -16,6 +16,7 @@ translations/zh-CN/content/actions/hosting-your-own-runners/adding-self-hosted-r translations/zh-CN/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md,Listed in localization-support#489 translations/zh-CN/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md,broken liquid tags translations/zh-CN/content/actions/learn-github-actions/usage-limits-billing-and-administration.md,broken liquid tags +translations/zh-CN/content/actions/managing-workflow-runs/re-running-workflows-and-jobs.md,rendering error translations/zh-CN/content/actions/managing-workflow-runs/removing-workflow-artifacts.md,broken liquid tags translations/zh-CN/content/actions/managing-workflow-runs/reviewing-deployments.md,Listed in localization-support#489 translations/zh-CN/content/actions/security-guides/security-hardening-for-github-actions.md,broken liquid tags 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 e3199cddc6..b722c71b7f 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 @@ -34,7 +34,10 @@ Você pode armazenar uma série de projetos em repositórios de {% data variable {% note %} -**Observação:** você pode criar repositórios públicos para um projeto de código aberto. Ao criar um repositório público, certifique-se de incluir um [arquivo de licença](https://choosealicense.com/) que determina como deseja que seu projeto seja compartilhado com outras pessoas. {% data reusables.open-source.open-source-guide-repositories %} {% data reusables.open-source.open-source-learning %} +**Notas:** +- You can create public repositories for an open source project. Ao criar um repositório público, certifique-se de incluir um [arquivo de licença](https://choosealicense.com/) que determina como deseja que seu projeto seja compartilhado com outras pessoas. {% data reusables.open-source.open-source-guide-repositories %} +- {% data reusables.open-source.open-source-learning %} +- You can also add community health files to your repositories, to set guidelines on how to contribute, keep your repositories safe, and much more. Para obter mais informações, consulte "[Criando um arquivo padrão de integridade da comunidade](/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file)." {% endnote %} diff --git a/translations/pt-BR/content/site-policy/privacy-policies/github-privacy-statement.md b/translations/pt-BR/content/site-policy/privacy-policies/github-privacy-statement.md index 3ae584aaee..84f170c797 100644 --- a/translations/pt-BR/content/site-policy/privacy-policies/github-privacy-statement.md +++ b/translations/pt-BR/content/site-policy/privacy-policies/github-privacy-statement.md @@ -177,7 +177,7 @@ We retain and use your information as described in this Privacy Statement, but b If GitHub processes Personal Data other than your profile information, such as information about you GitHub receives from [third parties](/github/site-policy/github-privacy-statement#information-we-collect-from-third-parties), then you may, subject to applicable law, access, update, alter, delete, object to or restrict the processing of your Personal Data by contacting [GitHub Support](https://support.github.com/contact) or [GitHub Premium Support](https://enterprise.githubsupport.com/hc/en-us). -You can adjust the settings on your Account regarding the display of your Personal Data in private or public repositories or Personal Data processed in connection with Community Features (such as the GitHub Feed, the GitHub Globe, GitHub Explore, the GitHub Discussion Leaderboard) through [profile settings](https://github.com/settings/profile). +You can adjust the settings on your Account regarding the display of your Personal Data in private or public repositories or Personal Data processed in connection with Community Features (such as GitHub Feed, GitHub Sponsors, and GitHub Explore) through [profile settings](https://github.com/settings/profile). Additionally, if you are unable to access certain Personal Data we have via the means described above, you can request access by contacting us as described at the bottom of this privacy statement. @@ -268,7 +268,7 @@ Envie suas perguntas sobre nossas práticas de coleta de informações ou a Decl Consulte abaixo este documento traduzido para outros idiomas. Em caso de conflito, incerteza ou aparente incoerência entre quaisquer versões traduzidas e a versão original em inglês, o documento em inglês prevalecerá. ### French -Cliquez ici pour obtenir la version française: [Déclaration de confidentialité de GitHub](/assets/images/help/site-policy/github-privacy-statement(07.22.20)(FR).pdf) +Clique aqui para consultar a versão em francês: [Déclaration de confidentialité de GitHub](/assets/images/help/site-policy/github-privacy-statement(07.22.20)(FR).pdf) ### Outras traduções diff --git a/translations/pt-BR/data/features/README.md b/translations/pt-BR/data/features/README.md index da21162c57..50043e53d8 100644 --- a/translations/pt-BR/data/features/README.md +++ b/translations/pt-BR/data/features/README.md @@ -45,7 +45,7 @@ versions: ## Aplicação de esquema -O esquema para validar a versão do recurso encontra-se em [`tests/helpers/schemas/feature-versions-schema.js`](/tests/helpers/schemas/feature-versions-schema.js) e é exercido por [`tests/linting/lint-files.js`](/tests/linting/lint-files.js). +O esquema para validar a versão do recurso encontra-se em [`tests/helpers/schemas/feature-versions-schema.js`](/tests/helpers/schemas/feature-versions-schema.js) e é exercido por [`tests/linting/lint-versioning.js`](/tests/linting/lint-versioning.js). ## Script para remover tags de recursos diff --git a/translations/pt-BR/data/reusables/secret-scanning/partner-secret-list-private-repo.md b/translations/pt-BR/data/reusables/secret-scanning/partner-secret-list-private-repo.md index 0cbaa7a827..2bfe44945e 100644 --- a/translations/pt-BR/data/reusables/secret-scanning/partner-secret-list-private-repo.md +++ b/translations/pt-BR/data/reusables/secret-scanning/partner-secret-list-private-repo.md @@ -147,6 +147,8 @@ Plivo | Plivo Auth ID | plivo_auth_id{% endif %} Plivo | Plivo Auth Token | plivo_auth_token{% endif %} Postman | Postman API Key | postman_api_key Proctorio | Proctorio Consumer Key | proctorio_consumer_key Proctorio | Proctorio Linkage Key | proctorio_linkage_key Proctorio | Proctorio Registration Key | proctorio_registration_key Proctorio | Proctorio Secret Key | proctorio_secret_key Pulumi | Pulumi Access Token | pulumi_access_token {%- ifversion fpt or ghec or ghes > 3.1 or ghae %} PyPI | PyPI API Token | pypi_api_token{% endif %} +{%- ifversion fpt or ghec or ghes > 3.5 or ghae-issue-7375 %} +redirect.pizza | redirect.pizza API Token | redirect_pizza_api_token{% endif %} {%- ifversion fpt or ghec or ghes > 3.1 or ghae %} RubyGems | RubyGems API Key | rubygems_api_key{% endif %} Samsara | Samsara API Token | samsara_api_token Samsara | Samsara OAuth Access Token | samsara_oauth_access_token {%- ifversion fpt or ghec or ghes > 3.4 or ghae-issue-6944 %} diff --git a/translations/pt-BR/data/reusables/secret-scanning/partner-secret-list-public-repo.md b/translations/pt-BR/data/reusables/secret-scanning/partner-secret-list-public-repo.md index 4c05e473dc..0259d7da64 100644 --- a/translations/pt-BR/data/reusables/secret-scanning/partner-secret-list-public-repo.md +++ b/translations/pt-BR/data/reusables/secret-scanning/partner-secret-list-public-repo.md @@ -77,6 +77,7 @@ | Proctorio | Chave de segredo de Proctorio | | Pulumi | Token de acesso de Pulumi | | PyPI | PyPI API Token | +| redirect.pizza | redirect.pizza API Token | | RubyGems | RubyGems API Key | | Samsara | Token de API de Samsara | | Samsara | Token de acesso de OAuth de Samsara | diff --git a/translations/pt-BR/data/reusables/secret-scanning/secret-list-private-push-protection.md b/translations/pt-BR/data/reusables/secret-scanning/secret-list-private-push-protection.md index 865b5cad3d..9d54d8a2f8 100644 --- a/translations/pt-BR/data/reusables/secret-scanning/secret-list-private-push-protection.md +++ b/translations/pt-BR/data/reusables/secret-scanning/secret-list-private-push-protection.md @@ -60,16 +60,5 @@ | PlanetScale | PlanetScale Service Token | planetscale_service_token | | Postman | Chave da API de Postman | postman_api_key | | Proctorio | Chave de segredo de Proctorio | proctorio_secret_key | -| Samsara | Token de API de Samsara | samsara_api_token | -| Samsara | Token de acesso de OAuth de Samsara | samsara_oauth_access_token | -| SendGrid | SendGrid API Key | sendgrid_api_key | -| Sendinblue | Sendinblue API Key | sendinblue_api_key | -| Sendinblue | Sendinblue SMTP Key | sendinblue_smtp_key | -| Shippo | Shippo Live API Token | shippo_live_api_token | -| Shopify | Segredo compartilhado do aplicativo Shopify | shopify_app_shared_secret | -| Shopify | Token de acesso de Shopify | shopify_access_token | -| Slack | Token da API de Slack | slack_api_token | -| Stripe | Chave de segredo Stripe Live | stripe_api_key | -| Tencent Cloud | ID de segredot de Tencent Cloud | tencent_cloud_secret_id | -| Typeform | Typeform Personal Access Token | typeform_personal_access_token | -| WorkOS | WorkOS Production API Key | workos_production_api_key | +{%- ifversion fpt or ghec or ghes > 3.5 or ghae-issue-7375 %} +redirect.pizza | redirect.pizza API Token | redirect_pizza_api_token{% endif %} Samsara | Samsara API Token | samsara_api_token Samsara | Samsara OAuth Access Token | samsara_oauth_access_token SendGrid | SendGrid API Key | sendgrid_api_key Sendinblue | Sendinblue API Key | sendinblue_api_key Sendinblue | Sendinblue SMTP Key | sendinblue_smtp_key Shippo | Shippo Live API Token | shippo_live_api_token Shopify | Shopify App Shared Secret | shopify_app_shared_secret Shopify | Shopify Access Token | shopify_access_token Slack | Slack API Token | slack_api_token Stripe | Stripe Live API Secret Key | stripe_api_key Tencent Cloud | Tencent Cloud Secret ID | tencent_cloud_secret_id Typeform | Typeform Personal Access Token | typeform_personal_access_token WorkOS | WorkOS Production API Key | workos_production_api_key diff --git a/translations/zh-CN/content/actions/examples/index.md b/translations/zh-CN/content/actions/examples/index.md index 7193f6904e..a7c82aff0e 100644 --- a/translations/zh-CN/content/actions/examples/index.md +++ b/translations/zh-CN/content/actions/examples/index.md @@ -1,7 +1,7 @@ --- title: 示例 shortTitle: 示例 -intro: 'Example workflows that demonstrate the CI/CD features of {% data variables.product.prodname_actions %}.' +intro: '演示 {% data variables.product.prodname_actions %} 的 CI/CD 功能的示例工作流程。' versions: fpt: '*' ghes: '*' diff --git a/translations/zh-CN/content/actions/examples/using-concurrency-expressions-and-a-test-matrix.md b/translations/zh-CN/content/actions/examples/using-concurrency-expressions-and-a-test-matrix.md index eed94ac8e8..b229b0c3b8 100644 --- a/translations/zh-CN/content/actions/examples/using-concurrency-expressions-and-a-test-matrix.md +++ b/translations/zh-CN/content/actions/examples/using-concurrency-expressions-and-a-test-matrix.md @@ -618,7 +618,7 @@ jobs: -This step uses the `actions/cache` action to cache the Next.js build, so that the workflow will attempt to retrieve a cache of the build, and not rebuild it from scratch every time. For more information, see "[Caching dependencies to speed up workflows](/actions/using-workflows/caching-dependencies-to-speed-up-workflows)." +此步骤使用“actions/cache”操作来缓存 Next.js 构建，以便工作流程尝试检索构建的缓存，而不是每次都从头开始重新构建。 更多信息请参阅“[缓存依赖关系以加快工作流程](/actions/using-workflows/caching-dependencies-to-speed-up-workflows)”。 @@ -631,7 +631,7 @@ This step uses the `actions/cache` action to cache the Next.js build, so that th -This step runs the build script. +此步骤运行构建脚本。 @@ -647,7 +647,7 @@ This step runs the build script. -This step runs the tests using `npm test`, and the test matrix provides a different value for {% raw %}`${{ matrix.test-group }}`{% endraw %} for each job in the matrix. It uses the `DIFF_FILE` environment variable to know which files have changed, and uses the `CHANGELOG_CACHE_FILE_PATH` environment variable for the changelog cache file. +此步骤使用“npm test”运行测试，并且测试矩阵为矩阵中的每个作业提供不同的 {% raw %}`${{ matrix.test-group }}`{% endraw %} 值。 它使用“DIFF_FILE”环境变量来了解哪些文件已更改，并将“CHANGELOG_CACHE_FILE_PATH”环境变量用于更改日志缓存文件。 diff --git a/translations/zh-CN/content/actions/examples/using-scripts-to-test-your-code-on-a-runner.md b/translations/zh-CN/content/actions/examples/using-scripts-to-test-your-code-on-a-runner.md index 0e2b924e2c..7f377ab2fb 100644 --- a/translations/zh-CN/content/actions/examples/using-scripts-to-test-your-code-on-a-runner.md +++ b/translations/zh-CN/content/actions/examples/using-scripts-to-test-your-code-on-a-runner.md @@ -1,7 +1,7 @@ --- -title: Using scripts to test your code on a runner -shortTitle: Using scripts to test your code on a runner -intro: 'How to use essential {% data variables.product.prodname_actions %} features for continuous integration (CI).' +title: 使用脚本在运行器上测试代码 +shortTitle: 使用脚本在运行器上测试代码 +intro: '如何使用必要 {% data variables.product.prodname_actions %} 功能进行持续集成 (CI)。' versions: fpt: '*' ghes: '> 3.1' @@ -23,7 +23,7 @@ topics: ## 示例概述 -{% data reusables.actions.example-workflow-intro-ci %} When this workflow is triggered, it automatically runs a script that checks whether the {% data variables.product.prodname_dotcom %} Docs site has any broken links. +{% data reusables.actions.example-workflow-intro-ci %} 此工作流程被触发时，它会自动运行一个脚本，用于检查 {% data variables.product.prodname_dotcom %} 文档网站是否有任何断开的链接。 {% data reusables.actions.example-diagram-intro %} @@ -44,7 +44,7 @@ topics: |在不同的运行器上运行作业，具体取决于存储库：| [`runs-on`](/actions/using-jobs/choosing-the-runner-for-a-job)| {% data reusables.actions.checkout-action-table-entry %} {% data reusables.actions.setup-node-table-entry %} -| Using a third-party action: | [`trilom/file-changes-action`](https://github.com/trilom/file-changes-action)| | Running a script on the runner: | Using `./script/rendered-content-link-checker.mjs` | +|使用第三方操作：| [`trilom/file-changes-action`](https://github.com/trilom/file-changes-action)| |在运行器上运行脚本：|使用 `./script/rendered-content-link-checker.mjs` | ## 示例工作流程 @@ -181,7 +181,7 @@ on: -Add the `workflow_dispatch` event if you want to be able to manually run this workflow from the UI. For more information, see [`workflow_dispatch`](/actions/using-workflows/events-that-trigger-workflows#workflow_dispatch). +如果您希望能够从 UI 手动运行此工作流程，请添加“workflow_dispatch”事件。 更多信息请参阅 [`workflow_dispatch`](/actions/using-workflows/events-that-trigger-workflows#workflow_dispatch)。 @@ -195,7 +195,7 @@ Add the `workflow_dispatch` event if you want to be able to manually run this wo -Add the `push` event, so that the workflow runs automatically every time a commit is pushed to a branch called `main`. 更多信息请参阅 [`push`](/actions/using-workflows/events-that-trigger-workflows#push)。 +添加 'push' 事件，以便每次将提交推送到分支 `main` 时，工作流程都会自动运行。 更多信息请参阅 [`push`](/actions/using-workflows/events-that-trigger-workflows#push)。 @@ -272,7 +272,7 @@ jobs: -Defines a job with the ID `check-links` that is stored within the `jobs` key. +定义 ID 为“check-links”的作业，该作业存储在“jobs”键中。 @@ -298,7 +298,7 @@ Defines a job with the ID `check-links` that is stored within the `jobs` key. -Groups together all the steps that will run as part of the `check-links` job. 工作流程中的每个作业都有自己的“steps”部分。 +组合将作为“check-links”作业一部分运行的所有步骤。 工作流程中的每个作业都有自己的“steps”部分。 @@ -327,7 +327,7 @@ Groups together all the steps that will run as part of the `check-links` job. -This step uses the `actions/setup-node` action to install the specified version of the Node.js software package on the runner, which gives you access to the `npm` command. +此步骤使用“actions/setup-node”操作在运行器上安装指定版本的 Node.js 软件包，这使您可以访问“npm”命令。 @@ -341,7 +341,7 @@ This step uses the `actions/setup-node` action to install the specified version -The `run` keyword tells the job to execute a command on the runner. In this case, `npm ci` is used to install the npm software packages for the project. +“run”关键字指示作业在运行器上执行命令。 在这种情况下，“npm ci”用于为项目安装 npm 软件包。 @@ -357,7 +357,7 @@ The `run` keyword tells the job to execute a command on the runner. In this case -Uses the `trilom/file-changes-action` action to gather all the changed files. 此示例使用 'a6ca26c14274c33b15e6499323aac178af06ad4b' SHA固定到操作的特定版本。 +使用“trilom/file-changes-action”操作来收集所有已更改的文件。 此示例使用 'a6ca26c14274c33b15e6499323aac178af06ad4b' SHA固定到操作的特定版本。 @@ -371,7 +371,7 @@ Uses the `trilom/file-changes-action` action to gather all the changed files. -Lists the contents of `files.json`. This will be visible in the workflow run's log, and can be useful for debugging. +列出“files.json”的内容。 这将在工作流程运行的日志中可见，并且对于调试非常有用。 @@ -391,7 +391,7 @@ Lists the contents of `files.json`. This will be visible in the workflow run's l -This step uses `run` command to execute a script that is stored in the repository at `script/rendered-content-link-checker.mjs` and passes all the parameters it needs to run. +此步骤使用“run”命令执行存储在存储库中的“script/rendered-content-link-checker.mjs”中的脚本，并传递运行所需的所有参数。 @@ -410,7 +410,7 @@ This step uses `run` command to execute a script that is stored in the repositor -This step also uses `run` command to execute a script that is stored in the repository at `script/rendered-content-link-checker.mjs` and passes a different set of parameters. +此步骤还使用“run”命令来执行存储在存储库中的“script/rendered-content-link-checker.mjs”中的脚本，并传递一组不同的参数。 diff --git a/translations/zh-CN/content/actions/examples/using-the-github-cli-on-a-runner.md b/translations/zh-CN/content/actions/examples/using-the-github-cli-on-a-runner.md index 132599b6d0..7d68d8f9a8 100644 --- a/translations/zh-CN/content/actions/examples/using-the-github-cli-on-a-runner.md +++ b/translations/zh-CN/content/actions/examples/using-the-github-cli-on-a-runner.md @@ -1,6 +1,6 @@ --- -title: Using the GitHub CLI on a runner -shortTitle: Using the GitHub CLI on a runner +title: 在运行器上使用 GitHub CLI +shortTitle: 在运行器上使用 GitHub CLI intro: '如何使用高级 {% data variables.product.prodname_actions %} 功能进行持续集成 (CI)。' versions: fpt: '*' @@ -23,7 +23,7 @@ topics: ## 示例概述 -{% data reusables.actions.example-workflow-intro-ci %} When this workflow is triggered, it automatically runs a script that checks whether the {% data variables.product.prodname_dotcom %} Docs site has any broken links. If any broken links are found, the workflow uses the {% data variables.product.prodname_dotcom %} CLI to create a {% data variables.product.prodname_dotcom %} issue with the details. +{% data reusables.actions.example-workflow-intro-ci %} 此工作流程被触发时，它会自动运行一个脚本，用于检查 {% data variables.product.prodname_dotcom %} 文档网站是否有任何断开的链接。 如果发现任何断开的链接，工作流程将使用 {% data variables.product.prodname_dotcom %} CLI 创建包含详细信息的 {% data variables.product.prodname_dotcom %} 议题。 {% data reusables.actions.example-diagram-intro %} @@ -42,7 +42,7 @@ topics: {% data reusables.actions.secrets-table-entry %} {% data reusables.actions.checkout-action-table-entry %} {% data reusables.actions.setup-node-table-entry %} -| Using a third-party action: | [`peter-evans/create-issue-from-file`](https://github.com/peter-evans/create-issue-from-file)| | Running shell commands on the runner: | [`run`](/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idstepsrun) | | Running a script on the runner: | Using `script/check-english-links.js` | | Generating an output file: | Piping the output using the `>` operator | | Checking for existing issues using {% data variables.product.prodname_cli %}: | [`gh issue list`](https://cli.github.com/manual/gh_issue_list) | | Commenting on an issue using {% data variables.product.prodname_cli %}: | [`gh issue comment`](https://cli.github.com/manual/gh_issue_comment) | +| 使用第三方操作：| [`peter-evans/create-issue-from-file`](https://github.com/peter-evans/create-issue-from-file)| | 在运行器上运行 shell 命令：| [`run`](/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idstepsrun) | | 在运行器上运行脚本：| 使用 `script/check-english-links.js` | | 生成输出文件：| 使用 `>` 运算符传递输出 | | 使用 {% data variables.product.prodname_cli %} 检查现有议题：| [`gh issue list`](https://cli.github.com/manual/gh_issue_list) | | 使用 {% data variables.product.prodname_cli %} 评论议题：| [`gh issue comment`](https://cli.github.com/manual/gh_issue_comment) | ## 示例工作流程 @@ -213,10 +213,10 @@ on: -Defines the `workflow_dispatch` and `scheduled` as triggers for the workflow: +将“workflow_dispatch”和“scheduled”定义为工作流程的触发器： -* The `workflow_dispatch` lets you manually run this workflow from the UI. For more information, see [`workflow_dispatch`](/actions/using-workflows/events-that-trigger-workflows#workflow_dispatch). -* The `schedule` event lets you use `cron` syntax to define a regular interval for automatically triggering the workflow. For more information, see [`schedule`](/actions/reference/events-that-trigger-workflows#schedule). +* “workflow_dispatch”允许您从 UI 手动运行此工作流程。 更多信息请参阅 [`workflow_dispatch`](/actions/using-workflows/events-that-trigger-workflows#workflow_dispatch)。 +* “schedule”事件允许您使用“cron”语法来定义自动触发工作流程的定期间隔。 更多信息请参阅 [`schedule`](/actions/reference/events-that-trigger-workflows#schedule)。 @@ -255,7 +255,7 @@ jobs: -Defines a job with the ID `check_all_english_links`, and the name `Check all links`, that is stored within the `jobs` key. +定义 ID 为“check_all_english_links”和名称为“Check all links”的作业，该作业存储在“jobs”键中。 @@ -267,7 +267,7 @@ if: github.repository == 'github/docs-internal' -Only run the `check_all_english_links` job if the repository is named `docs-internal` and is within the `github` organization. Otherwise, the job is marked as _skipped_. +仅当存储库名为“docs-internal”并且位于“github”组织内时，才运行“check_all_english_links”作业。 否则，作业将标记为 _skiped_。 @@ -279,7 +279,7 @@ runs-on: ubuntu-latest -配置作业在 Ubuntu Linux 运行器上运行。 This means that the job will execute on a fresh virtual machine hosted by {% data variables.product.prodname_dotcom %}. For syntax examples using other runners, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idruns-on)." +配置作业在 Ubuntu Linux 运行器上运行。 这意味着作业将在由 {% data variables.product.prodname_dotcom %} 托管的新虚拟机上执行。 有关使用其他运行器的语法示例，请参阅“[{% data variables.product.prodname_actions %} 的工作流语法](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idruns-on)”。 @@ -295,7 +295,7 @@ runs-on: ubuntu-latest -Creates custom environment variables, and redefines the built-in `GITHUB_TOKEN` variable to use a custom [secret](/actions/security-guides/encrypted-secrets). These variables will be referenced later in the workflow. +创建自定义环境变量，并重新定义内置的“GITHUB_TOKEN”变量以使用自定义 [secret](/actions/security-guides/encrypted-secrets)。 稍后将在工作流程中引用这些变量。 @@ -307,7 +307,7 @@ Creates custom environment variables, and redefines the built-in `GITHUB_TOKEN` -Groups together all the steps that will run as part of the `check_all_english_links` job. Each job in the workflow has its own `steps` section. +组合将作为“check_all_english_links”作业一部分运行的所有步骤。 工作流程中的每个作业都有自己的“steps”部分。 @@ -351,7 +351,7 @@ Groups together all the steps that will run as part of the `check_all_english_li -The `run` keyword tells the job to execute a command on the runner. In this case, the `npm ci` and `npm run build` commands are run as separate steps to install and build the Node.js application in the repository. +“run”关键字指示作业在运行器上执行命令。 在这种情况下，“npm ci”和“npm run build”命令作为单独的步骤运行，以在存储库中安装和构建 Node.js 应用程序。 @@ -365,7 +365,7 @@ The `run` keyword tells the job to execute a command on the runner. In this case -This `run` command executes a script that is stored in the repository at `script/check-english-links.js`, and pipes the output to a file called `broken_links.md`. +此“run”命令执行存储在存储库中“script/check-english-links.js”的脚本，并将输出传递到名为“broken_links.md”的文件。 @@ -380,7 +380,7 @@ This `run` command executes a script that is stored in the repository at `script -If the `check-english-links.js` script detects broken links and returns a non-zero (failure) exit status, then use a [workflow command](/actions/using-workflows/workflow-commands-for-github-actions#setting-an-output-parameter) to set an output that has the value of the first line of the `broken_links.md` file (this is used the next step). +如果“check-english-links.js”脚本检测到断开的链接并返回非零（失败）退出状态，则使用 [工作流程命令](/actions/using-workflows/workflow-commands-for-github-actions#setting-an-output-parameter) 来设置具有 “broken_links.md” 文件第一行值的输出（这是在下一步中使用）。 @@ -402,7 +402,7 @@ If the `check-english-links.js` script detects broken links and returns a non-ze -Uses the `peter-evans/create-issue-from-file` action to create a new {% data variables.product.prodname_dotcom %} issue. This example is pinned to a specific version of the action, using the `b4f9ee0a9d4abbfc6986601d9b1a4f8f8e74c77e` SHA. +使用“peter-evans/create-issue-from-file”操作创建新的 {% data variables.product.prodname_dotcom %} 议题。 此示例使用 'b4f9ee0a9d4abbfc6986601d9b1a4f8f8e74c77e' SHA 固定到操作的特定版本。 @@ -430,9 +430,9 @@ Uses the `peter-evans/create-issue-from-file` action to create a new {% data var -Uses [`gh issue list`](https://cli.github.com/manual/gh_issue_list) to locate the previously created issue from earlier runs. This is [aliased](https://cli.github.com/manual/gh_alias_set) to `gh list-reports` for simpler processing in later steps. To get the issue URL, the `jq` expression processes the resulting JSON output. +使用 [`gh issue list`](https://cli.github.com/manual/gh_issue_list) 从早期运行中查找以前创建的议题。 这将[aliased](https://cli.github.com/manual/gh_alias_set) 为“gh list-reports”，以便在后续步骤中简化处理。 若要获取议题 URL，“jq”表达式将处理生成的 JSON 输出。 -[`gh issue comment`](https://cli.github.com/manual/gh_issue_comment) is then used to add a comment to the new issue that links to the previous one. +[`gh issue comment`](https://cli.github.com/manual/gh_issue_comment) 然后用于向链接到上一个议题的新议题添加注释。 @@ -450,7 +450,7 @@ Uses [`gh issue list`](https://cli.github.com/manual/gh_issue_list) to locate th -If an issue from a previous run is open and assigned to someone, then use [`gh issue comment`](https://cli.github.com/manual/gh_issue_comment) to add a comment with a link to the new issue. +如果上一次运行中的议题已打开并分配给某人，请使用 [`gh issue comment`](https://cli.github.com/manual/gh_issue_comment) 添加带有指向新议题的链接的注释。 @@ -471,11 +471,11 @@ If an issue from a previous run is open and assigned to someone, then use [`gh i -If an issue from a previous run is open and is not assigned to anyone, then: +如果上一次运行中的议题已打开且未分配给任何人，则： -* Use [`gh issue comment`](https://cli.github.com/manual/gh_issue_comment) to add a comment with a link to the new issue. -* Use [`gh issue close`](https://cli.github.com/manual/gh_issue_close) to close the old issue. -* Use [`gh issue edit`](https://cli.github.com/manual/gh_issue_edit) to edit the old issue to remove it from a specific {% data variables.product.prodname_dotcom %} project board. +* 使用 [`gh issue comment`](https://cli.github.com/manual/gh_issue_comment) 添加带有新议题链接的评论。 +* 使用 [`gh issue close`](https://cli.github.com/manual/gh_issue_close) 关闭旧议题。 +* 使用 [`gh issue edit`](https://cli.github.com/manual/gh_issue_edit) 编辑旧议题，以将其从特定 {% data variables.product.prodname_dotcom %} 项目板中删除。 diff --git a/translations/zh-CN/content/actions/learn-github-actions/contexts.md b/translations/zh-CN/content/actions/learn-github-actions/contexts.md index d0098661c6..0d0354ed69 100644 --- a/translations/zh-CN/content/actions/learn-github-actions/contexts.md +++ b/translations/zh-CN/content/actions/learn-github-actions/contexts.md @@ -45,7 +45,7 @@ miniTocMaxHeadingLevel: 3 | `matrix` | `对象` | 包含在工作流程中定义的应用于当前作业的矩阵属性。 更多信息请参阅 [`matrix` 上下文](#matrix-context)。 | | `needs` | `对象` | 包含定义为当前作业依赖项的所有作业的输出。 更多信息请参阅 [`needs` 上下文](#needs-context)。 | {%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-4757 %} -| `inputs` | `object` | Contains the inputs of a reusable {% ifversion actions-unified-inputs %}or manually triggered {% endif %}workflow. 更多信息请参阅 [`inputs` 上下文](#inputs-context)。 |{% endif %} +| `inputs` | `object` | 包含可重用 {% ifversion actions-unified-inputs %}或手动触发 {% endif %}工作流程的输入。 更多信息请参阅 [`inputs` 上下文](#inputs-context)。 |{% endif %} 作为表达式的一部分，您可以使用以下两种语法之一访问上下文信息。 @@ -699,20 +699,20 @@ jobs: {% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-4757 %} ## `inputs` 上下文 -The `inputs` context contains input properties passed to a reusable workflow{% ifversion actions-unified-inputs %} or to a manually triggered workflow{% endif %}. {% ifversion actions-unified-inputs %}For reusable workflows, the{% else %}The{% endif %} input names and types are defined in the [`workflow_call` event configuration](/actions/learn-github-actions/events-that-trigger-workflows#workflow-reuse-events) of a reusable workflow, and the input values are passed from [`jobs..with`](/actions/learn-github-actions/workflow-syntax-for-github-actions#jobsjob_idwith) in an external workflow that calls the reusable workflow. {% ifversion actions-unified-inputs %}For manually triggered workflows, the inputs are defined in the [`workflow_dispatch` event configuration](/actions/learn-github-actions/events-that-trigger-workflows#workflow_dispatch) of a workflow.{% endif %} +`inputs` 上下文包含传递给可重用工作流程{% ifversion actions-unified-inputs %} 或手动触发的工作流{% endif %} 的输入属性。 {% ifversion actions-unified-inputs %}对于可重用的工作流程，{% else %}{% endif %}输入名称和类型在可重用工作流程的 [`workflow_call` 事件配置](/actions/learn-github-actions/events-that-trigger-workflows#workflow-reuse-events)中定义，输入值从调用可重用工作流程的外部工作流中的 [`jobs..with`](/actions/learn-github-actions/workflow-syntax-for-github-actions#jobsjob_idwith) 传递。 {% ifversion actions-unified-inputs %}对于手动触发的工作流，输入在工作流程的 [`workflow_dispatch` 事件配置](/actions/learn-github-actions/events-that-trigger-workflows#workflow_dispatch)中定义。{% endif %} -There are no standard properties in the `inputs` context, only those which are defined in the workflow file. +`inputs` 上下文中没有标准属性，只有工作流程文件中定义的属性。 {% data reusables.actions.reusable-workflows-ghes-beta %} -| 属性名称 | 类型 | 描述 | -| --------------------- | ------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `inputs` | `对象` | This context is only available in a [reusable workflow](/actions/learn-github-actions/reusing-workflows){% ifversion actions-unified-inputs %} or in a workflow triggered by the [`workflow_dispatch` event](/actions/learn-github-actions/events-that-trigger-workflows#workflow_dispatch){% endif %}. 您可以从工作流程中的任何作业或步骤访问此上下文。 此对象包含下面列出的属性。 | -| `inputs.` | `string` 或 `number` 或 `boolean` | 从外部工作流传递的每个输入值。 | +| 属性名称 | 类型 | 描述 | +| --------------------- | ------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `inputs` | `对象` | 此上下文仅在 [reusable workflow](/actions/learn-github-actions/reusing-workflows){% ifversion actions-unified-inputs %} 或由 [`workflow_dispatch` 事件](/actions/learn-github-actions/events-that-trigger-workflows#workflow_dispatch){% endif %} 触发的工作流程中可用。 您可以从工作流程中的任何作业或步骤访问此上下文。 此对象包含下面列出的属性。 | +| `inputs.` | `string` 或 `number` 或 `boolean` | 从外部工作流传递的每个输入值。 | ### `inputs` 上下文的示例内容 -The following example contents of the `inputs` context is from a workflow that has defined the `build_id`, `deploy_target`, and `perform_deploy` inputs. +以下 `inputs` 上下文的示例内容来自定义了 `build_id`、`deploy_target` 和 `perform_deploy` 输入的工作流程。 ```yaml { @@ -722,9 +722,9 @@ The following example contents of the `inputs` context is from a workflow that h } ``` -### Example usage of the `inputs` context in a reusable workflow +### 可重用工作流程中 `inputs` 上下文的示例用法 -This example reusable workflow uses the `inputs` context to get the values of the `build_id`, `deploy_target`, and `perform_deploy` inputs that were passed to the reusable workflow from the caller workflow. +此示例可重用工作流程使用 `inputs` 上下文来获取从调用方工作流程传递到可重用工作流程的 `build_id`、`deploy_target` 和 `perform_deploy` 输入的值。 {% raw %} ```yaml{:copy} @@ -753,9 +753,9 @@ jobs: {% endraw %} {% ifversion actions-unified-inputs %} -### Example usage of the `inputs` context in a manually triggered workflow +### 手动触发的工作流程中 `inputs` 上下文的示例用法 -This example workflow triggered by a `workflow_dispatch` event uses the `inputs` context to get the values of the `build_id`, `deploy_target`, and `perform_deploy` inputs that were passed to the workflow. +此示例工作流程由 `workflow_dispatch` 事件触发，它使用 `inputs` 上下文来获取传递给工作流程的 `build_id`、`deploy_target` 和 `perform_deploy` 输入的值。 {% raw %} ```yaml{:copy} diff --git a/translations/zh-CN/content/actions/managing-workflow-runs/re-running-workflows-and-jobs.md b/translations/zh-CN/content/actions/managing-workflow-runs/re-running-workflows-and-jobs.md index 6f3b451358..053517bec8 100644 --- a/translations/zh-CN/content/actions/managing-workflow-runs/re-running-workflows-and-jobs.md +++ b/translations/zh-CN/content/actions/managing-workflow-runs/re-running-workflows-and-jobs.md @@ -1,6 +1,6 @@ --- -title: 重新运行工作流程和作业 -intro: '您可以工作流程运行初始运行后最长 30 天内重新运行工作流程运行{% ifversion re-run-jobs %}、工作流程运行中所有失败的作业或工作流程运行中的特定作业{% endif %}。' +title: Re-running workflows and jobs +intro: You can re-run a workflow run{% ifversion re-run-jobs %}, all failed jobs in a workflow run, or specific jobs in a workflow run{% endif %} up to 30 days after its initial run. permissions: People with write permissions to a repository can re-run workflows in the repository. miniTocMaxHeadingLevel: 3 redirect_from: @@ -15,11 +15,11 @@ versions: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -## 关于重新运行工作流程和作业 +## About re-running workflows and jobs -重新运行工作流程{% ifversion re-run-jobs %} 或工作流程中的作业{% endif %} 会使用触发工作流程运行的原始事件的 `GITHUB_SHA`（提交 SHA）和 `GITHUB_REF` (Git ref)。 You can re-run a workflow{% ifversion re-run-jobs %} or jobs in a workflow{% endif %} for up to 30 days after the initial run.{% ifversion re-run-jobs %} You cannot re-run jobs in a workflow once its logs have passed their retention limits. For more information, see "[Usage limits, billing, and administration](/actions/learn-github-actions/usage-limits-billing-and-administration#artifact-and-log-retention-policy)."{% endif %}{% ifversion debug-reruns %} When you re-run a workflow or jobs in a workflow, you can enable debug logging for the re-run. 这将为重新运行启用运行程序诊断日志记录和步骤调试日志记录。 有关调试日志记录的更多信息，请参阅“[启用调试日志记录](/actions/monitoring-and-troubleshooting-workflows/enabling-debug-logging)”。{% endif %} +Re-running a workflow{% ifversion re-run-jobs %} or jobs in a workflow{% endif %} uses the same `GITHUB_SHA` (commit SHA) and `GITHUB_REF` (Git ref) of the original event that triggered the workflow run. You can re-run a workflow{% ifversion re-run-jobs %} or jobs in a workflow{% endif %} for up to 30 days after the initial run.{% ifversion re-run-jobs %} You cannot re-run jobs in a workflow once its logs have passed their retention limits. For more information, see "[Usage limits, billing, and administration](/actions/learn-github-actions/usage-limits-billing-and-administration#artifact-and-log-retention-policy)."{% endif %}{% ifversion debug-reruns %} When you re-run a workflow or jobs in a workflow, you can enable debug logging for the re-run. This will enable runner diagnostic logging and step debug logging for the re-run. For more information about debug logging, see "[Enabling debug logging](/actions/monitoring-and-troubleshooting-workflows/enabling-debug-logging)."{% endif %} -## 重新运行工作流程中的所有作业 +## Re-running all the jobs in a workflow {% webui %} @@ -28,12 +28,14 @@ versions: {% data reusables.repositories.navigate-to-workflow %} {% data reusables.repositories.view-run %} {% ifversion fpt or ghes > 3.4 or ghae-issue-4721 or ghec %} -1. 在工作流程的右上角，使用 **Re-run jobs（重新运行作业）**下拉菜单，并选择 **Re-run all jobs（重新运行所有作业）**。 +1. In the upper-right corner of the workflow, use the **Re-run jobs** drop-down menu, and select **Re-run all jobs**. - 如果没有作业失败，您将不会看到 **重新运行作业（Re-run jobs）**下拉菜单。 相反，请单击 **Re-run all jobs（重新运行所有作业）**。 ![重新运行检查下拉菜单](/assets/images/help/repository/rerun-checks-drop-down.png) + If no jobs failed, you will not see the **Re-run jobs** drop-down menu. Instead, click **Re-run all jobs**. + ![Rerun checks drop-down menu](/assets/images/help/repository/rerun-checks-drop-down.png) {% endif %} {% ifversion ghes < 3.5 or ghae %} -1. 在工作流程的右上角，使用 **Re-run jobs（重新运行作业）**下拉菜单，并选择 **Re-run all jobs（重新运行所有作业）**。 ![重新运行检查下拉菜单](/assets/images/help/repository/rerun-checks-drop-down-updated.png) +1. In the upper-right corner of the workflow, use the **Re-run jobs** drop-down menu, and select **Re-run all jobs**. + ![Re-run checks drop-down menu](/assets/images/help/repository/rerun-checks-drop-down-updated.png) {% endif %} {% data reusables.actions.enable-debug-logging %} @@ -43,7 +45,7 @@ versions: {% data reusables.cli.cli-learn-more %} -要重新运行失败的工作流程运行，请使用 `run rerun` 子命令。 将 `run-id` 替换为您想要重新运行的已失败运行的 ID。 如果您没有指定 `run-id`，{% data variables.product.prodname_cli %} 将返回一个交互式菜单，供您选择最近失败的运行。 +To re-run a failed workflow run, use the `run rerun` subcommand. Replace `run-id` with the ID of the failed run that you want to re-run. If you don't specify a `run-id`, {% data variables.product.prodname_cli %} returns an interactive menu for you to choose a recent failed run. ```shell gh run rerun run-id @@ -58,7 +60,7 @@ gh run rerun run-id --debug {% endif %} -要查看工作流程运行的进度，请使用 `run watch` 子命令，并从交互式列表中选择运行。 +To view the progress of the workflow run, use the `run watch` subcommand and select the run from the interactive list. ```shell gh run watch @@ -67,9 +69,9 @@ gh run watch {% endcli %} {% ifversion re-run-jobs %} -## 重新运行工作流程中失败的作业 +## Re-running failed jobs in a workflow -如果工作流程运行中的任何作业失败，您可以仅重新运行失败的作业。 在重新运行工作流程中失败的作业时，将为所有失败的作业及其依赖项启动新的工作流程运行。 上一个工作流程运行中任何成功作业的任何输出都将用于重新运行。 在初始运行中创建的任何构件都将在重新运行中可用。 在上一次运行中通过的任何环境保护规则都将自动在重新运行中通过。 +If any jobs in a workflow run failed, you can re-run just the jobs that failed. When you re-run failed jobs in a workflow, a new workflow run will start for all failed jobs and their dependents. Any outputs for any successful jobs in the previous workflow run will be used for the re-run. Any artifacts that were created in the initial run will be available in the re-run. Any environment protection rules that passed in the previous run will automatically pass in the re-run. {% webui %} @@ -77,14 +79,15 @@ gh run watch {% data reusables.repositories.actions-tab %} {% data reusables.repositories.navigate-to-workflow %} {% data reusables.repositories.view-run %} -1. 在工作流程的右上角，使用 **Re-run jobs（重新运行作业）**下拉菜单，并选择 **Re-run failed jobs（重新运行失败的作业）**。 ![重新运行失败的作业下拉菜单](/assets/images/help/repository/rerun-failed-jobs-drop-down.png) +1. In the upper-right corner of the workflow, use the **Re-run jobs** drop-down menu, and select **Re-run failed jobs**. + ![Re-run failed jobs drop-down menu](/assets/images/help/repository/rerun-failed-jobs-drop-down.png) {% data reusables.actions.enable-debug-logging %} {% endwebui %} {% cli %} -要重新运行工作流程运行中失败的作业，请使用 `run rerun` 子命令与 `--failed` 标志。 将 `run-id` 替换为要为其重新运行失败作业的运行 ID。 如果您没有指定 `run-id`，{% data variables.product.prodname_cli %} 将返回一个交互式菜单，供您选择最近失败的运行。 +To re-run failed jobs in a workflow run, use the `run rerun` subcommand with the `--failed` flag. Replace `run-id` with the ID of the run for which you want to re-run failed jobs. If you don't specify a `run-id`, {% data variables.product.prodname_cli %} returns an interactive menu for you to choose a recent failed run. ```shell gh run rerun run-id --failed @@ -100,9 +103,9 @@ gh run rerun run-id --failed --debug {% endif %} {% endcli %} -## 重新运行工作流程中的特定作业 +## Re-running a specific job in a workflow -重新运行工作流程中的特定作业时，将为该作业和任何依赖项启动新的工作流程运行。 上一个工作流程运行中任何其他作业的任何输出都将用于重新运行。 在初始运行中创建的任何构件都将在重新运行中可用。 在上一次运行中通过的任何环境保护规则都将自动在重新运行中通过。 +When you re-run a specific job in a workflow, a new workflow run will start for the job and any dependents. Any outputs for any other jobs in the previous workflow run will be used for the re-run. Any artifacts that were created in the initial run will be available in the re-run. Any environment protection rules that passed in the previous run will automatically pass in the re-run. {% webui %} @@ -110,16 +113,18 @@ gh run rerun run-id --failed --debug {% data reusables.repositories.actions-tab %} {% data reusables.repositories.navigate-to-workflow %} {% data reusables.repositories.view-run %} -1. 在要重新运行的作业旁边，单击 {% octicon "sync" aria-label="The re-run icon" %}。 ![重新运行选定的作业](/assets/images/help/repository/re-run-selected-job.png) +1. Next to the job that you want to re-run, click {% octicon "sync" aria-label="The re-run icon" %}. + ![Re-run selected job](/assets/images/help/repository/re-run-selected-job.png) - 或者，单击作业以查看日志。 在日志中，单击 {% octicon "sync" aria-label="The re-run icon" %}。 ![重新运行选定的作业](/assets/images/help/repository/re-run-single-job-from-log.png) + Alternatively, click on a job to view the log. In the log, click {% octicon "sync" aria-label="The re-run icon" %}. + ![Re-run selected job](/assets/images/help/repository/re-run-single-job-from-log.png) {% data reusables.actions.enable-debug-logging %} {% endwebui %} {% cli %} -要重新运行工作流程运行中的特定作业，请使用 `run rerun` 子命令与 `--job` 标志。 将 `job-id` 替换为您想要重新运行的作业的 ID。 +To re-run a specific job in a workflow run, use the `run rerun` subcommand with the `--job` flag. Replace `job-id` with the ID of the job that you want to re-run. ```shell gh run rerun --job job-id @@ -139,26 +144,28 @@ gh run rerun --job job-id --debug {% ifversion partial-reruns-with-reusable %} -## 使用可重用工作流程重新运行工作流程和作业 +## Re-running workflows and jobs with reusable workflows {% data reusables.actions.partial-reruns-with-reusable %} {% endif %} {% ifversion fpt or ghes > 3.4 or ghae-issue-4721 or ghec %} -## 查看以前的工作流程运行 +## Reviewing previous workflow runs -您可以查看以前尝试运行工作流程的结果。 您还可以使用 API 查看以前的工作流程运行。 更多信息请参阅“[获取工作流程运行](/rest/reference/actions#get-a-workflow-run)”。 +You can view the results from your previous attempts at running a workflow. You can also view previous workflow runs using the API. For more information, see ["Get a workflow run"](/rest/reference/actions#get-a-workflow-run). {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.actions-tab %} {% data reusables.repositories.navigate-to-workflow %} {% data reusables.repositories.view-run %} {%- ifversion re-run-jobs %} -1. 任何以前的运行尝试都显示在 **Latest（最新）**下拉菜单中。 ![以前的运行尝试](/assets/images/help/repository/previous-run-attempts.png) +1. Any previous run attempts are shown in the **Latest** drop-down menu. + ![Previous run attempts](/assets/images/help/repository/previous-run-attempts.png) {%- else %} -1. 任何以前的运行尝试都显示在左窗格中。 ![重新运行工作流程](/assets/images/help/settings/actions-review-workflow-rerun.png) +1. Any previous run attempts are shown in the left pane. + ![Rerun workflow](/assets/images/help/settings/actions-review-workflow-rerun.png) {%- endif %} -1. 单击某个条目以查看其结果。 +1. Click an entry to view its results. {% endif %} diff --git a/translations/zh-CN/content/actions/using-workflows/events-that-trigger-workflows.md b/translations/zh-CN/content/actions/using-workflows/events-that-trigger-workflows.md index 700cd5fe7d..7998130774 100644 --- a/translations/zh-CN/content/actions/using-workflows/events-that-trigger-workflows.md +++ b/translations/zh-CN/content/actions/using-workflows/events-that-trigger-workflows.md @@ -1250,12 +1250,12 @@ on: workflow_dispatch #### 提供输入 -您可以直接在工作流程中配置事件的自定义输入属性、默认输入值和必要输入。 触发事件时，可以提供 `ref` 和任何 `inputs`。 When the workflow runs, you can access the input values in the {% ifversion actions-unified-inputs %}`inputs`{% else %}`github.event.inputs`{% endif %} context. 更多信息请参阅“[上下文](/actions/learn-github-actions/contexts)”。 +您可以直接在工作流程中配置事件的自定义输入属性、默认输入值和必要输入。 触发事件时，可以提供 `ref` 和任何 `inputs`。 在工作流程运行时，您可以访问 {% ifversion actions-unified-inputs %}`inputs`{% else %}`github.event.inputs`{% endif %} 上下文中的输入值。 更多信息请参阅“[上下文](/actions/learn-github-actions/contexts)”。 {% data reusables.actions.inputs-vs-github-event-inputs %} {% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5511 %} -此示例定义了称为 `logLevel`、`tags` 和 `environment` 的输入。 在运行工作流程时，可以将这些输入的值传递给工作流程。 This workflow then prints the values to the log, using the {% ifversion actions-unified-inputs %}`inputs.logLevel`, `inputs.tags`, and `inputs.environment`{% else %}`github.event.inputs.logLevel`, `github.event.inputs.tags`, and `github.event.inputs.environment`{% endif %} context properties. +此示例定义了称为 `logLevel`、`tags` 和 `environment` 的输入。 在运行工作流程时，可以将这些输入的值传递给工作流程。 然后，此工作流程使用 {% ifversion actions-unified-inputs %}`inputs.logLevel`、`inputs.tags` 和 `inputs.environment`{% else %}`github.event.inputs.logLevel`、`github.event.inputs.tags`）和 `github.event.inputs.environment`{% endif %} 上下文属性，将值打印到日志中。 ```yaml on: @@ -1306,7 +1306,7 @@ gh workflow run run-tests.yml -f logLevel=warning -f tags=false -f environment=s 更多信息请参阅“[手动运行工作流程](/actions/managing-workflow-runs/manually-running-a-workflow)”中的 {% data variables.product.prodname_cli %} 信息。 {% else %} -This example defines the `name` and `home` inputs and prints them using the {% ifversion actions-unified-inputs %}`inputs.name` and `inputs.home`{% else %}`github.event.inputs.name` and `github.event.inputs.home`{% endif %} contexts. 如果未提供 `home` ，则打印默认值“The Octoverse”。 +此示例定义 `name` 和 `home` 输入，并使用 {% ifversion actions-unified-inputs %}`inputs.name` 和 `inputs.home`{% else %}`github.event.inputs.name` 和 `github.event.inputs.home`{% endif %} 上下文打印它们。 如果未提供 `home` ，则打印默认值“The Octoverse”。 ```yaml name: Manually triggered workflow diff --git a/translations/zh-CN/content/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file.md b/translations/zh-CN/content/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file.md index b93f03eb21..6ef2860749 100644 --- a/translations/zh-CN/content/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file.md +++ b/translations/zh-CN/content/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file.md @@ -280,7 +280,7 @@ updates: prefix-development: "pip dev" include: "scope" ``` -If you use the same configuration as in the example above, bumping the `requests` library in the `pip` development dependency group will generate a commit message of: +如果使用与上述示例中相同的配置，则在 `pip` 开发依赖项组中刷入 `requests` 库将生成以下提交消息： `pip dev: bump requests from 1.0.0 to 1.0.1` 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 f62bf434cc..1782bc23cd 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 @@ -34,7 +34,10 @@ topics: {% note %} -**注：**您可以为开源项目创建公共仓库。 创建公共仓库时，请确保包含[许可文件](https://choosealicense.com/)以确定您希望与其他人共享项目。 {% data reusables.open-source.open-source-guide-repositories %} {% data reusables.open-source.open-source-learning %} +**注意：** +- You can create public repositories for an open source project. 创建公共仓库时，请确保包含[许可文件](https://choosealicense.com/)以确定您希望与其他人共享项目。 {% data reusables.open-source.open-source-guide-repositories %} +- {% data reusables.open-source.open-source-learning %} +- You can also add community health files to your repositories, to set guidelines on how to contribute, keep your repositories safe, and much more. 更多信息请参阅“[创建默认社区健康文件](/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file)”。 {% endnote %} diff --git a/translations/zh-CN/content/rest/guides/index.md b/translations/zh-CN/content/rest/guides/index.md index 435db86619..502b9a1ba1 100644 --- a/translations/zh-CN/content/rest/guides/index.md +++ b/translations/zh-CN/content/rest/guides/index.md @@ -25,4 +25,4 @@ children: - /getting-started-with-the-checks-api --- -文档的这一部分旨在让您使用实际 {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API 应用程序开始运行。 We'll go over everything you need to know, from authentication to results manipulation to integrating results with other apps. Every tutorial will include a project, and each project will be saved and documented in our public [platform-samples](https://github.com/github/platform-samples) repository. ![The Octocat](/assets/images/electrocat.png) +文档的这一部分旨在让您使用实际 {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API 应用程序开始运行。 我们将介绍您需要了解的所有内容，从身份验证到结果操作，再到将结果与其他应用程序集成。 每个教程都将包含一个项目，每个项目都将保存并记录在我们的公共 [platform-samples](https://github.com/github/platform-samples) 存储库中。 ![The Octocat](/assets/images/electrocat.png) diff --git a/translations/zh-CN/content/site-policy/privacy-policies/github-privacy-statement.md b/translations/zh-CN/content/site-policy/privacy-policies/github-privacy-statement.md index 76f19a462c..5c75ed6753 100644 --- a/translations/zh-CN/content/site-policy/privacy-policies/github-privacy-statement.md +++ b/translations/zh-CN/content/site-policy/privacy-policies/github-privacy-statement.md @@ -177,7 +177,7 @@ GitHub 可能会向执法部门或其他政府机构披露我们收集的有关 如果 GitHub 处理除您的个人资料信息以外的个人数据，例如 GitHub 从[第三方](/github/site-policy/github-privacy-statement#information-we-collect-from-third-parties)收到的有关您的信息，则根据适用法律，您可以联系 [GitHub 支持](https://support.github.com/contact) 或 [GitHub 高级支持](https://enterprise.githubsupport.com/hc/en-us)访问、更新、更改、删除、反对或限制处理您的个人数据。 -您可以通过[个人资料设置](https://github.com/settings/profile)来调整帐户上的设置，包括将您的个人数据显示在私人或公共存储库中，或与社区功能（例如 GitHub Feed、GitHub Globe、GitHub Explore、GitHub 讨论排行榜）相关的个人数据。 +You can adjust the settings on your Account regarding the display of your Personal Data in private or public repositories or Personal Data processed in connection with Community Features (such as GitHub Feed, GitHub Sponsors, and GitHub Explore) through [profile settings](https://github.com/settings/profile). 此外，如果您无法通过上述方式访问我们拥有的某些个人数据，您可以按照本隐私声明底部所述与我们联系以请求访问。 diff --git a/translations/zh-CN/data/features/README.md b/translations/zh-CN/data/features/README.md index f8ec528a2d..71856170a4 100644 --- a/translations/zh-CN/data/features/README.md +++ b/translations/zh-CN/data/features/README.md @@ -45,7 +45,7 @@ versions: ## 架构执行 -验证功能版本管理的架构位于 [`tests/helpers/schemas/feature-versions-schema.js`](/tests/helpers/schemas/feature-versions-schema.js) 中，通过 [`tests/linting/lint-files.js`](/tests/linting/lint-files.js) 执行。 +验证功能版本管理的架构位于 [`tests/helpers/schemas/feature-versions-schema.js`](/tests/helpers/schemas/feature-versions-schema.js) 中，通过 [`tests/linting/lint-versioning.js`](/tests/linting/lint-versioning.js) 执行。 ## 删除功能标签的脚本 diff --git a/translations/zh-CN/data/reusables/secret-scanning/partner-secret-list-private-repo.md b/translations/zh-CN/data/reusables/secret-scanning/partner-secret-list-private-repo.md index c1875346d3..6a7e9225e0 100644 --- a/translations/zh-CN/data/reusables/secret-scanning/partner-secret-list-private-repo.md +++ b/translations/zh-CN/data/reusables/secret-scanning/partner-secret-list-private-repo.md @@ -147,6 +147,8 @@ Plivo | Plivo Auth ID | plivo_auth_id{% endif %} Plivo | Plivo 验证令牌 | plivo_auth_token{% endif %} Postman | Postman API 密钥 | postman_api_key Proctorio | Proctorio 消费者密钥 | proctorio_consumer_key Proctorio | Proctorio 链接密钥 | proctorio_linkage_key Proctorio | Proctorio 注册密钥 | proctorio_registration_key Proctorio | Proctorio 密钥 | proctorio_secret_key Pulumi | Pulumi 访问令牌 | pulumi_access_token {%- ifversion fpt or ghec or ghes > 3.1 or ghae %} PyPI | PyPI API Token | pypi_api_token{% endif %} +{%- ifversion fpt or ghec or ghes > 3.5 or ghae-issue-7375 %} +redirect.pizza | redirect.pizza API Token | redirect_pizza_api_token{% endif %} {%- ifversion fpt or ghec or ghes > 3.1 or ghae %} RubyGems | RubyGems API 密钥 | rubygems_api_key{% endif %} Samsara | Samsara API 令牌 | samsara_api_token Samsara | Samsara OAuth 访问令牌 | samsara_oauth_access_token {%- ifversion fpt or ghec or ghes > 3.4 or ghae-issue-6944 %} diff --git a/translations/zh-CN/data/reusables/secret-scanning/partner-secret-list-public-repo.md b/translations/zh-CN/data/reusables/secret-scanning/partner-secret-list-public-repo.md index 6be65bf5ad..bcce07b24f 100644 --- a/translations/zh-CN/data/reusables/secret-scanning/partner-secret-list-public-repo.md +++ b/translations/zh-CN/data/reusables/secret-scanning/partner-secret-list-public-repo.md @@ -77,6 +77,7 @@ | Proctorio | Proctorio 密钥 | | Pulumi | Pulumi 访问令牌 | | PyPI | PyPI API 令牌 | +| redirect.pizza | redirect.pizza API Token | | RubyGems | RubyGems API 密钥 | | Samsara | Samsara API 令牌 | | Samsara | Samsara OAuth 访问令牌 | diff --git a/translations/zh-CN/data/reusables/secret-scanning/secret-list-private-push-protection.md b/translations/zh-CN/data/reusables/secret-scanning/secret-list-private-push-protection.md index 85251ca1cb..4ded6dec06 100644 --- a/translations/zh-CN/data/reusables/secret-scanning/secret-list-private-push-protection.md +++ b/translations/zh-CN/data/reusables/secret-scanning/secret-list-private-push-protection.md @@ -60,16 +60,5 @@ | PlanetScale | PlanetScale 服务令牌 | planetscale_service_token | | Postman | Postman API 密钥 | postman_api_key | | Proctorio | Proctorio 密钥 | proctorio_secret_key | -| Samsara | Samsara API 令牌 | samsara_api_token | -| Samsara | Samsara OAuth 访问令牌 | samsara_oauth_access_token | -| SendGrid | SendGrid API Key | sendgrid_api_key | -| Sendinblue | SendinBlue API 密钥 | sendinblue_api_key | -| Sendinblue | SendinBlue SMTP 密钥 | sendinblue_smtp_key | -| Shippo | Shippo Live API Token | shippo_live_api_token | -| Shopify | Shopify App 共享密钥 | shopify_app_shared_secret | -| Shopify | Shopify 访问令牌 | shopify_access_token | -| Slack | Slack API 令牌 | slack_api_token | -| Stripe | Stripe Live API 密钥 | stripe_api_key | -| Tencent Cloud | 腾讯云密钥 ID | tencent_cloud_secret_id | -| Typeform | Typeform 个人访问令牌 | typeform_personal_access_token | -| WorkOS | WorkOS Production API Key | workos_production_api_key | +{%- ifversion fpt or ghec or ghes > 3.5 or ghae-issue-7375 %} +redirect.pizza | redirect.pizza API Token | redirect_pizza_api_token{% endif %} Samsara | Samsara API Token | samsara_api_token Samsara | Samsara OAuth Access Token | samsara_oauth_access_token SendGrid | SendGrid API Key | sendgrid_api_key Sendinblue | Sendinblue API Key | sendinblue_api_key Sendinblue | Sendinblue SMTP Key | sendinblue_smtp_key Shippo | Shippo Live API Token | shippo_live_api_token Shopify | Shopify App Shared Secret | shopify_app_shared_secret Shopify | Shopify Access Token | shopify_access_token Slack | Slack API Token | slack_api_token Stripe | Stripe Live API Secret Key | stripe_api_key Tencent Cloud | Tencent Cloud Secret ID | tencent_cloud_secret_id Typeform | Typeform Personal Access Token | typeform_personal_access_token WorkOS | WorkOS Production API Key | workos_production_api_key