[Localization] Translation batch 1637173972 (#22931)

* New Crowdin translations by Github Action

* Reset broken translated files to English

* Ran script/i18n/homogenize-frontmatter.js

* Ran script/i18n/fix-translation-errors.js

* Reverted translated files with rendering errors

* build: update app.json to test all languages in CI

* build: revert app.json back to original config

Co-authored-by: Crowdin Bot <support+bot@crowdin.com>

Author: francisfuzz

translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-accessibility-settings.md

@@ -0,0 +1,22 @@
+---
+title: Managing accessibility settings
+intro: 'You can disable character key shortcuts on {% data variables.product.prodname_dotcom %} in your accessibility settings.'
+versions:
+  fpt: '*'
+  ghes: '>=3.4'
+  feature: keyboard-shortcut-accessibility-setting
+---
+
+## About accessibility settings
+
+{% data variables.product.product_name %} includes a variety of keyboard shortcuts so that you can perform actions across the site without using your mouse to navigate. While shortcuts are useful to save time, they can sometimes make {% data variables.product.prodname_dotcom %} harder to use and less accessible.
+
+All keyboard shortcuts are enabled by default on {% data variables.product.product_name %}, but you can choose to disable character key shortcuts in your accessibility settings. This setting does not affect keyboard shortcuts provided by your web browser or {% data variables.product.prodname_dotcom %} shortcuts that use a modifier key such as `control` or `command`.
+
+## Managing character key shortcuts
+
+{% data reusables.user_settings.access_settings %}
+{% data reusables.user_settings.accessibility_settings %}
+1. Select or deselect the **Enable character key shortcuts** checkbox. 
+   ![Screenshot of the 'Enable character key shortcuts' checkbox](/assets/images/help/settings/disable-character-key-shortcuts.png)
+2. Click **Save**.

translations/es-ES/content/github/writing-on-github/working-with-advanced-formatting/organizing-information-with-collapsed-sections.md

@@ -0,0 +1,42 @@
+---
+title: Organizing information with collapsed sections
+intro: 'You can streamline your Markdown by creating a collapsed section with the `<details>` tag.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+shortTitle: Collapsed sections
+---
+## Creating a collapsed section
+
+You can temporarily obscure sections of your Markdown by creating a collapsed section that the reader can choose to expand. For example, when you want to include technical details in an issue comment that may not be relevant or interesting to every reader, you can put those details in a collapsed section.
+
+Any Markdown within the `<details>` block will be collapsed until the reader clicks {% octicon "triangle-right" aria-label="The right triange icon" %} to expand the details. Within the `<details>` block, use the `<summary>` tag to create a label to the right of {% octicon "triangle-right" aria-label="The right triange icon" %}.
+
+```markdown
+<details><summary>CLICK ME</summary>
+<p>
+
+#### We can hide anything, even code!
+
+    ```ruby
+      puts "Hello World"
+    ```
+
+</p>
+</details>
+```
+
+The Markdown will be collapsed by default.
+
+![Rendered collapsed](/assets/images/help/writing/collapsed-section-view.png)
+
+After a reader clicks {% octicon "triangle-right" aria-label="The right triange icon" %}, the details are expanded.
+
+![Rendered open](/assets/images/help/writing/open-collapsed-section.png)
+
+## Further reading
+
+- [{% data variables.product.prodname_dotcom %} Flavored Markdown Spec](https://github.github.com/gfm/)
+- "[Basic writing and formatting syntax](/articles/basic-writing-and-formatting-syntax)"

translations/es-ES/content/graphql/guides/migrating-graphql-global-node-ids.md

@@ -0,0 +1,69 @@
+---
+title: Migrating GraphQL global node IDs
+intro: 'Learn about the two global node ID formats and how to migrate from the legacy format to the new format.'
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - API
+shortTitle: Migrating global node IDs
+---
+
+## Background
+
+The {% data variables.product.product_name %} GraphQL API currently supports two types of global node ID formats. The legacy format will be deprecated and replaced with a new format.  This guide shows you how to migrate to the new format, if necessary. 
+
+By migrating to the new format, you ensure that the response times of your requests remain consistent and small. You also ensure that your application continues to work once the legacy IDs are fully deprecated.
+
+To learn more about why the legacy global node ID format will be deprecated, see "[New global ID format coming to GraphQL](https://github.blog/2021-02-10-new-global-id-format-coming-to-graphql)."
+
+## Determining if you need to take action
+
+You only need to follow the migration steps if you store references to GraphQL global node IDs.  These IDs correspond to the `id` field for any object in the schema.  If you don't store any global node IDs, then you can continue to interact with the API with no change.
+
+Additionally, if you currently decode the legacy IDs to extract type information (for example, if you use the first two characters of `PR_kwDOAHz1OX4uYAah` to determine if the object is a pull request), your service will break since the format of the IDs has changed.  You should migrate your service to treat these IDs as opaque strings.  These IDs will be unique, therefore you can rely on them directly as references.
+
+
+## Migrating to the new global IDs
+
+To facilitate migration to the new ID format, you can use the `X-Github-Next-Global-ID` header in your GraphQL API requests. The value of the `X-Github-Next-Global-ID` header can be `1` or `0`.  Setting the value to `1` will force the response payload to always use the new ID format for any object that you requested the `id` field for.  Setting the value to `0` will revert to default behavior, which is to show the legacy ID or new ID depending on the object creation date. 
+
+Here is an example request using cURL:
+
+```
+$ curl \
+  -H "Authorization: token $GITHUB_TOKEN" \
+  -H "X-Github-Next-Global-ID: 1" \
+  https://api.github.com/graphql \
+  -d '{ "query": "{ node(id: \"MDQ6VXNlcjM0MDczMDM=\") { id } }" }'
+```
+
+Even though the legacy ID `MDQ6VXNlcjM0MDczMDM=` was used in the query, the response will contain the new ID format:
+```
+{"data":{"node":{"id":"U_kgDOADP9xw"}}}
+```
+With the `X-Github-Next-Global-ID` header, you can find the new ID format for legacy IDs that you reference in your application. You can then update those references with the ID received in the response. You should update all references to legacy IDs and use the new ID format for any subsequent requests to the API. 
+To perform bulk operations, you can use aliases to submit multiple node queries in one API call. For more information, see "[the GraphQL docs](https://graphql.org/learn/queries/#aliases)."
+
+You can also get the new ID for a collection of items. For example, if you wanted to get the new ID for the last 10 repositories in your organization, you could use a query like this:
+```
+{
+  organization(login: "github") {
+    repositories(last: 10) {
+      edges {
+        cursor
+        node {
+          name
+          id
+        }
+      }
+    }
+  }
+}
+```
+
+Note that setting `X-Github-Next-Global-ID` to `1` will affect the return value of every `id` field in your query.  This means that even when you submit a non-`node` query, you will get back the new format ID if you requested the `id` field.
+
+## Sharing feedback
+
+If you have any concerns about the rollout of this change impacting your app, please [contact {% data variables.product.product_name %}](https://support.github.com/contact) and include information such as your app name so that we can better assist you.

translations/es-ES/data/features/keyboard-shortcut-accessibility-setting.yml

@@ -0,0 +1,8 @@
+---
+#Reference: #4999.
+#Documentation for the security manager org-level role
+versions:
+  fpt: '*'
+  ghes: '>=3.4'
+  ghae: 'ghae-issue-5430'
+  ghec: '*'

translations/es-ES/data/release-notes/enterprise-server/3-3/0-rc1.yml

@@ -17,7 +17,7 @@ sections:
     - heading: 'Cambios en la administración'
       notes:
         - '{% data variables.product.prodname_ghe_server %} 3.3 includes improvements to the maintenance of repositories, especially for repositories that contain many unreachable objects. Note that the first maintenance cycle after upgrading to {% data variables.product.prodname_ghe_server %} 3.3 may take longer than usual to complete.'
-        - '{% data variables.product.prodname_ghe_server %} 3.3 includes a repository cache for geographically-distributed teams and CI infrastructure. The repository cache keeps a read-only copy of your repositories available in additional geographies, which prevents clients from downloading duplicate Git content from your primary instance. For more information, see "[About repository caching](/admin/enterprise-management/caching-repositories/about-repository-caching)."'
+        - '{% data variables.product.prodname_ghe_server %} 3.3 includes the public beta of a repository cache for geographically-distributed teams and CI infrastructure. The repository cache keeps a read-only copy of your repositories available in additional geographies, which prevents clients from downloading duplicate Git content from your primary instance. For more information, see "[About repository caching](/admin/enterprise-management/caching-repositories/about-repository-caching)."'
         - '{% data variables.product.prodname_ghe_server %} 3.3 includes improvements to the user impersonation process. An impersonation session now requires a justification for the impersonation, actions are recorded in the audit log as being performed as an impersonated user, and the user who is impersonated will receive an email notification that they have been impersonated by an enterprise administrator. For more information, see "[Impersonating a user](/enterprise-server@3.3/admin/user-management/managing-users-in-your-enterprise/impersonating-a-user)."'
         - 'A new stream processing service has been added to facilitate the growing set of events that are published to the audit log, including events associated with Git and {% data variables.product.prodname_actions %} activity.'
     - heading: 'Cambios de Token'
@@ -77,6 +77,9 @@ sections:
         - 'When creating or updating a repository, you can now configure whether forking is allowed using the REST and GraphQL APIs. Previously, APIs for creating and updating repositories didn''t include the fields `allow_forking` (REST) or `forkingAllowed` (GraphQL). For more information, see "[Repositories](/rest/reference/repos)" in the REST API documentation and "[Repositories](/graphql/reference/objects#repository)" in the GraphQL API documentation.'
         - "A new GraphQL mutation [`createCommitOnBranch`](/graphql/reference/mutations#createcommitonbranch) makes it easier to add, update, and delete files in a branch of a repository. Compared to the REST API, you do not need to manually create blobs and trees before creating the commit. This allows you to add, update, or delete multiple files in a single API call.\n\nCommits authored using the new API are automatically GPG signed and are [marked as verified](/github/authenticating-to-github/managing-commit-signature-verification/about-commit-signature-verification) in the {% data variables.product.prodname_ghe_server %} UI. GitHub Apps can use the mutation to author commits directly or [on behalf of users](/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps#user-to-server-requests).\n"
         - 'When a new tag is created, the [push](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#push) webhook payload now always includes a `head_commit` object that contains the data of the commit that the new tag points to. As a result, the `head_commit` object will always contain the commit data of the payload''s `after` commit.'
+    - heading: 'Performance Changes'
+      notes:
+        - 'Page loads and jobs are now significantly faster for repositories with many Git refs.'
   known_issues:
     - 'On a freshly set up {% data variables.product.prodname_ghe_server %} instance without any users, an attacker could create the first admin user.'
     - 'Las reglas de cortafuegos personalizadas se eliminan durante el proceso de actualización.'

translations/es-ES/data/reusables/command-palette/change-scope.md

@@ -2,4 +2,4 @@
 
    - To narrow the scope within a user or organization account, highlight a repository then use <kbd>Tab</kbd> to add it to the scope.
    - To expand the scope, highlight and remove an item in the scope using the <kbd>Backspace</kbd> or <kbd>delete</kbd> key.
-   - To clear the scope and text box, click **Clear**.
+   - To clear the scope and text box, click **Clear** or use <kbd>Ctrl</kbd><kbd>Backspace</kbd> (Windows and Linux) or <kbd>⌘</kbd><kbd>Backspace</kbd> (Mac).

translations/es-ES/data/reusables/github-actions/supported-github-runners.md

@@ -9,7 +9,7 @@
 <tbody>
 <tr>
 <td>
-Windows Server 2022<sup>[beta]</sup>
+Windows Server 2022
 </td>
 <td>
 <code>windows-2022</code>

translations/es-ES/data/reusables/organizations/moderation-settings.md

@@ -0,0 +1 @@
+1. En la barra lateral izquierda, da clic en **Configuración de moderación**. ![Moderation settings in organization's settings](/assets/images/help/organizations/org-settings-moderation-settings.png)

translations/es-ES/data/reusables/user_settings/accessibility_settings.md

@@ -0,0 +1 @@
+1. In the navigation on the left hand side, click the **Accessibility** link. ![Screenshot of the user settings navigation. The Accessibility link is highlighted.](/assets/images/help/settings/accessibility-tab.png)

translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-accessibility-settings.md

@@ -0,0 +1,22 @@
+---
+title: Managing accessibility settings
+intro: 'You can disable character key shortcuts on {% data variables.product.prodname_dotcom %} in your accessibility settings.'
+versions:
+  fpt: '*'
+  ghes: '>=3.4'
+  feature: keyboard-shortcut-accessibility-setting
+---
+
+## About accessibility settings
+
+{% data variables.product.product_name %} includes a variety of keyboard shortcuts so that you can perform actions across the site without using your mouse to navigate. While shortcuts are useful to save time, they can sometimes make {% data variables.product.prodname_dotcom %} harder to use and less accessible.
+
+All keyboard shortcuts are enabled by default on {% data variables.product.product_name %}, but you can choose to disable character key shortcuts in your accessibility settings. This setting does not affect keyboard shortcuts provided by your web browser or {% data variables.product.prodname_dotcom %} shortcuts that use a modifier key such as `control` or `command`.
+
+## Managing character key shortcuts
+
+{% data reusables.user_settings.access_settings %}
+{% data reusables.user_settings.accessibility_settings %}
+1. Select or deselect the **Enable character key shortcuts** checkbox. 
+   ![Screenshot of the 'Enable character key shortcuts' checkbox](/assets/images/help/settings/disable-character-key-shortcuts.png)
+2. Click **Save**.