Gets the level of access that workflows outside of the repository have to actions and workflows in the repository.\nThis endpoint only applies to internal repositories. For more information, see \"Managing GitHub Actions settings for a repository.\"
\n
You must authenticate using an access token with the repo scope to use this endpoint. GitHub Apps must have the\nrepository administration permission to use this endpoint.
"
+ }
+ ],
+ "summary": "Set the level of access for workflows outside of the repository",
+ "requestBody": {
+ "required": true,
+ "content": {
+ "application/json": {
+ "schema": {
+ "type": "object",
+ "properties": {
+ "access_level": {
+ "type": "string",
+ "description": "
Required. Defines the level of access that workflows outside of the repository have to actions and workflows within the\nrepository. none means access is only possible from workflows in this repository. Can be one of none, organization, enterprise.
",
+ "enum": [
+ "none",
+ "organization",
+ "enterprise"
+ ],
+ "name": "access_level",
+ "in": "body",
+ "rawType": "string",
+ "rawDescription": "Defines the level of access that workflows outside of the repository have to actions and workflows within the\nrepository. `none` means access is only possible from workflows in this repository. Can be one of `none`, `organization`, `enterprise`.",
+ "childParamsGroups": []
+ }
+ },
+ "required": [
+ "access_level"
+ ]
+ },
+ "examples": {
+ "default": {
+ "value": {
+ "access_level": "organization"
+ }
+ }
+ }
+ }
+ }
+ },
+ "x-github": {
+ "enabledForGitHubApps": true,
+ "previews": [],
+ "category": "actions",
+ "subcategory": "permissions"
+ },
+ "slug": "set-the-level-of-access-for-workflows-outside-of-the-repository",
+ "category": "actions",
+ "subcategory": "permissions",
+ "notes": [],
+ "descriptionHTML": "
Sets the level of access that workflows outside of the repository have to actions and workflows in the repository.\nThis endpoint only applies to internal repositories. For more information, see \"Managing GitHub Actions settings for a repository.\"
\n
You must authenticate using an access token with the repo scope to use this endpoint. GitHub Apps must have the\nrepository administration permission to use this endpoint.
Required. Defines the level of access that workflows outside of the repository have to actions and workflows within the\nrepository. none means access is only possible from workflows in this repository. Can be one of none, organization, enterprise.
",
+ "enum": [
+ "none",
+ "organization",
+ "enterprise"
+ ],
+ "name": "access_level",
+ "in": "body",
+ "rawType": "string",
+ "rawDescription": "Defines the level of access that workflows outside of the repository have to actions and workflows within the\nrepository. `none` means access is only possible from workflows in this repository. Can be one of `none`, `organization`, `enterprise`.",
+ "childParamsGroups": []
+ }
+ ]
+ },
{
"verb": "get",
"requestPath": "/repos/{owner}/{repo}/actions/permissions/selected-actions",
diff --git a/lib/rest/static/dereferenced/api.github.com.deref.json b/lib/rest/static/dereferenced/api.github.com.deref.json
index 5c4d82114ef0..0aa6270b7020 100644
--- a/lib/rest/static/dereferenced/api.github.com.deref.json
+++ b/lib/rest/static/dereferenced/api.github.com.deref.json
@@ -135874,6 +135874,155 @@
}
}
},
+ "/repos/{owner}/{repo}/actions/permissions/access": {
+ "get": {
+ "summary": "Get the level of access for workflows outside of the repository",
+ "description": "Gets the level of access that workflows outside of the repository have to actions and workflows in the repository.\nThis endpoint only applies to internal repositories. For more information, see \"[Managing GitHub Actions settings for a repository](https://docs.github.com/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).\"\n\nYou must authenticate using an access token with the `repo` scope to use this endpoint. GitHub Apps must have the\nrepository `administration` permission to use this endpoint.",
+ "tags": [
+ "actions"
+ ],
+ "operationId": "actions/get-workflow-access-to-repository",
+ "externalDocs": {
+ "description": "API method documentation",
+ "url": "https://docs.github.com/rest/reference/actions#get-workflow-access-level-to-a-repository"
+ },
+ "parameters": [
+ {
+ "name": "owner",
+ "in": "path",
+ "required": true,
+ "schema": {
+ "type": "string"
+ }
+ },
+ {
+ "name": "repo",
+ "in": "path",
+ "required": true,
+ "schema": {
+ "type": "string"
+ }
+ }
+ ],
+ "responses": {
+ "200": {
+ "description": "Response",
+ "content": {
+ "application/json": {
+ "schema": {
+ "type": "object",
+ "properties": {
+ "access_level": {
+ "type": "string",
+ "description": "Defines the level of access that workflows outside of the repository have to actions and workflows within the\nrepository. `none` means access is only possible from workflows in this repository. Can be one of `none`, `organization`, `enterprise`.",
+ "enum": [
+ "none",
+ "organization",
+ "enterprise"
+ ]
+ }
+ },
+ "required": [
+ "access_level"
+ ]
+ },
+ "examples": {
+ "default": {
+ "value": {
+ "access_level": "organization"
+ }
+ }
+ }
+ }
+ }
+ }
+ },
+ "x-github": {
+ "githubCloudOnly": false,
+ "enabledForGitHubApps": true,
+ "previews": [
+
+ ],
+ "category": "actions",
+ "subcategory": "permissions"
+ }
+ },
+ "put": {
+ "summary": "Set the level of access for workflows outside of the repository",
+ "description": "Sets the level of access that workflows outside of the repository have to actions and workflows in the repository.\nThis endpoint only applies to internal repositories. For more information, see \"[Managing GitHub Actions settings for a repository](https://docs.github.com/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).\"\n\nYou must authenticate using an access token with the `repo` scope to use this endpoint. GitHub Apps must have the\nrepository `administration` permission to use this endpoint.",
+ "tags": [
+ "actions"
+ ],
+ "operationId": "actions/set-workflow-access-to-repository",
+ "externalDocs": {
+ "description": "API method documentation",
+ "url": "https://docs.github.com/rest/reference/actions#set-workflow-access-to-a-repository"
+ },
+ "parameters": [
+ {
+ "name": "owner",
+ "in": "path",
+ "required": true,
+ "schema": {
+ "type": "string"
+ }
+ },
+ {
+ "name": "repo",
+ "in": "path",
+ "required": true,
+ "schema": {
+ "type": "string"
+ }
+ }
+ ],
+ "requestBody": {
+ "required": true,
+ "content": {
+ "application/json": {
+ "schema": {
+ "type": "object",
+ "properties": {
+ "access_level": {
+ "type": "string",
+ "description": "Defines the level of access that workflows outside of the repository have to actions and workflows within the\nrepository. `none` means access is only possible from workflows in this repository. Can be one of `none`, `organization`, `enterprise`.",
+ "enum": [
+ "none",
+ "organization",
+ "enterprise"
+ ]
+ }
+ },
+ "required": [
+ "access_level"
+ ]
+ },
+ "examples": {
+ "default": {
+ "value": {
+ "access_level": "organization"
+ }
+ }
+ }
+ }
+ }
+ },
+ "responses": {
+ "204": {
+ "description": "Response"
+ }
+ },
+ "x-github": {
+ "githubCloudOnly": false,
+ "enabledForGitHubApps": true,
+ "previews": [
+
+ ],
+ "category": "actions",
+ "subcategory": "permissions"
+ }
+ }
+ },
"/repos/{owner}/{repo}/actions/permissions/selected-actions": {
"get": {
"summary": "Get allowed actions for a repository",
diff --git a/lib/search/popular-pages.json b/lib/search/popular-pages.json
index b56e1dea7f2a..22acf203f8bc 100644
--- a/lib/search/popular-pages.json
+++ b/lib/search/popular-pages.json
@@ -1,1000 +1,1000 @@
-{"path_article": "index", "path_count": 2590643}
-{"path_article": "authentication/connecting-to-github-with-ssh", "path_count": 479626}
-{"path_article": "authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent", "path_count": 437850}
-{"path_article": "authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token", "path_count": 374883}
-{"path_article": "get-started/quickstart/hello-world", "path_count": 350974}
-{"path_article": "pages", "path_count": 328472}
-{"path_article": "github/site-policy/github-privacy-statement", "path_count": 304909}
-{"path_article": "authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account", "path_count": 284510}
-{"path_article": "github/site-policy/github-terms-of-service", "path_count": 275206}
-{"path_article": "issues/trying-out-the-new-projects-experience", "path_count": 222495}
-{"path_article": "github/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax", "path_count": 206441}
-{"path_article": "get-started/quickstart/set-up-git", "path_count": 148124}
-{"path_article": "authentication/connecting-to-github-with-ssh/checking-for-existing-ssh-keys", "path_count": 131969}
-{"path_article": "github/importing-your-projects-to-github/importing-source-code-to-github/adding-an-existing-project-to-github-using-the-command-line", "path_count": 129356}
-{"path_article": "rest", "path_count": 128910}
-{"path_article": "codespaces", "path_count": 120111}
-{"path_article": "actions", "path_count": 113185}
-{"path_article": "get-started/getting-started-with-git/managing-remote-repositories", "path_count": 109951}
-{"path_article": "repositories/creating-and-managing-repositories/cloning-a-repository", "path_count": 103582}
-{"path_article": "rest/reference/repos", "path_count": 101750}
-{"path_article": "authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication", "path_count": 96522}
-{"path_article": "get-started/quickstart", "path_count": 95530}
-{"path_article": "get-started/getting-started-with-git/about-remote-repositories", "path_count": 89270}
-{"path_article": "get-started/getting-started-with-git/setting-your-username-in-git", "path_count": 89051}
-{"path_article": "pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests", "path_count": 88566}
-{"path_article": "actions/learn-github-actions/workflow-syntax-for-github-actions", "path_count": 84702}
-{"path_article": "pages/configuring-a-custom-domain-for-your-github-pages-site", "path_count": 82850}
-{"path_article": "authentication/troubleshooting-ssh/error-permission-denied-publickey", "path_count": 80800}
-{"path_article": "account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/setting-your-commit-email-address", "path_count": 75930}
-{"path_article": "authentication", "path_count": 74864}
-{"path_article": "account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/changing-your-primary-email-address", "path_count": 73988}
-{"path_article": "account-and-profile", "path_count": 71650}
-{"path_article": "get-started/learning-about-github/types-of-github-accounts", "path_count": 71151}
-{"path_article": "get-started/learning-about-github/githubs-products", "path_count": 70438}
-{"path_article": "actions/using-workflows/workflow-syntax-for-github-actions", "path_count": 61655}
-{"path_article": "get-started/quickstart/fork-a-repo", "path_count": 60234}
-{"path_article": "get-started/getting-started-with-git/caching-your-github-credentials-in-git", "path_count": 59148}
-{"path_article": "authentication/connecting-to-github-with-ssh/testing-your-ssh-connection", "path_count": 58673}
-{"path_article": "get-started/quickstart/create-a-repo", "path_count": 56301}
-{"path_article": "pull-requests/committing-changes-to-your-project/creating-and-editing-commits/changing-a-commit-message", "path_count": 51552}
-{"path_article": "actions/learn-github-actions", "path_count": 50681}
-{"path_article": "actions/learn-github-actions/environment-variables", "path_count": 49769}
-{"path_article": "authentication/connecting-to-github-with-ssh/working-with-ssh-key-passphrases", "path_count": 49046}
-{"path_article": "account-and-profile/setting-up-and-managing-your-github-profile", "path_count": 47984}
-{"path_article": "account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/why-are-my-contributions-not-showing-up-on-my-profile", "path_count": 47381}
-{"path_article": "get-started", "path_count": 46342}
-{"path_article": "actions/learn-github-actions/events-that-trigger-workflows", "path_count": 46137}
-{"path_article": "get-started/quickstart/github-flow", "path_count": 44899}
-{"path_article": "get-started/learning-about-github/access-permissions-on-github", "path_count": 44138}
-{"path_article": "account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository", "path_count": 43723}
-{"path_article": "get-started/signing-up-for-github/verifying-your-email-address", "path_count": 42654}
-{"path_article": "desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop/installing-github-desktop", "path_count": 42276}
-{"path_article": "actions/learn-github-actions/contexts", "path_count": 42263}
-{"path_article": "pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site", "path_count": 42139}
-{"path_article": "get-started/getting-started-with-git/ignoring-files", "path_count": 41803}
-{"path_article": "authentication/managing-commit-signature-verification", "path_count": 40711}
-{"path_article": "repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository", "path_count": 40173}
-{"path_article": "pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews", "path_count": 39164}
-{"path_article": "get-started/using-git/pushing-commits-to-a-remote-repository", "path_count": 39113}
-{"path_article": "pages/getting-started-with-github-pages", "path_count": 38645}
-{"path_article": "pages/getting-started-with-github-pages/about-github-pages", "path_count": 38191}
-{"path_article": "github/writing-on-github/working-with-advanced-formatting/creating-and-highlighting-code-blocks", "path_count": 37942}
-{"path_article": "pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-using-the-command-line", "path_count": 37511}
-{"path_article": "repositories/working-with-files/managing-files/adding-a-file-to-a-repository", "path_count": 37236}
-{"path_article": "account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/changing-your-github-username", "path_count": 36997}
-{"path_article": "rest/guides/getting-started-with-the-rest-api", "path_count": 36958}
-{"path_article": "get-started/using-github/supported-browsers", "path_count": 36365}
-{"path_article": "developers/overview/managing-deploy-keys", "path_count": 36322}
-{"path_article": "search-github/searching-on-github/searching-issues-and-pull-requests", "path_count": 36212}
-{"path_article": "actions/using-workflows/events-that-trigger-workflows", "path_count": 36171}
-{"path_article": "authentication/securing-your-account-with-two-factor-authentication-2fa/accessing-github-using-two-factor-authentication", "path_count": 35724}
-{"path_article": "pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository", "path_count": 34615}
-{"path_article": "pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request", "path_count": 34480}
-{"path_article": "repositories/creating-and-managing-repositories/deleting-a-repository", "path_count": 34433}
-{"path_article": "organizations/restricting-access-to-your-organizations-data/about-oauth-app-access-restrictions", "path_count": 34052}
-{"path_article": "actions/security-guides/encrypted-secrets", "path_count": 33686}
-{"path_article": "issues/trying-out-the-new-projects-experience/about-projects", "path_count": 33650}
-{"path_article": "packages/working-with-a-github-packages-registry/working-with-the-npm-registry", "path_count": 33191}
-{"path_article": "repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility", "path_count": 31409}
-{"path_article": "authentication/securing-your-account-with-two-factor-authentication-2fa", "path_count": 31235}
-{"path_article": "actions/learn-github-actions/understanding-github-actions", "path_count": 30624}
-{"path_article": "authentication/managing-commit-signature-verification/generating-a-new-gpg-key", "path_count": 30299}
-{"path_article": "rest/overview/other-authentication-methods", "path_count": 30166}
-{"path_article": "packages/working-with-a-github-packages-registry/working-with-the-docker-registry", "path_count": 29583}
-{"path_article": "get-started/getting-started-with-git/updating-credentials-from-the-macos-keychain", "path_count": 29469}
-{"path_article": "pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site", "path_count": 29155}
-{"path_article": "repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes", "path_count": 28732}
-{"path_article": "desktop", "path_count": 28404}
-{"path_article": "developers/apps/building-oauth-apps/authorizing-oauth-apps", "path_count": 27348}
-{"path_article": "get-started/using-github/troubleshooting-connectivity-problems", "path_count": 27270}
-{"path_article": "pages/getting-started-with-github-pages/creating-a-github-pages-site", "path_count": 26585}
-{"path_article": "repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches", "path_count": 26517}
-{"path_article": "rest/overview/resources-in-the-rest-api", "path_count": 26477}
-{"path_article": "code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-dependabot-security-updates", "path_count": 26255}
-{"path_article": "repositories/releasing-projects-on-github/about-releases", "path_count": 26111}
-{"path_article": "authentication/authenticating-with-saml-single-sign-on", "path_count": 26101}
-{"path_article": "actions/hosting-your-own-runners/about-self-hosted-runners", "path_count": 25892}
-{"path_article": "authentication/connecting-to-github-with-ssh/about-ssh", "path_count": 25078}
-{"path_article": "actions/security-guides/automatic-token-authentication", "path_count": 24936}
-{"path_article": "developers/webhooks-and-events/webhooks/webhook-events-and-payloads", "path_count": 24650}
-{"path_article": "actions/using-github-hosted-runners/about-github-hosted-runners", "path_count": 24412}
-{"path_article": "issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue", "path_count": 24310}
-{"path_article": "packages/working-with-a-github-packages-registry/working-with-the-container-registry", "path_count": 24251}
-{"path_article": null, "path_count": 23954}
-{"path_article": "graphql/overview/explorer", "path_count": 23772}
-{"path_article": "github", "path_count": 23414}
-{"path_article": "pages/quickstart", "path_count": 23081}
-{"path_article": "rest/reference/users", "path_count": 22971}
-{"path_article": "graphql", "path_count": 22686}
-{"path_article": "developers/webhooks-and-events/webhooks/about-webhooks", "path_count": 22553}
-{"path_article": "repositories/releasing-projects-on-github/managing-releases-in-a-repository", "path_count": 22490}
-{"path_article": "repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/changing-the-default-branch", "path_count": 22155}
-{"path_article": "actions/quickstart", "path_count": 21935}
-{"path_article": "rest/reference/actions", "path_count": 21809}
-{"path_article": "packages", "path_count": 21790}
-{"path_article": "authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository", "path_count": 21700}
-{"path_article": "repositories/working-with-files/managing-large-files", "path_count": 21668}
-{"path_article": "authentication/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials", "path_count": 21619}
-{"path_article": "packages/learn-github-packages/introduction-to-github-packages", "path_count": 21355}
-{"path_article": "pages/setting-up-a-github-pages-site-with-jekyll", "path_count": 21272}
-{"path_article": "get-started/using-git/about-git", "path_count": 21181}
-{"path_article": "actions/learn-github-actions/expressions", "path_count": 21114}
-{"path_article": "authentication/authenticating-with-saml-single-sign-on/authorizing-an-ssh-key-for-use-with-saml-single-sign-on", "path_count": 21020}
-{"path_article": "repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule", "path_count": 20890}
-{"path_article": "search-github/searching-on-github/searching-code", "path_count": 20766}
-{"path_article": "repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners", "path_count": 20338}
-{"path_article": "pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-on-github", "path_count": 20115}
-{"path_article": "billing/managing-your-github-billing-settings/setting-your-billing-email", "path_count": 20078}
-{"path_article": "pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork", "path_count": 19792}
-{"path_article": "authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on", "path_count": 19335}
-{"path_article": "repositories", "path_count": 19267}
-{"path_article": "desktop/contributing-and-collaborating-using-github-desktop/managing-commits/reverting-a-commit", "path_count": 19250}
-{"path_article": "repositories/creating-and-managing-repositories/duplicating-a-repository", "path_count": 19233}
-{"path_article": "rest/reference/pulls", "path_count": 19018}
-{"path_article": "desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/managing-branches", "path_count": 18926}
-{"path_article": "get-started/getting-started-with-git/configuring-git-to-handle-line-endings", "path_count": 18839}
-{"path_article": "codespaces/getting-started/quickstart", "path_count": 18832}
-{"path_article": "issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards", "path_count": 18700}
-{"path_article": "developers/apps/building-oauth-apps/scopes-for-oauth-apps", "path_count": 18539}
-{"path_article": "github/writing-on-github/getting-started-with-writing-and-formatting-on-github", "path_count": 18501}
-{"path_article": "get-started/getting-started-with-git/why-is-git-always-asking-for-my-password", "path_count": 18418}
-{"path_article": "desktop/contributing-and-collaborating-using-github-desktop/keeping-your-local-repository-in-sync-with-github/syncing-your-branch", "path_count": 18178}
-{"path_article": "developers", "path_count": 17983}
-{"path_article": "code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/configuration-options-for-dependency-updates", "path_count": 17958}
-{"path_article": "account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/managing-your-profile-readme", "path_count": 17901}
-{"path_article": "pull-requests/committing-changes-to-your-project/viewing-and-comparing-commits/comparing-commits", "path_count": 17708}
-{"path_article": "repositories/creating-and-managing-repositories/transferring-a-repository", "path_count": 17707}
-{"path_article": "account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/maintaining-ownership-continuity-of-your-user-accounts-repositories", "path_count": 17624}
-{"path_article": "actions/managing-workflow-runs/manually-running-a-workflow", "path_count": 16938}
-{"path_article": "authentication/managing-commit-signature-verification/adding-a-new-gpg-key-to-your-github-account", "path_count": 16860}
-{"path_article": "authentication/managing-commit-signature-verification/signing-commits", "path_count": 16751}
-{"path_article": "github/writing-on-github/working-with-advanced-formatting/organizing-information-with-tables", "path_count": 16495}
-{"path_article": "admin/release-notes", "path_count": 16323}
-{"path_article": "authentication/managing-commit-signature-verification/displaying-verification-statuses-for-all-of-your-commits", "path_count": 16232}
-{"path_article": "get-started/onboarding/getting-started-with-your-github-account", "path_count": 16210}
-{"path_article": "pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request", "path_count": 16130}
-{"path_article": "authentication/securing-your-account-with-two-factor-authentication-2fa/about-two-factor-authentication", "path_count": 16064}
-{"path_article": "pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site", "path_count": 15879}
-{"path_article": "get-started/signing-up-for-github/signing-up-for-a-new-github-account", "path_count": 15826}
-{"path_article": "rest/reference/search", "path_count": 15809}
-{"path_article": "authentication/keeping-your-account-and-data-secure/githubs-ssh-key-fingerprints", "path_count": 15193}
-{"path_article": "authentication/keeping-your-account-and-data-secure/creating-a-strong-password", "path_count": 15174}
-{"path_article": "get-started/using-git/getting-changes-from-a-remote-repository", "path_count": 14893}
-{"path_article": "actions/learn-github-actions/workflow-commands-for-github-actions", "path_count": 14772}
-{"path_article": "get-started/quickstart/github-glossary", "path_count": 14653}
-{"path_article": "developers/overview/github-developer-program", "path_count": 14583}
-{"path_article": "account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/deleting-your-user-account", "path_count": 14576}
-{"path_article": "actions/creating-actions/metadata-syntax-for-github-actions", "path_count": 14445}
-{"path_article": "desktop/installing-and-configuring-github-desktop", "path_count": 14442}
-{"path_article": "repositories/working-with-files/managing-files/deleting-files-in-a-repository", "path_count": 14426}
-{"path_article": "organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization", "path_count": 14417}
-{"path_article": "authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication-recovery-methods", "path_count": 14414}
-{"path_article": "actions/creating-actions/creating-a-docker-container-action", "path_count": 14403}
-{"path_article": "pages/configuring-a-custom-domain-for-your-github-pages-site/about-custom-domains-and-github-pages", "path_count": 14374}
-{"path_article": "authentication/keeping-your-account-and-data-secure/about-authentication-to-github", "path_count": 14340}
-{"path_article": "desktop/contributing-and-collaborating-using-github-desktop/adding-and-cloning-repositories/cloning-and-forking-repositories-from-github-desktop", "path_count": 14338}
-{"path_article": "rest/reference/issues", "path_count": 14333}
-{"path_article": "issues/organizing-your-work-with-project-boards/managing-project-boards/configuring-automation-for-project-boards", "path_count": 14330}
-{"path_article": "account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-a-user-account-repository", "path_count": 14299}
-{"path_article": "billing/managing-billing-for-github-actions/about-billing-for-github-actions", "path_count": 13969}
-{"path_article": "authentication/managing-commit-signature-verification/telling-git-about-your-signing-key", "path_count": 13916}
-{"path_article": "authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on", "path_count": 13876}
-{"path_article": "repositories/creating-and-managing-repositories/creating-a-new-repository", "path_count": 13870}
-{"path_article": "account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/adding-an-email-address-to-your-github-account", "path_count": 13837}
-{"path_article": "communities/using-templates-to-encourage-useful-issues-and-pull-requests/creating-a-pull-request-template-for-your-repository", "path_count": 13704}
-{"path_article": "account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile", "path_count": 13670}
-{"path_article": "get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax", "path_count": 13445}
-{"path_article": "authentication/keeping-your-account-and-data-secure/authorizing-oauth-apps", "path_count": 13414}
-{"path_article": "billing", "path_count": 13387}
-{"path_article": "repositories/working-with-files/managing-large-files/about-large-files-on-github", "path_count": 13366}
-{"path_article": "pages/getting-started-with-github-pages/adding-a-theme-to-your-github-pages-site-with-the-theme-chooser", "path_count": 13253}
-{"path_article": "actions/learn-github-actions/reusing-workflows", "path_count": 13250}
-{"path_article": "actions/automating-builds-and-tests/about-continuous-integration", "path_count": 13097}
-{"path_article": "education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork/apply-for-a-student-developer-pack", "path_count": 13042}
-{"path_article": "repositories/creating-and-managing-repositories/troubleshooting-cloning-errors", "path_count": 12962}
-{"path_article": "actions/deployment/targeting-different-environments/using-environments-for-deployment", "path_count": 12951}
-{"path_article": "actions/advanced-guides/storing-workflow-data-as-artifacts", "path_count": 12765}
-{"path_article": "github-cli/github-cli/about-github-cli", "path_count": 12721}
-{"path_article": "organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization", "path_count": 12703}
-{"path_article": "pages/configuring-a-custom-domain-for-your-github-pages-site/troubleshooting-custom-domains-and-github-pages", "path_count": 12652}
-{"path_article": "search-github/getting-started-with-searching-on-github/about-searching-on-github", "path_count": 12646}
-{"path_article": "graphql/reference/objects", "path_count": 12454}
-{"path_article": "github/writing-on-github/editing-and-sharing-content-with-gists/creating-gists", "path_count": 12403}
-{"path_article": "get-started/learning-about-github/about-github-advanced-security", "path_count": 12401}
-{"path_article": "account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications", "path_count": 12288}
-{"path_article": "packages/working-with-a-github-packages-registry/working-with-the-apache-maven-registry", "path_count": 12229}
-{"path_article": "organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization", "path_count": 12202}
-{"path_article": "github/writing-on-github/working-with-advanced-formatting/autolinked-references-and-urls", "path_count": 12028}
-{"path_article": "repositories/creating-and-managing-repositories/about-repositories", "path_count": 11929}
-{"path_article": "repositories/working-with-files/managing-large-files/installing-git-large-file-storage", "path_count": 11829}
-{"path_article": "actions/learn-github-actions/finding-and-customizing-actions", "path_count": 11753}
-{"path_article": "actions/advanced-guides/caching-dependencies-to-speed-up-workflows", "path_count": 11714}
-{"path_article": "actions/using-workflows/workflow-commands-for-github-actions", "path_count": 11622}
-{"path_article": "code-security", "path_count": 11567}
-{"path_article": "pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/approving-a-pull-request-with-required-reviews", "path_count": 11520}
-{"path_article": "pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally", "path_count": 11515}
-{"path_article": "rest/reference/orgs", "path_count": 11442}
-{"path_article": "developers/apps", "path_count": 11426}
-{"path_article": "github/site-policy/github-community-guidelines", "path_count": 11403}
-{"path_article": "pages/setting-up-a-github-pages-site-with-jekyll/about-github-pages-and-jekyll", "path_count": 11341}
-{"path_article": "github/writing-on-github", "path_count": 11256}
-{"path_article": "repositories/creating-and-managing-repositories/creating-a-repository-from-a-template", "path_count": 11117}
-{"path_article": "repositories/creating-and-managing-repositories/renaming-a-repository", "path_count": 11021}
-{"path_article": "repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/renaming-a-branch", "path_count": 11005}
-{"path_article": "communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository", "path_count": 10955}
-{"path_article": "get-started/quickstart/git-and-github-learning-resources", "path_count": 10889}
-{"path_article": "communities/setting-up-your-project-for-healthy-contributions/adding-a-license-to-a-repository", "path_count": 10857}
-{"path_article": "authentication/securing-your-account-with-two-factor-authentication-2fa/countries-where-sms-authentication-is-supported", "path_count": 10805}
-{"path_article": "repositories/working-with-files/managing-files/renaming-a-file", "path_count": 10760}
-{"path_article": "pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/reverting-a-pull-request", "path_count": 10727}
-{"path_article": "authentication/managing-commit-signature-verification/checking-for-existing-gpg-keys", "path_count": 10722}
-{"path_article": "actions/creating-actions/creating-a-composite-action", "path_count": 10680}
-{"path_article": "developers/webhooks-and-events/webhooks/creating-webhooks", "path_count": 10637}
-{"path_article": "issues/tracking-your-work-with-issues/about-issues", "path_count": 10625}
-{"path_article": "repositories/working-with-files/managing-large-files/configuring-git-large-file-storage", "path_count": 10622}
-{"path_article": "authentication/managing-commit-signature-verification/about-commit-signature-verification", "path_count": 10568}
-{"path_article": "actions/hosting-your-own-runners/adding-self-hosted-runners", "path_count": 10544}
-{"path_article": "packages/working-with-a-github-packages-registry/working-with-the-nuget-registry", "path_count": 10536}
-{"path_article": "get-started/quickstart/contributing-to-projects", "path_count": 10456}
-{"path_article": "actions/using-workflows/reusing-workflows", "path_count": 10367}
-{"path_article": "pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork", "path_count": 10357}
-{"path_article": "account-and-profile/managing-subscriptions-and-notifications-on-github", "path_count": 10120}
-{"path_article": "organizations", "path_count": 10110}
-{"path_article": "pages/getting-started-with-github-pages/securing-your-github-pages-site-with-https", "path_count": 10050}
-{"path_article": "developers/apps/getting-started-with-apps/about-apps", "path_count": 9904}
-{"path_article": "pull-requests/collaborating-with-pull-requests/working-with-forks/configuring-a-remote-for-a-fork", "path_count": 9873}
-{"path_article": "get-started/using-git/dealing-with-non-fast-forward-errors", "path_count": 9835}
-{"path_article": "rest/reference/git", "path_count": 9674}
-{"path_article": "authentication/keeping-your-account-and-data-secure/updating-your-github-access-credentials", "path_count": 9665}
-{"path_article": "repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests", "path_count": 9613}
-{"path_article": "communities/documenting-your-project-with-wikis/about-wikis", "path_count": 9590}
-{"path_article": "repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-citation-files", "path_count": 9527}
-{"path_article": "github/site-policy", "path_count": 9516}
-{"path_article": "pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review", "path_count": 9442}
-{"path_article": "account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/viewing-contributions-on-your-profile", "path_count": 9434}
-{"path_article": "account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/merging-multiple-user-accounts", "path_count": 9343}
-{"path_article": "organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization", "path_count": 9342}
-{"path_article": "repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/deleting-and-restoring-branches-in-a-pull-request", "path_count": 9339}
-{"path_article": "rest/reference/checks", "path_count": 9280}
-{"path_article": "actions/creating-actions", "path_count": 9234}
-{"path_article": "actions/learn-github-actions/managing-complex-workflows", "path_count": 9120}
-{"path_article": "desktop/installing-and-configuring-github-desktop/overview/getting-started-with-github-desktop", "path_count": 9068}
-{"path_article": "pages/setting-up-a-github-pages-site-with-jekyll/adding-content-to-your-github-pages-site-using-jekyll", "path_count": 9052}
-{"path_article": "search-github/getting-started-with-searching-on-github/understanding-the-search-syntax", "path_count": 9004}
-{"path_article": "codespaces/the-githubdev-web-based-editor", "path_count": 8984}
-{"path_article": "pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request", "path_count": 8983}
-{"path_article": "pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request", "path_count": 8958}
-{"path_article": "authentication/keeping-your-account-and-data-secure", "path_count": 8929}
-{"path_article": "rest/guides/basics-of-authentication", "path_count": 8913}
-{"path_article": "desktop/contributing-and-collaborating-using-github-desktop/adding-and-cloning-repositories/adding-a-repository-from-your-local-computer-to-github-desktop", "path_count": 8797}
-{"path_article": "pages/setting-up-a-github-pages-site-with-jekyll/creating-a-github-pages-site-with-jekyll", "path_count": 8793}
-{"path_article": "issues/tracking-your-work-with-issues/creating-an-issue", "path_count": 8784}
-{"path_article": "actions/learn-github-actions/essential-features-of-github-actions", "path_count": 8733}
-{"path_article": "issues/tracking-your-work-with-issues/about-task-lists", "path_count": 8719}
-{"path_article": "get-started/using-git/resolving-merge-conflicts-after-a-git-rebase", "path_count": 8713}
-{"path_article": "organizations/collaborating-with-groups-in-organizations/about-organizations", "path_count": 8660}
-{"path_article": "repositories/working-with-files/using-files/working-with-non-code-files", "path_count": 8605}
-{"path_article": "admin", "path_count": 8597}
-{"path_article": "actions/hosting-your-own-runners", "path_count": 8544}
-{"path_article": "discussions", "path_count": 8524}
-{"path_article": "actions/learn-github-actions/usage-limits-billing-and-administration", "path_count": 8450}
-{"path_article": "issues", "path_count": 8417}
-{"path_article": "repositories/working-with-files/managing-large-files/about-git-large-file-storage", "path_count": 8390}
-{"path_article": "get-started/using-github/keyboard-shortcuts", "path_count": 8386}
-{"path_article": "github/writing-on-github/getting-started-with-writing-and-formatting-on-github/about-writing-and-formatting-on-github", "path_count": 8329}
-{"path_article": "pull-requests", "path_count": 8256}
-{"path_article": "graphql/guides/forming-calls-with-graphql", "path_count": 8224}
-{"path_article": "developers/apps/building-github-apps/authenticating-with-github-apps", "path_count": 8147}
-{"path_article": "actions/deployment/about-deployments/deploying-with-github-actions", "path_count": 8138}
-{"path_article": "pages/setting-up-a-github-pages-site-with-jekyll/testing-your-github-pages-site-locally-with-jekyll", "path_count": 8087}
-{"path_article": "repositories/working-with-files/managing-files/moving-a-file-to-a-new-location", "path_count": 8064}
-{"path_article": "pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request", "path_count": 8042}
-{"path_article": "authentication/troubleshooting-ssh", "path_count": 8031}
-{"path_article": "get-started/importing-your-projects-to-github/importing-source-code-to-github/adding-an-existing-project-to-github-using-the-command-line", "path_count": 8021}
-{"path_article": "pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches", "path_count": 8003}
-{"path_article": "codespaces/managing-codespaces-for-your-organization/enabling-codespaces-for-your-organization", "path_count": 7949}
-{"path_article": "code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning", "path_count": 7911}
-{"path_article": "actions/publishing-packages/publishing-docker-images", "path_count": 7890}
-{"path_article": "pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges", "path_count": 7846}
-{"path_article": "authentication/keeping-your-account-and-data-secure/about-githubs-ip-addresses", "path_count": 7844}
-{"path_article": "desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/pushing-changes-to-github", "path_count": 7710}
-{"path_article": "github/importing-your-projects-to-github/importing-source-code-to-github/importing-a-git-repository-using-the-command-line", "path_count": 7647}
-{"path_article": "repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository", "path_count": 7590}
-{"path_article": "search-github/searching-on-github/searching-for-repositories", "path_count": 7588}
-{"path_article": "github-cli", "path_count": 7536}
-{"path_article": "actions/monitoring-and-troubleshooting-workflows/adding-a-workflow-status-badge", "path_count": 7481}
-{"path_article": "rest/reference/activity", "path_count": 7463}
-{"path_article": "organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch", "path_count": 7450}
-{"path_article": "desktop/contributing-and-collaborating-using-github-desktop/managing-commits/cherry-picking-a-commit", "path_count": 7408}
-{"path_article": "repositories/creating-and-managing-repositories/creating-a-template-repository", "path_count": 7377}
-{"path_article": "pages/getting-started-with-github-pages/unpublishing-a-github-pages-site", "path_count": 7372}
-{"path_article": "issues/using-labels-and-milestones-to-track-work/managing-labels", "path_count": 7365}
-{"path_article": "get-started/quickstart/git-cheatsheet", "path_count": 7359}
-{"path_article": "pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks", "path_count": 7354}
-{"path_article": "code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies", "path_count": 7191}
-{"path_article": "desktop/contributing-and-collaborating-using-github-desktop/adding-and-cloning-repositories/cloning-a-repository-from-github-to-github-desktop", "path_count": 7186}
-{"path_article": "code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-dependabot-security-updates", "path_count": 7181}
-{"path_article": "desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop/authenticating-to-github", "path_count": 7154}
-{"path_article": "rest/reference/apps", "path_count": 7045}
-{"path_article": "search-github/searching-on-github/searching-users", "path_count": 7016}
-{"path_article": "actions/automating-builds-and-tests/building-and-testing-nodejs-or-python", "path_count": 7003}
-{"path_article": "authentication/troubleshooting-ssh/recovering-your-ssh-key-passphrase", "path_count": 6998}
-{"path_article": "authentication/troubleshooting-ssh/using-ssh-over-the-https-port", "path_count": 6979}
-{"path_article": "account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-profile", "path_count": 6911}
-{"path_article": "repositories/working-with-files/managing-files/editing-files", "path_count": 6893}
-{"path_article": "developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps", "path_count": 6857}
-{"path_article": "desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/viewing-the-branch-history", "path_count": 6827}
-{"path_article": "pull-requests/committing-changes-to-your-project/troubleshooting-commits/why-are-my-commits-linked-to-the-wrong-user", "path_count": 6812}
-{"path_article": "code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph", "path_count": 6801}
-{"path_article": "communities/documenting-your-project-with-wikis/adding-or-editing-wiki-pages", "path_count": 6794}
-{"path_article": "pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/closing-a-pull-request", "path_count": 6769}
-{"path_article": "organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team", "path_count": 6731}
-{"path_article": "organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository", "path_count": 6682}
-{"path_article": "packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions", "path_count": 6666}
-{"path_article": "search-github/searching-on-github/searching-commits", "path_count": 6644}
-{"path_article": "desktop/contributing-and-collaborating-using-github-desktop/managing-commits/managing-tags", "path_count": 6622}
-{"path_article": "actions/creating-actions/about-custom-actions", "path_count": 6607}
-{"path_article": "rest/reference/commits", "path_count": 6567}
-{"path_article": "actions/security-guides/security-hardening-for-github-actions", "path_count": 6517}
-{"path_article": "account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/remembering-your-github-username-or-email", "path_count": 6465}
-{"path_article": "pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request", "path_count": 6449}
-{"path_article": "repositories/releasing-projects-on-github/automatically-generated-release-notes", "path_count": 6443}
-{"path_article": "actions/managing-workflow-runs/approving-workflow-runs-from-public-forks", "path_count": 6399}
-{"path_article": "developers/overview/using-ssh-agent-forwarding", "path_count": 6370}
-{"path_article": "developers/apps/managing-github-apps/installing-github-apps", "path_count": 6360}
-{"path_article": "pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-with-multiple-authors", "path_count": 6284}
-{"path_article": "repositories/working-with-files/managing-files/creating-new-files", "path_count": 6260}
-{"path_article": "desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/committing-and-reviewing-changes-to-your-project", "path_count": 6254}
-{"path_article": "communities/using-templates-to-encourage-useful-issues-and-pull-requests/about-issue-and-pull-request-templates", "path_count": 6253}
-{"path_article": "actions/hosting-your-own-runners/configuring-the-self-hosted-runner-application-as-a-service", "path_count": 6249}
-{"path_article": "github/site-policy/dmca-takedown-policy", "path_count": 6243}
-{"path_article": "repositories/creating-and-managing-repositories/restoring-a-deleted-repository", "path_count": 6206}
-{"path_article": "rest/reference/permissions-required-for-github-apps", "path_count": 6173}
-{"path_article": "issues/trying-out-the-new-projects-experience/quickstart", "path_count": 6150}
-{"path_article": "github/writing-on-github/working-with-advanced-formatting/creating-a-permanent-link-to-a-code-snippet", "path_count": 6123}
-{"path_article": "actions/using-workflows/advanced-workflow-features", "path_count": 6081}
-{"path_article": "pull-requests/collaborating-with-pull-requests/working-with-forks/merging-an-upstream-repository-into-your-fork", "path_count": 6038}
-{"path_article": "github/importing-your-projects-to-github/importing-source-code-to-github/importing-a-repository-with-github-importer", "path_count": 6033}
-{"path_article": "developers/apps/building-github-apps/creating-a-github-app", "path_count": 6007}
-{"path_article": "pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks", "path_count": 5970}
-{"path_article": "desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/creating-an-issue-or-pull-request", "path_count": 5940}
-{"path_article": "pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-base-branch-of-a-pull-request", "path_count": 5897}
-{"path_article": "pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-comparing-branches-in-pull-requests", "path_count": 5860}
-{"path_article": "rest/overview/libraries", "path_count": 5848}
-{"path_article": "repositories/creating-and-managing-repositories", "path_count": 5845}
-{"path_article": "authentication/keeping-your-account-and-data-secure/sudo-mode", "path_count": 5833}
-{"path_article": "get-started/exploring-projects-on-github/finding-ways-to-contribute-to-open-source-on-github", "path_count": 5819}
-{"path_article": "search-github", "path_count": 5754}
-{"path_article": "pull-requests/committing-changes-to-your-project/viewing-and-comparing-commits/differences-between-commit-views", "path_count": 5751}
-{"path_article": "github/writing-on-github/working-with-advanced-formatting/attaching-files", "path_count": 5742}
-{"path_article": "pages/configuring-a-custom-domain-for-your-github-pages-site/verifying-your-custom-domain-for-github-pages", "path_count": 5732}
-{"path_article": "packages/learn-github-packages/about-permissions-for-github-packages", "path_count": 5706}
-{"path_article": "organizations/organizing-members-into-teams", "path_count": 5699}
-{"path_article": "get-started/quickstart/be-social", "path_count": 5672}
-{"path_article": "github/extending-github/git-automation-with-oauth-tokens", "path_count": 5620}
-{"path_article": "codespaces/setting-up-your-project-for-codespaces/configuring-codespaces-for-your-project", "path_count": 5603}
+{"path_article": "index", "path_count": 2561381}
+{"path_article": "authentication/connecting-to-github-with-ssh", "path_count": 513366}
+{"path_article": "authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent", "path_count": 491571}
+{"path_article": "authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token", "path_count": 439532}
+{"path_article": "get-started/quickstart/hello-world", "path_count": 371241}
+{"path_article": "github/site-policy/github-privacy-statement", "path_count": 317967}
+{"path_article": "pages", "path_count": 316045}
+{"path_article": "authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account", "path_count": 310595}
+{"path_article": "github/site-policy/github-terms-of-service", "path_count": 274943}
+{"path_article": "get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax", "path_count": 245202}
+{"path_article": "issues/trying-out-the-new-projects-experience", "path_count": 234364}
+{"path_article": "get-started/quickstart/set-up-git", "path_count": 185288}
+{"path_article": "actions/using-workflows/workflow-syntax-for-github-actions", "path_count": 170253}
+{"path_article": null, "path_count": 150463}
+{"path_article": "authentication/connecting-to-github-with-ssh/checking-for-existing-ssh-keys", "path_count": 149048}
+{"path_article": "rest", "path_count": 143992}
+{"path_article": "get-started/importing-your-projects-to-github/importing-source-code-to-github/adding-an-existing-project-to-github-using-the-command-line", "path_count": 141074}
+{"path_article": "get-started/getting-started-with-git/managing-remote-repositories", "path_count": 128565}
+{"path_article": "repositories/creating-and-managing-repositories/cloning-a-repository", "path_count": 125291}
+{"path_article": "codespaces", "path_count": 124025}
+{"path_article": "actions", "path_count": 120636}
+{"path_article": "authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication", "path_count": 102727}
+{"path_article": "pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests", "path_count": 100567}
+{"path_article": "get-started/getting-started-with-git/about-remote-repositories", "path_count": 99537}
+{"path_article": "actions/using-workflows/events-that-trigger-workflows", "path_count": 98405}
+{"path_article": "rest/reference/repos", "path_count": 95320}
+{"path_article": "get-started/getting-started-with-git/setting-your-username-in-git", "path_count": 93216}
+{"path_article": "authentication/troubleshooting-ssh/error-permission-denied-publickey", "path_count": 90268}
+{"path_article": "pages/configuring-a-custom-domain-for-your-github-pages-site", "path_count": 82950}
+{"path_article": "account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/setting-your-commit-email-address", "path_count": 81066}
+{"path_article": "get-started/learning-about-github/githubs-products", "path_count": 76465}
+{"path_article": "get-started/quickstart", "path_count": 74711}
+{"path_article": "account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/changing-your-primary-email-address", "path_count": 74670}
+{"path_article": "authentication", "path_count": 73459}
+{"path_article": "get-started/learning-about-github/types-of-github-accounts", "path_count": 72407}
+{"path_article": "get-started/quickstart/fork-a-repo", "path_count": 72363}
+{"path_article": "get-started/quickstart/create-a-repo", "path_count": 72256}
+{"path_article": "authentication/connecting-to-github-with-ssh/testing-your-ssh-connection", "path_count": 62935}
+{"path_article": "get-started/getting-started-with-git/caching-your-github-credentials-in-git", "path_count": 62926}
+{"path_article": "actions/learn-github-actions/environment-variables", "path_count": 61585}
+{"path_article": "pull-requests/committing-changes-to-your-project/creating-and-editing-commits/changing-a-commit-message", "path_count": 61374}
+{"path_article": "authentication/connecting-to-github-with-ssh/working-with-ssh-key-passphrases", "path_count": 55730}
+{"path_article": "get-started/signing-up-for-github/verifying-your-email-address", "path_count": 52647}
+{"path_article": "get-started/using-git/pushing-commits-to-a-remote-repository", "path_count": 52174}
+{"path_article": "actions/learn-github-actions/contexts", "path_count": 51054}
+{"path_article": "actions/learn-github-actions", "path_count": 50907}
+{"path_article": "pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-using-the-command-line", "path_count": 50555}
+{"path_article": "account-and-profile", "path_count": 49850}
+{"path_article": "account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository", "path_count": 49539}
+{"path_article": "get-started/learning-about-github/access-permissions-on-github", "path_count": 49327}
+{"path_article": "account-and-profile/setting-up-and-managing-your-github-profile", "path_count": 48351}
+{"path_article": "desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop/installing-github-desktop", "path_count": 48283}
+{"path_article": "get-started/quickstart/github-flow", "path_count": 48264}
+{"path_article": "get-started/getting-started-with-git/ignoring-files", "path_count": 47783}
+{"path_article": "authentication/managing-commit-signature-verification", "path_count": 47329}
+{"path_article": "account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/why-are-my-contributions-not-showing-up-on-my-profile", "path_count": 47246}
+{"path_article": "repositories/working-with-files/managing-files/adding-a-file-to-a-repository", "path_count": 47199}
+{"path_article": "pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews", "path_count": 46762}
+{"path_article": "developers/overview/managing-deploy-keys", "path_count": 45054}
+{"path_article": "pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository", "path_count": 44450}
+{"path_article": "pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request", "path_count": 43554}
+{"path_article": "rest/guides/getting-started-with-the-rest-api", "path_count": 43092}
+{"path_article": "repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes", "path_count": 42943}
+{"path_article": "pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site", "path_count": 42857}
+{"path_article": "repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository", "path_count": 42126}
+{"path_article": "search-github/searching-on-github/searching-issues-and-pull-requests", "path_count": 41335}
+{"path_article": "repositories/creating-and-managing-repositories/deleting-a-repository", "path_count": 40990}
+{"path_article": "actions/security-guides/encrypted-secrets", "path_count": 40223}
+{"path_article": "pages/getting-started-with-github-pages/about-github-pages", "path_count": 39746}
+{"path_article": "get-started", "path_count": 39723}
+{"path_article": "account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/changing-your-github-username", "path_count": 39369}
+{"path_article": "pages/getting-started-with-github-pages", "path_count": 39249}
+{"path_article": "get-started/writing-on-github/working-with-advanced-formatting/creating-and-highlighting-code-blocks", "path_count": 38605}
+{"path_article": "organizations/restricting-access-to-your-organizations-data/about-oauth-app-access-restrictions", "path_count": 37337}
+{"path_article": "packages/working-with-a-github-packages-registry/working-with-the-npm-registry", "path_count": 37197}
+{"path_article": "repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility", "path_count": 36499}
+{"path_article": "actions/learn-github-actions/understanding-github-actions", "path_count": 35935}
+{"path_article": "authentication/managing-commit-signature-verification/generating-a-new-gpg-key", "path_count": 35597}
+{"path_article": "get-started/using-github/supported-browsers", "path_count": 34806}
+{"path_article": "developers/webhooks-and-events/webhooks/webhook-events-and-payloads", "path_count": 34340}
+{"path_article": "get-started/using-github/troubleshooting-connectivity-problems", "path_count": 33391}
+{"path_article": "rest/overview/other-authentication-methods", "path_count": 33155}
+{"path_article": "repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches", "path_count": 33003}
+{"path_article": "actions/using-workflows/workflow-commands-for-github-actions", "path_count": 31926}
+{"path_article": "actions/hosting-your-own-runners/about-self-hosted-runners", "path_count": 31305}
+{"path_article": "get-started/getting-started-with-git/updating-credentials-from-the-macos-keychain", "path_count": 31273}
+{"path_article": "packages/working-with-a-github-packages-registry/working-with-the-docker-registry", "path_count": 31178}
+{"path_article": "rest/reference/commits", "path_count": 30935}
+{"path_article": "rest/overview/resources-in-the-rest-api", "path_count": 30914}
+{"path_article": "pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site", "path_count": 30206}
+{"path_article": "developers/apps/building-oauth-apps/authorizing-oauth-apps", "path_count": 29438}
+{"path_article": "code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-dependabot-security-updates", "path_count": 29413}
+{"path_article": "actions/security-guides/automatic-token-authentication", "path_count": 29222}
+{"path_article": "issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue", "path_count": 29112}
+{"path_article": "actions/using-workflows/reusing-workflows", "path_count": 29011}
+{"path_article": "actions/using-github-hosted-runners/about-github-hosted-runners", "path_count": 28282}
+{"path_article": "authentication/authenticating-with-saml-single-sign-on", "path_count": 28054}
+{"path_article": "pages/getting-started-with-github-pages/creating-a-github-pages-site", "path_count": 28023}
+{"path_article": "pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-on-github", "path_count": 27549}
+{"path_article": "actions/learn-github-actions/expressions", "path_count": 27316}
+{"path_article": "rest/reference/users", "path_count": 27293}
+{"path_article": "desktop", "path_count": 27105}
+{"path_article": "repositories/releasing-projects-on-github/about-releases", "path_count": 26949}
+{"path_article": "repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/changing-the-default-branch", "path_count": 26824}
+{"path_article": "repositories/releasing-projects-on-github/managing-releases-in-a-repository", "path_count": 26793}
+{"path_article": "developers/webhooks-and-events/webhooks/about-webhooks", "path_count": 26666}
+{"path_article": "repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners", "path_count": 26574}
+{"path_article": "authentication/connecting-to-github-with-ssh/about-ssh", "path_count": 26574}
+{"path_article": "rest/reference/actions", "path_count": 26398}
+{"path_article": "repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule", "path_count": 25902}
+{"path_article": "packages/working-with-a-github-packages-registry/working-with-the-container-registry", "path_count": 25704}
+{"path_article": "actions/quickstart", "path_count": 25409}
+{"path_article": "pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork", "path_count": 25128}
+{"path_article": "graphql", "path_count": 25047}
+{"path_article": "authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository", "path_count": 24824}
+{"path_article": "graphql/overview/explorer", "path_count": 24755}
+{"path_article": "repositories/working-with-files/managing-large-files", "path_count": 24534}
+{"path_article": "authentication/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials", "path_count": 23862}
+{"path_article": "authentication/securing-your-account-with-two-factor-authentication-2fa/accessing-github-using-two-factor-authentication", "path_count": 23830}
+{"path_article": "authentication/authenticating-with-saml-single-sign-on/authorizing-an-ssh-key-for-use-with-saml-single-sign-on", "path_count": 23793}
+{"path_article": "search-github/searching-on-github/searching-code", "path_count": 23241}
+{"path_article": "rest/reference/pulls", "path_count": 23003}
+{"path_article": "admin/release-notes", "path_count": 22555}
+{"path_article": "desktop/contributing-and-collaborating-using-github-desktop/managing-commits/reverting-a-commit", "path_count": 22463}
+{"path_article": "pages/quickstart", "path_count": 22353}
+{"path_article": "desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/managing-branches", "path_count": 22326}
+{"path_article": "authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on", "path_count": 22265}
+{"path_article": "repositories/creating-and-managing-repositories/duplicating-a-repository", "path_count": 22204}
+{"path_article": "get-started/getting-started-with-git/configuring-git-to-handle-line-endings", "path_count": 22025}
+{"path_article": "desktop/contributing-and-collaborating-using-github-desktop/keeping-your-local-repository-in-sync-with-github/syncing-your-branch", "path_count": 21742}
+{"path_article": "packages/learn-github-packages/introduction-to-github-packages", "path_count": 21588}
+{"path_article": "get-started/getting-started-with-git/why-is-git-always-asking-for-my-password", "path_count": 21399}
+{"path_article": "get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github", "path_count": 21185}
+{"path_article": "pages/setting-up-a-github-pages-site-with-jekyll", "path_count": 21085}
+{"path_article": "packages", "path_count": 21023}
+{"path_article": "actions/managing-workflow-runs/manually-running-a-workflow", "path_count": 20678}
+{"path_article": "code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/configuration-options-for-dependency-updates", "path_count": 20654}
+{"path_article": "authentication/securing-your-account-with-two-factor-authentication-2fa", "path_count": 20643}
+{"path_article": "issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards", "path_count": 20591}
+{"path_article": "developers/apps/building-oauth-apps/scopes-for-oauth-apps", "path_count": 20470}
+{"path_article": "pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request", "path_count": 20384}
+{"path_article": "pull-requests/committing-changes-to-your-project/viewing-and-comparing-commits/comparing-commits", "path_count": 20313}
+{"path_article": "billing/managing-your-github-billing-settings/setting-your-billing-email", "path_count": 20279}
+{"path_article": "account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/managing-your-profile-readme", "path_count": 19884}
+{"path_article": "repositories/creating-and-managing-repositories/transferring-a-repository", "path_count": 19868}
+{"path_article": "authentication/managing-commit-signature-verification/signing-commits", "path_count": 19449}
+{"path_article": "authentication/managing-commit-signature-verification/adding-a-new-gpg-key-to-your-github-account", "path_count": 19353}
+{"path_article": "get-started/using-git/getting-changes-from-a-remote-repository", "path_count": 19173}
+{"path_article": "get-started/writing-on-github/working-with-advanced-formatting/organizing-information-with-tables", "path_count": 19146}
+{"path_article": "issues/trying-out-the-new-projects-experience/about-projects", "path_count": 18989}
+{"path_article": "rest/reference/search", "path_count": 18947}
+{"path_article": "codespaces/getting-started/quickstart", "path_count": 18899}
+{"path_article": "repositories", "path_count": 18563}
+{"path_article": "organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization", "path_count": 18038}
+{"path_article": "actions/creating-actions/metadata-syntax-for-github-actions", "path_count": 17594}
+{"path_article": "repositories/creating-and-managing-repositories/troubleshooting-cloning-errors", "path_count": 17564}
+{"path_article": "authentication/managing-commit-signature-verification/displaying-verification-statuses-for-all-of-your-commits", "path_count": 17464}
+{"path_article": "account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-a-user-account-repository", "path_count": 17185}
+{"path_article": "account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/deleting-your-user-account", "path_count": 17131}
+{"path_article": "actions/creating-actions/creating-a-docker-container-action", "path_count": 17078}
+{"path_article": "pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site", "path_count": 17051}
+{"path_article": "get-started/signing-up-for-github/signing-up-for-a-new-github-account", "path_count": 16987}
+{"path_article": "communities/using-templates-to-encourage-useful-issues-and-pull-requests/creating-a-pull-request-template-for-your-repository", "path_count": 16978}
+{"path_article": "get-started/using-git/about-git", "path_count": 16876}
+{"path_article": "repositories/working-with-files/managing-files/deleting-files-in-a-repository", "path_count": 16756}
+{"path_article": "billing/managing-billing-for-github-actions/about-billing-for-github-actions", "path_count": 16669}
+{"path_article": "rest/reference/issues", "path_count": 16557}
+{"path_article": "education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork/apply-for-a-student-developer-pack", "path_count": 16455}
+{"path_article": "github-cli/github-cli/about-github-cli", "path_count": 16365}
+{"path_article": "actions/deployment/targeting-different-environments/using-environments-for-deployment", "path_count": 16189}
+{"path_article": "get-started/quickstart/github-glossary", "path_count": 16165}
+{"path_article": "authentication/keeping-your-account-and-data-secure/githubs-ssh-key-fingerprints", "path_count": 16149}
+{"path_article": "github", "path_count": 16097}
+{"path_article": "repositories/working-with-files/managing-large-files/about-large-files-on-github", "path_count": 16023}
+{"path_article": "authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on", "path_count": 15849}
+{"path_article": "authentication/managing-commit-signature-verification/telling-git-about-your-signing-key", "path_count": 15835}
+{"path_article": "authentication/securing-your-account-with-two-factor-authentication-2fa/about-two-factor-authentication", "path_count": 15750}
+{"path_article": "repositories/creating-and-managing-repositories/creating-a-new-repository", "path_count": 15712}
+{"path_article": "actions/using-workflows/advanced-workflow-features", "path_count": 15569}
+{"path_article": "developers", "path_count": 15529}
+{"path_article": "search-github/getting-started-with-searching-on-github/about-searching-on-github", "path_count": 15411}
+{"path_article": "desktop/installing-and-configuring-github-desktop", "path_count": 15215}
+{"path_article": "graphql/reference/objects", "path_count": 15156}
+{"path_article": "authentication/keeping-your-account-and-data-secure/creating-a-strong-password", "path_count": 15112}
+{"path_article": "authentication/keeping-your-account-and-data-secure/about-authentication-to-github", "path_count": 14966}
+{"path_article": "account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile", "path_count": 14886}
+{"path_article": "desktop/contributing-and-collaborating-using-github-desktop/adding-and-cloning-repositories/cloning-and-forking-repositories-from-github-desktop", "path_count": 14785}
+{"path_article": "developers/overview/github-developer-program", "path_count": 14778}
+{"path_article": "pages/configuring-a-custom-domain-for-your-github-pages-site/about-custom-domains-and-github-pages", "path_count": 14645}
+{"path_article": "pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/approving-a-pull-request-with-required-reviews", "path_count": 14572}
+{"path_article": "organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization", "path_count": 14499}
+{"path_article": "authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication-recovery-methods", "path_count": 14491}
+{"path_article": "get-started/learning-about-github/about-github-advanced-security", "path_count": 14468}
+{"path_article": "actions/using-workflows/triggering-a-workflow", "path_count": 14425}
+{"path_article": "repositories/working-with-files/managing-large-files/installing-git-large-file-storage", "path_count": 14242}
+{"path_article": "actions/automating-builds-and-tests/about-continuous-integration", "path_count": 14239}
+{"path_article": "authentication/keeping-your-account-and-data-secure/authorizing-oauth-apps", "path_count": 14211}
+{"path_article": "account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/adding-an-email-address-to-your-github-account", "path_count": 14192}
+{"path_article": "repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/renaming-a-branch", "path_count": 14129}
+{"path_article": "repositories/creating-and-managing-repositories/about-repositories", "path_count": 13769}
+{"path_article": "rest/reference/orgs", "path_count": 13753}
+{"path_article": "get-started/writing-on-github/working-with-advanced-formatting/autolinked-references-and-urls", "path_count": 13603}
+{"path_article": "pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally", "path_count": 13426}
+{"path_article": "get-started/writing-on-github/editing-and-sharing-content-with-gists/creating-gists", "path_count": 13224}
+{"path_article": "account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications", "path_count": 13174}
+{"path_article": "pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/reverting-a-pull-request", "path_count": 13144}
+{"path_article": "organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization", "path_count": 13045}
+{"path_article": "repositories/working-with-files/managing-files/renaming-a-file", "path_count": 12878}
+{"path_article": "actions/creating-actions", "path_count": 12872}
+{"path_article": "repositories/creating-and-managing-repositories/renaming-a-repository", "path_count": 12864}
+{"path_article": "developers/webhooks-and-events/webhooks/creating-webhooks", "path_count": 12768}
+{"path_article": "actions/creating-actions/creating-a-composite-action", "path_count": 12714}
+{"path_article": "actions/hosting-your-own-runners/adding-self-hosted-runners", "path_count": 12577}
+{"path_article": "packages/working-with-a-github-packages-registry/working-with-the-apache-maven-registry", "path_count": 12427}
+{"path_article": "pages/getting-started-with-github-pages/adding-a-theme-to-your-github-pages-site-with-the-theme-chooser", "path_count": 12415}
+{"path_article": "repositories/creating-and-managing-repositories/creating-a-repository-from-a-template", "path_count": 12353}
+{"path_article": "pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork", "path_count": 12286}
+{"path_article": "github/site-policy/github-community-guidelines", "path_count": 12267}
+{"path_article": "developers/apps", "path_count": 12266}
+{"path_article": "get-started/onboarding/getting-started-with-your-github-account", "path_count": 12243}
+{"path_article": "repositories/working-with-files/managing-large-files/configuring-git-large-file-storage", "path_count": 12241}
+{"path_article": "get-started/using-git/dealing-with-non-fast-forward-errors", "path_count": 12240}
+{"path_article": "authentication/managing-commit-signature-verification/about-commit-signature-verification", "path_count": 12149}
+{"path_article": "pages/configuring-a-custom-domain-for-your-github-pages-site/troubleshooting-custom-domains-and-github-pages", "path_count": 11834}
+{"path_article": "authentication/managing-commit-signature-verification/checking-for-existing-gpg-keys", "path_count": 11777}
+{"path_article": "packages/working-with-a-github-packages-registry/working-with-the-nuget-registry", "path_count": 11776}
+{"path_article": "rest/reference/git", "path_count": 11745}
+{"path_article": "issues/tracking-your-work-with-issues/about-issues", "path_count": 11723}
+{"path_article": "communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository", "path_count": 11707}
+{"path_article": "get-started/writing-on-github", "path_count": 11694}
+{"path_article": "actions/learn-github-actions/finding-and-customizing-actions", "path_count": 11658}
+{"path_article": "actions/hosting-your-own-runners", "path_count": 11635}
+{"path_article": "pull-requests/collaborating-with-pull-requests/working-with-forks/configuring-a-remote-for-a-fork", "path_count": 11500}
+{"path_article": "communities/setting-up-your-project-for-healthy-contributions/adding-a-license-to-a-repository", "path_count": 11462}
+{"path_article": "get-started/quickstart/contributing-to-projects", "path_count": 11458}
+{"path_article": "repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests", "path_count": 11453}
+{"path_article": "authentication/keeping-your-account-and-data-secure/updating-your-github-access-credentials", "path_count": 11410}
+{"path_article": "repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/deleting-and-restoring-branches-in-a-pull-request", "path_count": 11395}
+{"path_article": "pages/setting-up-a-github-pages-site-with-jekyll/about-github-pages-and-jekyll", "path_count": 11322}
+{"path_article": "search-github/getting-started-with-searching-on-github/understanding-the-search-syntax", "path_count": 11213}
+{"path_article": "pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request", "path_count": 11205}
+{"path_article": "get-started/quickstart/git-and-github-learning-resources", "path_count": 11198}
+{"path_article": "communities/documenting-your-project-with-wikis/about-wikis", "path_count": 11178}
+{"path_article": "pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request", "path_count": 11136}
+{"path_article": "github/site-policy", "path_count": 10959}
+{"path_article": "rest/reference/checks", "path_count": 10815}
+{"path_article": "authentication/securing-your-account-with-two-factor-authentication-2fa/countries-where-sms-authentication-is-supported", "path_count": 10795}
+{"path_article": "code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning", "path_count": 10750}
+{"path_article": "get-started/using-git/resolving-merge-conflicts-after-a-git-rebase", "path_count": 10697}
+{"path_article": "authentication/keeping-your-account-and-data-secure/about-githubs-ip-addresses", "path_count": 10595}
+{"path_article": "pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review", "path_count": 10589}
+{"path_article": "organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization", "path_count": 10521}
+{"path_article": "get-started/importing-your-projects-to-github/importing-source-code-to-github/importing-a-git-repository-using-the-command-line", "path_count": 10438}
+{"path_article": "issues/tracking-your-work-with-issues/creating-an-issue", "path_count": 10400}
+{"path_article": "actions/learn-github-actions/usage-limits-billing-and-administration", "path_count": 10395}
+{"path_article": "get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/about-writing-and-formatting-on-github", "path_count": 10391}
+{"path_article": "rest/guides/basics-of-authentication", "path_count": 10221}
+{"path_article": "pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request", "path_count": 10201}
+{"path_article": "desktop/contributing-and-collaborating-using-github-desktop/managing-commits/cherry-picking-a-commit", "path_count": 10147}
+{"path_article": "organizations/collaborating-with-groups-in-organizations/about-organizations", "path_count": 10099}
+{"path_article": "desktop/contributing-and-collaborating-using-github-desktop/adding-and-cloning-repositories/adding-a-repository-from-your-local-computer-to-github-desktop", "path_count": 10078}
+{"path_article": "repositories/working-with-files/using-files/working-with-non-code-files", "path_count": 10042}
+{"path_article": "organizations", "path_count": 10026}
+{"path_article": "account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/merging-multiple-user-accounts", "path_count": 9894}
+{"path_article": "repositories/working-with-files/managing-large-files/about-git-large-file-storage", "path_count": 9887}
+{"path_article": "developers/apps/building-github-apps/authenticating-with-github-apps", "path_count": 9835}
+{"path_article": "desktop/installing-and-configuring-github-desktop/overview/getting-started-with-github-desktop", "path_count": 9832}
+{"path_article": "issues/tracking-your-work-with-issues/about-task-lists", "path_count": 9828}
+{"path_article": "developers/apps/getting-started-with-apps/about-apps", "path_count": 9816}
+{"path_article": "pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches", "path_count": 9804}
+{"path_article": "billing", "path_count": 9780}
+{"path_article": "pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges", "path_count": 9736}
+{"path_article": "graphql/guides/forming-calls-with-graphql", "path_count": 9721}
+{"path_article": "repositories/working-with-files/managing-files/moving-a-file-to-a-new-location", "path_count": 9720}
+{"path_article": "search-github/searching-on-github/searching-for-repositories", "path_count": 9648}
+{"path_article": "actions/using-workflows", "path_count": 9475}
+{"path_article": "actions/deployment/about-deployments/deploying-with-github-actions", "path_count": 9459}
+{"path_article": "actions/learn-github-actions/essential-features-of-github-actions", "path_count": 9449}
+{"path_article": "account-and-profile/managing-subscriptions-and-notifications-on-github", "path_count": 9438}
+{"path_article": "pages/getting-started-with-github-pages/securing-your-github-pages-site-with-https", "path_count": 9409}
+{"path_article": "account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/viewing-contributions-on-your-profile", "path_count": 9303}
+{"path_article": "pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks", "path_count": 9282}
+{"path_article": "desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/pushing-changes-to-github", "path_count": 9273}
+{"path_article": "pages/setting-up-a-github-pages-site-with-jekyll/adding-content-to-your-github-pages-site-using-jekyll", "path_count": 9174}
+{"path_article": "actions/publishing-packages/publishing-docker-images", "path_count": 9153}
+{"path_article": "codespaces/the-githubdev-web-based-editor", "path_count": 9112}
+{"path_article": "get-started/using-github/keyboard-shortcuts", "path_count": 9008}
+{"path_article": "repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository", "path_count": 8957}
+{"path_article": "code-security", "path_count": 8912}
+{"path_article": "pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request", "path_count": 8874}
+{"path_article": "pages/setting-up-a-github-pages-site-with-jekyll/creating-a-github-pages-site-with-jekyll", "path_count": 8760}
+{"path_article": "repositories/creating-and-managing-repositories/creating-a-template-repository", "path_count": 8742}
+{"path_article": "account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/remembering-your-github-username-or-email", "path_count": 8687}
+{"path_article": "desktop/contributing-and-collaborating-using-github-desktop/adding-and-cloning-repositories/cloning-a-repository-from-github-to-github-desktop", "path_count": 8576}
+{"path_article": "organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch", "path_count": 8533}
+{"path_article": "actions/monitoring-and-troubleshooting-workflows/adding-a-workflow-status-badge", "path_count": 8532}
+{"path_article": "rest/reference/apps", "path_count": 8528}
+{"path_article": "get-started/importing-your-projects-to-github/importing-source-code-to-github/importing-a-repository-with-github-importer", "path_count": 8509}
+{"path_article": "issues/using-labels-and-milestones-to-track-work/managing-labels", "path_count": 8479}
+{"path_article": "get-started/using-github/github-mobile", "path_count": 8478}
+{"path_article": "desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/viewing-the-branch-history", "path_count": 8416}
+{"path_article": "rest/reference/activity", "path_count": 8355}
+{"path_article": "authentication/troubleshooting-ssh", "path_count": 8331}
+{"path_article": "pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/closing-a-pull-request", "path_count": 8330}
+{"path_article": "code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-dependabot-security-updates", "path_count": 8283}
+{"path_article": "organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team", "path_count": 8252}
+{"path_article": "authentication/troubleshooting-ssh/recovering-your-ssh-key-passphrase", "path_count": 8196}
+{"path_article": "discussions", "path_count": 8192}
+{"path_article": "search-github/searching-on-github/searching-commits", "path_count": 8159}
+{"path_article": "repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository", "path_count": 8134}
+{"path_article": "desktop/contributing-and-collaborating-using-github-desktop/managing-commits/managing-tags", "path_count": 8053}
+{"path_article": "communities/documenting-your-project-with-wikis/adding-or-editing-wiki-pages", "path_count": 8038}
+{"path_article": "codespaces/managing-codespaces-for-your-organization/enabling-codespaces-for-your-organization", "path_count": 8020}
+{"path_article": "pages/setting-up-a-github-pages-site-with-jekyll/testing-your-github-pages-site-locally-with-jekyll", "path_count": 7974}
+{"path_article": "developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps", "path_count": 7970}
+{"path_article": "pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-with-multiple-authors", "path_count": 7967}
+{"path_article": "actions/advanced-guides/storing-workflow-data-as-artifacts", "path_count": 7962}
+{"path_article": "code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies", "path_count": 7936}
+{"path_article": "code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph", "path_count": 7879}
+{"path_article": "github/site-policy/dmca-takedown-policy", "path_count": 7864}
+{"path_article": "search-github/searching-on-github/searching-users", "path_count": 7818}
+{"path_article": "repositories/creating-and-managing-repositories/restoring-a-deleted-repository", "path_count": 7798}
+{"path_article": "pull-requests/committing-changes-to-your-project/troubleshooting-commits/why-are-my-commits-linked-to-the-wrong-user", "path_count": 7796}
+{"path_article": "actions/using-workflows/storing-workflow-data-as-artifacts", "path_count": 7773}
+{"path_article": "developers/overview/using-ssh-agent-forwarding", "path_count": 7769}
+{"path_article": "actions/creating-actions/about-custom-actions", "path_count": 7731}
+{"path_article": "authentication/troubleshooting-ssh/using-ssh-over-the-https-port", "path_count": 7720}
+{"path_article": "repositories/working-with-files/managing-files/creating-new-files", "path_count": 7688}
+{"path_article": "admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/about-enterprise-managed-users", "path_count": 7640}
+{"path_article": "repositories/releasing-projects-on-github/automatically-generated-release-notes", "path_count": 7634}
+{"path_article": "get-started/writing-on-github/working-with-advanced-formatting/creating-a-permanent-link-to-a-code-snippet", "path_count": 7630}
+{"path_article": "pages/getting-started-with-github-pages/unpublishing-a-github-pages-site", "path_count": 7610}
+{"path_article": "actions/using-workflows/creating-starter-workflows-for-your-organization", "path_count": 7545}
+{"path_article": "authentication/keeping-your-account-and-data-secure", "path_count": 7534}
+{"path_article": "get-started/quickstart/git-cheatsheet", "path_count": 7528}
+{"path_article": "actions/security-guides/security-hardening-for-github-actions", "path_count": 7507}
+{"path_article": "repositories/working-with-files/managing-files/editing-files", "path_count": 7419}
+{"path_article": "actions/automating-builds-and-tests/building-and-testing-nodejs-or-python", "path_count": 7397}
+{"path_article": "pull-requests", "path_count": 7339}
+{"path_article": "admin", "path_count": 7313}
+{"path_article": "actions/using-jobs/using-jobs-in-a-workflow", "path_count": 7300}
+{"path_article": "desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/committing-and-reviewing-changes-to-your-project", "path_count": 7279}
+{"path_article": "github-cli", "path_count": 7273}
+{"path_article": "communities/using-templates-to-encourage-useful-issues-and-pull-requests/about-issue-and-pull-request-templates", "path_count": 7181}
+{"path_article": "actions/hosting-your-own-runners/configuring-the-self-hosted-runner-application-as-a-service", "path_count": 7166}
+{"path_article": "pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-base-branch-of-a-pull-request", "path_count": 7142}
+{"path_article": "actions/using-workflows/caching-dependencies-to-speed-up-workflows", "path_count": 7139}
+{"path_article": "issues", "path_count": 7126}
+{"path_article": "pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks", "path_count": 7105}
+{"path_article": "rest/overview/libraries", "path_count": 7071}
+{"path_article": "rest/reference/permissions-required-for-github-apps", "path_count": 7009}
+{"path_article": "desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop/authenticating-to-github", "path_count": 7002}
+{"path_article": "desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/creating-an-issue-or-pull-request", "path_count": 6946}
+{"path_article": "account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-profile", "path_count": 6934}
+{"path_article": "pull-requests/collaborating-with-pull-requests/working-with-forks/merging-an-upstream-repository-into-your-fork", "path_count": 6932}
+{"path_article": "developers/apps/building-github-apps/creating-a-github-app", "path_count": 6930}
+{"path_article": "packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions", "path_count": 6919}
+{"path_article": "actions/advanced-guides/caching-dependencies-to-speed-up-workflows", "path_count": 6898}
+{"path_article": "pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-comparing-branches-in-pull-requests", "path_count": 6852}
+{"path_article": "rest/reference/teams", "path_count": 6815}
+{"path_article": "get-started/quickstart/be-social", "path_count": 6813}
+{"path_article": "developers/apps/managing-github-apps/installing-github-apps", "path_count": 6802}
+{"path_article": "packages/learn-github-packages/about-permissions-for-github-packages", "path_count": 6797}
+{"path_article": "codespaces/setting-up-your-project-for-codespaces/configuring-codespaces-for-your-project", "path_count": 6736}
+{"path_article": "desktop/contributing-and-collaborating-using-github-desktop/managing-commits/squashing-commits", "path_count": 6714}
+{"path_article": "actions/managing-workflow-runs/approving-workflow-runs-from-public-forks", "path_count": 6704}
+{"path_article": "authentication/keeping-your-account-and-data-secure/sudo-mode", "path_count": 6695}
+{"path_article": "rest/reference/branches", "path_count": 6629}
+{"path_article": "organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository", "path_count": 6626}
+{"path_article": "repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/viewing-branches-in-your-repository", "path_count": 6592}
+{"path_article": "get-started/writing-on-github/working-with-advanced-formatting/attaching-files", "path_count": 6588}
+{"path_article": "developers/apps/building-oauth-apps/creating-an-oauth-app", "path_count": 6522}
+{"path_article": "pull-requests/committing-changes-to-your-project/viewing-and-comparing-commits/differences-between-commit-views", "path_count": 6492}
+{"path_article": "pages/configuring-a-custom-domain-for-your-github-pages-site/verifying-your-custom-domain-for-github-pages", "path_count": 6430}
+{"path_article": "organizations/organizing-members-into-teams", "path_count": 6387}
+{"path_article": "repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-the-automatic-deletion-of-branches", "path_count": 6335}
+{"path_article": "actions/creating-actions/creating-a-javascript-action", "path_count": 6310}
+{"path_article": "get-started/getting-started-with-git/associating-text-editors-with-git", "path_count": 6304}
+{"path_article": "rest/reference/releases", "path_count": 6283}
+{"path_article": "rest/reference", "path_count": 6251}
+{"path_article": "authentication/managing-commit-signature-verification/associating-an-email-with-your-gpg-key", "path_count": 6118}
+{"path_article": "get-started/using-git/about-git-rebase", "path_count": 6064}
+{"path_article": "repositories/working-with-files/using-files/navigating-code-on-github", "path_count": 6055}
+{"path_article": "organizations/managing-access-to-your-organizations-repositories/viewing-people-with-access-to-your-repository", "path_count": 6050}
+{"path_article": "repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/classifying-your-repository-with-topics", "path_count": 6048}
+{"path_article": "education/explore-the-benefits-of-teaching-and-learning-with-github-education", "path_count": 6038}
+{"path_article": "organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization", "path_count": 5935}
+{"path_article": "billing/managing-billing-for-github-codespaces/about-billing-for-codespaces", "path_count": 5926}
+{"path_article": "actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow", "path_count": 5914}
+{"path_article": "search-github/searching-on-github/finding-files-on-github", "path_count": 5909}
+{"path_article": "developers/webhooks-and-events/events/github-event-types", "path_count": 5900}
+{"path_article": "code-security/secret-scanning/about-secret-scanning", "path_count": 5801}
+{"path_article": "organizations/organizing-members-into-teams/about-teams", "path_count": 5779}
+{"path_article": "get-started/exploring-projects-on-github/finding-ways-to-contribute-to-open-source-on-github", "path_count": 5743}
+{"path_article": "communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors", "path_count": 5741}
+{"path_article": "pull-requests/collaborating-with-pull-requests/working-with-forks", "path_count": 5740}
+{"path_article": "code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository", "path_count": 5711}
+{"path_article": "code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/enabling-and-disabling-dependabot-version-updates", "path_count": 5670}
+{"path_article": "authentication/troubleshooting-ssh/error-permission-to-userrepo-denied-to-userother-repo", "path_count": 5659}
+{"path_article": "admin/overview/about-enterprise-accounts", "path_count": 5654}
+{"path_article": "account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/maintaining-ownership-continuity-of-your-user-accounts-repositories", "path_count": 5635}
+{"path_article": "actions/publishing-packages/publishing-nodejs-packages", "path_count": 5604}
+{"path_article": "authentication/keeping-your-account-and-data-secure/reviewing-your-ssh-keys", "path_count": 5602}
{"path_article": "pages/setting-up-a-github-pages-site-with-jekyll/adding-a-theme-to-your-github-pages-site-using-jekyll", "path_count": 5597}
-{"path_article": "admin/overview/about-enterprise-accounts", "path_count": 5588}
-{"path_article": "communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors", "path_count": 5585}
-{"path_article": "repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/classifying-your-repository-with-topics", "path_count": 5536}
-{"path_article": "get-started/using-github/github-mobile", "path_count": 5527}
-{"path_article": "code-security/secret-scanning/about-secret-scanning", "path_count": 5463}
-{"path_article": "actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-amazon-web-services", "path_count": 5450}
-{"path_article": "rest/reference", "path_count": 5443}
-{"path_article": "code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/about-dependabot-version-updates", "path_count": 5439}
-{"path_article": "account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/publicizing-or-hiding-your-private-contributions-on-your-profile", "path_count": 5439}
-{"path_article": "developers/apps/building-oauth-apps/creating-an-oauth-app", "path_count": 5434}
-{"path_article": "billing/managing-billing-for-github-codespaces/about-billing-for-codespaces", "path_count": 5382}
-{"path_article": "rest/reference/teams", "path_count": 5315}
-{"path_article": "get-started/exploring-projects-on-github/saving-repositories-with-stars", "path_count": 5307}
-{"path_article": "repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/viewing-branches-in-your-repository", "path_count": 5305}
-{"path_article": "authentication/managing-commit-signature-verification/associating-an-email-with-your-gpg-key", "path_count": 5299}
-{"path_article": "repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository", "path_count": 5279}
-{"path_article": "actions/creating-actions/creating-a-javascript-action", "path_count": 5183}
-{"path_article": "actions/learn-github-actions/creating-starter-workflows-for-your-organization", "path_count": 5164}
-{"path_article": "account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/viewing-your-subscriptions", "path_count": 5108}
-{"path_article": "search-github/searching-on-github/finding-files-on-github", "path_count": 5079}
-{"path_article": "pages/setting-up-a-github-pages-site-with-jekyll/troubleshooting-jekyll-build-errors-for-github-pages-sites", "path_count": 5079}
-{"path_article": "communities/maintaining-your-safety-on-github/reporting-abuse-or-spam", "path_count": 5071}
-{"path_article": "repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-the-automatic-deletion-of-branches", "path_count": 5040}
-{"path_article": "actions/publishing-packages/publishing-nodejs-packages", "path_count": 5035}
-{"path_article": "issues/trying-out-the-new-projects-experience/creating-a-project", "path_count": 5019}
-{"path_article": "organizations/managing-access-to-your-organizations-repositories/viewing-people-with-access-to-your-repository", "path_count": 5003}
-{"path_article": "search-github/searching-on-github", "path_count": 4949}
-{"path_article": "authentication/keeping-your-account-and-data-secure/reviewing-your-ssh-keys", "path_count": 4905}
-{"path_article": "actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow", "path_count": 4901}
-{"path_article": "code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/enabling-and-disabling-dependabot-version-updates", "path_count": 4900}
-{"path_article": "pull-requests/collaborating-with-pull-requests/working-with-forks", "path_count": 4832}
-{"path_article": "organizations/organizing-members-into-teams/about-teams", "path_count": 4816}
-{"path_article": "repositories/working-with-files/using-files/navigating-code-on-github", "path_count": 4803}
-{"path_article": "desktop/contributing-and-collaborating-using-github-desktop/managing-commits/squashing-commits", "path_count": 4780}
-{"path_article": "organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization", "path_count": 4767}
-{"path_article": "account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings", "path_count": 4732}
-{"path_article": "actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect", "path_count": 4732}
-{"path_article": "rest/reference/projects", "path_count": 4728}
-{"path_article": "communities/maintaining-your-safety-on-github/blocking-a-user-from-your-personal-account", "path_count": 4719}
-{"path_article": "account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/about-your-personal-dashboard", "path_count": 4710}
-{"path_article": "get-started/using-git/about-git-rebase", "path_count": 4651}
-{"path_article": "pages/getting-started-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site", "path_count": 4649}
-{"path_article": "repositories/releasing-projects-on-github/viewing-your-repositorys-releases-and-tags", "path_count": 4636}
-{"path_article": "education/explore-the-benefits-of-teaching-and-learning-with-github-education", "path_count": 4604}
-{"path_article": "developers/webhooks-and-events/events/github-event-types", "path_count": 4596}
-{"path_article": "repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/about-merge-methods-on-github", "path_count": 4590}
-{"path_article": "admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server", "path_count": 4585}
-{"path_article": "repositories/working-with-files/managing-large-files/about-storage-and-bandwidth-usage", "path_count": 4555}
-{"path_article": "graphql/guides/introduction-to-graphql", "path_count": 4555}
-{"path_article": "admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users", "path_count": 4537}
-{"path_article": "github/site-policy/github-acceptable-use-policies", "path_count": 4508}
-{"path_article": "issues/trying-out-the-new-projects-experience/customizing-your-project-views", "path_count": 4477}
-{"path_article": "organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository", "path_count": 4475}
-{"path_article": "get-started/getting-started-with-git/associating-text-editors-with-git", "path_count": 4467}
-{"path_article": "rest/reference/releases", "path_count": 4467}
-{"path_article": "codespaces/overview", "path_count": 4464}
-{"path_article": "organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization", "path_count": 4441}
-{"path_article": "actions/using-containerized-services/about-service-containers", "path_count": 4423}
-{"path_article": "developers/github-marketplace", "path_count": 4390}
-{"path_article": "authentication/troubleshooting-ssh/error-permission-to-userrepo-denied-to-userother-repo", "path_count": 4372}
-{"path_article": "graphql/reference/queries", "path_count": 4336}
-{"path_article": "authentication/keeping-your-account-and-data-secure/token-expiration-and-revocation", "path_count": 4331}
-{"path_article": "repositories/working-with-files/using-files/tracking-changes-in-a-file", "path_count": 4313}
-{"path_article": "desktop/installing-and-configuring-github-desktop/overview/creating-your-first-repository-using-github-desktop", "path_count": 4306}
-{"path_article": "github/site-policy/github-corporate-terms-of-service", "path_count": 4274}
-{"path_article": "rest/reference/branches", "path_count": 4270}
-{"path_article": "developers/webhooks-and-events/webhooks/configuring-your-server-to-receive-payloads", "path_count": 4265}
-{"path_article": "github/site-policy/submitting-content-removal-requests", "path_count": 4257}
-{"path_article": "developers/webhooks-and-events/webhooks/securing-your-webhooks", "path_count": 4247}
-{"path_article": "get-started/using-git", "path_count": 4244}
-{"path_article": "account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/managing-your-subscriptions", "path_count": 4206}
-{"path_article": "packages/working-with-a-github-packages-registry", "path_count": 4203}
-{"path_article": "rest/overview/media-types", "path_count": 4197}
-{"path_article": "issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests", "path_count": 4190}
-{"path_article": "account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile", "path_count": 4167}
-{"path_article": "pull-requests/collaborating-with-pull-requests/getting-started/about-collaborative-development-models", "path_count": 4165}
-{"path_article": "actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners", "path_count": 4150}
-{"path_article": "issues/using-labels-and-milestones-to-track-work/about-milestones", "path_count": 4114}
-{"path_article": "sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account", "path_count": 4101}
-{"path_article": "get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud", "path_count": 4096}
-{"path_article": "actions/monitoring-and-troubleshooting-workflows/enabling-debug-logging", "path_count": 4062}
-{"path_article": "organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization", "path_count": 4043}
-{"path_article": "actions/automating-builds-and-tests/building-and-testing-java-with-maven", "path_count": 4037}
-{"path_article": "get-started/using-git/splitting-a-subfolder-out-into-a-new-repository", "path_count": 4028}
-{"path_article": "repositories/working-with-files/managing-files/customizing-how-changed-files-appear-on-github", "path_count": 4008}
-{"path_article": "actions/using-workflows/triggering-a-workflow", "path_count": 3978}
-{"path_article": "billing/managing-billing-for-your-github-account/downgrading-your-github-subscription", "path_count": 3972}
-{"path_article": "organizations/managing-organization-settings/restricting-repository-creation-in-your-organization", "path_count": 3960}
-{"path_article": "rest/reference/enterprise-admin", "path_count": 3942}
-{"path_article": "issues/organizing-your-work-with-project-boards/managing-project-boards/creating-a-project-board", "path_count": 3940}
-{"path_article": "education", "path_count": 3914}
-{"path_article": "packages/quickstart", "path_count": 3911}
-{"path_article": "github/site-policy/github-terms-for-additional-products-and-features", "path_count": 3899}
-{"path_article": "code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository", "path_count": 3884}
-{"path_article": "actions/managing-workflow-runs/disabling-and-enabling-a-workflow", "path_count": 3881}
-{"path_article": "packages/learn-github-packages/configuring-a-packages-access-control-and-visibility", "path_count": 3874}
-{"path_article": "github/site-policy/global-privacy-practices", "path_count": 3866}
-{"path_article": "organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization", "path_count": 3794}
-{"path_article": "account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications", "path_count": 3783}
-{"path_article": "actions/managing-workflow-runs/downloading-workflow-artifacts", "path_count": 3728}
-{"path_article": "get-started/using-git/using-git-rebase-on-the-command-line", "path_count": 3725}
-{"path_article": "desktop/contributing-and-collaborating-using-github-desktop/adding-and-cloning-repositories/adding-an-existing-project-to-github-using-github-desktop", "path_count": 3703}
-{"path_article": "github/writing-on-github/working-with-advanced-formatting", "path_count": 3681}
-{"path_article": "pull-requests/collaborating-with-pull-requests", "path_count": 3675}
-{"path_article": "packages/working-with-a-github-packages-registry/working-with-the-rubygems-registry", "path_count": 3652}
-{"path_article": "github/site-policy/github-trademark-policy", "path_count": 3640}
-{"path_article": "rest/reference/rate-limit", "path_count": 3632}
-{"path_article": "organizations/collaborating-with-groups-in-organizations", "path_count": 3626}
-{"path_article": "authentication/keeping-your-account-and-data-secure/reviewing-your-authorized-integrations", "path_count": 3620}
-{"path_article": "rest/guides/delivering-deployments", "path_count": 3600}
-{"path_article": "rest/guides/getting-started-with-the-checks-api", "path_count": 3585}
-{"path_article": "get-started/using-github/github-command-palette", "path_count": 3562}
-{"path_article": "actions/learn-github-actions/using-starter-workflows", "path_count": 3556}
-{"path_article": "account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/showing-an-overview-of-your-activity-on-your-profile", "path_count": 3546}
-{"path_article": "repositories/archiving-a-github-repository/archiving-repositories", "path_count": 3543}
-{"path_article": "packages/learn-github-packages", "path_count": 3536}
-{"path_article": "rest/overview/api-previews", "path_count": 3526}
-{"path_article": "github/copilot/github-copilot-telemetry-terms", "path_count": 3521}
-{"path_article": "actions/automating-builds-and-tests", "path_count": 3511}
-{"path_article": "repositories/archiving-a-github-repository/referencing-and-citing-content", "path_count": 3508}
-{"path_article": "billing/managing-your-github-billing-settings/about-billing-on-github", "path_count": 3490}
-{"path_article": "get-started/quickstart/communicating-on-github", "path_count": 3486}
-{"path_article": "rest/reference/gists", "path_count": 3476}
-{"path_article": "github/writing-on-github/working-with-advanced-formatting/organizing-information-with-collapsed-sections", "path_count": 3464}
-{"path_article": "authentication/troubleshooting-ssh/error-key-already-in-use", "path_count": 3456}
-{"path_article": "code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning", "path_count": 3453}
-{"path_article": "pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/dismissing-a-pull-request-review", "path_count": 3442}
-{"path_article": "issues/trying-out-the-new-projects-experience/automating-projects", "path_count": 3426}
-{"path_article": "packages/working-with-a-github-packages-registry/working-with-the-gradle-registry", "path_count": 3420}
-{"path_article": "repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-squashing-for-pull-requests", "path_count": 3414}
-{"path_article": "organizations/keeping-your-organization-secure/requiring-two-factor-authentication-in-your-organization", "path_count": 3407}
-{"path_article": "rest/overview/endpoints-available-for-github-apps", "path_count": 3399}
-{"path_article": "repositories/working-with-files/using-files/getting-permanent-links-to-files", "path_count": 3398}
-{"path_article": "account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/publicizing-or-hiding-organization-membership", "path_count": 3396}
-{"path_article": "repositories/managing-your-repositorys-settings-and-features", "path_count": 3388}
-{"path_article": "code-security/supply-chain-security/keeping-your-dependencies-updated-automatically", "path_count": 3369}
-{"path_article": "desktop/installing-and-configuring-github-desktop/overview/launching-github-desktop-from-the-command-line", "path_count": 3335}
-{"path_article": "actions/using-containerized-services/creating-postgresql-service-containers", "path_count": 3328}
-{"path_article": "actions/creating-actions/setting-exit-codes-for-actions", "path_count": 3320}
-{"path_article": "developers/overview/about-githubs-apis", "path_count": 3318}
-{"path_article": "communities/documenting-your-project-with-wikis/editing-wiki-content", "path_count": 3317}
-{"path_article": "account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/pinning-items-to-your-profile", "path_count": 3308}
-{"path_article": "organizations/managing-organization-settings/renaming-an-organization", "path_count": 3305}
-{"path_article": "graphql/overview/about-the-graphql-api", "path_count": 3278}
-{"path_article": "actions/deployment/deploying-to-your-cloud-provider/deploying-to-amazon-elastic-container-service", "path_count": 3262}
-{"path_article": "packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry", "path_count": 3222}
-{"path_article": "actions/managing-workflow-runs/re-running-workflows-and-jobs", "path_count": 3220}
-{"path_article": "issues/tracking-your-work-with-issues/assigning-issues-and-pull-requests-to-other-github-users", "path_count": 3215}
-{"path_article": "actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners", "path_count": 3213}
-{"path_article": "issues/trying-out-the-new-projects-experience/using-the-api-to-manage-projects", "path_count": 3211}
-{"path_article": "actions/learn-github-actions/sharing-workflows-secrets-and-runners-with-your-organization", "path_count": 3206}
-{"path_article": "organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization", "path_count": 3200}
-{"path_article": "code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/automating-dependabot-with-github-actions", "path_count": 3191}
-{"path_article": "codespaces/developing-in-codespaces/creating-a-codespace", "path_count": 3185}
-{"path_article": "organizations/organizing-members-into-teams/creating-a-team", "path_count": 3182}
-{"path_article": "issues/organizing-your-work-with-project-boards/managing-project-boards/linking-a-repository-to-a-project-board", "path_count": 3166}
-{"path_article": "packages/learn-github-packages/publishing-a-package", "path_count": 3155}
-{"path_article": "get-started/learning-about-github/about-versions-of-github-docs", "path_count": 3117}
-{"path_article": "account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/managing-notifications-from-your-inbox", "path_count": 3078}
-{"path_article": "admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrade-requirements", "path_count": 3073}
-{"path_article": "code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository", "path_count": 3058}
-{"path_article": "developers/apps/building-github-apps/rate-limits-for-github-apps", "path_count": 3058}
-{"path_article": "organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization", "path_count": 3033}
-{"path_article": "pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/about-merge-conflicts", "path_count": 3030}
-{"path_article": "github/site-policy/github-open-source-applications-terms-and-conditions", "path_count": 3019}
-{"path_article": "actions/monitoring-and-troubleshooting-workflows/using-workflow-run-logs", "path_count": 3016}
-{"path_article": "graphql/reference/interfaces", "path_count": 3016}
-{"path_article": "rest/guides/traversing-with-pagination", "path_count": 3008}
-{"path_article": "get-started/using-github/github-cli", "path_count": 2989}
-{"path_article": "billing/managing-billing-for-your-github-account/about-per-user-pricing", "path_count": 2985}
-{"path_article": "github/site-policy/github-username-policy", "path_count": 2982}
-{"path_article": "codespaces/getting-started/deep-dive", "path_count": 2976}
-{"path_article": "actions/automating-builds-and-tests/building-and-testing-net", "path_count": 2972}
-{"path_article": "repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-autolinks-to-reference-external-resources", "path_count": 2967}
-{"path_article": "actions/managing-workflow-runs/reviewing-deployments", "path_count": 2958}
-{"path_article": "rest/guides", "path_count": 2952}
-{"path_article": "pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/incorporating-feedback-in-your-pull-request", "path_count": 2948}
-{"path_article": "graphql/overview/public-schema", "path_count": 2947}
-{"path_article": "actions/managing-workflow-runs", "path_count": 2944}
-{"path_article": "account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/blocking-command-line-pushes-that-expose-your-personal-email-address", "path_count": 2943}
-{"path_article": "desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/stashing-changes", "path_count": 2935}
-{"path_article": "actions/automating-builds-and-tests/building-and-testing-java-with-gradle", "path_count": 2923}
-{"path_article": "admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise", "path_count": 2922}
-{"path_article": "organizations/managing-membership-in-your-organization/adding-people-to-your-organization", "path_count": 2902}
-{"path_article": "code-security/getting-started/github-security-features", "path_count": 2900}
-{"path_article": "actions/guides", "path_count": 2885}
-{"path_article": "actions/using-workflows", "path_count": 2882}
-{"path_article": "rest/reference/webhooks", "path_count": 2867}
-{"path_article": "code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/viewing-and-updating-vulnerable-dependencies-in-your-repository", "path_count": 2863}
-{"path_article": "repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/displaying-a-sponsor-button-in-your-repository", "path_count": 2862}
-{"path_article": "developers/overview", "path_count": 2857}
-{"path_article": "authentication/troubleshooting-ssh/error-agent-admitted-failure-to-sign", "path_count": 2849}
-{"path_article": "repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-forking-policy-for-your-repository", "path_count": 2827}
-{"path_article": "organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on", "path_count": 2819}
-{"path_article": "repositories/viewing-activity-and-data-for-your-repository/viewing-traffic-to-a-repository", "path_count": 2813}
-{"path_article": "graphql/reference/mutations", "path_count": 2811}
-{"path_article": "desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop/setting-up-github-desktop", "path_count": 2786}
-{"path_article": "pull-requests/collaborating-with-pull-requests/working-with-forks/allowing-changes-to-a-pull-request-branch-created-from-a-fork", "path_count": 2779}
-{"path_article": "organizations/managing-access-to-your-organizations-repositories", "path_count": 2772}
-{"path_article": "billing/managing-your-github-billing-settings", "path_count": 2766}
-{"path_article": "pages/setting-up-a-github-pages-site-with-jekyll/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll", "path_count": 2761}
-{"path_article": "repositories/working-with-files/managing-files", "path_count": 2758}
-{"path_article": "packages/learn-github-packages/viewing-packages", "path_count": 2736}
-{"path_article": "code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-pull-requests-for-dependency-updates", "path_count": 2733}
-{"path_article": "rest/reference/meta", "path_count": 2727}
-{"path_article": "rest/guides/discovering-resources-for-a-user", "path_count": 2722}
-{"path_article": "repositories/working-with-files/managing-large-files/removing-files-from-git-large-file-storage", "path_count": 2711}
-{"path_article": "organizations/organizing-members-into-teams/adding-organization-members-to-a-team", "path_count": 2709}
-{"path_article": "developers/apps/getting-started-with-apps/differences-between-github-apps-and-oauth-apps", "path_count": 2707}
-{"path_article": "issues/tracking-your-work-with-issues/viewing-all-of-your-issues-and-pull-requests", "path_count": 2707}
-{"path_article": "get-started/using-github/exploring-early-access-releases-with-feature-preview", "path_count": 2706}
-{"path_article": "actions/using-workflows/creating-starter-workflows-for-your-organization", "path_count": 2693}
-{"path_article": "organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization", "path_count": 2684}
-{"path_article": "repositories/archiving-a-github-repository/backing-up-a-repository", "path_count": 2675}
-{"path_article": "organizations/organizing-members-into-teams/assigning-the-team-maintainer-role-to-a-team-member", "path_count": 2646}
-{"path_article": "rest/overview/openapi-description", "path_count": 2641}
-{"path_article": "pages/setting-up-a-github-pages-site-with-jekyll/about-jekyll-build-errors-for-github-pages-sites", "path_count": 2635}
-{"path_article": "organizations/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization", "path_count": 2619}
-{"path_article": "rest/guides/getting-started-with-the-git-database-api", "path_count": 2611}
-{"path_article": "communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file", "path_count": 2602}
-{"path_article": "developers/apps/building-github-apps", "path_count": 2601}
-{"path_article": "github/site-policy/guidelines-for-legal-requests-of-user-data", "path_count": 2600}
-{"path_article": "code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-dependabot-errors", "path_count": 2594}
-{"path_article": "actions/creating-actions/dockerfile-support-for-github-actions", "path_count": 2567}
-{"path_article": "account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-yourself-from-a-collaborators-repository", "path_count": 2556}
-{"path_article": "issues/organizing-your-work-with-project-boards/managing-project-boards/changing-project-board-visibility", "path_count": 2550}
-{"path_article": "rest/reference/deployments", "path_count": 2547}
-{"path_article": "get-started/getting-started-with-git/git-workflows", "path_count": 2547}
-{"path_article": "sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor", "path_count": 2539}
-{"path_article": "repositories/viewing-activity-and-data-for-your-repository/viewing-a-summary-of-repository-activity", "path_count": 2539}
-{"path_article": "developers/webhooks-and-events/webhooks/testing-webhooks", "path_count": 2537}
-{"path_article": "organizations/managing-membership-in-your-organization/removing-a-member-from-your-organization", "path_count": 2514}
-{"path_article": "developers/apps/building-oauth-apps", "path_count": 2488}
-{"path_article": "packages/learn-github-packages/connecting-a-repository-to-a-package", "path_count": 2487}
-{"path_article": "billing/managing-billing-for-github-actions/viewing-your-github-actions-usage", "path_count": 2486}
-{"path_article": "admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/about-enterprise-managed-users", "path_count": 2482}
-{"path_article": "actions/using-jobs/using-jobs-in-a-workflow", "path_count": 2480}
-{"path_article": "repositories/viewing-activity-and-data-for-your-repository/understanding-connections-between-repositories", "path_count": 2479}
-{"path_article": "graphql/guides/using-the-explorer", "path_count": 2467}
-{"path_article": "organizations/collaborating-with-groups-in-organizations/customizing-your-organizations-profile", "path_count": 2466}
-{"path_article": "actions/publishing-packages/about-packaging-with-github-actions", "path_count": 2461}
-{"path_article": "issues/using-labels-and-milestones-to-track-work/creating-and-editing-milestones-for-issues-and-pull-requests", "path_count": 2459}
-{"path_article": "actions/migrating-to-github-actions/migrating-from-jenkins-to-github-actions", "path_count": 2458}
-{"path_article": "actions/using-github-hosted-runners/customizing-github-hosted-runners", "path_count": 2458}
-{"path_article": "get-started/writing-on-github/working-with-advanced-formatting/creating-and-highlighting-code-blocks", "path_count": 2458}
-{"path_article": "issues/organizing-your-work-with-project-boards/managing-project-boards/deleting-a-project-board", "path_count": 2452}
-{"path_article": "actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups", "path_count": 2451}
-{"path_article": "issues/tracking-your-work-with-issues/deleting-an-issue", "path_count": 2451}
-{"path_article": "repositories/releasing-projects-on-github/linking-to-releases", "path_count": 2439}
-{"path_article": "billing/managing-your-github-billing-settings/adding-or-editing-a-payment-method", "path_count": 2438}
-{"path_article": "discussions/quickstart", "path_count": 2432}
-{"path_article": "pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts", "path_count": 2429}
-{"path_article": "actions/deployment/about-deployments/about-continuous-deployment", "path_count": 2429}
-{"path_article": "github/site-policy/github-private-information-removal-policy", "path_count": 2407}
-{"path_article": "repositories/viewing-activity-and-data-for-your-repository/viewing-a-projects-contributors", "path_count": 2401}
-{"path_article": "billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security", "path_count": 2394}
-{"path_article": "organizations/managing-peoples-access-to-your-organization-with-roles/maintaining-ownership-continuity-for-your-organization", "path_count": 2388}
-{"path_article": "pages/getting-started-with-github-pages/using-submodules-with-github-pages", "path_count": 2387}
-{"path_article": "billing/managing-billing-for-github-packages/about-billing-for-github-packages", "path_count": 2380}
-{"path_article": "rest/reference/markdown", "path_count": 2371}
-{"path_article": "code-security/getting-started/adding-a-security-policy-to-your-repository", "path_count": 2359}
-{"path_article": "actions/publishing-packages/publishing-java-packages-with-maven", "path_count": 2356}
-{"path_article": "pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork", "path_count": 2342}
-{"path_article": "developers/apps/building-github-apps/refreshing-user-to-server-access-tokens", "path_count": 2340}
-{"path_article": "issues/organizing-your-work-with-project-boards/managing-project-boards/about-automation-for-project-boards", "path_count": 2336}
-{"path_article": "github/site-policy/github-subprocessors-and-cookies", "path_count": 2330}
-{"path_article": "desktop/contributing-and-collaborating-using-github-desktop/keeping-your-local-repository-in-sync-with-github", "path_count": 2325}
-{"path_article": "desktop/contributing-and-collaborating-using-github-desktop", "path_count": 2317}
-{"path_article": "issues/organizing-your-work-with-project-boards", "path_count": 2309}
-{"path_article": "actions/migrating-to-github-actions/migrating-from-gitlab-cicd-to-github-actions", "path_count": 2299}
-{"path_article": "organizations/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization", "path_count": 2269}
-{"path_article": "github/copilot", "path_count": 2268}
-{"path_article": "get-started/learning-about-github/faq-about-changes-to-githubs-plans", "path_count": 2259}
-{"path_article": "github/site-policy/guide-to-submitting-a-dmca-takedown-notice", "path_count": 2254}
-{"path_article": "repositories/working-with-files/managing-large-files/moving-a-file-in-your-repository-to-git-large-file-storage", "path_count": 2254}
-{"path_article": "graphql/overview/schema-previews", "path_count": 2250}
-{"path_article": "issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-issues-and-pull-requests-to-a-project-board", "path_count": 2246}
-{"path_article": "packages/learn-github-packages/deleting-and-restoring-a-package", "path_count": 2233}
-{"path_article": "account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-a-collaborator-from-a-personal-repository", "path_count": 2232}
-{"path_article": "code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/browsing-security-vulnerabilities-in-the-github-advisory-database", "path_count": 2223}
-{"path_article": "graphql/reference/input-objects", "path_count": 2216}
-{"path_article": "organizations/managing-access-to-your-organizations-repositories/setting-base-permissions-for-an-organization", "path_count": 2198}
-{"path_article": "authentication/securing-your-account-with-two-factor-authentication-2fa/disabling-two-factor-authentication-for-your-personal-account", "path_count": 2194}
-{"path_article": "actions/deployment/deploying-to-your-cloud-provider/deploying-to-google-kubernetes-engine", "path_count": 2190}
-{"path_article": "rest/reference/code-scanning", "path_count": 2186}
-{"path_article": "github/site-policy/github-and-trade-controls", "path_count": 2177}
-{"path_article": "packages/learn-github-packages/installing-a-package", "path_count": 2166}
-{"path_article": "communities", "path_count": 2160}
-{"path_article": "account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/requesting-organization-approval-for-oauth-apps", "path_count": 2160}
-{"path_article": "get-started/learning-about-github/github-language-support", "path_count": 2160}
-{"path_article": "repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository", "path_count": 2160}
-{"path_article": "authentication/managing-commit-signature-verification/signing-tags", "path_count": 2157}
-{"path_article": "actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history", "path_count": 2141}
-{"path_article": "rest/reference/packages", "path_count": 2135}
-{"path_article": "pull-requests/committing-changes-to-your-project", "path_count": 2128}
-{"path_article": "organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization", "path_count": 2122}
-{"path_article": "authentication/troubleshooting-commit-signature-verification/checking-your-commit-and-tag-signature-verification-status", "path_count": 2118}
-{"path_article": "communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-issue-forms", "path_count": 2105}
-{"path_article": "desktop/installing-and-configuring-github-desktop/configuring-and-customizing-github-desktop/configuring-git-for-github-desktop", "path_count": 2101}
-{"path_article": "rest/reference/migrations", "path_count": 2100}
-{"path_article": "get-started/signing-up-for-github", "path_count": 2096}
-{"path_article": "account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences", "path_count": 2092}
-{"path_article": "get-started/exploring-projects-on-github/following-people", "path_count": 2091}
-{"path_article": "code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository", "path_count": 2088}
-{"path_article": "organizations/organizing-members-into-teams/managing-scheduled-reminders-for-your-team", "path_count": 2084}
-{"path_article": "rest/guides/best-practices-for-integrators", "path_count": 2050}
-{"path_article": "repositories/archiving-a-github-repository", "path_count": 2047}
-{"path_article": "billing/managing-billing-for-git-large-file-storage/about-billing-for-git-large-file-storage", "path_count": 2042}
-{"path_article": "organizations/managing-organization-settings/deleting-an-organization-account", "path_count": 2041}
-{"path_article": "code-security/security-advisories/about-github-security-advisories", "path_count": 2039}
-{"path_article": "billing/managing-billing-for-your-github-account/upgrading-your-github-subscription", "path_count": 2034}
-{"path_article": "github/importing-your-projects-to-github", "path_count": 2034}
-{"path_article": "account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/accessing-an-organization", "path_count": 2033}
-{"path_article": "issues/trying-out-the-new-projects-experience/best-practices-for-managing-projects", "path_count": 2021}
-{"path_article": "communities/setting-up-your-project-for-healthy-contributions/adding-a-code-of-conduct-to-your-project", "path_count": 2016}
-{"path_article": "admin/installation/setting-up-a-github-enterprise-server-instance", "path_count": 2014}
-{"path_article": "account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings", "path_count": 2005}
-{"path_article": "billing/managing-billing-for-github-actions", "path_count": 1997}
-{"path_article": "developers/apps/guides/using-the-github-api-in-your-app", "path_count": 1997}
-{"path_article": "repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/troubleshooting-required-status-checks", "path_count": 1994}
-{"path_article": "code-security/getting-started/securing-your-repository", "path_count": 1977}
-{"path_article": "repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/using-a-merge-queue", "path_count": 1973}
-{"path_article": "get-started/onboarding/getting-started-with-github-enterprise-cloud", "path_count": 1965}
-{"path_article": "desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/viewing-a-pull-request-in-github-desktop", "path_count": 1958}
-{"path_article": "github-cli/github-cli/quickstart", "path_count": 1951}
-{"path_article": "repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-auto-merge-for-pull-requests-in-your-repository", "path_count": 1947}
-{"path_article": "desktop/installing-and-configuring-github-desktop/overview/keyboard-shortcuts", "path_count": 1946}
-{"path_article": "code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql", "path_count": 1939}
-{"path_article": "communities/documenting-your-project-with-wikis", "path_count": 1936}
-{"path_article": "billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces", "path_count": 1928}
-{"path_article": "developers/apps/guides/creating-ci-tests-with-the-checks-api", "path_count": 1926}
-{"path_article": "actions/hosting-your-own-runners/using-labels-with-self-hosted-runners", "path_count": 1917}
-{"path_article": "pull-requests/collaborating-with-pull-requests/working-with-forks/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility", "path_count": 1901}
-{"path_article": "billing/managing-billing-for-github-actions/managing-your-spending-limit-for-github-actions", "path_count": 1897}
-{"path_article": "repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/about-email-notifications-for-pushes-to-your-repository", "path_count": 1875}
-{"path_article": "github/writing-on-github/working-with-advanced-formatting/using-keywords-in-issues-and-pull-requests", "path_count": 1872}
-{"path_article": "organizations/managing-organization-settings/restricting-repository-visibility-changes-in-your-organization", "path_count": 1861}
-{"path_article": "communities/using-templates-to-encourage-useful-issues-and-pull-requests/manually-creating-a-single-issue-template-for-your-repository", "path_count": 1860}
-{"path_article": "actions/managing-workflow-runs/skipping-workflow-runs", "path_count": 1853}
-{"path_article": "actions/creating-actions/publishing-actions-in-github-marketplace", "path_count": 1846}
-{"path_article": "billing/managing-billing-for-your-github-account/about-billing-for-github-accounts", "path_count": 1843}
-{"path_article": "account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/converting-a-user-into-an-organization", "path_count": 1840}
-{"path_article": "organizations/managing-organization-settings/transferring-organization-ownership", "path_count": 1834}
-{"path_article": "account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-organizations-profile", "path_count": 1834}
-{"path_article": "get-started/using-github/github-desktop", "path_count": 1827}
-{"path_article": "github/site-policy/guide-to-submitting-a-dmca-counter-notice", "path_count": 1825}
-{"path_article": "authentication/authenticating-with-saml-single-sign-on/viewing-and-managing-your-active-saml-sessions", "path_count": 1820}
-{"path_article": "github/copilot/about-github-copilot-telemetry", "path_count": 1815}
-{"path_article": "graphql/overview/resource-limitations", "path_count": 1813}
-{"path_article": "graphql/reference/enums", "path_count": 1799}
-{"path_article": "rest/reference/collaborators", "path_count": 1797}
-{"path_article": "authentication/troubleshooting-ssh/error-unknown-key-type", "path_count": 1794}
-{"path_article": "github/site-policy/github-data-protection-agreement", "path_count": 1792}
-{"path_article": "admin/policies/enforcing-policy-with-pre-receive-hooks/creating-a-pre-receive-hook-script", "path_count": 1787}
-{"path_article": "rest/guides/working-with-comments", "path_count": 1782}
-{"path_article": "desktop/installing-and-configuring-github-desktop/configuring-and-customizing-github-desktop/configuring-a-default-editor", "path_count": 1781}
-{"path_article": "education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research/apply-for-an-educator-or-researcher-discount", "path_count": 1773}
-{"path_article": "repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/customizing-your-repositorys-social-media-preview", "path_count": 1773}
-{"path_article": "search-github/getting-started-with-searching-on-github/sorting-search-results", "path_count": 1773}
-{"path_article": "billing/managing-billing-for-your-github-account", "path_count": 1770}
-{"path_article": "developers/overview/secret-scanning-partner-program", "path_count": 1767}
-{"path_article": "developers/webhooks-and-events", "path_count": 1758}
-{"path_article": "codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code", "path_count": 1758}
-{"path_article": "organizations/restricting-access-to-your-organizations-data/approving-oauth-apps-for-your-organization", "path_count": 1756}
-{"path_article": "issues/tracking-your-work-with-issues/quickstart", "path_count": 1751}
-{"path_article": "developers/apps/getting-started-with-apps/setting-up-your-development-environment-to-create-a-github-app", "path_count": 1746}
-{"path_article": "communities/documenting-your-project-with-wikis/creating-a-footer-or-sidebar-for-your-wiki", "path_count": 1744}
-{"path_article": "authentication/keeping-your-account-and-data-secure/reviewing-your-security-log", "path_count": 1743}
-{"path_article": "repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges", "path_count": 1739}
-{"path_article": "rest/overview/troubleshooting", "path_count": 1734}
-{"path_article": "organizations/collaborating-with-groups-in-organizations/about-your-organization-dashboard", "path_count": 1731}
-{"path_article": "actions/automating-builds-and-tests/building-and-testing-python", "path_count": 1730}
-{"path_article": "graphql/guides/migrating-from-rest-to-graphql", "path_count": 1728}
-{"path_article": "repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-repository-languages", "path_count": 1718}
-{"path_article": "codespaces/customizing-your-codespace/personalizing-codespaces-for-your-account", "path_count": 1716}
-{"path_article": "account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/removing-yourself-from-an-organization", "path_count": 1706}
-{"path_article": "github/extending-github/about-webhooks", "path_count": 1698}
-{"path_article": "actions/advanced-guides/using-github-cli-in-workflows", "path_count": 1684}
-{"path_article": "communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository", "path_count": 1677}
-{"path_article": "organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization", "path_count": 1668}
-{"path_article": "actions/using-workflows/using-starter-workflows", "path_count": 1668}
-{"path_article": "github/importing-your-projects-to-github/importing-source-code-to-github/about-github-importer", "path_count": 1665}
-{"path_article": "admin/configuration/configuring-your-enterprise/command-line-utilities", "path_count": 1654}
-{"path_article": "actions/hosting-your-own-runners/using-a-proxy-server-with-self-hosted-runners", "path_count": 1652}
-{"path_article": "pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/working-with-pre-receive-hooks", "path_count": 1651}
-{"path_article": "organizations/managing-peoples-access-to-your-organization-with-roles", "path_count": 1649}
-{"path_article": "search-github/getting-started-with-searching-on-github", "path_count": 1646}
-{"path_article": "actions/using-workflows/sharing-workflows-secrets-and-runners-with-your-organization", "path_count": 1641}
-{"path_article": "repositories/viewing-activity-and-data-for-your-repository/viewing-deployment-activity-for-your-repository", "path_count": 1639}
-{"path_article": "code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-encrypted-secrets-for-dependabot", "path_count": 1627}
-{"path_article": "actions/managing-workflow-runs/removing-workflow-artifacts", "path_count": 1627}
-{"path_article": "repositories/working-with-files/managing-large-files/collaboration-with-git-large-file-storage", "path_count": 1611}
-{"path_article": "organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities", "path_count": 1609}
-{"path_article": "desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop", "path_count": 1602}
-{"path_article": "billing/managing-billing-for-your-github-account/how-does-upgrading-or-downgrading-affect-the-billing-process", "path_count": 1597}
-{"path_article": "organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization", "path_count": 1585}
-{"path_article": "repositories/viewing-activity-and-data-for-your-repository/about-repository-graphs", "path_count": 1580}
-{"path_article": "actions/managing-issues-and-pull-requests/adding-labels-to-issues", "path_count": 1577}
-{"path_article": "developers/apps/managing-github-apps/editing-a-github-apps-permissions", "path_count": 1575}
-{"path_article": "sponsors/getting-started-with-github-sponsors/about-github-sponsors", "path_count": 1575}
-{"path_article": "admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server", "path_count": 1574}
-{"path_article": "codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces", "path_count": 1567}
-{"path_article": "issues/tracking-your-work-with-issues/transferring-an-issue-to-another-repository", "path_count": 1548}
-{"path_article": "desktop/contributing-and-collaborating-using-github-desktop/managing-commits/amending-a-commit", "path_count": 1545}
-{"path_article": "actions/hosting-your-own-runners/removing-self-hosted-runners", "path_count": 1529}
-{"path_article": "desktop/installing-and-configuring-github-desktop/overview/supported-operating-systems", "path_count": 1527}
-{"path_article": "actions/migrating-to-github-actions/migrating-from-azure-pipelines-to-github-actions", "path_count": 1519}
-{"path_article": "issues/trying-out-the-new-projects-experience/managing-the-visibility-of-your-projects", "path_count": 1518}
-{"path_article": "sponsors", "path_count": 1511}
-{"path_article": "get-started/using-git/about-git-subtree-merges", "path_count": 1507}
-{"path_article": "authentication/keeping-your-account-and-data-secure/authorizing-github-apps", "path_count": 1506}
-{"path_article": "actions/managing-workflow-runs/deleting-a-workflow-run", "path_count": 1503}
-{"path_article": "get-started/getting-started-with-git", "path_count": 1500}
-{"path_article": "pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/viewing-a-pull-request-review", "path_count": 1492}
-{"path_article": "education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork/why-wasnt-my-application-for-a-student-developer-pack-approved", "path_count": 1484}
-{"path_article": "repositories/releasing-projects-on-github/comparing-releases", "path_count": 1482}
-{"path_article": "authentication/keeping-your-account-and-data-secure/connecting-with-third-party-applications", "path_count": 1470}
-{"path_article": "github/importing-your-projects-to-github/importing-source-code-to-github", "path_count": 1465}
-{"path_article": "billing/managing-billing-for-git-large-file-storage/upgrading-git-large-file-storage", "path_count": 1461}
-{"path_article": "authentication/securing-your-account-with-two-factor-authentication-2fa/changing-two-factor-authentication-delivery-methods-for-your-mobile-device", "path_count": 1449}
-{"path_article": "authentication/troubleshooting-commit-signature-verification", "path_count": 1446}
-{"path_article": "admin/overview/about-github-ae", "path_count": 1445}
-{"path_article": "code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/keeping-your-actions-up-to-date-with-dependabot", "path_count": 1440}
-{"path_article": "developers/apps/getting-started-with-apps/activating-optional-features-for-apps", "path_count": 1439}
-{"path_article": "organizations/managing-access-to-your-organizations-project-boards/project-board-permissions-for-an-organization", "path_count": 1436}
-{"path_article": "repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-rebasing-for-pull-requests", "path_count": 1434}
-{"path_article": "desktop/installing-and-configuring-github-desktop/configuring-and-customizing-github-desktop/configuring-basic-settings", "path_count": 1431}
-{"path_article": "developers/webhooks-and-events/webhooks", "path_count": 1427}
-{"path_article": "admin/overview/creating-an-enterprise-account", "path_count": 1425}
-{"path_article": "actions/monitoring-and-troubleshooting-workflows/notifications-for-workflow-runs", "path_count": 1423}
-{"path_article": "actions/managing-workflow-runs/canceling-a-workflow", "path_count": 1419}
-{"path_article": "desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop/uninstalling-github-desktop", "path_count": 1416}
-{"path_article": "account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/types-of-emails-github-sends", "path_count": 1415}
-{"path_article": "get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-server", "path_count": 1412}
-{"path_article": "rest/reference/secret-scanning", "path_count": 1408}
-{"path_article": "organizations/restricting-access-to-your-organizations-data", "path_count": 1404}
-{"path_article": "code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-notifications-for-vulnerable-dependencies", "path_count": 1399}
-{"path_article": "organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization", "path_count": 1396}
-{"path_article": "github/importing-your-projects-to-github/importing-source-code-to-github/source-code-migration-tools", "path_count": 1383}
-{"path_article": "github/importing-your-projects-to-github/working-with-subversion-on-github/support-for-subversion-clients", "path_count": 1383}
-{"path_article": "graphql/reference/scalars", "path_count": 1378}
-{"path_article": "repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-git-lfs-objects-in-archives-of-your-repository", "path_count": 1372}
-{"path_article": "get-started/onboarding/getting-started-with-github-team", "path_count": 1370}
-{"path_article": "desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop/updating-github-desktop", "path_count": 1370}
-{"path_article": "education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-at-your-educational-institution/about-github-campus-program", "path_count": 1355}
-{"path_article": "admin/guides", "path_count": 1352}
-{"path_article": "pull-requests/committing-changes-to-your-project/troubleshooting-commits/commit-exists-on-github-but-not-in-my-local-clone", "path_count": 1349}
-{"path_article": "developers/apps/building-github-apps/creating-a-github-app-from-a-manifest", "path_count": 1347}
-{"path_article": "organizations/keeping-your-organization-secure", "path_count": 1339}
-{"path_article": "search-github/searching-on-github/searching-topics", "path_count": 1335}
-{"path_article": "actions/deployment/managing-your-deployments/viewing-deployment-history", "path_count": 1334}
-{"path_article": "github/understanding-how-github-uses-and-protects-your-data/about-githubs-use-of-your-data", "path_count": 1331}
-{"path_article": "issues/trying-out-the-new-projects-experience/managing-access-to-projects", "path_count": 1331}
-{"path_article": "communities/setting-up-your-project-for-healthy-contributions/about-community-profiles-for-public-repositories", "path_count": 1330}
-{"path_article": "developers/apps/building-github-apps/setting-permissions-for-github-apps", "path_count": 1327}
-{"path_article": "account-and-profile/setting-up-and-managing-your-github-user-account", "path_count": 1313}
-{"path_article": "account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/sending-enterprise-contributions-to-your-githubcom-profile", "path_count": 1312}
-{"path_article": "actions/automating-builds-and-tests/building-and-testing-nodejs", "path_count": 1312}
-{"path_article": "actions/migrating-to-github-actions/migrating-from-circleci-to-github-actions", "path_count": 1306}
-{"path_article": "search-github/searching-on-github/searching-in-forks", "path_count": 1305}
-{"path_article": "code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review", "path_count": 1302}
-{"path_article": "account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-access-to-your-user-accounts-project-boards", "path_count": 1298}
-{"path_article": "admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise", "path_count": 1297}
-{"path_article": "actions/publishing-packages/publishing-java-packages-with-gradle", "path_count": 1297}
-{"path_article": "authentication/troubleshooting-ssh/deleted-or-missing-ssh-keys", "path_count": 1283}
-{"path_article": "actions/monitoring-and-troubleshooting-workflows/using-the-visualization-graph", "path_count": 1283}
-{"path_article": "github/customizing-your-github-workflow/exploring-integrations/about-integrations", "path_count": 1277}
-{"path_article": "actions/deployment/deploying-xcode-applications/installing-an-apple-certificate-on-macos-runners-for-xcode-development", "path_count": 1277}
-{"path_article": "github/site-policy/github-candidate-privacy-policy", "path_count": 1273}
-{"path_article": "code-security/guides", "path_count": 1271}
-{"path_article": "account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile", "path_count": 1268}
-{"path_article": "admin/configuration/configuring-network-settings/configuring-tls", "path_count": 1265}
-{"path_article": "admin/user-management/managing-users-in-your-enterprise/suspending-and-unsuspending-users", "path_count": 1261}
-{"path_article": "billing/managing-your-github-billing-settings/viewing-your-subscriptions-and-billing-date", "path_count": 1256}
-{"path_article": "organizations/restricting-access-to-your-organizations-data/enabling-oauth-app-access-restrictions-for-your-organization", "path_count": 1247}
-{"path_article": "rest/reference/metrics", "path_count": 1237}
-{"path_article": "account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/viewing-peoples-roles-in-an-organization", "path_count": 1234}
-{"path_article": "developers/github-marketplace/github-marketplace-overview/about-marketplace-badges", "path_count": 1230}
-{"path_article": "actions/using-jobs/using-conditions-to-control-job-execution", "path_count": 1227}
-{"path_article": "admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-vmware", "path_count": 1214}
-{"path_article": "account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories", "path_count": 1214}
-{"path_article": "actions/creating-actions/releasing-and-maintaining-actions", "path_count": 1206}
-{"path_article": "repositories/viewing-activity-and-data-for-your-repository/analyzing-changes-to-a-repositorys-content", "path_count": 1203}
-{"path_article": "actions/automating-builds-and-tests/building-and-testing-powershell", "path_count": 1192}
-{"path_article": "billing/managing-billing-for-git-large-file-storage/viewing-your-git-large-file-storage-usage", "path_count": 1192}
-{"path_article": "admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise", "path_count": 1184}
-{"path_article": "account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-accessibility-settings", "path_count": 1182}
-{"path_article": "communities/documenting-your-project-with-wikis/changing-access-permissions-for-wikis", "path_count": 1180}
-{"path_article": "issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/archiving-cards-on-a-project-board", "path_count": 1179}
-{"path_article": "account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/managing-your-scheduled-reminders", "path_count": 1177}
-{"path_article": "desktop/installing-and-configuring-github-desktop/configuring-and-customizing-github-desktop/about-git-large-file-storage-and-github-desktop", "path_count": 1172}
-{"path_article": "repositories/working-with-files", "path_count": 1172}
-{"path_article": "pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests", "path_count": 1165}
-{"path_article": "account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/about-organization-membership", "path_count": 1165}
-{"path_article": "billing/managing-billing-for-git-large-file-storage", "path_count": 1158}
-{"path_article": "account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/best-practices-for-leaving-your-company", "path_count": 1157}
-{"path_article": "organizations/managing-organization-settings/setting-permissions-for-adding-outside-collaborators", "path_count": 1152}
-{"path_article": "billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account", "path_count": 1150}
-{"path_article": "rest/reference/licenses", "path_count": 1149}
-{"path_article": "admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-the-dependency-graph-and-dependabot-alerts-on-your-enterprise-account", "path_count": 1148}
-{"path_article": "rest/reference/scim", "path_count": 1146}
-{"path_article": "communities/moderating-comments-and-conversations/managing-disruptive-comments", "path_count": 1142}
-{"path_article": "repositories/creating-and-managing-repositories/creating-an-issues-only-repository", "path_count": 1138}
-{"path_article": "authentication/troubleshooting-ssh/error-ssh-add-illegal-option----k", "path_count": 1135}
-{"path_article": "developers/apps/managing-oauth-apps/troubleshooting-oauth-app-access-token-request-errors", "path_count": 1134}
-{"path_article": "account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/troubleshooting-commits-on-your-timeline", "path_count": 1133}
-{"path_article": "admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-aws", "path_count": 1131}
-{"path_article": "rest/guides/rendering-data-as-graphs", "path_count": 1130}
-{"path_article": "get-started/writing-on-github/working-with-advanced-formatting/organizing-information-with-tables", "path_count": 1129}
-{"path_article": "repositories/viewing-activity-and-data-for-your-repository", "path_count": 1129}
-{"path_article": "billing/managing-your-license-for-github-enterprise", "path_count": 1128}
-{"path_article": "admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise", "path_count": 1127}
-{"path_article": "rest/reference/oauth-authorizations", "path_count": 1122}
-{"path_article": "authentication/keeping-your-account-and-data-secure/reviewing-your-deploy-keys", "path_count": 1121}
-{"path_article": "admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise", "path_count": 1120}
-{"path_article": "rest/guides/building-a-ci-server", "path_count": 1118}
-{"path_article": "pull-requests/committing-changes-to-your-project/creating-and-editing-commits/about-commits", "path_count": 1116}
-{"path_article": "communities/using-templates-to-encourage-useful-issues-and-pull-requests", "path_count": 1114}
-{"path_article": "actions/using-jobs/using-a-build-matrix-for-your-jobs", "path_count": 1113}
-{"path_article": "rest/reference/pages", "path_count": 1107}
-{"path_article": "actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-cloud-providers", "path_count": 1098}
-{"path_article": "actions/using-containerized-services/creating-redis-service-containers", "path_count": 1098}
-{"path_article": "github/extending-github/getting-started-with-the-api", "path_count": 1096}
-{"path_article": "account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github", "path_count": 1095}
-{"path_article": "repositories/working-with-files/managing-large-files/resolving-git-large-file-storage-upload-failures", "path_count": 1087}
-{"path_article": "codespaces/setting-up-your-project-for-codespaces/setting-up-your-python-project-for-codespaces", "path_count": 1086}
-{"path_article": "authentication/keeping-your-account-and-data-secure/about-anonymized-urls", "path_count": 1078}
-{"path_article": "actions/using-jobs/choosing-the-runner-for-a-job", "path_count": 1076}
-{"path_article": "authentication/keeping-your-account-and-data-secure/reviewing-your-authorized-applications-oauth", "path_count": 1074}
-{"path_article": "get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github", "path_count": 1071}
-{"path_article": "code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow", "path_count": 1069}
-{"path_article": "communities/setting-up-your-project-for-healthy-contributions", "path_count": 1064}
-{"path_article": "developers/webhooks-and-events/events/issue-event-types", "path_count": 1064}
-{"path_article": "authentication/troubleshooting-ssh/error-permission-to-userrepo-denied-to-other-user", "path_count": 1064}
-{"path_article": "codespaces/setting-up-your-project-for-codespaces/setting-up-your-nodejs-project-for-codespaces", "path_count": 1061}
-{"path_article": "billing/managing-your-github-billing-settings/viewing-your-payment-history-and-receipts", "path_count": 1056}
-{"path_article": "organizations/managing-organization-settings", "path_count": 1045}
-{"path_article": "education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork/about-github-education-for-students", "path_count": 1041}
-{"path_article": "organizations/organizing-members-into-teams/removing-organization-members-from-a-team", "path_count": 1037}
-{"path_article": "actions/automating-builds-and-tests/building-and-testing-java-with-ant", "path_count": 1036}
-{"path_article": "search-github/searching-on-github/searching-for-packages", "path_count": 1032}
-{"path_article": "github/copilot/research-recitation", "path_count": 1031}
-{"path_article": "codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces", "path_count": 1030}
-{"path_article": "github/site-policy-deprecated/amendment-to-github-terms-of-service-applicable-to-us-federal-government-users", "path_count": 1025}
-{"path_article": "github/site-policy/github-sponsors-additional-terms", "path_count": 1024}
-{"path_article": "repositories/archiving-a-github-repository/about-archiving-content-and-data-on-github", "path_count": 1020}
-{"path_article": "discussions/collaborating-with-your-community-using-discussions/about-discussions", "path_count": 1019}
-{"path_article": "codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace", "path_count": 1010}
-{"path_article": "admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance", "path_count": 1010}
-{"path_article": "organizations/managing-saml-single-sign-on-for-your-organization/configuring-saml-single-sign-on-and-scim-using-okta", "path_count": 1010}
-{"path_article": "account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-security-and-analysis-settings-for-your-user-account", "path_count": 1008}
-{"path_article": "organizations/managing-organization-settings/upgrading-to-the-corporate-terms-of-service", "path_count": 1006}
-{"path_article": "get-started/using-git/dealing-with-special-characters-in-branch-and-tag-names", "path_count": 1004}
-{"path_article": "github/site-policy/github-deceased-user-policy", "path_count": 1001}
-{"path_article": "code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/customizing-dependency-updates", "path_count": 1000}
-{"path_article": "admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud", "path_count": 998}
-{"path_article": "education/manage-coursework-with-github-classroom/teach-with-github-classroom/connect-a-learning-management-system-to-github-classroom", "path_count": 996}
-{"path_article": "organizations/managing-organization-settings/managing-default-labels-for-repositories-in-your-organization", "path_count": 994}
-{"path_article": "actions/automating-builds-and-tests/building-and-testing-ruby", "path_count": 993}
-{"path_article": "admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-amazon-s3-storage", "path_count": 992}
-{"path_article": "communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-githubs-form-schema", "path_count": 991}
-{"path_article": "code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-managing-vulnerable-dependencies", "path_count": 991}
-{"path_article": "pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/filtering-files-in-a-pull-request", "path_count": 985}
-{"path_article": "repositories/releasing-projects-on-github", "path_count": 982}
-{"path_article": "admin/configuration/configuring-network-settings/network-ports", "path_count": 979}
-{"path_article": "desktop/installing-and-configuring-github-desktop/configuring-and-customizing-github-desktop/setting-a-theme-for-github-desktop", "path_count": 979}
-{"path_article": "communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization", "path_count": 975}
-{"path_article": "developers/github-marketplace/creating-apps-for-github-marketplace/requirements-for-listing-an-app", "path_count": 974}
-{"path_article": "github/site-policy-deprecated/github-enterprise-service-level-agreement", "path_count": 970}
-{"path_article": "rest/reference/repository-metrics", "path_count": 964}
-{"path_article": "communities/documenting-your-project-with-wikis/viewing-a-wikis-history-of-changes", "path_count": 963}
-{"path_article": "code-security/code-scanning/integrating-with-code-scanning/uploading-a-sarif-file-to-github", "path_count": 962}
-{"path_article": "graphql/guides/using-global-node-ids", "path_count": 962}
-{"path_article": "admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise", "path_count": 961}
-{"path_article": "code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning", "path_count": 961}
-{"path_article": "issues/tracking-your-work-with-issues/planning-and-tracking-work-for-your-team-or-project", "path_count": 954}
-{"path_article": "admin/authentication/managing-your-enterprise-users-with-your-identity-provider/configuring-saml-single-sign-on-for-enterprise-managed-users", "path_count": 954}
-{"path_article": "pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests", "path_count": 953}
-{"path_article": "actions/creating-actions/sharing-actions-and-workflows-with-your-enterprise", "path_count": 951}
-{"path_article": "organizations/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization", "path_count": 949}
-{"path_article": "issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-notes-to-a-project-board", "path_count": 948}
-{"path_article": "code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/upgrading-from-dependabotcom-to-github-native-dependabot", "path_count": 944}
-{"path_article": "pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request", "path_count": 941}
-{"path_article": "communities/moderating-comments-and-conversations/locking-conversations", "path_count": 939}
-{"path_article": "education/manage-coursework-with-github-classroom/teach-with-github-classroom/manage-classrooms", "path_count": 934}
-{"path_article": "admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise", "path_count": 932}
-{"path_article": "developers/apps/building-github-apps/managing-allowed-ip-addresses-for-a-github-app", "path_count": 930}
-{"path_article": "organizations/collaborating-with-groups-in-organizations/accessing-your-organizations-settings", "path_count": 926}
-{"path_article": "issues/organizing-your-work-with-project-boards/managing-project-boards/copying-a-project-board", "path_count": 925}
-{"path_article": "issues/organizing-your-work-with-project-boards/managing-project-boards/editing-a-project-board", "path_count": 922}
-{"path_article": "admin/overview/system-overview", "path_count": 917}
-{"path_article": "developers/apps/getting-started-with-apps", "path_count": 914}
-{"path_article": "rest/reference/reactions", "path_count": 912}
-{"path_article": "admin/user-management/monitoring-activity-in-your-enterprise/viewing-push-logs", "path_count": 910}
-{"path_article": "actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-google-cloud-platform", "path_count": 908}
-{"path_article": "admin/user-management/managing-users-in-your-enterprise/managing-dormant-users", "path_count": 902}
-{"path_article": "authentication/troubleshooting-ssh/error-ssl-certificate-problem-verify-that-the-ca-cert-is-ok", "path_count": 895}
-{"path_article": "admin/configuration/configuring-your-enterprise/accessing-the-administrative-shell-ssh", "path_count": 892}
-{"path_article": "developers/apps/managing-github-apps/making-a-github-app-public-or-private", "path_count": 887}
-{"path_article": "admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise", "path_count": 884}
-{"path_article": "admin/installation", "path_count": 877}
-{"path_article": "github/working-with-github-support/submitting-a-ticket", "path_count": 877}
-{"path_article": "billing/managing-billing-for-github-packages/viewing-your-github-packages-usage", "path_count": 876}
-{"path_article": "codespaces/setting-up-your-project-for-codespaces/setting-up-your-project-for-codespaces", "path_count": 874}
-{"path_article": "graphql/guides/managing-enterprise-accounts", "path_count": 867}
-{"path_article": "admin/user-management/managing-users-in-your-enterprise/managing-support-entitlements-for-your-enterprise", "path_count": 864}
-{"path_article": "repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/disabling-issues", "path_count": 863}
-{"path_article": "code-security/secret-scanning/configuring-secret-scanning-for-your-repositories", "path_count": 862}
-{"path_article": "get-started/writing-on-github/working-with-advanced-formatting/autolinked-references-and-urls", "path_count": 862}
-{"path_article": "support", "path_count": 858}
-{"path_article": "organizations/restricting-access-to-your-organizations-data/disabling-oauth-app-access-restrictions-for-your-organization", "path_count": 857}
-{"path_article": "admin/configuration/configuring-network-settings/configuring-a-hostname", "path_count": 850}
-{"path_article": "actions/using-jobs/using-environments-for-jobs", "path_count": 849}
-{"path_article": "github/writing-on-github/editing-and-sharing-content-with-gists/forking-and-cloning-gists", "path_count": 848}
-{"path_article": "code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-the-codeql-workflow-for-compiled-languages", "path_count": 848}
-{"path_article": "codespaces/developing-in-codespaces/developing-in-a-codespace", "path_count": 832}
-{"path_article": "admin/user-management/monitoring-activity-in-your-enterprise/audit-logging", "path_count": 832}
-{"path_article": "code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/listing-dependencies-configured-for-version-updates", "path_count": 829}
-{"path_article": "desktop/contributing-and-collaborating-using-github-desktop/adding-and-cloning-repositories", "path_count": 826}
-{"path_article": "admin/user-management/managing-organizations-in-your-enterprise/streaming-the-audit-logs-for-organizations-in-your-enterprise-account", "path_count": 820}
-{"path_article": "graphql/guides/using-the-graphql-api-for-discussions", "path_count": 819}
-{"path_article": "admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/using-ldap", "path_count": 818}
-{"path_article": "actions/using-jobs/running-jobs-in-a-container", "path_count": 817}
+{"path_article": "github/site-policy/github-terms-for-additional-products-and-features", "path_count": 5583}
+{"path_article": "communities/maintaining-your-safety-on-github/reporting-abuse-or-spam", "path_count": 5567}
+{"path_article": "developers/webhooks-and-events/webhooks/securing-your-webhooks", "path_count": 5558}
+{"path_article": "repositories/working-with-files/managing-large-files/about-storage-and-bandwidth-usage", "path_count": 5552}
+{"path_article": "actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-amazon-web-services", "path_count": 5538}
+{"path_article": "actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect", "path_count": 5487}
+{"path_article": "get-started/exploring-projects-on-github/saving-repositories-with-stars", "path_count": 5480}
+{"path_article": "account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/publicizing-or-hiding-your-private-contributions-on-your-profile", "path_count": 5478}
+{"path_article": "get-started/using-git", "path_count": 5472}
+{"path_article": "actions/using-containerized-services/about-service-containers", "path_count": 5430}
+{"path_article": "account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/viewing-your-subscriptions", "path_count": 5390}
+{"path_article": "graphql/guides/introduction-to-graphql", "path_count": 5369}
+{"path_article": "rest/reference/projects", "path_count": 5354}
+{"path_article": "issues/trying-out-the-new-projects-experience/quickstart", "path_count": 5305}
+{"path_article": "actions/using-workflows/using-starter-workflows", "path_count": 5277}
+{"path_article": "actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners", "path_count": 5268}
+{"path_article": "repositories/releasing-projects-on-github/viewing-your-repositorys-releases-and-tags", "path_count": 5259}
+{"path_article": "organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository", "path_count": 5220}
+{"path_article": "graphql/reference/queries", "path_count": 5213}
+{"path_article": "admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server", "path_count": 5187}
+{"path_article": "codespaces/overview", "path_count": 5130}
+{"path_article": "code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/about-dependabot-version-updates", "path_count": 5106}
+{"path_article": "repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/about-merge-methods-on-github", "path_count": 5104}
+{"path_article": "actions/automating-builds-and-tests/building-and-testing-java-with-maven", "path_count": 5042}
+{"path_article": "get-started/learning-about-github/about-versions-of-github-docs", "path_count": 5030}
+{"path_article": "rest/reference/enterprise-admin", "path_count": 4986}
+{"path_article": "actions/monitoring-and-troubleshooting-workflows/enabling-debug-logging", "path_count": 4969}
+{"path_article": "issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests", "path_count": 4962}
+{"path_article": "organizations/managing-organization-settings/restricting-repository-creation-in-your-organization", "path_count": 4926}
+{"path_article": "get-started/using-git/splitting-a-subfolder-out-into-a-new-repository", "path_count": 4911}
+{"path_article": "account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile", "path_count": 4909}
+{"path_article": "organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization", "path_count": 4907}
+{"path_article": "pull-requests/collaborating-with-pull-requests/getting-started/about-collaborative-development-models", "path_count": 4898}
+{"path_article": "rest/overview/media-types", "path_count": 4872}
+{"path_article": "issues/trying-out-the-new-projects-experience/creating-a-project", "path_count": 4851}
+{"path_article": "github/site-policy/github-corporate-terms-of-service", "path_count": 4795}
+{"path_article": "github/site-policy/submitting-content-removal-requests", "path_count": 4793}
+{"path_article": "get-started/using-git/using-git-rebase-on-the-command-line", "path_count": 4788}
+{"path_article": "search-github/searching-on-github", "path_count": 4787}
+{"path_article": "issues/organizing-your-work-with-project-boards/managing-project-boards/creating-a-project-board", "path_count": 4767}
+{"path_article": "developers/webhooks-and-events/webhooks/configuring-your-server-to-receive-payloads", "path_count": 4742}
+{"path_article": "actions/automating-builds-and-tests", "path_count": 4732}
+{"path_article": "search-github", "path_count": 4731}
+{"path_article": "account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/managing-your-subscriptions", "path_count": 4722}
+{"path_article": "repositories/working-with-files/managing-files/customizing-how-changed-files-appear-on-github", "path_count": 4721}
+{"path_article": "actions/using-workflows/sharing-workflows-secrets-and-runners-with-your-organization", "path_count": 4700}
+{"path_article": "github/site-policy/github-acceptable-use-policies", "path_count": 4676}
+{"path_article": "packages/learn-github-packages/configuring-a-packages-access-control-and-visibility", "path_count": 4636}
+{"path_article": "organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization", "path_count": 4632}
+{"path_article": "pages/setting-up-a-github-pages-site-with-jekyll/troubleshooting-jekyll-build-errors-for-github-pages-sites", "path_count": 4627}
+{"path_article": "repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-squashing-for-pull-requests", "path_count": 4600}
+{"path_article": "issues/trying-out-the-new-projects-experience/customizing-your-project-views", "path_count": 4595}
+{"path_article": "billing/managing-billing-for-your-github-account/downgrading-your-github-subscription", "path_count": 4594}
+{"path_article": "github/copilot/github-copilot-telemetry-terms", "path_count": 4574}
+{"path_article": "actions/using-jobs/using-a-build-matrix-for-your-jobs", "path_count": 4563}
+{"path_article": "packages/working-with-a-github-packages-registry", "path_count": 4562}
+{"path_article": "account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/about-your-personal-dashboard", "path_count": 4562}
+{"path_article": "github/site-policy/global-privacy-practices", "path_count": 4560}
+{"path_article": "communities/maintaining-your-safety-on-github/blocking-a-user-from-your-personal-account", "path_count": 4558}
+{"path_article": "desktop/installing-and-configuring-github-desktop/overview/creating-your-first-repository-using-github-desktop", "path_count": 4552}
+{"path_article": "authentication/keeping-your-account-and-data-secure/token-expiration-and-revocation", "path_count": 4549}
+{"path_article": "actions/managing-workflow-runs/disabling-and-enabling-a-workflow", "path_count": 4527}
+{"path_article": "rest/reference/webhooks", "path_count": 4478}
+{"path_article": "actions/managing-workflow-runs/downloading-workflow-artifacts", "path_count": 4427}
+{"path_article": "issues/organizing-your-work-with-project-boards/managing-project-boards/configuring-automation-for-project-boards", "path_count": 4415}
+{"path_article": "actions/using-jobs/using-conditions-to-control-job-execution", "path_count": 4405}
+{"path_article": "pages/getting-started-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site", "path_count": 4380}
+{"path_article": "get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud", "path_count": 4354}
+{"path_article": "developers/apps/building-github-apps/rate-limits-for-github-apps", "path_count": 4344}
+{"path_article": "code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning", "path_count": 4337}
+{"path_article": "pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/dismissing-a-pull-request-review", "path_count": 4305}
+{"path_article": "rest/overview/endpoints-available-for-github-apps", "path_count": 4303}
+{"path_article": "developers/github-marketplace", "path_count": 4295}
+{"path_article": "desktop/contributing-and-collaborating-using-github-desktop/adding-and-cloning-repositories/adding-an-existing-project-to-github-using-github-desktop", "path_count": 4290}
+{"path_article": "rest/guides/getting-started-with-the-checks-api", "path_count": 4275}
+{"path_article": "packages/quickstart", "path_count": 4255}
+{"path_article": "sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account", "path_count": 4254}
+{"path_article": "repositories/archiving-a-github-repository/referencing-and-citing-content", "path_count": 4232}
+{"path_article": "rest/overview/api-previews", "path_count": 4210}
+{"path_article": "issues/using-labels-and-milestones-to-track-work/about-milestones", "path_count": 4209}
+{"path_article": "account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings", "path_count": 4195}
+{"path_article": "get-started/writing-on-github/working-with-advanced-formatting", "path_count": 4181}
+{"path_article": "rest/reference/gists", "path_count": 4180}
+{"path_article": "actions/using-jobs/using-concurrency", "path_count": 4176}
+{"path_article": "actions/deployment/deploying-to-your-cloud-provider/deploying-to-amazon-elastic-container-service", "path_count": 4171}
+{"path_article": "account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications", "path_count": 4157}
+{"path_article": "get-started/writing-on-github/working-with-advanced-formatting/organizing-information-with-collapsed-sections", "path_count": 4144}
+{"path_article": "billing/managing-billing-for-your-github-account/about-per-user-pricing", "path_count": 4138}
+{"path_article": "actions/creating-actions/setting-exit-codes-for-actions", "path_count": 4117}
+{"path_article": "developers/overview/about-githubs-apis", "path_count": 4096}
+{"path_article": "desktop/installing-and-configuring-github-desktop/overview/launching-github-desktop-from-the-command-line", "path_count": 4079}
+{"path_article": "education", "path_count": 4068}
+{"path_article": "repositories/archiving-a-github-repository/archiving-repositories", "path_count": 4041}
+{"path_article": "rest/reference/rate-limit", "path_count": 4024}
+{"path_article": "rest/guides/delivering-deployments", "path_count": 4019}
+{"path_article": "actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners", "path_count": 4013}
+{"path_article": "rest/guides/traversing-with-pagination", "path_count": 3988}
+{"path_article": "organizations/organizing-members-into-teams/creating-a-team", "path_count": 3975}
+{"path_article": "github/site-policy/github-trademark-policy", "path_count": 3952}
+{"path_article": "get-started/quickstart/communicating-on-github", "path_count": 3922}
+{"path_article": "actions/managing-workflow-runs/reviewing-deployments", "path_count": 3916}
+{"path_article": "repositories/working-with-files/using-files/getting-permanent-links-to-files", "path_count": 3907}
+{"path_article": "actions/using-containerized-services/creating-postgresql-service-containers", "path_count": 3869}
+{"path_article": "organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/restricting-email-notifications-for-your-organization", "path_count": 3863}
+{"path_article": "pull-requests/collaborating-with-pull-requests", "path_count": 3856}
+{"path_article": "actions/monitoring-and-troubleshooting-workflows/using-workflow-run-logs", "path_count": 3850}
+{"path_article": "rest/reference/deployments", "path_count": 3756}
+{"path_article": "repositories/working-with-files/managing-files", "path_count": 3750}
+{"path_article": "packages/working-with-a-github-packages-registry/working-with-the-rubygems-registry", "path_count": 3745}
+{"path_article": "graphql/reference/mutations", "path_count": 3744}
+{"path_article": "get-started/using-github/github-command-palette", "path_count": 3741}
+{"path_article": "organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-allowed-ip-addresses-for-your-organization", "path_count": 3740}
+{"path_article": "authentication/troubleshooting-ssh/error-key-already-in-use", "path_count": 3735}
+{"path_article": "packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry", "path_count": 3735}
+{"path_article": "desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/stashing-changes", "path_count": 3724}
+{"path_article": "admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrade-requirements", "path_count": 3713}
+{"path_article": "code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/automating-dependabot-with-github-actions", "path_count": 3678}
+{"path_article": "account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/showing-an-overview-of-your-activity-on-your-profile", "path_count": 3648}
+{"path_article": "authentication/keeping-your-account-and-data-secure/reviewing-your-authorized-integrations", "path_count": 3644}
+{"path_article": "actions/using-jobs/choosing-the-runner-for-a-job", "path_count": 3633}
+{"path_article": "pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/about-merge-conflicts", "path_count": 3631}
+{"path_article": "repositories/working-with-files/managing-large-files/removing-files-from-git-large-file-storage", "path_count": 3605}
+{"path_article": "packages/working-with-a-github-packages-registry/working-with-the-gradle-registry", "path_count": 3605}
+{"path_article": "actions/automating-builds-and-tests/building-and-testing-net", "path_count": 3599}
+{"path_article": "codespaces/developing-in-codespaces/creating-a-codespace", "path_count": 3597}
+{"path_article": "issues/tracking-your-work-with-issues/assigning-issues-and-pull-requests-to-other-github-users", "path_count": 3594}
+{"path_article": "actions/managing-workflow-runs/re-running-workflows-and-jobs", "path_count": 3571}
+{"path_article": "code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-dependabot-errors", "path_count": 3570}
+{"path_article": "issues/organizing-your-work-with-project-boards/managing-project-boards/linking-a-repository-to-a-project-board", "path_count": 3564}
+{"path_article": "pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/incorporating-feedback-in-your-pull-request", "path_count": 3558}
+{"path_article": "organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on", "path_count": 3553}
+{"path_article": "admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise", "path_count": 3548}
+{"path_article": "account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/publicizing-or-hiding-organization-membership", "path_count": 3540}
+{"path_article": "admin/overview/about-upgrades-to-new-releases", "path_count": 3533}
+{"path_article": "repositories/working-with-files/using-files/viewing-a-file", "path_count": 3523}
+{"path_article": "graphql/overview/about-the-graphql-api", "path_count": 3510}
+{"path_article": "actions/automating-builds-and-tests/building-and-testing-java-with-gradle", "path_count": 3502}
+{"path_article": "repositories/archiving-a-github-repository/backing-up-a-repository", "path_count": 3497}
+{"path_article": "rest/guides/discovering-resources-for-a-user", "path_count": 3478}
+{"path_article": "code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository", "path_count": 3453}
+{"path_article": "issues/trying-out-the-new-projects-experience/automating-projects", "path_count": 3441}
+{"path_article": "graphql/overview/public-schema", "path_count": 3425}
+{"path_article": "communities/documenting-your-project-with-wikis/editing-wiki-content", "path_count": 3424}
+{"path_article": "organizations/managing-organization-settings/renaming-an-organization", "path_count": 3423}
+{"path_article": "packages/learn-github-packages/publishing-a-package", "path_count": 3423}
+{"path_article": "codespaces/getting-started/deep-dive", "path_count": 3412}
+{"path_article": "organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/requiring-two-factor-authentication-in-your-organization", "path_count": 3394}
+{"path_article": "account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/pinning-items-to-your-profile", "path_count": 3367}
+{"path_article": "organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization", "path_count": 3361}
+{"path_article": "code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/viewing-and-updating-vulnerable-dependencies-in-your-repository", "path_count": 3351}
+{"path_article": "billing/managing-billing-for-github-actions/viewing-your-github-actions-usage", "path_count": 3320}
+{"path_article": "issues/trying-out-the-new-projects-experience/using-the-api-to-manage-projects", "path_count": 3310}
+{"path_article": "pull-requests/collaborating-with-pull-requests/working-with-forks/allowing-changes-to-a-pull-request-branch-created-from-a-fork", "path_count": 3305}
+{"path_article": "get-started/getting-started-with-git/git-workflows", "path_count": 3297}
+{"path_article": "get-started/using-github/github-cli", "path_count": 3282}
+{"path_article": "graphql/reference/interfaces", "path_count": 3280}
+{"path_article": "developers/apps/getting-started-with-apps/differences-between-github-apps-and-oauth-apps", "path_count": 3261}
+{"path_article": "actions/creating-actions/dockerfile-support-for-github-actions", "path_count": 3247}
+{"path_article": "actions/managing-workflow-runs", "path_count": 3245}
+{"path_article": "issues/tracking-your-work-with-issues/viewing-all-of-your-issues-and-pull-requests", "path_count": 3235}
+{"path_article": "code-security/supply-chain-security/keeping-your-dependencies-updated-automatically", "path_count": 3233}
+{"path_article": "github/site-policy/guide-to-submitting-a-dmca-takedown-notice", "path_count": 3196}
+{"path_article": "communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file", "path_count": 3170}
+{"path_article": "get-started/writing-on-github/working-with-advanced-formatting/creating-diagrams", "path_count": 3169}
+{"path_article": "organizations/organizing-members-into-teams/adding-organization-members-to-a-team", "path_count": 3158}
+{"path_article": "github/site-policy/github-username-policy", "path_count": 3145}
+{"path_article": "issues/organizing-your-work-with-project-boards/managing-project-boards/changing-project-board-visibility", "path_count": 3138}
+{"path_article": "rest/reference/meta", "path_count": 3127}
+{"path_article": "packages/learn-github-packages", "path_count": 3113}
+{"path_article": "actions/migrating-to-github-actions/migrating-from-jenkins-to-github-actions", "path_count": 3111}
+{"path_article": "rest/guides/getting-started-with-the-git-database-api", "path_count": 3098}
+{"path_article": "desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop/setting-up-github-desktop", "path_count": 3096}
+{"path_article": "actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups", "path_count": 3063}
+{"path_article": "repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-autolinks-to-reference-external-resources", "path_count": 3061}
+{"path_article": "organizations/organizing-members-into-teams/assigning-the-team-maintainer-role-to-a-team-member", "path_count": 3059}
+{"path_article": "actions/using-jobs/running-jobs-in-a-container", "path_count": 3048}
+{"path_article": "organizations/managing-membership-in-your-organization/adding-people-to-your-organization", "path_count": 3046}
+{"path_article": "github/site-policy/github-open-source-applications-terms-and-conditions", "path_count": 3042}
+{"path_article": "rest/overview/openapi-description", "path_count": 3033}
+{"path_article": "repositories/viewing-activity-and-data-for-your-repository/viewing-a-projects-contributors", "path_count": 3019}
+{"path_article": "github/site-policy/guidelines-for-legal-requests-of-user-data", "path_count": 3015}
+{"path_article": "repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/displaying-a-sponsor-button-in-your-repository", "path_count": 3012}
+{"path_article": "billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security", "path_count": 3008}
+{"path_article": "account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/blocking-command-line-pushes-that-expose-your-personal-email-address", "path_count": 3006}
+{"path_article": "actions/guides", "path_count": 2989}
+{"path_article": "graphql/guides/using-the-explorer", "path_count": 2968}
+{"path_article": "code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-pull-requests-for-dependency-updates", "path_count": 2965}
+{"path_article": "developers/webhooks-and-events/webhooks/testing-webhooks", "path_count": 2955}
+{"path_article": "repositories/viewing-activity-and-data-for-your-repository/viewing-traffic-to-a-repository", "path_count": 2950}
+{"path_article": "rest/guides", "path_count": 2932}
+{"path_article": "pages/setting-up-a-github-pages-site-with-jekyll/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll", "path_count": 2926}
+{"path_article": "graphql/reference/input-objects", "path_count": 2926}
+{"path_article": "packages/learn-github-packages/viewing-packages", "path_count": 2911}
+{"path_article": "pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts", "path_count": 2907}
+{"path_article": "rest/reference/code-scanning", "path_count": 2900}
+{"path_article": "packages/learn-github-packages/connecting-a-repository-to-a-package", "path_count": 2892}
+{"path_article": "organizations/managing-access-to-your-organizations-repositories", "path_count": 2889}
+{"path_article": "issues/tracking-your-work-with-issues/deleting-an-issue", "path_count": 2880}
+{"path_article": "organizations/collaborating-with-groups-in-organizations", "path_count": 2842}
+{"path_article": "get-started/using-github/exploring-early-access-releases-with-feature-preview", "path_count": 2842}
+{"path_article": "rest/reference/markdown", "path_count": 2827}
+{"path_article": "account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/managing-notifications-from-your-inbox", "path_count": 2822}
+{"path_article": "pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork", "path_count": 2820}
+{"path_article": "organizations/managing-membership-in-your-organization/removing-a-member-from-your-organization", "path_count": 2814}
+{"path_article": "organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization", "path_count": 2813}
+{"path_article": "repositories/managing-your-repositorys-settings-and-features", "path_count": 2803}
+{"path_article": "repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-forking-policy-for-your-repository", "path_count": 2801}
+{"path_article": "repositories/working-with-files/managing-large-files/moving-a-file-in-your-repository-to-git-large-file-storage", "path_count": 2788}
+{"path_article": "support", "path_count": 2787}
+{"path_article": "admin/all-releases", "path_count": 2780}
+{"path_article": "actions/deployment/about-deployments/about-continuous-deployment", "path_count": 2779}
+{"path_article": "billing/managing-your-github-billing-settings", "path_count": 2773}
+{"path_article": "actions/migrating-to-github-actions/migrating-from-gitlab-cicd-to-github-actions", "path_count": 2770}
+{"path_article": "organizations/organizing-members-into-teams/managing-scheduled-reminders-for-your-team", "path_count": 2766}
+{"path_article": "repositories/releasing-projects-on-github/linking-to-releases", "path_count": 2758}
+{"path_article": "actions/publishing-packages/about-packaging-with-github-actions", "path_count": 2754}
+{"path_article": "actions/using-github-hosted-runners/customizing-github-hosted-runners", "path_count": 2754}
+{"path_article": "github/site-policy/guide-to-submitting-a-dmca-counter-notice", "path_count": 2742}
+{"path_article": "get-started/importing-your-projects-to-github/importing-source-code-to-github/about-github-importer", "path_count": 2737}
+{"path_article": "desktop/contributing-and-collaborating-using-github-desktop/keeping-your-local-repository-in-sync-with-github", "path_count": 2729}
+{"path_article": "billing/managing-billing-for-github-packages/about-billing-for-github-packages", "path_count": 2724}
+{"path_article": "organizations/managing-access-to-your-organizations-repositories/setting-base-permissions-for-an-organization", "path_count": 2704}
+{"path_article": "repositories/viewing-activity-and-data-for-your-repository/viewing-a-summary-of-repository-activity", "path_count": 2701}
+{"path_article": "issues/using-labels-and-milestones-to-track-work/creating-and-editing-milestones-for-issues-and-pull-requests", "path_count": 2699}
+{"path_article": "actions/managing-workflow-runs/skipping-workflow-runs", "path_count": 2694}
+{"path_article": "repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/using-a-merge-queue", "path_count": 2677}
+{"path_article": "code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository", "path_count": 2664}
+{"path_article": "developers/apps/building-oauth-apps", "path_count": 2649}
+{"path_article": "developers/apps/building-github-apps/refreshing-user-to-server-access-tokens", "path_count": 2646}
+{"path_article": "billing/managing-your-github-billing-settings/about-billing-on-github", "path_count": 2642}
+{"path_article": "github/site-policy/github-private-information-removal-policy", "path_count": 2638}
+{"path_article": "issues/organizing-your-work-with-project-boards/managing-project-boards/deleting-a-project-board", "path_count": 2636}
+{"path_article": "rest/reference/migrations", "path_count": 2635}
+{"path_article": "developers/apps/building-github-apps", "path_count": 2633}
+{"path_article": "code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/browsing-security-vulnerabilities-in-the-github-advisory-database", "path_count": 2629}
+{"path_article": "code-security/getting-started/github-security-features", "path_count": 2612}
+{"path_article": "github/copilot", "path_count": 2607}
+{"path_article": "developers/apps/guides/using-the-github-api-in-your-app", "path_count": 2606}
+{"path_article": "repositories/viewing-activity-and-data-for-your-repository/understanding-connections-between-repositories", "path_count": 2604}
+{"path_article": "code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql", "path_count": 2602}
+{"path_article": "organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization", "path_count": 2592}
+{"path_article": "organizations/managing-peoples-access-to-your-organization-with-roles/maintaining-ownership-continuity-for-your-organization", "path_count": 2587}
+{"path_article": "billing/managing-billing-for-github-actions/managing-your-spending-limit-for-github-actions", "path_count": 2587}
+{"path_article": "github/site-policy/github-subprocessors-and-cookies", "path_count": 2586}
+{"path_article": "actions/publishing-packages/publishing-java-packages-with-maven", "path_count": 2553}
+{"path_article": "authentication/troubleshooting-commit-signature-verification/checking-your-commit-and-tag-signature-verification-status", "path_count": 2548}
+{"path_article": "issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-issues-and-pull-requests-to-a-project-board", "path_count": 2525}
+{"path_article": "get-started/learning-about-github/github-language-support", "path_count": 2519}
+{"path_article": "authentication/managing-commit-signature-verification/signing-tags", "path_count": 2519}
+{"path_article": "pages/getting-started-with-github-pages/using-submodules-with-github-pages", "path_count": 2516}
+{"path_article": "organizations/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization", "path_count": 2513}
+{"path_article": "get-started/onboarding/getting-started-with-github-enterprise-cloud", "path_count": 2506}
+{"path_article": "rest/guides/working-with-comments", "path_count": 2503}
+{"path_article": "packages/learn-github-packages/deleting-and-restoring-a-package", "path_count": 2498}
+{"path_article": "billing/managing-billing-for-your-github-account/upgrading-your-github-subscription", "path_count": 2493}
+{"path_article": "organizations/collaborating-with-groups-in-organizations/customizing-your-organizations-profile", "path_count": 2491}
+{"path_article": "github/site-policy/github-and-trade-controls", "path_count": 2481}
+{"path_article": "repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/troubleshooting-required-status-checks", "path_count": 2480}
+{"path_article": "rest/guides/best-practices-for-integrators", "path_count": 2479}
+{"path_article": "discussions/quickstart", "path_count": 2477}
+{"path_article": "developers/overview", "path_count": 2475}
+{"path_article": "packages/learn-github-packages/installing-a-package", "path_count": 2474}
+{"path_article": "organizations/managing-organization-settings/deleting-an-organization-account", "path_count": 2473}
+{"path_article": "developers/apps/guides/creating-ci-tests-with-the-checks-api", "path_count": 2470}
+{"path_article": "account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/requesting-organization-approval-for-oauth-apps", "path_count": 2458}
+{"path_article": "communities/setting-up-your-project-for-healthy-contributions/adding-a-code-of-conduct-to-your-project", "path_count": 2451}
+{"path_article": "actions/using-jobs/using-environments-for-jobs", "path_count": 2448}
+{"path_article": "desktop/installing-and-configuring-github-desktop/configuring-and-customizing-github-desktop/configuring-git-for-github-desktop", "path_count": 2431}
+{"path_article": "graphql/overview/schema-previews", "path_count": 2430}
+{"path_article": "rest/reference/metrics", "path_count": 2425}
+{"path_article": "code-security/getting-started/securing-your-repository", "path_count": 2422}
+{"path_article": "account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-a-collaborator-from-a-personal-repository", "path_count": 2415}
+{"path_article": "organizations/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization", "path_count": 2412}
+{"path_article": "rest/reference/packages", "path_count": 2399}
+{"path_article": "admin/installation/setting-up-a-github-enterprise-server-instance", "path_count": 2397}
+{"path_article": "repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-auto-merge-for-pull-requests-in-your-repository", "path_count": 2391}
+{"path_article": "admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server", "path_count": 2391}
+{"path_article": "desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/viewing-a-pull-request-in-github-desktop", "path_count": 2385}
+{"path_article": "communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-issue-forms", "path_count": 2363}
+{"path_article": "organizations/managing-organization-settings/restricting-repository-visibility-changes-in-your-organization", "path_count": 2359}
+{"path_article": "rest/reference/collaborators", "path_count": 2356}
+{"path_article": "pages/setting-up-a-github-pages-site-with-jekyll/about-jekyll-build-errors-for-github-pages-sites", "path_count": 2354}
+{"path_article": "repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/about-email-notifications-for-pushes-to-your-repository", "path_count": 2350}
+{"path_article": "billing/managing-your-github-billing-settings/adding-or-editing-a-payment-method", "path_count": 2348}
+{"path_article": "actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history", "path_count": 2324}
+{"path_article": "organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization", "path_count": 2316}
+{"path_article": "actions/deployment/deploying-to-your-cloud-provider/deploying-to-google-kubernetes-engine", "path_count": 2312}
+{"path_article": "code-security/getting-started/adding-a-security-policy-to-your-repository", "path_count": 2302}
+{"path_article": "actions/using-jobs/defining-outputs-for-jobs", "path_count": 2301}
+{"path_article": "organizations/restricting-access-to-your-organizations-data/approving-oauth-apps-for-your-organization", "path_count": 2277}
+{"path_article": "actions/hosting-your-own-runners/using-labels-with-self-hosted-runners", "path_count": 2275}
+{"path_article": "pull-requests/collaborating-with-pull-requests/working-with-forks/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility", "path_count": 2269}
+{"path_article": "repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-repository-languages", "path_count": 2265}
+{"path_article": "actions/using-jobs", "path_count": 2259}
+{"path_article": "github/site-policy/github-data-protection-agreement", "path_count": 2259}
+{"path_article": "desktop/contributing-and-collaborating-using-github-desktop", "path_count": 2247}
+{"path_article": "desktop/installing-and-configuring-github-desktop/overview/keyboard-shortcuts", "path_count": 2226}
+{"path_article": "account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/accessing-an-organization", "path_count": 2223}
+{"path_article": "admin/policies/enforcing-policy-with-pre-receive-hooks/creating-a-pre-receive-hook-script", "path_count": 2212}
+{"path_article": "billing/managing-billing-for-github-actions", "path_count": 2201}
+{"path_article": "developers/apps/getting-started-with-apps/setting-up-your-development-environment-to-create-a-github-app", "path_count": 2181}
+{"path_article": "search-github/getting-started-with-searching-on-github/sorting-search-results", "path_count": 2181}
+{"path_article": "get-started/learning-about-github/faq-about-changes-to-githubs-plans", "path_count": 2179}
+{"path_article": "repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges", "path_count": 2177}
+{"path_article": "account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-yourself-from-a-collaborators-repository", "path_count": 2167}
+{"path_article": "communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository", "path_count": 2157}
+{"path_article": "communities/documenting-your-project-with-wikis", "path_count": 2147}
+{"path_article": "graphql/reference/enums", "path_count": 2141}
+{"path_article": "account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences", "path_count": 2130}
+{"path_article": "repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-citation-files", "path_count": 2127}
+{"path_article": "actions/creating-actions/publishing-actions-in-github-marketplace", "path_count": 2110}
+{"path_article": "authentication/troubleshooting-ssh/error-agent-admitted-failure-to-sign", "path_count": 2103}
+{"path_article": "billing/managing-billing-for-git-large-file-storage/about-billing-for-git-large-file-storage", "path_count": 2093}
+{"path_article": "actions/hosting-your-own-runners/using-a-proxy-server-with-self-hosted-runners", "path_count": 2093}
+{"path_article": "get-started/using-github/github-desktop", "path_count": 2091}
+{"path_article": "repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository", "path_count": 2082}
+{"path_article": "get-started/exploring-projects-on-github/following-people", "path_count": 2081}
+{"path_article": "github-cli/github-cli/quickstart", "path_count": 2074}
+{"path_article": "codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces", "path_count": 2058}
+{"path_article": "organizations/managing-organization-settings/transferring-organization-ownership", "path_count": 2052}
+{"path_article": "communities/using-templates-to-encourage-useful-issues-and-pull-requests/manually-creating-a-single-issue-template-for-your-repository", "path_count": 2047}
+{"path_article": "authentication/troubleshooting-ssh/error-unknown-key-type", "path_count": 2040}
+{"path_article": "billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces", "path_count": 2035}
+{"path_article": "admin/configuration/configuring-your-enterprise/command-line-utilities", "path_count": 2034}
+{"path_article": "issues/organizing-your-work-with-project-boards", "path_count": 2026}
+{"path_article": "account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-organizations-profile", "path_count": 2026}
+{"path_article": "authentication/keeping-your-account-and-data-secure/reviewing-your-security-log", "path_count": 2024}
+{"path_article": "authentication/securing-your-account-with-two-factor-authentication-2fa/disabling-two-factor-authentication-for-your-personal-account", "path_count": 2014}
+{"path_article": "pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/working-with-pre-receive-hooks", "path_count": 2012}
+{"path_article": "repositories/working-with-files/managing-large-files/collaboration-with-git-large-file-storage", "path_count": 2005}
+{"path_article": "codespaces/customizing-your-codespace/personalizing-codespaces-for-your-account", "path_count": 2004}
+{"path_article": "get-started/customizing-your-github-workflow/exploring-integrations/about-webhooks", "path_count": 2003}
+{"path_article": "education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research/apply-for-an-educator-or-researcher-discount", "path_count": 2000}
+{"path_article": "support/contacting-github-support/creating-a-support-ticket", "path_count": 1996}
+{"path_article": "issues/tracking-your-work-with-issues/transferring-an-issue-to-another-repository", "path_count": 1985}
+{"path_article": "rest/overview/troubleshooting", "path_count": 1984}
+{"path_article": "graphql/overview/resource-limitations", "path_count": 1975}
+{"path_article": "desktop/installing-and-configuring-github-desktop/configuring-and-customizing-github-desktop/configuring-a-default-editor", "path_count": 1973}
+{"path_article": "desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop", "path_count": 1943}
+{"path_article": "account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/removing-yourself-from-an-organization", "path_count": 1940}
+{"path_article": "code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-encrypted-secrets-for-dependabot", "path_count": 1938}
+{"path_article": "issues/trying-out-the-new-projects-experience/best-practices-for-managing-projects", "path_count": 1937}
+{"path_article": "communities/documenting-your-project-with-wikis/creating-a-footer-or-sidebar-for-your-wiki", "path_count": 1933}
+{"path_article": "actions/managing-issues-and-pull-requests/adding-labels-to-issues", "path_count": 1932}
+{"path_article": "pull-requests/committing-changes-to-your-project", "path_count": 1911}
+{"path_article": "codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code", "path_count": 1857}
+{"path_article": "repositories/viewing-activity-and-data-for-your-repository/about-repository-graphs", "path_count": 1849}
+{"path_article": "support/learning-about-github-support/about-github-support", "path_count": 1845}
+{"path_article": "developers/apps/managing-github-apps/editing-a-github-apps-permissions", "path_count": 1842}
+{"path_article": "admin/overview/about-github-ae", "path_count": 1838}
+{"path_article": "organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization", "path_count": 1837}
+{"path_article": "authentication/keeping-your-account-and-data-secure/authorizing-github-apps", "path_count": 1833}
+{"path_article": "actions/monitoring-and-troubleshooting-workflows/notifications-for-workflow-runs", "path_count": 1830}
+{"path_article": "github/copilot/about-github-copilot-telemetry", "path_count": 1829}
+{"path_article": "organizations/collaborating-with-groups-in-organizations/about-your-organization-dashboard", "path_count": 1823}
+{"path_article": "graphql/guides/migrating-from-rest-to-graphql", "path_count": 1822}
+{"path_article": "admin/identity-and-access-management/managing-iam-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise", "path_count": 1818}
+{"path_article": "organizations/managing-organization-settings/setting-permissions-for-adding-outside-collaborators", "path_count": 1816}
+{"path_article": "desktop/contributing-and-collaborating-using-github-desktop/managing-commits/amending-a-commit", "path_count": 1815}
+{"path_article": "actions/managing-workflow-runs/deleting-a-workflow-run", "path_count": 1815}
+{"path_article": "graphql/reference/scalars", "path_count": 1812}
+{"path_article": "repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/customizing-your-repositorys-social-media-preview", "path_count": 1811}
+{"path_article": "account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/converting-a-user-into-an-organization", "path_count": 1801}
+{"path_article": "issues/tracking-your-work-with-issues/quickstart", "path_count": 1800}
+{"path_article": "education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-at-your-educational-institution/about-github-campus-program", "path_count": 1799}
+{"path_article": "get-started/using-git/about-git-subtree-merges", "path_count": 1797}
+{"path_article": "get-started/importing-your-projects-to-github/importing-source-code-to-github", "path_count": 1793}
+{"path_article": "actions/migrating-to-github-actions/migrating-from-azure-pipelines-to-github-actions", "path_count": 1783}
+{"path_article": "actions/automating-builds-and-tests/building-and-testing-python", "path_count": 1778}
+{"path_article": "get-started/signing-up-for-github", "path_count": 1771}
+{"path_article": "actions/managing-workflow-runs/canceling-a-workflow", "path_count": 1763}
+{"path_article": "pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/viewing-a-pull-request-review", "path_count": 1763}
+{"path_article": "actions/managing-workflow-runs/removing-workflow-artifacts", "path_count": 1759}
+{"path_article": "communities", "path_count": 1743}
+{"path_article": "authentication/authenticating-with-saml-single-sign-on/viewing-and-managing-your-active-saml-sessions", "path_count": 1727}
+{"path_article": "repositories/releasing-projects-on-github/comparing-releases", "path_count": 1712}
+{"path_article": "billing/managing-billing-for-your-github-account/about-billing-for-github-accounts", "path_count": 1710}
+{"path_article": "repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-rebasing-for-pull-requests", "path_count": 1701}
+{"path_article": "repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-git-lfs-objects-in-archives-of-your-repository", "path_count": 1698}
+{"path_article": "developers/apps/building-github-apps/creating-a-github-app-from-a-manifest", "path_count": 1698}
+{"path_article": "pull-requests/committing-changes-to-your-project/troubleshooting-commits/commit-exists-on-github-but-not-in-my-local-clone", "path_count": 1689}
+{"path_article": "desktop/installing-and-configuring-github-desktop/configuring-and-customizing-github-desktop/configuring-basic-settings", "path_count": 1683}
+{"path_article": "education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork/why-wasnt-my-application-for-a-student-developer-pack-approved", "path_count": 1679}
+{"path_article": "actions/automating-builds-and-tests/building-and-testing-powershell", "path_count": 1678}
+{"path_article": "actions/hosting-your-own-runners/removing-self-hosted-runners", "path_count": 1677}
+{"path_article": "admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise", "path_count": 1674}
+{"path_article": "rest/reference/dependabot", "path_count": 1672}
+{"path_article": "sponsors/getting-started-with-github-sponsors/about-github-sponsors", "path_count": 1671}
+{"path_article": "get-started/importing-your-projects-to-github/importing-source-code-to-github/source-code-migration-tools", "path_count": 1666}
+{"path_article": "search-github/searching-on-github/searching-in-forks", "path_count": 1664}
+{"path_article": "developers/webhooks-and-events", "path_count": 1664}
+{"path_article": "organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization", "path_count": 1651}
+{"path_article": "issues/organizing-your-work-with-project-boards/managing-project-boards/about-automation-for-project-boards", "path_count": 1646}
+{"path_article": "repositories/creating-and-managing-repositories", "path_count": 1642}
+{"path_article": "code-security/security-advisories/about-github-security-advisories", "path_count": 1634}
+{"path_article": "authentication/keeping-your-account-and-data-secure/connecting-with-third-party-applications", "path_count": 1633}
+{"path_article": "github/site-policy/github-candidate-privacy-policy", "path_count": 1631}
+{"path_article": "actions/using-jobs/assigning-permissions-to-jobs", "path_count": 1626}
+{"path_article": "admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise", "path_count": 1626}
+{"path_article": "organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities", "path_count": 1622}
+{"path_article": "organizations/restricting-access-to-your-organizations-data", "path_count": 1610}
+{"path_article": "issues/trying-out-the-new-projects-experience/managing-the-visibility-of-your-projects", "path_count": 1606}
+{"path_article": "organizations/managing-access-to-your-organizations-project-boards/project-board-permissions-for-an-organization", "path_count": 1601}
+{"path_article": "actions/monitoring-and-troubleshooting-workflows/using-the-visualization-graph", "path_count": 1598}
+{"path_article": "actions/using-jobs/setting-default-values-for-jobs", "path_count": 1598}
+{"path_article": "desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop/updating-github-desktop", "path_count": 1592}
+{"path_article": "rest/guides/rendering-data-as-graphs", "path_count": 1590}
+{"path_article": "code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-notifications-for-vulnerable-dependencies", "path_count": 1588}
+{"path_article": "rest/guides/building-a-ci-server", "path_count": 1579}
+{"path_article": "developers/apps/building-github-apps/setting-permissions-for-github-apps", "path_count": 1571}
+{"path_article": "pull-requests/committing-changes-to-your-project/creating-and-editing-commits/about-commits", "path_count": 1570}
+{"path_article": "repositories/viewing-activity-and-data-for-your-repository/viewing-deployment-activity-for-your-repository", "path_count": 1569}
+{"path_article": "billing/managing-billing-for-your-github-account", "path_count": 1567}
+{"path_article": "get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-server", "path_count": 1565}
+{"path_article": "developers/apps/getting-started-with-apps/activating-optional-features-for-apps", "path_count": 1562}
+{"path_article": "rest/reference/scim", "path_count": 1555}
+{"path_article": "admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/configuring-saml-single-sign-on-for-enterprise-managed-users", "path_count": 1554}
+{"path_article": "billing/managing-billing-for-git-large-file-storage/upgrading-git-large-file-storage", "path_count": 1552}
+{"path_article": "developers/overview/secret-scanning-partner-program", "path_count": 1548}
+{"path_article": "code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/keeping-your-actions-up-to-date-with-dependabot", "path_count": 1548}
+{"path_article": "actions/publishing-packages/publishing-java-packages-with-gradle", "path_count": 1545}
+{"path_article": "account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories", "path_count": 1542}
+{"path_article": "account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings", "path_count": 1541}
+{"path_article": "account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/viewing-peoples-roles-in-an-organization", "path_count": 1538}
+{"path_article": "code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review", "path_count": 1537}
+{"path_article": "desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop/uninstalling-github-desktop", "path_count": 1532}
+{"path_article": "repositories/archiving-a-github-repository", "path_count": 1529}
+{"path_article": "get-started/writing-on-github/working-with-advanced-formatting/using-keywords-in-issues-and-pull-requests", "path_count": 1522}
+{"path_article": "authentication/troubleshooting-ssh/deleted-or-missing-ssh-keys", "path_count": 1522}
+{"path_article": "rest/reference/secret-scanning", "path_count": 1522}
+{"path_article": "get-started/importing-your-projects-to-github/working-with-subversion-on-github/support-for-subversion-clients", "path_count": 1518}
+{"path_article": "organizations/managing-saml-single-sign-on-for-your-organization/configuring-saml-single-sign-on-and-scim-using-okta", "path_count": 1515}
+{"path_article": "actions/deployment/managing-your-deployments/viewing-deployment-history", "path_count": 1510}
+{"path_article": "admin/user-management/monitoring-activity-in-your-enterprise/viewing-push-logs", "path_count": 1508}
+{"path_article": "admin/identity-and-access-management/authenticating-users-for-your-github-enterprise-server-instance/using-ldap", "path_count": 1502}
+{"path_article": "desktop/installing-and-configuring-github-desktop/overview/supported-operating-systems", "path_count": 1488}
+{"path_article": "actions/creating-actions/sharing-actions-and-workflows-with-your-enterprise", "path_count": 1484}
+{"path_article": "issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/archiving-cards-on-a-project-board", "path_count": 1481}
+{"path_article": "admin/overview/creating-an-enterprise-account", "path_count": 1474}
+{"path_article": "admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-aws", "path_count": 1472}
+{"path_article": "issues/trying-out-the-new-projects-experience/managing-access-to-projects", "path_count": 1460}
+{"path_article": "rest/reference/licenses", "path_count": 1455}
+{"path_article": "billing/managing-billing-for-git-large-file-storage/viewing-your-git-large-file-storage-usage", "path_count": 1448}
+{"path_article": "account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/managing-your-scheduled-reminders", "path_count": 1442}
+{"path_article": "developers/webhooks-and-events/webhooks", "path_count": 1434}
+{"path_article": "code-security/secret-scanning/secret-scanning-partners", "path_count": 1429}
+{"path_article": "sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers", "path_count": 1423}
+{"path_article": "get-started/importing-your-projects-to-github", "path_count": 1416}
+{"path_article": "admin/user-management/monitoring-activity-in-your-enterprise/audit-logging", "path_count": 1412}
+{"path_article": "billing/managing-your-github-billing-settings/viewing-your-subscriptions-and-billing-date", "path_count": 1411}
+{"path_article": "actions/using-containerized-services/creating-redis-service-containers", "path_count": 1411}
+{"path_article": "account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-access-to-your-user-accounts-project-boards", "path_count": 1407}
+{"path_article": "account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/sending-enterprise-contributions-to-your-githubcom-profile", "path_count": 1404}
+{"path_article": "repositories/viewing-activity-and-data-for-your-repository/analyzing-changes-to-a-repositorys-content", "path_count": 1404}
+{"path_article": "actions/migrating-to-github-actions/migrating-from-circleci-to-github-actions", "path_count": 1401}
+{"path_article": "github/site-policy-deprecated/github-enterprise-service-level-agreement", "path_count": 1399}
+{"path_article": "search-github/searching-on-github/searching-topics", "path_count": 1389}
+{"path_article": "admin/configuration/configuring-network-settings/configuring-tls", "path_count": 1389}
+{"path_article": "desktop/installing-and-configuring-github-desktop/configuring-and-customizing-github-desktop/about-git-large-file-storage-and-github-desktop", "path_count": 1379}
+{"path_article": "actions/automating-builds-and-tests/building-and-testing-nodejs", "path_count": 1376}
+{"path_article": "authentication/troubleshooting-commit-signature-verification", "path_count": 1371}
+{"path_article": "admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise", "path_count": 1370}
+{"path_article": "organizations/keeping-your-organization-secure", "path_count": 1365}
+{"path_article": "admin/configuration/configuring-network-settings/network-ports", "path_count": 1360}
+{"path_article": "actions/deployment/deploying-xcode-applications/installing-an-apple-certificate-on-macos-runners-for-xcode-development", "path_count": 1360}
+{"path_article": "actions/using-workflows/using-github-cli-in-workflows", "path_count": 1358}
+{"path_article": "communities/moderating-comments-and-conversations/managing-disruptive-comments", "path_count": 1354}
+{"path_article": "admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-vmware", "path_count": 1352}
+{"path_article": "pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/filtering-files-in-a-pull-request", "path_count": 1352}
+{"path_article": "pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/keeping-your-pull-request-in-sync-with-the-base-branch", "path_count": 1349}
+{"path_article": "github/site-policy/github-sponsors-additional-terms", "path_count": 1348}
+{"path_article": "sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor", "path_count": 1342}
+{"path_article": "repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-suggestions-to-update-pull-request-branches", "path_count": 1338}
+{"path_article": "pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request", "path_count": 1336}
+{"path_article": "account-and-profile/setting-up-and-managing-your-github-user-account", "path_count": 1336}
+{"path_article": "organizations/restricting-access-to-your-organizations-data/enabling-oauth-app-access-restrictions-for-your-organization", "path_count": 1333}
+{"path_article": "account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/types-of-emails-github-sends", "path_count": 1332}
+{"path_article": "admin/configuration/configuring-github-connect/managing-github-connect", "path_count": 1328}
+{"path_article": "actions/creating-actions/releasing-and-maintaining-actions", "path_count": 1328}
+{"path_article": "authentication/troubleshooting-ssh/error-ssh-add-illegal-option----k", "path_count": 1328}
+{"path_article": "repositories/creating-and-managing-repositories/creating-an-issues-only-repository", "path_count": 1322}
+{"path_article": "education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork/about-github-education-for-students", "path_count": 1322}
+{"path_article": "organizations/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization", "path_count": 1316}
+{"path_article": "get-started/privacy-on-github/about-githubs-use-of-your-data", "path_count": 1315}
+{"path_article": "authentication/troubleshooting-ssh/error-permission-to-userrepo-denied-to-other-user", "path_count": 1311}
+{"path_article": "rest/reference/reactions", "path_count": 1309}
+{"path_article": "codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces", "path_count": 1309}
+{"path_article": "admin/overview/system-overview", "path_count": 1302}
+{"path_article": "developers/github-marketplace/github-marketplace-overview/about-marketplace-badges", "path_count": 1299}
+{"path_article": "developers/webhooks-and-events/events/issue-event-types", "path_count": 1295}
+{"path_article": "admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-amazon-s3-storage", "path_count": 1293}
+{"path_article": "developers/apps/managing-github-apps/making-a-github-app-public-or-private", "path_count": 1292}
+{"path_article": "organizations/managing-peoples-access-to-your-organization-with-roles", "path_count": 1289}
+{"path_article": "get-started/getting-started-with-git", "path_count": 1275}
+{"path_article": "communities/setting-up-your-project-for-healthy-contributions/about-community-profiles-for-public-repositories", "path_count": 1272}
+{"path_article": "account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile", "path_count": 1269}
+{"path_article": "rest/reference/pages", "path_count": 1266}
+{"path_article": "admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance", "path_count": 1262}
+{"path_article": "communities/setting-up-your-project-for-healthy-contributions", "path_count": 1247}
+{"path_article": "pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests", "path_count": 1245}
+{"path_article": "code-security/code-scanning/integrating-with-code-scanning/uploading-a-sarif-file-to-github", "path_count": 1241}
+{"path_article": "admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise", "path_count": 1238}
+{"path_article": "repositories/working-with-files/managing-large-files/resolving-git-large-file-storage-upload-failures", "path_count": 1235}
+{"path_article": "admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise", "path_count": 1220}
+{"path_article": "communities/documenting-your-project-with-wikis/changing-access-permissions-for-wikis", "path_count": 1217}
+{"path_article": "get-started/customizing-your-github-workflow/exploring-integrations/about-integrations", "path_count": 1216}
+{"path_article": "authentication/keeping-your-account-and-data-secure/reviewing-your-authorized-applications-oauth", "path_count": 1216}
+{"path_article": "sponsors", "path_count": 1208}
+{"path_article": "rest/reference/oauth-authorizations", "path_count": 1207}
+{"path_article": "code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning", "path_count": 1204}
+{"path_article": "communities/using-templates-to-encourage-useful-issues-and-pull-requests", "path_count": 1198}
+{"path_article": "admin/guides", "path_count": 1193}
+{"path_article": "billing/managing-billing-for-git-large-file-storage", "path_count": 1192}
+{"path_article": "admin/configuration/configuring-your-enterprise/accessing-the-administrative-shell-ssh", "path_count": 1190}
+{"path_article": "authentication/keeping-your-account-and-data-secure/reviewing-your-deploy-keys", "path_count": 1190}
+{"path_article": "admin/installation", "path_count": 1185}
+{"path_article": "account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/about-organization-membership", "path_count": 1185}
+{"path_article": "authentication/securing-your-account-with-two-factor-authentication-2fa/changing-two-factor-authentication-delivery-methods-for-your-mobile-device", "path_count": 1177}
+{"path_article": "get-started/onboarding/getting-started-with-github-team", "path_count": 1176}
+{"path_article": "github/site-policy-deprecated/amendment-to-github-terms-of-service-applicable-to-us-federal-government-users", "path_count": 1173}
+{"path_article": "organizations/restricting-access-to-your-organizations-data/disabling-oauth-app-access-restrictions-for-your-organization", "path_count": 1172}
+{"path_article": "communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-githubs-form-schema", "path_count": 1170}
+{"path_article": "billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account", "path_count": 1162}
+{"path_article": "actions/automating-builds-and-tests/building-and-testing-java-with-ant", "path_count": 1162}
+{"path_article": "github/site-policy/github-logo-policy", "path_count": 1161}
+{"path_article": "account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/troubleshooting-commits-on-your-timeline", "path_count": 1157}
+{"path_article": "code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow", "path_count": 1156}
+{"path_article": "codespaces/setting-up-your-project-for-codespaces/setting-up-your-project-for-codespaces", "path_count": 1154}
+{"path_article": "admin/user-management/managing-users-in-your-enterprise/suspending-and-unsuspending-users", "path_count": 1150}
+{"path_article": "account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/best-practices-for-leaving-your-company", "path_count": 1148}
+{"path_article": "billing/managing-billing-for-your-github-account/how-does-upgrading-or-downgrading-affect-the-billing-process", "path_count": 1145}
+{"path_article": "admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/configuring-scim-provisioning-for-enterprise-managed-users", "path_count": 1143}
+{"path_article": "organizations/organizing-members-into-teams/removing-organization-members-from-a-team", "path_count": 1141}
+{"path_article": "admin/configuration/configuring-network-settings/configuring-a-hostname", "path_count": 1140}
+{"path_article": "issues/organizing-your-work-with-project-boards/managing-project-boards/editing-a-project-board", "path_count": 1133}
+{"path_article": "billing/managing-your-license-for-github-enterprise", "path_count": 1132}
+{"path_article": "github/copilot/research-recitation", "path_count": 1131}
+{"path_article": "organizations/managing-organization-settings/upgrading-to-the-corporate-terms-of-service", "path_count": 1127}
+{"path_article": "organizations/managing-organization-settings/managing-default-labels-for-repositories-in-your-organization", "path_count": 1118}
+{"path_article": "admin/user-management/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise", "path_count": 1118}
+{"path_article": "actions/automating-builds-and-tests/building-and-testing-ruby", "path_count": 1110}
+{"path_article": "code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system", "path_count": 1108}
+{"path_article": "actions/advanced-guides/using-github-cli-in-workflows", "path_count": 1106}
+{"path_article": "admin/user-management/managing-organizations-in-your-enterprise/streaming-the-audit-logs-for-organizations-in-your-enterprise-account", "path_count": 1104}
+{"path_article": "actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-cloud-providers", "path_count": 1100}
+{"path_article": "pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests", "path_count": 1098}
+{"path_article": "organizations/managing-organization-settings", "path_count": 1093}
+{"path_article": "get-started/importing-your-projects-to-github/importing-source-code-to-github/updating-commit-author-attribution-with-github-importer", "path_count": 1092}
+{"path_article": "graphql/guides/using-global-node-ids", "path_count": 1088}
+{"path_article": "developers/apps/managing-oauth-apps/troubleshooting-oauth-app-access-token-request-errors", "path_count": 1088}
+{"path_article": "search-github/searching-on-github/searching-for-packages", "path_count": 1088}
+{"path_article": "codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace", "path_count": 1086}
+{"path_article": "admin/identity-and-access-management/authenticating-users-for-your-github-enterprise-server-instance/using-saml", "path_count": 1083}
+{"path_article": "admin/user-management/managing-users-in-your-enterprise/managing-dormant-users", "path_count": 1073}
+{"path_article": "rest/reference/billing", "path_count": 1067}
+{"path_article": "code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-the-codeql-workflow-for-compiled-languages", "path_count": 1066}
+{"path_article": "actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-azure", "path_count": 1061}
+{"path_article": "billing/managing-your-github-billing-settings/viewing-your-payment-history-and-receipts", "path_count": 1055}
+{"path_article": "code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-managing-vulnerable-dependencies", "path_count": 1051}
+{"path_article": "codespaces/developing-in-codespaces/codespaces-lifecycle", "path_count": 1051}
+{"path_article": "authentication/keeping-your-account-and-data-secure/about-anonymized-urls", "path_count": 1048}
+{"path_article": "issues/organizing-your-work-with-project-boards/managing-project-boards/copying-a-project-board", "path_count": 1043}
+{"path_article": "communities/documenting-your-project-with-wikis/viewing-a-wikis-history-of-changes", "path_count": 1041}
+{"path_article": "admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise", "path_count": 1040}
+{"path_article": "repositories/archiving-a-github-repository/about-archiving-content-and-data-on-github", "path_count": 1039}
+{"path_article": "communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization", "path_count": 1036}
+{"path_article": "get-started/using-git/dealing-with-special-characters-in-branch-and-tag-names", "path_count": 1032}
+{"path_article": "organizations/collaborating-with-groups-in-organizations/accessing-your-organizations-settings", "path_count": 1027}
+{"path_article": "github/site-policy/github-codespaces-privacy-statement", "path_count": 1026}
+{"path_article": "code-security/guides", "path_count": 1024}
+{"path_article": "pull-requests/committing-changes-to-your-project/viewing-and-comparing-commits", "path_count": 1024}
+{"path_article": "billing/managing-billing-for-github-packages/viewing-your-github-packages-usage", "path_count": 1024}
+{"path_article": "issues/tracking-your-work-with-issues/planning-and-tracking-work-for-your-team-or-project", "path_count": 1023}
+{"path_article": "developers/apps/getting-started-with-apps", "path_count": 1018}
+{"path_article": "authentication/troubleshooting-ssh/error-ssl-certificate-problem-verify-that-the-ca-cert-is-ok", "path_count": 1017}
+{"path_article": "discussions/collaborating-with-your-community-using-discussions/about-discussions", "path_count": 1017}
+{"path_article": "admin/configuration/configuring-github-connect/enabling-the-dependency-graph-and-dependabot-alerts-for-your-enterprise", "path_count": 1017}
+{"path_article": "graphql/reference/unions", "path_count": 1010}
+{"path_article": "code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/customizing-dependency-updates", "path_count": 1007}
+{"path_article": "code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors", "path_count": 1006}
+{"path_article": "admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise", "path_count": 1003}
+{"path_article": "communities/moderating-comments-and-conversations/locking-conversations", "path_count": 1002}
+{"path_article": "issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-notes-to-a-project-board", "path_count": 1001}
+{"path_article": "actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-nodejs-to-azure-app-service", "path_count": 995}
+{"path_article": "admin/user-management/managing-organizations-in-your-enterprise/adding-people-to-teams", "path_count": 986}
+{"path_article": "desktop/installing-and-configuring-github-desktop/configuring-and-customizing-github-desktop/setting-a-theme-for-github-desktop", "path_count": 985}
+{"path_article": "code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests", "path_count": 984}
+{"path_article": "account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-accessibility-settings", "path_count": 982}
+{"path_article": "organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization", "path_count": 981}
+{"path_article": "graphql/overview/breaking-changes", "path_count": 980}
+{"path_article": "get-started/writing-on-github/editing-and-sharing-content-with-gists/forking-and-cloning-gists", "path_count": 979}
+{"path_article": "actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-google-cloud-platform", "path_count": 971}
+{"path_article": "codespaces/developing-in-codespaces/developing-in-a-codespace", "path_count": 968}
+{"path_article": "developers/github-marketplace/creating-apps-for-github-marketplace/requirements-for-listing-an-app", "path_count": 966}
+{"path_article": "account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-security-and-analysis-settings-for-your-user-account", "path_count": 966}
+{"path_article": "organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group", "path_count": 964}
diff --git a/pages/[versionId]/rest/reference/[category].tsx b/pages/[versionId]/rest/reference/[category].tsx
index ebd670026769..35acd842456f 100644
--- a/pages/[versionId]/rest/reference/[category].tsx
+++ b/pages/[versionId]/rest/reference/[category].tsx
@@ -29,7 +29,11 @@ type CategoryDataT = {
introContent: string
}
-type RestDataT = Record
+type RestDataT = {
+ [version: string]: {
+ [category: string]: CategoryDataT
+ }
+}
type Props = {
mainContext: MainContextT
@@ -40,7 +44,7 @@ type Props = {
}
let rest: RestOperationsT | null = null
-const restOperationData: RestDataT = {}
+let restOperationData: RestDataT | null = null
export default function Category({
mainContext,
@@ -94,10 +98,15 @@ export const getServerSideProps: GetServerSideProps = async (context) =>
rest = (await getRest()) as RestOperationsT
}
+ if (!restOperationData) {
+ restOperationData = {}
+ Object.keys(req.context.allVersions).forEach((version) => (restOperationData![version] = {}))
+ }
+
const restOperations = rest[currentVersion][category]
- if (!(category in restOperationData)) {
- restOperationData[category] = (await getRestOperationData(
+ if (!(category in restOperationData[currentVersion])) {
+ restOperationData[currentVersion][category] = (await getRestOperationData(
category,
restOperations,
req.context
@@ -109,15 +118,15 @@ export const getServerSideProps: GetServerSideProps = async (context) =>
// are undefined. We need to populate those properties with the static
// data read from the decorated schema files.
const articleContext = getArticleContextFromRequest(req)
- articleContext.miniTocItems = restOperationData[category].miniTocItems
+ articleContext.miniTocItems = restOperationData[currentVersion][category].miniTocItems
return {
props: {
restOperations,
mainContext: getMainContext(req, res),
- descriptions: restOperationData[category].descriptions,
+ descriptions: restOperationData[currentVersion][category].descriptions,
articleContext: articleContext,
- introContent: restOperationData[category].introContent,
+ introContent: restOperationData[currentVersion][category].introContent,
},
}
}
diff --git a/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-java-with-ant.md b/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-java-with-ant.md
index 695823dffc28..8006c54d6923 100644
--- a/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-java-with-ant.md
+++ b/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-java-with-ant.md
@@ -78,9 +78,9 @@ Este flujo de trabajo realiza los siguientes pasos:
Los flujos de trabajo iniciales predeterminados son un punto de partida excelente para crear tu flujo de trabajo de prueba y de compilación y puedes personalizarlos de acuerdo con las necesidades de tu proyecto.
-{% data reusables.github-actions.example-github-runner %}
+{% data reusables.actions.example-github-runner %}
-{% data reusables.github-actions.java-jvm-architecture %}
+{% data reusables.actions.java-jvm-architecture %}
## Construir y probar tu código
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 d2da20b22bc1..5282d21fa168 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
@@ -83,9 +83,9 @@ Este flujo de trabajo realiza los siguientes pasos:
Los flujos de trabajo iniciales predeterminados son un punto de partida excelente para crear tu flujo de trabajo de prueba y de compilación y puedes personalizarlos de acuerdo con las necesidades de tu proyecto.
-{% data reusables.github-actions.example-github-runner %}
+{% data reusables.actions.example-github-runner %}
-{% data reusables.github-actions.java-jvm-architecture %}
+{% data reusables.actions.java-jvm-architecture %}
## Construir y probar tu código
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 659be5bde747..cdce2cf66658 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
@@ -78,9 +78,9 @@ Este flujo de trabajo realiza los siguientes pasos:
Los flujos de trabajo iniciales predeterminados son un punto de partida excelente para crear tu flujo de trabajo de prueba y de compilación y puedes personalizarlos de acuerdo con las necesidades de tu proyecto.
-{% data reusables.github-actions.example-github-runner %}
+{% data reusables.actions.example-github-runner %}
-{% data reusables.github-actions.java-jvm-architecture %}
+{% data reusables.actions.java-jvm-architecture %}
## Construir y probar tu código
diff --git a/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-nodejs.md b/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-nodejs.md
index 6453d4bc56d8..2fe6f5c5e617 100644
--- a/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-nodejs.md
+++ b/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-nodejs.md
@@ -73,7 +73,7 @@ jobs:
```
{% endraw %}
-{% data reusables.github-actions.example-github-runner %}
+{% data reusables.actions.example-github-runner %}
## Especificar la versión de Node.js
@@ -204,7 +204,7 @@ steps:
### Ejemplo de uso de un registro privado y la creación del archivo .npmrc
-{% data reusables.github-actions.setup-node-intro %}
+{% data reusables.actions.setup-node-intro %}
Para autenticar tu registro privado, necesitarás almacenar tu token de autenticación de npm como un secreto. Por ejemplo, crea un repositorio secreto que se llame `NPM_TOKEN`. Para más información, consulta "[Crear y usar secretos cifrados](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)."
diff --git a/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-xamarin-applications.md b/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-xamarin-applications.md
index 5749a33e9d8d..f596e4e82d7d 100644
--- a/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-xamarin-applications.md
+++ b/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-xamarin-applications.md
@@ -31,7 +31,7 @@ Para encontrar una lista completa de versiones disponibles de Xamarin SDK en los
* [macOS 10.15](https://github.com/actions/virtual-environments/blob/main/images/macos/macos-10.15-Readme.md#xamarin-bundles)
* [macOS 11](https://github.com/actions/virtual-environments/blob/main/images/macos/macos-11-Readme.md#xamarin-bundles)
-{% data reusables.github-actions.macos-runner-preview %}
+{% data reusables.actions.macos-runner-preview %}
## Prerrequisitos
diff --git a/translations/es-ES/content/actions/creating-actions/about-custom-actions.md b/translations/es-ES/content/actions/creating-actions/about-custom-actions.md
index 66cf09edae84..cd0659f918bf 100644
--- a/translations/es-ES/content/actions/creating-actions/about-custom-actions.md
+++ b/translations/es-ES/content/actions/creating-actions/about-custom-actions.md
@@ -47,13 +47,13 @@ Los contenedores Docker empaquetan el entorno con el código de las {% data vari
Un contenedor Docker te permite usar versiones específicas de un sistema operativo, dependencias, herramientas y código. Para las acciones que se deben ejecutar en una configuración de entorno específica, Docker es una opción ideal porque puedes personalizar el sistema operativo y las herramientas. Debido a la latencia para crear y recuperar el contenedor, las acciones del contenedor Docker son más lentas que las acciones de JavaScript.
-Las acciones de contenedor de Docker solo pueden ejecutarse en ejecutores con un sistema operativo Linux. {% data reusables.github-actions.self-hosted-runner-reqs-docker %}
+Las acciones de contenedor de Docker solo pueden ejecutarse en ejecutores con un sistema operativo Linux. {% data reusables.actions.self-hosted-runner-reqs-docker %}
### Acciones de JavaScript
Las acciones de JavaScript pueden ejecutarse directamente en una máquina del ejecutor y separar el código de acción del entorno utilizado para ejecutar el código. El uso de una acción de JavaScript simplifica el código de acción y se ejecuta más rápido que una acción de contenedor Docker.
-{% data reusables.github-actions.pure-javascript %}
+{% data reusables.actions.pure-javascript %}
Si estás desarrollando un proyecto Node.js, el conjunto de herramientas de las {% data variables.product.prodname_actions %} te ofrece paquetes que puedes usar en tu proyecto para acelerar el desarrollo. Para obtener más información, consulta el repositorio [actions/toolkit](https://github.com/actions/toolkit).
diff --git a/translations/es-ES/content/actions/creating-actions/creating-a-composite-action.md b/translations/es-ES/content/actions/creating-actions/creating-a-composite-action.md
index f1e887ef345f..4118bc8eb964 100644
--- a/translations/es-ES/content/actions/creating-actions/creating-a-composite-action.md
+++ b/translations/es-ES/content/actions/creating-actions/creating-a-composite-action.md
@@ -23,7 +23,7 @@ En esta guía, aprenderás acerca de los componentes básicos necesarios para cr
Una vez que completes este proyecto, deberías comprender cómo crear tu propia acción compuesta y probarla en un flujo de trabajo.
-{% data reusables.github-actions.context-injection-warning %}
+{% data reusables.actions.context-injection-warning %}
## Prerrequisitos
diff --git a/translations/es-ES/content/actions/creating-actions/creating-a-docker-container-action.md b/translations/es-ES/content/actions/creating-actions/creating-a-docker-container-action.md
index 049b7b020803..e9a51c564145 100644
--- a/translations/es-ES/content/actions/creating-actions/creating-a-docker-container-action.md
+++ b/translations/es-ES/content/actions/creating-actions/creating-a-docker-container-action.md
@@ -27,9 +27,9 @@ In this guide, you'll learn about the basic components needed to create and use
Once you complete this project, you should understand how to build your own Docker container action and test it in a workflow.
-{% data reusables.github-actions.self-hosted-runner-reqs-docker %}
+{% data reusables.actions.self-hosted-runner-reqs-docker %}
-{% data reusables.github-actions.context-injection-warning %}
+{% data reusables.actions.context-injection-warning %}
## Prerequisites
diff --git a/translations/es-ES/content/actions/creating-actions/creating-a-javascript-action.md b/translations/es-ES/content/actions/creating-actions/creating-a-javascript-action.md
index a0f17e8c4589..e0cc9e6237d4 100644
--- a/translations/es-ES/content/actions/creating-actions/creating-a-javascript-action.md
+++ b/translations/es-ES/content/actions/creating-actions/creating-a-javascript-action.md
@@ -29,9 +29,9 @@ Esta guía usa el módulo Node.js del kit de herramientas {% data variables.prod
Una vez que completes este proyecto, deberías comprender cómo crear tu propia acción de JavaScript y probarla en un flujo de trabajo.
-{% data reusables.github-actions.pure-javascript %}
+{% data reusables.actions.pure-javascript %}
-{% data reusables.github-actions.context-injection-warning %}
+{% data reusables.actions.context-injection-warning %}
## Prerrequisitos
diff --git a/translations/es-ES/content/actions/creating-actions/dockerfile-support-for-github-actions.md b/translations/es-ES/content/actions/creating-actions/dockerfile-support-for-github-actions.md
index 3795a144fd62..16527876de01 100644
--- a/translations/es-ES/content/actions/creating-actions/dockerfile-support-for-github-actions.md
+++ b/translations/es-ES/content/actions/creating-actions/dockerfile-support-for-github-actions.md
@@ -105,7 +105,7 @@ Si defines el `args` en el archivo de metadatos de la acción, `args` invalidar
Si utilizas `CMD` en tu `Dockerfile`, sigue estos lineamientos:
-{% data reusables.github-actions.dockerfile-guidelines %}
+{% data reusables.actions.dockerfile-guidelines %}
## Capacidades de Linux compatibles
diff --git a/translations/es-ES/content/actions/creating-actions/metadata-syntax-for-github-actions.md b/translations/es-ES/content/actions/creating-actions/metadata-syntax-for-github-actions.md
index 6ccd392be310..80347dcf6c69 100644
--- a/translations/es-ES/content/actions/creating-actions/metadata-syntax-for-github-actions.md
+++ b/translations/es-ES/content/actions/creating-actions/metadata-syntax-for-github-actions.md
@@ -272,7 +272,7 @@ Para obtener más información, consulta la sección "[``](/actions/reference/co
**Opcional** Puedes utilizar el condicional `if` para prevenir que un paso se ejecute a menos de que se cumpla con una condición. Puedes usar cualquier contexto y expresión admitidos para crear un condicional.
-{% data reusables.github-actions.expression-syntax-if %} Para obtener más información, consulta la sección "[Expresiones](/actions/learn-github-actions/expressions)".
+{% data reusables.actions.expression-syntax-if %} Para obtener más información, consulta la sección "[Expresiones](/actions/learn-github-actions/expressions)".
**Ejemplo: Utilizando contextos**
@@ -441,7 +441,7 @@ runs:
Los `args` se usan en el lugar de la instrucción `CMD` en un `Dockerfile`. Si usas `CMD` en tu `Dockerfile`, usa los lineamientos ordenados por preferencia:
-{% data reusables.github-actions.dockerfile-guidelines %}
+{% data reusables.actions.dockerfile-guidelines %}
Si necesitas pasar variables de ambiente a una acción, asegúrate que ésta ejecute un shell de comandos para realizar la sustitución de variables. Por ejemplo, si se configura tu atributo `entrypoint` como `"sh -c"`, entoces `args` se ejecutará en un shell de comandos. Como alternativa, si tu `Dockerfile` utiliza un `ENTRYPOINT` para ejecutar el mismo comando (`"sh -c"`), entonces `args` se ejecutará en un shell de comandos.
diff --git a/translations/es-ES/content/actions/deployment/targeting-different-environments/using-environments-for-deployment.md b/translations/es-ES/content/actions/deployment/targeting-different-environments/using-environments-for-deployment.md
index 855725325cbe..091b672d0cd0 100644
--- a/translations/es-ES/content/actions/deployment/targeting-different-environments/using-environments-for-deployment.md
+++ b/translations/es-ES/content/actions/deployment/targeting-different-environments/using-environments-for-deployment.md
@@ -69,13 +69,13 @@ Los secretos que se almacenan en un ambiente sólo se encuentran disponibles par
## Crear un ambiente
-{% data reusables.github-actions.permissions-statement-environment %}
+{% data reusables.actions.permissions-statement-environment %}
{% data reusables.repositories.navigate-to-repo %}
{% data reusables.repositories.sidebar-settings %}
-{% data reusables.github-actions.sidebar-environment %}
-{% data reusables.github-actions.new-environment %}
-{% data reusables.github-actions.name-environment %}
+{% data reusables.actions.sidebar-environment %}
+{% data reusables.actions.new-environment %}
+{% data reusables.actions.name-environment %}
1. Opcionalmente, personas o equipos específicos deben aprobar los jobs de flujo de trabajo que utilicen este ambiente.
1. Selecciona **Revisores requeridos**.
1. Ingresa hasta 6 personas o equipos. Solo uno de los revisores requeridos necesita aprobar el job para que éste pueda proceder.
@@ -107,13 +107,13 @@ Cuando un flujo de trabajo referencia un ambiente, éste aparecerá en los despl
## Borrar un ambiente
-{% data reusables.github-actions.permissions-statement-environment %}
+{% data reusables.actions.permissions-statement-environment %}
El borrar un ambiente borrará todos los secretos y reglas de protección asociadas con éste. Cualquier job que esté actualmente en espera porque depende de las reglas de protección del ambiente que se borró, fallará automáticamente.
{% data reusables.repositories.navigate-to-repo %}
{% data reusables.repositories.sidebar-settings %}
-{% data reusables.github-actions.sidebar-environment %}
+{% data reusables.actions.sidebar-environment %}
1. Junto al ambiente que quieres borrar, haz clic en {% octicon "trash" aria-label="The trash icon" %}.
2. Da clic en **Entiendo, borra este ambiente**.
diff --git a/translations/es-ES/content/actions/hosting-your-own-runners/about-self-hosted-runners.md b/translations/es-ES/content/actions/hosting-your-own-runners/about-self-hosted-runners.md
index d2d43e503959..31c4aee2284f 100644
--- a/translations/es-ES/content/actions/hosting-your-own-runners/about-self-hosted-runners.md
+++ b/translations/es-ES/content/actions/hosting-your-own-runners/about-self-hosted-runners.md
@@ -18,25 +18,25 @@ type: overview
## About self-hosted runners
-{% data reusables.github-actions.self-hosted-runner-description %} Self-hosted runners can be physical, virtual, in a container, on-premises, or in a cloud.
+{% data reusables.actions.self-hosted-runner-description %} Self-hosted runners can be physical, virtual, in a container, on-premises, or in a cloud.
You can add self-hosted runners at various levels in the management hierarchy:
- Repository-level runners are dedicated to a single repository.
- Organization-level runners can process jobs for multiple repositories in an organization.
- Enterprise-level runners can be assigned to multiple organizations in an enterprise account.
-Your runner machine connects to {% data variables.product.product_name %} using the {% data variables.product.prodname_actions %} self-hosted runner application. {% data reusables.github-actions.runner-app-open-source %} When a new version is released, the runner application automatically updates itself when a job is assigned to the runner, or within a week of release if the runner hasn't been assigned any jobs.
+Your runner machine connects to {% data variables.product.product_name %} using the {% data variables.product.prodname_actions %} self-hosted runner application. {% data reusables.actions.runner-app-open-source %} When a new version is released, the runner application automatically updates itself when a job is assigned to the runner, or within a week of release if the runner hasn't been assigned any jobs.
-{% data reusables.github-actions.self-hosted-runner-auto-removal %}
+{% data reusables.actions.self-hosted-runner-auto-removal %}
For more information about installing and using self-hosted runners, see "[Adding self-hosted runners](/github/automating-your-workflow-with-github-actions/adding-self-hosted-runners)" and "[Using self-hosted runners in a workflow](/github/automating-your-workflow-with-github-actions/using-self-hosted-runners-in-a-workflow)."
-## {% ifversion fpt or ghes %}Differences between {% data variables.product.prodname_dotcom %}-hosted and {% elsif ghae %}Characteristics of {% endif %}self-hosted runners
+## {% ifversion fpt or ghec or ghes %}Differences between {% data variables.product.prodname_dotcom %}-hosted and {% elsif ghae %}Characteristics of {% endif %}self-hosted runners
-{% ifversion fpt or ghes %}
+{% ifversion fpt or ghec or ghes %}
{% data variables.product.prodname_dotcom %}-hosted runners offer a quicker, simpler way to run your workflows, while self-hosted{% elsif ghae %}Self-hosted{% endif %} runners are a highly configurable way to run workflows in your own custom environment. {% ifversion ghae %}Self-hosted runners:{% endif %}
-{% ifversion fpt or ghes %}
+{% ifversion fpt or ghec or ghes %}
**{% data variables.product.prodname_dotcom %}-hosted runners:**
- Receive automatic updates for the operating system, preinstalled packages and tools, and the self-hosted runner application.
- Are managed and maintained by {% data variables.product.prodname_dotcom %}.
@@ -70,15 +70,15 @@ You can automatically increase or decrease the number of self-hosted runners in
There are some limits on {% data variables.product.prodname_actions %} usage when using self-hosted runners. These limits are subject to change.
-{% data reusables.github-actions.usage-workflow-run-time %}
+{% data reusables.actions.usage-workflow-run-time %}
- **Job queue time** - Each job for self-hosted runners can be queued for a maximum of 24 hours. If a self-hosted runner does not start executing the job within this limit, the job is terminated and fails to complete.
-{% data reusables.github-actions.usage-api-requests %}
-- **Job matrix** - {% data reusables.github-actions.usage-matrix-limits %}
-{% data reusables.github-actions.usage-workflow-queue-limits %}
+{% data reusables.actions.usage-api-requests %}
+- **Job matrix** - {% data reusables.actions.usage-matrix-limits %}
+{% data reusables.actions.usage-workflow-queue-limits %}
## Workflow continuity for self-hosted runners
-{% data reusables.github-actions.runner-workflow-continuity %}
+{% data reusables.actions.runner-workflow-continuity %}
## Supported architectures and operating systems for self-hosted runners
@@ -224,7 +224,7 @@ codeload.github.com
{% ifversion fpt or ghec %}
-{% data reusables.github-actions.self-hosted-runner-security %}
+{% data reusables.actions.self-hosted-runner-security %}
{% endif %}
diff --git a/translations/es-ES/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md b/translations/es-ES/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md
index a43a506f24e3..6be17995b524 100644
--- a/translations/es-ES/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md
+++ b/translations/es-ES/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md
@@ -26,7 +26,7 @@ For information on supported operating systems for self-hosted runners, or using
{% ifversion not ghae %}
{% warning %}
-**Warning:** {% data reusables.github-actions.self-hosted-runner-security %}
+**Warning:** {% data reusables.actions.self-hosted-runner-security %}
For more information, see "[About self-hosted runners](/github/automating-your-workflow-with-github-actions/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)."
@@ -40,18 +40,18 @@ You can add self-hosted runners to a single repository. To add a self-hosted run
{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5091 %}
{% data reusables.repositories.navigate-to-repo %}
{% data reusables.repositories.sidebar-settings %}
-{% data reusables.github-actions.settings-sidebar-actions %}
-{% data reusables.github-actions.settings-sidebar-actions-runners-updated %}
+{% data reusables.actions.settings-sidebar-actions %}
+{% data reusables.actions.settings-sidebar-actions-runners-updated %}
1. Click **New self-hosted runner**.
-{% data reusables.github-actions.self-hosted-runner-configure %}
+{% data reusables.actions.self-hosted-runner-configure %}
{% elsif ghae or ghes < 3.4 %}
{% data reusables.repositories.navigate-to-repo %}
{% data reusables.repositories.sidebar-settings %}
-{% data reusables.github-actions.settings-sidebar-actions-runners %}
+{% data reusables.actions.settings-sidebar-actions-runners %}
1. Under {% ifversion ghes > 3.1 or ghae or ghec %}"Runners"{% else %}"Self-hosted runners"{% endif %}, click **Add runner**.
-{% data reusables.github-actions.self-hosted-runner-configure %}
+{% data reusables.actions.self-hosted-runner-configure %}
{% endif %}
-{% data reusables.github-actions.self-hosted-runner-check-installation-success %}
+{% data reusables.actions.self-hosted-runner-check-installation-success %}
## Adding a self-hosted runner to an organization
@@ -60,21 +60,21 @@ You can add self-hosted runners at the organization level, where they can be use
{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5091 %}
{% data reusables.organizations.navigate-to-org %}
{% data reusables.organizations.org_settings %}
-{% data reusables.github-actions.settings-sidebar-actions %}
-{% data reusables.github-actions.settings-sidebar-actions-runners-updated %}
+{% data reusables.actions.settings-sidebar-actions %}
+{% data reusables.actions.settings-sidebar-actions-runners-updated %}
1. Click **New runner**.
-{% data reusables.github-actions.self-hosted-runner-configure %}
+{% data reusables.actions.self-hosted-runner-configure %}
{% elsif ghae or ghes < 3.4 %}
{% data reusables.organizations.navigate-to-org %}
{% data reusables.organizations.org_settings %}
-{% data reusables.github-actions.settings-sidebar-actions-runners %}
+{% data reusables.actions.settings-sidebar-actions-runners %}
1. Under {% ifversion ghes > 3.1 or ghae %}"Runners", click **Add new**, then click **New runner**.{% elsif ghes < 3.2 %}"Self-hosted runners", click **Add runner**."{% endif %}
-{% data reusables.github-actions.self-hosted-runner-configure %}
+{% data reusables.actions.self-hosted-runner-configure %}
{% endif %}
-{% data reusables.github-actions.self-hosted-runner-check-installation-success %}
+{% data reusables.actions.self-hosted-runner-check-installation-success %}
-{% data reusables.github-actions.self-hosted-runner-public-repo-access %}
+{% data reusables.actions.self-hosted-runner-public-repo-access %}
## Adding a self-hosted runner to an enterprise
@@ -92,7 +92,7 @@ To add a self-hosted runner to an enterprise account, you must be an enterprise
{% data reusables.enterprise-accounts.actions-tab %}
{% data reusables.enterprise-accounts.actions-runners-tab %}
1. Click **New runner**.
-{% data reusables.github-actions.self-hosted-runner-configure %}
+{% data reusables.actions.self-hosted-runner-configure %}
{% elsif ghae or ghes < 3.4 %}
To add a self-hosted runner at the enterprise level of {% data variables.product.product_location %}, you must be a site administrator.
{% data reusables.enterprise-accounts.access-enterprise %}
@@ -100,11 +100,11 @@ To add a self-hosted runner at the enterprise level of {% data variables.product
{% data reusables.enterprise-accounts.actions-tab %}
{% data reusables.enterprise-accounts.actions-runners-tab %}
1. Click **Add new**, then click **New runner**.
-{% data reusables.github-actions.self-hosted-runner-configure %}
+{% data reusables.actions.self-hosted-runner-configure %}
{% endif %}
-{% data reusables.github-actions.self-hosted-runner-check-installation-success %}
+{% data reusables.actions.self-hosted-runner-check-installation-success %}
-{% data reusables.github-actions.self-hosted-runner-public-repo-access %}
+{% data reusables.actions.self-hosted-runner-public-repo-access %}
### Making enterprise runners available to repositories
diff --git a/translations/es-ES/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md b/translations/es-ES/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md
index 27c5cb1ca780..e158e70a7294 100644
--- a/translations/es-ES/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md
+++ b/translations/es-ES/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md
@@ -49,22 +49,22 @@ Cuando creas un grupo, debes elegir una política que defina qué repositorios t
{% ifversion ghec or ghes > 3.3 or ghae-issue-5091 %}
{% data reusables.organizations.navigate-to-org %}
{% data reusables.organizations.org_settings %}
-{% data reusables.github-actions.settings-sidebar-actions-runner-groups %}
+{% data reusables.actions.settings-sidebar-actions-runner-groups %}
1. En la sección de "Grupos de ejecutores", haz clic en **Grupo de ejecutores nuevo**.
- {% data reusables.github-actions.runner-group-assign-policy-repo %}
+ {% data reusables.actions.runner-group-assign-policy-repo %}
{% warning %}
- **Advertencia**: {% indented_data_reference reusables.github-actions.self-hosted-runner-security spaces=3 %}
+ **Advertencia**: {% indented_data_reference reusables.actions.self-hosted-runner-security spaces=3 %}
Para obtener más información, consulta "[Acerca de los ejecutores autoalojados](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)."
{% endwarning %}
-{% data reusables.github-actions.self-hosted-runner-create-group %}
+{% data reusables.actions.self-hosted-runner-create-group %}
{% elsif ghae or ghes < 3.4 %}
{% data reusables.organizations.navigate-to-org %}
{% data reusables.organizations.org_settings %}
-{% data reusables.github-actions.settings-sidebar-actions-runners %}
+{% data reusables.actions.settings-sidebar-actions-runners %}
1. Debajo de {% ifversion ghes > 3.1 or ghae %}"Ejecutores"{% elsif ghes < 3.2 %}"Ejecutores auto-hospedados"{% endif %}, haz clic en **Agregar nuevo** y luego en **Grupo nuevo**.
@@ -76,7 +76,7 @@ Cuando creas un grupo, debes elegir una política que defina qué repositorios t
**Advertencia**
- {% indented_data_reference reusables.github-actions.self-hosted-runner-security spaces=3 %}
+ {% indented_data_reference reusables.actions.self-hosted-runner-security spaces=3 %}
Para obtener más información, consulta "[Acerca de los ejecutores autoalojados](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)."
@@ -100,18 +100,18 @@ Cuando creas un grupo, debes elegir la política que defina qué organizaciones
{% data reusables.enterprise-accounts.actions-tab %}
{% data reusables.enterprise-accounts.actions-runner-groups-tab %}
1. Haz clic en **Grupo de ejecución nuevo**.
- {% data reusables.github-actions.runner-group-assign-policy-org %}
+ {% data reusables.actions.runner-group-assign-policy-org %}
{% warning %}
**Advertencia**
- {% indented_data_reference reusables.github-actions.self-hosted-runner-security spaces=3 %}
+ {% indented_data_reference reusables.actions.self-hosted-runner-security spaces=3 %}
Para obtener más información, consulta "[Acerca de los ejecutores autoalojados](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)."
{% endwarning %}
-{% data reusables.github-actions.self-hosted-runner-create-group %}
+{% data reusables.actions.self-hosted-runner-create-group %}
{% elsif ghae or ghes < 3.4 %}
{% data reusables.enterprise-accounts.access-enterprise %}
{% data reusables.enterprise-accounts.policies-tab %}
@@ -128,7 +128,7 @@ Cuando creas un grupo, debes elegir la política que defina qué organizaciones
**Advertencia**
- {% indented_data_reference reusables.github-actions.self-hosted-runner-security spaces=3 %}
+ {% indented_data_reference reusables.actions.self-hosted-runner-security spaces=3 %}
Para obtener más información, consulta "[Acerca de los ejecutores autoalojados](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)."
@@ -143,21 +143,21 @@ Cuando creas un grupo, debes elegir la política que defina qué organizaciones
Puedes actualizar la política de acceso de un grupo ejecutor o renombrarlo.
{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5091 %}
-{% data reusables.github-actions.self-hosted-runner-groups-navigate-to-repo-org-enterprise %}
-{% data reusables.github-actions.settings-sidebar-actions-runner-groups-selection %}
+{% data reusables.actions.self-hosted-runner-groups-navigate-to-repo-org-enterprise %}
+{% data reusables.actions.settings-sidebar-actions-runner-groups-selection %}
1. Modifica las opciones de acceso o cambia el nombre del grupo de ejecutores.
{% warning %}
**Advertencia**
- {% indented_data_reference reusables.github-actions.self-hosted-runner-security spaces=3 %}
+ {% indented_data_reference reusables.actions.self-hosted-runner-security spaces=3 %}
Para obtener más información, consulta "[Acerca de los ejecutores autoalojados](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)."
{% endwarning %}
{% elsif ghae or ghes < 3.4 %}
-{% data reusables.github-actions.self-hosted-runner-configure-runner-group-access %}
+{% data reusables.actions.self-hosted-runner-configure-runner-group-access %}
{% endif %}
{% ifversion ghec or ghes or ghae %}
@@ -179,7 +179,7 @@ Could not find any self-hosted runner group named "rg-runnergroup".
Si no especificas un grupo de ejecutores durante el proceso de registro, tus ejecutores auto-hospedados nuevos se asignarán automáticamente al grupo predeterminado y después se moverán a otro grupo.
-{% data reusables.github-actions.self-hosted-runner-navigate-to-org-enterprise %}
+{% data reusables.actions.self-hosted-runner-navigate-to-org-enterprise %}
{% ifversion ghec or ghes > 3.3 or ghae-issue-5091 %}
1. En la lista de "Ejecutores", haz clic en aquél que quieras configurar.
2. Selecciona el menú desplegable del grupo de ejecutores.
@@ -195,7 +195,7 @@ Si no especificas un grupo de ejecutores durante el proceso de registro, tus eje
Los ejecutores auto-hospedados se devuelven automáticamente al grupo predeterminado cuando su grupo se elimina.
{% ifversion ghes > 3.1 or ghae or ghec %}
-{% data reusables.github-actions.self-hosted-runner-groups-navigate-to-repo-org-enterprise %}
+{% data reusables.actions.self-hosted-runner-groups-navigate-to-repo-org-enterprise %}
1. En la lista de grupos, a la derecha del grupo que quieras borrar, haz clic en {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}.
2. Para eliminar el grupo, da clic en **Eliminar grupo**.
3. Revisa el mensaje de confirmación y da clic en **Eliminar este grupo de ejecutores**.
diff --git a/translations/es-ES/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md b/translations/es-ES/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md
index 8621853dcd14..9d6baa9ecfe7 100644
--- a/translations/es-ES/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md
+++ b/translations/es-ES/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md
@@ -21,10 +21,10 @@ shortTitle: Monitor & troubleshoot
## Checking the status of a self-hosted runner
-{% data reusables.github-actions.self-hosted-runner-management-permissions-required %}
+{% data reusables.actions.self-hosted-runner-management-permissions-required %}
-{% data reusables.github-actions.self-hosted-runner-navigate-repo-and-org %}
-{% data reusables.github-actions.settings-sidebar-actions-runners %}
+{% data reusables.actions.self-hosted-runner-navigate-repo-and-org %}
+{% data reusables.actions.settings-sidebar-actions-runners %}
1. Under {% ifversion fpt or ghes > 3.1 or ghae or ghec %}"Runners"{% else %}"Self-hosted runners"{% endif %}, you can view a list of registered runners, including the runner's name, labels, and status.
The status can be one of the following:
@@ -46,12 +46,12 @@ For example:
{% mac %}
-{% data reusables.github-actions.self-hosted-runner-check-mac-linux %}
+{% data reusables.actions.self-hosted-runner-check-mac-linux %}
{% endmac %}
{% linux %}
-{% data reusables.github-actions.self-hosted-runner-check-mac-linux %}
+{% data reusables.actions.self-hosted-runner-check-mac-linux %}
{% endlinux %}
{% windows %}
diff --git a/translations/es-ES/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md b/translations/es-ES/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md
index 6c392b79c821..09927c29589d 100644
--- a/translations/es-ES/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md
+++ b/translations/es-ES/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md
@@ -21,54 +21,54 @@ shortTitle: Elimina ejecutores auto-hospedados
{% note %}
-**Nota:** {% data reusables.github-actions.self-hosted-runner-removal-impact %}
+**Nota:**{% data reusables.actions.self-hosted-runner-removal-impact %}
-{% data reusables.github-actions.self-hosted-runner-auto-removal %}
+{% data reusables.actions.self-hosted-runner-auto-removal %}
{% endnote %}
Para eliminar un ejecutor autoalojado de un repositorio de usuario, debes ser el propietario del repositorio. Para los repositorios organizacionales, debes ser el propietario de la organización o tener acceso de administrador a éste. Recomendamos que también tengas acceso a la máquina del ejecutor auto-hospedado. Para obtener más información sobre cómo eliminar un ejecutor auto-hospedado con la API de REST, consulta la sección "[Ejecutores auto-hospedados](/rest/reference/actions#self-hosted-runners)".
-{% data reusables.github-actions.self-hosted-runner-reusing %}
+{% data reusables.actions.self-hosted-runner-reusing %}
{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5091 %}
{% data reusables.repositories.navigate-to-repo %}
{% data reusables.repositories.sidebar-settings %}
-{% data reusables.github-actions.settings-sidebar-actions %}
-{% data reusables.github-actions.settings-sidebar-actions-runners-updated %}
-{% data reusables.github-actions.settings-sidebar-actions-runner-selection %}
-{% data reusables.github-actions.self-hosted-runner-removing-a-runner-updated %}
+{% data reusables.actions.settings-sidebar-actions %}
+{% data reusables.actions.settings-sidebar-actions-runners-updated %}
+{% data reusables.actions.settings-sidebar-actions-runner-selection %}
+{% data reusables.actions.self-hosted-runner-removing-a-runner-updated %}
{% elsif ghae or ghes < 3.4 %}
{% data reusables.repositories.navigate-to-repo %}
{% data reusables.repositories.sidebar-settings %}
-{% data reusables.github-actions.settings-sidebar-actions-runners %}
-{% data reusables.github-actions.self-hosted-runner-removing-a-runner %}
+{% data reusables.actions.settings-sidebar-actions-runners %}
+{% data reusables.actions.self-hosted-runner-removing-a-runner %}
{% endif %}
## Eliminar el ejecutor de una organización
{% note %}
-**Nota:** {% data reusables.github-actions.self-hosted-runner-removal-impact %}
+**Nota:**{% data reusables.actions.self-hosted-runner-removal-impact %}
-{% data reusables.github-actions.self-hosted-runner-auto-removal %}
+{% data reusables.actions.self-hosted-runner-auto-removal %}
{% endnote %}
Para eliminar el ejecutor auto-hospedado de una organización, debes ser el propietario de la misma. Recomendamos que también tengas acceso a la máquina del ejecutor auto-hospedado. Para obtener más información sobre cómo eliminar un ejecutor auto-hospedado con la API de REST, consulta la sección "[Ejecutores auto-hospedados](/rest/reference/actions#self-hosted-runners)".
-{% data reusables.github-actions.self-hosted-runner-reusing %}
+{% data reusables.actions.self-hosted-runner-reusing %}
{% ifversion fpt or ghes > 3.3 or ghec %}
{% data reusables.organizations.navigate-to-org %}
{% data reusables.organizations.org_settings %}
-{% data reusables.github-actions.settings-sidebar-actions %}
-{% data reusables.github-actions.settings-sidebar-actions-runners-updated %}
-{% data reusables.github-actions.settings-sidebar-actions-runner-selection %}
-{% data reusables.github-actions.self-hosted-runner-removing-a-runner-updated %}
+{% data reusables.actions.settings-sidebar-actions %}
+{% data reusables.actions.settings-sidebar-actions-runners-updated %}
+{% data reusables.actions.settings-sidebar-actions-runner-selection %}
+{% data reusables.actions.self-hosted-runner-removing-a-runner-updated %}
{% elsif ghes < 3.4 or ghae %}
{% data reusables.organizations.navigate-to-org %}
{% data reusables.organizations.org_settings %}
-{% data reusables.github-actions.settings-sidebar-actions-runners %}
-{% data reusables.github-actions.self-hosted-runner-removing-a-runner %}
+{% data reusables.actions.settings-sidebar-actions-runners %}
+{% data reusables.actions.self-hosted-runner-removing-a-runner %}
{% endif %}
## Eliminar un ejecutor de una empresa
@@ -80,27 +80,27 @@ Si utilizas
{% ifversion ghec or ghes or ghae %}
{% note %}
-**Nota:** {% data reusables.github-actions.self-hosted-runner-removal-impact %}
+**Nota:**{% data reusables.actions.self-hosted-runner-removal-impact %}
-{% data reusables.github-actions.self-hosted-runner-auto-removal %}
+{% data reusables.actions.self-hosted-runner-auto-removal %}
{% endnote %}
Para eliminar a un ejecutor auto-hospedado de una empresa, debes ser un propietario de esta. Recomendamos que también tengas acceso a la máquina del ejecutor auto-hospedado. Para obtener más información sobre cómo eliminar un ejecutor auto-hospedado con la API de REST, consulta las terminales empresariales en la [API de REST de {% data variables.product.prodname_actions %}](/rest/reference/actions#self-hosted-runners).
-{% data reusables.github-actions.self-hosted-runner-reusing %}
+{% data reusables.actions.self-hosted-runner-reusing %}
{% ifversion ghec or ghes > 3.3 or ghae-issue-5091 %}
{% data reusables.enterprise-accounts.access-enterprise %}
{% data reusables.enterprise-accounts.policies-tab %}
{% data reusables.enterprise-accounts.actions-tab %}
{% data reusables.enterprise-accounts.actions-runners-tab %}
-{% data reusables.github-actions.settings-sidebar-actions-runner-selection %}
-{% data reusables.github-actions.self-hosted-runner-removing-a-runner-updated %}
+{% data reusables.actions.settings-sidebar-actions-runner-selection %}
+{% data reusables.actions.self-hosted-runner-removing-a-runner-updated %}
{% elsif ghae or ghes < 3.4 %}
{% data reusables.enterprise-accounts.access-enterprise %}
{% data reusables.enterprise-accounts.policies-tab %}
{% data reusables.enterprise-accounts.actions-tab %}
{% data reusables.enterprise-accounts.actions-runners-tab %}
-{% data reusables.github-actions.self-hosted-runner-removing-a-runner %}
+{% data reusables.actions.self-hosted-runner-removing-a-runner %}
{% endif %}
{% endif %}
diff --git a/translations/es-ES/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md b/translations/es-ES/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md
index e3b4ce03b526..37d3e9c0d408 100644
--- a/translations/es-ES/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md
+++ b/translations/es-ES/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md
@@ -16,54 +16,54 @@ shortTitle: Etiquetar ejecutores
Para obtener información sobre cómo utilizar las etiquetas para rutear jobs a tipos específicos de ejecutores auto-hospedados, consulta la sección "[Utilizar ejecutores auto-hospedados en un flujo de trabajo](/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow)".
-{% data reusables.github-actions.self-hosted-runner-management-permissions-required %}
+{% data reusables.actions.self-hosted-runner-management-permissions-required %}
## Crear una etiqueta personalizada
{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5091 %}
-{% data reusables.github-actions.self-hosted-runner-navigate-to-repo-org-enterprise %}
- {% data reusables.github-actions.settings-sidebar-actions-runner-selection %}
+{% data reusables.actions.self-hosted-runner-navigate-to-repo-org-enterprise %}
+ {% data reusables.actions.settings-sidebar-actions-runner-selection %}
1. En la sección de "Etiquetas", haz clic en {% octicon "gear" aria-label="The Gear icon" %}.
- 1. En el campo de "Encuentra o crea una etiqueta", teclea el nombre de tu etiqueta nueva y haz clic en **Crear etiqueta nueva**. La etiqueta personalizada se creará y asignará al ejecutor auto-hospedado. Las etiquetas personalizadas pueden eliminarse de los ejecutores auto-hospedados, pero actualmente no pueden eliminarse manualmente. {% data reusables.github-actions.actions-unused-labels %}
+ 1. En el campo de "Encuentra o crea una etiqueta", teclea el nombre de tu etiqueta nueva y haz clic en **Crear etiqueta nueva**. La etiqueta personalizada se creará y asignará al ejecutor auto-hospedado. Las etiquetas personalizadas pueden eliminarse de los ejecutores auto-hospedados, pero actualmente no pueden eliminarse manualmente. {% data reusables.actions.actions-unused-labels %}
{% elsif ghae or ghes < 3.4 %}
-{% data reusables.github-actions.self-hosted-runner-navigate-to-repo-org-enterprise %}
-{% data reusables.github-actions.self-hosted-runner-list %}
-{% data reusables.github-actions.self-hosted-runner-list-group %}
-{% data reusables.github-actions.self-hosted-runner-labels-view-assigned-labels %}
+{% data reusables.actions.self-hosted-runner-navigate-to-repo-org-enterprise %}
+{% data reusables.actions.self-hosted-runner-list %}
+{% data reusables.actions.self-hosted-runner-list-group %}
+{% data reusables.actions.self-hosted-runner-labels-view-assigned-labels %}
1. En el campo "Filtrar etiquetas", teclea el nombre de tu nueva etiqueta y da clic en **Crear nueva etiqueta**. 
-La etiqueta personalizada se creará y asignará al ejecutor auto-hospedado. Las etiquetas personalizadas pueden eliminarse de los ejecutores auto-hospedados, pero actualmente no pueden eliminarse manualmente. {% data reusables.github-actions.actions-unused-labels %}
+La etiqueta personalizada se creará y asignará al ejecutor auto-hospedado. Las etiquetas personalizadas pueden eliminarse de los ejecutores auto-hospedados, pero actualmente no pueden eliminarse manualmente. {% data reusables.actions.actions-unused-labels %}
{% endif %}
## Asignar una etiqueta a un ejecutor auto-hospedado
{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5091 %}
-{% data reusables.github-actions.self-hosted-runner-navigate-to-repo-org-enterprise %}
-{% data reusables.github-actions.settings-sidebar-actions-runner-selection %}
-{% data reusables.github-actions.runner-label-settings %}
+{% data reusables.actions.self-hosted-runner-navigate-to-repo-org-enterprise %}
+{% data reusables.actions.settings-sidebar-actions-runner-selection %}
+{% data reusables.actions.runner-label-settings %}
1. Para asignar una etiqueta a tu ejecutor auto-hospedado, en el campo de "Encuentra o crea una etiqueta", haz clic en ella.
{% elsif ghae or ghes < 3.4 %}
-{% data reusables.github-actions.self-hosted-runner-navigate-to-repo-org-enterprise %}
-{% data reusables.github-actions.self-hosted-runner-list %}
-{% data reusables.github-actions.self-hosted-runner-list-group %}
-{% data reusables.github-actions.self-hosted-runner-labels-view-assigned-labels %}
+{% data reusables.actions.self-hosted-runner-navigate-to-repo-org-enterprise %}
+{% data reusables.actions.self-hosted-runner-list %}
+{% data reusables.actions.self-hosted-runner-list-group %}
+{% data reusables.actions.self-hosted-runner-labels-view-assigned-labels %}
1. Da clic en la etiqueta para asignarla a tu ejecutor auto-hospedado.
{% endif %}
## Eliminar una etiqueta personalizada de un ejecutor auto-hospedado
{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5091 %}
-{% data reusables.github-actions.self-hosted-runner-navigate-to-repo-org-enterprise %}
-{% data reusables.github-actions.settings-sidebar-actions-runner-selection %}
-{% data reusables.github-actions.runner-label-settings %}
+{% data reusables.actions.self-hosted-runner-navigate-to-repo-org-enterprise %}
+{% data reusables.actions.settings-sidebar-actions-runner-selection %}
+{% data reusables.actions.runner-label-settings %}
1. En el campo "Encuentra o crea una etiqueta", las etiquetas asignadas se marcan con el
icono {% octicon "check" aria-label="The Check icon" %}. Haz clic en una etiqueta marcada para desasignarla de tu ejecutor auto-hospedado.
{% elsif ghae or ghes < 3.4 %}
-{% data reusables.github-actions.self-hosted-runner-navigate-to-repo-org-enterprise %}
-{% data reusables.github-actions.self-hosted-runner-list %}
-{% data reusables.github-actions.self-hosted-runner-list-group %}
-{% data reusables.github-actions.self-hosted-runner-labels-view-assigned-labels %}
-1. Da clic en la etiqueta asignada para eliminarla de tu ejecutor auto-hospedado. {% data reusables.github-actions.actions-unused-labels %}
+{% data reusables.actions.self-hosted-runner-navigate-to-repo-org-enterprise %}
+{% data reusables.actions.self-hosted-runner-list %}
+{% data reusables.actions.self-hosted-runner-list-group %}
+{% data reusables.actions.self-hosted-runner-labels-view-assigned-labels %}
+1. Da clic en la etiqueta asignada para eliminarla de tu ejecutor auto-hospedado. {% data reusables.actions.actions-unused-labels %}
{% endif %}
## Utilizar el script de configuración para crear y asignar etiquetas
diff --git a/translations/es-ES/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md b/translations/es-ES/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md
index 67c98f9aa699..b6263760e740 100644
--- a/translations/es-ES/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md
+++ b/translations/es-ES/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md
@@ -23,7 +23,7 @@ Para obtener más información sobre cómo crear etiquetas personalizadas y pred
Las etiquetas te permiten enviar jobs de flujo de trabajo a tipos específicos de ejecutores auto-hospedados, de acuerdo con sus características compartidas. Por ejemplo, si tu job requiere una componente de hardware o paquete de software específico, puedes asignar una etiqueta personalizada a un ejecutor y después configurar tu job para que solo se ejecute en los ejecutores con esta etiqueta.
-{% data reusables.github-actions.self-hosted-runner-labels-runs-on %}
+{% data reusables.actions.self-hosted-runner-labels-runs-on %}
Para obtener más información, consulta "[Sintaxis de flujo de trabajo para {% data variables.product.prodname_actions %}](/github/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idruns-on)."
diff --git a/translations/es-ES/content/actions/learn-github-actions/contexts.md b/translations/es-ES/content/actions/learn-github-actions/contexts.md
index ad0f5dccd4b4..e3ff6f9ca30f 100644
--- a/translations/es-ES/content/actions/learn-github-actions/contexts.md
+++ b/translations/es-ES/content/actions/learn-github-actions/contexts.md
@@ -31,7 +31,7 @@ You can access contexts using the expression syntax. For more information, see "
`${{ }}`
{% endraw %}
-{% data reusables.github-actions.context-injection-warning %}
+{% data reusables.actions.context-injection-warning %}
| Context name | Type | Description |
|---------------|------|-------------|
@@ -59,7 +59,7 @@ In order to use property dereference syntax, the property name must:
### Determining when to use contexts
-{% data reusables.github-actions.using-context-or-environment-variables %}
+{% data reusables.actions.using-context-or-environment-variables %}
### Context availability
@@ -142,7 +142,7 @@ The following table indicates where each context and special function can be use
You can print the contents of contexts to the log for debugging. The [`toJSON` function](/actions/learn-github-actions/expressions#tojson) is required to pretty-print JSON objects to the log.
-{% data reusables.github-actions.github-context-warning %}
+{% data reusables.actions.github-context-warning %}
{% raw %}
```yaml{:copy}
@@ -173,8 +173,8 @@ jobs:
The `github` context contains information about the workflow run and the event that triggered the run. You can also read most of the `github` context data in environment variables. For more information about environment variables, see "[Using environment variables](/actions/automating-your-workflow-with-github-actions/using-environment-variables)."
-{% data reusables.github-actions.github-context-warning %}
-{% data reusables.github-actions.context-injection-warning %}
+{% data reusables.actions.github-context-warning %}
+{% data reusables.actions.context-injection-warning %}
| Property name | Type | Description |
|---------------|------|-------------|
@@ -204,11 +204,11 @@ The `github` context contains information about the workflow run and the event t
| `github.repository_owner` | `string` | The repository owner's name. For example, `Codertocat`. |
| `github.repositoryUrl` | `string` | The Git URL to the repository. For example, `git://github.com/codertocat/hello-world.git`. |
| `github.retention_days` | `string` | The number of days that workflow run logs and artifacts are kept. |
-| `github.run_id` | `string` | {% data reusables.github-actions.run_id_description %} |
-| `github.run_number` | `string` | {% data reusables.github-actions.run_number_description %} |
+| `github.run_id` | `string` | {% data reusables.actions.run_id_description %} |
+| `github.run_number` | `string` | {% data reusables.actions.run_number_description %} |
{%- ifversion fpt or ghec or ghes > 3.5 or ghae-issue-4722 %}
| `github.run_attempt` | `string` | A unique number for each attempt of a particular workflow run in a repository. This number begins at 1 for the workflow run's first attempt, and increments with each re-run. |
-{% endif %}
+{%- endif %}
| `github.server_url` | `string` | The URL of the GitHub server. For example: `https://github.com`. |
| `github.sha` | `string` | The commit SHA that triggered the workflow run. |
| `github.token` | `string` | A token to authenticate on behalf of the GitHub App installed on your repository. This is functionally equivalent to the `GITHUB_TOKEN` secret. For more information, see "[Automatic token authentication](/actions/security-guides/automatic-token-authentication)." |
@@ -529,7 +529,7 @@ The `secrets` context contains the names and values of secrets that are availabl
`GITHUB_TOKEN` is a secret that is automatically created for every workflow run, and is always included in the `secrets` context. For more information, see "[Automatic token authentication](/actions/security-guides/automatic-token-authentication)."
-{% data reusables.github-actions.secrets-redaction-warning %}
+{% data reusables.actions.secrets-redaction-warning %}
| Property name | Type | Description |
|---------------|------|-------------|
@@ -551,7 +551,7 @@ The following example contents of the `secrets` context shows the automatic `GIT
### Example usage of the `secrets` context
-{% data reusables.github-actions.github_token-input-example %}
+{% data reusables.actions.github_token-input-example %}
## `strategy` context
diff --git a/translations/es-ES/content/actions/learn-github-actions/environment-variables.md b/translations/es-ES/content/actions/learn-github-actions/environment-variables.md
index 7d0160927cc6..faa0d688e92c 100644
--- a/translations/es-ES/content/actions/learn-github-actions/environment-variables.md
+++ b/translations/es-ES/content/actions/learn-github-actions/environment-variables.md
@@ -153,8 +153,8 @@ We strongly recommend that actions use environment variables to access the files
| `GITHUB_REPOSITORY_OWNER` | The repository owner's name. For example, `octocat`. |
| `GITHUB_RETENTION_DAYS` | The number of days that workflow run logs and artifacts are kept. For example, `90`. |
| `GITHUB_RUN_ATTEMPT` | A unique number for each attempt of a particular workflow run in a repository. This number begins at 1 for the workflow run's first attempt, and increments with each re-run. For example, `3`. |
-| `GITHUB_RUN_ID` | {% data reusables.github-actions.run_id_description %} For example, `1658821493`. |
-| `GITHUB_RUN_NUMBER` | {% data reusables.github-actions.run_number_description %} For example, `3`. |
+| `GITHUB_RUN_ID` | {% data reusables.actions.run_id_description %} For example, `1658821493`. |
+| `GITHUB_RUN_NUMBER` | {% data reusables.actions.run_number_description %} For example, `3`. |
| `GITHUB_SERVER_URL`| The URL of the {% data variables.product.product_name %} server. For example: `https://{% data variables.product.product_url %}`.
| `GITHUB_SHA` | The commit SHA that triggered the workflow. For example, `ffac537e6cbbf934b08745a378932722df287a53`. |
| `GITHUB_WORKFLOW` | The name of the workflow. For example, `My test workflow`. If the workflow file doesn't specify a `name`, the value of this variable is the full path of the workflow file in the repository. |
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 ad84017c60d0..9db783d4847e 100644
--- a/translations/es-ES/content/actions/learn-github-actions/expressions.md
+++ b/translations/es-ES/content/actions/learn-github-actions/expressions.md
@@ -25,9 +25,9 @@ Debes usar una sintaxis específica para decirle a {% data variables.product.pro
`${{ }}`
{% endraw %}
-{% data reusables.github-actions.expression-syntax-if %} Para obtener más información acerca de los condicionales `if`, consulta la sección "[sintaxis de flujo de trabajo para {% data variables.product.prodname_actions %}](/articles/workflow-syntax-for-github-actions/#jobsjob_idif)".
+{% data reusables.actions.expression-syntax-if %} Para obtener más información acerca de los condicionales `if`, consulta la sección "[sintaxis de flujo de trabajo para {% data variables.product.prodname_actions %}](/articles/workflow-syntax-for-github-actions/#jobsjob_idif)".
-{% data reusables.github-actions.context-injection-warning %}
+{% data reusables.actions.context-injection-warning %}
#### Expresión de ejemplo en un condicional `if`
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 4d7d9523edf2..7b9576e6fb4e 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
@@ -254,7 +254,7 @@ Para entender cómo funciona la facturación de las {% data variables.product.pr
## Contactar con soporte técnico
-{% data reusables.github-actions.contacting-support %}
+{% data reusables.actions.contacting-support %}
## Leer más
diff --git a/translations/es-ES/content/actions/learn-github-actions/usage-limits-billing-and-administration.md b/translations/es-ES/content/actions/learn-github-actions/usage-limits-billing-and-administration.md
index a5e581c2a01a..930df58646a2 100644
--- a/translations/es-ES/content/actions/learn-github-actions/usage-limits-billing-and-administration.md
+++ b/translations/es-ES/content/actions/learn-github-actions/usage-limits-billing-and-administration.md
@@ -21,7 +21,7 @@ shortTitle: Límites & facturación de los flujos de trabajo
{% data reusables.repositories.about-github-actions %} Para obtener más información, consulta las secciones "[Entender las {% data variables.product.prodname_actions %}](/actions/learn-github-actions/understanding-github-actions){% ifversion fpt %}".{% elsif ghes or ghec %}" y "[Acerca de {% data variables.product.prodname_actions %} para las empresas](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises)".{% endif %}
{% ifversion fpt or ghec %}
-{% data reusables.github-actions.actions-billing %} Para obtener más información, consulta "[Acerca de la facturación de {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions/about-billing-for-github-actions)".
+{% data reusables.actions.actions-billing %} Para obtener más información, consulta "[Acerca de la facturación de {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions/about-billing-for-github-actions)".
{% else %}
El uso de GitHub Actions es gratuito para las instancias de {% data variables.product.prodname_ghe_server %} que utilizan ejecutores auto-hospedados. Para obtener más información, consulta "[Acerca de los ejecutores autoalojados](/actions/hosting-your-own-runners/about-self-hosted-runners)."
{% endif %}
@@ -47,8 +47,8 @@ Hay algunos límites de uso de {% data variables.product.prodname_actions %} cua
{% endnote %}
- **Tiempo de ejecución de jobs** - Cada job en un flujo de trabajo puede ejecutarse hasta por 6 horas en tiempo de ejecución. Si un job llega a este límite, éste se terminará y fallará en completarse.
-{% data reusables.github-actions.usage-workflow-run-time %}
-{% data reusables.github-actions.usage-api-requests %}
+{% data reusables.actions.usage-workflow-run-time %}
+{% data reusables.actions.usage-api-requests %}
- **Jobs simultáneos** - La cantidad de jobs que puedes ejecutar simultáneamente en tu cuenta depende de tu plan de GitHub, como se indica en la siguiente tabla. Si eso se excede, cualquier job adicional se pondrá en cola de espera.
| Plan de GitHub | Jobs simultáneos totales | Jobs simultáneos de macOS máximos |
@@ -57,8 +57,8 @@ Hay algunos límites de uso de {% data variables.product.prodname_actions %} cua
| Pro | 40 | 5 |
| Team | 60 | 5 |
| Empresa | 180 | 50 |
-- **Matiz de jobs** - {% data reusables.github-actions.usage-matrix-limits %}
-{% data reusables.github-actions.usage-workflow-queue-limits %}
+- **Matiz de jobs** - {% data reusables.actions.usage-matrix-limits %}
+{% data reusables.actions.usage-workflow-queue-limits %}
{% else %}
Los límites de uso aplican a los ejecutores auto-hospedados. Para obtener más información, consulta "[Acerca de los ejecutores autoalojados](/actions/hosting-your-own-runners/about-self-hosted-runners/#usage-limits)."
@@ -94,7 +94,7 @@ Para obtener más información, consulta:
## Inhabilitar o limitar {% data variables.product.prodname_actions %} para tu repositorio u organización
-{% data reusables.github-actions.disabling-github-actions %}
+{% data reusables.actions.disabling-github-actions %}
Para obtener más información, consulta:
- "[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)"
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 a9fd16dd98da..76fea1a69e3d 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
@@ -22,7 +22,7 @@ shortTitle: Eliminar los artefactos de un flujo de trabajo
{% data reusables.repositories.permissions-statement-write %}
-{% data reusables.github-actions.artifact-log-retention-statement %}
+{% data reusables.actions.artifact-log-retention-statement %}
{% data reusables.repositories.navigate-to-repo %}
{% data reusables.repositories.actions-tab %}
diff --git a/translations/es-ES/content/actions/migrating-to-github-actions/migrating-from-travis-ci-to-github-actions.md b/translations/es-ES/content/actions/migrating-to-github-actions/migrating-from-travis-ci-to-github-actions.md
index 1ae8230e127f..b8d4c8efe537 100644
--- a/translations/es-ES/content/actions/migrating-to-github-actions/migrating-from-travis-ci-to-github-actions.md
+++ b/translations/es-ES/content/actions/migrating-to-github-actions/migrating-from-travis-ci-to-github-actions.md
@@ -179,7 +179,7 @@ git:
Tanto {% data variables.product.prodname_actions %} como Travis CI pueden agregar variables de ambiente personalizadas a una matriz de pruebas, lo cual te permite referirte a la variable en un paso subsecuente.
-En {% data variables.product.prodname_actions %}, puedes utilizar la clave `include` para agregar variables de ambiente personalizadas a una matriz. {% data reusables.github-actions.matrix-variable-example %}
+En {% data variables.product.prodname_actions %}, puedes utilizar la clave `include` para agregar variables de ambiente personalizadas a una matriz. {% data reusables.actions.matrix-variable-example %}
## Características clave en {% data variables.product.prodname_actions %}
diff --git a/translations/es-ES/content/actions/monitoring-and-troubleshooting-workflows/about-monitoring-and-troubleshooting.md b/translations/es-ES/content/actions/monitoring-and-troubleshooting-workflows/about-monitoring-and-troubleshooting.md
index 06825d1e267d..d10246169c28 100644
--- a/translations/es-ES/content/actions/monitoring-and-troubleshooting-workflows/about-monitoring-and-troubleshooting.md
+++ b/translations/es-ES/content/actions/monitoring-and-troubleshooting-workflows/about-monitoring-and-troubleshooting.md
@@ -18,7 +18,7 @@ miniTocMaxHeadingLevel: 3
{% if github-runner-dashboard %}
### Monitorear tus jobs actuales en tu organización o empresa
-{% data reusables.github-actions.github-hosted-runners-check-concurrency %}
+{% data reusables.actions.github-hosted-runners-check-concurrency %}
{% endif %}
diff --git a/translations/es-ES/content/actions/monitoring-and-troubleshooting-workflows/enabling-debug-logging.md b/translations/es-ES/content/actions/monitoring-and-troubleshooting-workflows/enabling-debug-logging.md
index f40c4a4005ed..8c933e4a0c1a 100644
--- a/translations/es-ES/content/actions/monitoring-and-troubleshooting-workflows/enabling-debug-logging.md
+++ b/translations/es-ES/content/actions/monitoring-and-troubleshooting-workflows/enabling-debug-logging.md
@@ -15,12 +15,12 @@ versions:
Estas bitácoras extra se habilitan configurando los secretos en el repositorio que contiene el flujo de trabajo, así que aplicarán los mismos requisitos de los permisos:
-- {% data reusables.github-actions.permissions-statement-secrets-repository %}
+- {% data reusables.actions.permissions-statement-secrets-repository %}
{% ifversion fpt or ghes > 3.0 or ghae or ghec %}
-- {% data reusables.github-actions.permissions-statement-secrets-environment %}
+- {% data reusables.actions.permissions-statement-secrets-environment %}
{% endif %}
-- {% data reusables.github-actions.permissions-statement-secrets-organization %}
-- {% data reusables.github-actions.permissions-statement-secrets-api %}
+- {% data reusables.actions.permissions-statement-secrets-organization %}
+- {% data reusables.actions.permissions-statement-secrets-api %}
Para obtener más información sobre cómo establecer secretos, consulta la sección "[Crear y usar secretos cifrados](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)."
diff --git a/translations/es-ES/content/actions/monitoring-and-troubleshooting-workflows/using-workflow-run-logs.md b/translations/es-ES/content/actions/monitoring-and-troubleshooting-workflows/using-workflow-run-logs.md
index dcbd93d94ada..0f80452fb7f2 100644
--- a/translations/es-ES/content/actions/monitoring-and-troubleshooting-workflows/using-workflow-run-logs.md
+++ b/translations/es-ES/content/actions/monitoring-and-troubleshooting-workflows/using-workflow-run-logs.md
@@ -19,7 +19,7 @@ Si la ejecución está completa, puedes ver si el resultado fue exitoso, fallido
{% data variables.product.prodname_actions %} usa la API de verificaciones para generar estados, resultados y registros para un flujo de trabajo. {% data variables.product.prodname_dotcom %} crea una nueva comprobación de suite para cada ejecución de flujo de trabajo. La comprobación de suite contiene una ejecución de comprobación para cada trabajo en el flujo de trabajo, y cada trabajo incluye diferentes pasos. {% data variables.product.prodname_actions %} se ejecutan como un paso en un flujo de trabajo. Para obtener más información acerca de la API de Verificaciones, consulta la sección "[Verificaciones](/rest/reference/checks)".
-{% data reusables.github-actions.invalid-workflow-files %}
+{% data reusables.actions.invalid-workflow-files %}
## Ver registros para diagnosticar fallas
diff --git a/translations/es-ES/content/actions/publishing-packages/publishing-docker-images.md b/translations/es-ES/content/actions/publishing-packages/publishing-docker-images.md
index b33291634c8c..f54f8528f3c9 100644
--- a/translations/es-ES/content/actions/publishing-packages/publishing-docker-images.md
+++ b/translations/es-ES/content/actions/publishing-packages/publishing-docker-images.md
@@ -50,7 +50,7 @@ En esta guía, utilizaremos la acción `build-push-action` de Docker para compil
## Publicar imágenes en Docker Hub
-{% data reusables.github-actions.release-trigger-workflow %}
+{% data reusables.actions.release-trigger-workflow %}
En el flujo de trabajo de ejemplo a continuación, utilizamos las acciones `login-action` y `build-push-action` para crear la imagen de Docker y, si la compilación es exitosa, subimos la imagen compilada a Docker Hub.
@@ -108,7 +108,7 @@ El flujo de trabajo anterior verifica el repositorio de {% data variables.produc
## Publicar imágenes en {% data variables.product.prodname_registry %}
-{% data reusables.github-actions.release-trigger-workflow %}
+{% data reusables.actions.release-trigger-workflow %}
En el siguiente ejemplo de flujo de trabajo, utilizamos las acciones `login-action` {% ifversion fpt or ghec %}, `metadata-action`,{% endif %} y `build-push-action` de Docker para crear la imagen de Docker y, si la compilación tiene éxito, sube la imagen cargada al {% data variables.product.prodname_registry %}.
diff --git a/translations/es-ES/content/actions/publishing-packages/publishing-java-packages-with-gradle.md b/translations/es-ES/content/actions/publishing-packages/publishing-java-packages-with-gradle.md
index c1397f78259c..631a7b59562f 100644
--- a/translations/es-ES/content/actions/publishing-packages/publishing-java-packages-with-gradle.md
+++ b/translations/es-ES/content/actions/publishing-packages/publishing-java-packages-with-gradle.md
@@ -23,7 +23,7 @@ shortTitle: Paquetes de Java con Gradle
## Introducción
-{% data reusables.github-actions.publishing-java-packages-intro %}
+{% data reusables.actions.publishing-java-packages-intro %}
## Prerrequisitos
@@ -104,7 +104,7 @@ jobs:
MAVEN_PASSWORD: {% raw %}${{ secrets.OSSRH_TOKEN }}{% endraw %}
```
-{% data reusables.github-actions.gradle-workflow-steps %}
+{% data reusables.actions.gradle-workflow-steps %}
1. Ejecuta la acción [`gradle/gradle-build-action`](https://github.com/gradle/gradle-build-action) con el argumento `publish` para publicar en el repositorio `OSSRH` de Maven. La variable de entorno `MAVEN_USERNAME` se establecerá con los contenidos de tu `OSSRH_USERNAME` secreto, y la variable de entorno `MAVEN_PASSWORD` se establecerá con los contenidos de tu `OSSRH_TOKEN` secreto.
Para obtener más información acerca del uso de secretos en tu flujo de trabajo, consulta "[Crear y usar secretos cifrados](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)".
@@ -115,7 +115,7 @@ Cada vez que creas un lanzamiento nuevo, puedes desencadenar un flujo de trabajo
Puedes definir un nuevo repositorio de Maven en el bloque de publicación de tu _build.gradle_ que apunte a {% data variables.product.prodname_registry %}. En esa configuración de repositorio, también puedes aprovechar las variables de entorno establecidas en tu ejecución de flujo de trabajo de CI. Puedes usar la variable de entorno `GITHUB_ACTOR` como nombre de usuario y puedes establecer la variable de entorno `GITHUB_TOKEN` con tu `GITHUB_TOKEN` secreto.
-{% data reusables.github-actions.github-token-permissions %}
+{% data reusables.actions.github-token-permissions %}
Por ejemplo, si tu organización se llama "octocat" y tu repositorio se llama "hello-world", entonces la configuración {% data variables.product.prodname_registry %} en _build.gradle_ tendría un aspecto similar al ejemplo a continuación.
@@ -174,7 +174,7 @@ jobs:
GITHUB_TOKEN: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
```
-{% data reusables.github-actions.gradle-workflow-steps %}
+{% data reusables.actions.gradle-workflow-steps %}
1. Ejecuta la acción [`gradle/gradle-build-action`](https://github.com/gradle/gradle-build-action) con el argumento `publish` para publicar al {% data variables.product.prodname_registry %}. La variable de entorno `GITHUB_TOKEN` se establecerá con el contenido del `GITHUB_TOKEN` secreto. {% ifversion fpt or ghes > 3.1 or ghae or ghec %}La clave de `permissions` especifica el acceso que permitirá el secreto del `GITHUB_TOKEN`.{% endif %}
Para obtener más información acerca del uso de secretos en tu flujo de trabajo, consulta "[Crear y usar secretos cifrados](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)".
@@ -255,7 +255,7 @@ jobs:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}{% endraw %}
```
-{% data reusables.github-actions.gradle-workflow-steps %}
+{% data reusables.actions.gradle-workflow-steps %}
1. Ejecuta la acción [`gradle/gradle-build-action`](https://github.com/gradle/gradle-build-action) con el argumento `publish` para publicar en el repositorio `OSSRH` de Maven y en el {% data variables.product.prodname_registry %}. La variable de entorno `MAVEN_USERNAME` se establecerá con los contenidos de tu `OSSRH_USERNAME` secreto, y la variable de entorno `MAVEN_PASSWORD` se establecerá con los contenidos de tu `OSSRH_TOKEN` secreto. La variable de entorno `GITHUB_TOKEN` se establecerá con el contenido del `GITHUB_TOKEN` secreto. {% ifversion fpt or ghes > 3.1 or ghae or ghec %}La clave de `permissions` especifica el acceso que permitirá el secreto del `GITHUB_TOKEN`.{% endif %}
Para obtener más información acerca del uso de secretos en tu flujo de trabajo, consulta "[Crear y usar secretos cifrados](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)".
diff --git a/translations/es-ES/content/actions/publishing-packages/publishing-java-packages-with-maven.md b/translations/es-ES/content/actions/publishing-packages/publishing-java-packages-with-maven.md
index caadb02fddd2..eab307afc0cf 100644
--- a/translations/es-ES/content/actions/publishing-packages/publishing-java-packages-with-maven.md
+++ b/translations/es-ES/content/actions/publishing-packages/publishing-java-packages-with-maven.md
@@ -23,7 +23,7 @@ shortTitle: Paquetes de Java con Maven
## Introducción
-{% data reusables.github-actions.publishing-java-packages-intro %}
+{% data reusables.actions.publishing-java-packages-intro %}
## Prerrequisitos
@@ -105,7 +105,7 @@ Este flujo de trabajo realiza los siguientes pasos:
1. Verifica una copia del repositorio del proyecto.
1. Configura el JDK de Java y también el archivo _settings. xml_ de Maven para agregarle autenticación al repositorio de `ossrh` utilizando las variables de entorno `MAVEN_USERNAME` y `MAVEN_PASSWORD`.
-1. {% data reusables.github-actions.publish-to-maven-workflow-step %}
+1. {% data reusables.actions.publish-to-maven-workflow-step %}
Para obtener más información acerca del uso de secretos en tu flujo de trabajo, consulta "[Crear y usar secretos cifrados](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)".
@@ -115,7 +115,7 @@ Cada vez que creas un lanzamiento nuevo, puedes desencadenar un flujo de trabajo
En este flujo de trabajo, puedes usar la acicón `setup-java`. Esta acción instala la versión determinada del JDK en el `PATH` y configura un _settings.xml_ de Maven para publicar el paquete en el {% data variables.product.prodname_registry %}. El _settings.sml_ generado define la autenticación para un servidor con una `id` de `github`, utilizando la variable de entorno `GITHUB_ACTOR` como nombre de usuario y la variable de entorno `GITHUB_TOKEN` como contraseña. Se le asigna el valor del secreto especial `GITHUB_TOKEN` a la variable de ambiente `GITHUB_TOKEN`.
-{% data reusables.github-actions.github-token-permissions %}
+{% data reusables.actions.github-token-permissions %}
Para un proyecto basado en Maven, puedes hacer uso de estas configuraciones creando un repositorio de distribución en tu archivo _pom.xml_ con una `id` de `github` que apunta a tu extremo {% data variables.product.prodname_registry %}.
@@ -165,7 +165,7 @@ Este flujo de trabajo realiza los siguientes pasos:
1. Verifica una copia del repositorio del proyecto.
1. Configura el JDK de Java y configura automáticamente el archivo _settings.xml_ de Maven para agregar autenticación para que el repositorio `github` de Maven utilice la variable de entorno `GITHUB_TOKEN`.
-1. {% data reusables.github-actions.publish-to-packages-workflow-step %}
+1. {% data reusables.actions.publish-to-packages-workflow-step %}
Para obtener más información acerca del uso de secretos en tu flujo de trabajo, consulta "[Crear y usar secretos cifrados](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)".
@@ -218,8 +218,8 @@ Este flujo de trabajo realiza los siguientes pasos:
1. Verifica una copia del repositorio del proyecto.
1. Llama al `setup-java` la primera vez. Esto configura el archivo _settings.xml_ de Maven para el repositorio `ossrh` y establece las opciones de autenticación en las variables de entorno que se definen en el siguiente paso.
-1. {% data reusables.github-actions.publish-to-maven-workflow-step %}
+1. {% data reusables.actions.publish-to-maven-workflow-step %}
1. Llama al `setup-java` la segunda vez. Esto configura automáticamente el archivo _settings.xml_ de Maven para el {% data variables.product.prodname_registry %}.
-1. {% data reusables.github-actions.publish-to-packages-workflow-step %}
+1. {% data reusables.actions.publish-to-packages-workflow-step %}
Para obtener más información acerca del uso de secretos en tu flujo de trabajo, consulta "[Crear y usar secretos cifrados](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)".
diff --git a/translations/es-ES/content/actions/publishing-packages/publishing-nodejs-packages.md b/translations/es-ES/content/actions/publishing-packages/publishing-nodejs-packages.md
index 4edf4d5293eb..fb893204ed0a 100644
--- a/translations/es-ES/content/actions/publishing-packages/publishing-nodejs-packages.md
+++ b/translations/es-ES/content/actions/publishing-packages/publishing-nodejs-packages.md
@@ -43,7 +43,7 @@ También puede ser útil tener un entendimiento básico de lo siguiente:
Los campos `Nombre` y `Versión` en el archivo *package.json* crean un identificador único que los registros usan para vincular tu paquete a un registro. Puedes agregar un resumen para la página de descripción del paquete al incluir un campo `Descripción` en el archivo *package.json*. Para obtener más información, consulta "[Crear un archivo package.json](https://docs.npmjs.com/creating-a-package-json-file) y [Crear módulos Node.js](https://docs.npmjs.com/creating-node-js-modules)"en la documentación de npm.
-Cuando existe un archivo *.npmrc* local y tiene un valor especificado de `registro`, el comando `npm publish` usa el registro configurado en el archivo *.npmrc*. {% data reusables.github-actions.setup-node-intro %}
+Cuando existe un archivo *.npmrc* local y tiene un valor especificado de `registro`, el comando `npm publish` usa el registro configurado en el archivo *.npmrc*. {% data reusables.actions.setup-node-intro %}
Puedes especificar la versión de Node.js instalada en el ejecutor utilizando la acción `setup-node`.
@@ -115,7 +115,7 @@ Sin embargo, si no proporcionas la clave del `repository`, entonces el repositor
### Autenticarse en el repositorio de destino
-Para realizar operaciones autenticadas en el registro {% data variables.product.prodname_registry %} de tu flujo de trabajo, puedes utilizar el `GITHUB_TOKEN`. {% data reusables.github-actions.github-token-permissions %}
+Para realizar operaciones autenticadas en el registro {% data variables.product.prodname_registry %} de tu flujo de trabajo, puedes utilizar el `GITHUB_TOKEN`. {% data reusables.actions.github-token-permissions %}
Si quieres publicar tu paquete en un repositorio diferente, debes utilizar un token de acceso personal (PAT) que tenga permisos de escritura en los paquetes del repositorio destino. Para obtener más información, consulta las secciones "[Crear un token de acceso personal](/github/authenticating-to-github/creating-a-personal-access-token)" y "[Secretos cifrados](/actions/reference/encrypted-secrets)".
diff --git a/translations/es-ES/content/actions/security-guides/automatic-token-authentication.md b/translations/es-ES/content/actions/security-guides/automatic-token-authentication.md
index 16a0f24f9588..a6cdabb850e1 100644
--- a/translations/es-ES/content/actions/security-guides/automatic-token-authentication.md
+++ b/translations/es-ES/content/actions/security-guides/automatic-token-authentication.md
@@ -39,11 +39,11 @@ You can use the `GITHUB_TOKEN` by using the standard syntax for referencing secr
{% endnote %}
{% endif %}
-{% data reusables.github-actions.actions-do-not-trigger-workflows %}
+{% data reusables.actions.actions-do-not-trigger-workflows %}
### Example 1: passing the `GITHUB_TOKEN` as an input
-{% data reusables.github-actions.github_token-input-example %}
+{% data reusables.actions.github_token-input-example %}
### Example 2: calling the REST API
@@ -123,7 +123,7 @@ You can see the permissions that `GITHUB_TOKEN` had for a specific job in the "S
You can use the `permissions` key in your workflow file to modify permissions for the `GITHUB_TOKEN` for an entire workflow or for individual jobs. This allows you to configure the minimum required permissions for a workflow or job. When the `permissions` key is used, all unspecified permissions are set to no access, with the exception of the `metadata` scope, which always gets read access.
-{% data reusables.github-actions.forked-write-permission %}
+{% data reusables.actions.forked-write-permission %}
The two workflow examples earlier in this article show the `permissions` key being used at the workflow level, and at the job level. In [Example 1](#example-1-passing-the-github_token-as-an-input) the two permissions are specified for the entire workflow. In [Example 2](#example-2-calling-the-rest-api) write access is granted for one scope for a single job.
diff --git a/translations/es-ES/content/actions/security-guides/encrypted-secrets.md b/translations/es-ES/content/actions/security-guides/encrypted-secrets.md
index 29f4b70e9dfb..a3ca1d7ebc71 100644
--- a/translations/es-ES/content/actions/security-guides/encrypted-secrets.md
+++ b/translations/es-ES/content/actions/security-guides/encrypted-secrets.md
@@ -21,7 +21,7 @@ versions:
Los secretos son variables de ambiente cifradas que creas en una organización{% ifversion fpt or ghes > 3.0 or ghae or ghec %}, repositorio, o ambiente de repositorio{% else %} o repositorio{% endif %}. Los secretos que creas están disponibles para utilizarse en los flujos de trabajo de {% data variables.product.prodname_actions %}. {% data variables.product.prodname_dotcom %} utiliza una [caja sellada de libsodium](https://libsodium.gitbook.io/doc/public-key_cryptography/sealed_boxes) para ayudarte a garantizar que los secretos se cifran antes de llegar a {% data variables.product.prodname_dotcom %} y que permanezcan cifrados hasta que los utilices en un flujo de trabajo.
-{% data reusables.github-actions.secrets-org-level-overview %}
+{% data reusables.actions.secrets-org-level-overview %}
{% ifversion fpt or ghes > 3.0 or ghae or ghec %}
Para que los secretos se almacenen a nivel de ambiente, puedes habilitar los revisores requeridos para controlar el acceso a los secretos. Un job de flujo de trabajo no puede acceder a los secretos del ambiente hasta que los revisores requeridos le otorguen aprobación.
@@ -53,7 +53,7 @@ Para hacer que un secreto esté disponible para una acción, debes configurar el
Puedes usar y leer secretos cifrados en un archivo de flujo de trabajo si tienes acceso para editar el archivo. Para obtener más información, consulta "[Permisos de acceso en {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/access-permissions-on-github)."
-{% data reusables.github-actions.secrets-redaction-warning %}
+{% data reusables.actions.secrets-redaction-warning %}
{% ifversion fpt or ghes > 3.0 or ghae or ghec %}
Los secretos de organización y de repositorio se leen cuando una ejecución de flujo de trabajo está en cola y los secretos de ambiente se leen cuando un job que referencia el ambiente comienza.
@@ -73,13 +73,13 @@ Cuando generes credenciales, te recomendamos que otorgues los mínimos permisos
## Crear secretos cifrados para un repositorio
-{% data reusables.github-actions.permissions-statement-secrets-repository %}
+{% data reusables.actions.permissions-statement-secrets-repository %}
{% webui %}
{% data reusables.repositories.navigate-to-repo %}
{% data reusables.repositories.sidebar-settings %}
-{% data reusables.github-actions.sidebar-secret %}
+{% data reusables.actions.sidebar-secret %}
1. Da clic en **Secreto de repositorio nuevo**.
1. Teclea un nombre para tu secreto en el cuadro de entrada **Name**.
1. Ingresa el valor de tu secreto.
@@ -113,13 +113,13 @@ Para listar todos los secretos del repositorio, utiliza el subcomando `gh secret
## Crear secretos cifrados para un ambiente
-{% data reusables.github-actions.permissions-statement-secrets-environment %}
+{% data reusables.actions.permissions-statement-secrets-environment %}
{% webui %}
{% data reusables.repositories.navigate-to-repo %}
{% data reusables.repositories.sidebar-settings %}
-{% data reusables.github-actions.sidebar-environment %}
+{% data reusables.actions.sidebar-environment %}
1. Da clic en el ambiente al cual quieras agregar un secreto.
2. Debajo de **Secretos de ambiente**, da clic en **Agregar secreto**.
3. Teclea un nombre para tu secreto en el cuadro de entrada **Name**.
@@ -150,13 +150,13 @@ gh secret list --env environment-name
Cuando creas un secreto en una organización, puedes utilizar una política para limitar el acceso de los repositorios a este. Por ejemplo, puedes otorgar acceso a todos los repositorios, o limitarlo a solo los repositorios privados o a una lista específica de estos.
-{% data reusables.github-actions.permissions-statement-secrets-organization %}
+{% data reusables.actions.permissions-statement-secrets-organization %}
{% webui %}
{% data reusables.organizations.navigate-to-org %}
{% data reusables.organizations.org_settings %}
-{% data reusables.github-actions.sidebar-secret %}
+{% data reusables.actions.sidebar-secret %}
1. Da clic en **Secreto de organización nuevo**.
1. Teclea un nombre para tu secreto en el cuadro de entrada **Name**.
1. Ingresa el **Valor** para tu secreto.
@@ -209,7 +209,7 @@ Puedes revisar qué políticas de acceso se están aplicando a un secreto en tu
{% data reusables.organizations.navigate-to-org %}
{% data reusables.organizations.org_settings %}
-{% data reusables.github-actions.sidebar-secret %}
+{% data reusables.actions.sidebar-secret %}
1. La lista de secretos incluye cualquier política y permiso configurado. Por ejemplo: 
1. Para encontrar más detalles sobre los permisos configurados para cada secreto, da clic en **Actualizar**.
diff --git a/translations/es-ES/content/actions/using-containerized-services/about-service-containers.md b/translations/es-ES/content/actions/using-containerized-services/about-service-containers.md
index 1483dba34717..7bf04f5238da 100644
--- a/translations/es-ES/content/actions/using-containerized-services/about-service-containers.md
+++ b/translations/es-ES/content/actions/using-containerized-services/about-service-containers.md
@@ -25,7 +25,7 @@ Los contenedores de servicios son contenedores de Docker que ofrecen una manera
Puedes configurar contenedores de servicios para cada trabajo en un flujo de trabajo. {% data variables.product.prodname_dotcom %} crea un contenedor de Docker nuevo para cada servicio configurado en el flujo de trabajo y destruye el contenedor de servicios cuando se termina el trabajo. Los pasos de un trabajo pueden comunicarse con todos los contenedores de servicios que son parte del mismo trabajo.
-{% data reusables.github-actions.docker-container-os-support %}
+{% data reusables.actions.docker-container-os-support %}
## Comunicarse con contenedores de servicios
diff --git a/translations/es-ES/content/actions/using-containerized-services/creating-postgresql-service-containers.md b/translations/es-ES/content/actions/using-containerized-services/creating-postgresql-service-containers.md
index 71cceedbe2c5..6dd0a14e66c8 100644
--- a/translations/es-ES/content/actions/using-containerized-services/creating-postgresql-service-containers.md
+++ b/translations/es-ES/content/actions/using-containerized-services/creating-postgresql-service-containers.md
@@ -24,11 +24,11 @@ topics:
En esta guía se muestran ejemplos de flujos de trabajo que configuran un contenedor de servicios mediante la imagen `postgres` de Docker Hub. El flujo de trabajo ejecuta un script que se conecta con el servicio de PostgreSQL, crea una tabla y luego la llena de datos. Para probar que el flujo de trabajo crea y puebla la tabla de PostgreSQL, el script imprimie los datos de esta en la consola.
-{% data reusables.github-actions.docker-container-os-support %}
+{% data reusables.actions.docker-container-os-support %}
## Prerrequisitos
-{% data reusables.github-actions.service-container-prereqs %}
+{% data reusables.actions.service-container-prereqs %}
También puede ser útil tener un conocimiento básico de YAML, la sintaxis para las {% data variables.product.prodname_actions %}, y de PostgreSQL. Para obtener más información, consulta:
@@ -37,9 +37,9 @@ También puede ser útil tener un conocimiento básico de YAML, la sintaxis para
## Ejecutar trabajos en contenedores
-{% data reusables.github-actions.container-jobs-intro %}
+{% data reusables.actions.container-jobs-intro %}
-{% data reusables.github-actions.copy-workflow-file %}
+{% data reusables.actions.copy-workflow-file %}
{% raw %}
```yaml{:copy}
@@ -95,9 +95,9 @@ jobs:
### Configurar el trabajo del ejecutador
-{% data reusables.github-actions.service-container-host %}
+{% data reusables.actions.service-container-host %}
-{% data reusables.github-actions.postgres-label-description %}
+{% data reusables.actions.postgres-label-description %}
```yaml{:copy}
jobs:
@@ -122,7 +122,7 @@ jobs:
### Configurar los pasos
-{% data reusables.github-actions.service-template-steps %}
+{% data reusables.actions.service-template-steps %}
```yaml{:copy}
steps:
@@ -148,7 +148,7 @@ steps:
POSTGRES_PORT: 5432
```
-{% data reusables.github-actions.postgres-environment-variables %}
+{% data reusables.actions.postgres-environment-variables %}
El nombre del host del servicio PostgreSQL es la etiqueta que configuraste en tu flujo de trabajo, en este caso, `postgres`. Dado que los contenedores de Docker de la misma red de puentes definida por el usuario abren todos los puertos por defecto, podrás acceder al contenedor de servicios en el puerto 5432 PostgreSQL predeterminado.
@@ -156,7 +156,7 @@ El nombre del host del servicio PostgreSQL es la etiqueta que configuraste en tu
Cuando ejecutes un trabajo directamente en la máquina del ejecutor, deberás asignar los puertos del contenedor de servicios a los puertos del host de Docker. Puedes acceder a los contenedores de servicios desde el host de Docker utilizando `localhost` y el número de puerto del host de Docker.
-{% data reusables.github-actions.copy-workflow-file %}
+{% data reusables.actions.copy-workflow-file %}
{% raw %}
```yaml{:copy}
@@ -214,9 +214,9 @@ jobs:
### Configurar el trabajo del ejecutador
-{% data reusables.github-actions.service-container-host-runner %}
+{% data reusables.actions.service-container-host-runner %}
-{% data reusables.github-actions.postgres-label-description %}
+{% data reusables.actions.postgres-label-description %}
El flujo de trabajo asigna el puerto 5432 del contenedor de servicios PostgreSQL al host de Docker. Para obtener más información acerca de la palabra clave `ports`, consulta "[Acerca de los contenedores de servicio](/actions/automating-your-workflow-with-github-actions/about-service-containers#mapping-docker-host-and-service-container-ports)".
@@ -248,7 +248,7 @@ jobs:
### Configurar los pasos
-{% data reusables.github-actions.service-template-steps %}
+{% data reusables.actions.service-template-steps %}
```yaml{:copy}
steps:
@@ -274,9 +274,9 @@ steps:
POSTGRES_PORT: 5432
```
-{% data reusables.github-actions.postgres-environment-variables %}
+{% data reusables.actions.postgres-environment-variables %}
-{% data reusables.github-actions.service-container-localhost %}
+{% data reusables.actions.service-container-localhost %}
## Probar el contenedor de servicios de PostgreSQL
@@ -284,7 +284,7 @@ Puedes probar tu flujo de trabajo utilizando el siguiente script, el cual se con
Puedes modificar *client.js* para incluir cualquier operación de PostgreSQL que necesite tu flujo de trabajo. En este ejemplo, el script se conecta al servicio de PostgreSQL, agrega la tabla a la base de datos de `postgres`, inserta algunos datos de marcador de posición y luego recupera los datos.
-{% data reusables.github-actions.service-container-add-script %}
+{% data reusables.actions.service-container-add-script %}
```javascript{:copy}
const { Client } = require('pg');
diff --git a/translations/es-ES/content/actions/using-containerized-services/creating-redis-service-containers.md b/translations/es-ES/content/actions/using-containerized-services/creating-redis-service-containers.md
index 77c847bf237f..36aac663107d 100644
--- a/translations/es-ES/content/actions/using-containerized-services/creating-redis-service-containers.md
+++ b/translations/es-ES/content/actions/using-containerized-services/creating-redis-service-containers.md
@@ -24,11 +24,11 @@ topics:
En esta guía se muestran ejemplos de flujo de trabajo que configuran un contenedor de servicio mediante la imagen `redis` de Docker Hub. El flujo de trabajo ejecuta un script para crear un cliente Redis y rellenar el cliente con datos. Para probar que el flujo de trabajo crea y rellena el cliente Redis, el script imprime los datos del cliente en la consola.
-{% data reusables.github-actions.docker-container-os-support %}
+{% data reusables.actions.docker-container-os-support %}
## Prerrequisitos
-{% data reusables.github-actions.service-container-prereqs %}
+{% data reusables.actions.service-container-prereqs %}
También puede ser útil tener una comprensión básica de YAML, la sintaxis para {% data variables.product.prodname_actions %}, y Redis. Para obtener más información, consulta:
@@ -37,9 +37,9 @@ También puede ser útil tener una comprensión básica de YAML, la sintaxis par
## Ejecutar trabajos en contenedores
-{% data reusables.github-actions.container-jobs-intro %}
+{% data reusables.actions.container-jobs-intro %}
-{% data reusables.github-actions.copy-workflow-file %}
+{% data reusables.actions.copy-workflow-file %}
{% raw %}
```yaml{:copy}
@@ -90,9 +90,9 @@ jobs:
### Configurar el trabajo del contenedor
-{% data reusables.github-actions.service-container-host %}
+{% data reusables.actions.service-container-host %}
-{% data reusables.github-actions.redis-label-description %}
+{% data reusables.actions.redis-label-description %}
```yaml{:copy}
jobs:
@@ -118,7 +118,7 @@ jobs:
### Configurar los pasos
-{% data reusables.github-actions.service-template-steps %}
+{% data reusables.actions.service-template-steps %}
```yaml{:copy}
steps:
@@ -143,7 +143,7 @@ steps:
REDIS_PORT: 6379
```
-{% data reusables.github-actions.redis-environment-variables %}
+{% data reusables.actions.redis-environment-variables %}
El nombre del host del servicio Redis es la etiqueta que configuraste en tu flujo de trabajo, en este caso, `redis`. Dado que los contenedores Docker en la misma red de puentes definida por el usuario abren todos los puertos por defecto, podrás acceder al contenedor del servicio en el puerto Redis predeterminado 6379.
@@ -151,7 +151,7 @@ El nombre del host del servicio Redis es la etiqueta que configuraste en tu fluj
Cuando ejecutes un trabajo directamente en la máquina del ejecutor, deberás asignar los puertos del contenedor de servicios a los puertos del host de Docker. Puedes acceder a los contenedores de servicios desde el host de Docker utilizando `localhost` y el número de puerto del host de Docker.
-{% data reusables.github-actions.copy-workflow-file %}
+{% data reusables.actions.copy-workflow-file %}
{% raw %}
```yaml{:copy}
@@ -206,9 +206,9 @@ jobs:
### Configurar el trabajo del ejecutador
-{% data reusables.github-actions.service-container-host-runner %}
+{% data reusables.actions.service-container-host-runner %}
-{% data reusables.github-actions.redis-label-description %}
+{% data reusables.actions.redis-label-description %}
El flujo de trabajo asigna el puerto 6379 en el contenedor del servicio Redis al host Docker. Para obtener más información acerca de la palabra clave `ports`, consulta "[Acerca de los contenedores de servicio](/actions/automating-your-workflow-with-github-actions/about-service-containers#mapping-docker-host-and-service-container-ports)".
@@ -238,7 +238,7 @@ jobs:
### Configurar los pasos
-{% data reusables.github-actions.service-template-steps %}
+{% data reusables.actions.service-template-steps %}
```yaml{:copy}
steps:
@@ -264,9 +264,9 @@ steps:
REDIS_PORT: 6379
```
-{% data reusables.github-actions.redis-environment-variables %}
+{% data reusables.actions.redis-environment-variables %}
-{% data reusables.github-actions.service-container-localhost %}
+{% data reusables.actions.service-container-localhost %}
## Probar el contenedor de servicio Redis
@@ -274,7 +274,7 @@ Puedes probar tu flujo de trabajo usando el siguiente script, que crea un client
Puedes modificar *client.js* para incluir cualquier operación de Redis que necesite tu flujo de trabajo. En este ejemplo, el script crea la instancia del cliente Redis, agrega datos de marcador de posición y luego recupera los datos.
-{% data reusables.github-actions.service-container-add-script %}
+{% data reusables.actions.service-container-add-script %}
```javascript{:copy}
const redis = require("redis");
diff --git a/translations/es-ES/content/actions/using-github-hosted-runners/about-github-hosted-runners.md b/translations/es-ES/content/actions/using-github-hosted-runners/about-github-hosted-runners.md
index 662d33b84ffa..0021f07728f9 100644
--- a/translations/es-ES/content/actions/using-github-hosted-runners/about-github-hosted-runners.md
+++ b/translations/es-ES/content/actions/using-github-hosted-runners/about-github-hosted-runners.md
@@ -29,7 +29,7 @@ You can specify the runner type for each job in a workflow. Each job in a workfl
{% ifversion not ghes %}
-{% data reusables.github-actions.runner-app-open-source %}
+{% data reusables.actions.runner-app-open-source %}
### Cloud hosts for {% data variables.product.prodname_dotcom %}-hosted runners
@@ -39,7 +39,7 @@ You can specify the runner type for each job in a workflow. Each job in a workfl
### Workflow continuity for {% data variables.product.prodname_dotcom %}-hosted runners
-{% data reusables.github-actions.runner-workflow-continuity %}
+{% data reusables.actions.runner-workflow-continuity %}
In addition, if the workflow run has been successfully queued, but has not been processed by a {% data variables.product.prodname_dotcom %}-hosted runner within 45 minutes, then the queued workflow run is discarded.
@@ -61,7 +61,7 @@ Hardware specification for macOS virtual machines:
- 14 GB of RAM memory
- 14 GB of SSD disk space
-{% data reusables.github-actions.supported-github-runners %}
+{% data reusables.actions.supported-github-runners %}
Workflow logs list the runner used to run a job. For more information, see "[Viewing workflow run history](/actions/managing-workflow-runs/viewing-workflow-run-history)."
diff --git a/translations/es-ES/content/actions/using-github-hosted-runners/monitoring-your-current-jobs.md b/translations/es-ES/content/actions/using-github-hosted-runners/monitoring-your-current-jobs.md
index 3deda99110cd..091c57810b2a 100644
--- a/translations/es-ES/content/actions/using-github-hosted-runners/monitoring-your-current-jobs.md
+++ b/translations/es-ES/content/actions/using-github-hosted-runners/monitoring-your-current-jobs.md
@@ -1,5 +1,5 @@
---
-title: Monitoring your current jobs
+title: Monitorear tus jobs actuales
intro: 'Monitor how {% data variables.product.prodname_dotcom %}-hosted runners are processing jobs in your organization or enterprise, and identify any related constraints.'
versions:
feature: github-runner-dashboard
@@ -13,8 +13,8 @@ shortTitle: Monitorear tus jobs actuales
You can get a list of all jobs currently running on {% data variables.product.prodname_dotcom %}-hosted runners in your organization or enterprise.
-{% data reusables.github-actions.github-hosted-runners-navigate-to-repo-org-enterprise %}
-{% data reusables.github-actions.github-hosted-runners-table-entry %}
+{% data reusables.actions.github-hosted-runners-navigate-to-repo-org-enterprise %}
+{% data reusables.actions.github-hosted-runners-table-entry %}
1. Review the "Active jobs" section, which contains a list of all jobs currently running on {% data variables.product.prodname_dotcom %}-hosted runners.
@@ -25,6 +25,6 @@ You can get a list of all jobs currently running on {% data variables.product.pr
The following procedure demonstrates how to check the maximum number of concurrent jobs you can run.
-{% data reusables.github-actions.github-hosted-runners-navigate-to-repo-org-enterprise %}
-{% data reusables.github-actions.github-hosted-runners-table-entry %}
+{% data reusables.actions.github-hosted-runners-navigate-to-repo-org-enterprise %}
+{% data reusables.actions.github-hosted-runners-table-entry %}
1. Review the "All jobs usage" section, which lists the number of active jobs and the maximum number of jobs you can run. In this example, `9` jobs are currently running out of a maximum of `180`. 
diff --git a/translations/es-ES/content/actions/using-jobs/using-concurrency.md b/translations/es-ES/content/actions/using-jobs/using-concurrency.md
index 7817e1033997..7381eca0e82b 100644
--- a/translations/es-ES/content/actions/using-jobs/using-concurrency.md
+++ b/translations/es-ES/content/actions/using-jobs/using-concurrency.md
@@ -20,5 +20,5 @@ miniTocMaxHeadingLevel: 4
{% if github-runner-dashboard %}
## Monitorear tus jobs actuales en tu organización o empresa
-{% data reusables.github-actions.github-hosted-runners-check-concurrency %}
+{% data reusables.actions.github-hosted-runners-check-concurrency %}
{% endif %}
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 ff2d0e1a345e..ba9ea552eced 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
@@ -37,7 +37,7 @@ Algunos eventos tienen tipos de actividad múltiple. Para ellos, puedes especifi
{% endnote %}
-{% data reusables.github-actions.branch-requirement %}
+{% data reusables.actions.branch-requirement %}
Ejecuta tu flujo de trabajo cuando se cambian las reglas de protección de rama en el repositorio del flujo de trabajo. Para obtener más información sobre las reglas de protección de rama, consulta la sección "[Acerca de las ramas protegidasrama protegida](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches)". Para obtener más información acerca de las API de regla de protección de rama, consulta la sección "[BranchProtectionRule](/graphql/reference/objects#branchprotectionrule)" en la documentación de la API de GraphQL o "[Ramas](/rest/reference/branches)" en la documentación de la API de REST.
@@ -64,7 +64,7 @@ on:
{% endnote %}
-{% data reusables.github-actions.branch-requirement %}
+{% data reusables.actions.branch-requirement %}
Ejecuta tu flujo de trabajo cuando ocurre actividad relacionada con una ejecución de verificación. Una ejecución de verificación es una prueba individual que forma parte de una suite de verificación. Para obtener más información, consulta la sección "[Iniciar con la API de verificaciones](/rest/guides/getting-started-with-the-checks-api)". Para obtener más información sobre las API de ejecución de verificación, consulta la sección "[CheckRun](/graphql/reference/objects#checkrun)" en la documentación de la API de GraphQL o "[Checks](/rest/reference/checks#runs)" en la documentación de la API de REST.
@@ -88,7 +88,7 @@ on:
{% endnote %}
-{% data reusables.github-actions.branch-requirement %}
+{% data reusables.actions.branch-requirement %}
{% note %}
@@ -133,7 +133,7 @@ on:
| ---------------------------------------------------------------------------------------- | ------------------ | --------------------------------------------- | ------------------- |
| [`delete`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads/#delete) | n/a | Última confirmación en la rama predeterminada | Rama predeterminada |
-{% data reusables.github-actions.branch-requirement %}
+{% data reusables.actions.branch-requirement %}
{% note %}
@@ -199,7 +199,7 @@ on:
{% endnote %}
-{% data reusables.github-actions.branch-requirement %}
+{% data reusables.actions.branch-requirement %}
{% data reusables.webhooks.discussions-webhooks-beta %}
@@ -225,7 +225,7 @@ on:
{% endnote %}
-{% data reusables.github-actions.branch-requirement %}
+{% data reusables.actions.branch-requirement %}
{% data reusables.webhooks.discussions-webhooks-beta %}
@@ -247,7 +247,7 @@ on:
| ------------------------------------------------------------------------------------------- | ------------------ | --------------------------------------------- | ------------------- |
| [`bifurcación`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads/#fork) | n/a | Última confirmación en la rama predeterminada | Rama predeterminada |
-{% data reusables.github-actions.branch-requirement %}
+{% data reusables.actions.branch-requirement %}
Ejecuta tu flujo de trabajo cuando alguien bifurca un repositorio. Para obtener más información sobre la API de REST, consulta la sección "[Crear una bifurcación](/rest/reference/repos#create-a-fork)".
@@ -264,7 +264,7 @@ on:
| ---------------------------------------------------------------------------------------- | ------------------ | --------------------------------------------- | ------------------- |
| [`gollum`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads/#gollum) | n/a | Última confirmación en la rama predeterminada | Rama predeterminada |
-{% data reusables.github-actions.branch-requirement %}
+{% data reusables.actions.branch-requirement %}
Ejecuta tu flujo de trabajo cuando alguien crea o actualiza una página de Wiki. Para obtener más información, consulta la sección "[Acerca de los wikis](/communities/documenting-your-project-with-wikis/about-wikis)".
@@ -287,7 +287,7 @@ on:
{% endnote %}
-{% data reusables.github-actions.branch-requirement %}
+{% data reusables.actions.branch-requirement %}
Ejecuta tu flujo de trabajo cuando se crea, edita o borra un comentario en una propuesta o solicitud de cambios. Para obtener más información sobre las API de comentarios en propuestas, consulta la sección "[ssueComment](/graphql/reference/objects#issuecomment)" en la documentación de la API de GraphQL o "[comentarios de propuesta](/developers/webhooks-and-events/webhook-events-and-payloads#issue_comment)" en la documentación de la API de REST.
@@ -344,7 +344,7 @@ jobs:
{% endnote %}
-{% data reusables.github-actions.branch-requirement %}
+{% data reusables.actions.branch-requirement %}
Ejecuta tu flujo de trabajo cuando se crea o modifica una propuesta en el repositorio de un flujo de trabajo. Para ver la actividad relacionada con los comentarios de una propuesta, utiliza el evento [`issue_comment`](#issue_comment). Para obtener más información acerca de los informes de problemas, consulta la sección "[Acerca de los informes de problemas](/issues/tracking-your-work-with-issues/about-issues)". Para obtener la información sobre las API de propuestas, consulta la sección "[Propuestas](/graphql/reference/objects#issue)" en la documentación de la API de GraphQL o "[Propuestas](/rest/reference/issues)" en la documentación de la API de REST.
@@ -368,7 +368,7 @@ on:
{% endnote %}
-{% data reusables.github-actions.branch-requirement %}
+{% data reusables.actions.branch-requirement %}
Ejecuta tu flujo de trabajo cuando se crea o modifica una etiqueta en el repositorio del mismo. Para obtener más información sobre las etiquetas, consulta la sección "[Administrar etiquetas](/issues/using-labels-and-milestones-to-track-work/managing-labels)". Para obtener más información sobre las API de etiquetas, consulta la sección "[Etiqueta](/graphql/reference/objects#label)" en la documentación de la API de GraphQL o "[Etiquetas](/rest/reference/issues#labels)" en la documentación de la API de REST.
@@ -394,7 +394,7 @@ on:
{% endnote %}
-{% data reusables.github-actions.branch-requirement %}
+{% data reusables.actions.branch-requirement %}
Ejecuta tu flujo de trabajo cuando se crea o modifica un hito en el repositorio de tu flujo de trabajo. Para obtener más información sobre los hitos, consulta la sección "[Acerca de los hitos](/issues/using-labels-and-milestones-to-track-work/about-milestones)". Para obtener más información sobre las API de hitos, consulta "[Hito](/graphql/reference/objects#milestone)" en la documentación de la API de GraphQL o "[Hitos](/rest/reference/issues#milestones)" en la documentación de la API de REST.
@@ -414,7 +414,7 @@ on:
| ------------------------------------------------------------------------------------------------ | ------------------ | --------------------------------------------- | ------------ |
| [`page_build`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads/#page_build) | n/a | Última confirmación en la rama predeterminada | n/a |
-{% data reusables.github-actions.branch-requirement %}
+{% data reusables.actions.branch-requirement %}
Ejecuta tu flujo de trabajo cuando alguien sube información a una rama que sea la fuente de publicación de {% data variables.product.prodname_pages %} si {% data variables.product.prodname_pages %} se encuentra habilitado para el repositorio. Para obtener más información sobre las fuentes de publicación de {% data variables.product.prodname_pages %}, consulta la sección "[Cojnfigurar una fuente de publicación para tu sitio de GitHub Pages](/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site#choosing-a-publishing-source)". Para obtener información acerca de la API de REST, consulta la sección "[Páginas](/rest/reference/repos#pages)".
@@ -437,7 +437,7 @@ on:
{% endnote %}
-{% data reusables.github-actions.branch-requirement %}
+{% data reusables.actions.branch-requirement %}
{% note %}
@@ -475,7 +475,7 @@ on:
{% endnote %}
-{% data reusables.github-actions.branch-requirement %}
+{% data reusables.actions.branch-requirement %}
{% note %}
@@ -513,7 +513,7 @@ on:
{% endnote %}
-{% data reusables.github-actions.branch-requirement %}
+{% data reusables.actions.branch-requirement %}
{% note %}
@@ -545,7 +545,7 @@ on:
| ---------------------------------------------------------------------------------------- | ------------------ | --------------------------------------------- | ------------------- |
| [`public`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads/#public) | n/a | Última confirmación en la rama predeterminada | Rama predeterminada |
-{% data reusables.github-actions.branch-requirement %}
+{% data reusables.actions.branch-requirement %}
Ejecuta tu flujo de trabajo cuando el repositorio de tu flujo de trabajo cambia de privado a público. Para obtener más información acerca de la API de REST, consulta la sección "[Editar repositorios](/rest/reference/repos#edit)".
@@ -625,7 +625,7 @@ on:
{% note %}
-**Nota:** {% data reusables.github-actions.branch-paths-filter %} Por ejemplo, el siguiente flujo de trabajos solo se ejecutará cuando se abra una solicitud de cambios que incluya un cambio en un archivo de JavaScript (`.js`) en una rama cuyo nombre inicie con `releases/`:
+**Note:** {% data reusables.actions.branch-paths-filter %} For example, the following workflow will only run when a pull request that includes a change to a JavaScript (`.js`) file is opened on a branch whose name starts with `releases/`:
```yaml
on:
@@ -670,7 +670,7 @@ on:
{% note %}
-**Nota:** {% data reusables.github-actions.branch-paths-filter %} Por ejemplo, el siguiente flujo de trabajos solo se ejecutará cuando se abra una solicitud de cambios que incluya un cambio en un archivo de JavaScript (`.js`) en una rama cuyo nombre inicie con `releases/`:
+**Note:** {% data reusables.actions.branch-paths-filter %} For example, the following workflow will only run when a pull request that includes a change to a JavaScript (`.js`) file is opened on a branch whose name starts with `releases/`:
```yaml
on:
@@ -685,9 +685,9 @@ on:
{% endnote %}
-#### Running your workflow when a pull request merges
+#### Ejecutar tu flujo de trabajo cuando se fusiona una solicitud de cambios
-When a pull request merges, the pull request is automatically closed. To run a workflow when a pull request merges, use the `pull_request` `closed` event type along with a conditional that checks the `merged` value of the event. For example, the following workflow will run whenever a pull request closes. The `if_merged` job will only run if the pull request was also merged.
+Cuando se fusiona una solicitud de cambios, esta se cierra automáticamente. To run a workflow when a pull request merges, use the `pull_request` `closed` event type along with a conditional that checks the `merged` value of the event. Por ejemplo, el siguiente flujo de trabajo se ejecutará cada que se cierre una solicitud de cambios. El job `if_merged` solo se ejecutará si la solicitud de cambios también se fusionó.
```yaml
on:
@@ -828,7 +828,7 @@ on:
{% note %}
-**Nota:** {% data reusables.github-actions.branch-paths-filter %} Por ejemplo, el siguiente flujo de trabajos solo se ejecutará cuando se abra una solicitud de cambios que incluya un cambio en un archivo de JavaScript (`.js`) en una rama cuyo nombre inicie con `releases/`:
+**Note:** {% data reusables.actions.branch-paths-filter %} For example, the following workflow will only run when a pull request that includes a change to a JavaScript (`.js`) file is opened on a branch whose name starts with `releases/`:
```yaml
on:
@@ -873,7 +873,7 @@ on:
{% note %}
-**Nota:** {% data reusables.github-actions.branch-paths-filter %} Por ejemplo, el siguiente flujo de trabajos solo se ejecutará cuando se abra una solicitud de cambios que incluya un cambio en un archivo de JavaScript (`.js`) en una rama cuyo nombre inicie con `releases/`:
+**Note:** {% data reusables.actions.branch-paths-filter %} For example, the following workflow will only run when a pull request that includes a change to a JavaScript (`.js`) file is opened on a branch whose name starts with `releases/`:
```yaml
on:
@@ -950,7 +950,7 @@ on:
{% note %}
-**Nota:** {% data reusables.github-actions.branch-paths-filter %} Por ejemplo, el siguiente flujo de trabajo solo se ejecutará cuando se suba información que incluya un cambio a un archivo de JavaScript (`.js`) en una rama cuyo nombre inicie con `releases/`:
+**Note:** {% data reusables.actions.branch-paths-filter %} For example, the following workflow will only run when a push that includes a change to a JavaScript (`.js`) file is made to a branch whose name starts with `releases/`:
```yaml
on:
@@ -991,7 +991,7 @@ on:
{% note %}
-**Nota:** {% data reusables.github-actions.branch-paths-filter %} Por ejemplo, el siguiente flujo de trabajo solo se ejecutará cuando se suba información que incluya un cambio a un archivo de JavaScript (`.js`) en una rama cuyo nombre inicie con `releases/`:
+**Note:** {% data reusables.actions.branch-paths-filter %} For example, the following workflow will only run when a push that includes a change to a JavaScript (`.js`) file is made to a branch whose name starts with `releases/`:
```yaml
on:
@@ -1016,7 +1016,7 @@ on:
{% endnote %}
-{% data reusables.github-actions.branch-requirement %}
+{% data reusables.actions.branch-requirement %}
Ejecuta tu flujo de trabajo cuando ocurre actividad relacionada con el {% data variables.product.prodname_registry %} en tu repositorio. Para obtener más información, consulta la "[Documentación del {% data variables.product.prodname_registry %}](/packages)".
@@ -1068,7 +1068,7 @@ on:
| ---------------------------------------------------------------------------------------------------------------- | ------------------ | --------------------------------------------- | ------------------- |
| [repository_dispatch](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads/#repository_dispatch) | Personalizado | Última confirmación en la rama predeterminada | Rama predeterminada |
-{% data reusables.github-actions.branch-requirement %}
+{% data reusables.actions.branch-requirement %}
Puedes utilizar la API de {% data variables.product.product_name %} para activar un evento de webhook llamado [`repository_dispatch`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads/#repository_dispatch) cuando quieras activar un flujo de trabajo para una actividad que suceda fuera de {% data variables.product.product_name %}. Para obtener más información, consulta la sección "[Crear un evento de envío de repositorio](/rest/reference/repos#create-a-repository-dispatch-event)".
@@ -1160,7 +1160,7 @@ Las notificaciones para los flujos de trabajo programados se envían al usuario
| ---------------------------------------------------------------------------------------- | ------------------ | --------------------------------------------- | ------------ |
| [`estado`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads/#status) | n/a | Última confirmación en la rama predeterminada | n/a |
-{% data reusables.github-actions.branch-requirement %}
+{% data reusables.actions.branch-requirement %}
Ejecuta tu flujo de trabajo cuando cambia el estado de una confirmación de Git. Por ejemplo, las confirmaciones pueden marcarse como `error`, `failure`, `pending` o `success`. Si quieres proporcionar más detalles sobre el cambio de estado, puede que quieras utilizar el evento [`check_run`](#check_run). Para obtener más información sobre las API de estado de confirmación, consulta la sección "[Estado](/graphql/reference/objects#statue)" en la documentación de la API de GraphQL o "[Estados](/rest/reference/commits#commit-statuses)" en la documentación de la API de REST.
@@ -1201,7 +1201,7 @@ jobs:
{% endnote %}
-{% data reusables.github-actions.branch-requirement %}
+{% data reusables.actions.branch-requirement %}
Ejecuta tu flujo de trabajo cuando su repositorio se marcó como favorito. Para obtener más información sobre las API de solicitud de cambios, consulta la sección "[addStar](/graphql/reference/mutations#addstar)" en la documentación de la API de GraphQL o "[Marcar como favorito](/rest/reference/activity#starring)" en la documentación de la API de REST.
@@ -1343,7 +1343,7 @@ jobs:
{% endnote %}
-{% data reusables.github-actions.branch-requirement %}
+{% data reusables.actions.branch-requirement %}
{% note %}
diff --git a/translations/es-ES/content/actions/using-workflows/sharing-workflows-secrets-and-runners-with-your-organization.md b/translations/es-ES/content/actions/using-workflows/sharing-workflows-secrets-and-runners-with-your-organization.md
index 60cc56399ab4..51b7620f25f2 100644
--- a/translations/es-ES/content/actions/using-workflows/sharing-workflows-secrets-and-runners-with-your-organization.md
+++ b/translations/es-ES/content/actions/using-workflows/sharing-workflows-secrets-and-runners-with-your-organization.md
@@ -50,11 +50,11 @@ Puedes admnistrar tus secretos centralmente dentro de una organización y hacerl
Cuando creas un secreto en una organización, puedes utilizar una política para limitar el acceso de los repositorios a este. Por ejemplo, puedes otorgar acceso a todos los repositorios, o limitarlo a solo los repositorios privados o a una lista específica de estos.
-{% data reusables.github-actions.permissions-statement-secrets-organization %}
+{% data reusables.actions.permissions-statement-secrets-organization %}
{% data reusables.organizations.navigate-to-org %}
{% data reusables.organizations.org_settings %}
-{% data reusables.github-actions.sidebar-secret %}
+{% data reusables.actions.sidebar-secret %}
1. Da clic en **Secreto nuevo**.
1. Teclea un nombre para tu secreto en el cuadro de entrada **Name**.
1. Ingresa el **Valor** para tu secreto.
diff --git a/translations/es-ES/content/actions/using-workflows/storing-workflow-data-as-artifacts.md b/translations/es-ES/content/actions/using-workflows/storing-workflow-data-as-artifacts.md
index 2d8e146febe7..9b3d039e1632 100644
--- a/translations/es-ES/content/actions/using-workflows/storing-workflow-data-as-artifacts.md
+++ b/translations/es-ES/content/actions/using-workflows/storing-workflow-data-as-artifacts.md
@@ -26,7 +26,7 @@ topics:
Los artefactos te permiten hacer datos persistentes después de que se complete un job y comparten estos datos con otro job en el mismo flujo de trabajo. Un artefacto es un archivo o recopilación de archivos producidos durante una ejecución de flujo de trabajo. Por ejemplo, puedes utilizar artefactos para guardar tu compilación y probar el resultado después de que haya terminado una ejecución de flujo de trabajo. {% data reusables.actions.reusable-workflow-artifacts %}
-{% data reusables.github-actions.artifact-log-retention-statement %} El periodo de retención para una solicitud de cambios se reinicia cada vez que alguien sube una confirmación nueva en dicha solicitud.
+{% data reusables.actions.artifact-log-retention-statement %} The retention period for a pull request restarts each time someone pushes a new commit to the pull request.
Estos son algunos de los artefactos comunes que puedes subir:
@@ -37,7 +37,7 @@ Estos son algunos de los artefactos comunes que puedes subir:
{% ifversion fpt or ghec %}
-Almacenar artefactos consume espacio de almacenamiento en {% data variables.product.product_name %}. {% data reusables.github-actions.actions-billing %} Para obtener más información, consulta "[Administrar la facturación para {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions)".
+Almacenar artefactos consume espacio de almacenamiento en {% data variables.product.product_name %}. {% data reusables.actions.actions-billing %} For more information, see "[Managing billing for {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions)."
{% else %}
diff --git a/translations/es-ES/content/actions/using-workflows/triggering-a-workflow.md b/translations/es-ES/content/actions/using-workflows/triggering-a-workflow.md
index 8f1925e0051e..fd774e012e21 100644
--- a/translations/es-ES/content/actions/using-workflows/triggering-a-workflow.md
+++ b/translations/es-ES/content/actions/using-workflows/triggering-a-workflow.md
@@ -1,5 +1,5 @@
---
-title: Triggering a workflow
+title: Activar un flujo de trabajo
shortTitle: Activar un flujo de trabajo
intro: 'How to automatically trigger {% data variables.product.prodname_actions %} workflows'
versions:
@@ -41,7 +41,7 @@ Los siguientes pasos se producen para activar una ejecución de flujo de trabajo
### Activar un flujo de trabajo desde otro
-{% data reusables.github-actions.actions-do-not-trigger-workflows %} Para obtener más información, consulta "[Autenticar con el GITHUB_TOKEN](/actions/configuring-and-managing-workflows/authenticating-with-the-github_token)".
+{% data reusables.actions.actions-do-not-trigger-workflows %} For more information, see "[Authenticating with the GITHUB_TOKEN](/actions/configuring-and-managing-workflows/authenticating-with-the-github_token)."
Si no quieres activar un flujo de trabajo dentro una ejecución de flujo de trabajo, puedes utilizar un token de acceso personal en vez de un `GITHUB_TOKEN` para activar los eventos que requieren tu token. Necesitaras crear un token de acceso personal y almacenarlo como un secreto. Para minimizar tus costos de uso de {% data variables.product.prodname_actions %}, asegúrate de no crear ejecuciones de flujo de trabajo recurrentes o involuntarias. Para obtener más información acerca de cómo crear un token de acceso personal, consulta la sección "[Crear un token de acceso personal](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)". Para obtener más información sobre cómo almacenr un token de acceso personal como secreto, consulta la sección "[Crear y almacenar secretos cifrados](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets)".
@@ -89,23 +89,23 @@ Utiliza la clave `on` para especificar qué eventos activan tu flujo de trabajo.
### Utilizar un evento simple
-{% data reusables.github-actions.on-single-example %}
+{% data reusables.actions.on-single-example %}
### Utilizar eventos múltiples
-{% data reusables.github-actions.on-multiple-example %}
+{% data reusables.actions.on-multiple-example %}
### Utilizar los tipos de actividad y filtros con eventos múltiples
-You can use activity types and filters to further control when your workflow will run. For more information, see [Using event activity types](#using-event-activity-types) and [Using filters](#using-filters). {% data reusables.github-actions.actions-multiple-types %}
+You can use activity types and filters to further control when your workflow will run. For more information, see [Using event activity types](#using-event-activity-types) and [Using filters](#using-filters). {% data reusables.actions.actions-multiple-types %}
## Using event activity types
-{% data reusables.github-actions.actions-activity-types %}
+{% data reusables.actions.actions-activity-types %}
## Utilizar filtros
-{% data reusables.github-actions.actions-filters %}
+{% data reusables.actions.actions-filters %}
### Using filters to target specific branches for pull request events
@@ -125,7 +125,7 @@ You can use activity types and filters to further control when your workflow wil
## Defining inputs for manually triggered workflows
-{% data reusables.github-actions.workflow-dispatch-inputs %}
+{% data reusables.actions.workflow-dispatch-inputs %}
{% ifversion fpt or ghes > 3.3 or ghae-issue-4757 or ghec %}
## Defining inputs, outputs, and secrets for reusable workflows
diff --git a/translations/es-ES/content/actions/using-workflows/workflow-syntax-for-github-actions.md b/translations/es-ES/content/actions/using-workflows/workflow-syntax-for-github-actions.md
index e942212e718e..c2e3f974cd0f 100644
--- a/translations/es-ES/content/actions/using-workflows/workflow-syntax-for-github-actions.md
+++ b/translations/es-ES/content/actions/using-workflows/workflow-syntax-for-github-actions.md
@@ -173,7 +173,7 @@ A boolean specifying whether the secret must be supplied.
## `on.workflow_dispatch.inputs`
-{% data reusables.github-actions.workflow-dispatch-inputs %}
+{% data reusables.actions.workflow-dispatch-inputs %}
{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
## `permissions`
@@ -318,7 +318,7 @@ A unique identifier for the step. You can use the `id` to reference the step in
You can use the `if` conditional to prevent a step from running unless a condition is met. You can use any supported context and expression to create a conditional.
-{% data reusables.github-actions.expression-syntax-if %} For more information, see "[Expressions](/actions/learn-github-actions/expressions)."
+{% data reusables.actions.expression-syntax-if %} For more information, see "[Expressions](/actions/learn-github-actions/expressions)."
#### Example: Using contexts
@@ -759,7 +759,7 @@ strategy:
## `jobs..container`
-{% data reusables.github-actions.docker-container-os-support %}
+{% data reusables.actions.docker-container-os-support %}
{% data reusables.actions.jobs.section-running-jobs-in-a-container %}
@@ -789,7 +789,7 @@ strategy:
## `jobs..services`
-{% data reusables.github-actions.docker-container-os-support %}
+{% data reusables.actions.docker-container-os-support %}
Used to host service containers for a job in a workflow. Service containers are useful for creating databases or cache services like Redis. The runner automatically creates a Docker network and manages the life cycle of the service containers.
diff --git a/translations/es-ES/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md b/translations/es-ES/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md
index e92b04b449dd..dfa5276cbebf 100644
--- a/translations/es-ES/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md
+++ b/translations/es-ES/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md
@@ -114,7 +114,7 @@ Allows you to find the universally unique identifier (UUID) of your node in `clu
```
{% ifversion ghes %}
-Allows you to exempt a list of users from API rate limits. For more information, see "[Resources in the REST API](/rest/overview/resources-in-the-rest-api#rate-limiting)."
+Allows you to exempt a list of users from API rate limits. A hard limit of 120,000 requests will still apply to these users. For more information, see "[Resources in the REST API](/rest/overview/resources-in-the-rest-api#rate-limiting)."
``` shell
$ ghe-config app.github.rate-limiting-exempt-users "hubotgithub-actions"
diff --git a/translations/es-ES/content/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise.md b/translations/es-ES/content/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise.md
index b9096079e66f..3471576d3e69 100644
--- a/translations/es-ES/content/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise.md
+++ b/translations/es-ES/content/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise.md
@@ -70,4 +70,4 @@ Para las restricciones a nivel de instancia que utilizan los NSG de Azure, conta
## Utilizar {% data variables.product.prodname_actions %} con un listado de direcciones IP permitidas
-{% data reusables.github-actions.ip-allow-list-self-hosted-runners %}
+{% data reusables.actions.ip-allow-list-self-hosted-runners %}
diff --git a/translations/es-ES/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises.md b/translations/es-ES/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises.md
index 5bc6ad8bdcda..f30b19566c89 100644
--- a/translations/es-ES/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises.md
+++ b/translations/es-ES/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises.md
@@ -12,6 +12,16 @@ topics:
- Enterprise
---
+{% ifversion ghes < 3.3 %}
+{% note %}
+
+**Nota:**{% data reusables.enterprise.upgrade-ghes-for-actions %}
+
+{% endnote %}
+{% endif %}
+
+## About {% data variables.product.prodname_actions %} for enterprises
+
With {% data variables.product.prodname_actions %}, you can improve developer productivity by automating every phase of your enterprise's software development workflow.
| Tarea | Más información |
@@ -23,18 +33,29 @@ With {% data variables.product.prodname_actions %}, you can improve developer pr
{% data variables.product.prodname_actions %} helps your team work faster at scale. When large repositories start using {% data variables.product.prodname_actions %}, teams merge significantly more pull requests per day, and the pull requests are merged significantly faster. For more information, see "[Writing and shipping code faster](https://octoverse.github.com/writing-code-faster/#scale-through-automation)" in the State of the Octoverse.
-{% data variables.product.prodname_actions %} also provides greater control over deployments. Por ejemplo, puedes utilizar ambientes para requerir aprobaciones para que un job pueda proceder, restringir qué ramas pueden activar un flujo de trabajo o limitar el acceso a los secretos.{% ifversion ghec or ghae-issue-4856 %} Si tus flujos de trabajo necesitan acceder a los recursos desde un proveedor de servicios en la nube que sea compatible con OpenID Conect (OIDC), puedes configurar tus flujos de trabajo para que se autentiquen directamente con dicho proveedor. This will allow you to stop storing credentials as long-lived secrets and provide other security benefits. For more information, see "[About security hardening with OpenID Connect](/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect)."{% endif %}
+You can create your own unique automations, or you can use and adapt workflows from our ecosystem of over 10,000 actions built by industry leaders and the open source community. Para obtener más información, consulta la sección "[Encontrar y personalizar las acciones](/actions/learn-github-actions/finding-and-customizing-actions)".
{% data variables.product.prodname_actions %} is developer friendly, because it's integrated directly into the familiar {% data variables.product.product_name %} experience.
-You can create your own unique automations, or you can use and adapt workflows from our ecosystem of over 10,000 actions built by industry leaders and the open source community. Para obtener más información, consulta la sección "[Encontrar y personalizar las acciones](/actions/learn-github-actions/finding-and-customizing-actions)".
-
{% ifversion ghec %}You can enjoy the convenience of {% data variables.product.company_short %}-hosted runners, which are maintained and upgraded by {% data variables.product.company_short %}, or you{% else %}You{% endif %} can control your own private CI/CD infrastructure by using self-hosted runners. Self-hosted runners allow you to determine the exact environment and resources that complete your builds, testing, and deployments, without exposing your software development cycle to the internet. For more information, see {% ifversion ghec %}"[About {% data variables.product.company_short %}-hosted runners](/actions/using-github-hosted-runners/about-github-hosted-runners)" and{% endif %} "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners)."
+{% data variables.product.prodname_actions %} provides greater control over deployments. Por ejemplo, puedes utilizar ambientes para requerir aprobaciones para que un job pueda proceder, restringir qué ramas pueden activar un flujo de trabajo o limitar el acceso a los secretos.{% ifversion ghec or ghae-issue-4856 %} Si tus flujos de trabajo necesitan acceder a los recursos desde un proveedor de servicios en la nube que sea compatible con OpenID Conect (OIDC), puedes configurar tus flujos de trabajo para que se autentiquen directamente con dicho proveedor. OIDC provides security benefits such as eliminating the need to store credentials as long-lived secrets. For more information, see "[About security hardening with OpenID Connect](/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect)."{% endif %}
+
{% data variables.product.prodname_actions %} also includes tools to govern your enterprise's software development cycle and meet compliance obligations. 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)".
+## About getting started with {% data variables.product.prodname_actions %}
+
+{% data reusables.actions.introducing-enterprise %}
+
+{% data reusables.actions.migrating-enterprise %}
+
+{% ifversion ghes %}
+{% data reusables.actions.ghes-actions-not-enabled-by-default %} After you finish planning, you can follow the instructions for enabling {% data variables.product.prodname_actions %}. For example, you may need to upgrade the CPU and memory resources for {% data variables.product.product_location %}. Para obtener más información, consulta la sección "[Iniciar con las {% data variables.product.prodname_actions %} para {% data variables.product.prodname_ghe_server %}](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server)".
+
+{% else %}
+After you finish planning, you can follow the instructions for getting started with {% data variables.product.prodname_actions %}. For more information, see {% ifversion ghec %}"[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_cloud %}](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-cloud)."{% elsif ghae %}"[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_managed %}](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-ae)."{% endif %}
+{% endif %}
-To learn more about how you can successfully adopt {% data variables.product.prodname_actions %} for your enterprise, follow the "[Adopt {% data variables.product.prodname_actions %} for your enterprise](/admin/guides#adopt-github-actions-for-your-enterprise)" learning path.
## Leer más
diff --git a/translations/es-ES/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server.md b/translations/es-ES/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server.md
index d8c7e195ccee..c4fd2b03f3f0 100644
--- a/translations/es-ES/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server.md
+++ b/translations/es-ES/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server.md
@@ -26,7 +26,7 @@ Este artículo explica cómo los administradores de sitio pueden habilitar {% da
{% data reusables.enterprise.upgrade-ghes-for-actions %}
-{% data variables.product.prodname_actions %} is not enabled for {% data variables.product.prodname_ghe_server %} by default. You'll need to determine whether your instance has adequate CPU and memory resources to handle the load from {% data variables.product.prodname_actions %} without causing performance loss, and possibly increase those resources. You'll also need to decide which storage provider you'll use for the blob storage required to store artifacts generated by workflow runs. Then, you'll enable {% data variables.product.prodname_actions %} for your enterprise, manage access permissions, and add self-hosted runners to run workflows.
+{% data reusables.actions.ghes-actions-not-enabled-by-default %} You'll need to determine whether your instance has adequate CPU and memory resources to handle the load from {% data variables.product.prodname_actions %} without causing performance loss, and possibly increase those resources. You'll also need to decide which storage provider you'll use for the blob storage required to store artifacts generated by workflow runs. Then, you'll enable {% data variables.product.prodname_actions %} for your enterprise, manage access permissions, and add self-hosted runners to run workflows.
{% data reusables.actions.introducing-enterprise %}
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 acf1fb385872..21a1ef525c08 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
@@ -85,6 +85,12 @@ Whenever your workflow developers want to use an action that's stored in a priva
You should plan for how you'll manage the resources required to use {% data variables.product.prodname_actions %}.
+{% ifversion ghes %}
+### Hardware requirements
+
+You may need to upgrade the CPU and memory resources for {% data variables.product.product_location %} to handle the load from {% data variables.product.prodname_actions %} without causing performance loss. For more information, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server#review-hardware-requirements)."
+{% endif %}
+
### Ejecutores
{% data variables.product.prodname_actions %} workflows require runners.{% ifversion ghec %} You can choose to use {% data variables.product.prodname_dotcom %}-hosted runners or self-hosted runners. {% data variables.product.prodname_dotcom %}-hosted runners are convenient because they are managed by {% data variables.product.company_short %}, who handles maintenance and upgrades for you. Sin embargo, podrías querer considerar los ejecutores auto-hospedados si necesitas ejecutar un flujo de trabajo que accederá a los recursos tras tu cortafuegos o si quieres tener más control sobre los recursos, configuración o ubicación geográfica de tus máquinas de ejecutores. Para obtener más información, consulta las secciones "[Acerca de los ejecutores hospedados en {% data variables.product.prodname_dotcom %}](/actions/using-github-hosted-runners/about-github-hosted-runners)" y "[Acerca de los ejecutores auto-hospedados](/actions/hosting-your-own-runners/about-self-hosted-runners)".{% else %} Necesitarás hospedar tus propios ejecutores instalando la aplicación de ejecutores auto-hospedados de {% data variables.product.prodname_actions %} en tus propias máquinas. Para obtener más información, consulta la sección "[Acerca de los ejecutores auto-hospedados](/actions/hosting-your-own-runners/about-self-hosted-runners)".{% endif %}
@@ -111,7 +117,7 @@ You must configure external blob storage for these artifacts. Decide which suppo
{% ifversion ghec or ghes %}
-{% data reusables.github-actions.artifact-log-retention-statement %}
+{% data reusables.actions.artifact-log-retention-statement %}
{% endif %}
diff --git a/translations/es-ES/content/admin/guides.md b/translations/es-ES/content/admin/guides.md
index 0fc246777c73..e535a24a5e3f 100644
--- a/translations/es-ES/content/admin/guides.md
+++ b/translations/es-ES/content/admin/guides.md
@@ -136,5 +136,6 @@ includeGuides:
- /admin/user-management/requiring-two-factor-authentication-for-an-organization
- /admin/user-management/suspending-and-unsuspending-users
- /admin/overview/creating-an-enterprise-account
+ - /admin/user-management/managing-organizations-in-your-enterprise/restoring-a-deleted-organization
---
diff --git a/translations/es-ES/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md b/translations/es-ES/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md
index 933afa458eac..92ccb7ece7ae 100644
--- a/translations/es-ES/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md
+++ b/translations/es-ES/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md
@@ -71,7 +71,7 @@ Las {% data variables.product.prodname_actions %} pueden restablecer los archivo
{% data reusables.enterprise-accounts.access-enterprise %}
{% data reusables.enterprise-accounts.policies-tab %}
{% data reusables.enterprise-accounts.actions-tab %}
-{% data reusables.github-actions.change-retention-period-for-artifacts-logs %}
+{% data reusables.actions.change-retention-period-for-artifacts-logs %}
{% endif %}
@@ -88,7 +88,7 @@ Puedes requerir políticas para controlar la forma en la que se comportan las {%
{% data reusables.enterprise-accounts.access-enterprise %}
{% data reusables.enterprise-accounts.policies-tab %}
{% data reusables.enterprise-accounts.actions-tab %}
-{% data reusables.github-actions.workflows-from-public-fork-setting %}
+{% data reusables.actions.workflows-from-public-fork-setting %}
{% data reusables.actions.workflow-run-approve-link %}
@@ -98,16 +98,16 @@ Puedes requerir políticas para controlar la forma en la que se comportan las {%
### Requerir una política para bifurcar solicitudes de cambio en repositorios privados
-{% data reusables.github-actions.private-repository-forks-overview %}
+{% data reusables.actions.private-repository-forks-overview %}
Si se habilita una política para una empresa, esta puede inhabilitarse selectivamente en organizaciones o repositorios individuales. Si se inhabilita una política para una empresa, las organizaciones o repositorios individuales no pueden habilitarla.
-{% data reusables.github-actions.private-repository-forks-options %}
+{% data reusables.actions.private-repository-forks-options %}
{% data reusables.enterprise-accounts.access-enterprise %}
{% data reusables.enterprise-accounts.policies-tab %}
{% data reusables.enterprise-accounts.actions-tab %}
-{% data reusables.github-actions.private-repository-forks-configure %}
+{% data reusables.actions.private-repository-forks-configure %}
{% endif %}
@@ -115,11 +115,11 @@ Si se habilita una política para una empresa, esta puede inhabilitarse selectiv
## Requerir una política para los permisos de flujo de trabajo en tu empresa
-{% data reusables.github-actions.workflow-permissions-intro %}
+{% data reusables.actions.workflow-permissions-intro %}
Puedes configurar los permisos predeterminados para del `GITHUB_TOKEN` en la configuración de tu empresa, organización o repositorio. Si eliges la opción restringida como lo predeterminado en la configuración de tu empresa, esto previene que puedas elegir más configuraciones permisivas en la configuración de tu organización o repositorio.
-{% data reusables.github-actions.workflow-permissions-modifying %}
+{% data reusables.actions.workflow-permissions-modifying %}
{% data reusables.enterprise-accounts.access-enterprise %}
{% data reusables.enterprise-accounts.policies-tab %}
diff --git a/translations/es-ES/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise.md b/translations/es-ES/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise.md
index de27d99c43a5..69f67199d584 100644
--- a/translations/es-ES/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise.md
+++ b/translations/es-ES/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise.md
@@ -119,7 +119,7 @@ You can also configure allowed IP addresses for an individual organization. For
### Using {% data variables.product.prodname_actions %} with an IP allow list
-{% data reusables.github-actions.ip-allow-list-self-hosted-runners %}
+{% data reusables.actions.ip-allow-list-self-hosted-runners %}
{% endif %}
@@ -129,9 +129,11 @@ You can also configure allowed IP addresses for an individual organization. For
You can use a SSH certificate authorities (CA) to allow members of any organization owned by your enterprise to access that organization's repositories using SSH certificates you provide. {% data reusables.organizations.can-require-ssh-cert %} For more information, see "[About SSH certificate authorities](/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities)."
+{% data reusables.organizations.add-extension-to-cert %}
+
### Adding an SSH certificate authority
-{% data reusables.organizations.add-extension-to-cert %}
+If you require SSH certificates for your enterprise, enterprise members should use a special URL for Git operations over SSH. For more information, see "[About SSH certificate authorities](/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities#about-ssh-urls-with-ssh-certificates)."
{% data reusables.enterprise-accounts.access-enterprise %}
{% data reusables.enterprise-accounts.settings-tab %}
diff --git a/translations/es-ES/content/admin/user-management/managing-organizations-in-your-enterprise/index.md b/translations/es-ES/content/admin/user-management/managing-organizations-in-your-enterprise/index.md
index c9457ce8e616..8a20b20a58f6 100644
--- a/translations/es-ES/content/admin/user-management/managing-organizations-in-your-enterprise/index.md
+++ b/translations/es-ES/content/admin/user-management/managing-organizations-in-your-enterprise/index.md
@@ -27,6 +27,7 @@ children:
- /streaming-the-audit-logs-for-organizations-in-your-enterprise-account
- /removing-users-from-teams-and-organizations
- /removing-organizations-from-your-enterprise
+ - /restoring-a-deleted-organization
- /managing-projects-using-jira
- /continuous-integration-using-jenkins
shortTitle: Administrar las organizaciones
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
new file mode 100644
index 000000000000..08feafff958d
--- /dev/null
+++ b/translations/es-ES/content/admin/user-management/managing-organizations-in-your-enterprise/restoring-a-deleted-organization.md
@@ -0,0 +1,53 @@
+---
+title: Restoring a deleted organization
+intro: 'You can partially restore an organization that was previously deleted on {% data variables.product.product_location %}.'
+versions:
+ ghes: '*'
+type: how_to
+topics:
+ - Administrator
+ - Enterprise
+ - Organizations
+shortTitle: Restore organization
+permissions: 'Site administers can restore an organization on {% data variables.product.product_name %}.'
+---
+
+## About organization restoration
+
+You can use the site admin dashboard to restore an organization that was previously deleted on {% data variables.product.product_location %}, as long as the audit log Elasticsearch indices contain the data for the `org.delete` event.
+
+Immediately after you restore an organization, the organization will not be exactly the same as it was prior to the deletion. You'll have to manually restore any repositories that were owned by the organization. Para obtener más información, consulta "[Restaurar un repositorio eliminado](/admin/user-management/managing-repositories-in-your-enterprise/restoring-a-deleted-repository)".
+
+You can also use the audit log to help you manually re-add teams and organization members. For more information, see "[Restoring members and teams](#restoring-members-and-teams)."
+
+## Restoring an organization
+
+{% data reusables.enterprise_site_admin_settings.access-settings %}
+1. Under "Search users, organizations, enterprises, teams, repositories, gists, and applications", search for the organization.
+
+ 
+
+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**.
+
+ 
+
+## Restoring members and teams
+
+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)."
+
+In all the search phrases below, replace ORGANIZATION with the name of the organization and TEAM with the name of the team.
+
+### Restoring organization members
+
+1. To find all users who were added to and removed from the organization, search the audit log for `action:org.add_member org:ORGANIZATION` and `action:org.remove_member org:ORGANIZATION`.
+1. Manually add to the organization each user that should still be a member. For more information, see "[Adding people to your organization](/organizations/managing-membership-in-your-organization/adding-people-to-your-organization)."
+
+### Restoring teams
+
+1. To find each team name, search the audit log for `action:team.create org:ORGANIZATION`.
+1. Manually recreate the team. Para obtener más información, consulta la sección "[Crear un equipo](/organizations/organizing-members-into-teams/creating-a-team)".
+1. To find the members that have been added to each team, search for `action:team.add_member team:"ORGANIZATION/TEAM"`.
+1. Manually re-add the team members. For more information, see "[Adding organization members to a team](/organizations/organizing-members-into-teams/adding-organization-members-to-a-team)."
+1. To find the repositories that the team was granted access to, search for `action:team.add_repository team:"ORGANIZATION/TEAM"`.
+1. To find the access level that the team was granted for each repository, search for `action:team.update_repository_permission team:"ORGANIZATION/TEAM"`.
+1. Manually give the team access again. Para obtener más información, consulta la sección "[Administrar el acceso de un equipo a un repositorio organizacional](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository)".
diff --git a/translations/es-ES/content/authentication/managing-commit-signature-verification/checking-for-existing-gpg-keys.md b/translations/es-ES/content/authentication/managing-commit-signature-verification/checking-for-existing-gpg-keys.md
index 88f7bba3555b..6b5071bb48f1 100644
--- a/translations/es-ES/content/authentication/managing-commit-signature-verification/checking-for-existing-gpg-keys.md
+++ b/translations/es-ES/content/authentication/managing-commit-signature-verification/checking-for-existing-gpg-keys.md
@@ -28,7 +28,12 @@ shortTitle: Llaves GPG existentes
{% data reusables.gpg.list-keys-with-note %}
3. Comprueba el resultado de los comandos para ver si tienes un par de llaves GPG.
* Si no hay pares de llaves GPG o no quieres usar algunas de las que están disponibles para las confirmaciones y las etiquetas firmadas, [genera una nueva llave GPG](/articles/generating-a-new-gpg-key).
- * Si existe un nuevo par de llaves GPG existente y quieres usarlo para firmar confirmaciones y etiquetas, [agrega tu llave GPG a tu cuenta de GitHub](/articles/adding-a-new-gpg-key-to-your-github-account).
+ * If there's an existing GPG key pair and you want to use it to sign commits and tags, you can display the public key using the following command, substituting in the GPG key ID you'd like to use. En este ejemplo, el ID de la llave GPG es `3AA5C34371567BD2`:
+ ```shell
+ $ gpg --armor --export 3AA5C34371567BD2
+ # Prints the GPG key ID, in ASCII armor format
+ ```
+ You can then [add your GPG key to your GitHub account](/articles/adding-a-new-gpg-key-to-your-github-account).
## Leer más
diff --git a/translations/es-ES/content/authentication/managing-commit-signature-verification/telling-git-about-your-signing-key.md b/translations/es-ES/content/authentication/managing-commit-signature-verification/telling-git-about-your-signing-key.md
index ad9b87632963..1b7ad5b8fccb 100644
--- a/translations/es-ES/content/authentication/managing-commit-signature-verification/telling-git-about-your-signing-key.md
+++ b/translations/es-ES/content/authentication/managing-commit-signature-verification/telling-git-about-your-signing-key.md
@@ -45,6 +45,12 @@ Si tienes múltiples llaves GPG, le debes decir a Git cuál utilizar.
$ if [ -r ~/.bash_profile ]; then echo 'export GPG_TTY=$(tty)' >> ~/.bash_profile; \
else echo 'export GPG_TTY=$(tty)' >> ~/.profile; fi
```
+1. Optionally, to prompt you to enter a PIN or passphrase when required, install `pinentry-mac`. For example, using [Homebrew](https://brew.sh/):
+ ```shell
+ $ brew install pinentry-mac
+ $ echo "pinentry-program $(which pinentry-mac)" >> ~/.gnupg/gpg-agent.conf
+ $ killall gpg-agent
+ ```
{% data reusables.gpg.x-509-key %}
diff --git a/translations/es-ES/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md b/translations/es-ES/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md
index b5f2fa6984ea..a4e7780d0a0a 100644
--- a/translations/es-ES/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md
+++ b/translations/es-ES/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md
@@ -16,9 +16,9 @@ shortTitle: Facturación de las GitHub Actions
## Acerca de la facturación para {% data variables.product.prodname_actions %}
-{% data reusables.github-actions.actions-billing %}
+{% data reusables.actions.actions-billing %}
-{% data reusables.github-actions.actions-spending-limit-brief %} Para obtener más información, consulta la sección "[Acerca de los límites de gasto](#about-spending-limits)".
+{% data reusables.actions.actions-spending-limit-brief %} Para obtener más información, consulta la sección "[Acerca de los límites de gasto](#about-spending-limits)".
{% ifversion ghec %}
Si compraste {% data variables.product.prodname_enterprise %} mediante un Acuerdo de Microsoft Enterprise, puedes conectar tu ID de Suscripción de Azure a tu cuenta empresarial para habilitar y pagar por el uso de {% data variables.product.prodname_actions %} más allá de las cantidades que se incluyen en tu cuenta. Para obtener más información, consulta la sección "[Conectar una suscripción de Azure a tu empresa](/billing/managing-billing-for-your-github-account/connecting-an-azure-subscription-to-your-enterprise)".
@@ -99,7 +99,7 @@ Tu uso de {% data variables.product.prodname_actions %} comparte la fecha de fac
## Acerca de los límites de gasto
-{% data reusables.github-actions.actions-spending-limit-detailed %}
+{% data reusables.actions.actions-spending-limit-detailed %}
Para obtener más información sobre cómo administrar y cambiar el límite de gastos de tu organización, consulta la sección "[Administrar tu límite de gastos para {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions/managing-your-spending-limit-for-github-actions)".
diff --git a/translations/es-ES/content/billing/managing-billing-for-github-actions/managing-your-spending-limit-for-github-actions.md b/translations/es-ES/content/billing/managing-billing-for-github-actions/managing-your-spending-limit-for-github-actions.md
index bd11a6254536..00579433dad9 100644
--- a/translations/es-ES/content/billing/managing-billing-for-github-actions/managing-your-spending-limit-for-github-actions.md
+++ b/translations/es-ES/content/billing/managing-billing-for-github-actions/managing-your-spending-limit-for-github-actions.md
@@ -19,9 +19,9 @@ shortTitle: Límites de gasto para las acciones
## Acerca de los límites de gastos para {% data variables.product.prodname_actions %}
-{% data reusables.github-actions.actions-billing %}
+{% data reusables.actions.actions-billing %}
-{% data reusables.github-actions.actions-spending-limit-brief %}
+{% data reusables.actions.actions-spending-limit-brief %}
{% data reusables.actions.actions-packages-set-spending-limit %}Para obtener más información acerca de los costos de {% data variables.product.prodname_actions %}, consulta la sección "[Acerca de los costos de {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions/about-billing-for-github-actions)".
diff --git a/translations/es-ES/content/billing/managing-billing-for-github-actions/viewing-your-github-actions-usage.md b/translations/es-ES/content/billing/managing-billing-for-github-actions/viewing-your-github-actions-usage.md
index 2d61025a258a..9a4d662be350 100644
--- a/translations/es-ES/content/billing/managing-billing-for-github-actions/viewing-your-github-actions-usage.md
+++ b/translations/es-ES/content/billing/managing-billing-for-github-actions/viewing-your-github-actions-usage.md
@@ -43,7 +43,7 @@ Los propietarios de empresa y gerentes de facturación pueden ver el uso de {% d
{% note %}
-**Nota:** Los detalles de facturación para las cuentas empresariales no resumen el uso de los minutos para cada sistema operativo. {% data reusables.github-actions.enterprise-billing-details %}
+**Nota:** Los detalles de facturación para las cuentas empresariales no resumen el uso de los minutos para cada sistema operativo. {% data reusables.actions.enterprise-billing-details %}
{% endnote %}
diff --git a/translations/es-ES/content/billing/managing-billing-for-github-packages/viewing-your-github-packages-usage.md b/translations/es-ES/content/billing/managing-billing-for-github-packages/viewing-your-github-packages-usage.md
index e1a74945ffaf..d0eff4b4ac15 100644
--- a/translations/es-ES/content/billing/managing-billing-for-github-packages/viewing-your-github-packages-usage.md
+++ b/translations/es-ES/content/billing/managing-billing-for-github-packages/viewing-your-github-packages-usage.md
@@ -42,7 +42,7 @@ Los propietarios de empresa y gerentes de facturación pueden ver el uso de {% d
{% note %}
-**Nota:** Los detalles de facturación para cuentas empresariales únicamente resumen el uso de almacenamiento de datos por organización. {% data reusables.github-actions.enterprise-billing-details %}
+**Nota:** Los detalles de facturación para cuentas empresariales únicamente resumen el uso de almacenamiento de datos por organización. {% data reusables.actions.enterprise-billing-details %}
{% endnote %}
diff --git a/translations/es-ES/content/billing/managing-your-github-billing-settings/setting-your-billing-email.md b/translations/es-ES/content/billing/managing-your-github-billing-settings/setting-your-billing-email.md
index 41d8ddf6fbb1..84a8d713c68f 100644
--- a/translations/es-ES/content/billing/managing-your-github-billing-settings/setting-your-billing-email.md
+++ b/translations/es-ES/content/billing/managing-your-github-billing-settings/setting-your-billing-email.md
@@ -64,3 +64,44 @@ Siempre debe existir una dirección designada como el destinatario principal. La
1. Para la entrada del usuario en la lista, da clic en **Editar**. 
1. A la derecha de la dirección de correo electrónico, utiliza el menú desplegable "Editar" y haz clic en **Eliminar**. 
1. Revisa el mensaje de confirmación y luego da clic en **Eliminar**.
+
+{% ifversion ghec %}
+## Setting your enterprise's billing email
+
+Your enterprise's billing email is where {% data variables.product.product_name %} sends receipts and other billing-related communication. The email address does not need to be unique to the enterprise account.
+
+Only enterprise members with the owner or billing manager role can access or change billing settings for your enterprise. Para obtener más información, consulta la sección "[Administrar usuarios en tu empresa](/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise)".
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.settings-tab %}
+{% data reusables.enterprise-accounts.billing-tab %}
+1. Click **Billing emails**.
+2. Under "Email recipients", to the right of the billing email address, click **Edit**. 
+2. Teclea una dirección de correo electrónico válida y luego haz clic en **Actualizar**. 
+
+## Managing additional recipients for your enterprise's billing email
+
+Si tienes usuarios que quieran recibir reportes de facturación, puedes agregar sus direcciones de correo electrónico como destinatarios del correo de facturación.
+
+Only enterprise members with the owner or billing manager role can access or change billing settings for your enterprise. Para obtener más información, consulta la sección "[Administrar usuarios en tu empresa](/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise)".
+
+### Agregar un destinatario para las notificaciones de facturación
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.settings-tab %}
+{% data reusables.enterprise-accounts.billing-tab %}
+1. Click **Billing emails**.
+2. Under "Email recipients", to the right of the billing email address, click **Add**. 
+3. Teclea la dirección de correo electrónico del destinatario y luego da clic en **Agregar**. 
+
+### Eliminar un destinatario de las notificaciones de facturación
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.settings-tab %}
+{% data reusables.enterprise-accounts.billing-tab %}
+1. Click **Billing emails**.
+2. Debajo de "Destinatarios de correo electrónico", encuentra la dirección de correo electrónico que quieres eliminar.
+3. Para la entrada del usuario en la lista, da clic en **Editar**. 
+4. A la derecha de la dirección de correo electrónico, utiliza el menú desplegable "Editar" y haz clic en **Eliminar**. 
+5. Revisa el mensaje de confirmación y luego da clic en **Eliminar**.
+{% endif %}
diff --git a/translations/es-ES/content/code-security/code-scanning/integrating-with-code-scanning/uploading-a-sarif-file-to-github.md b/translations/es-ES/content/code-security/code-scanning/integrating-with-code-scanning/uploading-a-sarif-file-to-github.md
index 8f21ec78dff1..0e33d7b940fb 100644
--- a/translations/es-ES/content/code-security/code-scanning/integrating-with-code-scanning/uploading-a-sarif-file-to-github.md
+++ b/translations/es-ES/content/code-security/code-scanning/integrating-with-code-scanning/uploading-a-sarif-file-to-github.md
@@ -86,7 +86,11 @@ jobs:
build:
runs-on: ubuntu-latest{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
permissions:
- security-events: write{% endif %}
+ # required for all workflows
+ security-events: write
+ # only required for workflows in private repositories
+ actions: read
+ contents: read{% endif %}
steps:
# This step checks out a copy of your repository.
- name: Checkout repository
@@ -123,7 +127,11 @@ jobs:
build:
runs-on: ubuntu-latest{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
permissions:
- security-events: write{% endif %}
+ # required for all workflows
+ security-events: write
+ # only required for workflows in private repositories
+ actions: read
+ contents: read{% endif %}
steps:
- uses: actions/checkout@v2
- name: Run npm install
diff --git a/translations/es-ES/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-encrypted-secrets-for-dependabot.md b/translations/es-ES/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-encrypted-secrets-for-dependabot.md
index e177ef64a73c..2227c4590041 100644
--- a/translations/es-ES/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-encrypted-secrets-for-dependabot.md
+++ b/translations/es-ES/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-encrypted-secrets-for-dependabot.md
@@ -44,11 +44,11 @@ The name of a {% data variables.product.prodname_dependabot %} secret:
## Adding a repository secret for {% data variables.product.prodname_dependabot %}
-{% data reusables.github-actions.permissions-statement-secrets-repository %}
+{% data reusables.actions.permissions-statement-secrets-repository %}
{% data reusables.repositories.navigate-to-repo %}
{% data reusables.repositories.sidebar-settings %}
-{% data reusables.github-actions.sidebar-secret %}
+{% data reusables.actions.sidebar-secret %}
{% data reusables.dependabot.dependabot-secrets-button %}
1. Click **New repository secret**.
1. Type a name for your secret in the **Name** input box.
@@ -63,11 +63,11 @@ The name of a {% data variables.product.prodname_dependabot %} secret:
When creating a secret in an organization, you can use a policy to limit which repositories can access that secret. For example, you can grant access to all repositories, or limit access to only private repositories or a specified list of repositories.
-{% data reusables.github-actions.permissions-statement-secrets-organization %}
+{% data reusables.actions.permissions-statement-secrets-organization %}
{% data reusables.organizations.navigate-to-org %}
{% data reusables.organizations.org_settings %}
-{% data reusables.github-actions.sidebar-secret %}
+{% data reusables.actions.sidebar-secret %}
{% data reusables.dependabot.dependabot-secrets-button %}
1. Click **New organization secret**.
1. Type a name for your secret in the **Name** input box.
diff --git a/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces.md b/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces.md
index 2fe0a0ede9e5..31404b3b7eae 100644
--- a/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces.md
+++ b/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces.md
@@ -51,7 +51,7 @@ Para crear secretos para un repositorio de la organización, debes tener acceso
Cuando creas un secreto en una organización, puedes utilizar una política para limitar el acceso de los repositorios a este. Por ejemplo, puedes otorgar acceso a todos los repositorios, o limitarlo a solo los repositorios privados o a una lista específica de estos.
-{% data reusables.github-actions.permissions-statement-secrets-organization %}
+{% data reusables.actions.permissions-statement-secrets-organization %}
{% data reusables.organizations.navigate-to-org %}
{% data reusables.organizations.org_settings %}
@@ -68,7 +68,7 @@ Puedes revisar qué políticas de acceso se aplican a un secreto en tu organizac
{% data reusables.organizations.navigate-to-org %}
{% data reusables.organizations.org_settings %}
-{% data reusables.github-actions.sidebar-secret %}
+{% data reusables.actions.sidebar-secret %}
1. La lista de secretos incluye cualquier política y permiso configurado. Por ejemplo: 
1. Para encontrar más detalles sobre los permisos configurados para cada secreto, da clic en **Actualizar**.
diff --git a/translations/es-ES/content/get-started/learning-about-github/githubs-products.md b/translations/es-ES/content/get-started/learning-about-github/githubs-products.md
index 774b8fe369f3..5aeaa75fcaaf 100644
--- a/translations/es-ES/content/get-started/learning-about-github/githubs-products.md
+++ b/translations/es-ES/content/get-started/learning-about-github/githubs-products.md
@@ -89,7 +89,7 @@ Adicionalmente a las características disponibles con {% data variables.product.
{% data variables.product.company_short %} factura por {% data variables.product.prodname_team %} en una modalidad "por usuario". Para obtener más información, consulta la sección "[Acerca de los precios por usuario]({% ifversion not fpt %}/free-pro-team@latest{% endif %}/billing/managing-billing-for-your-github-account/about-per-user-pricing){% ifversion fpt %}".{% else %}" en la documentación de los tipos de cuenta gratuito, Pro & de equipo.{% endif %}
-{% data reusables.github-actions.actions-billing %}
+{% data reusables.actions.actions-billing %}
## {% data variables.product.prodname_enterprise %}
diff --git a/translations/es-ES/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-allowed-ip-addresses-for-your-organization.md b/translations/es-ES/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-allowed-ip-addresses-for-your-organization.md
index 618e6d056af7..444975d81293 100644
--- a/translations/es-ES/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-allowed-ip-addresses-for-your-organization.md
+++ b/translations/es-ES/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-allowed-ip-addresses-for-your-organization.md
@@ -82,4 +82,4 @@ Para obtener más información sobre cómo crear una lista de direcciones permit
## Utilizar {% data variables.product.prodname_actions %} con un listado de direcciones IP permitidas
-{% data reusables.github-actions.ip-allow-list-self-hosted-runners %}
+{% data reusables.actions.ip-allow-list-self-hosted-runners %}
diff --git a/translations/es-ES/content/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities.md b/translations/es-ES/content/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities.md
index 835e187a8a1b..a75bc1007011 100644
--- a/translations/es-ES/content/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities.md
+++ b/translations/es-ES/content/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities.md
@@ -28,9 +28,15 @@ For example, you can build an internal system that issues a new certificate to y
Organization members can use their signed certificates for authentication even if you've enforced SAML single sign-on. Unless you make SSH certificates a requirement, organization members can continue to use other means of authentication to access your organization's resources with Git, including their username and password, personal access tokens, and their own SSH keys.
{% endif %}
-Members will not be able to use their certificates to access forks of your repositories that are owned by their user accounts.
+Members will not be able to use their certificates to access forks of your repositories that are owned by their personal accounts.
-To prevent authentication errors, organization members should use a special URL that includes the organization ID to clone repositories using signed certificates. Anyone with read access to the repository can find this URL on the repository page. For more information, see "[Cloning a repository](/articles/cloning-a-repository)."
+## About SSH URLs with SSH certificates
+
+If your organization requires SSH certificates, to prevent authentication errors, organization members should use a special URL that includes the organization ID when performing Git operations over SSH. This special URL allows the client and server to more easily negotiate which key on the member's computer should be used for authentication. If a member uses the normal URL, which starts with `git@github.com`, the SSH client might offer the wrong key, causing the operation to fail.
+
+Anyone with read access to the repository can find this URL by selecting the **Code** dropdown menu on the main page of the repository, then clicking **Use SSH**.
+
+If your organization doesn't require SSH certificates, members can continue to use their own SSH keys, or other means of authentication. In that case, either the special URL or the normal URL, which starts with `git@github.com`, will work.
## Issuing certificates
diff --git a/translations/es-ES/content/organizations/managing-git-access-to-your-organizations-repositories/managing-your-organizations-ssh-certificate-authorities.md b/translations/es-ES/content/organizations/managing-git-access-to-your-organizations-repositories/managing-your-organizations-ssh-certificate-authorities.md
index 5d0f3c09ca41..5006a0cf3ab3 100644
--- a/translations/es-ES/content/organizations/managing-git-access-to-your-organizations-repositories/managing-your-organizations-ssh-certificate-authorities.md
+++ b/translations/es-ES/content/organizations/managing-git-access-to-your-organizations-repositories/managing-your-organizations-ssh-certificate-authorities.md
@@ -20,9 +20,11 @@ Los propietarios de la organización pueden administrar autoridades de certifica
Puedes permitir que los miembros accedan a los repositorios d ela organización mediante certificados SSH que brindas al agregar un CA SSH a tu organización. {% data reusables.organizations.can-require-ssh-cert %}Para obtener más información, consulta "[Acerca de las autoridades de certificados de SSH](/articles/about-ssh-certificate-authorities)".
+{% data reusables.organizations.add-extension-to-cert %}
+
## Agregar una autoridad de certificado de SSH
-{% data reusables.organizations.add-extension-to-cert %}
+If you require SSH certificates for your enterprise, enterprise members should use a special URL for Git operations over SSH. Para obtener más información, consulta [Acerca de las autoridades de certificación de SSH](/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities#about-ssh-urls-with-ssh-certificates)".
{% data reusables.profile.access_org %}
{% data reusables.profile.org_settings %}
diff --git a/translations/es-ES/content/organizations/managing-organization-settings/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-organization.md b/translations/es-ES/content/organizations/managing-organization-settings/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-organization.md
index 065346576964..c17c87e6e404 100644
--- a/translations/es-ES/content/organizations/managing-organization-settings/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-organization.md
+++ b/translations/es-ES/content/organizations/managing-organization-settings/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-organization.md
@@ -21,4 +21,4 @@ shortTitle: Configurar el periodo de retención
{% data reusables.organizations.navigate-to-org %}
{% data reusables.organizations.org_settings %}
{% data reusables.organizations.settings-sidebar-actions %}
-{% data reusables.github-actions.change-retention-period-for-artifacts-logs %}
+{% data reusables.actions.change-retention-period-for-artifacts-logs %}
diff --git a/translations/es-ES/content/organizations/managing-organization-settings/deleting-an-organization-account.md b/translations/es-ES/content/organizations/managing-organization-settings/deleting-an-organization-account.md
index d65a325759be..5f13e4f882e5 100644
--- a/translations/es-ES/content/organizations/managing-organization-settings/deleting-an-organization-account.md
+++ b/translations/es-ES/content/organizations/managing-organization-settings/deleting-an-organization-account.md
@@ -12,7 +12,7 @@ versions:
topics:
- Organizations
- Teams
-shortTitle: Borrar una cuenta organizacional
+shortTitle: Delete organization
---
{% ifversion fpt or ghec %}
@@ -26,7 +26,15 @@ shortTitle: Borrar una cuenta organizacional
## 1. Haz una copia de respaldo del contenido de tu organización
-Una vez que eliminas una organización, GitHub **no puede restaurar su contenido**. Por lo tanto, antes de que borres tu organización, asegúrate de que tengas una copia de todos los repositorios, wikis, propuestas y tableros de proyecto de la cuenta.
+{% ifversion not ghes %} After you delete an organization, {% data variables.product.company_short %} **cannot restore your content**. Therefore, before{% else %}Before{% endif %} you delete your organization, make sure you have a copy of all repositories, wikis, issues, and project boards from the account.
+
+{% ifversion ghes %}
+{% note %}
+
+**Note:** If necessary, a site administrator for {% data variables.product.product_location %} may be able to partially restore a deleted organization. For more information, see "[Restoring a deleted organization](/admin/user-management/managing-organizations-in-your-enterprise/restoring-a-deleted-organization)."
+
+{% endnote %}
+{% endif %}
## 2. Elimina la organización
diff --git a/translations/es-ES/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md b/translations/es-ES/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md
index a9cdd933d0f8..04f8fe0b1ad5 100644
--- a/translations/es-ES/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md
+++ b/translations/es-ES/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md
@@ -19,11 +19,11 @@ shortTitle: Inhabilitar o limitar las acciones
## Acerca de los permisos de {% data variables.product.prodname_actions %} para tu organización
-{% data reusables.github-actions.disabling-github-actions %}Para obtener más información acerca de {% data variables.product.prodname_actions %}, consulta la sección "[Acerca de {% data variables.product.prodname_actions %}](/actions/getting-started-with-github-actions/about-github-actions)".
+{% data reusables.actions.disabling-github-actions %}Para obtener más información acerca de {% data variables.product.prodname_actions %}, consulta la sección "[Acerca de {% data variables.product.prodname_actions %}](/actions/getting-started-with-github-actions/about-github-actions)".
-Puedes habilitar {% data variables.product.prodname_actions %} para todos los repositorios en tu organización. {% data reusables.github-actions.enabled-actions-description %}Puedes inhabilitar {% data variables.product.prodname_actions %} para todos los repositorios en tu organización. {% data reusables.github-actions.disabled-actions-description %}
+Puedes habilitar {% data variables.product.prodname_actions %} para todos los repositorios en tu organización. {% data reusables.actions.enabled-actions-description %}Puedes inhabilitar {% data variables.product.prodname_actions %} para todos los repositorios en tu organización. {% data reusables.actions.disabled-actions-description %}
-De manera alterna, puedes habilitar {% data variables.product.prodname_actions %} para todos los repositorios en tu organización, pero limitando las acciones que un flujo de trabajo puede ejecutar. {% data reusables.github-actions.enabled-local-github-actions %}
+De manera alterna, puedes habilitar {% data variables.product.prodname_actions %} para todos los repositorios en tu organización, pero limitando las acciones que un flujo de trabajo puede ejecutar. {% data reusables.actions.enabled-local-github-actions %}
## Administrar los permisos de {% data variables.product.prodname_actions %} para tu organización
@@ -68,7 +68,7 @@ Puedes configurar este comportamiento de una organización utilizando los siguie
{% data reusables.profile.access_org %}
{% data reusables.profile.org_settings %}
{% data reusables.organizations.settings-sidebar-actions %}
-{% data reusables.github-actions.workflows-from-public-fork-setting %}
+{% data reusables.actions.workflows-from-public-fork-setting %}
{% data reusables.actions.workflow-run-approve-link %}
{% endif %}
@@ -76,28 +76,28 @@ Puedes configurar este comportamiento de una organización utilizando los siguie
{% ifversion fpt or ghes or ghec %}
## Habilitar flujos de trabajo para las bifurcaciones de repositorios privados
-{% data reusables.github-actions.private-repository-forks-overview %}
+{% data reusables.actions.private-repository-forks-overview %}
{% ifversion ghec or ghae or ghes %}Si se inhabilita una política para una empresa, esta no podrá habilitarse para las organizaciones.{% endif %} Si una política se inhabilita para una organización, no podrá habilitarse en los repositorios. Si una organización habilita una política, esta podrá inhabilitarse para los repositorios individuales.
-{% data reusables.github-actions.private-repository-forks-options %}
+{% data reusables.actions.private-repository-forks-options %}
### Configurar la política de bifurcaciones privadas para una organización
{% data reusables.profile.access_org %}
{% data reusables.profile.org_settings %}
{% data reusables.organizations.settings-sidebar-actions %}
-{% data reusables.github-actions.private-repository-forks-configure %}
+{% data reusables.actions.private-repository-forks-configure %}
{% endif %}
{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
## Configurar los permisos del `GITHUB_TOKEN` para tu organización
-{% data reusables.github-actions.workflow-permissions-intro %}
+{% data reusables.actions.workflow-permissions-intro %}
Puedes configurar los permisos predeterminados para el `GITHUB_TOKEN` en la configuración de tu organización o tus repositorios. Si eliges la opción restringida como la predeterminada en tu configuración de organización, la misma opción se auto-seleccionará en la configuración de los repositorios dentro de dicha organización y se inhabilitará la opción permisiva. Si tu organización le pertenece a una cuenta {% data variables.product.prodname_enterprise %} y la configuración predeterminada más restringida se seleccionó en la configuración de dicha empresa, no podrás elegir la opción predeterminada permisiva en la configuración de tu organización.
-{% data reusables.github-actions.workflow-permissions-modifying %}
+{% data reusables.actions.workflow-permissions-modifying %}
### Configuring the default `GITHUB_TOKEN` permissions
diff --git a/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork.md b/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork.md
index 586100d514dc..ea4610c2fc75 100644
--- a/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork.md
+++ b/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork.md
@@ -13,6 +13,7 @@ versions:
ghec: '*'
topics:
- Pull requests
+permissions: People with write access for a forked repository can sync the fork to the upstream repository.
---
{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
@@ -20,9 +21,9 @@ topics:
## Syncing a fork from the web UI
1. On {% data variables.product.product_name %}, navigate to the main page of the forked repository that you want to sync with the upstream repository.
-1. Select the **Fetch upstream** drop-down.
+2. Select the **Fetch upstream** drop-down.
-1. Review the details about the commits from the upstream repository, then click **Fetch and merge**.
+3. Review the details about the commits from the upstream repository, then click **Fetch and merge**.
If the changes from the upstream repository cause conflicts, {% data variables.product.company_short %} will prompt you to create a pull request to resolve the conflicts.
@@ -35,6 +36,7 @@ Before you can sync your fork with an upstream repository, you must [configure a
{% data reusables.command_line.open_the_multi_os_terminal %}
2. Change the current working directory to your local project.
3. Fetch the branches and their respective commits from the upstream repository. Commits to `BRANCHNAME` will be stored in the local branch `upstream/BRANCHNAME`.
+
```shell
$ git fetch upstream
> remote: Counting objects: 75, done.
@@ -44,12 +46,16 @@ Before you can sync your fork with an upstream repository, you must [configure a
> From https://{% data variables.command_line.codeblock %}/ORIGINAL_OWNER/ORIGINAL_REPOSITORY
> * [new branch] main -> upstream/main
```
+
4. Check out your fork's local default branch - in this case, we use `main`.
+
```shell
$ git checkout main
> Switched to branch 'main'
```
+
5. Merge the changes from the upstream default branch - in this case, `upstream/main` - into your local default branch. This brings your fork's default branch into sync with the upstream repository, without losing your local changes.
+
```shell
$ git merge upstream/main
> Updating a422352..5fdff0f
diff --git a/translations/es-ES/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/about-commits.md b/translations/es-ES/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/about-commits.md
index ba51e2d5e1f2..8e90ee209d65 100644
--- a/translations/es-ES/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/about-commits.md
+++ b/translations/es-ES/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/about-commits.md
@@ -6,6 +6,7 @@ redirect_from:
- /github/committing-changes-to-your-project/why-are-my-commits-in-the-wrong-order
- /github/committing-changes-to-your-project/about-commits
- /github/committing-changes-to-your-project/creating-and-editing-commits/about-commits
+ - /pull-requests/committing-changes-to-your-project/viewing-and-comparing-commits/commit-branch-and-tag-labels
versions:
fpt: '*'
ghes: '*'
@@ -23,5 +24,22 @@ You can also create a commit on behalf of an organization. For more information,
Rebasing allows you to change a series of commits and can modify the order of the commits in your timeline. For more information, see "[About git rebase](/github/getting-started-with-github/about-git-rebase)."
+## About commit branches and tag labels
+
+You can see which branch a commit is on by looking at the labels beneath the commit on the commit page.
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.navigate-to-commit-page %}
+1. Navigate to the commit by clicking the commit message link.
+ 
+2. To see what branch the commit is on, check the label below the commit message.
+ 
+
+If your commit is not on the default branch (`main`), the label will show the branches which contain the commit. If the commit is part of an unmerged pull request, you can click the link to go to the pull request.
+
+Once the commit is on the default branch, any tags that contain the commit will be shown and the default branch will be the only branch listed. For more information on tags, see "[Git Basics - Tagging](https://git-scm.com/book/en/v2/Git-Basics-Tagging)" in the Git documentation.
+
+
+
## Further reading
-- "[Committing and reviewing changes to your project](/desktop/contributing-to-projects/committing-and-reviewing-changes-to-your-project#about-commits)" on {% data variables.product.prodname_desktop %}
+- "[Committing and reviewing changes to your project](/desktop/contributing-to-projects/committing-and-reviewing-changes-to-your-project#about-commits)" on {% data variables.product.prodname_desktop %}
\ No newline at end of file
diff --git a/translations/es-ES/content/pull-requests/committing-changes-to-your-project/viewing-and-comparing-commits/commit-branch-and-tag-labels.md b/translations/es-ES/content/pull-requests/committing-changes-to-your-project/viewing-and-comparing-commits/commit-branch-and-tag-labels.md
deleted file mode 100644
index b6fa40384a5c..000000000000
--- a/translations/es-ES/content/pull-requests/committing-changes-to-your-project/viewing-and-comparing-commits/commit-branch-and-tag-labels.md
+++ /dev/null
@@ -1,26 +0,0 @@
----
-title: Commit branch and tag labels
-intro: You can easily see what branch a commit is in by looking at the labels beneath the commit on the commit page.
-redirect_from:
- - /articles/commit-branch-and-tag-labels
- - /github/committing-changes-to-your-project/commit-branch-and-tag-labels
- - /github/committing-changes-to-your-project/viewing-and-comparing-commits/commit-branch-and-tag-labels
-versions:
- fpt: '*'
- ghes: '*'
- ghae: '*'
- ghec: '*'
-shortTitle: Branch & tag labels
----
-If your commit is not on the default branch, an indicator will show the branches which contain the commit. If the commit is part of an unmerged pull request, it will show a link.
-
-
-
-Once the commit is on the default branch, any tags that contain the commit will be shown and the default branch will be the only branch listed.
-
-
-
-## Further reading
-
-* "[Signing commits](/articles/signing-commits)"
-* "[Signing tags](/articles/signing-tags)"
diff --git a/translations/es-ES/content/pull-requests/committing-changes-to-your-project/viewing-and-comparing-commits/index.md b/translations/es-ES/content/pull-requests/committing-changes-to-your-project/viewing-and-comparing-commits/index.md
index 142130613edd..5ce680942643 100644
--- a/translations/es-ES/content/pull-requests/committing-changes-to-your-project/viewing-and-comparing-commits/index.md
+++ b/translations/es-ES/content/pull-requests/committing-changes-to-your-project/viewing-and-comparing-commits/index.md
@@ -10,7 +10,6 @@ versions:
ghae: '*'
ghec: '*'
children:
- - /commit-branch-and-tag-labels
- /comparing-commits
- /differences-between-commit-views
shortTitle: View & compare commits
diff --git a/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/enabling-or-disabling-github-discussions-for-a-repository.md b/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/enabling-or-disabling-github-discussions-for-a-repository.md
index e539d6c2d01f..3a943f54dc3d 100644
--- a/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/enabling-or-disabling-github-discussions-for-a-repository.md
+++ b/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/enabling-or-disabling-github-discussions-for-a-repository.md
@@ -11,7 +11,7 @@ topics:
redirect_from:
- /github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository
- /github/administering-a-repository/managing-repository-settings/enabling-or-disabling-github-discussions-for-a-repository
-shortTitle: Debates
+shortTitle: Discussions
---
## Habilitar o inhabilitar los {% data variables.product.prodname_discussions %} en tu repositorio
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 7398a8f6bab6..e7e83ebf5518 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
@@ -24,11 +24,11 @@ shortTitle: Administrar los ajustes de las GitHub Actions
## Acerca de los permisos de {% data variables.product.prodname_actions %} para tu repositorio
-{% data reusables.github-actions.disabling-github-actions %}Para obtener más información acerca de {% data variables.product.prodname_actions %}, consulta la sección "[Acerca de {% data variables.product.prodname_actions %}](/actions/getting-started-with-github-actions/about-github-actions)".
+{% data reusables.actions.disabling-github-actions %}Para obtener más información acerca de {% data variables.product.prodname_actions %}, consulta la sección "[Acerca de {% data variables.product.prodname_actions %}](/actions/getting-started-with-github-actions/about-github-actions)".
-Puedes habilitar {% data variables.product.prodname_actions %} para tu repositorio. {% data reusables.github-actions.enabled-actions-description %} Puedes inhabilitar {% data variables.product.prodname_actions %} totalmente para tu repositorio. {% data reusables.github-actions.disabled-actions-description %}
+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 %}
-De manera alterna, puedes habilitar {% data variables.product.prodname_actions %} en tu repositorio, pero limitar las acciones que un flujo de trabajo puede ejecutar. {% data reusables.github-actions.enabled-local-github-actions %}
+De manera alterna, puedes habilitar {% data variables.product.prodname_actions %} en tu repositorio, pero limitar las acciones que un flujo de trabajo puede ejecutar. {% data reusables.actions.enabled-local-github-actions %}
## Administrar los permisos de {% data variables.product.prodname_actions %} para tu repositorio
@@ -78,34 +78,34 @@ Puedes configurar este comportamiento para un repositorio si utilizas el siguien
{% data reusables.repositories.navigate-to-repo %}
{% data reusables.repositories.sidebar-settings %}
{% data reusables.repositories.settings-sidebar-actions %}
-{% data reusables.github-actions.workflows-from-public-fork-setting %}
+{% data reusables.actions.workflows-from-public-fork-setting %}
{% data reusables.actions.workflow-run-approve-link %}
{% endif %}
## Habilitar flujos de trabajo para las bifurcaciones de repositorios privados
-{% data reusables.github-actions.private-repository-forks-overview %}
+{% data reusables.actions.private-repository-forks-overview %}
Si se inhabilita una política para una {% ifversion ghec or ghae or ghes %}empresa u{% endif %} organización, esta no puede habilitarse para un repositorio.
-{% data reusables.github-actions.private-repository-forks-options %}
+{% data reusables.actions.private-repository-forks-options %}
### Configurar la política de bifurcaciones privadas para un repositorio
{% data reusables.repositories.navigate-to-repo %}
{% data reusables.repositories.sidebar-settings %}
{% data reusables.repositories.settings-sidebar-actions %}
-{% data reusables.github-actions.private-repository-forks-configure %}
+{% data reusables.actions.private-repository-forks-configure %}
{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
## Configurar los permisos del `GITHUB_TOKEN` para tu repositorio
-{% data reusables.github-actions.workflow-permissions-intro %}
+{% data reusables.actions.workflow-permissions-intro %}
Los permisos predeterminados también pueden configurarse en los ajustes de la organización. Si el predeterminado más restringido se seleccionó en la configuración de la organización, la misma opción se autoselecciona en tu configuración de repositorio y la opción permisiva se inhabilita.
-{% data reusables.github-actions.workflow-permissions-modifying %}
+{% data reusables.actions.workflow-permissions-modifying %}
### Configuring the default `GITHUB_TOKEN` permissions
@@ -152,4 +152,4 @@ Tambièn puedes definir un periodo de retenciòn personalizado para un artefacto
{% data reusables.repositories.navigate-to-repo %}
{% data reusables.repositories.sidebar-settings %}
{% data reusables.repositories.settings-sidebar-actions %}
-{% data reusables.github-actions.change-retention-period-for-artifacts-logs %}
+{% data reusables.actions.change-retention-period-for-artifacts-logs %}
diff --git a/translations/es-ES/content/rest/overview/index.md b/translations/es-ES/content/rest/overview/index.md
index 61c1aef1351c..bb4ae9013219 100644
--- a/translations/es-ES/content/rest/overview/index.md
+++ b/translations/es-ES/content/rest/overview/index.md
@@ -18,5 +18,6 @@ children:
- /libraries
- /openapi-description
- /endpoints-available-for-github-apps
+ - /permissions-required-for-github-apps
---
diff --git a/translations/es-ES/content/rest/reference/permissions-required-for-github-apps.md b/translations/es-ES/content/rest/overview/permissions-required-for-github-apps.md
similarity index 99%
rename from translations/es-ES/content/rest/reference/permissions-required-for-github-apps.md
rename to translations/es-ES/content/rest/overview/permissions-required-for-github-apps.md
index dc83d50fd395..d02f6f683695 100644
--- a/translations/es-ES/content/rest/reference/permissions-required-for-github-apps.md
+++ b/translations/es-ES/content/rest/overview/permissions-required-for-github-apps.md
@@ -3,6 +3,7 @@ title: Permisos que requieren las Github Apps
intro: 'Puedes encontrar los permisos que requiere cada terminal compatible con {% data variables.product.prodname_github_app %}.'
redirect_from:
- /v3/apps/permissions
+ - /rest/reference/permissions-required-for-github-apps
versions:
fpt: '*'
ghes: '*'
@@ -104,7 +105,7 @@ _Miembros de la organización_
- [`GET /orgs/:org/public_members`](/rest/reference/orgs#list-public-organization-members)
- [`GET /orgs/:org/public_members/:username`](/rest/reference/orgs#check-public-organization-membership-for-a-user)
-_Search_
+_Buscar_
- [`GET /search/code`](/rest/reference/search#search-code)
- [`GET /search/commits`](/rest/reference/search#search-commits)
- [`GET /search/issues`](/rest/reference/search#search-issues-and-pull-requests)
@@ -399,7 +400,7 @@ _Git_
- [`GET /repos/:owner/:repo/git/trees/:sha`](/rest/reference/git#get-a-tree) (:read)
{% ifversion fpt or ghec %}
-_Import_
+_Importar_
- [`GET /repos/:owner/:repo/import`](/rest/reference/migrations#get-an-import-status) (:read)
- [`PUT /repos/:owner/:repo/import`](/rest/reference/migrations#start-an-import) (:write)
- [`PATCH /repos/:owner/:repo/import`](/rest/reference/migrations#update-an-import) (:write)
diff --git a/translations/es-ES/content/rest/reference/actions.md b/translations/es-ES/content/rest/reference/actions.md
index 6ce95aca37ed..683cb891809d 100644
--- a/translations/es-ES/content/rest/reference/actions.md
+++ b/translations/es-ES/content/rest/reference/actions.md
@@ -13,93 +13,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-
-The {% data variables.product.prodname_actions %} API enables you to manage {% data variables.product.prodname_actions %} using the REST API. {% data reusables.actions.actions-authentication %} {% data variables.product.prodname_github_apps %} require the permissions mentioned in each endpoint. For more information, see "[{% data variables.product.prodname_actions %} Documentation](/actions)."
-
-{% for operation in currentRestOperations %}
- {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
-{% endfor %}
-
-## Artifacts
-
-The Artifacts API allows you to download, delete, and retrieve information about workflow artifacts. {% data reusables.actions.about-artifacts %} For more information, see "[Persisting workflow data using artifacts](/actions/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)."
-
-{% data reusables.actions.actions-authentication %} {% data reusables.actions.actions-app-actions-permissions-api %}
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'artifacts' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% ifversion fpt or ghes > 2.22 or ghae or ghec %}
-## Permissions
-
-The Permissions API allows you to set permissions for what enterprises, organizations, and repositories are allowed to run {% data variables.product.prodname_actions %}, and what actions are allowed to run.{% ifversion fpt or ghec or ghes %} For more information, see "[Usage limits, billing, and administration](/actions/reference/usage-limits-billing-and-administration#disabling-or-limiting-github-actions-for-your-repository-or-organization)."{% endif %}
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'permissions' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-{% endif %}
-
-## Secrets
-
-The Secrets API lets you create, update, delete, and retrieve information about encrypted secrets. {% data reusables.actions.about-secrets %} For more information, see "[Creating and using encrypted secrets](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)."
-
-{% data reusables.actions.actions-authentication %} {% data variables.product.prodname_github_apps %} must have the `secrets` permission to use this API. Authenticated users must have collaborator access to a repository to create, update, or read secrets.
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'secrets' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## Self-hosted runners
-
-{% data reusables.actions.ae-self-hosted-runners-notice %}
-
-The Self-hosted Runners API allows you to register, view, and delete self-hosted runners. {% data reusables.actions.about-self-hosted-runners %} For more information, see "[Hosting your own runners](/actions/hosting-your-own-runners)."
-
-{% data reusables.actions.actions-authentication %} {% data variables.product.prodname_github_apps %} must have the `administration` permission for repositories the `organization_self_hosted_runners` permission for organizations. Authenticated users must have admin access to repositories or organizations, or the `manage_runners:enterprise` scope for enterprises to use this API.
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'self-hosted-runners' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## Self-hosted runner groups
-
-{% data reusables.actions.ae-self-hosted-runners-notice %}
-
-The Self-hosted Runners Groups API allows you manage groups of self-hosted runners. For more information, see "[Managing access to self-hosted runners using groups](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups)."
-
-{% data reusables.actions.actions-authentication %} {% data variables.product.prodname_github_apps %} must have the `administration` permission for repositories or the `organization_self_hosted_runners` permission for organizations. Authenticated users must have admin access to repositories or organizations, or the `manage_runners:enterprise` scope for enterprises to use this API.
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'self-hosted-runner-groups' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## Workflows
-
-The Workflows API allows you to view workflows for a repository. {% data reusables.actions.about-workflows %} For more information, see "[Automating your workflow with GitHub Actions](/actions/automating-your-workflow-with-github-actions)."
-
-{% data reusables.actions.actions-authentication %} {% data reusables.actions.actions-app-actions-permissions-api %}
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'workflows' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## Workflow jobs
-
-The Workflow Jobs API allows you to view logs and workflow jobs. {% data reusables.actions.about-workflow-jobs %} For more information, see "[Workflow syntax for GitHub Actions](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions)".
-
-{% data reusables.actions.actions-authentication %} {% data reusables.actions.actions-app-actions-permissions-api %}
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'workflow-jobs' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## Workflow runs
-
-The Workflow Runs API allows you to view, re-run, cancel, and view logs for workflow runs. {% data reusables.actions.about-workflow-runs %} For more information, see "[Managing a workflow run](/actions/automating-your-workflow-with-github-actions/managing-a-workflow-run)."
-
-{% data reusables.actions.actions-authentication %} {% data reusables.actions.actions-app-actions-permissions-api %}
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'workflow-runs' %}{% include rest_operation %}{% endif %}
-{% endfor %}
+
diff --git a/translations/es-ES/content/rest/reference/activity.md b/translations/es-ES/content/rest/reference/activity.md
index 804b4094d240..469e3fd72e41 100644
--- a/translations/es-ES/content/rest/reference/activity.md
+++ b/translations/es-ES/content/rest/reference/activity.md
@@ -13,186 +13,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-{% for operation in currentRestOperations %}
- {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
-{% endfor %}
-
-## Events
-
-The Events API is a read-only API to the {% data variables.product.prodname_dotcom %} events. These events power the various activity streams on the site.
-
-The Events API can return different types of events triggered by activity on {% data variables.product.product_name %}. For more information about the specific events that you can receive from the Events API, see "[{% data variables.product.prodname_dotcom %} Event types](/developers/webhooks-and-events/github-event-types)." An events API for repository issues is also available. For more information, see the "[Issue Events API](/rest/reference/issues#events)."
-
-Events are optimized for polling with the "ETag" header. If no new events have been triggered, you will see a "304 Not Modified" response, and your current rate limit will be untouched. There is also an "X-Poll-Interval" header that specifies how often (in seconds) you are allowed to poll. In times of high server load, the time may increase. Please obey the header.
-
-``` shell
-$ curl -I {% data variables.product.api_url_pre %}/users/tater/events
-> HTTP/2 200
-> X-Poll-Interval: 60
-> ETag: "a18c3bded88eb5dbb5c849a489412bf3"
-
-# The quotes around the ETag value are important
-$ curl -I {% data variables.product.api_url_pre %}/users/tater/events \
-$ -H 'If-None-Match: "a18c3bded88eb5dbb5c849a489412bf3"'
-> HTTP/2 304
-> X-Poll-Interval: 60
-```
-
-Only events created within the past 90 days will be included in timelines. Events older than 90 days will not be included (even if the total number of events in the timeline is less than 300).
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'events' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## Feeds
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'feeds' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-### Example of getting an Atom feed
-
-To get a feed in Atom format, you must specify the `application/atom+xml` type in the `Accept` header. For example, to get the Atom feed for GitHub security advisories:
-
- curl -H "Accept: application/atom+xml" https://github.com/security-advisories
-
-#### Response
-
-```shell
-HTTP/2 200
-```
-
-```xml
-
-
- tag:github.com,2008:/security-advisories
-
- GitHub Security Advisory Feed
-
- GitHub
-
- 2019-01-14T19:34:52Z
-
- tag:github.com,2008:GHSA-abcd-12ab-23cd
- 2018-07-26T15:14:52Z
- 2019-01-14T19:34:52Z
- [GHSA-abcd-12ab-23cd] Moderate severity vulnerability that affects Octoapp
-
-
- <p>Octoapp node module before 4.17.5 suffers from a Modification of Assumed-Immutable Data (MAID) vulnerability via defaultsDeep, merge, and mergeWith functions, which allows a malicious user to modify the prototype of "Object" via <strong>proto</strong>, causing the addition or modification of an existing property that will exist on all objects.</p>
- <p><strong>Affected Packages</strong></p>
-
- <dl>
- <dt>Octoapp</dt>
- <dd>Ecosystem: npm</dd>
- <dd>Severity: moderate</dd>
- <dd>Versions: < 4.17.5</dd>
- <dd>Fixed in: 4.17.5</dd>
- </dl>
-
- <p><strong>References</strong></p>
-
- <ul>
- <li>https://nvd.nist.gov/vuln/detail/CVE-2018-123</li>
- </ul>
-
-
-
-
-```
-
-## Notifications
-
-Users receive notifications for conversations in repositories they watch including:
-
-* Issues and their comments
-* Pull Requests and their comments
-* Comments on any commits
-
-Notifications are also sent for conversations in unwatched repositories when the user is involved including:
-
-* **@mentions**
-* Issue assignments
-* Commits the user authors or commits
-* Any discussion in which the user actively participates
-
-All Notification API calls require the `notifications` or `repo` API scopes. Doing this will give read-only access to some issue and commit content. You will still need the `repo` scope to access issues and commits from their respective endpoints.
-
-Notifications come back as "threads". A thread contains information about the current discussion of an issue, pull request, or commit.
-
-Notifications are optimized for polling with the `Last-Modified` header. If there are no new notifications, you will see a `304 Not Modified` response, leaving your current rate limit untouched. There is an `X-Poll-Interval` header that specifies how often (in seconds) you are allowed to poll. In times of high server load, the time may increase. Please obey the header.
-
-``` shell
-# Add authentication to your requests
-$ curl -I {% data variables.product.api_url_pre %}/notifications
-HTTP/2 200
-Last-Modified: Thu, 25 Oct 2012 15:16:27 GMT
-X-Poll-Interval: 60
-
-# Pass the Last-Modified header exactly
-$ curl -I {% data variables.product.api_url_pre %}/notifications
-$ -H "If-Modified-Since: Thu, 25 Oct 2012 15:16:27 GMT"
-> HTTP/2 304
-> X-Poll-Interval: 60
-```
-
-### Notification reasons
-
-When retrieving responses from the Notifications API, each payload has a key titled `reason`. These correspond to events that trigger a notification.
-
-Here's a list of potential `reason`s for receiving a notification:
-
-Reason Name | Description
-------------|------------
-`assign` | You were assigned to the issue.
-`author` | You created the thread.
-`comment` | You commented on the thread.
-`ci_activity` | A {% data variables.product.prodname_actions %} workflow run that you triggered was completed.
-`invitation` | You accepted an invitation to contribute to the repository.
-`manual` | You subscribed to the thread (via an issue or pull request).
-`mention` | You were specifically **@mentioned** in the content.
-`review_requested` | You, or a team you're a member of, were requested to review a pull request.{% ifversion fpt or ghec %}
-`security_alert` | {% data variables.product.prodname_dotcom %} discovered a [security vulnerability](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies) in your repository.{% endif %}
-`state_change` | You changed the thread state (for example, closing an issue or merging a pull request).
-`subscribed` | You're watching the repository.
-`team_mention` | You were on a team that was mentioned.
-
-Note that the `reason` is modified on a per-thread basis, and can change, if the `reason` on a later notification is different.
-
-For example, if you are the author of an issue, subsequent notifications on that issue will have a `reason` of `author`. If you're then **@mentioned** on the same issue, the notifications you fetch thereafter will have a `reason` of `mention`. The `reason` remains as `mention`, regardless of whether you're ever mentioned again.
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'notifications' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## Starring
-
-Repository starring is a feature that lets users bookmark repositories. Stars are shown next to repositories to show an approximate level of interest. Stars have no effect on notifications or the activity feed.
-
-### Starring vs. Watching
-
-In August 2012, we [changed the way watching
-works](https://github.com/blog/1204-notifications-stars) on {% data variables.product.prodname_dotcom %}. Many API
-client applications may be using the original "watcher" endpoints for accessing
-this data. You can now start using the "star" endpoints instead (described
-below). For more information, see the [Watcher API Change post](https://developer.github.com/changes/2012-09-05-watcher-api/) and the "[Repository Watching API](/rest/reference/activity#watching)."
-
-### Custom media types for starring
-
-There is one supported custom media type for the Starring REST API. When you use this custom media type, you will receive a response with the `starred_at` timestamp property that indicates the time the star was created. The response also has a second property that includes the resource that is returned when the custom media type is not included. The property that contains the resource will be either `user` or `repo`.
-
- application/vnd.github.v3.star+json
-
-For more information about media types, see "[Custom media types](/rest/overview/media-types)."
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'starring' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## Watching
-
-Watching a repository registers the user to receive notifications on new discussions, as well as events in the user's activity feed. For simple repository bookmarks, see "[Repository starring](/rest/reference/activity#starring)."
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'watching' %}{% include rest_operation %}{% endif %}
-{% endfor %}
+
\ No newline at end of file
diff --git a/translations/es-ES/content/rest/reference/apps.md b/translations/es-ES/content/rest/reference/apps.md
index fe8a5dc5ffa8..49509192249e 100644
--- a/translations/es-ES/content/rest/reference/apps.md
+++ b/translations/es-ES/content/rest/reference/apps.md
@@ -13,66 +13,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-{% data reusables.apps.general-apps-restrictions %}
-
-This page lists endpoints that you can access while authenticated as a GitHub App. See "[Authenticating as a GitHub App](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-a-github-app)" to learn more.
-
-When authenticated as a GitHub App, the GitHub Apps API enables you to get high-level information about a GitHub App as well as specific information about installations of an app.
-
-You can access REST API v3 endpoints while authenticated as a GitHub App. These endpoints have a "Notes" section that contains a bullet point that says "Works with GitHub Apps." You can also access these endpoints while authenticated as a user.
-
-A subset of REST API v3 endpoints requires authenticating as a GitHub App installation. See [Installations](/rest/reference/apps#installations) for a list of these endpoints.
-
-{% for operation in currentRestOperations %}
- {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
-{% endfor %}
-
-## OAuth Applications API
-
-You can use this API to manage the OAuth tokens an OAuth application uses to access people's accounts on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}.
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'oauth-applications' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## Installations
-
-The Installations API enables you to get information about installations of your GitHub App and perform actions within those installations. An _installation_ refers to any user or organization account that has installed the app. For information on how to authenticate as an installation and limit access to specific repositories, see "[Authenticating as an installation](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation)."
-
-To list all GitHub App installations for an organization, see "[List app installations for an organization](/rest/reference/orgs#list-app-installations-for-an-organization)."
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'installations' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% ifversion fpt or ghec %}
-## Marketplace
-
-For more information about {% data variables.product.prodname_marketplace %}, see "[GitHub Marketplace](/marketplace/)."
-
-The {% data variables.product.prodname_marketplace %} API allows you to see which customers are using a pricing plan, see a customer's purchases, and see if an account has an active subscription.
-
-### Testing with stubbed endpoints
-
-This API includes endpoints that allow you to [test your {% data variables.product.prodname_github_app %}](/marketplace/integrating-with-the-github-marketplace-api/testing-github-marketplace-apps/) with **stubbed data**. Stubbed data is hard-coded, fake data that will not change based on actual subscriptions.
-
-To test with stubbed data, use a stubbed endpoint in place of its production counterpart. This allows you to test whether API logic succeeds before listing {% data variables.product.prodname_github_apps %} on {% data variables.product.prodname_marketplace %}.
-
-Be sure to replace stubbed endpoints with production endpoints before deploying your {% data variables.product.prodname_github_app %}.
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'marketplace' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% endif %}
-
-{% ifversion fpt or ghes > 2.22 or ghae or ghec %}
-## Webhooks
-
-A {% data variables.product.prodname_github_app %}'s webhook allows you to receive HTTP `POST` payloads whenever certain events happen for an app. {% data reusables.webhooks.webhooks-rest-api-links %}
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'webhooks' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% endif %}
+
\ No newline at end of file
diff --git a/translations/es-ES/content/rest/reference/billing.md b/translations/es-ES/content/rest/reference/billing.md
index fe0cf42be4a1..42a5e06e06a2 100644
--- a/translations/es-ES/content/rest/reference/billing.md
+++ b/translations/es-ES/content/rest/reference/billing.md
@@ -10,8 +10,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-You can get billing information for an enterprise. For more information, see the "[{% data variables.product.prodname_dotcom %} Enterprise administration](/rest/reference/enterprise-admin#billing)" REST API.
-
-{% for operation in currentRestOperations %}
- {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
-{% endfor %}
+
\ No newline at end of file
diff --git a/translations/es-ES/content/rest/reference/branches.md b/translations/es-ES/content/rest/reference/branches.md
index 2c9471b3b6b5..9ae8088834ac 100644
--- a/translations/es-ES/content/rest/reference/branches.md
+++ b/translations/es-ES/content/rest/reference/branches.md
@@ -12,11 +12,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-{% for operation in currentRestOperations %}
- {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
-{% endfor %}
-
-## Ramas protegidas
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'branch-protection' %}{% include rest_operation %}{% endif %}
-{% endfor %}
+
diff --git a/translations/es-ES/content/rest/reference/checks.md b/translations/es-ES/content/rest/reference/checks.md
index 723346a74c31..2075cb128be0 100644
--- a/translations/es-ES/content/rest/reference/checks.md
+++ b/translations/es-ES/content/rest/reference/checks.md
@@ -12,26 +12,7 @@ topics:
- API
miniTocMaxHeadingLevel: 3
---
-You can create apps that perform continuous integration, code linting, or code scanning services and provide detailed feedback on commits. For more information, see "[Getting started with the checks API](/rest/guides/getting-started-with-the-checks-api)" and "[Creating CI tests with the Checks API](/apps/quickstart-guides/creating-ci-tests-with-the-checks-api/)."
-{% for operation in currentRestOperations %}
- {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
-{% endfor %}
-
-## Check Runs
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'runs' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## Check Suites
-
-{% note %}
-
- **Note:** A GitHub App only receives one [`check_suite`](/webhooks/event-payloads/#check_suite) event per commit SHA, even if you push the commit SHA to more than one branch. To find out when a commit SHA is pushed to a branch, you can subscribe to branch [`create`](/webhooks/event-payloads/#create) events.
-
-{% endnote %}
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'suites' %}{% include rest_operation %}{% endif %}
-{% endfor %}
+
\ No newline at end of file
diff --git a/translations/es-ES/content/rest/reference/code-scanning.md b/translations/es-ES/content/rest/reference/code-scanning.md
index 43ce3828fa4c..87f7efa0a3c6 100644
--- a/translations/es-ES/content/rest/reference/code-scanning.md
+++ b/translations/es-ES/content/rest/reference/code-scanning.md
@@ -17,20 +17,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-{% data reusables.code-scanning.beta %}
-
-La API del {% data variables.product.prodname_code_scanning %} te permite recuperar y actualizar las alertas del {% data variables.product.prodname_code_scanning %} desde un repositorio. Puedes utilizar las terminales para crear reportes automatizados para las alertas del {% data variables.product.prodname_code_scanning %} en una organización o cargar resutlados de análisis que se hayan generado utilizando con herramientas fuera de línea del {% data variables.product.prodname_code_scanning %}. Para obtener más información, consulta la sección "[Encontrar vulnerabilidades de seguridad y errores en tu código](/github/finding-security-vulnerabilities-and-errors-in-your-code)".
-
-{% ifversion fpt or ghes > 3.0 or ghae or ghec %}
-### Tipos de medios personalizados para el {% data variables.product.prodname_code_scanning %}
-
-Hay un tipo de medios personalizado compatible para la API de REST del {% data variables.product.prodname_code_scanning %}.
-
- application/sarif+json
-
-Puedes utilizarla con las solicitudes de tipo `GET` que envíes a la terminal de `/analyses/{analysis_id}`. Para obtener más información sobre esta operación, consulta la sección [Obtén un análisis del {% data variables.product.prodname_code_scanning %} para un repositorio](#get-a-code-scanning-analysis-for-a-repository)". Cuando utilices este tipo de medios con esta operación, la respuesta incluirá un subconjunto de los datos actuals que se cargaron para el análisis específico en vez del resumen del análisis que se devuelve cuando utilizas el tipo de medios predeterminado. La respuesta también incluye datos adicionales, tales como las propiedades de `github/alertNumber` y `github/alertUrl`. Estos datos tienen formato de [SARIF versión 2.1.0](https://docs.oasis-open.org/sarif/sarif/v2.1.0/cs01/sarif-v2.1.0-cs01.html).
-
-Para obtener más información, consulta la sección "[Tipos de medios](/rest/overview/media-types)".
-{% endif %}
-
-{% include rest_operations_at_current_path %}
+
diff --git a/translations/es-ES/content/rest/reference/codes-of-conduct.md b/translations/es-ES/content/rest/reference/codes-of-conduct.md
index 3f5dab72a934..dfd64ae7b3d8 100644
--- a/translations/es-ES/content/rest/reference/codes-of-conduct.md
+++ b/translations/es-ES/content/rest/reference/codes-of-conduct.md
@@ -14,6 +14,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-Puedes usar la API de Códigos de Conducta para recuperar la información acerca del código de conducta de un repositorio. Para obtener el código de conducta de un repositorio, utiliza la terminal "[Obtener un repositorio](/rest/reference/repos#get-a-repository)".
-
-{% include rest_operations_at_current_path %}
+
diff --git a/translations/es-ES/content/rest/reference/codespaces.md b/translations/es-ES/content/rest/reference/codespaces.md
index 9b5109d8fbc3..6bc0d14872a3 100644
--- a/translations/es-ES/content/rest/reference/codespaces.md
+++ b/translations/es-ES/content/rest/reference/codespaces.md
@@ -10,24 +10,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-{% data reusables.codespaces.codespaces-api-beta-note %}
-
-La API de {% data variables.product.prodname_codespaces %} te permite administrar las {% data variables.product.prodname_codespaces %} utilizando la API de REST. Esta API se encuentra disponible para los usuarios autenticados y las Apps de OAuth, pero no para las GitHub Apps. Para obtener más información, consulta la sección "[{% data variables.product.prodname_codespaces %}](/codespaces)".
-
-{% for operation in currentRestOperations %}
- {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
-{% endfor %}
-
-## Máquinas
-La API de máquinas permite que un usuario determine qué tipos de máquina están disponibles para crear un codespace, ya sea en un repositorio definido o como un usuario autenticado. Para obtener más información, consulta la sección "[Acerca de los tipos de máquina](/codespaces/developing-in-codespaces/changing-the-machine-type-for-your-codespace#about-machine-types)".
-
-También puedes utilizar esta información cuando cambies la máquina de un codespace existente actualizando su propiedad de `machine`. La actualización de la máquina tomará lugar la siguiente vez que el codespace se reinicie. Para obtener más información, consulta la sección "[Cambiar el tipo de máquina de tu codespace](/codespaces/developing-in-codespaces/changing-the-machine-type-for-your-codespace)".
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'machines' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## Secretos
-La API de secretos permite que un usuario cree, liste y borre secretos (tales como los tokens de acceso para los servicios en la nube) así como asignar secretos a los repositorios a los que el usuario tenga acceso. Estos secretos se hacen disponibles para el codespace en el tiempo de ejecución. Para obtener más información, consulta la sección "[Administrar los secretos cifrados para tu codespace](/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces)".
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'secrets' %}{% include rest_operation %}{% endif %}
-{% endfor %}
+
diff --git a/translations/es-ES/content/rest/reference/collaborators.md b/translations/es-ES/content/rest/reference/collaborators.md
index de2d31a5110e..382a5a9921f6 100644
--- a/translations/es-ES/content/rest/reference/collaborators.md
+++ b/translations/es-ES/content/rest/reference/collaborators.md
@@ -12,20 +12,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-{% for operation in currentRestOperations %}
- {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
-{% endfor %}
-
-## Invitaciones
-
-La API de Invitaciones al Repositorio permite a los usuarios o a los servicios externos invitar a otros usuarios para colaborar en un repositorio. Los usuarios invitados (o los servicios externos en nombre de estos) pueden elegir aceptar o rechazar la invitación.
-
-Toma en cuenta que el [alcance de OAuth](/developers/apps/scopes-for-oauth-apps) `repo:invite` otorga un acceso dirigido a las invitaciones **sin** otorgar también el acceso al código del repositorio, mientras que el alcance `repo` otorga permisos para el código así como para las invitaciones.
-
-### Invitar a un usuario a un repositorio
-
-Utiliza la terminal de la API para agregar un colaborador. Para obtener más información, consulta la sección "[Agregar un colaborador del repositorio](/rest/reference/collaborators#add-a-repository-collaborator)".
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'invitations' %}{% include rest_operation %}{% endif %}
-{% endfor %}
+
diff --git a/translations/es-ES/content/rest/reference/commits.md b/translations/es-ES/content/rest/reference/commits.md
index 2ad89b871979..78cf57b40ee2 100644
--- a/translations/es-ES/content/rest/reference/commits.md
+++ b/translations/es-ES/content/rest/reference/commits.md
@@ -12,41 +12,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-{% for operation in currentRestOperations %}
- {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
-{% endfor %}
-
-## Comentarios sobre confirmación de cambios
-
-### Tipos de medios personalizados para los comentarios de las confirmaciones
-
-Estos son los tipos de medios compatibles para los comentarios de las confirmaciones. Puedes leer más sobre el uso de tipos de medios en la API [aquí](/rest/overview/media-types).
-
- application/vnd.github-commitcomment.raw+json
- application/vnd.github-commitcomment.text+json
- application/vnd.github-commitcomment.html+json
- application/vnd.github-commitcomment.full+json
-
-Para obtener más información, consulta la sección "[Tipos de medios personalizados](/rest/overview/media-types)".
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'comments' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## Estados de confirmación
-
-La API de estados permite que los servicios externos marquen las confirmaciones con un estado de `error`, `failure`, `pending`, o `success`, el cual se refleja después en las solicitudes de extracción que involucran a esas confirmaciones.
-
-Los estados también incluyen una `description` y una `target_url` opcionales, y recomendamos ampliamente proporcionarlas, ya que hacen mucho más útiles a los estados en la IU de GitHub.
-
-Como ejemplo, un uso común es que los servicios de integración contínua marquen a las confirmaciones como compilaciones que pasan o fallan utilizando los estados. La `target_url` sería la URL completa de la salida de la compilación, y la `description` sería el resumen de alto nivel de lo que pasó con la compilación.
-
-Los estados pueden incluir un `context` para indicar qué servicio está proporcionando ese estado. Por ejemplo, puedes hacer que tu servicio de integración continua cargue estados con un contexto de `ci`, y que una herramienta de auditoria de seguridad cargue estados con un contexto de `security`. Puedes utilizar entonces el [Obtener el estado combinado para una referencia específica](/rest/reference/commits#get-the-combined-status-for-a-specific-reference) para recuperar todo el estado de una confirmación.
-
-Toma en cuenta que el [alcance de OAuth](/developers/apps/scopes-for-oauth-apps) de `repo:status` otorga acceso dirigido a los estados **sin** otorgar también el acceso al código del repositorio, mientras que el alcance `repo` otorga permisos para el código y también para los estados.
-
-Si estás desarrollando una GitHub App y quieres proporcionar información más detallada sobre un servicio externo, tal vez quieras utilizar la [API de Verificaciones](/rest/reference/checks).
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'statuses' %}{% include rest_operation %}{% endif %}
-{% endfor %}
+
diff --git a/translations/es-ES/content/rest/reference/dependabot.md b/translations/es-ES/content/rest/reference/dependabot.md
index a7bfdc6d248b..5fe2940b7c99 100644
--- a/translations/es-ES/content/rest/reference/dependabot.md
+++ b/translations/es-ES/content/rest/reference/dependabot.md
@@ -10,10 +10,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-The {% data variables.product.prodname_dependabot %} Secrets API lets you create, update, delete, and retrieve information about encrypted secrets. {% data reusables.actions.about-secrets %} Para obtener más información, consulta "[Administrar los secretos cifrados para el Dependabot](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-encrypted-secrets-for-dependabot)".
-
-{% data reusables.actions.actions-authentication %} {% data variables.product.prodname_github_apps %} must have the `dependabot_secrets` permission to use this API. Los usuarios autenticados deben tener acceso de colaborador en el repositorio para crear, actualizar o leer los secretos.
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'secrets' %}{% include rest_operation %}{% endif %}
-{% endfor %}
+
\ No newline at end of file
diff --git a/translations/es-ES/content/rest/reference/deployments.md b/translations/es-ES/content/rest/reference/deployments.md
index 0117c8e6a3cf..58fa4aca8edd 100644
--- a/translations/es-ES/content/rest/reference/deployments.md
+++ b/translations/es-ES/content/rest/reference/deployments.md
@@ -12,81 +12,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-Los despliegues son slicitudes para desplegar una ref específica (rma, SHA, etiqueta). GitHub despliega un [evento de `deployment`](/developers/webhooks-and-events/webhook-events-and-payloads#deployment) al que puedan escuchar los servicios externos y al con el cual puedan actuar cuando se creen los despliegues nuevos. Los despliegues habilitan a los desarrolladores y a las organizaciones para crear herramientas sin conexión directa en torno a los despliegues, sin tener que preocuparse acerca de los detalles de implementación de entregar tipos de aplicaciones diferentes (por ejemplo, web o nativas).
-
-Los estados de despliegue permiten que los servicios externos marquen estos despliegues con un estado de `error`, `failure`, `pending`, `in_progress`, `queued`, o `success` que pueden consumir los sistemas que escuchan a los [eventos de `deployment_status`](/developers/webhooks-and-events/webhook-events-and-payloads#deployment_status).
-
-Los estados de despliegue también incluyen una `description` y una `log_url` opcionales, las cuales se recomiendan ampliamente, ya que hacen que los estados de despliegue sean más útiles. La `log_url` es la URL completa para la salida del despliegue, y la `description` es el resumen de alto nivel de lo que pasó con este despliegue.
-
-GitHub envía eventos de `deployment` y `deployment_status` cuando se crean despliegues y estados de despliegue nuevos. Estos eventos permiten que las integraciones de terceros reciban respuesta de las solicitudes de despliegue y actualizan el estado de un despliegue conforme éste progrese.
-
-Debajo encontrarás un diagrama de secuencia simple que explica cómo funcionarían estas interacciones.
-
-```
-+---------+ +--------+ +-----------+ +-------------+
-| Tooling | | GitHub | | 3rd Party | | Your Server |
-+---------+ +--------+ +-----------+ +-------------+
- | | | |
- | Create Deployment | | |
- |--------------------->| | |
- | | | |
- | Deployment Created | | |
- |<---------------------| | |
- | | | |
- | | Deployment Event | |
- | |---------------------->| |
- | | | SSH+Deploys |
- | | |-------------------->|
- | | | |
- | | Deployment Status | |
- | |<----------------------| |
- | | | |
- | | | Deploy Completed |
- | | |<--------------------|
- | | | |
- | | Deployment Status | |
- | |<----------------------| |
- | | | |
-```
-
-Ten en cuenta que GitHub jamás accede a tus servidores realmente. La interacción con los eventos de despliegue dependerá de tu integración de terceros. Varios sistemas pueden escuchar a los eventos de despliegue, y depende de cada uno de ellos decidir si son responsables de cargar el código a tus servidores, si crean código nativo, etc.
-
-Toma en cuenta que el [Alcance de OAuth](/developers/apps/scopes-for-oauth-apps) de `repo_deployment` otorga acceso dirigido para los despliegues y estados de despliegue **sin** otorgar acceso al código del repositorio, mientras que {% ifversion not ghae %} los alcances de `public_repo` y{% endif %}`repo` también otorgan permisos para el código.
-
-### Despliegues inactivos
-
-Cuando configuras el estado de un despliegue como `success`, entonces todos los despliegues anteriores que no sean transitorios ni de producción y que se encuentren en el mismo repositorio con el mismo ambiente se convertirán en `inactive`. Para evitar esto, puedes configurar a `auto_inactive` como `false` cuando creas el estado del servidor.
-
-Puedes comunicar que un ambiente transitorio ya no existe si configuras el `state` como `inactive`. El configurar al `state` como `inactive`muestra el despliegue como `destroyed` en {% data variables.product.prodname_dotcom %} y elimina el acceso al mismo.
-
-{% for operation in currentRestOperations %}
- {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
-{% endfor %}
-
-## Estados de despliegue
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'statuses' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## Llaves de implementación
-
-{% data reusables.repositories.deploy-keys %}
-
-Las llaves de despliegue pueden ya sea configurarse utilizando las siguientes terminales de la API, o mediante GitHub. Para aprender cómo configurar las llaves de despliegue en GitHub, consulta la sección "[Administrar las llaves de despliegue](/developers/overview/managing-deploy-keys)".
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'keys' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
-## Ambientes
-
-La API de Ambientes te permite crear, configurar y borrar ambientes. Para obtener más información sobre los ambientes, consulta la sección "[Utilizar ambientes para despliegue](/actions/deployment/using-environments-for-deployment)". Para administrar los secretos de ambiente, consulta la sección "[Secretos](/rest/reference/actions#secrets)".
-
-{% data reusables.gated-features.environments %}
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'environments' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-{% endif %}
+
diff --git a/translations/es-ES/content/rest/reference/emojis.md b/translations/es-ES/content/rest/reference/emojis.md
index 3cdea546474f..0c28f7ce59f3 100644
--- a/translations/es-ES/content/rest/reference/emojis.md
+++ b/translations/es-ES/content/rest/reference/emojis.md
@@ -14,4 +14,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-{% include rest_operations_at_current_path %}
+
diff --git a/translations/es-ES/content/rest/reference/enterprise-admin.md b/translations/es-ES/content/rest/reference/enterprise-admin.md
index 303f997677e8..c1f2d237c5fd 100644
--- a/translations/es-ES/content/rest/reference/enterprise-admin.md
+++ b/translations/es-ES/content/rest/reference/enterprise-admin.md
@@ -16,309 +16,6 @@ miniTocMaxHeadingLevel: 3
shortTitle: Enterprise administration
---
-{% ifversion fpt or ghec %}
-
-{% note %}
-
-**Note:** This article applies to {% data variables.product.prodname_ghe_cloud %}. To see the {% data variables.product.prodname_ghe_managed %} or {% data variables.product.prodname_ghe_server %} version, use the **{% data ui.pages.article_version %}** drop-down menu.
-
-{% endnote %}
-
-{% endif %}
-
-### Endpoint URLs
-
-REST API endpoints{% ifversion ghes %}—except [Management Console](#management-console) API endpoints—{% endif %} are prefixed with the following URL:
-
-```shell
-{% data variables.product.api_url_pre %}
-```
-
-{% ifversion fpt or ghec %}
-When endpoints include `{enterprise}`, replace `{enterprise}` with the handle for your enterprise account, which is included in the URL for your enterprise settings. For example, if your enterprise account is located at `https://github.com/enterprises/octo-enterprise`, replace `{enterprise}` with `octo-enterprise`.
-{% endif %}
-
-{% ifversion ghes %}
-[Management Console](#management-console) API endpoints are only prefixed with a hostname:
-
-```shell
-http(s)://hostname/
-```
-{% endif %}
-{% ifversion ghae or ghes %}
-### Authentication
-
-Your {% data variables.product.product_name %} installation's API endpoints accept [the same authentication methods](/rest/overview/resources-in-the-rest-api#authentication) as the GitHub.com API. You can authenticate yourself with **[OAuth tokens](/apps/building-integrations/setting-up-and-registering-oauth-apps/)** {% ifversion ghes %}(which can be created using the [Authorizations API](/rest/reference/oauth-authorizations#create-a-new-authorization)) {% endif %}or **[basic authentication](/rest/overview/resources-in-the-rest-api#basic-authentication)**. {% ifversion ghes %}
-OAuth tokens must have the `site_admin` [OAuth scope](/developers/apps/scopes-for-oauth-apps#available-scopes) when used with Enterprise-specific endpoints.{% endif %}
-
-Enterprise administration API endpoints are only accessible to authenticated {% data variables.product.product_name %} site administrators{% ifversion ghes %}, except for the [Management Console](#management-console) API, which requires the [Management Console password](/enterprise/admin/articles/accessing-the-management-console/){% endif %}.
-
-{% endif %}
-
-{% ifversion ghae or ghes %}
-### Version information
-
-The current version of your enterprise is returned in the response header of every API:
-`X-GitHub-Enterprise-Version: {{currentVersion}}.0`
-You can also read the current version by calling the [meta endpoint](/rest/reference/meta/).
-
-{% for operation in currentRestOperations %}
- {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
-{% endfor %}
-
-{% endif %}
-
-{% ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5528 %}
-
-## Audit log
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'audit-log' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% endif %}
-
-{% ifversion fpt or ghec or ghes > 3.3 %}
-## Billing
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'billing' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% endif %}
-
-{% ifversion ghae or ghes %}
-## Admin stats
-
-The Admin Stats API provides a variety of metrics about your installation. *It is only available to [authenticated](/rest/overview/resources-in-the-rest-api#authentication) site administrators.* Normal users will receive a `404` response if they try to access it.
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'admin-stats' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% endif %}
-
-{% ifversion ghae or ghes > 2.22 %}
-
-## Announcements
-
-The Announcements API allows you to manage the global announcement banner in your enterprise. For more information, see "[Customizing user messages for your enterprise](/admin/user-management/customizing-user-messages-for-your-enterprise#creating-a-global-announcement-banner)."
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'announcement' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% endif %}
-
-{% ifversion ghae or ghes %}
-
-## Global webhooks
-
-Global webhooks are installed on your enterprise. You can use global webhooks to automatically monitor, respond to, or enforce rules for users, organizations, teams, and repositories on your enterprise. Global webhooks can subscribe to the [organization](/developers/webhooks-and-events/webhook-events-and-payloads#organization), [user](/developers/webhooks-and-events/webhook-events-and-payloads#user), [repository](/developers/webhooks-and-events/webhook-events-and-payloads#repository), [team](/developers/webhooks-and-events/webhook-events-and-payloads#team), [member](/developers/webhooks-and-events/webhook-events-and-payloads#member), [membership](/developers/webhooks-and-events/webhook-events-and-payloads#membership), [fork](/developers/webhooks-and-events/webhook-events-and-payloads#fork), and [ping](/developers/webhooks-and-events/about-webhooks#ping-event) event types.
-
-*This API is only available to [authenticated](/rest/overview/resources-in-the-rest-api#authentication) site administrators.* Normal users will receive a `404` response if they try to access it. To learn how to configure global webhooks, see [About global webhooks](/enterprise/admin/user-management/about-global-webhooks).
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'global-webhooks' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% endif %}
-
-{% ifversion ghes %}
-
-## LDAP
-
-You can use the LDAP API to update account relationships between a {% data variables.product.product_name %} user or team and its linked LDAP entry or queue a new synchronization.
-
-With the LDAP mapping endpoints, you're able to update the Distinguished Name (DN) that a user or team maps to. Note that the LDAP endpoints are generally only effective if your {% data variables.product.product_name %} appliance has [LDAP Sync enabled](/enterprise/admin/authentication/using-ldap). The [Update LDAP mapping for a user](#update-ldap-mapping-for-a-user) endpoint can be used when LDAP is enabled, even if LDAP Sync is disabled.
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'ldap' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% endif %}
-
-{% ifversion ghae or ghes %}
-## License
-
-The License API provides information on your Enterprise license. *It is only available to [authenticated](/rest/overview/resources-in-the-rest-api#authentication) site administrators.* Normal users will receive a `404` response if they try to access it.
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'license' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% endif %}
-
-{% ifversion ghes %}
-
-## Management console
-
-The Management Console API helps you manage your {% data variables.product.product_name %} installation.
-
-{% tip %}
-
-You must explicitly set the port number when making API calls to the Management Console. If TLS is enabled on your enterprise, the port number is `8443`; otherwise, the port number is `8080`.
-
-If you don't want to provide a port number, you'll need to configure your tool to automatically follow redirects.
-
-You may also need to add the [`-k` flag](http://curl.haxx.se/docs/manpage.html#-k) when using `curl`, since {% data variables.product.product_name %} uses a self-signed certificate before you [add your own TLS certificate](/enterprise/admin/guides/installation/configuring-tls/).
-
-{% endtip %}
-
-### Authentication
-
-You need to pass your [Management Console password](/enterprise/admin/articles/accessing-the-management-console/) as an authentication token to every Management Console API endpoint except [`/setup/api/start`](#create-a-github-enterprise-server-license).
-
-Use the `api_key` parameter to send this token with each request. For example:
-
-```shell
-$ curl -L 'https://hostname:admin_port/setup/api?api_key=your-amazing-password'
-```
-
-You can also use standard HTTP authentication to send this token. For example:
-
-```shell
-$ curl -L -u "api_key:your-amazing-password" 'https://hostname:admin_port/setup/api'
-```
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'management-console' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% endif %}
-
-{% ifversion ghae or ghes %}
-## Organizations
-
-The Organization Administration API allows you to create organizations on your enterprise. *It is only available to [authenticated](/rest/overview/resources-in-the-rest-api#authentication) site administrators.* Normal users will receive a `404` response if they try to access it.
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'orgs' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% endif %}
-
-{% ifversion ghes %}
-## Organization pre-receive hooks
-
-The Organization Pre-receive Hooks API allows you to view and modify
-enforcement of the pre-receive hooks that are available to an organization.
-
-### Object attributes
-
-| Name | Type | Description |
-|----------------------------------|-----------|-----------------------------------------------------------|
-| `name` | `string` | The name of the hook. |
-| `enforcement` | `string` | The state of enforcement for the hook on this repository. |
-| `allow_downstream_configuration` | `boolean` | Whether repositories can override enforcement. |
-| `configuration_url` | `string` | URL for the endpoint where enforcement is set. |
-
-Possible values for *enforcement* are `enabled`, `disabled` and`testing`. `disabled` indicates the pre-receive hook will not run. `enabled` indicates it will run and reject
-any pushes that result in a non-zero status. `testing` means the script will run but will not cause any pushes to be rejected.
-
-`configuration_url` may be a link to this endpoint or this hook's global
-configuration. Only site admins are able to access the global configuration.
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'org-pre-receive-hooks' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% endif %}
-
-{% ifversion ghes %}
-
-## Pre-receive environments
-
-The Pre-receive Environments API allows you to create, list, update and delete environments for pre-receive hooks. *It is only available to [authenticated](/rest/overview/resources-in-the-rest-api#authentication) site administrators.* Normal users will receive a `404` response if they try to access it.
-
-### Object attributes
-
-#### Pre-receive Environment
-
-| Name | Type | Description |
-|-----------------------|-----------|----------------------------------------------------------------------------|
-| `name` | `string` | The name of the environment as displayed in the UI. |
-| `image_url` | `string` | URL to the tarball that will be downloaded and extracted. |
-| `default_environment` | `boolean` | Whether this is the default environment that ships with {% data variables.product.product_name %}. |
-| `download` | `object` | This environment's download status. |
-| `hooks_count` | `integer` | The number of pre-receive hooks that use this environment. |
-
-#### Pre-receive Environment Download
-
-| Name | Type | Description |
-|-----------------|----------|---------------------------------------------------------|
-| `state` | `string` | The state of the most recent download. |
-| `downloaded_at` | `string` | The time when the most recent download started. |
-| `message` | `string` | On failure, this will have any error messages produced. |
-
-Possible values for `state` are `not_started`, `in_progress`, `success`, `failed`.
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'pre-receive-environments' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% endif %}
-
-{% ifversion ghes %}
-## Pre-receive hooks
-
-The Pre-receive Hooks API allows you to create, list, update and delete pre-receive hooks. *It is only available to
-[authenticated](/rest/overview/resources-in-the-rest-api#authentication) site administrators.* Normal users will receive a `404` response if they try to access it.
-
-### Object attributes
-
-#### Pre-receive Hook
-
-| Name | Type | Description |
-|----------------------------------|-----------|-----------------------------------------------------------------|
-| `name` | `string` | The name of the hook. |
-| `script` | `string` | The script that the hook runs. |
-| `script_repository` | `object` | The GitHub repository where the script is kept. |
-| `environment` | `object` | The pre-receive environment where the script is executed. |
-| `enforcement` | `string` | The state of enforcement for this hook. |
-| `allow_downstream_configuration` | `boolean` | Whether enforcement can be overridden at the org or repo level. |
-
-Possible values for *enforcement* are `enabled`, `disabled` and`testing`. `disabled` indicates the pre-receive hook will not run. `enabled` indicates it will run and reject
-any pushes that result in a non-zero status. `testing` means the script will run but will not cause any pushes to be rejected.
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'pre-receive-hooks' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% endif %}
-
-{% ifversion ghes %}
-
-## Repository pre-receive hooks
-
-The Repository Pre-receive Hooks API allows you to view and modify
-enforcement of the pre-receive hooks that are available to a repository.
-
-### Object attributes
-
-| Name | Type | Description |
-|---------------------|----------|-----------------------------------------------------------|
-| `name` | `string` | The name of the hook. |
-| `enforcement` | `string` | The state of enforcement for the hook on this repository. |
-| `configuration_url` | `string` | URL for the endpoint where enforcement is set. |
-
-Possible values for *enforcement* are `enabled`, `disabled` and`testing`. `disabled` indicates the pre-receive hook will not run. `enabled` indicates it will run and reject any pushes that result in a non-zero status. `testing` means the script will run but will not cause any pushes to be rejected.
-
-`configuration_url` may be a link to this repository, it's organization owner or global configuration. Authorization to access the endpoint at `configuration_url` is determined at the owner or site admin level.
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'repo-pre-receive-hooks' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% endif %}
-
-{% ifversion ghae or ghes %}
-## Users
-
-The User Administration API allows you to suspend{% ifversion ghes %}, unsuspend, promote, and demote{% endif %}{% ifversion ghae %} and unsuspend{% endif %} users on your enterprise. *It is only available to [authenticated](/rest/overview/resources-in-the-rest-api#authentication) site administrators.* Normal users will receive a `403` response if they try to access it.
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'users' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% endif %}
+
\ No newline at end of file
diff --git a/translations/es-ES/content/rest/reference/gists.md b/translations/es-ES/content/rest/reference/gists.md
index 7bf20b9c56ad..46aad2876d98 100644
--- a/translations/es-ES/content/rest/reference/gists.md
+++ b/translations/es-ES/content/rest/reference/gists.md
@@ -13,44 +13,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-### Autenticación
-
-Puedes leer gists públicos {% ifversion ghae or ghes %}y crearlos para usuarios anónimos sin un token{% else %} de forma anónima, pero debes haber iniciado sesión en GitHub para crear gists.{% endif %} Para leer o escribir gists en nombre de un usuario, necesitas el alcance de OAuth para gists y un token. Par aobtener más información, consulta la sección "[Alcances para las Apps de OAuth](/developers/apps/scopes-for-oauth-apps)".
-
-
-
-### Truncamiento
-
-La API de Gist proporciona hasta un megabyte de contenido para cada archivo en el gist. Cada archivo que se devuelve para un gist a través de la API tiene una clave que se llama `truncated`. Si `truncated` aparece como `true`, significa que el archivo es demasiado grande y solo se devolvió una parte de su contenido en `content`.
-
-Si necesitas el contenido completo del archivo, puedes hacer una solicitud de tipo `GET` a la URL que se especifica en `raw_url`. Ten en cuent que, para los archivos mayores a diez megabytes, necesitarás clonar el gist a través de la URL que proprocionó `git_pull_url`.
-
-Adicionalmente a el truncamiento del contenido específico del archivo, la lista de archivos completa podría truncarse si la cantidad total excede los 300 archivos. Si la clave `truncated` de nivel superior aparece como `true`, únicamente se han devuelto los primeros 300 archivos en la lista. Si necesitas recuperar todos los archivos del gist, necesitarás clonarlo a través de la URL que te proporcionó `git_pull_url`.
-
-### Tipos de medios personalizados para los gists
-
-Estos son los tipos de medios compatibles para recuperar el contenido de los gists.
-
- application/vnd.github.VERSION.raw
- application/vnd.github.VERSION.base64
-
-Para obtener más información, consulta la sección "[Tipos de medios](/rest/overview/media-types)".
-
-{% for operation in currentRestOperations %}
- {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
-{% endfor %}
-
-## Comentarios
-
-### Tipos de medios personalizados para los comentarios de los Gists
-
-Estos son los tipos de medios compatibles para los comentarios de los gists.
-
- application/vnd.github.VERSION.raw
- application/vnd.github.VERSION.base64
-
-Para obtener más información acerca de los tipos de medios, consulta la sección "[Tipos de medios personalizados](/rest/overview/media-types)".
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'comments' %}{% include rest_operation %}{% endif %}
-{% endfor %}
+
diff --git a/translations/es-ES/content/rest/reference/git.md b/translations/es-ES/content/rest/reference/git.md
index 68b41f39e36e..1504ac51e67e 100644
--- a/translations/es-ES/content/rest/reference/git.md
+++ b/translations/es-ES/content/rest/reference/git.md
@@ -14,57 +14,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-La API de la Base de datos de Git te da acceso de escritura y lectora para los objetos sin procesar de Git que se encuentran en tu base de datos de Git en {% data variables.product.product_name %} y para listar y actualizar tus referencias (cabezas de rama y etiquetas). Para obtener más información acerca de utilizar la API de la Base de Datos de Git, consulta la secicón "[Empezar con la API de datos de Git](/rest/guides/getting-started-with-the-git-database-api)".
-
-{% for operation in currentRestOperations %}
- {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
-{% endfor %}
-
-## Blobs
-
-Un blob (objeto binario grande, por sus siglas en inglés) de Git es el tipo de objeto que se utiliza para almacenar el contenido de cada archivo en un repositorio. El hash SHA-1 del archivo se calcula y almacena en el objeto del blob. Estas terminales te permiten leer y escribir [objetos de blob](https://git-scm.com/book/en/v1/Git-Internals-Git-Objects) en tu base de datos de Git en {% data variables.product.product_name %}. Los blobs aprovechan [estos tipos de medios personalizados](#custom-media-types-for-blobs). Puedes leer más acerca del uso de tipos de medios en la API [aquí](/rest/overview/media-types).
-
-### Tipos de medios personalizados para los blobs
-
-Estos son los tipos de medios compatibles para los blobs.
-
- application/json
- application/vnd.github.VERSION.raw
-
-Para obtener más información, consulta la sección "[Tipos de medios](/rest/overview/media-types)".
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'blobs' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## Confirmaciones
-
-Una confirmación de Git es una impresión de pantalla de la jerarquía ([árbol de Git](/rest/reference/git#trees)) y del contenido de los archivos ([blob de Git](/rest/reference/git#blobs)) en un reposiotorio de Git. Estas terminales te permiten leer y escribir [objetos de confirmación](https://git-scm.com/book/en/v1/Git-Internals-Git-Objects#Commit-Objects) en tu base de datos en {% data variables.product.product_name %}.
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'commits' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## Referencias
-
-Una referencia (`git ref`) es simplemente un archivo que contiene un hash SHA-1 de una confirmación de Git. Cuando te refieres a una confirmación de Git, puedes utilizar la referencia de Git, la cual es un nombre fácil de recordar, en vez de utilizar el hash. La referencia de Git puede reescribirse para apuntar a una confirmación nueva. Una rama es solo una referencia de Git que almacena el hash de la confirmación de Git nueva. Estas terminales te permiten leer y escribir [referencias](https://git-scm.com/book/en/v1/Git-Internals-Git-References) en tu base de datos de Git en {% data variables.product.product_name %}.
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'refs' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## Etiquetas
-
-Una etiqueta de git es similar a una [referencia de Git](/rest/reference/git#refs), pero la confirmación de Git a la que apunta jamás cambia. Las etiquetas de git son útiles cuando quieres apuntar a algún lanzamiento específico. Estas terminales te permiten leer y escribir [objetos de etiquetas](https://git-scm.com/book/en/v1/Git-Internals-Git-References#Tags)en tu base de datos de Git en {% data variables.product.product_name %}. La API de etiquetas de Git son compatibles únicamente con los [objetos de etiqueta anotados](https://git-scm.com/book/en/v1/Git-Internals-Git-References#Tags), no con etiquetas ligeras.
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'tags' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## Árboles
-
-Un objeto de árbol de Git crea la jerarquía entre archivos para un repositorio de Git. Puedes utilizar el objeto de árbol de Git para crear una relación entre directorios y entre los archivos que contienen. Estas terminales te permiten leer y escribir [objetos de árbol](https://git-scm.com/book/en/v1/Git-Internals-Git-Objects#Tree-Objects)en tu base de datos de Git en {% data variables.product.product_name %}.
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'trees' %}{% include rest_operation %}{% endif %}
-{% endfor %}
+
diff --git a/translations/es-ES/content/rest/reference/gitignore.md b/translations/es-ES/content/rest/reference/gitignore.md
index 3736e6f6b7d1..a651874adb01 100644
--- a/translations/es-ES/content/rest/reference/gitignore.md
+++ b/translations/es-ES/content/rest/reference/gitignore.md
@@ -13,14 +13,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-Cuando creas un repositorio nuevo en {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} a través de la API, puedes especificar una [plantilla de.gitignore](/github/getting-started-with-github/ignoring-files) para aplicarla al repositorio cuando lo crees. La API de plantillas de .gitignore lista y recupera plantillas del [repositorio de .gitignore](https://github.com/github/gitignore) de {% data variables.product.product_name %}.
-
-### Tipos de medios personalizados para gitignore
-
-Puedes utilizar este tipo de medios personalizado cuando obtengas una plantilla de gitignore.
-
- application/vnd.github.VERSION.raw
-
-Para obtener más información, consulta la sección "[Tipos de medios](/rest/overview/media-types)".
-
-{% include rest_operations_at_current_path %}
+
diff --git a/translations/es-ES/content/rest/reference/index.md b/translations/es-ES/content/rest/reference/index.md
index ee65e3acba75..a61999b33984 100644
--- a/translations/es-ES/content/rest/reference/index.md
+++ b/translations/es-ES/content/rest/reference/index.md
@@ -51,6 +51,5 @@ children:
- /teams
- /users
- /webhooks
- - /permissions-required-for-github-apps
---
diff --git a/translations/es-ES/content/rest/reference/interactions.md b/translations/es-ES/content/rest/reference/interactions.md
index 09300130804b..b839ad92a72b 100644
--- a/translations/es-ES/content/rest/reference/interactions.md
+++ b/translations/es-ES/content/rest/reference/interactions.md
@@ -11,50 +11,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-Los usuarios interactuan con los repositorios al comentar, abrir informes de problemas y crear solicitudes de extracción. La API de interacciones permite a las personas con acceso de propietario o de administrador restringir la interacción con los repositorios públicos temporalmente a un tipo específico de usuario.
-
-{% for operation in currentRestOperations %}
- {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
-{% endfor %}
-
-## Organización
-
-La API de Interacciones Organizacionales permite a los propietarios el restringir temporalmente qué tipo de usuariopuede comentar, abrir propuestas, o crear solicitudes de cambios en los repositorios públicos de la organización. {% data reusables.interactions.interactions-detail %} Aquí puedes aprender más sobre los tipos de usuario de {% data variables.product.product_name %}:
-
-* {% data reusables.interactions.existing-user-limit-definition %} en la organización.
-* {% data reusables.interactions.contributor-user-limit-definition %} en la organización.
-* {% data reusables.interactions.collaborator-user-limit-definition %} en la organización.
-
-Configurar el límite de interacciones a nivel organizacional sobreescribirá cualquier límite de interacción que se haya configurado para los repositorios individuales que pertenezcan a la organización. Para configurar los límites de interacción para los repositorios individuales que pertenezcan a la organización, mejor utiliza la terminal de interaciones del [Repositorio](#repository).
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'orgs' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## Repositorio
-
-La API de interacciones de repositorio permite a las personas con acceso administrativo o de propietario restringir temporalmente qué tipo de usuario puede comentar, abrir propuestas, o crear solicitudes de cambios en un repositorio privado. {% data reusables.interactions.interactions-detail %} Aquí puedes aprender más sobre los tipos de usuario de {% data variables.product.product_name %}:
-
-* {% data reusables.interactions.existing-user-limit-definition %} en el repositorio.
-* {% data reusables.interactions.contributor-user-limit-definition %} en el repositorio.
-* {% data reusables.interactions.collaborator-user-limit-definition %} en el repositorio.
-
-Si se habilita un límite de interacción para el usuario u organización a la que pertenece el repositorio, éste no podrá cambiarse para el repositorio individual. En su lugar, utiliza las terminales de interacciones de [Usuario](#user) o de [Organización](#organization) para cambiar el límite de interacción.
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'repos' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## Usuario
-
-La API de interacciones de usuario te permite restringir temporalmente qué tipo de usuario puede comentar, abrir propuestas, o crear solicitudes de cambio en tus repositorios públicos. {% data reusables.interactions.interactions-detail %} Aquí puedes aprender más sobre los tipos de usuario de {% data variables.product.product_name %}:
-
-* {% data reusables.interactions.existing-user-limit-definition %} de interactuar con tus repositorios.
-* {% data reusables.interactions.contributor-user-limit-definition %} de interactuar con tus repositorios.
-* {% data reusables.interactions.collaborator-user-limit-definition %} de interactuar con tus repositorios.
-
-El configurar el límite de interacción a nivel de usuario sobreescribirá cualquier límite de interacción que se configure para los repositorios individuales que le pertenezcan a éste. Para configurar límites de interacción diferentes para los repositorios individuales que pertenezcan al usuario, utiliza la terminal de interacciones de [Repositorio](#repository) en su lugar.
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'user' %}{% include rest_operation %}{% endif %}
-{% endfor %}
+
diff --git a/translations/es-ES/content/rest/reference/issues.md b/translations/es-ES/content/rest/reference/issues.md
index 090fb3feaa83..0381301db99f 100644
--- a/translations/es-ES/content/rest/reference/issues.md
+++ b/translations/es-ES/content/rest/reference/issues.md
@@ -13,63 +13,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-### Tipos de mendios personalizados para los informes de problemas
-
-Estos son los tipos de medios compatibles para los informes de problemas.
-
- application/vnd.github.VERSION.raw+json
- application/vnd.github.VERSION.text+json
- application/vnd.github.VERSION.html+json
- application/vnd.github.VERSION.full+json
-
-Para obtener más información acerca de los tipos de medios, consulta la sección "[Tipos de medios personalizados](/rest/overview/media-types)".
-
-{% for operation in currentRestOperations %}
- {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
-{% endfor %}
-
-## Asignatarios
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'assignees' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## Comentarios
-
-La API de Comentarios par los Informes de Problemas es compatible con listar, ver, editar y crear comentarios en informes de problemas y solicitudes de extracción.
-
-Los comentarios de los informes de problemas utilizan [estos tipos de medios personalizados](#custom-media-types). Puedes leer más acerca del uso de tipos de medios en la API [aquí](/rest/overview/media-types).
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'comments' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## Eventos
-
-La API de eventos para Informes de problemas puede devolver diferentes tipos de eventos que se activan de acuerdo a la actividad en los informes de problemas y solicitudes de extracción. La API de eventos para Informes de problemas puede devolver diferentes tipos de eventos que se activan de acuerdo a la actividad en los informes de problemas y solicitudes de extracción. Para obtener más información acerca de los eventos específicos que puedes recibir de la API de Eventos para Solicitudes de Extracción, consulta la sección "[Tipos de evento de las Solicitudes de Extracción](/developers/webhooks-and-events/issue-event-types)". Para obtener más información, consulta la "[API de Eventos](/developers/webhooks-and-events/github-event-types)".
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'events' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## Etiquetas
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'labels' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## Hitos
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'milestones' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## Línea de tiempo
-
-La API de eventos para la línea de tiempo puede devolver diferentes tipos de eventos que se activan de acuerdo a la actividad de la línea de tiempo en los informes de problemas y solicitudes de extracción. La API de eventos para Informes de problemas puede devolver diferentes tipos de eventos que se activan de acuerdo a la actividad en los informes de problemas y solicitudes de extracción. Para obtener más información acerca de los eventos específicos que puedes recibir de la API de Eventos para Solicitudes de Extracción, consulta la sección "[Tipos de evento de las Solicitudes de Extracción](/developers/webhooks-and-events/issue-event-types)". Para obtener más información, consulta la "[API de Eventos de GitHub](/developers/webhooks-and-events/github-event-types)".
-
-Puedes utilizar esta API para mostrar información sobre los informes de problemas y solicitudes de extracción o para determinar a quién debería notificársele sobre los comentarios en los informes de problemas.
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'timeline' %}{% include rest_operation %}{% endif %}
-{% endfor %}
+
diff --git a/translations/es-ES/content/rest/reference/licenses.md b/translations/es-ES/content/rest/reference/licenses.md
index d41e203c4c41..e7fbd1e995da 100644
--- a/translations/es-ES/content/rest/reference/licenses.md
+++ b/translations/es-ES/content/rest/reference/licenses.md
@@ -13,27 +13,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-La API de licencias devuelve metadatos acerca de las liciencias de código abierto populares y acerca de la información sobre un archivo de licencia específico de un proyecto.
-
-La API de licencias utiliza [el Licenciatario de código abierto de la Gema de Ruby ](https://github.com/benbalter/licensee) para intentar identificar la licencia del proyecto. Este licenciatario empata el contenido del archivo de `LICENSE` de un proyecto (si es que existe) contra una lista corta de licencias conocidas. Como resultado, la API no toma en cuenta las licencias de las dependencias del proyecto u otros medios de documentar la licencia de un proyecto tales como las referencias al nombre de la licencia en la documentación.
-
-Si una licencia empata, la llave de licencia y el nombre devuelto se apegan a la [especificación SPDX](https://spdx.org/).
-
-**Nota:** Estas terminales también devolverán la información de licencia de un repositorio:
-
-- [Obtener un repositorio](/rest/reference/repos#get-a-repository)
-- [Listar los repositorios para un usuario](/rest/reference/repos#list-repositories-for-a-user)
-- [Listar los repositorios de una organización](/rest/reference/repos#list-organization-repositories)
-- [Listar las bifurcaciones](/rest/reference/repos#list-forks)
-- [Listar los repositorios que el usuario está observando](/rest/reference/activity#list-repositories-watched-by-a-user)
-- [Listar los repositorios de equipo](/rest/reference/teams#list-team-repositories)
-
-{% warning %}
-
-GitHub puede ser muchas cosas, pero no es un buró legal. Como tal, GitHub no proporcional consejo legal. Al utilizar la API de licencias o al enviarnos un mensaje de correo electrónico acerca de ellas no estás incurriendo en ningún consejo legal ni creando una relación abogado-cliente. Si tienes cualquier pregunta acerca de lo que puedes o no hacer con una licencia específica, debes acudir a tu propio consejero legal antes de continuar. De hecho, siempre debes consultar con tu propio abogado antes de que decidas tomar cualquier decisión que pudiera tener implicaciones legales o que pudiera impactar tus derechos.
-
-GitHub creó la API de Licencias para ayudar a los usuarios a obtener información acerca de las licencias de código abierto y de los proyectos que las utilizan. Esperamos que te sea útil, pero ten presente que no somos abogados (por lo menos, la mayoría de nosotros no lo somos) y que cometemos errores como todo el mundo. Es por esto que GitHub proporciona la API "tal como está" y no da ninguna garantía de cualquier tipo de información o licencias que se proporcionen en o a través de ella y se deslinda de cualquier responsabilidad derivada de los daños que pudiesen resultar de su uso.
-
-{% endwarning %}
-
-{% include rest_operations_at_current_path %}
+
diff --git a/translations/es-ES/content/rest/reference/markdown.md b/translations/es-ES/content/rest/reference/markdown.md
index 2525c83d9570..43aba496570f 100644
--- a/translations/es-ES/content/rest/reference/markdown.md
+++ b/translations/es-ES/content/rest/reference/markdown.md
@@ -13,4 +13,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-{% include rest_operations_at_current_path %}
+
diff --git a/translations/es-ES/content/rest/reference/meta.md b/translations/es-ES/content/rest/reference/meta.md
index 7abbe08df24f..aa2eea144872 100644
--- a/translations/es-ES/content/rest/reference/meta.md
+++ b/translations/es-ES/content/rest/reference/meta.md
@@ -13,4 +13,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-{% include rest_operations_at_current_path %}
+
diff --git a/translations/es-ES/content/rest/reference/metrics.md b/translations/es-ES/content/rest/reference/metrics.md
index 28fe52ad9ee8..1f00b23b6067 100644
--- a/translations/es-ES/content/rest/reference/metrics.md
+++ b/translations/es-ES/content/rest/reference/metrics.md
@@ -14,47 +14,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-{% for operation in currentRestOperations %}
- {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
-{% endfor %}
-
-{% ifversion fpt or ghec %}
-## Comunidad
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'community' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% endif %}
-
-## Estadísticas
-
-La API de Estadísticas del Repositorio te permite recuperar los datos que {% data variables.product.product_name %} utiliza para visualizar los diferentes tipos de actividad del repositorio.
-
-### Unas palabras sobre el almacenamiento en caché
-
-El calcular las estadísitcas del repositorio es una operación costosa, así que intentamos devolver los datos almacenados en caché cuando nos es posible. Si los datos no se han almacenado en caché cuando consultas la estadística de un repositorio, recibirás una respuesta `202`; también se dispara un job en segundo plano para comenzar a compilar estas estadísticas. Permite que el job se complete, y luego emite la solicitud nuevamente. Si el job ya terminó, esa solicitud recibirá una respuesta `200` con la estadística en el cuerpo de la respuesta.
-
-El SHA de la rama predeterminada del repositorio guarda en caché las estadísticas del repositorio; el subir información a la rama predeterminada restablece el caché de de las estadísticas.
-
-### Las estadísticas excluyen algunos tipos de confirmaciones
-
-Las estadísticas que expone la API empatan con aquellas que muestran [diversas gráficas del repositorio](/github/visualizing-repository-data-with-graphs/about-repository-graphs).
-
-Para resumir:
-- Todas las estadísticas excluyen las confirmaciones de fusión.
-- Las estadísticas del colaborador también excluyen a las confirmaciones vacías.
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'statistics' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% ifversion fpt or ghec %}
-## Tráfico
-
-Para los repositorios en los que tienes acceso de carga, la API de tráfico proporciona acceso a la información proporcionada en tu gráfica de repositorio. Para obtener más información, consulta la sección "Ver el tráfico hacia un repositorio".
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'traffic' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-{% endif %}
+
diff --git a/translations/es-ES/content/rest/reference/migrations.md b/translations/es-ES/content/rest/reference/migrations.md
index 7b5ee4190502..a49666dce78b 100644
--- a/translations/es-ES/content/rest/reference/migrations.md
+++ b/translations/es-ES/content/rest/reference/migrations.md
@@ -15,116 +15,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-{% for operation in currentRestOperations %}
- {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
-{% endfor %}
-
-## Organización
-
-La API de Migraciones solo está disponible para los propietarios autenticados de la organización. Para obtener más información, consulta las secciones "[Roles en una organización](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#permission-levels-for-an-organization)" y "[Otros métodos de autenticación](/rest/overview/other-authentication-methods)".
-
-{% data variables.migrations.organization_migrations_intro %}
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'orgs' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% ifversion fpt or ghec %}
-## Importaciones de Código Fuente
-
-{% data variables.migrations.source_imports_intro %}
-
-Una importación de código fuente habitual inicia la importación y luego actualiza (opcionalmente) a los autores y/o actualiza las preferencias para utilizar el LFS de Ggit si existen archivos grandes en la importación. También puedes crear un webhook que escuche al [`RepositoryImportEvent`](/developers/webhooks-and-events/webhook-events-and-payloads#repository_import) para encontrar el estado de la importación.
-
-Se puede ver un ejemplo más detallado en este diagrama:
-
-```
-+---------+ +--------+ +---------------------+
-| Tooling | | GitHub | | Original Repository |
-+---------+ +--------+ +---------------------+
- | | |
- | Start import | |
- |----------------------------->| |
- | | |
- | | Download source data |
- | |--------------------------------------------->|
- | | Begin streaming data |
- | |<---------------------------------------------|
- | | |
- | Get import progress | |
- |----------------------------->| |
- | "status": "importing" | |
- |<-----------------------------| |
- | | |
- | Get commit authors | |
- |----------------------------->| |
- | | |
- | Map a commit author | |
- |----------------------------->| |
- | | |
- | | |
- | | Finish streaming data |
- | |<---------------------------------------------|
- | | |
- | | Rewrite commits with mapped authors |
- | |------+ |
- | | | |
- | |<-----+ |
- | | |
- | | Update repository on GitHub |
- | |------+ |
- | | | |
- | |<-----+ |
- | | |
- | Map a commit author | |
- |----------------------------->| |
- | | Rewrite commits with mapped authors |
- | |------+ |
- | | | |
- | |<-----+ |
- | | |
- | | Update repository on GitHub |
- | |------+ |
- | | | |
- | |<-----+ |
- | | |
- | Get large files | |
- |----------------------------->| |
- | | |
- | opt_in to Git LFS | |
- |----------------------------->| |
- | | Rewrite commits for large files |
- | |------+ |
- | | | |
- | |<-----+ |
- | | |
- | | Update repository on GitHub |
- | |------+ |
- | | | |
- | |<-----+ |
- | | |
- | Get import progress | |
- |----------------------------->| |
- | "status": "complete" | |
- |<-----------------------------| |
- | | |
- | | |
-```
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'source-imports' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-{% endif %}
-## Usuario
-
-La API de migraciones de usuario solo está disponible para los propietarios de cuentas autenticadas. Para obtener más información, consulta la sección "[Otros métodos de autenticación](/rest/overview/other-authentication-methods)".
-
-{% data variables.migrations.user_migrations_intro %} Para encontrar una lista descargable de datos de migración, consulta "[Descarga un archivo de migración de usuario](#download-a-user-migration-archive)".
-
-Antes de descargar un archivo deberás iniciar la migración del usuario. Una vez que el estado de la migración sea `exported`, podrás descargarla.
-
-Ya que hayas creado el archivo de migración, este estará disponible para su descarga por siete días. Pero puedes borrar el archivo de migración del usuario antes si lo prefieres. Puedes desbloquear tu repositorio cuando la migración aparezca como `exported` para comenzar a utilizar tu repositorio nuevamente o borrarlo si ya no necesitas los datos del código fuente.
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'users' %}{% include rest_operation %}{% endif %}
-{% endfor %}
+
diff --git a/translations/es-ES/content/rest/reference/oauth-authorizations.md b/translations/es-ES/content/rest/reference/oauth-authorizations.md
index 10785b61ecce..dc3e120e989e 100644
--- a/translations/es-ES/content/rest/reference/oauth-authorizations.md
+++ b/translations/es-ES/content/rest/reference/oauth-authorizations.md
@@ -8,8 +8,6 @@ versions:
miniTocMaxHeadingLevel: 3
---
-Puedes utilizar esta API para administrar el acceso que las aplicaciones de OAuth tienen en tu cuenta. Solo puedes acceder a esta API a través de la [Autenticación Básica](/rest/overview/other-authentication-methods#basic-authentication) utilizando tu nombre de usuario y contraseña, y no los tokens.
-
-Si tú o tus usuarios habilitaron la autenticación de dos factores, asegúrate de que entiendes cómo [trabajar con la autenticación de dos factores](/rest/overview/other-authentication-methods#working-with-two-factor-authentication).
-
-{% include rest_operations_at_current_path %}
+
diff --git a/translations/es-ES/content/rest/reference/orgs.md b/translations/es-ES/content/rest/reference/orgs.md
index 3e8f530df849..63baa20df7b4 100644
--- a/translations/es-ES/content/rest/reference/orgs.md
+++ b/translations/es-ES/content/rest/reference/orgs.md
@@ -14,66 +14,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-{% for operation in currentRestOperations %}
- {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
-{% endfor %}
-
-{% ifversion fpt or ghec %}
-## Bloquear usuarios
-
-El token que se utiliza para autenticar la llamada debe tener el alcance de `admin:org` para poder hacer cualquier llamada de bloqueo para una organización. De lo contrario, la respuesta devolverá un `HTTP 404`.
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'blocking' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% endif %}
-
-## Miembros
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'members' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## Colaboradores externos
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'outside-collaborators' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% ifversion fpt or ghes > 3.4 %}
-## Roles de repositorio personalizados
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'custom_roles' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-{% endif %}
-
-## Webhooks
-
-Los webhooks de las organizaciones te permiten recibir cargas útiles de `POST` por HTTP cuando ciertos eventos suceden en una organización. {% data reusables.webhooks.webhooks-rest-api-links %}
-
-Para obtener más información sobre las acciones a las cuales te puedes suscribir, consulta los "[tipos de eventos de {% data variables.product.prodname_dotcom %}](/developers/webhooks-and-events/github-event-types)".
-
-### Alcances & Restricciones
-
-Todas las acciones en contra de los webhooks de una organización requieren que el usuario autenticado sea un administrador de la organización que se está administrando. Adicionalmente, los tokens de OAuth requieren el alcance `admin:org_hook`. Par aobtener más información, consulta la sección "[Alcances para las Apps de OAuth](/developers/apps/scopes-for-oauth-apps)".
-
-Para porteger los datos sensibles que pueden encontrarse en las configuraciones de los webhooks, también imponemos las siguientes reglas de control de accesos:
-
-- Las aplicaciones de OAuth no pueden listar, ver o editar los webhooks que no crearon ellas mismas.
-- Los usuarios no pueden listar, ver o editar los webhooks que crearon las aplicaciones de OAuth.
-
-### Recibir Webhooks
-
-Para que {% data variables.product.product_name %} envíe cargas útiles de webhooks, se necesita que se pueda acceder a tu servidor desde la internet. También sugerimos ampliamente utilizar SSL para que podamos enviar cargas útiles cifradas a través de HTTPS.
-
-Para encontrar más de las mejores prácticas, [consulta nuestra guía](/guides/best-practices-for-integrators/).
-
-#### Encabezados de Webhook
-
-{% data variables.product.product_name %} enviará varios encabezados de HTTP para diferenciar los tipos de eventos y los identificadores de las cargas útiles. Consulta la sección de [encabezados de webhook](/webhooks/event-payloads/#delivery-headers) para encontrar más detalles.
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'webhooks' %}{% include rest_operation %}{% endif %}
-{% endfor %}
+
diff --git a/translations/es-ES/content/rest/reference/packages.md b/translations/es-ES/content/rest/reference/packages.md
index 62f0256da3e6..65ebafa63172 100644
--- a/translations/es-ES/content/rest/reference/packages.md
+++ b/translations/es-ES/content/rest/reference/packages.md
@@ -10,17 +10,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-La API de {% data variables.product.prodname_registry %} te permite administrar paquetes utilizando la API de REST. Para aprender más sobre cómo restablecer o borrar paquetes, consulta la sección "[Restablecer y borrar paquetes](/packages/learn-github-packages/deleting-and-restoring-a-package)".
-
-Para utilizar esta API, primero tienes que autenticarte utilizando un token de acceso personal.
- - Para acceder a los metadatos del paquete, tu token debe incluir el alcance `read:packages`.
- - Para borrar los paquetes y las versiones de paquetes, tu token debe incluir los alcances `read:packages` y `delete:packages`.
- - Para restablecer los paquetes y sus versiones, tu token debe incluir los alcances de `read:packages` y `write:packages`.
-
-Si tu `package_type` es `npm`, `maven`, `rubygems`, o `nuget`, entonces tu token también debe incluir el alcance `repo`, ya que este hereda los permisos de un repositorio de {% data variables.product.prodname_dotcom %}. Si tu paquete está en el {% data variables.product.prodname_container_registry %}, entonces tu `package_type` es `container` y tu token no necesita el alcance de `repo` para acceder o administrar este `package_type`. Los paquetes de `container` ofrecen permisos granulares separados de un repositorio. Para obtener más información, consulta la sección "[Acerca de los permisos para el {% data variables.product.prodname_registry %}](/packages/learn-github-packages/about-permissions-for-github-packages#about-scopes-and-permissions-for-package-registries)".
-
-Si quieres utilizar la API del {% data variables.product.prodname_registry %} para acceder a los recursos de una organización con el SSO habilitado, entonces debes habilitar el SSO para tu token de acceso personal. Para obtener más información, consulta la sección "[Autorizar un token de acceso personal para utilizarse con el inicio de sesión único de SAML](/github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on){% ifversion fpt %}" en la documentación de {% data variables.product.prodname_ghe_cloud %}.{% else %}".{% endif %}
-
-{% for operation in currentRestOperations %}
- {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
-{% endfor %}
+
diff --git a/translations/es-ES/content/rest/reference/pages.md b/translations/es-ES/content/rest/reference/pages.md
index 96b0e7999aee..5b2d3e536ee5 100644
--- a/translations/es-ES/content/rest/reference/pages.md
+++ b/translations/es-ES/content/rest/reference/pages.md
@@ -12,22 +12,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-La API de {% data variables.product.prodname_pages %} recupera información sobre tu configuración de {% data variables.product.prodname_pages %} y sobre los estados de tus compilaciones. Solo los propietarios autenticados pueden acceder a la información sobre el sitio y sobre las compilaciones{% ifversion not ghae %}, incluso si los sitios web son públicos{% endif %}. Para obtener más información, consulta la sección "[Acerca de {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages)".
-
-En las terminales de la API de {% data variables.product.prodname_pages %} que llevan una clave de `status` en su respuesta, el valor puede ser uno de entre los siguientes:
-* `null`: El sitio aún tiene que crearse.
-* `queued`: Se solicitó la compilación, pero no ha iniciado.
-* `building`: La compilación está en curso.
-* `built`: Se creó el sitio.
-* `errored`: Indica que ocurrió un error durante la compilación.
-
-En las terminales de la API de {% data variables.product.prodname_pages %} que devulenven información del sitio de GitHub Pages, las respuestas de JSON incluyen estos campos:
-* `html_url`: La URL absoluta (incluyendo el modelo) del sitio de Páginas que se interpretó. Por ejemplo, `https://username.github.io`.
-* `source`: Un objeto que contiene la rama origen y el directorio del sitio de Páginas que se interpretó. Esto incluye:
- - `branch`: La rama del repositorio que se utilizó para publicar los [archivos de código fuente de tu sitio](/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site). Por ejemplo, _main_ o _gh-pages_.
- - `path`: El directorio del repositorio desde el cual publica el sitio. Podría ser `/` o `/docs`.
-
-{% comment %}An extra blank line is needed here to make sure the operations below don't continue the list above.{% endcomment %}
-{% for operation in currentRestOperations %}
- {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
-{% endfor %}
+
diff --git a/translations/es-ES/content/rest/reference/projects.md b/translations/es-ES/content/rest/reference/projects.md
index 135631b1d652..7190b6ce7bfc 100644
--- a/translations/es-ES/content/rest/reference/projects.md
+++ b/translations/es-ES/content/rest/reference/projects.md
@@ -13,26 +13,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-{% for operation in currentRestOperations %}
- {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
-{% endfor %}
-
-## Tarjetas
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'cards' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## Colaboradores
-
-Esta API te permite interactuar con los proyectos de una organización.
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'collaborators' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## Columnas
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'columns' %}{% include rest_operation %}{% endif %}
-{% endfor %}
+
diff --git a/translations/es-ES/content/rest/reference/pulls.md b/translations/es-ES/content/rest/reference/pulls.md
index 12331460691f..36e1e2019761 100644
--- a/translations/es-ES/content/rest/reference/pulls.md
+++ b/translations/es-ES/content/rest/reference/pulls.md
@@ -13,76 +13,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-The Pull Request API allows you to list, view, edit, create, and even merge pull requests. Comments on pull requests can be managed via the [Issue Comments API](/rest/reference/issues#comments).
-
-Every pull request is an issue, but not every issue is a pull request. For this reason, "shared" actions for both features, like manipulating assignees, labels and milestones, are provided within [the Issues API](/rest/reference/issues).
-
-### Custom media types for pull requests
-
-These are the supported media types for pull requests.
-
- application/vnd.github.VERSION.raw+json
- application/vnd.github.VERSION.text+json
- application/vnd.github.VERSION.html+json
- application/vnd.github.VERSION.full+json
- application/vnd.github.VERSION.diff
- application/vnd.github.VERSION.patch
-
-For more information, see "[Custom media types](/rest/overview/media-types)."
-
-If a diff is corrupt, contact {% data variables.contact.contact_support %}. Include the repository name and pull request ID in your message.
-
-### Link Relations
-
-Pull Requests have these possible link relations:
-
-Name | Description
------|-----------|
-`self`| The API location of this Pull Request.
-`html`| The HTML location of this Pull Request.
-`issue`| The API location of this Pull Request's [Issue](/rest/reference/issues).
-`comments`| The API location of this Pull Request's [Issue comments](/rest/reference/issues#comments).
-`review_comments`| The API location of this Pull Request's [Review comments](/rest/reference/pulls#comments).
-`review_comment`| The [URL template](/rest#hypermedia) to construct the API location for a [Review comment](/rest/reference/pulls#comments) in this Pull Request's repository.
-`commits`|The API location of this Pull Request's [commits](#list-commits-on-a-pull-request).
-`statuses`| The API location of this Pull Request's [commit statuses](/rest/reference/commits#commit-statuses), which are the statuses of its `head` branch.
-
-{% for operation in currentRestOperations %}
- {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
-{% endfor %}
-
-## Reviews
-
-Pull Request Reviews are groups of Pull Request Review Comments on the Pull
-Request, grouped together with a state and optional body comment.
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'reviews' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## Review comments
-
-Pull request review comments are comments on a portion of the unified diff made during a pull request review. Commit comments and issue comments are different from pull request review comments. You apply commit comments directly to a commit and you apply issue comments without referencing a portion of the unified diff. For more information, see "[Create a commit comment](/rest/reference/commits#create-a-commit-comment)" and "[Create an issue comment](/rest/reference/issues#create-an-issue-comment)."
-
-### Custom media types for pull request review comments
-
-These are the supported media types for pull request review comments.
-
- application/vnd.github.VERSION.raw+json
- application/vnd.github.VERSION.text+json
- application/vnd.github.VERSION.html+json
- application/vnd.github.VERSION.full+json
-
-For more information, see "[Custom media types](/rest/overview/media-types)."
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'comments' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## Review requests
-
-Pull request authors and repository owners and collaborators can request a pull request review from anyone with write access to the repository. Each requested reviewer will receive a notification asking them to review the pull request.
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'review-requests' %}{% include rest_operation %}{% endif %}
-{% endfor %}
+
\ No newline at end of file
diff --git a/translations/es-ES/content/rest/reference/rate-limit.md b/translations/es-ES/content/rest/reference/rate-limit.md
index c9e1631d48d2..ec13bdc8072e 100644
--- a/translations/es-ES/content/rest/reference/rate-limit.md
+++ b/translations/es-ES/content/rest/reference/rate-limit.md
@@ -14,22 +14,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-La documentación general de la API de REST describe las [reglas de los límites de tasa](/rest/overview/resources-in-the-rest-api#rate-limiting). Puedes revisar tu estado actual de límite de tasa en cualquier momento utilizando la API de Límites de Tasa que se describe a continuación.
-
-### Entender el estado de tu límite de tasa
-
-La API de Búsqueda tiene un [límite de tasa personalizado](/rest/reference/search#rate-limit) separado de aquél que rige el resto de la API de REST. La API de GraphQL también tiene un [límite de tasa personalizado]({% ifversion ghec%}/free-pro-team@latest{% endif %}/graphql/overview/resource-limitations#rate-limit) que está separado y se calcula diferente que los límites de tasa de la API de REST.
-
-Es por esto que la respuesta de la API de Límites de Tasa categoriza tu límite de tasa. Debajo de `resources`, verás cuatro objetos:
-
-* El objeto `core` proporciona tu estado de límite de tasa para todos los recursos no relacionados a búsquedas en la API de REST.
-
-* El objeto `search` proporciona el estado de tu límite de tasa para la [API de Búsqueda](/rest/reference/search).
-
-* El objeto `graphql` proporciona el estado de tu límite de tasa para la [API de GraphQL]({% ifversion ghec%}/free-pro-team@latest{% endif %}/graphql).
-
-* El objeto `integration_manifest` proporciona el estado de tu límite de tasa para la terminal [Conversión de código para el Manifiesto de GitHub App](/apps/building-github-apps/creating-github-apps-from-a-manifest/#3-you-exchange-the-temporary-code-to-retrieve-the-app-configuration).
-
-Para obtener más información sobre los encabezados y valores en la respuesta de límite de tasa, consulta la sección "[Recursos en la API de REST](/rest/overview/resources-in-the-rest-api#rate-limit-http-headers)".
-
-{% include rest_operations_at_current_path %}
+
diff --git a/translations/es-ES/content/rest/reference/reactions.md b/translations/es-ES/content/rest/reference/reactions.md
index 897595632837..8f9506da010d 100644
--- a/translations/es-ES/content/rest/reference/reactions.md
+++ b/translations/es-ES/content/rest/reference/reactions.md
@@ -13,10 +13,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-### Tipos de reacción
-
-Cuando creas una reacción, los valores permitidos para el parámetro `content` son los siguientes (con el emoji correspondiente como referencia):
-
-{% data reusables.repositories.reaction_list %}
-
-{% include rest_operations_at_current_path %}
+
diff --git a/translations/es-ES/content/rest/reference/releases.md b/translations/es-ES/content/rest/reference/releases.md
index 4370f3a1bdb2..e5a858f3efc0 100644
--- a/translations/es-ES/content/rest/reference/releases.md
+++ b/translations/es-ES/content/rest/reference/releases.md
@@ -12,18 +12,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-{% note %}
-
-**Nota:** La API de Lanzamientos reemplaza a la API de Descargas. Puedes recuperar el conteo de descargas y la URL de descarga del buscador desde las terminales en esta API, las cuales devuelven los lanzamientos y los activos de éstos.
-
-{% endnote %}
-
-{% for operation in currentRestOperations %}
- {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
-{% endfor %}
-
-## Release assets
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'assets' %}{% include rest_operation %}{% endif %}
-{% endfor %}
+
diff --git a/translations/es-ES/content/rest/reference/repos.md b/translations/es-ES/content/rest/reference/repos.md
index 89a55881b8e8..51710d0f0ccc 100644
--- a/translations/es-ES/content/rest/reference/repos.md
+++ b/translations/es-ES/content/rest/reference/repos.md
@@ -14,64 +14,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-{% for operation in currentRestOperations %}
- {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
-{% endfor %}
-
-{% ifversion fpt or ghec or ghes > 3.2 or ghae-issue-4742 %}
-## Autolinks
-
-To help streamline your workflow, you can use the API to add autolinks to external resources like JIRA issues and Zendesk tickets. For more information, see "[Configuring autolinks to reference external resources](/github/administering-a-repository/configuring-autolinks-to-reference-external-resources)."
-
-{% data variables.product.prodname_github_apps %} require repository administration permissions with read or write access to use the Autolinks API.
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'autolinks' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-{% endif %}
-
-
-## Contents
-
-These API endpoints let you create, modify, and delete Base64 encoded content in a repository. To request the raw format or rendered HTML (when supported), use custom media types for repository contents.
-
-### Custom media types for repository contents
-
-[READMEs](/rest/reference/repos#get-a-repository-readme), [files](/rest/reference/repos#get-repository-content), and [symlinks](/rest/reference/repos#get-repository-content) support the following custom media types:
-
- application/vnd.github.VERSION.raw
- application/vnd.github.VERSION.html
-
-Use the `.raw` media type to retrieve the contents of the file.
-
-For markup files such as Markdown or AsciiDoc, you can retrieve the rendered HTML using the `.html` media type. Markup languages are rendered to HTML using our open-source [Markup library](https://github.com/github/markup).
-
-[All objects](/rest/reference/repos#get-repository-content) support the following custom media type:
-
- application/vnd.github.VERSION.object
-
-Use the `object` media type parameter to retrieve the contents in a consistent object format regardless of the content type. For example, instead of an array of objects
-for a directory, the response will be an object with an `entries` attribute containing the array of objects.
-
-You can read more about the use of media types in the API [here](/rest/overview/media-types).
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'contents' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## Forks
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'forks' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% ifversion fpt or ghae or ghes > 3.2 or ghec %}
-
-## Git LFS
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'lfs' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% endif %}
-
+
\ No newline at end of file
diff --git a/translations/es-ES/content/rest/reference/scim.md b/translations/es-ES/content/rest/reference/scim.md
index ab9cbd2350d9..4dc117d0ac1b 100644
--- a/translations/es-ES/content/rest/reference/scim.md
+++ b/translations/es-ES/content/rest/reference/scim.md
@@ -11,46 +11,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-### Aprovisionamiento de SCIM para las Organizaciones
-
-Los proveedores de identidad (IdP) habilitados para SCIM utilizan la API de SCIM para automatizar el aprovisionamiento de la membrecía de las organizaciones de {% data variables.product.product_name %}. La API de {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} se basa en la versión 2.0 del [SCIM estándar](http://www.simplecloud.info/). La terminal de SCIM de {% data variables.product.product_name %} que deben utilizar los IdP es: `{% data variables.product.api_url_code %}/scim/v2/organizations/{org}/`.
-
-{% note %}
-
-**Notas:**
- - La API de SCIM se encuentra disponible únicamente para las organizaciones de [{% data variables.product.prodname_ghe_cloud %}](/billing/managing-billing-for-your-github-account/about-billing-for-github-accounts) que cuentan con el [SSO de SAML](/rest/overview/other-authentication-methods#authenticating-for-saml-sso) habilitado. {% data reusables.scim.enterprise-account-scim %} Para obtener más información sobre SCIM, consulta la sección "[Acerca de SCIM](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim)".
- - La API de SCIM no puede utilizarse con {% data variables.product.prodname_emus %}.
-
-{% endnote %}
-
-### Autenticar las llamadas a la API de SCIM
-
-Debes autenticarte como un propietario de una organización de {% data variables.product.product_name %} para utilizar la API de SCIM. La API espera que se incluya un token [Portador de OAuth 2.0](/developers/apps/authenticating-with-github-apps) en el encabezado `Authorization`. También puedes utilizar un token de acceso personal, pero primero debes [autorizarlo para su uso con tu orgnización que cuenta con el SSO de SAML](/github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on).
-
-### Mapeo de los datos de SAML y de SCIM
-
-{% data reusables.scim.nameid-and-username-must-match %}
-
-### Atributos de Usuario de SCIM compatibles
-
-| Nombre | Tipo | Descripción |
-| ----------------- | ----------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `userName` | `secuencia` | El nombre de usuario para el usuario. |
-| `name.givenName` | `secuencia` | El primer nombre del usuario. |
-| `name.familyName` | `secuencia` | El apellido del usuario. |
-| `emails` | `arreglo` | Lista de correos electrónicos del usuario. |
-| `externalId` | `secuencia` | El proveedor de SAML genera este identificador, el cual utiliza como una ID única para empatarla contra un usuario de GitHub. Puedes encontrar la `externalID` de un usuario ya sea con el proveedor de SAML, o utilizando la terminal de [Listar las identidades aprovisionadas de SCIM](#list-scim-provisioned-identities) y filtrando otros atributos conocidos, tales como el nombre de usuario de GitHub o la dirección de correo electrónico de un usuario. |
-| `id` | `secuencia` | Identificador que genera la terminal de SCIM de GitHub. |
-| `active` | `boolean` | Se utiliza para indicar si la identidad está activa (true) o si debe desaprovisionarse (false). |
-
-{% note %}
-
-**Nota:** Las URL de terminal para la API de SCIM distinguen entre mayúsculas y minúsculas. Por ejemplo, la primera letra en la terminal `Users` debe ponerse en mayúscula:
-
-```shell
-GET /scim/v2/organizations/{org}/Users/{scim_user_id}
-```
-
-{% endnote %}
-
-{% include rest_operations_at_current_path %}
+
diff --git a/translations/es-ES/content/rest/reference/search.md b/translations/es-ES/content/rest/reference/search.md
index 7d67c72db596..f22157a05e72 100644
--- a/translations/es-ES/content/rest/reference/search.md
+++ b/translations/es-ES/content/rest/reference/search.md
@@ -13,150 +13,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-La API de Búsqueda te ayuda a buscar el elemento específico que quieres encontrar. Por ejemplo, puedes buscar un usuario o un archivo específico en el repositorio. Tómalo como el simil de realizar una búsqueda en Google. Se diseñó para ayudarte a encontrar el resultado exacto que estás buscando (o tal vez algunos de los resultados que buscas). Tal como la búsqueda en Google, a veces quieres ver algunas páginas de los resultados de búsqueda para que puedas encontrar el elemento que mejor satisfaga tus necesidades. Para satisfacer esta necesidad, la API de Búsqueda de {% data variables.product.product_name %} proporciona **hasta 1,000 resultados por búsqueda**.
-
-Puedes delimitar tu búsqueda utilizando consultas. Para aprender más sobre la sintaxis de las consultas de búsqueda, dirígete a "[Construir una consulta de búsqueda](/rest/reference/search#constructing-a-search-query)".
-
-### Clasificar los resultados de la búsqueda
-
-A menos de que se proporcione algún otro tipo de opción como parámetro de consulta, los resultados se clasificarán de acuerdo a la exactitud de la coincidencia en orden descendente. Varios factores se combinan para impulsar el elemento más relevante hasta arriba de la lista de resultados.
-
-### Limite de tasa
-
-{% data reusables.enterprise.rate_limit %}
-
-La API de Búsqueda tiene un límite de tasa personalizado. Para las solicitudes que utilizan [Autenticación Básica](/rest#authentication), [OAuth](/rest#authentication), o [secreto e ID de cliente](/rest#increasing-the-unauthenticated-rate-limit-for-oauth-applications), puedes hacer hasta 30 solicitudes por minuto. Para las solicitudes sin autenticar, el límite de tasa te permite hacer hasta 10 por minuto.
-
-Consulta la [documentación del límite de tasa](/rest/reference/rate-limit) para obtener más detalles sobre cómo determinar tu estado de límite de tasa actual.
-
-### Construir una consulta de búsqueda
-
-Cada terminal en la API de búsqueda utiliza [parámetros de búsqueda](https://en.wikipedia.org/wiki/Query_string) para realizar búsqeudas en {% data variables.product.product_name %}. Observa la terminal individual an la API de Búsqueda para encontrar un ejemplo que incluye los parámetros de consulta y de terminal.
-
-Una consulta puede contener cualquier combinación de calificadores de búsqueda que sea compatible con {% data variables.product.product_name %}. El formato de esta consulta de búsqueda es:
-
-```
-SEARCH_KEYWORD_1 SEARCH_KEYWORD_N QUALIFIER_1 QUALIFIER_N
-```
-
-Por ejemplo, si quisieras buscar todos los _repositorios_ que pertenecen a `defunkt` y que contienen la palabra `GitHub` y `Octocat` en el archivo de README, utilizarías la siguiente consulta con la terminal de _buscar repositorios_:
-
-```
-GitHub Octocat in:readme user:defunkt
-```
-
-**Nota:** Asegúrate de utilizar el codificador HTML preferido de tu lenguaje de programación para construir tus cadenas de consulta. Por ejemplo:
-```javascript
-// JavaScript
-const queryString = 'q=' + encodeURIComponent('GitHub Octocat in:readme user:defunkt');
-```
-
-Consulta la sección "[Buscar en GitHub](/search-github/searching-on-github)" para encontrar una lista completa de calificadores disponibles, su formato, y ejemplos de cómo utilizarlos. Para obtener más información acerca de cómo utilizar los operadores para que coincidan con cantidades y fechas específicas o para que excluyan resultados, consulta la sección "[Entender la sintaxis de búsqueda](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax/)".
-
-### Limitaciones sobre la longitud de la consulta
-
-La API de búsqueda no es compatible con consultas que:
-- sean mayores a 256 caracteres (sin incluir los operadores o calificativos).
-- tengan más de cinco operadores de `AND`, `OR`, o `NOT`.
-
-Estas consultas de búsqueda devolverán un mensaje de error de "Validation failed".
-
-### Tiempos excedidos y resultados incompletos
-
-Para que la API de Búsqueda se mantenga rápida para todos, limitamos el tiempo que puede jecutarse cualquier consulta específica. Para las consultas que [exceden el límite de tiempo](https://developer.github.com/changes/2014-04-07-understanding-search-results-and-potential-timeouts/), la API devuelve las coincidencias que ya se habían encontrado antes de exceder el tiempo, y la respuesta tiene la propiedad `incomplete_results` como `true`.
-
-Llegar a una interrupción no necesariamente significa que los resultados de búsqueda estén incompletos. Puede que se hayan encontrado más resultados, pero también puede que no.
-
-### Errores de acceso o resultados de búsqueda faltantes
-
-Necesitas autenticarte con éxito y tener acceso a los repositorios en tus consultas de búsqueda, de otro modo, verás un error `422 Unprocessable Entry` con un mensaje de "Validation Failed". Por ejemplo, tu búsqueda fallará si tu consulta incluye los calificadores `repo:`, `user:`, o `org:` que solicitan los recursos a los cuales no tienes acceso cuando inicias sesión en {% data variables.product.prodname_dotcom %}.
-
-Cuando tu consulta de búsqueda solicita recursos múltiples, la respuesta solo contendrá aquellos a los que tengas acceso y **no** proporcionará un mensaje de error que liste los recursos que no se devolvieron.
-
-Por ejemplo, si tu consulta de búsqueda quiere buscar en los repositorios `octocat/test` y `codertocat/test`, pero solo tienes acceso a `octocat/test`, tu respuesta mostrará los resultados de búsqueda para `octocat/test` y no mostrará nada para `codertocat/test`. Este comportamiento simula cómo funciona la búsqueda en {% data variables.product.prodname_dotcom %}.
-
-{% include rest_operations_at_current_path %}
-
-
-### Metadatos en el texto coincidente
-
-En GitHub, puedes utilizar el contexto que te proporcionan los extractos de código y los puntos destacados en los resultados de búsqueda. La API de Búsqueda ofrece metadatos adicionales que te permiten resaltar los términos de búsqueda coincidentes cuando se muestran los resultados de la búsqueda.
-
-
-
-Las solicitudes pueden decidir recibir esos fragmentos de texto en la respuesta, y cada fragmento se acompaña de intervalos numéricos que identifican la ubicación exacta de cada término de búsqueda coincidente.
-
-Para obtener estos metadatos en tus resultados de búsqueda, especifica el tipo de medios `text-match` en tu encabezado de `Accept`.
-
-```shell
-application/vnd.github.v3.text-match+json
-```
-
-Cuando proporcionas el tipo de medios `text-match`, recibirás una clave extra en la carga útil de JSON llamada `text_matches`, la cual proporciona información acerca de la posición de tus términos de búsqueda dentro del texto y la `property` que incluye dicho término de búsqueda. Dentro de la matriz `text_matches`, cada objeto incluye los siguientes atributos:
-
-| Nombre | Descripción |
-| ------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `object_url` | La URL del recurso que contiene una propiedad de secuencia que empata con uno de los términos de búsqueda. |
-| `object_type` | El nombre del tipo de recurso que existe en la `object_url` específica. |
-| `property` | El nombre de la propiedad del recurso que existe en la `object_url`. Esa propiedad es una secuencia que empata con uno de los términos de la búsqueda. (En el JSON que se devuelve de la `object_url`, el contenido entero para el `fragment` se encontrará en la propiedad con este nombre.) |
-| `fragmento` | Un subconjunto del valor de `property`. Este es el fragmento de texto que empata con uno o más de los términos de búsqueda. |
-| `matches` | Una matriz de uno o más términos de búsqueda presentes en el `fragment`. Los índices (es decir, "intervalos") son relativos al fragmento. (No son relativos al contenido _completo_ de `property`.) |
-
-#### Ejemplo
-
-Si utilizas cURL y también el [ejemplo de búsqueda de informe de problemas](#search-issues-and-pull-requests) anterior, nuestra solicitud de la API se vería así:
-
-``` shell
-curl -H 'Accept: application/vnd.github.v3.text-match+json' \
-'{% data variables.product.api_url_pre %}/search/issues?q=windows+label:bug+language:python+state:open&sort=created&order=asc'
-```
-
-La respuesta incluirá una matriz de `text_matches` para cada resultado de búsqueda. En el JSON que se muestra a continuación, tenemos dos objetos en la matriz `text_matches`.
-
-La primera coincidencia de texto ocurrió en la propiedad de `body` del informe de problemas. Aquí vemos un fragmento de texto del cuerpo del informe de problemas. El término de búsqueda (`windows`) aparece dos veces dentro de ese fragmento, y tenemos los índices para cada ocurrencia.
-
-La segunda coincidencia de texto ocurrió en la propiedad `body` de uno de los comentarios del informe de problemas. Tenemos la URL para el comentario del informe de problemas. Y, por supuesto, vemos un fragmento de texto del cuerpo del comentario. El término de búsqueda (`windows`) se muestra una vez dentro de ese fragmento.
-
-```json
-{
- "text_matches": [
- {
- "object_url": "https://api.github.com/repositories/215335/issues/132",
- "object_type": "Issue",
- "property": "body",
- "fragment": "comprehensive windows font I know of).\n\nIf we can find a commonly distributed windows font that supports them then no problem (we can use html font tags) but otherwise the '(21)' style is probably better.\n",
- "matches": [
- {
- "text": "windows",
- "indices": [
- 14,
- 21
- ]
- },
- {
- "text": "windows",
- "indices": [
- 78,
- 85
- ]
- }
- ]
- },
- {
- "object_url": "https://api.github.com/repositories/215335/issues/comments/25688",
- "object_type": "IssueComment",
- "property": "body",
- "fragment": " right after that are a bit broken IMHO :). I suppose we could have some hack that maxes out at whatever the font does...\n\nI'll check what the state of play is on Windows.\n",
- "matches": [
- {
- "text": "Windows",
- "indices": [
- 163,
- 170
- ]
- }
- ]
- }
- ]
-}
-```
+
diff --git a/translations/es-ES/content/rest/reference/secret-scanning.md b/translations/es-ES/content/rest/reference/secret-scanning.md
index d9f59f618e03..73645f419cb0 100644
--- a/translations/es-ES/content/rest/reference/secret-scanning.md
+++ b/translations/es-ES/content/rest/reference/secret-scanning.md
@@ -9,14 +9,6 @@ versions:
miniTocMaxHeadingLevel: 3
---
-{% data reusables.secret-scanning.api-beta %}
-
-La API del {% data variables.product.prodname_secret_scanning %} te permite {% ifversion fpt or ghec or ghes > 3.1 or ghae %}:
-
-- Habilitar o inhabilitar el {% data variables.product.prodname_secret_scanning %} para un repositorio. Para obtener más información, consulta la sección "[Repositorios](/rest/reference/repos#update-a-repository)" en la documentación de REST.
-- Recupera y actualiza las alertas del {% data variables.product.prodname_secret_scanning %} desde un repositorio {% ifversion fpt or ghec %}privado{% endif %}. Para obtener más detalles, consulta las secciones a continuación.
-{%- else %} recupera y actualiza las alertas del {% data variables.product.prodname_secret_scanning %} desde un repositorio {% ifversion fpt or ghec %}privado{% endif %}.{% endif %}
-
-Para obtener más información acerca de las {% data variables.product.prodname_secret_scanning %}, consulta la sección "[Acerca del {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/about-secret-scanning)".
-
-{% include rest_operations_at_current_path %}
+
diff --git a/translations/es-ES/content/rest/reference/teams.md b/translations/es-ES/content/rest/reference/teams.md
index d21fba1287cb..b1da1945f400 100644
--- a/translations/es-ES/content/rest/reference/teams.md
+++ b/translations/es-ES/content/rest/reference/teams.md
@@ -13,84 +13,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-Esta API solo está disponible para los miembros autenticados de la [organization](/rest/reference/orgs) del equipo. Los tokens de acceso de OAuth requieren el [alcance](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/) `read:org`. {% data variables.product.prodname_dotcom %} genera el `slug` del equipo a partir del `name` del mismo.
-
-{% for operation in currentRestOperations %}
- {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
-{% endfor %}
-
-## Debates
-
-La API de debates de equipo te permite obtener, crear, editar y borrar las publicaciones de un debate en la página de un equipo. Puedes utilizar los debates de equipo para sostener conversaciones que no son específicas de un repositorio o proyecto. Cualquier miembro de la [organización](/rest/reference/orgs) del equipo puede crear y leer las publicaciones de debates públicos. Para obtener más detalles, consulta la sección "[Acerca de los debates de equipo](//organizations/collaborating-with-your-team/about-team-discussions/)". Para aprender más sobre cómo comentar en una publicación de debate, consulta la [API de comentarios para debates de equipo](/rest/reference/teams#discussion-comments). Esta API solo está disponible para los miembros autenticados de la organization del equipo.
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'discussions' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## Comentarios de debate
-
-La API de comentarios para debates de equipo te permite obtener, crear, editar y borrar los comentarios del debate en una publicación de un [debate de equipo](/rest/reference/teams#discussions). Cualquier miembro de la [organización](/rest/reference/orgs) del equipo puede crear y leer los comentarios de un debate público. Para obtener más detalles, consulta la sección "[Acerca de los debates de equipo](/organizations/collaborating-with-your-team/about-team-discussions/)". Esta API solo está disponible para los miembros autenticados de la organization del equipo.
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'discussion-comments' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## Miembros
-
-Esta API solo está disponible para los miembros autenticados de la organization del equipo. Los tokens de acceso de OAuth requieren el [alcance](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/) `read:org`.
-
-{% ifversion fpt or ghes or ghec %}
-{% note %}
-
-**Nota:** Cuando configuras la sincornizacion de equipos para un equipo con el proveedor de identidad (IdP) de tu organización, verás un error si intentas utilizar la API para hacer cambios en la membrecía de dicho equipo. Si tienes acceso para administrar las membrecías de usuario en tu IdP, puedes administrar la membrecía del equipo de GitHub a través de tu proveedor de identidad, lo cual agrega y elimina automáticamente a los miembros en una organización. Para obtener más información, consulta la sección "Sincronizar equipos entre tu proveedor de identidad y GitHub".
-
-{% endnote %}
-
-{% endif %}
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'members' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% ifversion ghec or ghae %}
-## Grupos externos
-
-La API de grupos externos te permite ver los grupos de proveedor de identidad externos que están disponibles para tu organización, así como administrar la conexión entre los grupos externos y los equipos de tu organziación.
-
-Para utilizar esta API, el usuario autenticado debe ser un mantenedor del equipo o un propietario de la organización asociada con éste.
-
-{% ifversion ghec %}
-{% note %}
-
-**Notas:**
-
-- La API de grupos externos solo se encuentra disponible para aquellas organizaciones que sean parte de una empresa que utilice {% data variables.product.prodname_emus %}. Para obtener más información, consulta la sección "[Acerca de los Usuarios Empresariales Administrados](/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)".
-- Si tu organización utiliza la sincronización de equipos, puedes usar la API de Sincronización de Equipos. Para obtener más información, consulta la "[API de sincronización de equipos](#team-synchronization)".
-
-{% endnote %}
-{% endif %}
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'external-groups' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% endif %}
-
-{% ifversion fpt or ghes or ghec %}
-## Sincronización de equipos
-
-La API de sincronización de equipos te permite administrar las conexiones entre los equipos de {% data variables.product.product_name %} y los grupos del proveedor de identidad (IdP) externo. Para utilizar esta API, el usuario autenticado debe ser un mantenedor del equipo o un propietario de la organización asociada con éste. El token que utilizas para autenticarte también necesitará autorizarse para su uso con tu proveedor IdP (SSO). Para obtener más información, consulta la sección "Autorizar un token de acceso personal para su uso con una organización que tiene inicio de sesión único de SAML".
-
-Puedes administrar a los miembros del equipo de GitHub a través de tu IdP con la sincronización de equipos. Ésta se debe habilitar para usar la API de Sincronización de Equipos. Para obtener más información, consulta la sección "Sincronizar equipos entre tu proveedor de identidad y GitHub".
-
-{% note %}
-
-**Nota:** La API de sincronización de equipos no puede utilizarse con {% data variables.product.prodname_emus %}. Para aprender más sobre cómo administrar una {% data variables.product.prodname_emu_org %}, consulta la sección "[API de grupos externos](/enterprise-cloud@latest/rest/reference/teams#external-groups)".
-
-{% endnote %}
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'team-sync' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% endif %}
+
diff --git a/translations/es-ES/content/rest/reference/users.md b/translations/es-ES/content/rest/reference/users.md
index 3997716757b7..e17aeff2651e 100644
--- a/translations/es-ES/content/rest/reference/users.md
+++ b/translations/es-ES/content/rest/reference/users.md
@@ -13,48 +13,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-Muchos de los recursos en la API de los usuarios proporcionan un atajo para obtener información acerca del usuario autenticado actualmente. Si una URL de solicitud no incluye un parámetro de `{username}`, entonces la respuesta será para el usuario que inició sesión (y debes pasar la [información de autenticación](/rest/overview/resources-in-the-rest-api#authentication) con tu solicitud).{% ifversion fpt or ghes or ghec %} La información privada adicional, tal como si un usuario tiene habilitada la autenticación bifactorial, se incluye cuando se está autenticado con la autenticación básica o a través de OAuth, con el alcance de `user`.{% endif %}
-
-{% for operation in currentRestOperations %}
- {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
-{% endfor %}
-
-{% ifversion fpt or ghec %}
-## Bloquear usuarios
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'blocking' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% endif %}
-
-{% ifversion fpt or ghes or ghec %}
-## Emails (Correos electrónicos)
-
-Administrar las direcciones de correo electrónico a través de la API requiere que ingreses con la autenticación básica o con OAuth con un alcance correcto para la terminal.
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'emails' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% endif %}
-
-## Seguidores
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'followers' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## Llaves SSH de Git
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'keys' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## Claves GPG
-
-Los datos que se devuelven en el campo de respuesta de `public_key` no son una llave con formato de GPG. Cuando un usuario carga una llave GPG, se interpreta y la llave pública criptográfica se extrae y se almacena. Esta llave criptográfica es lo que devuelven las API en esta página. Esta llave no es apta para utilizarse directamente con programas como GPG.
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'gpg-keys' %}{% include rest_operation %}{% endif %}
-{% endfor %}
+
diff --git a/translations/es-ES/content/rest/reference/webhooks.md b/translations/es-ES/content/rest/reference/webhooks.md
index 62ab78c2c992..c59eb213e7cf 100644
--- a/translations/es-ES/content/rest/reference/webhooks.md
+++ b/translations/es-ES/content/rest/reference/webhooks.md
@@ -12,83 +12,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-Los webhooks de repositorio te permiten recibir cargas útiles de `POST` por HTTP cuando ciertos eventos suceden en un repositorio. {% data reusables.webhooks.webhooks-rest-api-links %}
-
-Si te gustaría configurar un solo webhook para recibir eventos de todos los repositorios de tu organización, consulta nuestra documentación de la API para los [Webhooks de una Organización](/rest/reference/orgs#webhooks).
-
-Adicionalmente a la API de REST, {% data variables.product.prodname_dotcom %} también puede servir como un punto de [PubSubHubbub](#pubsubhubbub) para los repositorios.
-
-{% for operation in currentRestOperations %}
- {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
-{% endfor %}
-
-## Webhooks de repositorio
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'repos' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## Repository webhook configuration
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'repo-config' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## Repository webhook deliveries
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'repo-deliveries' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## Recibir Webhooks
-
-Para que {% data variables.product.product_name %} envíe cargas útiles de webhooks, se necesita que se pueda acceder a tu servidor desde la internet. También sugerimos ampliamente utilizar SSL para que podamos enviar cargas útiles cifradas a través de HTTPS.
-
-### Encabezados de Webhook
-
-{% data variables.product.product_name %} enviará varios encabezados de HTTP para diferenciar los tipos de eventos y los identificadores de las cargas útiles. Consulta la sección de [encabezados de webhook](/developers/webhooks-and-events/webhook-events-and-payloads#delivery-headers) para encontrar más detalles.
-
-## PubSubHubbub
-
-GitHub también puede fungir como un centro de [PubSubHubbub](https://github.com/pubsubhubbub/PubSubHubbub) para todos los repositorios. PSHB es un proptocolo simple de publicación/suscripción que permite a los servidores registrarse para recibir actualizaciones de cuándo se actualiza un tema. Las actualizaciones se mandan con una solicitud HTTP de tipo POST a una URL de rellamado. Las URL de tema para las cargas a un repositorio de GitHub están en este formato:
-
-`https://github.com/{owner}/{repo}/events/{event}`
-
-El veneto puede ser cualquier evento de webhook disponible. Para obtener más información, consulta la sección "[eventos y cargas útiles de los webhooks](/developers/webhooks-and-events/webhook-events-and-payloads)".
-
-### Formato de respuesta
-
-El formato predeterminado es lo que [deberían esperar los ganchos de post-recepción](/post-receive-hooks/): Un cuerpo de JSON que se envía como un parámetro de `payload` en un POST. También puedes especificar si quieres recibir el cuerpo en JSON sin procesar, ya sea un encabezado de `Accept` o una extensión `.json`.
-
- Accept: application/json
- https://github.com/{owner}/{repo}/events/push.json
-
-### URL de Rellamado
-
-Las URL de rellamado puede utilizar el protocolo `http://`.
-
- # Send updates to postbin.org
- http://postbin.org/123
-
-### Suscribirse
-
-La terminal de PubSubHubbub de GitHub es: `{% data variables.product.api_url_code %}/hub`. Una solicitud exitosa con curl se vería así:
-
-``` shell
-curl -u "user" -i \
- {% data variables.product.api_url_pre %}/hub \
- -F "hub.mode=subscribe" \
- -F "hub.topic=https://github.com/{owner}/{repo}/events/push" \
- -F "hub.callback=http://postbin.org/123"
-```
-
-Las solicitudes de PubSubHubbub pueden enviarse varias veces. Si el gancho ya existe, se modificará de acuerdo con la solicitud.
-
-#### Parámetros
-
-| Nombre | Tipo | Descripción |
-| -------------- | ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| `hub.mode` | `secuencia` | **Requerido**. Ya sea `subscribe` o `unsubscribe`. |
-| `hub.topic` | `secuencia` | **Requerido**. La URI del repositorio de GitHub al cual suscribirse. La ruta debe estar en el formato `/{owner}/{repo}/events/{event}`. |
-| `hub.callback` | `secuencia` | La URI para recibir las actualizaciones del tema. |
-| `hub.secret` | `secuencia` | Una llave de secreto compartido que genera una firma de hash del contenido saliente del cuerpo. Puedes verificar si una subida vino de GitHub comparando el cuerpo de la solicitud sin procesar con el contenido de los encabezados de la {% ifversion fpt or ghes > 2.22 or ghec %}`X-Hub-Signature` o `X-Hub-Signature-256`{% elsif ghes < 3.0 %}`X-Hub-Signature`{% elsif ghae %}`X-Hub-Signature-256`{% endif %}. Puedes ver [la documentación de PubSubHubbub](https://pubsubhubbub.github.io/PubSubHubbub/pubsubhubbub-core-0.4.html#authednotify) para obtener más detalles. |
+
diff --git a/translations/es-ES/data/graphql/ghae/graphql_upcoming_changes.public-ghae.yml b/translations/es-ES/data/graphql/ghae/graphql_upcoming_changes.public-ghae.yml
index 0da647997a41..c94652d1f500 100644
--- a/translations/es-ES/data/graphql/ghae/graphql_upcoming_changes.public-ghae.yml
+++ b/translations/es-ES/data/graphql/ghae/graphql_upcoming_changes.public-ghae.yml
@@ -112,3 +112,17 @@ upcoming_changes:
date: '2021-10-01T00:00:00+00:00'
criticality: breaking
owner: synthead
+ -
+ location: PullRequest.viewerCanOverrideMergeQueue
+ description: '`viewerCanOverrideMergeQueue` will be removed. Use PullRequest.viewerCanMergeAsAdmin instead.'
+ reason: '`viewer_can_override_merge_queue` will be removed'
+ date: '01-04-2022'
+ criticality: breaking
+ owner: cbeaman
+ -
+ location: Repository.defaultMergeQueue
+ description: '`defaultMergeQueue` will be removed. Use `Repository.mergeQueue` instead.'
+ reason: '`defaultMergeQueue` will be removed.'
+ date: '01-04-2022'
+ criticality: breaking
+ owner: colinshum
diff --git a/translations/es-ES/data/graphql/ghec/graphql_upcoming_changes.public.yml b/translations/es-ES/data/graphql/ghec/graphql_upcoming_changes.public.yml
index 897fb69107b7..14faa119fb44 100644
--- a/translations/es-ES/data/graphql/ghec/graphql_upcoming_changes.public.yml
+++ b/translations/es-ES/data/graphql/ghec/graphql_upcoming_changes.public.yml
@@ -126,3 +126,24 @@ upcoming_changes:
date: '2021-10-01T00:00:00+00:00'
criticality: breaking
owner: synthead
+ -
+ location: PullRequest.viewerCanOverrideMergeQueue
+ description: '`viewerCanOverrideMergeQueue` will be removed. Use PullRequest.viewerCanMergeAsAdmin instead.'
+ reason: '`viewer_can_override_merge_queue` will be removed'
+ date: '01-04-2022'
+ criticality: breaking
+ owner: cbeaman
+ -
+ location: Repository.defaultMergeQueue
+ description: '`defaultMergeQueue` will be removed. Use `Repository.mergeQueue` instead.'
+ reason: '`defaultMergeQueue` will be removed.'
+ date: '01-04-2022'
+ criticality: breaking
+ owner: colinshum
+ -
+ location: Query.sponsorables.dependencyEcosystem
+ description: '`dependencyEcosystem` will be removed. Use the ecosystem argument instead.'
+ reason: The type is switching from SecurityAdvisoryEcosystem to DependencyGraphEcosystem.
+ date: '2022-07-01T00:00:00+00:00'
+ criticality: breaking
+ owner: cheshire137
diff --git a/translations/es-ES/data/graphql/graphql_upcoming_changes.public.yml b/translations/es-ES/data/graphql/graphql_upcoming_changes.public.yml
index 897fb69107b7..14faa119fb44 100644
--- a/translations/es-ES/data/graphql/graphql_upcoming_changes.public.yml
+++ b/translations/es-ES/data/graphql/graphql_upcoming_changes.public.yml
@@ -126,3 +126,24 @@ upcoming_changes:
date: '2021-10-01T00:00:00+00:00'
criticality: breaking
owner: synthead
+ -
+ location: PullRequest.viewerCanOverrideMergeQueue
+ description: '`viewerCanOverrideMergeQueue` will be removed. Use PullRequest.viewerCanMergeAsAdmin instead.'
+ reason: '`viewer_can_override_merge_queue` will be removed'
+ date: '01-04-2022'
+ criticality: breaking
+ owner: cbeaman
+ -
+ location: Repository.defaultMergeQueue
+ description: '`defaultMergeQueue` will be removed. Use `Repository.mergeQueue` instead.'
+ reason: '`defaultMergeQueue` will be removed.'
+ date: '01-04-2022'
+ criticality: breaking
+ owner: colinshum
+ -
+ location: Query.sponsorables.dependencyEcosystem
+ description: '`dependencyEcosystem` will be removed. Use the ecosystem argument instead.'
+ reason: The type is switching from SecurityAdvisoryEcosystem to DependencyGraphEcosystem.
+ date: '2022-07-01T00:00:00+00:00'
+ criticality: breaking
+ owner: cheshire137
diff --git a/translations/es-ES/data/reusables/github-actions/actions-activity-types.md b/translations/es-ES/data/reusables/actions/actions-activity-types.md
similarity index 100%
rename from translations/es-ES/data/reusables/github-actions/actions-activity-types.md
rename to translations/es-ES/data/reusables/actions/actions-activity-types.md
diff --git a/translations/es-ES/data/reusables/github-actions/actions-billing.md b/translations/es-ES/data/reusables/actions/actions-billing.md
similarity index 100%
rename from translations/es-ES/data/reusables/github-actions/actions-billing.md
rename to translations/es-ES/data/reusables/actions/actions-billing.md
diff --git a/translations/es-ES/data/reusables/github-actions/actions-do-not-trigger-workflows.md b/translations/es-ES/data/reusables/actions/actions-do-not-trigger-workflows.md
similarity index 100%
rename from translations/es-ES/data/reusables/github-actions/actions-do-not-trigger-workflows.md
rename to translations/es-ES/data/reusables/actions/actions-do-not-trigger-workflows.md
diff --git a/translations/es-ES/data/reusables/github-actions/actions-filters.md b/translations/es-ES/data/reusables/actions/actions-filters.md
similarity index 100%
rename from translations/es-ES/data/reusables/github-actions/actions-filters.md
rename to translations/es-ES/data/reusables/actions/actions-filters.md
diff --git a/translations/es-ES/data/reusables/github-actions/actions-multiple-types.md b/translations/es-ES/data/reusables/actions/actions-multiple-types.md
similarity index 100%
rename from translations/es-ES/data/reusables/github-actions/actions-multiple-types.md
rename to translations/es-ES/data/reusables/actions/actions-multiple-types.md
diff --git a/translations/es-ES/data/reusables/actions/actions-on-examples.md b/translations/es-ES/data/reusables/actions/actions-on-examples.md
new file mode 100644
index 000000000000..027db33e7fe2
--- /dev/null
+++ b/translations/es-ES/data/reusables/actions/actions-on-examples.md
@@ -0,0 +1,19 @@
+### Utilizar un evento simple
+
+{% data reusables.actions.on-single-example %}
+
+### Utilizar eventos múltiples
+
+{% data reusables.actions.on-multiple-example %}
+
+### Utilizar tipos de actividad
+
+{% data reusables.actions.actions-activity-types %}
+
+### Utilizar filtros
+
+{% data reusables.actions.actions-filters %}
+
+### Utilizar los tipos de actividad y filtros con eventos múltiples
+
+{% data reusables.actions.actions-multiple-types %}
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/github-actions/actions-spending-limit-brief.md b/translations/es-ES/data/reusables/actions/actions-spending-limit-brief.md
similarity index 100%
rename from translations/es-ES/data/reusables/github-actions/actions-spending-limit-brief.md
rename to translations/es-ES/data/reusables/actions/actions-spending-limit-brief.md
diff --git a/translations/es-ES/data/reusables/github-actions/actions-spending-limit-detailed.md b/translations/es-ES/data/reusables/actions/actions-spending-limit-detailed.md
similarity index 88%
rename from translations/es-ES/data/reusables/github-actions/actions-spending-limit-detailed.md
rename to translations/es-ES/data/reusables/actions/actions-spending-limit-detailed.md
index 81d05a2b041f..96d0af91771d 100644
--- a/translations/es-ES/data/reusables/github-actions/actions-spending-limit-detailed.md
+++ b/translations/es-ES/data/reusables/actions/actions-spending-limit-detailed.md
@@ -1,3 +1,3 @@
-{% data reusables.github-actions.actions-spending-limit-brief %}
+{% data reusables.actions.actions-spending-limit-brief %}
Si tu límite de gastos es ilimitado o lo configuraste en más de $0 USD, se te facturará por cualquier minuto o almacenamiento adicional que esté más allá de las cantidades que se incluyen en tu cuenta, lo cual también se conoce como excedentes. {% data variables.product.prodname_dotcom %} cobra el uso a la cuenta a la que pertenezca el repositorio en donde se ejecuta un flujo de trabajo. No podrán aplicarse los cupones que tenga tu cuenta para los excedentes de {% data variables.product.prodname_actions %}.
diff --git a/translations/es-ES/data/reusables/github-actions/actions-unused-labels.md b/translations/es-ES/data/reusables/actions/actions-unused-labels.md
similarity index 100%
rename from translations/es-ES/data/reusables/github-actions/actions-unused-labels.md
rename to translations/es-ES/data/reusables/actions/actions-unused-labels.md
diff --git a/translations/es-ES/data/reusables/github-actions/artifact-log-retention-statement.md b/translations/es-ES/data/reusables/actions/artifact-log-retention-statement.md
similarity index 100%
rename from translations/es-ES/data/reusables/github-actions/artifact-log-retention-statement.md
rename to translations/es-ES/data/reusables/actions/artifact-log-retention-statement.md
diff --git a/translations/es-ES/data/reusables/github-actions/branch-paths-filter.md b/translations/es-ES/data/reusables/actions/branch-paths-filter.md
similarity index 100%
rename from translations/es-ES/data/reusables/github-actions/branch-paths-filter.md
rename to translations/es-ES/data/reusables/actions/branch-paths-filter.md
diff --git a/translations/es-ES/data/reusables/github-actions/branch-requirement.md b/translations/es-ES/data/reusables/actions/branch-requirement.md
similarity index 100%
rename from translations/es-ES/data/reusables/github-actions/branch-requirement.md
rename to translations/es-ES/data/reusables/actions/branch-requirement.md
diff --git a/translations/es-ES/data/reusables/github-actions/change-retention-period-for-artifacts-logs.md b/translations/es-ES/data/reusables/actions/change-retention-period-for-artifacts-logs.md
similarity index 100%
rename from translations/es-ES/data/reusables/github-actions/change-retention-period-for-artifacts-logs.md
rename to translations/es-ES/data/reusables/actions/change-retention-period-for-artifacts-logs.md
diff --git a/translations/es-ES/data/reusables/github-actions/contacting-support.md b/translations/es-ES/data/reusables/actions/contacting-support.md
similarity index 100%
rename from translations/es-ES/data/reusables/github-actions/contacting-support.md
rename to translations/es-ES/data/reusables/actions/contacting-support.md
diff --git a/translations/es-ES/data/reusables/github-actions/container-jobs-intro.md b/translations/es-ES/data/reusables/actions/container-jobs-intro.md
similarity index 100%
rename from translations/es-ES/data/reusables/github-actions/container-jobs-intro.md
rename to translations/es-ES/data/reusables/actions/container-jobs-intro.md
diff --git a/translations/es-ES/data/reusables/github-actions/context-injection-warning.md b/translations/es-ES/data/reusables/actions/context-injection-warning.md
similarity index 100%
rename from translations/es-ES/data/reusables/github-actions/context-injection-warning.md
rename to translations/es-ES/data/reusables/actions/context-injection-warning.md
diff --git a/translations/es-ES/data/reusables/github-actions/copy-workflow-file.md b/translations/es-ES/data/reusables/actions/copy-workflow-file.md
similarity index 100%
rename from translations/es-ES/data/reusables/github-actions/copy-workflow-file.md
rename to translations/es-ES/data/reusables/actions/copy-workflow-file.md
diff --git a/translations/es-ES/data/reusables/github-actions/defaults-override.md b/translations/es-ES/data/reusables/actions/defaults-override.md
similarity index 100%
rename from translations/es-ES/data/reusables/github-actions/defaults-override.md
rename to translations/es-ES/data/reusables/actions/defaults-override.md
diff --git a/translations/es-ES/data/reusables/github-actions/disabled-actions-description.md b/translations/es-ES/data/reusables/actions/disabled-actions-description.md
similarity index 100%
rename from translations/es-ES/data/reusables/github-actions/disabled-actions-description.md
rename to translations/es-ES/data/reusables/actions/disabled-actions-description.md
diff --git a/translations/es-ES/data/reusables/github-actions/disabling-github-actions.md b/translations/es-ES/data/reusables/actions/disabling-github-actions.md
similarity index 100%
rename from translations/es-ES/data/reusables/github-actions/disabling-github-actions.md
rename to translations/es-ES/data/reusables/actions/disabling-github-actions.md
diff --git a/translations/es-ES/data/reusables/github-actions/docker-container-os-support.md b/translations/es-ES/data/reusables/actions/docker-container-os-support.md
similarity index 100%
rename from translations/es-ES/data/reusables/github-actions/docker-container-os-support.md
rename to translations/es-ES/data/reusables/actions/docker-container-os-support.md
diff --git a/translations/es-ES/data/reusables/github-actions/dockerfile-guidelines.md b/translations/es-ES/data/reusables/actions/dockerfile-guidelines.md
similarity index 100%
rename from translations/es-ES/data/reusables/github-actions/dockerfile-guidelines.md
rename to translations/es-ES/data/reusables/actions/dockerfile-guidelines.md
diff --git a/translations/es-ES/data/reusables/github-actions/enabled-actions-description.md b/translations/es-ES/data/reusables/actions/enabled-actions-description.md
similarity index 100%
rename from translations/es-ES/data/reusables/github-actions/enabled-actions-description.md
rename to translations/es-ES/data/reusables/actions/enabled-actions-description.md
diff --git a/translations/es-ES/data/reusables/github-actions/enabled-local-github-actions.md b/translations/es-ES/data/reusables/actions/enabled-local-github-actions.md
similarity index 100%
rename from translations/es-ES/data/reusables/github-actions/enabled-local-github-actions.md
rename to translations/es-ES/data/reusables/actions/enabled-local-github-actions.md
diff --git a/translations/es-ES/data/reusables/github-actions/enterprise-billing-details.md b/translations/es-ES/data/reusables/actions/enterprise-billing-details.md
similarity index 100%
rename from translations/es-ES/data/reusables/github-actions/enterprise-billing-details.md
rename to translations/es-ES/data/reusables/actions/enterprise-billing-details.md
diff --git a/translations/es-ES/data/reusables/github-actions/example-github-runner.md b/translations/es-ES/data/reusables/actions/example-github-runner.md
similarity index 100%
rename from translations/es-ES/data/reusables/github-actions/example-github-runner.md
rename to translations/es-ES/data/reusables/actions/example-github-runner.md
diff --git a/translations/es-ES/data/reusables/github-actions/expression-syntax-if.md b/translations/es-ES/data/reusables/actions/expression-syntax-if.md
similarity index 100%
rename from translations/es-ES/data/reusables/github-actions/expression-syntax-if.md
rename to translations/es-ES/data/reusables/actions/expression-syntax-if.md
diff --git a/translations/es-ES/data/reusables/github-actions/forked-write-permission.md b/translations/es-ES/data/reusables/actions/forked-write-permission.md
similarity index 100%
rename from translations/es-ES/data/reusables/github-actions/forked-write-permission.md
rename to translations/es-ES/data/reusables/actions/forked-write-permission.md
diff --git a/translations/es-ES/data/reusables/actions/ghes-actions-not-enabled-by-default.md b/translations/es-ES/data/reusables/actions/ghes-actions-not-enabled-by-default.md
new file mode 100644
index 000000000000..04afb9489221
--- /dev/null
+++ b/translations/es-ES/data/reusables/actions/ghes-actions-not-enabled-by-default.md
@@ -0,0 +1 @@
+{% data variables.product.prodname_actions %} is not enabled for {% data variables.product.prodname_ghe_server %} by default.
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/github-actions/github-context-warning.md b/translations/es-ES/data/reusables/actions/github-context-warning.md
similarity index 100%
rename from translations/es-ES/data/reusables/github-actions/github-context-warning.md
rename to translations/es-ES/data/reusables/actions/github-context-warning.md
diff --git a/translations/es-ES/data/reusables/github-actions/github-hosted-runners-check-concurrency.md b/translations/es-ES/data/reusables/actions/github-hosted-runners-check-concurrency.md
similarity index 100%
rename from translations/es-ES/data/reusables/github-actions/github-hosted-runners-check-concurrency.md
rename to translations/es-ES/data/reusables/actions/github-hosted-runners-check-concurrency.md
diff --git a/translations/es-ES/data/reusables/github-actions/github-hosted-runners-navigate-to-repo-org-enterprise.md b/translations/es-ES/data/reusables/actions/github-hosted-runners-navigate-to-repo-org-enterprise.md
similarity index 100%
rename from translations/es-ES/data/reusables/github-actions/github-hosted-runners-navigate-to-repo-org-enterprise.md
rename to translations/es-ES/data/reusables/actions/github-hosted-runners-navigate-to-repo-org-enterprise.md
diff --git a/translations/es-ES/data/reusables/github-actions/github-hosted-runners-table-entry.md b/translations/es-ES/data/reusables/actions/github-hosted-runners-table-entry.md
similarity index 100%
rename from translations/es-ES/data/reusables/github-actions/github-hosted-runners-table-entry.md
rename to translations/es-ES/data/reusables/actions/github-hosted-runners-table-entry.md
diff --git a/translations/zh-CN/data/reusables/github-actions/github-token-available-permissions.md b/translations/es-ES/data/reusables/actions/github-token-available-permissions.md
similarity index 72%
rename from translations/zh-CN/data/reusables/github-actions/github-token-available-permissions.md
rename to translations/es-ES/data/reusables/actions/github-token-available-permissions.md
index 5fca1254333e..5af40196917d 100644
--- a/translations/zh-CN/data/reusables/github-actions/github-token-available-permissions.md
+++ b/translations/es-ES/data/reusables/actions/github-token-available-permissions.md
@@ -1,4 +1,4 @@
-可用的作用域和访问权限值：
+Available scopes and access values:
```yaml
permissions:
@@ -17,9 +17,9 @@ permissions:
statuses: read|write|none
```
-如果您指定其中任何作用域的访问权限，则所有未指定的作用域都被设置为 `none`。
+If you specify the access for any of these scopes, all of those that are not specified are set to `none`.
-您可以使用以下语法来定义所有可用作用域的读取或写入权限：
+You can use the following syntax to define read or write access for all of the available scopes:
```yaml
permissions: read-all|write-all
diff --git a/translations/es-ES/data/reusables/github-actions/github-token-permissions.md b/translations/es-ES/data/reusables/actions/github-token-permissions.md
similarity index 100%
rename from translations/es-ES/data/reusables/github-actions/github-token-permissions.md
rename to translations/es-ES/data/reusables/actions/github-token-permissions.md
diff --git a/translations/es-ES/data/reusables/github-actions/github_token-input-example.md b/translations/es-ES/data/reusables/actions/github_token-input-example.md
similarity index 100%
rename from translations/es-ES/data/reusables/github-actions/github_token-input-example.md
rename to translations/es-ES/data/reusables/actions/github_token-input-example.md
diff --git a/translations/es-ES/data/reusables/github-actions/gradle-workflow-steps.md b/translations/es-ES/data/reusables/actions/gradle-workflow-steps.md
similarity index 100%
rename from translations/es-ES/data/reusables/github-actions/gradle-workflow-steps.md
rename to translations/es-ES/data/reusables/actions/gradle-workflow-steps.md
diff --git a/translations/es-ES/data/reusables/github-actions/hosted-runner-configure-runner-group-access.md b/translations/es-ES/data/reusables/actions/hosted-runner-configure-runner-group-access.md
similarity index 100%
rename from translations/es-ES/data/reusables/github-actions/hosted-runner-configure-runner-group-access.md
rename to translations/es-ES/data/reusables/actions/hosted-runner-configure-runner-group-access.md
diff --git a/translations/es-ES/data/reusables/github-actions/hosted-runner-labels-view-assigned-labels.md b/translations/es-ES/data/reusables/actions/hosted-runner-labels-view-assigned-labels.md
similarity index 100%
rename from translations/es-ES/data/reusables/github-actions/hosted-runner-labels-view-assigned-labels.md
rename to translations/es-ES/data/reusables/actions/hosted-runner-labels-view-assigned-labels.md
diff --git a/translations/es-ES/data/reusables/github-actions/hosted-runner-list-group.md b/translations/es-ES/data/reusables/actions/hosted-runner-list-group.md
similarity index 100%
rename from translations/es-ES/data/reusables/github-actions/hosted-runner-list-group.md
rename to translations/es-ES/data/reusables/actions/hosted-runner-list-group.md
diff --git a/translations/es-ES/data/reusables/github-actions/hosted-runner-list.md b/translations/es-ES/data/reusables/actions/hosted-runner-list.md
similarity index 100%
rename from translations/es-ES/data/reusables/github-actions/hosted-runner-list.md
rename to translations/es-ES/data/reusables/actions/hosted-runner-list.md
diff --git a/translations/es-ES/data/reusables/github-actions/invalid-workflow-files.md b/translations/es-ES/data/reusables/actions/invalid-workflow-files.md
similarity index 100%
rename from translations/es-ES/data/reusables/github-actions/invalid-workflow-files.md
rename to translations/es-ES/data/reusables/actions/invalid-workflow-files.md
diff --git a/translations/es-ES/data/reusables/actions/ip-allow-list-self-hosted-runners.md b/translations/es-ES/data/reusables/actions/ip-allow-list-self-hosted-runners.md
new file mode 100644
index 000000000000..9820a0e3cc7b
--- /dev/null
+++ b/translations/es-ES/data/reusables/actions/ip-allow-list-self-hosted-runners.md
@@ -0,0 +1,11 @@
+{% ifversion ghae %}
+Para permitir que los ejecutores auto-hospedados se comuniquen con {% data variables.product.prodname_dotcom %}, agrega la dirección o rango de direcciones IP de tus ejecutores auto-hospedados a la lista de IP permitidas. Para obtener más información, consulta "[Agregar una dirección IP permitida](#adding-an-allowed-ip-address)".
+{% else %}
+{% warning %}
+
+**Advertencia**: Si utilzas una lista de IP permitidas y también quisieras utilizar {% data variables.product.prodname_actions %}, debes usar los ejecutores auto-hospedados. Para obtener más información, consulta la sección "[Hospedar tus propios ejecutores](/actions/automating-your-workflow-with-github-actions/about-self-hosted-runners)".
+
+{% endwarning %}
+
+Para permitir que los ejecutores auto-hospedados se comuniquen con {% data variables.product.prodname_dotcom %}, agrega la dirección o rango de direcciones IP de tus ejecutores auto-hospedados a la lista de IP permitidas. Para obtener más información, consulta "[Agregar una dirección IP permitida](#adding-an-allowed-ip-address)".
+{% endif %}
diff --git a/translations/es-ES/data/reusables/github-actions/java-jvm-architecture.md b/translations/es-ES/data/reusables/actions/java-jvm-architecture.md
similarity index 100%
rename from translations/es-ES/data/reusables/github-actions/java-jvm-architecture.md
rename to translations/es-ES/data/reusables/actions/java-jvm-architecture.md
diff --git a/translations/es-ES/data/reusables/actions/jobs/section-assigning-permissions-to-jobs-specific.md b/translations/es-ES/data/reusables/actions/jobs/section-assigning-permissions-to-jobs-specific.md
index e3eb397cdb1d..8e95bb181577 100644
--- a/translations/es-ES/data/reusables/actions/jobs/section-assigning-permissions-to-jobs-specific.md
+++ b/translations/es-ES/data/reusables/actions/jobs/section-assigning-permissions-to-jobs-specific.md
@@ -2,8 +2,8 @@ Para un job específico, puedes utilizar `jobs..permissions` para modifi
Si especificas el permiso dentro de una definición de job, puedes configurar un conjunto diferente de permisos para el `GITHUB_TOKEN` de cada job, en caso de que se requiera. Como alternativa, puedes especificar los permisos para todos los jobs en el flujo de trabajo. Para obtener más información sobre los permisos que se definen a nivel del flujo de trabajo, consulta los [`permissions`](/actions/using-workflows/workflow-syntax-for-github-actions#permissions).
-{% data reusables.github-actions.github-token-available-permissions %}
-{% data reusables.github-actions.forked-write-permission %}
+{% data reusables.actions.github-token-available-permissions %}
+{% data reusables.actions.forked-write-permission %}
#### Example: Setting permissions for a specific job
diff --git a/translations/es-ES/data/reusables/actions/jobs/section-assigning-permissions-to-jobs.md b/translations/es-ES/data/reusables/actions/jobs/section-assigning-permissions-to-jobs.md
index 08ede72015b7..1d6c09be851d 100644
--- a/translations/es-ES/data/reusables/actions/jobs/section-assigning-permissions-to-jobs.md
+++ b/translations/es-ES/data/reusables/actions/jobs/section-assigning-permissions-to-jobs.md
@@ -2,8 +2,8 @@ You can use `permissions` to modify the default permissions granted to the `GITH
Puedes utilizar los `permissions` ya sea como una clave de nivel superior, para aplicar todos los jobs en el flujo de trabajo, o dentro de jobs específicos. Cuando agregas la clave `permissions` dentro de un job específico, todas las acciones y comandos de ejecución dentro de este que utilicen el `GITHUB_TOKEN` obtendrán los derechos de acceso que especificas. Para obtener más información, consulta los [`jobspermissions`](/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idpermissions).
-{% data reusables.github-actions.github-token-available-permissions %}
-{% data reusables.github-actions.forked-write-permission %}
+{% data reusables.actions.github-token-available-permissions %}
+{% data reusables.actions.forked-write-permission %}
### Example: Assigning permissions to GITHUB_TOKEN
diff --git a/translations/es-ES/data/reusables/actions/jobs/section-choosing-the-runner-for-a-job.md b/translations/es-ES/data/reusables/actions/jobs/section-choosing-the-runner-for-a-job.md
index 86270ccfccfd..cf2218dc7d61 100644
--- a/translations/es-ES/data/reusables/actions/jobs/section-choosing-the-runner-for-a-job.md
+++ b/translations/es-ES/data/reusables/actions/jobs/section-choosing-the-runner-for-a-job.md
@@ -10,7 +10,7 @@ Si usas un ejecutor alojado {% data variables.product.prodname_dotcom %}, cada t
Los tipos de ejecutores alojados {% data variables.product.prodname_dotcom %} disponibles son:
-{% data reusables.github-actions.supported-github-runners %}
+{% data reusables.actions.supported-github-runners %}
#### Example: Specifying an operating system
@@ -27,7 +27,7 @@ Para obtener más información, consulta "[Entornos virtuales para ejecutores al
{% data reusables.actions.ae-self-hosted-runners-notice %}
-{% data reusables.github-actions.self-hosted-runner-labels-runs-on %}
+{% data reusables.actions.self-hosted-runner-labels-runs-on %}
#### Example: Using labels for runner selection
diff --git a/translations/es-ES/data/reusables/actions/jobs/section-using-a-build-matrix-for-your-jobs-matrix.md b/translations/es-ES/data/reusables/actions/jobs/section-using-a-build-matrix-for-your-jobs-matrix.md
index 8c2513fb1c19..c1ee82c0c970 100644
--- a/translations/es-ES/data/reusables/actions/jobs/section-using-a-build-matrix-for-your-jobs-matrix.md
+++ b/translations/es-ES/data/reusables/actions/jobs/section-using-a-build-matrix-for-your-jobs-matrix.md
@@ -1,7 +1,7 @@
Use `jobs..strategy.matrix` to define a matrix of different job configurations. Una matriz te permite crear múltiples trabajos realizando la sustitución de variables en una definición de trabajo único. Por ejemplo, puedes usar una matriz para crear trabajos para más de una versión compatible de un lenguaje de programación, sistema operativo o herramienta. Una matriz reutiliza la configuración del trabajo y crea un trabajo para cada matriz que configuras.
-{% data reusables.github-actions.usage-matrix-limits %}
+{% data reusables.actions.usage-matrix-limits %}
Cada opción que definas en la `matriz` tiene una clave y un valor. Las claves que defines se convierten en propiedades en el contexto `matriz` y puedes hacer referencia a la propiedad en otras áreas de tu archivo de flujo de trabajo. Por ejemplo, si defines la clave `os` que contiene una matriz de sistemas operativos, puedes usar la propiedad `matrix.os` como el valor de la palabra clave `runs-on` para crear un trabajo para cada sistema operativo. Para obtener más información, consulta "[Contextos](/actions/learn-github-actions/contexts)".
@@ -123,4 +123,4 @@ strategy:
Puedes agregar variables de ambiente personalizadas para cada combinación de prueba si utilizas la clave `include`. Posteriormente, puedes referirte a las variables de ambiente personalizadas en un paso subsecuente.
-{% data reusables.github-actions.matrix-variable-example %}
+{% data reusables.actions.matrix-variable-example %}
diff --git a/translations/es-ES/data/reusables/actions/jobs/section-using-conditions-to-control-job-execution.md b/translations/es-ES/data/reusables/actions/jobs/section-using-conditions-to-control-job-execution.md
index 1eb2b0c97aeb..afd967f2f55d 100644
--- a/translations/es-ES/data/reusables/actions/jobs/section-using-conditions-to-control-job-execution.md
+++ b/translations/es-ES/data/reusables/actions/jobs/section-using-conditions-to-control-job-execution.md
@@ -1,6 +1,6 @@
You can use the `jobs..if` conditional to prevent a job from running unless a condition is met. Puedes usar cualquier contexto y expresión admitidos para crear un condicional.
-{% data reusables.github-actions.expression-syntax-if %} Para obtener más información, consulta la sección "[Expresiones](/actions/learn-github-actions/expressions)".
+{% data reusables.actions.expression-syntax-if %} Para obtener más información, consulta la sección "[Expresiones](/actions/learn-github-actions/expressions)".
### Example: Only run job for specific repository
diff --git a/translations/es-ES/data/reusables/actions/jobs/setting-default-values-for-jobs-defaults-job-run.md b/translations/es-ES/data/reusables/actions/jobs/setting-default-values-for-jobs-defaults-job-run.md
index ef90cfce9cef..5b05c619783d 100644
--- a/translations/es-ES/data/reusables/actions/jobs/setting-default-values-for-jobs-defaults-job-run.md
+++ b/translations/es-ES/data/reusables/actions/jobs/setting-default-values-for-jobs-defaults-job-run.md
@@ -2,7 +2,7 @@ Use `jobs..defaults.run` to provide default `shell` and `working-directo
Puedes proporcionar opciones predeterminadas de `shell` y `working-directory` para todos los pasos de [`run`](/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idstepsrun) en un job. También puedes configurar ajustes predeterminados para `run` para todo el flujo de trabajo. Para obtener más información, consulta [`jobs.defaults.run`](/actions/using-workflows/workflow-syntax-for-github-actions#defaultsrun). No podrás utilizar contextos o expresiones en esta palabra clave.
-{% data reusables.github-actions.defaults-override %}
+{% data reusables.actions.defaults-override %}
#### Example: Setting default `run` step options for a job
diff --git a/translations/es-ES/data/reusables/actions/jobs/setting-default-values-for-jobs-defaults-job.md b/translations/es-ES/data/reusables/actions/jobs/setting-default-values-for-jobs-defaults-job.md
index 6c8463f9ef0d..bc3f569ca982 100644
--- a/translations/es-ES/data/reusables/actions/jobs/setting-default-values-for-jobs-defaults-job.md
+++ b/translations/es-ES/data/reusables/actions/jobs/setting-default-values-for-jobs-defaults-job.md
@@ -1,3 +1,3 @@
Use `jobs..defaults` to create a `map` of default settings that will apply to all steps in the job. También puedes configurar ajustes predeterminados para todo el flujo de trabajo. Para obtener más información, consulta [`defaults`](/actions/using-workflows/workflow-syntax-for-github-actions#defaults).
-{% data reusables.github-actions.defaults-override %}
\ No newline at end of file
+{% data reusables.actions.defaults-override %}
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/actions/jobs/setting-default-values-for-jobs-defaults-run.md b/translations/es-ES/data/reusables/actions/jobs/setting-default-values-for-jobs-defaults-run.md
index b45486739cf1..24962bafb470 100644
--- a/translations/es-ES/data/reusables/actions/jobs/setting-default-values-for-jobs-defaults-run.md
+++ b/translations/es-ES/data/reusables/actions/jobs/setting-default-values-for-jobs-defaults-run.md
@@ -1,6 +1,6 @@
Puedes utilizar `defaults.run` para proporcionar opciones predeterminadas de `shell` y `working-directory` para todos los pasos de [`run`](/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idstepsrun) en un flujo de trabajo. También puedes configurar ajustes predeterminados para `run` que solo estén disponibles para un job. Para obtener más información, consulta [`jobs..defaults.run`](/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_iddefaultsrun). No podrás utilizar contextos o expresiones en esta palabra clave.
-{% data reusables.github-actions.defaults-override %}
+{% data reusables.actions.defaults-override %}
#### Ejemplo: Configurar el directorio de trabajo y shell predeterminados
diff --git a/translations/es-ES/data/reusables/actions/jobs/setting-default-values-for-jobs-defaults.md b/translations/es-ES/data/reusables/actions/jobs/setting-default-values-for-jobs-defaults.md
index f1a9e10dd1ae..f01a61105f1f 100644
--- a/translations/es-ES/data/reusables/actions/jobs/setting-default-values-for-jobs-defaults.md
+++ b/translations/es-ES/data/reusables/actions/jobs/setting-default-values-for-jobs-defaults.md
@@ -1,3 +1,3 @@
Use `defaults` to create a `map` of default settings that will apply to all jobs in the workflow. También puedes configurar los ajustes predeterminados que solo estén disponibles para un job. Para obtener más información, consulta la sección [`jobs..defaults`](/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_iddefaults).
-{% data reusables.github-actions.defaults-override %}
\ No newline at end of file
+{% data reusables.actions.defaults-override %}
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/github-actions/macos-runner-preview.md b/translations/es-ES/data/reusables/actions/macos-runner-preview.md
similarity index 100%
rename from translations/es-ES/data/reusables/github-actions/macos-runner-preview.md
rename to translations/es-ES/data/reusables/actions/macos-runner-preview.md
diff --git a/translations/es-ES/data/reusables/github-actions/matrix-variable-example.md b/translations/es-ES/data/reusables/actions/matrix-variable-example.md
similarity index 100%
rename from translations/es-ES/data/reusables/github-actions/matrix-variable-example.md
rename to translations/es-ES/data/reusables/actions/matrix-variable-example.md
diff --git a/translations/es-ES/data/reusables/github-actions/name-environment.md b/translations/es-ES/data/reusables/actions/name-environment.md
similarity index 100%
rename from translations/es-ES/data/reusables/github-actions/name-environment.md
rename to translations/es-ES/data/reusables/actions/name-environment.md
diff --git a/translations/es-ES/data/reusables/github-actions/new-environment.md b/translations/es-ES/data/reusables/actions/new-environment.md
similarity index 100%
rename from translations/es-ES/data/reusables/github-actions/new-environment.md
rename to translations/es-ES/data/reusables/actions/new-environment.md
diff --git a/translations/es-ES/data/reusables/github-actions/on-multiple-example.md b/translations/es-ES/data/reusables/actions/on-multiple-example.md
similarity index 100%
rename from translations/es-ES/data/reusables/github-actions/on-multiple-example.md
rename to translations/es-ES/data/reusables/actions/on-multiple-example.md
diff --git a/translations/es-ES/data/reusables/github-actions/on-single-example.md b/translations/es-ES/data/reusables/actions/on-single-example.md
similarity index 100%
rename from translations/es-ES/data/reusables/github-actions/on-single-example.md
rename to translations/es-ES/data/reusables/actions/on-single-example.md
diff --git a/translations/es-ES/data/reusables/github-actions/permissions-statement-environment.md b/translations/es-ES/data/reusables/actions/permissions-statement-environment.md
similarity index 100%
rename from translations/es-ES/data/reusables/github-actions/permissions-statement-environment.md
rename to translations/es-ES/data/reusables/actions/permissions-statement-environment.md
diff --git a/translations/es-ES/data/reusables/github-actions/permissions-statement-secrets-api.md b/translations/es-ES/data/reusables/actions/permissions-statement-secrets-api.md
similarity index 100%
rename from translations/es-ES/data/reusables/github-actions/permissions-statement-secrets-api.md
rename to translations/es-ES/data/reusables/actions/permissions-statement-secrets-api.md
diff --git a/translations/es-ES/data/reusables/github-actions/permissions-statement-secrets-environment.md b/translations/es-ES/data/reusables/actions/permissions-statement-secrets-environment.md
similarity index 100%
rename from translations/es-ES/data/reusables/github-actions/permissions-statement-secrets-environment.md
rename to translations/es-ES/data/reusables/actions/permissions-statement-secrets-environment.md
diff --git a/translations/es-ES/data/reusables/github-actions/permissions-statement-secrets-organization.md b/translations/es-ES/data/reusables/actions/permissions-statement-secrets-organization.md
similarity index 100%
rename from translations/es-ES/data/reusables/github-actions/permissions-statement-secrets-organization.md
rename to translations/es-ES/data/reusables/actions/permissions-statement-secrets-organization.md
diff --git a/translations/es-ES/data/reusables/github-actions/permissions-statement-secrets-repository.md b/translations/es-ES/data/reusables/actions/permissions-statement-secrets-repository.md
similarity index 100%
rename from translations/es-ES/data/reusables/github-actions/permissions-statement-secrets-repository.md
rename to translations/es-ES/data/reusables/actions/permissions-statement-secrets-repository.md
diff --git a/translations/es-ES/data/reusables/github-actions/postgres-environment-variables.md b/translations/es-ES/data/reusables/actions/postgres-environment-variables.md
similarity index 100%
rename from translations/es-ES/data/reusables/github-actions/postgres-environment-variables.md
rename to translations/es-ES/data/reusables/actions/postgres-environment-variables.md
diff --git a/translations/es-ES/data/reusables/github-actions/postgres-label-description.md b/translations/es-ES/data/reusables/actions/postgres-label-description.md
similarity index 100%
rename from translations/es-ES/data/reusables/github-actions/postgres-label-description.md
rename to translations/es-ES/data/reusables/actions/postgres-label-description.md
diff --git a/translations/es-ES/data/reusables/github-actions/private-repository-forks-configure.md b/translations/es-ES/data/reusables/actions/private-repository-forks-configure.md
similarity index 100%
rename from translations/es-ES/data/reusables/github-actions/private-repository-forks-configure.md
rename to translations/es-ES/data/reusables/actions/private-repository-forks-configure.md
diff --git a/translations/es-ES/data/reusables/github-actions/private-repository-forks-options.md b/translations/es-ES/data/reusables/actions/private-repository-forks-options.md
similarity index 100%
rename from translations/es-ES/data/reusables/github-actions/private-repository-forks-options.md
rename to translations/es-ES/data/reusables/actions/private-repository-forks-options.md
diff --git a/translations/es-ES/data/reusables/github-actions/private-repository-forks-overview.md b/translations/es-ES/data/reusables/actions/private-repository-forks-overview.md
similarity index 100%
rename from translations/es-ES/data/reusables/github-actions/private-repository-forks-overview.md
rename to translations/es-ES/data/reusables/actions/private-repository-forks-overview.md
diff --git a/translations/es-ES/data/reusables/github-actions/publish-to-maven-workflow-step.md b/translations/es-ES/data/reusables/actions/publish-to-maven-workflow-step.md
similarity index 100%
rename from translations/es-ES/data/reusables/github-actions/publish-to-maven-workflow-step.md
rename to translations/es-ES/data/reusables/actions/publish-to-maven-workflow-step.md
diff --git a/translations/es-ES/data/reusables/github-actions/publish-to-packages-workflow-step.md b/translations/es-ES/data/reusables/actions/publish-to-packages-workflow-step.md
similarity index 100%
rename from translations/es-ES/data/reusables/github-actions/publish-to-packages-workflow-step.md
rename to translations/es-ES/data/reusables/actions/publish-to-packages-workflow-step.md
diff --git a/translations/es-ES/data/reusables/github-actions/publishing-java-packages-intro.md b/translations/es-ES/data/reusables/actions/publishing-java-packages-intro.md
similarity index 100%
rename from translations/es-ES/data/reusables/github-actions/publishing-java-packages-intro.md
rename to translations/es-ES/data/reusables/actions/publishing-java-packages-intro.md
diff --git a/translations/es-ES/data/reusables/github-actions/pure-javascript.md b/translations/es-ES/data/reusables/actions/pure-javascript.md
similarity index 100%
rename from translations/es-ES/data/reusables/github-actions/pure-javascript.md
rename to translations/es-ES/data/reusables/actions/pure-javascript.md
diff --git a/translations/es-ES/data/reusables/github-actions/redis-environment-variables.md b/translations/es-ES/data/reusables/actions/redis-environment-variables.md
similarity index 100%
rename from translations/es-ES/data/reusables/github-actions/redis-environment-variables.md
rename to translations/es-ES/data/reusables/actions/redis-environment-variables.md
diff --git a/translations/es-ES/data/reusables/github-actions/redis-label-description.md b/translations/es-ES/data/reusables/actions/redis-label-description.md
similarity index 100%
rename from translations/es-ES/data/reusables/github-actions/redis-label-description.md
rename to translations/es-ES/data/reusables/actions/redis-label-description.md
diff --git a/translations/es-ES/data/reusables/github-actions/release-trigger-workflow.md b/translations/es-ES/data/reusables/actions/release-trigger-workflow.md
similarity index 100%
rename from translations/es-ES/data/reusables/github-actions/release-trigger-workflow.md
rename to translations/es-ES/data/reusables/actions/release-trigger-workflow.md
diff --git a/translations/es-ES/data/reusables/github-actions/run_id_description.md b/translations/es-ES/data/reusables/actions/run_id_description.md
similarity index 100%
rename from translations/es-ES/data/reusables/github-actions/run_id_description.md
rename to translations/es-ES/data/reusables/actions/run_id_description.md
diff --git a/translations/es-ES/data/reusables/github-actions/run_number_description.md b/translations/es-ES/data/reusables/actions/run_number_description.md
similarity index 100%
rename from translations/es-ES/data/reusables/github-actions/run_number_description.md
rename to translations/es-ES/data/reusables/actions/run_number_description.md
diff --git a/translations/es-ES/data/reusables/github-actions/runner-app-open-source.md b/translations/es-ES/data/reusables/actions/runner-app-open-source.md
similarity index 100%
rename from translations/es-ES/data/reusables/github-actions/runner-app-open-source.md
rename to translations/es-ES/data/reusables/actions/runner-app-open-source.md
diff --git a/translations/es-ES/data/reusables/github-actions/runner-group-assign-policy-org.md b/translations/es-ES/data/reusables/actions/runner-group-assign-policy-org.md
similarity index 100%
rename from translations/es-ES/data/reusables/github-actions/runner-group-assign-policy-org.md
rename to translations/es-ES/data/reusables/actions/runner-group-assign-policy-org.md
diff --git a/translations/es-ES/data/reusables/github-actions/runner-group-assign-policy-repo.md b/translations/es-ES/data/reusables/actions/runner-group-assign-policy-repo.md
similarity index 100%
rename from translations/es-ES/data/reusables/github-actions/runner-group-assign-policy-repo.md
rename to translations/es-ES/data/reusables/actions/runner-group-assign-policy-repo.md
diff --git a/translations/es-ES/data/reusables/github-actions/runner-label-settings.md b/translations/es-ES/data/reusables/actions/runner-label-settings.md
similarity index 100%
rename from translations/es-ES/data/reusables/github-actions/runner-label-settings.md
rename to translations/es-ES/data/reusables/actions/runner-label-settings.md
diff --git a/translations/es-ES/data/reusables/github-actions/runner-workflow-continuity.md b/translations/es-ES/data/reusables/actions/runner-workflow-continuity.md
similarity index 100%
rename from translations/es-ES/data/reusables/github-actions/runner-workflow-continuity.md
rename to translations/es-ES/data/reusables/actions/runner-workflow-continuity.md
diff --git a/translations/es-ES/data/reusables/github-actions/secrets-org-level-overview.md b/translations/es-ES/data/reusables/actions/secrets-org-level-overview.md
similarity index 100%
rename from translations/es-ES/data/reusables/github-actions/secrets-org-level-overview.md
rename to translations/es-ES/data/reusables/actions/secrets-org-level-overview.md
diff --git a/translations/es-ES/data/reusables/github-actions/secrets-redaction-warning.md b/translations/es-ES/data/reusables/actions/secrets-redaction-warning.md
similarity index 100%
rename from translations/es-ES/data/reusables/github-actions/secrets-redaction-warning.md
rename to translations/es-ES/data/reusables/actions/secrets-redaction-warning.md
diff --git a/translations/es-ES/data/reusables/github-actions/self-hosted-runner-auto-removal.md b/translations/es-ES/data/reusables/actions/self-hosted-runner-auto-removal.md
similarity index 100%
rename from translations/es-ES/data/reusables/github-actions/self-hosted-runner-auto-removal.md
rename to translations/es-ES/data/reusables/actions/self-hosted-runner-auto-removal.md
diff --git a/translations/es-ES/data/reusables/github-actions/self-hosted-runner-check-installation-success.md b/translations/es-ES/data/reusables/actions/self-hosted-runner-check-installation-success.md
similarity index 91%
rename from translations/es-ES/data/reusables/github-actions/self-hosted-runner-check-installation-success.md
rename to translations/es-ES/data/reusables/actions/self-hosted-runner-check-installation-success.md
index dbd662838190..0174d0c7f922 100644
--- a/translations/es-ES/data/reusables/github-actions/self-hosted-runner-check-installation-success.md
+++ b/translations/es-ES/data/reusables/actions/self-hosted-runner-check-installation-success.md
@@ -5,6 +5,6 @@ Después de completar estos pasos para agregar un ejecutor auto-hospedado, dicho
La aplicación del ejecutor autoalojado debe estar activa para que el ejecutor acepte trabajos. Cuando la aplicación del ejecutor está conectada a {% data variables.product.product_name %} y lista para recibir trabajos, verás el siguiente mensaje en la terminal de la máquina.
-{% data reusables.github-actions.self-hosted-runner-connected-output %}
+{% data reusables.actions.self-hosted-runner-connected-output %}
Para obtener más información, consulta la sección "[Monitorear y solucionar problemas de los ejecutores auto-hospedados](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners)".
diff --git a/translations/es-ES/data/reusables/github-actions/self-hosted-runner-check-mac-linux.md b/translations/es-ES/data/reusables/actions/self-hosted-runner-check-mac-linux.md
similarity index 100%
rename from translations/es-ES/data/reusables/github-actions/self-hosted-runner-check-mac-linux.md
rename to translations/es-ES/data/reusables/actions/self-hosted-runner-check-mac-linux.md
diff --git a/translations/es-ES/data/reusables/github-actions/self-hosted-runner-configure-runner-group-access.md b/translations/es-ES/data/reusables/actions/self-hosted-runner-configure-runner-group-access.md
similarity index 90%
rename from translations/es-ES/data/reusables/github-actions/self-hosted-runner-configure-runner-group-access.md
rename to translations/es-ES/data/reusables/actions/self-hosted-runner-configure-runner-group-access.md
index 78fd73c235c0..0662b9ec3a76 100644
--- a/translations/es-ES/data/reusables/github-actions/self-hosted-runner-configure-runner-group-access.md
+++ b/translations/es-ES/data/reusables/actions/self-hosted-runner-configure-runner-group-access.md
@@ -6,7 +6,7 @@
**Advertencia**
- {% indented_data_reference reusables.github-actions.self-hosted-runner-security spaces=3 %}
+ {% indented_data_reference reusables.actions.self-hosted-runner-security spaces=3 %}
Para obtener más información, consulta "[Acerca de los ejecutores autoalojados](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)."
diff --git a/translations/es-ES/data/reusables/github-actions/self-hosted-runner-configure.md b/translations/es-ES/data/reusables/actions/self-hosted-runner-configure.md
similarity index 100%
rename from translations/es-ES/data/reusables/github-actions/self-hosted-runner-configure.md
rename to translations/es-ES/data/reusables/actions/self-hosted-runner-configure.md
diff --git a/translations/es-ES/data/reusables/github-actions/self-hosted-runner-connected-output.md b/translations/es-ES/data/reusables/actions/self-hosted-runner-connected-output.md
similarity index 100%
rename from translations/es-ES/data/reusables/github-actions/self-hosted-runner-connected-output.md
rename to translations/es-ES/data/reusables/actions/self-hosted-runner-connected-output.md
diff --git a/translations/es-ES/data/reusables/github-actions/self-hosted-runner-create-group.md b/translations/es-ES/data/reusables/actions/self-hosted-runner-create-group.md
similarity index 100%
rename from translations/es-ES/data/reusables/github-actions/self-hosted-runner-create-group.md
rename to translations/es-ES/data/reusables/actions/self-hosted-runner-create-group.md
diff --git a/translations/es-ES/data/reusables/github-actions/self-hosted-runner-description.md b/translations/es-ES/data/reusables/actions/self-hosted-runner-description.md
similarity index 100%
rename from translations/es-ES/data/reusables/github-actions/self-hosted-runner-description.md
rename to translations/es-ES/data/reusables/actions/self-hosted-runner-description.md
diff --git a/translations/es-ES/data/reusables/github-actions/self-hosted-runner-groups-navigate-to-repo-org-enterprise.md b/translations/es-ES/data/reusables/actions/self-hosted-runner-groups-navigate-to-repo-org-enterprise.md
similarity index 100%
rename from translations/es-ES/data/reusables/github-actions/self-hosted-runner-groups-navigate-to-repo-org-enterprise.md
rename to translations/es-ES/data/reusables/actions/self-hosted-runner-groups-navigate-to-repo-org-enterprise.md
diff --git a/translations/es-ES/data/reusables/github-actions/self-hosted-runner-labels-runs-on.md b/translations/es-ES/data/reusables/actions/self-hosted-runner-labels-runs-on.md
similarity index 100%
rename from translations/es-ES/data/reusables/github-actions/self-hosted-runner-labels-runs-on.md
rename to translations/es-ES/data/reusables/actions/self-hosted-runner-labels-runs-on.md
diff --git a/translations/es-ES/data/reusables/github-actions/self-hosted-runner-labels-view-assigned-labels.md b/translations/es-ES/data/reusables/actions/self-hosted-runner-labels-view-assigned-labels.md
similarity index 100%
rename from translations/es-ES/data/reusables/github-actions/self-hosted-runner-labels-view-assigned-labels.md
rename to translations/es-ES/data/reusables/actions/self-hosted-runner-labels-view-assigned-labels.md
diff --git a/translations/es-ES/data/reusables/github-actions/self-hosted-runner-list-group.md b/translations/es-ES/data/reusables/actions/self-hosted-runner-list-group.md
similarity index 100%
rename from translations/es-ES/data/reusables/github-actions/self-hosted-runner-list-group.md
rename to translations/es-ES/data/reusables/actions/self-hosted-runner-list-group.md
diff --git a/translations/es-ES/data/reusables/github-actions/self-hosted-runner-list.md b/translations/es-ES/data/reusables/actions/self-hosted-runner-list.md
similarity index 100%
rename from translations/es-ES/data/reusables/github-actions/self-hosted-runner-list.md
rename to translations/es-ES/data/reusables/actions/self-hosted-runner-list.md
diff --git a/translations/es-ES/data/reusables/github-actions/self-hosted-runner-management-permissions-required.md b/translations/es-ES/data/reusables/actions/self-hosted-runner-management-permissions-required.md
similarity index 100%
rename from translations/es-ES/data/reusables/github-actions/self-hosted-runner-management-permissions-required.md
rename to translations/es-ES/data/reusables/actions/self-hosted-runner-management-permissions-required.md
diff --git a/translations/es-ES/data/reusables/github-actions/self-hosted-runner-navigate-repo-and-org.md b/translations/es-ES/data/reusables/actions/self-hosted-runner-navigate-repo-and-org.md
similarity index 100%
rename from translations/es-ES/data/reusables/github-actions/self-hosted-runner-navigate-repo-and-org.md
rename to translations/es-ES/data/reusables/actions/self-hosted-runner-navigate-repo-and-org.md
diff --git a/translations/es-ES/data/reusables/github-actions/self-hosted-runner-navigate-to-org-enterprise.md b/translations/es-ES/data/reusables/actions/self-hosted-runner-navigate-to-org-enterprise.md
similarity index 100%
rename from translations/es-ES/data/reusables/github-actions/self-hosted-runner-navigate-to-org-enterprise.md
rename to translations/es-ES/data/reusables/actions/self-hosted-runner-navigate-to-org-enterprise.md
diff --git a/translations/es-ES/data/reusables/github-actions/self-hosted-runner-navigate-to-repo-org-enterprise.md b/translations/es-ES/data/reusables/actions/self-hosted-runner-navigate-to-repo-org-enterprise.md
similarity index 100%
rename from translations/es-ES/data/reusables/github-actions/self-hosted-runner-navigate-to-repo-org-enterprise.md
rename to translations/es-ES/data/reusables/actions/self-hosted-runner-navigate-to-repo-org-enterprise.md
diff --git a/translations/es-ES/data/reusables/github-actions/self-hosted-runner-public-repo-access.md b/translations/es-ES/data/reusables/actions/self-hosted-runner-public-repo-access.md
similarity index 100%
rename from translations/es-ES/data/reusables/github-actions/self-hosted-runner-public-repo-access.md
rename to translations/es-ES/data/reusables/actions/self-hosted-runner-public-repo-access.md
diff --git a/translations/es-ES/data/reusables/github-actions/self-hosted-runner-removal-impact.md b/translations/es-ES/data/reusables/actions/self-hosted-runner-removal-impact.md
similarity index 100%
rename from translations/es-ES/data/reusables/github-actions/self-hosted-runner-removal-impact.md
rename to translations/es-ES/data/reusables/actions/self-hosted-runner-removal-impact.md
diff --git a/translations/es-ES/data/reusables/github-actions/self-hosted-runner-removing-a-runner-updated.md b/translations/es-ES/data/reusables/actions/self-hosted-runner-removing-a-runner-updated.md
similarity index 100%
rename from translations/es-ES/data/reusables/github-actions/self-hosted-runner-removing-a-runner-updated.md
rename to translations/es-ES/data/reusables/actions/self-hosted-runner-removing-a-runner-updated.md
diff --git a/translations/es-ES/data/reusables/github-actions/self-hosted-runner-removing-a-runner.md b/translations/es-ES/data/reusables/actions/self-hosted-runner-removing-a-runner.md
similarity index 100%
rename from translations/es-ES/data/reusables/github-actions/self-hosted-runner-removing-a-runner.md
rename to translations/es-ES/data/reusables/actions/self-hosted-runner-removing-a-runner.md
diff --git a/translations/es-ES/data/reusables/github-actions/self-hosted-runner-reqs-docker.md b/translations/es-ES/data/reusables/actions/self-hosted-runner-reqs-docker.md
similarity index 100%
rename from translations/es-ES/data/reusables/github-actions/self-hosted-runner-reqs-docker.md
rename to translations/es-ES/data/reusables/actions/self-hosted-runner-reqs-docker.md
diff --git a/translations/es-ES/data/reusables/github-actions/self-hosted-runner-reusing.md b/translations/es-ES/data/reusables/actions/self-hosted-runner-reusing.md
similarity index 100%
rename from translations/es-ES/data/reusables/github-actions/self-hosted-runner-reusing.md
rename to translations/es-ES/data/reusables/actions/self-hosted-runner-reusing.md
diff --git a/translations/es-ES/data/reusables/github-actions/self-hosted-runner-security.md b/translations/es-ES/data/reusables/actions/self-hosted-runner-security.md
similarity index 100%
rename from translations/es-ES/data/reusables/github-actions/self-hosted-runner-security.md
rename to translations/es-ES/data/reusables/actions/self-hosted-runner-security.md
diff --git a/translations/es-ES/data/reusables/github-actions/service-container-add-script.md b/translations/es-ES/data/reusables/actions/service-container-add-script.md
similarity index 100%
rename from translations/es-ES/data/reusables/github-actions/service-container-add-script.md
rename to translations/es-ES/data/reusables/actions/service-container-add-script.md
diff --git a/translations/es-ES/data/reusables/github-actions/service-container-host-runner.md b/translations/es-ES/data/reusables/actions/service-container-host-runner.md
similarity index 100%
rename from translations/es-ES/data/reusables/github-actions/service-container-host-runner.md
rename to translations/es-ES/data/reusables/actions/service-container-host-runner.md
diff --git a/translations/es-ES/data/reusables/github-actions/service-container-host.md b/translations/es-ES/data/reusables/actions/service-container-host.md
similarity index 100%
rename from translations/es-ES/data/reusables/github-actions/service-container-host.md
rename to translations/es-ES/data/reusables/actions/service-container-host.md
diff --git a/translations/es-ES/data/reusables/github-actions/service-container-localhost.md b/translations/es-ES/data/reusables/actions/service-container-localhost.md
similarity index 100%
rename from translations/es-ES/data/reusables/github-actions/service-container-localhost.md
rename to translations/es-ES/data/reusables/actions/service-container-localhost.md
diff --git a/translations/es-ES/data/reusables/github-actions/service-container-prereqs.md b/translations/es-ES/data/reusables/actions/service-container-prereqs.md
similarity index 100%
rename from translations/es-ES/data/reusables/github-actions/service-container-prereqs.md
rename to translations/es-ES/data/reusables/actions/service-container-prereqs.md
diff --git a/translations/es-ES/data/reusables/github-actions/service-template-steps.md b/translations/es-ES/data/reusables/actions/service-template-steps.md
similarity index 100%
rename from translations/es-ES/data/reusables/github-actions/service-template-steps.md
rename to translations/es-ES/data/reusables/actions/service-template-steps.md
diff --git a/translations/es-ES/data/reusables/github-actions/settings-sidebar-actions-runner-groups-selection.md b/translations/es-ES/data/reusables/actions/settings-sidebar-actions-runner-groups-selection.md
similarity index 100%
rename from translations/es-ES/data/reusables/github-actions/settings-sidebar-actions-runner-groups-selection.md
rename to translations/es-ES/data/reusables/actions/settings-sidebar-actions-runner-groups-selection.md
diff --git a/translations/es-ES/data/reusables/github-actions/settings-sidebar-actions-runner-groups.md b/translations/es-ES/data/reusables/actions/settings-sidebar-actions-runner-groups.md
similarity index 100%
rename from translations/es-ES/data/reusables/github-actions/settings-sidebar-actions-runner-groups.md
rename to translations/es-ES/data/reusables/actions/settings-sidebar-actions-runner-groups.md
diff --git a/translations/es-ES/data/reusables/github-actions/settings-sidebar-actions-runner-selection.md b/translations/es-ES/data/reusables/actions/settings-sidebar-actions-runner-selection.md
similarity index 100%
rename from translations/es-ES/data/reusables/github-actions/settings-sidebar-actions-runner-selection.md
rename to translations/es-ES/data/reusables/actions/settings-sidebar-actions-runner-selection.md
diff --git a/translations/es-ES/data/reusables/github-actions/settings-sidebar-actions-runners-updated.md b/translations/es-ES/data/reusables/actions/settings-sidebar-actions-runners-updated.md
similarity index 100%
rename from translations/es-ES/data/reusables/github-actions/settings-sidebar-actions-runners-updated.md
rename to translations/es-ES/data/reusables/actions/settings-sidebar-actions-runners-updated.md
diff --git a/translations/es-ES/data/reusables/github-actions/settings-sidebar-actions-runners.md b/translations/es-ES/data/reusables/actions/settings-sidebar-actions-runners.md
similarity index 100%
rename from translations/es-ES/data/reusables/github-actions/settings-sidebar-actions-runners.md
rename to translations/es-ES/data/reusables/actions/settings-sidebar-actions-runners.md
diff --git a/translations/es-ES/data/reusables/github-actions/settings-sidebar-actions.md b/translations/es-ES/data/reusables/actions/settings-sidebar-actions.md
similarity index 100%
rename from translations/es-ES/data/reusables/github-actions/settings-sidebar-actions.md
rename to translations/es-ES/data/reusables/actions/settings-sidebar-actions.md
diff --git a/translations/es-ES/data/reusables/github-actions/setup-node-intro.md b/translations/es-ES/data/reusables/actions/setup-node-intro.md
similarity index 100%
rename from translations/es-ES/data/reusables/github-actions/setup-node-intro.md
rename to translations/es-ES/data/reusables/actions/setup-node-intro.md
diff --git a/translations/es-ES/data/reusables/github-actions/sidebar-environment.md b/translations/es-ES/data/reusables/actions/sidebar-environment.md
similarity index 100%
rename from translations/es-ES/data/reusables/github-actions/sidebar-environment.md
rename to translations/es-ES/data/reusables/actions/sidebar-environment.md
diff --git a/translations/es-ES/data/reusables/github-actions/sidebar-secret.md b/translations/es-ES/data/reusables/actions/sidebar-secret.md
similarity index 100%
rename from translations/es-ES/data/reusables/github-actions/sidebar-secret.md
rename to translations/es-ES/data/reusables/actions/sidebar-secret.md
diff --git a/translations/es-ES/data/reusables/github-actions/supported-github-runners.md b/translations/es-ES/data/reusables/actions/supported-github-runners.md
similarity index 93%
rename from translations/es-ES/data/reusables/github-actions/supported-github-runners.md
rename to translations/es-ES/data/reusables/actions/supported-github-runners.md
index e1b40c572ef3..9077576c213f 100644
--- a/translations/es-ES/data/reusables/github-actions/supported-github-runners.md
+++ b/translations/es-ES/data/reusables/actions/supported-github-runners.md
@@ -12,10 +12,10 @@
Windows Server 2022
-windows-2022
+windows-latest o windows-2022
-La etiqueta de windows-latest actualmente utiliza la imagen de ejecutor de Windows Server 2019.
+La etiqueta de windows-latest actualmente utiliza la imagen de ejecutor de Windows Server 2022.
@@ -23,7 +23,7 @@ La etiqueta de windows-latest actualmente utiliza la imagen de ejec
Windows Server 2019
-windows-latest o windows-2019
+windows-2019
diff --git a/translations/es-ES/data/reusables/github-actions/usage-api-requests.md b/translations/es-ES/data/reusables/actions/usage-api-requests.md
similarity index 100%
rename from translations/es-ES/data/reusables/github-actions/usage-api-requests.md
rename to translations/es-ES/data/reusables/actions/usage-api-requests.md
diff --git a/translations/es-ES/data/reusables/actions/usage-matrix-limits.md b/translations/es-ES/data/reusables/actions/usage-matrix-limits.md
new file mode 100644
index 000000000000..548e5d7b17c6
--- /dev/null
+++ b/translations/es-ES/data/reusables/actions/usage-matrix-limits.md
@@ -0,0 +1 @@
+Una matriz de jobs puede generar un máximo de 256 jobs por ejecución de flujo de trabajo. Este límite también aplica a los ejecutores auto-hospedados.
diff --git a/translations/es-ES/data/reusables/github-actions/usage-workflow-queue-limits.md b/translations/es-ES/data/reusables/actions/usage-workflow-queue-limits.md
similarity index 100%
rename from translations/es-ES/data/reusables/github-actions/usage-workflow-queue-limits.md
rename to translations/es-ES/data/reusables/actions/usage-workflow-queue-limits.md
diff --git a/translations/es-ES/data/reusables/github-actions/usage-workflow-run-time.md b/translations/es-ES/data/reusables/actions/usage-workflow-run-time.md
similarity index 100%
rename from translations/es-ES/data/reusables/github-actions/usage-workflow-run-time.md
rename to translations/es-ES/data/reusables/actions/usage-workflow-run-time.md
diff --git a/translations/es-ES/data/reusables/github-actions/using-context-or-environment-variables.md b/translations/es-ES/data/reusables/actions/using-context-or-environment-variables.md
similarity index 100%
rename from translations/es-ES/data/reusables/github-actions/using-context-or-environment-variables.md
rename to translations/es-ES/data/reusables/actions/using-context-or-environment-variables.md
diff --git a/translations/es-ES/data/reusables/github-actions/workflow-dispatch-inputs.md b/translations/es-ES/data/reusables/actions/workflow-dispatch-inputs.md
similarity index 100%
rename from translations/es-ES/data/reusables/github-actions/workflow-dispatch-inputs.md
rename to translations/es-ES/data/reusables/actions/workflow-dispatch-inputs.md
diff --git a/translations/es-ES/data/reusables/github-actions/workflow-permissions-intro.md b/translations/es-ES/data/reusables/actions/workflow-permissions-intro.md
similarity index 100%
rename from translations/es-ES/data/reusables/github-actions/workflow-permissions-intro.md
rename to translations/es-ES/data/reusables/actions/workflow-permissions-intro.md
diff --git a/translations/es-ES/data/reusables/github-actions/workflow-permissions-modifying.md b/translations/es-ES/data/reusables/actions/workflow-permissions-modifying.md
similarity index 100%
rename from translations/es-ES/data/reusables/github-actions/workflow-permissions-modifying.md
rename to translations/es-ES/data/reusables/actions/workflow-permissions-modifying.md
diff --git a/translations/es-ES/data/reusables/github-actions/workflows-from-public-fork-setting.md b/translations/es-ES/data/reusables/actions/workflows-from-public-fork-setting.md
similarity index 100%
rename from translations/es-ES/data/reusables/github-actions/workflows-from-public-fork-setting.md
rename to translations/es-ES/data/reusables/actions/workflows-from-public-fork-setting.md
diff --git a/translations/es-ES/data/reusables/actions/workflows/section-triggering-a-workflow.md b/translations/es-ES/data/reusables/actions/workflows/section-triggering-a-workflow.md
index 2114bfe1a741..f7542c3fb7c3 100644
--- a/translations/es-ES/data/reusables/actions/workflows/section-triggering-a-workflow.md
+++ b/translations/es-ES/data/reusables/actions/workflows/section-triggering-a-workflow.md
@@ -3,4 +3,4 @@ To automatically trigger a workflow, use `on` to define which events can cause t
You can define single or multiple events that can a trigger workflow, or set a time schedule. You can also restrict the execution of a workflow to only occur for specific files, tags, or branch changes. Estas opciones se describen en las siguietnes secciones.
-{% data reusables.github-actions.actions-on-examples %}
+{% data reusables.actions.actions-on-examples %}
diff --git a/translations/es-ES/data/reusables/github-actions/actions-on-examples.md b/translations/es-ES/data/reusables/github-actions/actions-on-examples.md
deleted file mode 100644
index 168e9c9ce547..000000000000
--- a/translations/es-ES/data/reusables/github-actions/actions-on-examples.md
+++ /dev/null
@@ -1,19 +0,0 @@
-### Utilizar un evento simple
-
-{% data reusables.github-actions.on-single-example %}
-
-### Utilizar eventos múltiples
-
-{% data reusables.github-actions.on-multiple-example %}
-
-### Utilizar tipos de actividad
-
-{% data reusables.github-actions.actions-activity-types %}
-
-### Utilizar filtros
-
-{% data reusables.github-actions.actions-filters %}
-
-### Utilizar los tipos de actividad y filtros con eventos múltiples
-
-{% data reusables.github-actions.actions-multiple-types %}
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/github-actions/ip-allow-list-self-hosted-runners.md b/translations/es-ES/data/reusables/github-actions/ip-allow-list-self-hosted-runners.md
deleted file mode 100644
index ed15a5ea5999..000000000000
--- a/translations/es-ES/data/reusables/github-actions/ip-allow-list-self-hosted-runners.md
+++ /dev/null
@@ -1,13 +0,0 @@
-{% ifversion ghae %}
-Para permitir que tus ejecutores auto-hospedados se comuniquen con
-{% data variables.product.prodname_dotcom %}, agrega la dirección o rango de direcciones IP de tus ejecutores auto-hospedados a la lista de IP permitidas. Para obtener más información, consulta "[Agregar una dirección IP permitida](#adding-an-allowed-ip-address)".
-{% else %}
-{% warning %}
-
-**Advertencia**: Si utilzas una lista de IP permitidas y también quisieras utilizar {% data variables.product.prodname_actions %}, debes usar los ejecutores auto-hospedados. Para obtener más información, consulta la sección "[Hospedar tus propios ejecutores](/actions/automating-your-workflow-with-github-actions/about-self-hosted-runners)".
-
-{% endwarning %}
-Para permitir que tus ejecutores auto-hospedados se comuniquen con
-
-{% data variables.product.prodname_dotcom %}, agrega la dirección o rango de direcciones IP de tus ejecutores auto-hospedados a la lista de IP permitidas. Para obtener más información, consulta "[Agregar una dirección IP permitida](#adding-an-allowed-ip-address)".
-{% endif %}
diff --git a/translations/es-ES/data/reusables/github-actions/usage-matrix-limits.md b/translations/es-ES/data/reusables/github-actions/usage-matrix-limits.md
deleted file mode 100644
index b9650b6e473d..000000000000
--- a/translations/es-ES/data/reusables/github-actions/usage-matrix-limits.md
+++ /dev/null
@@ -1 +0,0 @@
-Una matriz de jobs puede generar un máximo de 256 jobs por ejecución de flujo de trabajo. Este límite también aplica para los ejecutores auto-hospedados.
diff --git a/translations/es-ES/data/reusables/repositories/navigate-to-commit-page.md b/translations/es-ES/data/reusables/repositories/navigate-to-commit-page.md
new file mode 100644
index 000000000000..bec770c79066
--- /dev/null
+++ b/translations/es-ES/data/reusables/repositories/navigate-to-commit-page.md
@@ -0,0 +1 @@
+1. On the main page of the repository, click the commits to navigate to the commits page. 
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/rest-reference/actions/actions.md b/translations/es-ES/data/reusables/rest-reference/actions/actions.md
new file mode 100644
index 000000000000..ed311bab6b59
--- /dev/null
+++ b/translations/es-ES/data/reusables/rest-reference/actions/actions.md
@@ -0,0 +1 @@
+La API de {% data variables.product.prodname_actions %} te permite administrar las {% data variables.product.prodname_actions %} utilizando la API de REST. La {% data reusables.actions.actions-authentication %} de las {% data variables.product.prodname_github_apps %} requieren los permisos que se mencionan en cada terminal. Para obtener más información, consulta la sección "[Documentación de {% data variables.product.prodname_actions %}](/actions)".
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/rest-reference/actions/artifacts.md b/translations/es-ES/data/reusables/rest-reference/actions/artifacts.md
new file mode 100644
index 000000000000..399aea71c98e
--- /dev/null
+++ b/translations/es-ES/data/reusables/rest-reference/actions/artifacts.md
@@ -0,0 +1,5 @@
+## Artefactos
+
+La API de Artefactos te permite descargar, borrar y recuperar información acerca de los artefactos de los flujos de trabajo. {% data reusables.actions.about-artifacts %} Para obtener más información, consulta la sección "[Conservar datos de flujo de trabajo mediante artefactos](/actions/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)".
+
+{% data reusables.actions.actions-authentication %} {% data reusables.actions.actions-app-actions-permissions-api %}
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/rest-reference/actions/permissions.md b/translations/es-ES/data/reusables/rest-reference/actions/permissions.md
new file mode 100644
index 000000000000..dd2ef2012ff6
--- /dev/null
+++ b/translations/es-ES/data/reusables/rest-reference/actions/permissions.md
@@ -0,0 +1,3 @@
+## Permisos
+
+La API de permisos te permite configurar permisos para determinar qué empresas, organizaciones y repositorios pueden ejecutar {% data variables.product.prodname_actions %} y qué acciones pueden ejecutarse. {% ifversion fpt or ghec or ghes %} Para obtener más información, consulta la sección "[Límites de uso, facturación y administración](/actions/reference/usage-limits-billing-and-administration#disabling-or-limiting-github-actions-for-your-repository-or-organization)".{% endif %}
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/rest-reference/actions/secrets.md b/translations/es-ES/data/reusables/rest-reference/actions/secrets.md
new file mode 100644
index 000000000000..71a3592673e6
--- /dev/null
+++ b/translations/es-ES/data/reusables/rest-reference/actions/secrets.md
@@ -0,0 +1,5 @@
+## Secretos
+
+La API de Secretos te permite crear, actualizar, borrar y recuperar información acerca de los secretos cifrados. {% data reusables.actions.about-secrets %} Para obtener más información, consulta la sección "[Crear y utilizar secretos cifrados](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)".
+
+La {% data reusables.actions.actions-authentication %} en las {% data variables.product.prodname_github_apps %} debe contar con el permiso de `secrets` para utilizar esta API. Los usuarios autenticados deben tener acceso de colaborador en el repositorio para crear, actualizar o leer los secretos.
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/rest-reference/actions/self-hosted-runner-groups.md b/translations/es-ES/data/reusables/rest-reference/actions/self-hosted-runner-groups.md
new file mode 100644
index 000000000000..885b70b69d93
--- /dev/null
+++ b/translations/es-ES/data/reusables/rest-reference/actions/self-hosted-runner-groups.md
@@ -0,0 +1,7 @@
+## Grupos de ejecutores auto-hospedados
+
+{% data reusables.actions.ae-self-hosted-runners-notice %}
+
+La API de Grupos de Ejecutores Auto-Hospedados te permite administrar grupos para los ejecutores auto-hospedados. Para obtener más información, consulta la sección "[Administrar el acceso a los ejecutores auto-hospedados](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups)".
+
+La {% data reusables.actions.actions-authentication %} en las {% data variables.product.prodname_github_apps %} debe contar con el permiso de `administration` para los repositorios o aquél de `organization_self_hosted_runners` para las organizaciones. Los usuarios autenticados deben contar con acceso administrativo a los repositorios u organizaciones o con el alcance de `manage_runners:enterprise` para empresas si quieren utilizar esta API.
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/rest-reference/actions/self-hosted-runners.md b/translations/es-ES/data/reusables/rest-reference/actions/self-hosted-runners.md
new file mode 100644
index 000000000000..f3957522aa7d
--- /dev/null
+++ b/translations/es-ES/data/reusables/rest-reference/actions/self-hosted-runners.md
@@ -0,0 +1,7 @@
+## Ejecutores autoalojados
+
+{% data reusables.actions.ae-self-hosted-runners-notice %}
+
+La API de Ejecutores auto-hospedados te permite registrar, ver, y borrar estos ejecutores. {% data reusables.actions.about-self-hosted-runners %} Para obtener más información, consulta "[Alojar tus propios ejecutores](/actions/hosting-your-own-runners)".
+
+La {% data reusables.actions.actions-authentication %} en las {% data variables.product.prodname_github_apps %} debe contar con el permiso de `administration` para los repositorios o aquél de `organization_self_hosted_runners` para las organizaciones. Los usuarios autenticados deben contar con acceso administrativo a los repositorios u organizaciones o con el alcance de `manage_runners:enterprise` para empresas si quieren utilizar esta API.
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/rest-reference/actions/workflow-jobs.md b/translations/es-ES/data/reusables/rest-reference/actions/workflow-jobs.md
new file mode 100644
index 000000000000..65ffd6b167a6
--- /dev/null
+++ b/translations/es-ES/data/reusables/rest-reference/actions/workflow-jobs.md
@@ -0,0 +1,5 @@
+## Jobs de los flujos de trabajo
+
+La API de Jobs de Flujos de Trabajo te permite ver las bitácoras y los jobs de un flujo de trabajo. {% data reusables.actions.about-workflow-jobs %} Para obtener más información, consulta la sección "[Sintaxis de flujode trabajo para GitHub Actions](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions)".
+
+{% data reusables.actions.actions-authentication %} {% data reusables.actions.actions-app-actions-permissions-api %}
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/rest-reference/actions/workflow-runs.md b/translations/es-ES/data/reusables/rest-reference/actions/workflow-runs.md
new file mode 100644
index 000000000000..0f38e2b7a2d9
--- /dev/null
+++ b/translations/es-ES/data/reusables/rest-reference/actions/workflow-runs.md
@@ -0,0 +1,5 @@
+## Workflow runs
+
+The Workflow Runs API allows you to view, re-run, cancel, and view logs for workflow runs. {% data reusables.actions.about-workflow-runs %} For more information, see "[Managing a workflow run](/actions/automating-your-workflow-with-github-actions/managing-a-workflow-run)."
+
+{% data reusables.actions.actions-authentication %} {% data reusables.actions.actions-app-actions-permissions-api %}
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/rest-reference/actions/workflows.md b/translations/es-ES/data/reusables/rest-reference/actions/workflows.md
new file mode 100644
index 000000000000..03a8b65ce696
--- /dev/null
+++ b/translations/es-ES/data/reusables/rest-reference/actions/workflows.md
@@ -0,0 +1,5 @@
+## Flujos de trabajo
+
+La API de flujos de trabajo te permite ver los flujos de trabajo de un repositorio. {% data reusables.actions.about-workflows %} Para obtener más información, consulta la sección "[Automatizar tu flujo de trabajo con GitHub Actions](/actions/automating-your-workflow-with-github-actions)".
+
+{% data reusables.actions.actions-authentication %} {% data reusables.actions.actions-app-actions-permissions-api %}
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/rest-reference/activity/events.md b/translations/es-ES/data/reusables/rest-reference/activity/events.md
new file mode 100644
index 000000000000..78f65cef3653
--- /dev/null
+++ b/translations/es-ES/data/reusables/rest-reference/activity/events.md
@@ -0,0 +1,22 @@
+## Events
+
+The Events API is a read-only API to the {% data variables.product.prodname_dotcom %} events. These events power the various activity streams on the site.
+
+The Events API can return different types of events triggered by activity on {% data variables.product.product_name %}. For more information about the specific events that you can receive from the Events API, see "[{% data variables.product.prodname_dotcom %} Event types](/developers/webhooks-and-events/github-event-types)." An events API for repository issues is also available. For more information, see the "[Issue Events API](/rest/reference/issues#events)."
+
+Events are optimized for polling with the "ETag" header. If no new events have been triggered, you will see a "304 Not Modified" response, and your current rate limit will be untouched. There is also an "X-Poll-Interval" header that specifies how often (in seconds) you are allowed to poll. In times of high server load, the time may increase. Please obey the header.
+
+``` shell
+$ curl -I {% data variables.product.api_url_pre %}/users/tater/events
+> HTTP/2 200
+> X-Poll-Interval: 60
+> ETag: "a18c3bded88eb5dbb5c849a489412bf3"
+
+# The quotes around the ETag value are important
+$ curl -I {% data variables.product.api_url_pre %}/users/tater/events \
+$ -H 'If-None-Match: "a18c3bded88eb5dbb5c849a489412bf3"'
+> HTTP/2 304
+> X-Poll-Interval: 60
+```
+
+Only events created within the past 90 days will be included in timelines. Events older than 90 days will not be included (even if the total number of events in the timeline is less than 300).
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/rest-reference/activity/feeds.md b/translations/es-ES/data/reusables/rest-reference/activity/feeds.md
new file mode 100644
index 000000000000..a9a32ed7647c
--- /dev/null
+++ b/translations/es-ES/data/reusables/rest-reference/activity/feeds.md
@@ -0,0 +1,52 @@
+## Fuentes
+
+### Example of getting an Atom feed
+
+To get a feed in Atom format, you must specify the `application/atom+xml` type in the `Accept` header. For example, to get the Atom feed for GitHub security advisories:
+
+ curl -H "Accept: application/atom+xml" https://github.com/security-advisories
+
+#### Respuesta
+
+```shell
+HTTP/2 200
+```
+
+```xml
+
+
+ tag:github.com,2008:/security-advisories
+
+ GitHub Security Advisory Feed
+
+ GitHub
+
+ 2019-01-14T19:34:52Z
+
+ tag:github.com,2008:GHSA-abcd-12ab-23cd
+ 2018-07-26T15:14:52Z
+ 2019-01-14T19:34:52Z
+ [GHSA-abcd-12ab-23cd] Moderate severity vulnerability that affects Octoapp
+
+
+ <p>Octoapp node module before 4.17.5 suffers from a Modification of Assumed-Immutable Data (MAID) vulnerability via defaultsDeep, merge, and mergeWith functions, which allows a malicious user to modify the prototype of "Object" via <strong>proto</strong>, causing the addition or modification of an existing property that will exist on all objects.</p>
+ <p><strong>Affected Packages</strong></p>
+
+ <dl>
+ <dt>Octoapp</dt>
+ <dd>Ecosystem: npm</dd>
+ <dd>Severity: moderate</dd>
+ <dd>Versions: < 4.17.5</dd>
+ <dd>Fixed in: 4.17.5</dd>
+ </dl>
+
+ <p><strong>References</strong></p>
+
+ <ul>
+ <li>https://nvd.nist.gov/vuln/detail/CVE-2018-123</li>
+ </ul>
+
+
+
+
+```
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/rest-reference/activity/notifications.md b/translations/es-ES/data/reusables/rest-reference/activity/notifications.md
new file mode 100644
index 000000000000..a58737225b1f
--- /dev/null
+++ b/translations/es-ES/data/reusables/rest-reference/activity/notifications.md
@@ -0,0 +1,59 @@
+## Notificaciones
+
+Los usuarios reciben notificaciones para las conversaciones en los repositorios que observan, incluyendo:
+
+* Las de los informes de problemas y sus comentarios
+* Las de las solicitudes de extracción en sus comentarios
+* Las de los comentarios en cualquier confirmación
+
+También se envían notificaciones para las conversaciones en los repositorios sin observar cuando el usuario está involucrado, incluyendo:
+
+* **@menciones**
+* Asignaciones de informes de problemas
+* Confirmaciones que confirme o cree el usuario
+* Cualquier debate en el que el usuario participe activamente
+
+Todas las llamadas de la API para notificaciones necesitan los alcances de la API para `notifications` o `repo`. El hacerlo te dará acceso de solo lectura a algunos contenidos de informes de problemas y de confirmaciones. Aún necesitarás el alcance de `repo` para acceder a los informes de problemas y a las confirmaciones desde sus respectivas terminales.
+
+Las notificaciones se devuelven como "hilos". Un hilo contiene información acerca del debate actual sobre un informe de problemas, solicitud de extracción o confirmación.
+
+Las notificaciones se optimizan para el sondeo con el encabezado `Last-Modified`. Si no hay notificaciones nuevas, verás una respuesta `304 Not Modified`, la cual dejará tu límite de tasa intacto. Hay un encabezado de `X-Poll-Interval` que especifica la frecuencia (en segundos) en la que se te permite hacer sondeos. Este tiempo podría incrementarse durante los periodos de carga fuerte en el servidor. Por favor obedece al encabezado.
+
+``` shell
+# Add authentication to your requests
+$ curl -I {% data variables.product.api_url_pre %}/notifications
+HTTP/2 200
+Last-Modified: Thu, 25 Oct 2012 15:16:27 GMT
+X-Poll-Interval: 60
+
+# Pass the Last-Modified header exactly
+$ curl -I {% data variables.product.api_url_pre %}/notifications
+$ -H "If-Modified-Since: Thu, 25 Oct 2012 15:16:27 GMT"
+> HTTP/2 304
+> X-Poll-Interval: 60
+```
+
+### Razones para obtener las notificaciones
+
+Cuando recuperas respuestas de la API de Notificaciones, cada carga útil tiene una clave que se titula `reason`. Estas corresponden a los eventos que activan una notificación.
+
+Hay una lista potencial de `reason` para recibir una notificación:
+
+| Nombre de la razón | Descripción |
+| ------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `assign` | Se te asignó al informe de problemas. |
+| `autor` | Creaste el hilo. |
+| `comentario` | Comentaste en el hilo. |
+| `ci_activity` | Se completó una ejecución de flujo de trabajo de {% data variables.product.prodname_actions %}. |
+| `invitación` | Aceptaste una invitación para colaborar en el repositorio. |
+| `manual` | Te suscribiste al hilo (a través de un informe de problemas o solicitud de extracción). |
+| `mención` | Se te **@mencionó** específicamente en el contenido. |
+| `review_requested` | Se te solicitó, o se solicitó a un equipo del cual eres miembro, revisar una solicitud de extracción.{% ifversion fpt or ghec %}
+| `security_alert` | {% data variables.product.prodname_dotcom %} descubrió una [vulnerabilidad de seguridad](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies) en tu repositorio.{% endif %}
+| `state_change` | Cambiaste el estado del hilo (por ejemplo, cerraste un informe de problemas o fusionaste una solicitud de extracción). |
+| `subscribed` | Estás observando el repositorio. |
+| `team_mention` | Estuviste en un equipo al que se mencionó. |
+
+Toma en cuenta que la `reason` se modificará conforme al hilo, y puede cambiar si esta `reason` es diferente en una notificación posterior.
+
+Por ejemplo, si eres el autor de un informe de problemas, las notificaciones subsecuentes de dicho informe tendrán una `reason` o un `author`. Si entonces se te **@menciona** en el mismo informe de problemas, las notificaciones que obtengas de ahí en adelante tendrán una `reason` o una `mention`. La `reason` se queda como una `mention`, sin importar si nunca se te menciona.
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/rest-reference/activity/starring.md b/translations/es-ES/data/reusables/rest-reference/activity/starring.md
new file mode 100644
index 000000000000..d222dece2301
--- /dev/null
+++ b/translations/es-ES/data/reusables/rest-reference/activity/starring.md
@@ -0,0 +1,15 @@
+## Marcar con una estrella
+
+El marcar a los repositorios con una estrella es una característica que permite a los usuarios marcar a los repositorios como favoritos. Las estrellas se muestran junto a los repositorios para denotar un nivel aproximado de interés. Las estrellas no tienen efecto alguno en las notificaciones o en los canales de actividad.
+
+### Marcar con estrella vs. Observar
+
+En agosto de 2012, [cambiamos la forma en la que funciona el observar repositorios](https://github.com/blog/1204-notifications-stars) en {% data variables.product.prodname_dotcom %}. Muchas aplicaciones de cliente de la API podrían estar utilizando las terminales de "observación" originales para acceder a estos datos. Ahora puedes comenzar a utilizar las terminales de "estrella" como sustitución (como se describe más adelante). Para obtener más información, consulta la [publicación de Cambio de la API de observaciones](https://developer.github.com/changes/2012-09-05-watcher-api/) y la "[API para Observar Repositorios](/rest/reference/activity#watching)".
+
+### Tipos de medio personalizados para marcar con estrella
+
+Hay un tipo de medios personalizado compatible para la API de REST para Marcar con estrella. Cuando utilizas este tipo de medios personalizado, recibirás una respuesta con la marca de tiempo `starred_at` que indica la hora en el que se creó la estrella. La respuesta también tiene una segunda propiedad que incluye el recurso que se devuelve cuando no se incluye el tipo de medios personalizado. La propiedad que contiene el recurso puede ser `user` o `repo`.
+
+ application/vnd.github.v3.star+json
+
+Para obtener más información acerca de los tipos de medios, consulta la sección "[Tipos de medios personalizados](/rest/overview/media-types)".
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/rest-reference/activity/watching.md b/translations/es-ES/data/reusables/rest-reference/activity/watching.md
new file mode 100644
index 000000000000..7ece26483588
--- /dev/null
+++ b/translations/es-ES/data/reusables/rest-reference/activity/watching.md
@@ -0,0 +1,3 @@
+## Observar
+
+Observar un repositorio registra al usuario para recibir notificaciones en debates nuevos, así como en los eventos de los canales de actividad del mismo. Para marcar a un repositorio como favorito de forma sencilla, consulta la sección "[Marcar repositorios con una estrella](/rest/reference/activity#starring)".
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/rest-reference/apps/apps.md b/translations/es-ES/data/reusables/rest-reference/apps/apps.md
new file mode 100644
index 000000000000..10a745622e26
--- /dev/null
+++ b/translations/es-ES/data/reusables/rest-reference/apps/apps.md
@@ -0,0 +1,9 @@
+{% data reusables.apps.general-apps-restrictions %}
+
+Esta página lista las terminales a las que puedes acceder mientras te autenticas como una GitHub App. Consulta la sección "[Autenticarse como una GitHub App](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-a-github-app)" para conocer más.
+
+Cuando estás autenticado como una GitHub App, la API de GitHub Apps te habilita para obtener información de alto nivel sobre una GitHub App así como para obtener información específica sobre las instalaciones de éstas.
+
+Puedes acceder a las terminales de la API v3 de REST mientras estás autenticado como una GitHub App. Estas terminales tienen una sección de "Notas" que contiene una viñeta que dice "Funciona con las GitHub Apps". También puedes acceder a estas terminales mientras estás autenticado como un usuario.
+
+Un subconjunto de terminales de la API v3 de REST requiere que te autentiques como una instalación de una GitHub App. Consulta las [Instalaciones](/rest/reference/apps#installations) para obtener una lista de estas terminales.
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/rest-reference/apps/installations.md b/translations/es-ES/data/reusables/rest-reference/apps/installations.md
new file mode 100644
index 000000000000..64fd9aa49f61
--- /dev/null
+++ b/translations/es-ES/data/reusables/rest-reference/apps/installations.md
@@ -0,0 +1,5 @@
+## Instalaciones
+
+La API de instalaciones te habilita para obtener información acerca de las instalaciones de tu GitHub App y para realizar acciones dentro de esas instalaciones. Una _instalación_ se refiere a cualquier cuenta de usuario o de organización que tenga la app instalada. Para obtener más información sobre cómo autenticarte como una instalación y limitar el acceso a repositorios específicos, consulta la sección "[Autenticarte como una instalación](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation)".
+
+Para listar las instalaciones de una GitHub App para una organización, consulta la sección "[Listar instalaciones de la app para una organización](/rest/reference/orgs#list-app-installations-for-an-organization)".
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/rest-reference/apps/marketplace.md b/translations/es-ES/data/reusables/rest-reference/apps/marketplace.md
new file mode 100644
index 000000000000..f4eb63f3d23b
--- /dev/null
+++ b/translations/es-ES/data/reusables/rest-reference/apps/marketplace.md
@@ -0,0 +1,13 @@
+## Marketplace
+
+Para obtener más información acerca de {% data variables.product.prodname_marketplace %}, consulta "[GitHub Marketplace](/marketplace/)".
+
+La API de {% data variables.product.prodname_marketplace %} te permite ver qué clientes están utilizando un plan de precios, ver sus compras y también ver si una cuenta tiene una suscripción activa.
+
+### Hacer pruebas con terminales de muestra
+
+Esta API incluye terminales que te permiten [probar tu {% data variables.product.prodname_github_app %}](/marketplace/integrating-with-the-github-marketplace-api/testing-github-marketplace-apps/) con **datos de muestra**. Los datos de muestra son datos falsos y preprogramados que no cambiarán con base en las suscripciones reales.
+
+Para hacer pruebas con estos datos, utiliza una terminal de muestra en vez de su contraparte productiva. Esto te permite probar si la lógica de la API tendrá éxito antes de listar tus {% data variables.product.prodname_github_apps %} en {% data variables.product.prodname_marketplace %}.
+
+Asegúrate de reemplazar tus terminales de muestra con aquellas productivas antes de desplegar tu {% data variables.product.prodname_github_app %}.
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/rest-reference/apps/oauth-applications.md b/translations/es-ES/data/reusables/rest-reference/apps/oauth-applications.md
new file mode 100644
index 000000000000..8d7164ce7be9
--- /dev/null
+++ b/translations/es-ES/data/reusables/rest-reference/apps/oauth-applications.md
@@ -0,0 +1,3 @@
+## API de las Aplicaciones de OAuth
+
+Puedes utilizar esta API para administrar los tokens de OAuth que utiliza una aplicación de OAuth para acceder a las cuentas de las personas en {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}.
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/rest-reference/apps/webhooks.md b/translations/es-ES/data/reusables/rest-reference/apps/webhooks.md
new file mode 100644
index 000000000000..7ae5665f8bbc
--- /dev/null
+++ b/translations/es-ES/data/reusables/rest-reference/apps/webhooks.md
@@ -0,0 +1,3 @@
+## Webhooks
+
+A {% data variables.product.prodname_github_app %}'s webhook allows you to receive HTTP `POST` payloads whenever certain events happen for an app. {% data reusables.webhooks.webhooks-rest-api-links %}
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/rest-reference/billing/billing.md b/translations/es-ES/data/reusables/rest-reference/billing/billing.md
new file mode 100644
index 000000000000..f7b929f2ddea
--- /dev/null
+++ b/translations/es-ES/data/reusables/rest-reference/billing/billing.md
@@ -0,0 +1 @@
+Puedes obtener información de facturación para una empresa. Para obtener más información, consulta la API de REST para la "[ Administración de {% data variables.product.prodname_dotcom %} Enterprise](/rest/reference/enterprise-admin#billing)".
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/rest-reference/branches/branch-protection.md b/translations/es-ES/data/reusables/rest-reference/branches/branch-protection.md
new file mode 100644
index 000000000000..338eaef2b308
--- /dev/null
+++ b/translations/es-ES/data/reusables/rest-reference/branches/branch-protection.md
@@ -0,0 +1 @@
+## Ramas protegidas
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/rest-reference/checks/checks.md b/translations/es-ES/data/reusables/rest-reference/checks/checks.md
new file mode 100644
index 000000000000..1b99c60cf06f
--- /dev/null
+++ b/translations/es-ES/data/reusables/rest-reference/checks/checks.md
@@ -0,0 +1 @@
+Puedes crear apps que lleven a cabo integración contínua, limpieza de código, o servicios de escaneo de código y que proporcionen retroalimentación detallada en las confirmaciones. Para obtener más información, consulta la sección "[Empezar con la API de verificaciones](/rest/guides/getting-started-with-the-checks-api)" y "[Crear pruebas de IC con la API de verificaciones](/apps/quickstart-guides/creating-ci-tests-with-the-checks-api/)".
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/rest-reference/checks/runs.md b/translations/es-ES/data/reusables/rest-reference/checks/runs.md
new file mode 100644
index 000000000000..e2558ed62718
--- /dev/null
+++ b/translations/es-ES/data/reusables/rest-reference/checks/runs.md
@@ -0,0 +1 @@
+## Ejecuciones de Verificación
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/rest-reference/checks/suites.md b/translations/es-ES/data/reusables/rest-reference/checks/suites.md
new file mode 100644
index 000000000000..4df4ae360df3
--- /dev/null
+++ b/translations/es-ES/data/reusables/rest-reference/checks/suites.md
@@ -0,0 +1,7 @@
+## Conjuntos de Verificaciones
+
+{% note %}
+
+ **Nota:** Una GitHub App solo recibe un evento de [`check_suite`](/webhooks/event-payloads/#check_suite) por SHA de confirmación, aún si cargas este SHA en más de una rama. Para saber cuándo se carga un SHA de confirmación a una rama, puedes suscribirte a los eventos de [`create`](/webhooks/event-payloads/#create) de la misma.
+
+{% endnote %}
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/rest-reference/code-scanning/code-scanning.md b/translations/es-ES/data/reusables/rest-reference/code-scanning/code-scanning.md
new file mode 100644
index 000000000000..b6b94873fcec
--- /dev/null
+++ b/translations/es-ES/data/reusables/rest-reference/code-scanning/code-scanning.md
@@ -0,0 +1,15 @@
+{% data reusables.code-scanning.beta %}
+
+La API del {% data variables.product.prodname_code_scanning %} te permite recuperar y actualizar las alertas del {% data variables.product.prodname_code_scanning %} desde un repositorio. Puedes utilizar las terminales para crear reportes automatizados para las alertas del {% data variables.product.prodname_code_scanning %} en una organización o cargar resutlados de análisis que se hayan generado utilizando con herramientas fuera de línea del {% data variables.product.prodname_code_scanning %}. Para obtener más información, consulta la sección "[Encontrar vulnerabilidades de seguridad y errores en tu código](/github/finding-security-vulnerabilities-and-errors-in-your-code)".
+
+{% ifversion fpt or ghes > 3.0 or ghae or ghec %}
+### Tipos de medios personalizados para el {% data variables.product.prodname_code_scanning %}
+
+Hay un tipo de medios personalizado compatible para la API de REST del {% data variables.product.prodname_code_scanning %}.
+
+ application/sarif+json
+
+Puedes utilizarla con las solicitudes de tipo `GET` que envíes a la terminal de `/analyses/{analysis_id}`. Para obtener más información sobre esta operación, consulta la sección [Obtén un análisis del {% data variables.product.prodname_code_scanning %} para un repositorio](#get-a-code-scanning-analysis-for-a-repository)". Cuando utilices este tipo de medios con esta operación, la respuesta incluirá un subconjunto de los datos actuals que se cargaron para el análisis específico en vez del resumen del análisis que se devuelve cuando utilizas el tipo de medios predeterminado. La respuesta también incluye datos adicionales, tales como las propiedades de `github/alertNumber` y `github/alertUrl`. Estos datos tienen formato de [SARIF versión 2.1.0](https://docs.oasis-open.org/sarif/sarif/v2.1.0/cs01/sarif-v2.1.0-cs01.html).
+
+Para obtener más información, consulta la sección "[Tipos de medios](/rest/overview/media-types)".
+{% endif %}
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/rest-reference/codes-of-conduct/codes-of-conduct.md b/translations/es-ES/data/reusables/rest-reference/codes-of-conduct/codes-of-conduct.md
new file mode 100644
index 000000000000..7fb3e8220d43
--- /dev/null
+++ b/translations/es-ES/data/reusables/rest-reference/codes-of-conduct/codes-of-conduct.md
@@ -0,0 +1,2 @@
+
+Puedes usar la API de Códigos de Conducta para recuperar la información acerca del código de conducta de un repositorio. Para obtener el código de conducta de un repositorio, utiliza la terminal "[Obtener un repositorio](/rest/reference/repos#get-a-repository)".
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/rest-reference/codespaces/codespaces.md b/translations/es-ES/data/reusables/rest-reference/codespaces/codespaces.md
new file mode 100644
index 000000000000..4d0b0d1c38f2
--- /dev/null
+++ b/translations/es-ES/data/reusables/rest-reference/codespaces/codespaces.md
@@ -0,0 +1,3 @@
+{% data reusables.codespaces.codespaces-api-beta-note %}
+
+La API de {% data variables.product.prodname_codespaces %} te permite administrar las {% data variables.product.prodname_codespaces %} utilizando la API de REST. Esta API se encuentra disponible para los usuarios autenticados y las Apps de OAuth, pero no para las GitHub Apps. Para obtener más información, consulta la sección "[{% data variables.product.prodname_codespaces %}](/codespaces)".
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/rest-reference/codespaces/machines.md b/translations/es-ES/data/reusables/rest-reference/codespaces/machines.md
new file mode 100644
index 000000000000..e3fc37db249d
--- /dev/null
+++ b/translations/es-ES/data/reusables/rest-reference/codespaces/machines.md
@@ -0,0 +1,4 @@
+## Máquinas
+La API de máquinas permite que un usuario determine qué tipos de máquina están disponibles para crear un codespace, ya sea en un repositorio definido o como un usuario autenticado. Para obtener más información, consulta la sección "[Acerca de los tipos de máquina](/codespaces/developing-in-codespaces/changing-the-machine-type-for-your-codespace#about-machine-types)".
+
+También puedes utilizar esta información cuando cambies la máquina de un codespace existente actualizando su propiedad de `machine`. La actualización de la máquina tomará lugar la siguiente vez que el codespace se reinicie. Para obtener más información, consulta la sección "[Cambiar el tipo de máquina de tu codespace](/codespaces/developing-in-codespaces/changing-the-machine-type-for-your-codespace)".
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/rest-reference/codespaces/secrets.md b/translations/es-ES/data/reusables/rest-reference/codespaces/secrets.md
new file mode 100644
index 000000000000..3a23d4300eed
--- /dev/null
+++ b/translations/es-ES/data/reusables/rest-reference/codespaces/secrets.md
@@ -0,0 +1,2 @@
+## Secretos
+La API de secretos permite que un usuario cree, liste y borre secretos (tales como los tokens de acceso para los servicios en la nube) así como asignar secretos a los repositorios a los que el usuario tenga acceso. Estos secretos se hacen disponibles para el codespace en el tiempo de ejecución. Para obtener más información, consulta la sección "[Administrar los secretos cifrados para tu codespace](/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces)".
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/rest-reference/collaborators/invitations.md b/translations/es-ES/data/reusables/rest-reference/collaborators/invitations.md
new file mode 100644
index 000000000000..3d659a04bead
--- /dev/null
+++ b/translations/es-ES/data/reusables/rest-reference/collaborators/invitations.md
@@ -0,0 +1,9 @@
+## Invitaciones
+
+La API de Invitaciones al Repositorio permite a los usuarios o a los servicios externos invitar a otros usuarios para colaborar en un repositorio. Los usuarios invitados (o los servicios externos en nombre de estos) pueden elegir aceptar o rechazar la invitación.
+
+Toma en cuenta que el [alcance de OAuth](/developers/apps/scopes-for-oauth-apps) `repo:invite` otorga un acceso dirigido a las invitaciones **sin** otorgar también el acceso al código del repositorio, mientras que el alcance `repo` otorga permisos para el código así como para las invitaciones.
+
+### Invitar a un usuario a un repositorio
+
+Utiliza la terminal de la API para agregar un colaborador. Para obtener más información, consulta la sección "[Agregar un colaborador del repositorio](/rest/reference/collaborators#add-a-repository-collaborator)".
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/rest-reference/commits/comments.md b/translations/es-ES/data/reusables/rest-reference/commits/comments.md
new file mode 100644
index 000000000000..b1701baa4c30
--- /dev/null
+++ b/translations/es-ES/data/reusables/rest-reference/commits/comments.md
@@ -0,0 +1,12 @@
+## Comentarios sobre confirmación de cambios
+
+### Tipos de medios personalizados para los comentarios de las confirmaciones
+
+Estos son los tipos de medios compatibles para los comentarios de las confirmaciones. Puedes leer más sobre el uso de tipos de medios en la API [aquí](/rest/overview/media-types).
+
+ application/vnd.github-commitcomment.raw+json
+ application/vnd.github-commitcomment.text+json
+ application/vnd.github-commitcomment.html+json
+ application/vnd.github-commitcomment.full+json
+
+Para obtener más información, consulta la sección "[Tipos de medios personalizados](/rest/overview/media-types)".
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/rest-reference/commits/statuses.md b/translations/es-ES/data/reusables/rest-reference/commits/statuses.md
new file mode 100644
index 000000000000..f7ab2b474b37
--- /dev/null
+++ b/translations/es-ES/data/reusables/rest-reference/commits/statuses.md
@@ -0,0 +1,13 @@
+## Estados de confirmación
+
+La API de estados permite que los servicios externos marquen las confirmaciones con un estado de `error`, `failure`, `pending`, o `success`, el cual se refleja después en las solicitudes de extracción que involucran a esas confirmaciones.
+
+Los estados también incluyen una `description` y una `target_url` opcionales, y recomendamos ampliamente proporcionarlas, ya que hacen mucho más útiles a los estados en la IU de GitHub.
+
+Como ejemplo, un uso común es que los servicios de integración contínua marquen a las confirmaciones como compilaciones que pasan o fallan utilizando los estados. La `target_url` sería la URL completa de la salida de la compilación, y la `description` sería el resumen de alto nivel de lo que pasó con la compilación.
+
+Los estados pueden incluir un `context` para indicar qué servicio está proporcionando ese estado. Por ejemplo, puedes hacer que tu servicio de integración continua cargue estados con un contexto de `ci`, y que una herramienta de auditoria de seguridad cargue estados con un contexto de `security`. Puedes utilizar entonces el [Obtener el estado combinado para una referencia específica](/rest/reference/commits#get-the-combined-status-for-a-specific-reference) para recuperar todo el estado de una confirmación.
+
+Toma en cuenta que el [alcance de OAuth](/developers/apps/scopes-for-oauth-apps) de `repo:status` otorga acceso dirigido a los estados **sin** otorgar también el acceso al código del repositorio, mientras que el alcance `repo` otorga permisos para el código y también para los estados.
+
+Si estás desarrollando una GitHub App y quieres proporcionar información más detallada sobre un servicio externo, tal vez quieras utilizar la [API de Verificaciones](/rest/reference/checks).
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/rest-reference/dependabot/dependabot.md b/translations/es-ES/data/reusables/rest-reference/dependabot/dependabot.md
new file mode 100644
index 000000000000..e1430f19c2b4
--- /dev/null
+++ b/translations/es-ES/data/reusables/rest-reference/dependabot/dependabot.md
@@ -0,0 +1,3 @@
+The {% data variables.product.prodname_dependabot %} Secrets API lets you create, update, delete, and retrieve information about encrypted secrets. {% data reusables.actions.about-secrets %} Para obtener más información, consulta "[Administrar los secretos cifrados para el Dependabot](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-encrypted-secrets-for-dependabot)".
+
+{% data reusables.actions.actions-authentication %} {% data variables.product.prodname_github_apps %} must have the `dependabot_secrets` permission to use this API. Los usuarios autenticados deben tener acceso de colaborador en el repositorio para crear, actualizar o leer los secretos.
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/rest-reference/deployments/deployments.md b/translations/es-ES/data/reusables/rest-reference/deployments/deployments.md
new file mode 100644
index 000000000000..3f2e97ca1083
--- /dev/null
+++ b/translations/es-ES/data/reusables/rest-reference/deployments/deployments.md
@@ -0,0 +1,46 @@
+Los despliegues son slicitudes para desplegar una ref específica (rma, SHA, etiqueta). GitHub despliega un [evento de `deployment`](/developers/webhooks-and-events/webhook-events-and-payloads#deployment) al que puedan escuchar los servicios externos y al con el cual puedan actuar cuando se creen los despliegues nuevos. Los despliegues habilitan a los desarrolladores y a las organizaciones para crear herramientas sin conexión directa en torno a los despliegues, sin tener que preocuparse acerca de los detalles de implementación de entregar tipos de aplicaciones diferentes (por ejemplo, web o nativas).
+
+Los estados de despliegue permiten que los servicios externos marquen estos despliegues con un estado de `error`, `failure`, `pending`, `in_progress`, `queued`, o `success` que pueden consumir los sistemas que escuchan a los [eventos de `deployment_status`](/developers/webhooks-and-events/webhook-events-and-payloads#deployment_status).
+
+Los estados de despliegue también incluyen una `description` y una `log_url` opcionales, las cuales se recomiendan ampliamente, ya que hacen que los estados de despliegue sean más útiles. La `log_url` es la URL completa para la salida del despliegue, y la `description` es el resumen de alto nivel de lo que pasó con este despliegue.
+
+GitHub envía eventos de `deployment` y `deployment_status` cuando se crean despliegues y estados de despliegue nuevos. Estos eventos permiten que las integraciones de terceros reciban respuesta de las solicitudes de despliegue y actualizan el estado de un despliegue conforme éste progrese.
+
+Debajo encontrarás un diagrama de secuencia simple que explica cómo funcionarían estas interacciones.
+
+```
++---------+ +--------+ +-----------+ +-------------+
+| Tooling | | GitHub | | 3rd Party | | Your Server |
++---------+ +--------+ +-----------+ +-------------+
+ | | | |
+ | Create Deployment | | |
+ |--------------------->| | |
+ | | | |
+ | Deployment Created | | |
+ |<---------------------| | |
+ | | | |
+ | | Deployment Event | |
+ | |---------------------->| |
+ | | | SSH+Deploys |
+ | | |-------------------->|
+ | | | |
+ | | Deployment Status | |
+ | |<----------------------| |
+ | | | |
+ | | | Deploy Completed |
+ | | |<--------------------|
+ | | | |
+ | | Deployment Status | |
+ | |<----------------------| |
+ | | | |
+```
+
+Ten en cuenta que GitHub jamás accede a tus servidores realmente. La interacción con los eventos de despliegue dependerá de tu integración de terceros. Varios sistemas pueden escuchar a los eventos de despliegue, y depende de cada uno de ellos decidir si son responsables de cargar el código a tus servidores, si crean código nativo, etc.
+
+Toma en cuenta que el [Alcance de OAuth](/developers/apps/scopes-for-oauth-apps) de `repo_deployment` otorga acceso dirigido para los despliegues y estados de despliegue **sin** otorgar acceso al código del repositorio, mientras que {% ifversion not ghae %} los alcances de `public_repo` y{% endif %}`repo` también otorgan permisos para el código.
+
+### Despliegues inactivos
+
+Cuando configuras el estado de un despliegue como `success`, entonces todos los despliegues anteriores que no sean transitorios ni de producción y que se encuentren en el mismo repositorio con el mismo ambiente se convertirán en `inactive`. Para evitar esto, puedes configurar a `auto_inactive` como `false` cuando creas el estado del servidor.
+
+Puedes comunicar que un ambiente transitorio ya no existe si configuras el `state` como `inactive`. El configurar al `state` como `inactive`muestra el despliegue como `destroyed` en {% data variables.product.prodname_dotcom %} y elimina el acceso al mismo.
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/rest-reference/deployments/environments.md b/translations/es-ES/data/reusables/rest-reference/deployments/environments.md
new file mode 100644
index 000000000000..c5e112dfd4d6
--- /dev/null
+++ b/translations/es-ES/data/reusables/rest-reference/deployments/environments.md
@@ -0,0 +1,5 @@
+## Ambientes
+
+La API de Ambientes te permite crear, configurar y borrar ambientes. Para obtener más información sobre los ambientes, consulta la sección "[Utilizar ambientes para despliegue](/actions/deployment/using-environments-for-deployment)". Para administrar los secretos de ambiente, consulta la sección "[Secretos](/rest/reference/actions#secrets)".
+
+{% data reusables.gated-features.environments %}
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/rest-reference/deployments/keys.md b/translations/es-ES/data/reusables/rest-reference/deployments/keys.md
new file mode 100644
index 000000000000..23b36b1d075b
--- /dev/null
+++ b/translations/es-ES/data/reusables/rest-reference/deployments/keys.md
@@ -0,0 +1,5 @@
+## Llaves de implementación
+
+{% data reusables.repositories.deploy-keys %}
+
+Las llaves de despliegue pueden ya sea configurarse utilizando las siguientes terminales de la API, o mediante GitHub. Para aprender cómo configurar las llaves de despliegue en GitHub, consulta la sección "[Administrar las llaves de despliegue](/developers/overview/managing-deploy-keys)".
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/rest-reference/deployments/statuses.md b/translations/es-ES/data/reusables/rest-reference/deployments/statuses.md
new file mode 100644
index 000000000000..cb426dcd8200
--- /dev/null
+++ b/translations/es-ES/data/reusables/rest-reference/deployments/statuses.md
@@ -0,0 +1 @@
+## Estados de despliegue
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/rest-reference/enterprise-admin/admin-stats.md b/translations/es-ES/data/reusables/rest-reference/enterprise-admin/admin-stats.md
new file mode 100644
index 000000000000..a0c1e176944f
--- /dev/null
+++ b/translations/es-ES/data/reusables/rest-reference/enterprise-admin/admin-stats.md
@@ -0,0 +1,3 @@
+## Estadísticas de los Administradores
+
+La API de estadísticas de los administradores proporciona diversas métricas sobre tu instalación. *Solo se encuentra disponible para los administradores de sitio [autenticados.](/rest/overview/resources-in-the-rest-api#authentication)* Los usuarios normales recibirán una respuesta `404` si intentan acceder a ella.
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/rest-reference/enterprise-admin/announcements.md b/translations/es-ES/data/reusables/rest-reference/enterprise-admin/announcements.md
new file mode 100644
index 000000000000..ae2cc9220a8f
--- /dev/null
+++ b/translations/es-ES/data/reusables/rest-reference/enterprise-admin/announcements.md
@@ -0,0 +1,3 @@
+## Anuncios
+
+La API de anuncios te permite administrar el letrero de anuncios globales en tu empresa. Para obtener más información, consulta la sección "[Personalizar los mensajes de usuario para tu empresa](/admin/user-management/customizing-user-messages-for-your-enterprise#creating-a-global-announcement-banner)".
diff --git a/translations/es-ES/data/reusables/rest-reference/enterprise-admin/audit-log.md b/translations/es-ES/data/reusables/rest-reference/enterprise-admin/audit-log.md
new file mode 100644
index 000000000000..b22956501e6f
--- /dev/null
+++ b/translations/es-ES/data/reusables/rest-reference/enterprise-admin/audit-log.md
@@ -0,0 +1 @@
+## Registro de auditoría
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/rest-reference/enterprise-admin/billing.md b/translations/es-ES/data/reusables/rest-reference/enterprise-admin/billing.md
new file mode 100644
index 000000000000..c696975a61c6
--- /dev/null
+++ b/translations/es-ES/data/reusables/rest-reference/enterprise-admin/billing.md
@@ -0,0 +1 @@
+## Facturación
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/rest-reference/enterprise-admin/enterprise-admin.md b/translations/es-ES/data/reusables/rest-reference/enterprise-admin/enterprise-admin.md
new file mode 100644
index 000000000000..acfc024c0ef3
--- /dev/null
+++ b/translations/es-ES/data/reusables/rest-reference/enterprise-admin/enterprise-admin.md
@@ -0,0 +1,44 @@
+{% ifversion fpt or ghec %}
+
+{% note %}
+
+**Nota:** Este artículo aplica a {% data variables.product.prodname_ghe_cloud %}. Para ver la versión de {% data variables.product.prodname_ghe_managed %} o de {% data variables.product.prodname_ghe_server %}, utiliza el menú desplegable de **{% data ui.pages.article_version %}**.
+
+{% endnote %}
+
+{% endif %}
+
+### URL de las Terminales
+
+Las terminales de la API de REST{% ifversion ghes %}—excepto las terminales de la API de [Consola de Administración](#management-console)—{% endif %} se prefijan con la siguiente URL:
+
+```shell
+{% data variables.product.api_url_pre %}
+```
+
+{% ifversion fpt or ghec %}
+Cuando las terminales incluyen a `{enterprise}`, reemplaza `{enterprise}` con el manejo de tu cuenta empresarial, el cual se incluye en la URL de los ajustes de tu empresa. Por ejemplo, si tu cuenta empresarial se ubica en `https://github.com/enterprises/octo-enterprise`, reemplaza a `{enterprise}` con `octo-enterprise`.
+{% endif %}
+
+{% ifversion ghes %}
+Las terminales de la API de [Consola de Administración](#management-console) solo llevan un prefijo con un nombre de host:
+
+```shell
+http(s)://hostname/
+```
+{% endif %}
+{% ifversion ghae or ghes %}
+### Autenticación
+
+Las terminales de la API para tu instalación de {% data variables.product.product_name %} acceptan [los mismos métodos de autenticación](/rest/overview/resources-in-the-rest-api#authentication) que los de la API de GitHub.com. Puedes autenticarte con **[Tokens de OAuth](/apps/building-integrations/setting-up-and-registering-oauth-apps/)** {% ifversion ghes %}(los cuales se pueden crear utilizando la [API de autorizciones](/rest/reference/oauth-authorizations#create-a-new-authorization)) {% endif %}o con la **[autenticación básica](/rest/overview/resources-in-the-rest-api#basic-authentication)**. {% ifversion ghes %} Los tokens de OAuth deben tener el [alcance de OAuth](/developers/apps/scopes-for-oauth-apps#available-scopes) de `site_admin` cuando se utilicen con las terminales específicas de la empresa. {% endif %}
+
+Solo los administradores de sitio autenticados en {% data variables.product.product_name %} pueden acceder a las terminales de la API de administración empresarial{% ifversion ghes %}, con exepción de la API de [Consola de Administración](#management-console), la cual requiere la [contraseña de la Consola de Administración](/enterprise/admin/articles/accessing-the-management-console/){% endif %}.
+
+{% endif %}
+
+{% ifversion ghae or ghes %}
+### Información de la versión
+
+La versión actual de tu empresa se devuelve en el encabezado de respuesta de cada API: `X-GitHub-Enterprise-Version: {{currentVersion}}.0` También puedes leer la versión actual si llamas a la [terminal de meta](/rest/reference/meta/).
+
+{% endif %}
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/rest-reference/enterprise-admin/global-webhooks.md b/translations/es-ES/data/reusables/rest-reference/enterprise-admin/global-webhooks.md
new file mode 100644
index 000000000000..2082a449e818
--- /dev/null
+++ b/translations/es-ES/data/reusables/rest-reference/enterprise-admin/global-webhooks.md
@@ -0,0 +1,5 @@
+## Webhooks globales
+
+Los webhooks globales se instalan en tu empresa. Puedes utilizar los webhooks globales para monitorear, responder a, o requerir las reglas para los usuarios, organizaciones, equipos y repositorios en tu empresa. Los webhooks globales se pueden suscribir a los tipos de evento para [organizaciones](/developers/webhooks-and-events/webhook-events-and-payloads#organization), [usuarios](/developers/webhooks-and-events/webhook-events-and-payloads#user), [repositorios](/developers/webhooks-and-events/webhook-events-and-payloads#repository), [equipos](/developers/webhooks-and-events/webhook-events-and-payloads#team), [miembros](/developers/webhooks-and-events/webhook-events-and-payloads#member), [membrecías](/developers/webhooks-and-events/webhook-events-and-payloads#membership), [bifuraciones](/developers/webhooks-and-events/webhook-events-and-payloads#fork), y [pings](/developers/webhooks-and-events/about-webhooks#ping-event).
+
+*Esta API solo se encuentra disponible para los administradores de sitio [autenticados.](/rest/overview/resources-in-the-rest-api#authentication)* Los usuarios normales recibirán una respuesta `404` si intentan acceder a ella. Para aprender cómo configurar los webhooks globales, consulta la sección [Acerca de los webhooks globales](/enterprise/admin/user-management/about-global-webhooks).
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/rest-reference/enterprise-admin/ldap.md b/translations/es-ES/data/reusables/rest-reference/enterprise-admin/ldap.md
new file mode 100644
index 000000000000..56c098ae2d8f
--- /dev/null
+++ b/translations/es-ES/data/reusables/rest-reference/enterprise-admin/ldap.md
@@ -0,0 +1,5 @@
+## LDAP
+
+Puedes utilizar la API de LDAP para actualizar las relaciones de cuenta entre un usuario de {% data variables.product.product_name %} o un equipo y su entrada enlazada de LDAP o poner en cola una sincronización nueva.
+
+Con las terminales de mapeo de LDAP, puedes actualizar el Nombre Distintivo (DN, por sus siglas en inglés) al cual mapea un usuario o equipo. Toma en cuenta que las terminales de LDAP generalmente solo son efectivas si tu aplicativo de {% data variables.product.product_name %} [habilitó la sincronización con LDAP](/enterprise/admin/authentication/using-ldap). La terminal de [mapeo de LDAP para actualización para un usuario](#update-ldap-mapping-for-a-user) puede utilizarse cuando se habilita LDAP, aún si la sincronización con LDAP está inhabilitada.
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/rest-reference/enterprise-admin/license.md b/translations/es-ES/data/reusables/rest-reference/enterprise-admin/license.md
new file mode 100644
index 000000000000..daa704ddafc9
--- /dev/null
+++ b/translations/es-ES/data/reusables/rest-reference/enterprise-admin/license.md
@@ -0,0 +1,3 @@
+## Licencia
+
+La API de licencias proporciona información sobre tu licencia empresarial. *Solo se encuentra disponible para los administradores de sitio [autenticados.](/rest/overview/resources-in-the-rest-api#authentication)* Los usuarios normales recibirán una respuesta `404` si intentan acceder a ella.
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/rest-reference/enterprise-admin/management-console.md b/translations/es-ES/data/reusables/rest-reference/enterprise-admin/management-console.md
new file mode 100644
index 000000000000..201a7e6fa061
--- /dev/null
+++ b/translations/es-ES/data/reusables/rest-reference/enterprise-admin/management-console.md
@@ -0,0 +1,29 @@
+## Consola de administración
+
+La API de la Consola de Administración te ayuda a administrar tu instalación de {% data variables.product.product_name %}.
+
+{% tip %}
+
+Debes configurar el número de puerto explícitamente cuando haces llamadas de la API hacia la Consola de Administración. Si habilitaste TLS en tu empresa, el número de puerto es `8443`; de lo contrario, el número de puerto es `8080`.
+
+Si no quieres proporcionar un número de puerto, necesitarás configurar tu herramienta para seguir automáticamente las redirecciones.
+
+Podría que también necesites agregar el [marcador `-k`](http://curl.haxx.se/docs/manpage.html#-k) cuando utilices `curl`, ya que {% data variables.product.product_name %} utiliza un certificado auto-firmado antes de que [agregues tu propio certificado TLS](/enterprise/admin/guides/installation/configuring-tls/).
+
+{% endtip %}
+
+### Autenticación
+
+Necesitas pasar tu [Contraseña de la Consola de Administración](/enterprise/admin/articles/accessing-the-management-console/) como un token de autenticación para cada terminal de la API de ésta, con excepción de [`/setup/api/start`](#create-a-github-enterprise-server-license).
+
+Utiliza el parámetro de `api_key` para enviar este token con cada solicitud. Por ejemplo:
+
+```shell
+$ curl -L 'https://hostname:admin_port/setup/api?api_key=your-amazing-password'
+```
+
+También puedes utilizar la autenticación HTTP estándar para enviar este token. Por ejemplo:
+
+```shell
+$ curl -L -u "api_key:your-amazing-password" 'https://hostname:admin_port/setup/api'
+```
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/rest-reference/enterprise-admin/org-pre-receive-hooks.md b/translations/es-ES/data/reusables/rest-reference/enterprise-admin/org-pre-receive-hooks.md
new file mode 100644
index 000000000000..5f11917d0162
--- /dev/null
+++ b/translations/es-ES/data/reusables/rest-reference/enterprise-admin/org-pre-receive-hooks.md
@@ -0,0 +1,16 @@
+## Ganchos de Pre-recepción de la Organización
+
+La API de Ganchos de Pre-recepción de la Organización te permite ver y modificar la aplicación de dichos ganchos que están disponibles para una organización.
+
+### Atributos de objeto
+
+| Nombre | Tipo | Descripción |
+| -------------------------------- | ----------- | --------------------------------------------------------- |
+| `name (nombre)` | `secuencia` | El nombre del gancho. |
+| `enforcement` | `secuencia` | El estado de imposición del gancho en este repositorio. |
+| `allow_downstream_configuration` | `boolean` | Si los repositorios pueden ignorar la imposición o no. |
+| `configuration_url` | `secuencia` | URL para la terminal en donde se configuró la imposición. |
+
+Los valores posibles para *enforcement* son `enabled`, `disabled` y `testing`. El valor `disabled` indica que el gancho de pre-recepción no se ejecutará. El valor `enabled` indica que se ejecutará y rechazará cualquier carga que resulte en un estado diferente a zero. El valor `testing` indica que el script va a ejecutarse pero no va a causar que se rechace ninguna carga.
+
+`configuration_url` podría ser un enlace a esta terminal o ser la configuración global de este gancho. Solo los administradores de sistema pueden acceder a la configuración global.
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/rest-reference/enterprise-admin/orgs.md b/translations/es-ES/data/reusables/rest-reference/enterprise-admin/orgs.md
new file mode 100644
index 000000000000..48b19a508fd0
--- /dev/null
+++ b/translations/es-ES/data/reusables/rest-reference/enterprise-admin/orgs.md
@@ -0,0 +1,3 @@
+## Organizaciones
+
+La API de Administración Organizacional te permite crear organizaciones en tu empresa. *Solo se encuentra disponible para los administradores de sitio [autenticados.](/rest/overview/resources-in-the-rest-api#authentication)* Los usuarios normales recibirán una respuesta `404` si intentan acceder a ella.
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/rest-reference/enterprise-admin/pre-receive-environments.md b/translations/es-ES/data/reusables/rest-reference/enterprise-admin/pre-receive-environments.md
new file mode 100644
index 000000000000..c24fd48cb5b9
--- /dev/null
+++ b/translations/es-ES/data/reusables/rest-reference/enterprise-admin/pre-receive-environments.md
@@ -0,0 +1,25 @@
+## Ambientes de pre-recepción
+
+La API de Ambientes de Pre-recepción te permite crear, listar, actualizar y borrar ambientes para los ganchos de pre-recepción. *Solo se encuentra disponible para los administradores de sitio [autenticados.](/rest/overview/resources-in-the-rest-api#authentication)* Los usuarios normales recibirán una respuesta `404` si intentan acceder a ella.
+
+### Atributos de objeto
+
+#### Ambiente de pre-recepción
+
+| Nombre | Tipo | Descripción |
+| --------------------- | ----------- | --------------------------------------------------------------------------------------------------- |
+| `name (nombre)` | `secuencia` | El nombre del ambiente como se muestra en la IU. |
+| `image_url` | `secuencia` | La URL del tarball que se descargará y extraerá. |
+| `default_environment` | `boolean` | Si este es el ambiente predeterminado que viene con {% data variables.product.product_name %} o no. |
+| `download` | `objeto` | El estado de descarga de este ambiente. |
+| `hooks_count` | `número` | La cantidad de ganchos de pre-recepción que utilizan este ambiente. |
+
+#### Descarga del Ambiente de Pre-recepción
+
+| Nombre | Tipo | Descripción |
+| --------------- | ----------- | -------------------------------------------------------------------------------- |
+| `state` | `secuencia` | El estado de la mayoría de las descargas recientes. |
+| `downloaded_at` | `secuencia` | La hora en la cual iniciaron la mayoría de las descrgas recientes. |
+| `message` | `secuencia` | Cuando algo falla, este tendrá cualquier mensaje de error que se haya producido. |
+
+Los valores posibles para `state` son `not_started`, `in_progress`, `success`, `failed`.
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/rest-reference/enterprise-admin/pre-receive-hooks.md b/translations/es-ES/data/reusables/rest-reference/enterprise-admin/pre-receive-hooks.md
new file mode 100644
index 000000000000..60117b440f06
--- /dev/null
+++ b/translations/es-ES/data/reusables/rest-reference/enterprise-admin/pre-receive-hooks.md
@@ -0,0 +1,18 @@
+## Ganchos de pre-recepción
+
+La API de Ganchos Pre-recepción te permite crear, listar, actualizar y borrar los ganchos de pre-recepción. *Solo se encuentra disponible para los administradores de sitio [autenticados.](/rest/overview/resources-in-the-rest-api#authentication)* Los usuarios normales recibirán una respuesta `404` si intentan acceder a ella.
+
+### Atributos de objeto
+
+#### Ganchos de pre-recepción
+
+| Nombre | Tipo | Descripción |
+| -------------------------------- | ----------- | ----------------------------------------------------------------------------------- |
+| `name (nombre)` | `secuencia` | El nombre del gancho. |
+| `script` | `secuencia` | El script que ejecuta el gancho. |
+| `script_repository` | `objeto` | El repositorio de GitHub en donde se mantiene el script. |
+| `environment` | `objeto` | El ambiente de pre-recepción en donde se ejecuta el script. |
+| `enforcement` | `secuencia` | El estado de las imposiciones para este gancho. |
+| `allow_downstream_configuration` | `boolean` | Si las imposiciones pueden o no ignorarse a nivel de organización o de repositorio. |
+
+Los valores posibles para *enforcement* son `enabled`, `disabled` y `testing`. El valor `disabled` indica que el gancho de pre-recepción no se ejecutará. El valor `enabled` indica que se ejecutará y rechazará cualquier carga que resulte en un estado diferente a zero. El valor `testing` indica que el script va a ejecutarse pero no va a causar que se rechace ninguna carga.
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/rest-reference/enterprise-admin/repo-pre-receive-hooks.md b/translations/es-ES/data/reusables/rest-reference/enterprise-admin/repo-pre-receive-hooks.md
new file mode 100644
index 000000000000..bd5fffee21ab
--- /dev/null
+++ b/translations/es-ES/data/reusables/rest-reference/enterprise-admin/repo-pre-receive-hooks.md
@@ -0,0 +1,15 @@
+## Ganchos de pre-recepción del repositorio
+
+La API de Ganchos de Pre-recepción para Repositorios te permite ver y modificar la imposición de los ganchos de pre-recepción que están disponibles para un repositorio.
+
+### Atributos de objeto
+
+| Nombre | Tipo | Descripción |
+| ------------------- | ----------- | --------------------------------------------------------- |
+| `name (nombre)` | `secuencia` | El nombre del gancho. |
+| `enforcement` | `secuencia` | El estado de imposición del gancho en este repositorio. |
+| `configuration_url` | `secuencia` | URL para la terminal en donde se configuró la imposición. |
+
+Los valores posibles para *enforcement* son `enabled`, `disabled` y `testing`. El valor `disabled` indica que el gancho de pre-recepción no se ejecutará. El valor `enabled` indica que se ejecutará y rechazará cualquier carga que resulte en un estado diferente a zero. El valor `testing` indica que el script va a ejecutarse pero no va a causar que se rechace ninguna carga.
+
+`configuration_url` podría ser un enlace a este repositorio, al propietario de su organización o a su configuración global. La autorización para acceder a esta terminal en `configuration_url` se determina a nivel de administrador de sitio o de propietario.
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/rest-reference/enterprise-admin/users.md b/translations/es-ES/data/reusables/rest-reference/enterprise-admin/users.md
new file mode 100644
index 000000000000..3ab880ffb144
--- /dev/null
+++ b/translations/es-ES/data/reusables/rest-reference/enterprise-admin/users.md
@@ -0,0 +1,3 @@
+## Usuarios
+
+La API de Administración de Usuarios te permite suspender{% ifversion ghes %}, dejar de suspender, promover, y degradar{% endif %}{% ifversion ghae %} y dejar de suspender{% endif %} a los usuarios en tu empresa. *Solo se encuentra disponible para los administradores de sitio [autenticados.](/rest/overview/resources-in-the-rest-api#authentication)* Los usuarios normales recibirán una respuesta `403` si intentan acceder a ella.
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/rest-reference/gists/comments.md b/translations/es-ES/data/reusables/rest-reference/gists/comments.md
new file mode 100644
index 000000000000..62f10d6ad2b0
--- /dev/null
+++ b/translations/es-ES/data/reusables/rest-reference/gists/comments.md
@@ -0,0 +1,10 @@
+## Comentarios
+
+### Tipos de medios personalizados para los comentarios de los Gists
+
+Estos son los tipos de medios compatibles para los comentarios de los gists.
+
+ application/vnd.github.VERSION.raw
+ application/vnd.github.VERSION.base64
+
+Para obtener más información acerca de los tipos de medios, consulta la sección "[Tipos de medios personalizados](/rest/overview/media-types)".
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/rest-reference/gists/gists.md b/translations/es-ES/data/reusables/rest-reference/gists/gists.md
new file mode 100644
index 000000000000..db375a869b09
--- /dev/null
+++ b/translations/es-ES/data/reusables/rest-reference/gists/gists.md
@@ -0,0 +1,22 @@
+### Autenticación
+
+Puedes leer gists públicos {% ifversion ghae or ghes %}y crearlos para usuarios anónimos sin un token{% else %} de forma anónima, pero debes haber iniciado sesión en GitHub para crear gists.{% endif %} Para leer o escribir gists en nombre de un usuario, necesitas el alcance de OAuth para gists y un token. Par aobtener más información, consulta la sección "[Alcances para las Apps de OAuth](/developers/apps/scopes-for-oauth-apps)".
+
+
+
+### Truncamiento
+
+La API de Gist proporciona hasta un megabyte de contenido para cada archivo en el gist. Cada archivo que se devuelve para un gist a través de la API tiene una clave que se llama `truncated`. Si `truncated` aparece como `true`, significa que el archivo es demasiado grande y solo se devolvió una parte de su contenido en `content`.
+
+Si necesitas el contenido completo del archivo, puedes hacer una solicitud de tipo `GET` a la URL que se especifica en `raw_url`. Ten en cuent que, para los archivos mayores a diez megabytes, necesitarás clonar el gist a través de la URL que proprocionó `git_pull_url`.
+
+Adicionalmente a el truncamiento del contenido específico del archivo, la lista de archivos completa podría truncarse si la cantidad total excede los 300 archivos. Si la clave `truncated` de nivel superior aparece como `true`, únicamente se han devuelto los primeros 300 archivos en la lista. Si necesitas recuperar todos los archivos del gist, necesitarás clonarlo a través de la URL que te proporcionó `git_pull_url`.
+
+### Tipos de medios personalizados para los gists
+
+Estos son los tipos de medios compatibles para recuperar el contenido de los gists.
+
+ application/vnd.github.VERSION.raw
+ application/vnd.github.VERSION.base64
+
+Para obtener más información, consulta la sección "[Tipos de medios](/rest/overview/media-types)".
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/rest-reference/git/blobs.md b/translations/es-ES/data/reusables/rest-reference/git/blobs.md
new file mode 100644
index 000000000000..f342643bf9b9
--- /dev/null
+++ b/translations/es-ES/data/reusables/rest-reference/git/blobs.md
@@ -0,0 +1,12 @@
+## Blobs
+
+Un blob (objeto binario grande, por sus siglas en inglés) de Git es el tipo de objeto que se utiliza para almacenar el contenido de cada archivo en un repositorio. El hash SHA-1 del archivo se calcula y almacena en el objeto del blob. Estas terminales te permiten leer y escribir [objetos de blob](https://git-scm.com/book/en/v1/Git-Internals-Git-Objects) en tu base de datos de Git en {% data variables.product.product_name %}. Los blobs aprovechan [estos tipos de medios personalizados](#custom-media-types-for-blobs). Puedes leer más acerca del uso de tipos de medios en la API [aquí](/rest/overview/media-types).
+
+### Tipos de medios personalizados para los blobs
+
+Estos son los tipos de medios compatibles para los blobs.
+
+ application/json
+ application/vnd.github.VERSION.raw
+
+Para obtener más información, consulta la sección "[Tipos de medios](/rest/overview/media-types)".
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/rest-reference/git/commits.md b/translations/es-ES/data/reusables/rest-reference/git/commits.md
new file mode 100644
index 000000000000..754a9d15b736
--- /dev/null
+++ b/translations/es-ES/data/reusables/rest-reference/git/commits.md
@@ -0,0 +1,3 @@
+## Confirmaciones
+
+Una confirmación de Git es una impresión de pantalla de la jerarquía ([árbol de Git](/rest/reference/git#trees)) y del contenido de los archivos ([blob de Git](/rest/reference/git#blobs)) en un reposiotorio de Git. Estas terminales te permiten leer y escribir [objetos de confirmación](https://git-scm.com/book/en/v1/Git-Internals-Git-Objects#Commit-Objects) en tu base de datos en {% data variables.product.product_name %}.
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/rest-reference/git/git.md b/translations/es-ES/data/reusables/rest-reference/git/git.md
new file mode 100644
index 000000000000..df61c8ef7237
--- /dev/null
+++ b/translations/es-ES/data/reusables/rest-reference/git/git.md
@@ -0,0 +1 @@
+La API de la Base de datos de Git te da acceso de escritura y lectora para los objetos sin procesar de Git que se encuentran en tu base de datos de Git en {% data variables.product.product_name %} y para listar y actualizar tus referencias (cabezas de rama y etiquetas). Para obtener más información acerca de utilizar la API de la Base de Datos de Git, consulta la secicón "[Empezar con la API de datos de Git](/rest/guides/getting-started-with-the-git-database-api)".
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/rest-reference/git/refs.md b/translations/es-ES/data/reusables/rest-reference/git/refs.md
new file mode 100644
index 000000000000..0d2cf90c8373
--- /dev/null
+++ b/translations/es-ES/data/reusables/rest-reference/git/refs.md
@@ -0,0 +1,3 @@
+## Referencias
+
+Una referencia (`git ref`) es simplemente un archivo que contiene un hash SHA-1 de una confirmación de Git. Cuando te refieres a una confirmación de Git, puedes utilizar la referencia de Git, la cual es un nombre fácil de recordar, en vez de utilizar el hash. La referencia de Git puede reescribirse para apuntar a una confirmación nueva. Una rama es solo una referencia de Git que almacena el hash de la confirmación de Git nueva. Estas terminales te permiten leer y escribir [referencias](https://git-scm.com/book/en/v1/Git-Internals-Git-References) en tu base de datos de Git en {% data variables.product.product_name %}.
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/rest-reference/git/tags.md b/translations/es-ES/data/reusables/rest-reference/git/tags.md
new file mode 100644
index 000000000000..fd923e55f90f
--- /dev/null
+++ b/translations/es-ES/data/reusables/rest-reference/git/tags.md
@@ -0,0 +1,3 @@
+## Etiquetas
+
+Una etiqueta de git es similar a una [referencia de Git](/rest/reference/git#refs), pero la confirmación de Git a la que apunta jamás cambia. Las etiquetas de git son útiles cuando quieres apuntar a algún lanzamiento específico. Estas terminales te permiten leer y escribir [objetos de etiquetas](https://git-scm.com/book/en/v1/Git-Internals-Git-References#Tags)en tu base de datos de Git en {% data variables.product.product_name %}. La API de etiquetas de Git son compatibles únicamente con los [objetos de etiqueta anotados](https://git-scm.com/book/en/v1/Git-Internals-Git-References#Tags), no con etiquetas ligeras.
diff --git a/translations/es-ES/data/reusables/rest-reference/git/trees.md b/translations/es-ES/data/reusables/rest-reference/git/trees.md
new file mode 100644
index 000000000000..480439c28f63
--- /dev/null
+++ b/translations/es-ES/data/reusables/rest-reference/git/trees.md
@@ -0,0 +1,3 @@
+## Árboles
+
+Un objeto de árbol de Git crea la jerarquía entre archivos para un repositorio de Git. Puedes utilizar el objeto de árbol de Git para crear una relación entre directorios y entre los archivos que contienen. Estas terminales te permiten leer y escribir [objetos de árbol](https://git-scm.com/book/en/v1/Git-Internals-Git-Objects#Tree-Objects)en tu base de datos de Git en {% data variables.product.product_name %}.
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/rest-reference/gitignore/gitignore.md b/translations/es-ES/data/reusables/rest-reference/gitignore/gitignore.md
new file mode 100644
index 000000000000..2da3a2f14ff2
--- /dev/null
+++ b/translations/es-ES/data/reusables/rest-reference/gitignore/gitignore.md
@@ -0,0 +1,9 @@
+Cuando creas un repositorio nuevo en {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} a través de la API, puedes especificar una [plantilla de.gitignore](/github/getting-started-with-github/ignoring-files) para aplicarla al repositorio cuando lo crees. La API de plantillas de .gitignore lista y recupera plantillas del [repositorio de .gitignore](https://github.com/github/gitignore) de {% data variables.product.product_name %}.
+
+### Tipos de medios personalizados para gitignore
+
+Puedes utilizar este tipo de medios personalizado cuando obtengas una plantilla de gitignore.
+
+ application/vnd.github.VERSION.raw
+
+Para obtener más información, consulta la sección "[Tipos de medios](/rest/overview/media-types)".
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/rest-reference/interactions/interactions.md b/translations/es-ES/data/reusables/rest-reference/interactions/interactions.md
new file mode 100644
index 000000000000..dc2cb8e136d3
--- /dev/null
+++ b/translations/es-ES/data/reusables/rest-reference/interactions/interactions.md
@@ -0,0 +1 @@
+Los usuarios interactuan con los repositorios al comentar, abrir informes de problemas y crear solicitudes de extracción. La API de interacciones permite a las personas con acceso de propietario o de administrador restringir la interacción con los repositorios públicos temporalmente a un tipo específico de usuario.
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/rest-reference/interactions/orgs.md b/translations/es-ES/data/reusables/rest-reference/interactions/orgs.md
new file mode 100644
index 000000000000..c6187738444a
--- /dev/null
+++ b/translations/es-ES/data/reusables/rest-reference/interactions/orgs.md
@@ -0,0 +1,9 @@
+## Organización
+
+La API de Interacciones Organizacionales permite a los propietarios el restringir temporalmente qué tipo de usuariopuede comentar, abrir propuestas, o crear solicitudes de cambios en los repositorios públicos de la organización. {% data reusables.interactions.interactions-detail %} Aquí puedes aprender más sobre los tipos de usuario de {% data variables.product.product_name %}:
+
+* {% data reusables.interactions.existing-user-limit-definition %} en la organización.
+* {% data reusables.interactions.contributor-user-limit-definition %} en la organización.
+* {% data reusables.interactions.collaborator-user-limit-definition %} en la organización.
+
+Configurar el límite de interacciones a nivel organizacional sobreescribirá cualquier límite de interacción que se haya configurado para los repositorios individuales que pertenezcan a la organización. Para configurar los límites de interacción para los repositorios individuales que pertenezcan a la organización, mejor utiliza la terminal de interaciones del [Repositorio](#repository).
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/rest-reference/interactions/repos.md b/translations/es-ES/data/reusables/rest-reference/interactions/repos.md
new file mode 100644
index 000000000000..f5a19d13951f
--- /dev/null
+++ b/translations/es-ES/data/reusables/rest-reference/interactions/repos.md
@@ -0,0 +1,9 @@
+## Repositorio
+
+La API de interacciones de repositorio permite a las personas con acceso administrativo o de propietario restringir temporalmente qué tipo de usuario puede comentar, abrir propuestas, o crear solicitudes de cambios en un repositorio privado. {% data reusables.interactions.interactions-detail %} Aquí puedes aprender más sobre los tipos de usuario de {% data variables.product.product_name %}:
+
+* {% data reusables.interactions.existing-user-limit-definition %} en el repositorio.
+* {% data reusables.interactions.contributor-user-limit-definition %} en el repositorio.
+* {% data reusables.interactions.collaborator-user-limit-definition %} en el repositorio.
+
+Si se habilita un límite de interacción para el usuario u organización a la que pertenece el repositorio, éste no podrá cambiarse para el repositorio individual. En su lugar, utiliza las terminales de interacciones de [Usuario](#user) o de [Organización](#organization) para cambiar el límite de interacción.
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/rest-reference/interactions/users.md b/translations/es-ES/data/reusables/rest-reference/interactions/users.md
new file mode 100644
index 000000000000..36171434ec51
--- /dev/null
+++ b/translations/es-ES/data/reusables/rest-reference/interactions/users.md
@@ -0,0 +1,9 @@
+## Usuario
+
+The User Interactions API allows you to temporarily restrict which type of user can comment, open issues, or create pull requests on your public repositories. {% data reusables.interactions.interactions-detail %} Aquí puedes aprender más sobre los tipos de usuario de {% data variables.product.product_name %}:
+
+* {% data reusables.interactions.existing-user-limit-definition %} from interacting with your repositories.
+* {% data reusables.interactions.contributor-user-limit-definition %} from interacting with your repositories.
+* {% data reusables.interactions.collaborator-user-limit-definition %} from interacting with your repositories.
+
+Setting the interaction limit at the user level will overwrite any interaction limits that are set for individual repositories owned by the user. To set different interaction limits for individual repositories owned by the user, use the [Repository](#repository) interactions endpoints instead.
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/rest-reference/issues/assignees.md b/translations/es-ES/data/reusables/rest-reference/issues/assignees.md
new file mode 100644
index 000000000000..47096cc770d6
--- /dev/null
+++ b/translations/es-ES/data/reusables/rest-reference/issues/assignees.md
@@ -0,0 +1 @@
+## Asignatarios
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/rest-reference/issues/comments.md b/translations/es-ES/data/reusables/rest-reference/issues/comments.md
new file mode 100644
index 000000000000..ef7a4d2ba178
--- /dev/null
+++ b/translations/es-ES/data/reusables/rest-reference/issues/comments.md
@@ -0,0 +1,5 @@
+## Comentarios
+
+La API de Comentarios par los Informes de Problemas es compatible con listar, ver, editar y crear comentarios en informes de problemas y solicitudes de extracción.
+
+Los comentarios de los informes de problemas utilizan [estos tipos de medios personalizados](#custom-media-types). Puedes leer más acerca del uso de tipos de medios en la API [aquí](/rest/overview/media-types).
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/rest-reference/issues/events.md b/translations/es-ES/data/reusables/rest-reference/issues/events.md
new file mode 100644
index 000000000000..655f3d2cad2a
--- /dev/null
+++ b/translations/es-ES/data/reusables/rest-reference/issues/events.md
@@ -0,0 +1,3 @@
+## Eventos
+
+The Issue Events API can return different types of events triggered by activity in issues and pull requests. For more information about the specific events that you can receive from the Issue Events API, see "[Issue event types](/developers/webhooks-and-events/issue-event-types)." Para obtener más información acerca de los eventos específicos que puedes recibir de la API de Eventos para Solicitudes de Extracción, consulta la sección "[Tipos de evento de las Solicitudes de Extracción](/developers/webhooks-and-events/issue-event-types)". For more information, see the "[Events API](/developers/webhooks-and-events/github-event-types)."
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/rest-reference/issues/issues.md b/translations/es-ES/data/reusables/rest-reference/issues/issues.md
new file mode 100644
index 000000000000..e00a237fd68b
--- /dev/null
+++ b/translations/es-ES/data/reusables/rest-reference/issues/issues.md
@@ -0,0 +1,10 @@
+### Tipos de mendios personalizados para los informes de problemas
+
+Estos son los tipos de medios compatibles para los informes de problemas.
+
+ application/vnd.github.VERSION.raw+json
+ application/vnd.github.VERSION.text+json
+ application/vnd.github.VERSION.html+json
+ application/vnd.github.VERSION.full+json
+
+Para obtener más información acerca de los tipos de medios, consulta la sección "[Tipos de medios personalizados](/rest/overview/media-types)".
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/rest-reference/issues/labels.md b/translations/es-ES/data/reusables/rest-reference/issues/labels.md
new file mode 100644
index 000000000000..e01b345a6b03
--- /dev/null
+++ b/translations/es-ES/data/reusables/rest-reference/issues/labels.md
@@ -0,0 +1 @@
+## Etiquetas
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/rest-reference/issues/milestones.md b/translations/es-ES/data/reusables/rest-reference/issues/milestones.md
new file mode 100644
index 000000000000..7b1f8111a112
--- /dev/null
+++ b/translations/es-ES/data/reusables/rest-reference/issues/milestones.md
@@ -0,0 +1 @@
+## Hitos
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/rest-reference/issues/timeline.md b/translations/es-ES/data/reusables/rest-reference/issues/timeline.md
new file mode 100644
index 000000000000..23dd997ca9f9
--- /dev/null
+++ b/translations/es-ES/data/reusables/rest-reference/issues/timeline.md
@@ -0,0 +1,5 @@
+## Línea de tiempo
+
+La API de eventos para la línea de tiempo puede devolver diferentes tipos de eventos que se activan de acuerdo a la actividad de la línea de tiempo en los informes de problemas y solicitudes de extracción. For more information about the specific events that you can receive from the Issue Events API, see "[Issue event types](/developers/webhooks-and-events/issue-event-types)." Para obtener más información acerca de los eventos específicos que puedes recibir de la API de Eventos para Solicitudes de Extracción, consulta la sección "[Tipos de evento de las Solicitudes de Extracción](/developers/webhooks-and-events/issue-event-types)". Para obtener más información, consulta la "[API de Eventos de GitHub](/developers/webhooks-and-events/github-event-types)".
+
+Puedes utilizar esta API para mostrar información sobre los informes de problemas y solicitudes de extracción o para determinar a quién debería notificársele sobre los comentarios en los informes de problemas.
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/rest-reference/licenses/licenses.md b/translations/es-ES/data/reusables/rest-reference/licenses/licenses.md
new file mode 100644
index 000000000000..b589d7db750a
--- /dev/null
+++ b/translations/es-ES/data/reusables/rest-reference/licenses/licenses.md
@@ -0,0 +1,22 @@
+La API de licencias devuelve metadatos acerca de las liciencias de código abierto populares y acerca de la información sobre un archivo de licencia específico de un proyecto.
+
+La API de licencias utiliza [el Licenciatario de código abierto de la Gema de Ruby ](https://github.com/benbalter/licensee) para intentar identificar la licencia del proyecto. Este licenciatario empata el contenido del archivo de `LICENSE` de un proyecto (si es que existe) contra una lista corta de licencias conocidas. Como resultado, la API no toma en cuenta las licencias de las dependencias del proyecto u otros medios de documentar la licencia de un proyecto tales como las referencias al nombre de la licencia en la documentación.
+
+Si una licencia empata, la llave de licencia y el nombre devuelto se apegan a la [especificación SPDX](https://spdx.org/).
+
+**Nota:** Estas terminales también devolverán la información de licencia de un repositorio:
+
+- [Obtener un repositorio](/rest/reference/repos#get-a-repository)
+- [Listar los repositorios para un usuario](/rest/reference/repos#list-repositories-for-a-user)
+- [Listar los repositorios de una organización](/rest/reference/repos#list-organization-repositories)
+- [Listar las bifurcaciones](/rest/reference/repos#list-forks)
+- [Listar los repositorios que el usuario está observando](/rest/reference/activity#list-repositories-watched-by-a-user)
+- [Listar los repositorios de equipo](/rest/reference/teams#list-team-repositories)
+
+{% warning %}
+
+GitHub puede ser muchas cosas, pero no es un buró legal. Como tal, GitHub no proporcional consejo legal. Al utilizar la API de licencias o al enviarnos un mensaje de correo electrónico acerca de ellas no estás incurriendo en ningún consejo legal ni creando una relación abogado-cliente. Si tienes cualquier pregunta acerca de lo que puedes o no hacer con una licencia específica, debes acudir a tu propio consejero legal antes de continuar. De hecho, siempre debes consultar con tu propio abogado antes de que decidas tomar cualquier decisión que pudiera tener implicaciones legales o que pudiera impactar tus derechos.
+
+GitHub creó la API de Licencias para ayudar a los usuarios a obtener información acerca de las licencias de código abierto y de los proyectos que las utilizan. Esperamos que te sea útil, pero ten presente que no somos abogados (por lo menos, la mayoría de nosotros no lo somos) y que cometemos errores como todo el mundo. Es por esto que GitHub proporciona la API "tal como está" y no da ninguna garantía de cualquier tipo de información o licencias que se proporcionen en o a través de ella y se deslinda de cualquier responsabilidad derivada de los daños que pudiesen resultar de su uso.
+
+{% endwarning %}
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/rest-reference/metrics/community.md b/translations/es-ES/data/reusables/rest-reference/metrics/community.md
new file mode 100644
index 000000000000..46e5605242ef
--- /dev/null
+++ b/translations/es-ES/data/reusables/rest-reference/metrics/community.md
@@ -0,0 +1 @@
+## Comunidad
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/rest-reference/metrics/statistics.md b/translations/es-ES/data/reusables/rest-reference/metrics/statistics.md
new file mode 100644
index 000000000000..8f7fd486a6a3
--- /dev/null
+++ b/translations/es-ES/data/reusables/rest-reference/metrics/statistics.md
@@ -0,0 +1,17 @@
+## Estadísticas
+
+La API de Estadísticas del Repositorio te permite recuperar los datos que {% data variables.product.product_name %} utiliza para visualizar los diferentes tipos de actividad del repositorio.
+
+### Unas palabras sobre el almacenamiento en caché
+
+El calcular las estadísitcas del repositorio es una operación costosa, así que intentamos devolver los datos almacenados en caché cuando nos es posible. Si los datos no se han almacenado en caché cuando consultas la estadística de un repositorio, recibirás una respuesta `202`; también se dispara un job en segundo plano para comenzar a compilar estas estadísticas. Permite que el job se complete, y luego emite la solicitud nuevamente. Si el job ya terminó, esa solicitud recibirá una respuesta `200` con la estadística en el cuerpo de la respuesta.
+
+El SHA de la rama predeterminada del repositorio guarda en caché las estadísticas del repositorio; el subir información a la rama predeterminada restablece el caché de de las estadísticas.
+
+### Las estadísticas excluyen algunos tipos de confirmaciones
+
+Las estadísticas que expone la API empatan con aquellas que muestran [diversas gráficas del repositorio](/github/visualizing-repository-data-with-graphs/about-repository-graphs).
+
+Para resumir:
+- Todas las estadísticas excluyen las confirmaciones de fusión.
+- Las estadísticas del colaborador también excluyen a las confirmaciones vacías.
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/rest-reference/metrics/traffic.md b/translations/es-ES/data/reusables/rest-reference/metrics/traffic.md
new file mode 100644
index 000000000000..9a8fa46a8c15
--- /dev/null
+++ b/translations/es-ES/data/reusables/rest-reference/metrics/traffic.md
@@ -0,0 +1,3 @@
+## Tráfico
+
+Para los repositorios en los que tienes acceso de carga, la API de tráfico proporciona acceso a la información proporcionada en tu gráfica de repositorio. Para obtener más información, consulta la sección "Ver el tráfico hacia un repositorio".
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/rest-reference/migrations/orgs.md b/translations/es-ES/data/reusables/rest-reference/migrations/orgs.md
new file mode 100644
index 000000000000..e398a2041a5e
--- /dev/null
+++ b/translations/es-ES/data/reusables/rest-reference/migrations/orgs.md
@@ -0,0 +1,5 @@
+## Organización
+
+La API de Migraciones solo está disponible para los propietarios autenticados de la organización. Para obtener más información, consulta las secciones "[Roles en una organización](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#permission-levels-for-an-organization)" y "[Otros métodos de autenticación](/rest/overview/other-authentication-methods)".
+
+{% data variables.migrations.organization_migrations_intro %}
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/rest-reference/migrations/source-imports.md b/translations/es-ES/data/reusables/rest-reference/migrations/source-imports.md
new file mode 100644
index 000000000000..efbf589793fc
--- /dev/null
+++ b/translations/es-ES/data/reusables/rest-reference/migrations/source-imports.md
@@ -0,0 +1,80 @@
+## Importaciones de Código Fuente
+
+{% data variables.migrations.source_imports_intro %}
+
+Una importación de código fuente habitual inicia la importación y luego actualiza (opcionalmente) a los autores y/o actualiza las preferencias para utilizar el LFS de Ggit si existen archivos grandes en la importación. También puedes crear un webhook que escuche al [`RepositoryImportEvent`](/developers/webhooks-and-events/webhook-events-and-payloads#repository_import) para encontrar el estado de la importación.
+
+Se puede ver un ejemplo más detallado en este diagrama:
+
+```
++---------+ +--------+ +---------------------+
+| Tooling | | GitHub | | Original Repository |
++---------+ +--------+ +---------------------+
+ | | |
+ | Start import | |
+ |----------------------------->| |
+ | | |
+ | | Download source data |
+ | |--------------------------------------------->|
+ | | Begin streaming data |
+ | |<---------------------------------------------|
+ | | |
+ | Get import progress | |
+ |----------------------------->| |
+ | "status": "importing" | |
+ |<-----------------------------| |
+ | | |
+ | Get commit authors | |
+ |----------------------------->| |
+ | | |
+ | Map a commit author | |
+ |----------------------------->| |
+ | | |
+ | | |
+ | | Finish streaming data |
+ | |<---------------------------------------------|
+ | | |
+ | | Rewrite commits with mapped authors |
+ | |------+ |
+ | | | |
+ | |<-----+ |
+ | | |
+ | | Update repository on GitHub |
+ | |------+ |
+ | | | |
+ | |<-----+ |
+ | | |
+ | Map a commit author | |
+ |----------------------------->| |
+ | | Rewrite commits with mapped authors |
+ | |------+ |
+ | | | |
+ | |<-----+ |
+ | | |
+ | | Update repository on GitHub |
+ | |------+ |
+ | | | |
+ | |<-----+ |
+ | | |
+ | Get large files | |
+ |----------------------------->| |
+ | | |
+ | opt_in to Git LFS | |
+ |----------------------------->| |
+ | | Rewrite commits for large files |
+ | |------+ |
+ | | | |
+ | |<-----+ |
+ | | |
+ | | Update repository on GitHub |
+ | |------+ |
+ | | | |
+ | |<-----+ |
+ | | |
+ | Get import progress | |
+ |----------------------------->| |
+ | "status": "complete" | |
+ |<-----------------------------| |
+ | | |
+ | | |
+```
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/rest-reference/migrations/users.md b/translations/es-ES/data/reusables/rest-reference/migrations/users.md
new file mode 100644
index 000000000000..f983d6a60e4d
--- /dev/null
+++ b/translations/es-ES/data/reusables/rest-reference/migrations/users.md
@@ -0,0 +1,9 @@
+## Usuario
+
+La API de migraciones de usuario solo está disponible para los propietarios de cuentas autenticadas. Para obtener más información, consulta la sección "[Otros métodos de autenticación](/rest/overview/other-authentication-methods)".
+
+{% data variables.migrations.user_migrations_intro %} Para encontrar una lista descargable de datos de migración, consulta "[Descarga un archivo de migración de usuario](#download-a-user-migration-archive)".
+
+Antes de descargar un archivo deberás iniciar la migración del usuario. Una vez que el estado de la migración sea `exported`, podrás descargarla.
+
+Ya que hayas creado el archivo de migración, este estará disponible para su descarga por siete días. Pero puedes borrar el archivo de migración del usuario antes si lo prefieres. Puedes desbloquear tu repositorio cuando la migración aparezca como `exported` para comenzar a utilizar tu repositorio nuevamente o borrarlo si ya no necesitas los datos del código fuente.
diff --git a/translations/es-ES/data/reusables/rest-reference/oauth-authorizations/oauth-authorizations.md b/translations/es-ES/data/reusables/rest-reference/oauth-authorizations/oauth-authorizations.md
new file mode 100644
index 000000000000..9d685491d0a0
--- /dev/null
+++ b/translations/es-ES/data/reusables/rest-reference/oauth-authorizations/oauth-authorizations.md
@@ -0,0 +1,3 @@
+Puedes utilizar esta API para administrar el acceso que las aplicaciones de OAuth tienen en tu cuenta. Solo puedes acceder a esta API a través de la [Autenticación Básica](/rest/overview/other-authentication-methods#basic-authentication) utilizando tu nombre de usuario y contraseña, y no los tokens.
+
+Si tú o tus usuarios habilitaron la autenticación de dos factores, asegúrate de que entiendes cómo [trabajar con la autenticación de dos factores](/rest/overview/other-authentication-methods#working-with-two-factor-authentication).
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/rest-reference/orgs/blocking.md b/translations/es-ES/data/reusables/rest-reference/orgs/blocking.md
new file mode 100644
index 000000000000..068c581d94d8
--- /dev/null
+++ b/translations/es-ES/data/reusables/rest-reference/orgs/blocking.md
@@ -0,0 +1,3 @@
+## Bloquear usuarios
+
+El token que se utiliza para autenticar la llamada debe tener el alcance de `admin:org` para poder hacer cualquier llamada de bloqueo para una organización. De lo contrario, la respuesta devolverá un `HTTP 404`.
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/rest-reference/orgs/custom_roles.md b/translations/es-ES/data/reusables/rest-reference/orgs/custom_roles.md
new file mode 100644
index 000000000000..0aa1f4005377
--- /dev/null
+++ b/translations/es-ES/data/reusables/rest-reference/orgs/custom_roles.md
@@ -0,0 +1 @@
+## Roles de repositorio personalizados
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/rest-reference/orgs/members.md b/translations/es-ES/data/reusables/rest-reference/orgs/members.md
new file mode 100644
index 000000000000..03067453c099
--- /dev/null
+++ b/translations/es-ES/data/reusables/rest-reference/orgs/members.md
@@ -0,0 +1 @@
+## Miembros
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/rest-reference/orgs/outside-collaborators.md b/translations/es-ES/data/reusables/rest-reference/orgs/outside-collaborators.md
new file mode 100644
index 000000000000..e4b68bef01f8
--- /dev/null
+++ b/translations/es-ES/data/reusables/rest-reference/orgs/outside-collaborators.md
@@ -0,0 +1 @@
+## Colaboradores externos
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/rest-reference/orgs/webhooks.md b/translations/es-ES/data/reusables/rest-reference/orgs/webhooks.md
new file mode 100644
index 000000000000..de0834e0b127
--- /dev/null
+++ b/translations/es-ES/data/reusables/rest-reference/orgs/webhooks.md
@@ -0,0 +1,24 @@
+## Webhooks
+
+Los webhooks de las organizaciones te permiten recibir cargas útiles de `POST` por HTTP cuando ciertos eventos suceden en una organización. {% data reusables.webhooks.webhooks-rest-api-links %}
+
+Para obtener más información sobre las acciones a las cuales te puedes suscribir, consulta los "[tipos de eventos de {% data variables.product.prodname_dotcom %}](/developers/webhooks-and-events/github-event-types)".
+
+### Alcances & Restricciones
+
+Todas las acciones en contra de los webhooks de una organización requieren que el usuario autenticado sea un administrador de la organización que se está administrando. Adicionalmente, los tokens de OAuth requieren el alcance `admin:org_hook`. Par aobtener más información, consulta la sección "[Alcances para las Apps de OAuth](/developers/apps/scopes-for-oauth-apps)".
+
+Para porteger los datos sensibles que pueden encontrarse en las configuraciones de los webhooks, también imponemos las siguientes reglas de control de accesos:
+
+- Las aplicaciones de OAuth no pueden listar, ver o editar los webhooks que no crearon ellas mismas.
+- Los usuarios no pueden listar, ver o editar los webhooks que crearon las aplicaciones de OAuth.
+
+### Recibir Webhooks
+
+Para que {% data variables.product.product_name %} envíe cargas útiles de webhooks, se necesita que se pueda acceder a tu servidor desde la internet. También sugerimos ampliamente utilizar SSL para que podamos enviar cargas útiles cifradas a través de HTTPS.
+
+Para encontrar más de las mejores prácticas, [consulta nuestra guía](/guides/best-practices-for-integrators/).
+
+#### Encabezados de Webhook
+
+{% data variables.product.product_name %} enviará varios encabezados de HTTP para diferenciar los tipos de eventos y los identificadores de las cargas útiles. Consulta la sección de [encabezados de webhook](/webhooks/event-payloads/#delivery-headers) para encontrar más detalles.
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/rest-reference/packages/packages.md b/translations/es-ES/data/reusables/rest-reference/packages/packages.md
new file mode 100644
index 000000000000..834d026e8db6
--- /dev/null
+++ b/translations/es-ES/data/reusables/rest-reference/packages/packages.md
@@ -0,0 +1,10 @@
+La API de {% data variables.product.prodname_registry %} te permite administrar paquetes utilizando la API de REST. Para aprender más sobre cómo restablecer o borrar paquetes, consulta la sección "[Restablecer y borrar paquetes](/packages/learn-github-packages/deleting-and-restoring-a-package)".
+
+Para utilizar esta API, primero tienes que autenticarte utilizando un token de acceso personal.
+ - Para acceder a los metadatos del paquete, tu token debe incluir el alcance `read:packages`.
+ - Para borrar los paquetes y las versiones de paquetes, tu token debe incluir los alcances `read:packages` y `delete:packages`.
+ - Para restablecer los paquetes y sus versiones, tu token debe incluir los alcances de `read:packages` y `write:packages`.
+
+Si tu `package_type` es `npm`, `maven`, `rubygems`, o `nuget`, entonces tu token también debe incluir el alcance `repo`, ya que este hereda los permisos de un repositorio de {% data variables.product.prodname_dotcom %}. Si tu paquete está en el {% data variables.product.prodname_container_registry %}, entonces tu `package_type` es `container` y tu token no necesita el alcance de `repo` para acceder o administrar este `package_type`. Los paquetes de `container` ofrecen permisos granulares separados de un repositorio. Para obtener más información, consulta la sección "[Acerca de los permisos para el {% data variables.product.prodname_registry %}](/packages/learn-github-packages/about-permissions-for-github-packages#about-scopes-and-permissions-for-package-registries)".
+
+Si quieres utilizar la API del {% data variables.product.prodname_registry %} para acceder a los recursos de una organización con el SSO habilitado, entonces debes habilitar el SSO para tu token de acceso personal. Para obtener más información, consulta la sección "[Autorizar un token de acceso personal para utilizarse con el inicio de sesión único de SAML](/github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on){% ifversion fpt %}" en la documentación de {% data variables.product.prodname_ghe_cloud %}.{% else %}".{% endif %}
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/rest-reference/pages/pages.md b/translations/es-ES/data/reusables/rest-reference/pages/pages.md
new file mode 100644
index 000000000000..fcae1be172be
--- /dev/null
+++ b/translations/es-ES/data/reusables/rest-reference/pages/pages.md
@@ -0,0 +1,14 @@
+La API de {% data variables.product.prodname_pages %} recupera información sobre tu configuración de {% data variables.product.prodname_pages %} y sobre los estados de tus compilaciones. Solo los propietarios autenticados pueden acceder a la información sobre el sitio y sobre las compilaciones{% ifversion not ghae %}, incluso si los sitios web son públicos{% endif %}. Para obtener más información, consulta la sección "[Acerca de {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages)".
+
+En las terminales de la API de {% data variables.product.prodname_pages %} que llevan una clave de `status` en su respuesta, el valor puede ser uno de entre los siguientes:
+* `null`: El sitio aún tiene que crearse.
+* `queued`: Se solicitó la compilación, pero no ha iniciado.
+* `building`: La compilación está en curso.
+* `built`: Se creó el sitio.
+* `errored`: Indica que ocurrió un error durante la compilación.
+
+En las terminales de la API de {% data variables.product.prodname_pages %} que devulenven información del sitio de GitHub Pages, las respuestas de JSON incluyen estos campos:
+* `html_url`: La URL absoluta (incluyendo el modelo) del sitio de Páginas que se interpretó. Por ejemplo, `https://username.github.io`.
+* `source`: Un objeto que contiene la rama origen y el directorio del sitio de Páginas que se interpretó. Esto incluye:
+ - `branch`: La rama del repositorio que se utilizó para publicar los [archivos de código fuente de tu sitio](/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site). Por ejemplo, _main_ o _gh-pages_.
+ - `path`: El directorio del repositorio desde el cual publica el sitio. Podría ser `/` o `/docs`.
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/rest-reference/projects/cards.md b/translations/es-ES/data/reusables/rest-reference/projects/cards.md
new file mode 100644
index 000000000000..84415b51acc0
--- /dev/null
+++ b/translations/es-ES/data/reusables/rest-reference/projects/cards.md
@@ -0,0 +1 @@
+## Tarjetas
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/rest-reference/projects/collaborators.md b/translations/es-ES/data/reusables/rest-reference/projects/collaborators.md
new file mode 100644
index 000000000000..240488cd3e79
--- /dev/null
+++ b/translations/es-ES/data/reusables/rest-reference/projects/collaborators.md
@@ -0,0 +1,3 @@
+## Colaboradores
+
+Esta API te permite interactuar con los proyectos de una organización.
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/rest-reference/projects/columns.md b/translations/es-ES/data/reusables/rest-reference/projects/columns.md
new file mode 100644
index 000000000000..05d264f38ab7
--- /dev/null
+++ b/translations/es-ES/data/reusables/rest-reference/projects/columns.md
@@ -0,0 +1 @@
+## Columnas
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/rest-reference/pulls/comments.md b/translations/es-ES/data/reusables/rest-reference/pulls/comments.md
new file mode 100644
index 000000000000..2e537f5fe13b
--- /dev/null
+++ b/translations/es-ES/data/reusables/rest-reference/pulls/comments.md
@@ -0,0 +1,14 @@
+## Comentarios de revisión
+
+Los comentarios de revisión de las solicitudes de extracción son comentarios de una porción de la diff unificada durante la revisión de esta solicitud. Los comentarios de confirmación y comentarios de la solicitud de extracción son diferentes de aquellos sobre la revisión de estas solicitudes. Se aplican comentarios de confirmación directamente a un confirmación, así como se aplican comentarios del informe de problemas sin referenciar una porción de la diff unificada. Para obtener más información, consulta las secciones "[Crear un comentario sobre una confirmación](/rest/reference/commits#create-a-commit-comment)" y "[Crear un comentario sobre un informe de problemas](/rest/reference/issues#create-an-issue-comment)".
+
+### Tipos de medios personalizados para los comentarios sobre las revisiones de las solicitudes de extracción
+
+Estos son los tipos de medios compatibles para los comentarios sobre las revisiones de las solicitudes de exstracción.
+
+ application/vnd.github.VERSION.raw+json
+ application/vnd.github.VERSION.text+json
+ application/vnd.github.VERSION.html+json
+ application/vnd.github.VERSION.full+json
+
+Para obtener más información, consulta la sección "[Tipos de medios personalizados](/rest/overview/media-types)".
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/rest-reference/pulls/pulls.md b/translations/es-ES/data/reusables/rest-reference/pulls/pulls.md
new file mode 100644
index 000000000000..ae6740c5a49f
--- /dev/null
+++ b/translations/es-ES/data/reusables/rest-reference/pulls/pulls.md
@@ -0,0 +1,33 @@
+La API de Solicitudes de Extracción te permite listar, ver, editar, crear e incluso fusionar solicitudes de extracción. Los comentarios en las solicitudes de extracción se pueden administrar a través de la [API de Comentarios de los Informes de Problemas](/rest/reference/issues#comments).
+
+Cada solicitud de extracción es un informe de problemas, pero no todos los informes de problemas son una solicitud de extracción. Es por esto que las acciones "compartidas" para ambas características, como el manipular a los asignados, etiquetas e hitos, se proporcionan dentro de la [API de Informes de Problemas](/rest/reference/issues).
+
+### Tipos de medios personalizados para las solicitudes de extracción
+
+Estos son los tipos de medios compatibles para las solicitudes de extracción.
+
+ application/vnd.github.VERSION.raw+json
+ application/vnd.github.VERSION.text+json
+ application/vnd.github.VERSION.html+json
+ application/vnd.github.VERSION.full+json
+ application/vnd.github.VERSION.diff
+ application/vnd.github.VERSION.patch
+
+Para obtener más información, consulta la sección "[Tipos de medios personalizados](/rest/overview/media-types)".
+
+Si existe alguna diff que se haya dañado, contacta a {% data variables.contact.contact_support %}. Incluye el nombre del repositorio y la ID de la solicitud de extracción en tu mensaje.
+
+### Relaciones de los enlaces
+
+Las solicitudes de extracción tienen estas posibles relaciones de enlaces:
+
+| Nombre | Descripción |
+| ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `self` | La ubicación de la API para esta Solicitud de Extracción. |
+| `html` | La ubicación de HTML para esta Solicitud de Extracción. |
+| `propuesta` | La ubicación de la API para el [informe de problemas](/rest/reference/issues) de esta Solicitud de Extracción. |
+| `comments` | La ubicación de la API para los [Comentarios del informe de problemas](/rest/reference/issues#comments) de esta Solicitud de Extracción. |
+| `review_comments` | La ubicación de la API para los [Comentarios de revisión](/rest/reference/pulls#comments) de esta Solicitud de Extracción. |
+| `review_comment` | La [plantilla de URL](/rest#hypermedia) para construir la ubicación de la API para un [Comentario de revisión](/rest/reference/pulls#comments) en el repositorio de esta Solicitud de Extracción. |
+| `commits` | La ubicación de la API para las [confirmaciones](#list-commits-on-a-pull-request) de esta solicitud de extracción. |
+| `estados` | La ubicación de la API para los [estados de las confirmaciones](/rest/reference/commits#commit-statuses) de esta Solicitud de Extracción, los cuales son los estados de su rama `head`. |
diff --git a/translations/es-ES/data/reusables/rest-reference/pulls/review-requests.md b/translations/es-ES/data/reusables/rest-reference/pulls/review-requests.md
new file mode 100644
index 000000000000..26ef3c0781bc
--- /dev/null
+++ b/translations/es-ES/data/reusables/rest-reference/pulls/review-requests.md
@@ -0,0 +1,3 @@
+## Solicitudes de revisión
+
+Los autores de las solicitudes de extracción y los propietarios y colaboradores de los repositorios pueden solicitar una revisión de una solicitud de extracción a cualquiera con acceso de escritura en el repositorio. Cada revisor solicitado recibirá una notificación solicitándoles revisar la solicitud de extracción.
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/rest-reference/pulls/reviews.md b/translations/es-ES/data/reusables/rest-reference/pulls/reviews.md
new file mode 100644
index 000000000000..410c23d6b67b
--- /dev/null
+++ b/translations/es-ES/data/reusables/rest-reference/pulls/reviews.md
@@ -0,0 +1,3 @@
+## Revisiones
+
+Las revisiones de las solicitudes de extracción son grupos de Comentarios de Revisión de las Solicitudes de Extracción en las mismas, los cuales se agrupan con un estado y, opcionalmente, con un comentario en el cuerpo.
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/rest-reference/rate-limit/rate-limit.md b/translations/es-ES/data/reusables/rest-reference/rate-limit/rate-limit.md
new file mode 100644
index 000000000000..7b2919881f9a
--- /dev/null
+++ b/translations/es-ES/data/reusables/rest-reference/rate-limit/rate-limit.md
@@ -0,0 +1,17 @@
+La documentación general de la API de REST describe las [reglas de los límites de tasa](/rest/overview/resources-in-the-rest-api#rate-limiting). Puedes revisar tu estado actual de límite de tasa en cualquier momento utilizando la API de Límites de Tasa que se describe a continuación.
+
+### Entender el estado de tu límite de tasa
+
+La API de Búsqueda tiene un [límite de tasa personalizado](/rest/reference/search#rate-limit) separado de aquél que rige el resto de la API de REST. La API de GraphQL también tiene un [límite de tasa personalizado]({% ifversion ghec%}/free-pro-team@latest{% endif %}/graphql/overview/resource-limitations#rate-limit) que está separado y se calcula diferente que los límites de tasa de la API de REST.
+
+Es por esto que la respuesta de la API de Límites de Tasa categoriza tu límite de tasa. Debajo de `resources`, verás cuatro objetos:
+
+* El objeto `core` proporciona tu estado de límite de tasa para todos los recursos no relacionados a búsquedas en la API de REST.
+
+* El objeto `search` proporciona el estado de tu límite de tasa para la [API de Búsqueda](/rest/reference/search).
+
+* El objeto `graphql` proporciona el estado de tu límite de tasa para la [API de GraphQL]({% ifversion ghec%}/free-pro-team@latest{% endif %}/graphql).
+
+* El objeto `integration_manifest` proporciona el estado de tu límite de tasa para la terminal [Conversión de código para el Manifiesto de GitHub App](/apps/building-github-apps/creating-github-apps-from-a-manifest/#3-you-exchange-the-temporary-code-to-retrieve-the-app-configuration).
+
+Para obtener más información sobre los encabezados y valores en la respuesta de límite de tasa, consulta la sección "[Recursos en la API de REST](/rest/overview/resources-in-the-rest-api#rate-limit-http-headers)".
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/rest-reference/reations/reactions.md b/translations/es-ES/data/reusables/rest-reference/reations/reactions.md
new file mode 100644
index 000000000000..d2feff37dd76
--- /dev/null
+++ b/translations/es-ES/data/reusables/rest-reference/reations/reactions.md
@@ -0,0 +1,5 @@
+### Reaction types
+
+When creating a reaction, the allowed values for the `content` parameter are as follows (with the corresponding emoji for reference):
+
+{% data reusables.repositories.reaction_list %}
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/rest-reference/releases/assets.md b/translations/es-ES/data/reusables/rest-reference/releases/assets.md
new file mode 100644
index 000000000000..902620cfeba1
--- /dev/null
+++ b/translations/es-ES/data/reusables/rest-reference/releases/assets.md
@@ -0,0 +1 @@
+## Release assets
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/rest-reference/releases/releases.md b/translations/es-ES/data/reusables/rest-reference/releases/releases.md
new file mode 100644
index 000000000000..779e20d40348
--- /dev/null
+++ b/translations/es-ES/data/reusables/rest-reference/releases/releases.md
@@ -0,0 +1,5 @@
+{% note %}
+
+**Nota:** La API de Lanzamientos reemplaza a la API de Descargas. Puedes recuperar el conteo de descargas y la URL de descarga del buscador desde las terminales en esta API, las cuales devuelven los lanzamientos y los activos de éstos.
+
+{% endnote %}
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/rest-reference/repos/autolinks.md b/translations/es-ES/data/reusables/rest-reference/repos/autolinks.md
new file mode 100644
index 000000000000..afe1da660743
--- /dev/null
+++ b/translations/es-ES/data/reusables/rest-reference/repos/autolinks.md
@@ -0,0 +1,5 @@
+## Autoenlaces
+
+Para ayudar a optimizar tu flujo de trabajo, puedes utilizar la API para agregar autoenlaces a los recursos externos como propuestas de JIRA y tickets de Zendesk. Para obtener más información, consulta la sección "[Configurar los autoenlaces para referenciar recursos externos](/github/administering-a-repository/configuring-autolinks-to-reference-external-resources)".
+
+Las {% data variables.product.prodname_github_apps %} requieren permisos de administración de repositorios con acceso de lectura o escritura para utilizar la API de Autoenlaces.
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/rest-reference/repos/contents.md b/translations/es-ES/data/reusables/rest-reference/repos/contents.md
new file mode 100644
index 000000000000..3cc870940db2
--- /dev/null
+++ b/translations/es-ES/data/reusables/rest-reference/repos/contents.md
@@ -0,0 +1,22 @@
+## Contenido
+
+Las terminales de esta API te permiten crear, modificar y borrar contenido cifrado en Base64 en un repositorio. Para solicitar el formato sin procesar y interpretado en HTML (cuando sea posible), utiliza los tipos de medios personalizados para el contenido de un repositorio.
+
+### Tipos de medios personalizados para el contenido de un repositorio
+
+Los [README](/rest/reference/repos#get-a-repository-readme), [archivos](/rest/reference/repos#get-repository-content) y [symlinks](/rest/reference/repos#get-repository-content) son compatibles con los siguientes tipos de medios personalizados:
+
+ application/vnd.github.VERSION.raw
+ application/vnd.github.VERSION.html
+
+Utiliza el tipo de medios `.raw` para recuperar el contenido del archivo.
+
+Para archivos de markup tales como Markdown o AsciiDoc, puedes recuperar la interpretación en HTML si utilizas el tipo de medios `.html`. Los lenguajes de Markup se interpretan en HTML utilizando nuestra [biblioteca de Markup](https://github.com/github/markup) de código abierto.
+
+[Todos los objetos](/rest/reference/repos#get-repository-content) son compatibles con el siguiente tipo de medios personalizados:
+
+ application/vnd.github.VERSION.object
+
+Utiliza el parámetro de tipo de medios `object` para recuperar el contenido en un formato de objeto consistente sin importar el tipo de contenido. Por ejemplo, en vez de ser una matriz de objetos para un directorio, la respuesta será un objeto con un atributo de `entries` que contenga la matriz de objetos.
+
+Puedes leer más acerca del uso de tipos de medios en la API [aquí](/rest/overview/media-types).
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/rest-reference/repos/forks.md b/translations/es-ES/data/reusables/rest-reference/repos/forks.md
new file mode 100644
index 000000000000..2008b190ce64
--- /dev/null
+++ b/translations/es-ES/data/reusables/rest-reference/repos/forks.md
@@ -0,0 +1 @@
+## Bifurcaciones
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/rest-reference/repos/lfs.md b/translations/es-ES/data/reusables/rest-reference/repos/lfs.md
new file mode 100644
index 000000000000..5a48e59434d8
--- /dev/null
+++ b/translations/es-ES/data/reusables/rest-reference/repos/lfs.md
@@ -0,0 +1,2 @@
+
+## Git LFS
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/rest-reference/scim/scim.md b/translations/es-ES/data/reusables/rest-reference/scim/scim.md
new file mode 100644
index 000000000000..d1e34a4851c8
--- /dev/null
+++ b/translations/es-ES/data/reusables/rest-reference/scim/scim.md
@@ -0,0 +1,41 @@
+### Aprovisionamiento de SCIM para las Organizaciones
+
+Los proveedores de identidad (IdP) habilitados para SCIM utilizan la API de SCIM para automatizar el aprovisionamiento de la membrecía de las organizaciones de {% data variables.product.product_name %}. La API de {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} se basa en la versión 2.0 del [SCIM estándar](http://www.simplecloud.info/). La terminal de SCIM de {% data variables.product.product_name %} que deben utilizar los IdP es: `{% data variables.product.api_url_code %}/scim/v2/organizations/{org}/`.
+
+{% note %}
+
+**Notas:**
+ - La API de SCIM se encuentra disponible únicamente para las organizaciones de [{% data variables.product.prodname_ghe_cloud %}](/billing/managing-billing-for-your-github-account/about-billing-for-github-accounts) que cuentan con el [SSO de SAML](/rest/overview/other-authentication-methods#authenticating-for-saml-sso) habilitado. {% data reusables.scim.enterprise-account-scim %} Para obtener más información sobre SCIM, consulta la sección "[Acerca de SCIM](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim)".
+ - La API de SCIM no puede utilizarse con {% data variables.product.prodname_emus %}.
+
+{% endnote %}
+
+### Autenticar las llamadas a la API de SCIM
+
+Debes autenticarte como un propietario de una organización de {% data variables.product.product_name %} para utilizar la API de SCIM. La API espera que se incluya un token [Portador de OAuth 2.0](/developers/apps/authenticating-with-github-apps) en el encabezado `Authorization`. También puedes utilizar un token de acceso personal, pero primero debes [autorizarlo para su uso con tu orgnización que cuenta con el SSO de SAML](/github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on).
+
+### Mapeo de los datos de SAML y de SCIM
+
+{% data reusables.scim.nameid-and-username-must-match %}
+
+### Atributos de Usuario de SCIM compatibles
+
+| Nombre | Tipo | Descripción |
+| ----------------- | ----------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `userName` | `secuencia` | El nombre de usuario para el usuario. |
+| `name.givenName` | `secuencia` | El primer nombre del usuario. |
+| `name.familyName` | `secuencia` | El apellido del usuario. |
+| `emails` | `arreglo` | Lista de correos electrónicos del usuario. |
+| `externalId` | `secuencia` | El proveedor de SAML genera este identificador, el cual utiliza como una ID única para empatarla contra un usuario de GitHub. Puedes encontrar la `externalID` de un usuario ya sea con el proveedor de SAML, o utilizando la terminal de [Listar las identidades aprovisionadas de SCIM](#list-scim-provisioned-identities) y filtrando otros atributos conocidos, tales como el nombre de usuario de GitHub o la dirección de correo electrónico de un usuario. |
+| `id` | `secuencia` | Identificador que genera la terminal de SCIM de GitHub. |
+| `active` | `boolean` | Se utiliza para indicar si la identidad está activa (true) o si debe desaprovisionarse (false). |
+
+{% note %}
+
+**Nota:** Las URL de terminal para la API de SCIM distinguen entre mayúsculas y minúsculas. Por ejemplo, la primera letra en la terminal `Users` debe ponerse en mayúscula:
+
+```shell
+GET /scim/v2/organizations/{org}/Users/{scim_user_id}
+```
+
+{% endnote %}
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/rest-reference/search/search.md b/translations/es-ES/data/reusables/rest-reference/search/search.md
new file mode 100644
index 000000000000..1d5ee025ebfc
--- /dev/null
+++ b/translations/es-ES/data/reusables/rest-reference/search/search.md
@@ -0,0 +1,144 @@
+La API de Búsqueda te ayuda a buscar el elemento específico que quieres encontrar. Por ejemplo, puedes buscar un usuario o un archivo específico en el repositorio. Tómalo como el simil de realizar una búsqueda en Google. Se diseñó para ayudarte a encontrar el resultado exacto que estás buscando (o tal vez algunos de los resultados que buscas). Tal como la búsqueda en Google, a veces quieres ver algunas páginas de los resultados de búsqueda para que puedas encontrar el elemento que mejor satisfaga tus necesidades. Para satisfacer esta necesidad, la API de Búsqueda de {% data variables.product.product_name %} proporciona **hasta 1,000 resultados por búsqueda**.
+
+Puedes delimitar tu búsqueda utilizando consultas. Para aprender más sobre la sintaxis de las consultas de búsqueda, dirígete a "[Construir una consulta de búsqueda](/rest/reference/search#constructing-a-search-query)".
+
+### Clasificar los resultados de la búsqueda
+
+A menos de que se proporcione algún otro tipo de opción como parámetro de consulta, los resultados se clasificarán de acuerdo a la exactitud de la coincidencia en orden descendente. Varios factores se combinan para impulsar el elemento más relevante hasta arriba de la lista de resultados.
+
+### Limite de tasa
+
+{% data reusables.enterprise.rate_limit %}
+
+La API de Búsqueda tiene un límite de tasa personalizado. Para las solicitudes que utilizan [Autenticación Básica](/rest#authentication), [OAuth](/rest#authentication), o [secreto e ID de cliente](/rest#increasing-the-unauthenticated-rate-limit-for-oauth-applications), puedes hacer hasta 30 solicitudes por minuto. Para las solicitudes sin autenticar, el límite de tasa te permite hacer hasta 10 por minuto.
+
+Consulta la [documentación del límite de tasa](/rest/reference/rate-limit) para obtener más detalles sobre cómo determinar tu estado de límite de tasa actual.
+
+### Construir una consulta de búsqueda
+
+Cada terminal en la API de búsqueda utiliza [parámetros de búsqueda](https://en.wikipedia.org/wiki/Query_string) para realizar búsqeudas en {% data variables.product.product_name %}. Observa la terminal individual an la API de Búsqueda para encontrar un ejemplo que incluye los parámetros de consulta y de terminal.
+
+Una consulta puede contener cualquier combinación de calificadores de búsqueda que sea compatible con {% data variables.product.product_name %}. El formato de esta consulta de búsqueda es:
+
+```
+SEARCH_KEYWORD_1 SEARCH_KEYWORD_N QUALIFIER_1 QUALIFIER_N
+```
+
+Por ejemplo, si quisieras buscar todos los _repositorios_ que pertenecen a `defunkt` y que contienen la palabra `GitHub` y `Octocat` en el archivo de README, utilizarías la siguiente consulta con la terminal de _buscar repositorios_:
+
+```
+GitHub Octocat in:readme user:defunkt
+```
+
+**Nota:** Asegúrate de utilizar el codificador HTML preferido de tu lenguaje de programación para construir tus cadenas de consulta. Por ejemplo:
+```javascript
+// JavaScript
+const queryString = 'q=' + encodeURIComponent('GitHub Octocat in:readme user:defunkt');
+```
+
+Consulta la sección "[Buscar en GitHub](/search-github/searching-on-github)" para encontrar una lista completa de calificadores disponibles, su formato, y ejemplos de cómo utilizarlos. Para obtener más información acerca de cómo utilizar los operadores para que coincidan con cantidades y fechas específicas o para que excluyan resultados, consulta la sección "[Entender la sintaxis de búsqueda](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax/)".
+
+### Limitaciones sobre la longitud de la consulta
+
+La API de búsqueda no es compatible con consultas que:
+- sean mayores a 256 caracteres (sin incluir los operadores o calificativos).
+- tengan más de cinco operadores de `AND`, `OR`, o `NOT`.
+
+Estas consultas de búsqueda devolverán un mensaje de error de "Validation failed".
+
+### Tiempos excedidos y resultados incompletos
+
+Para que la API de Búsqueda se mantenga rápida para todos, limitamos el tiempo que puede jecutarse cualquier consulta específica. Para las consultas que [exceden el límite de tiempo](https://developer.github.com/changes/2014-04-07-understanding-search-results-and-potential-timeouts/), la API devuelve las coincidencias que ya se habían encontrado antes de exceder el tiempo, y la respuesta tiene la propiedad `incomplete_results` como `true`.
+
+Llegar a una interrupción no necesariamente significa que los resultados de búsqueda estén incompletos. Puede que se hayan encontrado más resultados, pero también puede que no.
+
+### Errores de acceso o resultados de búsqueda faltantes
+
+Necesitas autenticarte con éxito y tener acceso a los repositorios en tus consultas de búsqueda, de otro modo, verás un error `422 Unprocessable Entry` con un mensaje de "Validation Failed". Por ejemplo, tu búsqueda fallará si tu consulta incluye los calificadores `repo:`, `user:`, o `org:` que solicitan los recursos a los cuales no tienes acceso cuando inicias sesión en {% data variables.product.prodname_dotcom %}.
+
+Cuando tu consulta de búsqueda solicita recursos múltiples, la respuesta solo contendrá aquellos a los que tengas acceso y **no** proporcionará un mensaje de error que liste los recursos que no se devolvieron.
+
+Por ejemplo, si tu consulta de búsqueda quiere buscar en los repositorios `octocat/test` y `codertocat/test`, pero solo tienes acceso a `octocat/test`, tu respuesta mostrará los resultados de búsqueda para `octocat/test` y no mostrará nada para `codertocat/test`. Este comportamiento simula cómo funciona la búsqueda en {% data variables.product.prodname_dotcom %}.
+
+### Metadatos en el texto coincidente
+
+En GitHub, puedes utilizar el contexto que te proporcionan los extractos de código y los puntos destacados en los resultados de búsqueda. La API de Búsqueda ofrece metadatos adicionales que te permiten resaltar los términos de búsqueda coincidentes cuando se muestran los resultados de la búsqueda.
+
+
+
+Las solicitudes pueden decidir recibir esos fragmentos de texto en la respuesta, y cada fragmento se acompaña de intervalos numéricos que identifican la ubicación exacta de cada término de búsqueda coincidente.
+
+Para obtener estos metadatos en tus resultados de búsqueda, especifica el tipo de medios `text-match` en tu encabezado de `Accept`.
+
+```shell
+application/vnd.github.v3.text-match+json
+```
+
+Cuando proporcionas el tipo de medios `text-match`, recibirás una clave extra en la carga útil de JSON llamada `text_matches`, la cual proporciona información acerca de la posición de tus términos de búsqueda dentro del texto y la `property` que incluye dicho término de búsqueda. Dentro de la matriz `text_matches`, cada objeto incluye los siguientes atributos:
+
+| Nombre | Descripción |
+| ------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `object_url` | La URL del recurso que contiene una propiedad de secuencia que empata con uno de los términos de búsqueda. |
+| `object_type` | El nombre del tipo de recurso que existe en la `object_url` específica. |
+| `property` | El nombre de la propiedad del recurso que existe en la `object_url`. Esa propiedad es una secuencia que empata con uno de los términos de la búsqueda. (En el JSON que se devuelve de la `object_url`, el contenido entero para el `fragment` se encontrará en la propiedad con este nombre.) |
+| `fragmento` | Un subconjunto del valor de `property`. Este es el fragmento de texto que empata con uno o más de los términos de búsqueda. |
+| `matches` | Una matriz de uno o más términos de búsqueda presentes en el `fragment`. Los índices (es decir, "intervalos") son relativos al fragmento. (No son relativos al contenido _completo_ de `property`.) |
+
+#### Ejemplo
+
+Si utilizas cURL y también el [ejemplo de búsqueda de informe de problemas](#search-issues-and-pull-requests) anterior, nuestra solicitud de la API se vería así:
+
+``` shell
+curl -H 'Accept: application/vnd.github.v3.text-match+json' \
+'{% data variables.product.api_url_pre %}/search/issues?q=windows+label:bug+language:python+state:open&sort=created&order=asc'
+```
+
+La respuesta incluirá una matriz de `text_matches` para cada resultado de búsqueda. En el JSON que se muestra a continuación, tenemos dos objetos en la matriz `text_matches`.
+
+La primera coincidencia de texto ocurrió en la propiedad de `body` del informe de problemas. Aquí vemos un fragmento de texto del cuerpo del informe de problemas. El término de búsqueda (`windows`) aparece dos veces dentro de ese fragmento, y tenemos los índices para cada ocurrencia.
+
+La segunda coincidencia de texto ocurrió en la propiedad `body` de uno de los comentarios del informe de problemas. Tenemos la URL para el comentario del informe de problemas. Y, por supuesto, vemos un fragmento de texto del cuerpo del comentario. El término de búsqueda (`windows`) se muestra una vez dentro de ese fragmento.
+
+```json
+{
+ "text_matches": [
+ {
+ "object_url": "https://api.github.com/repositories/215335/issues/132",
+ "object_type": "Issue",
+ "property": "body",
+ "fragment": "comprehensive windows font I know of).\n\nIf we can find a commonly distributed windows font that supports them then no problem (we can use html font tags) but otherwise the '(21)' style is probably better.\n",
+ "matches": [
+ {
+ "text": "windows",
+ "indices": [
+ 14,
+ 21
+ ]
+ },
+ {
+ "text": "windows",
+ "indices": [
+ 78,
+ 85
+ ]
+ }
+ ]
+ },
+ {
+ "object_url": "https://api.github.com/repositories/215335/issues/comments/25688",
+ "object_type": "IssueComment",
+ "property": "body",
+ "fragment": " right after that are a bit broken IMHO :). I suppose we could have some hack that maxes out at whatever the font does...\n\nI'll check what the state of play is on Windows.\n",
+ "matches": [
+ {
+ "text": "Windows",
+ "indices": [
+ 163,
+ 170
+ ]
+ }
+ ]
+ }
+ ]
+}
+```
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/rest-reference/secret-scanning/secret-scanning.md b/translations/es-ES/data/reusables/rest-reference/secret-scanning/secret-scanning.md
new file mode 100644
index 000000000000..64d021496e76
--- /dev/null
+++ b/translations/es-ES/data/reusables/rest-reference/secret-scanning/secret-scanning.md
@@ -0,0 +1,9 @@
+{% data reusables.secret-scanning.api-beta %}
+
+La API del {% data variables.product.prodname_secret_scanning %} te permite {% ifversion fpt or ghec or ghes > 3.1 or ghae %}:
+
+- Habilitar o inhabilitar el {% data variables.product.prodname_secret_scanning %} para un repositorio. Para obtener más información, consulta la sección "[Repositorios](/rest/reference/repos#update-a-repository)" en la documentación de REST.
+- Recupera y actualiza las alertas del {% data variables.product.prodname_secret_scanning %} desde un repositorio {% ifversion fpt or ghec %}privado{% endif %}. Para obtener más detalles, consulta las secciones a continuación.
+{%- else %} recupera y actualiza las alertas del {% data variables.product.prodname_secret_scanning %} desde un repositorio {% ifversion fpt or ghec %}privado{% endif %}.{% endif %}
+
+Para obtener más información acerca de las {% data variables.product.prodname_secret_scanning %}, consulta la sección "[Acerca del {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/about-secret-scanning)".
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/rest-reference/teams/discussion-comments.md b/translations/es-ES/data/reusables/rest-reference/teams/discussion-comments.md
new file mode 100644
index 000000000000..b018095810f0
--- /dev/null
+++ b/translations/es-ES/data/reusables/rest-reference/teams/discussion-comments.md
@@ -0,0 +1,3 @@
+## Comentarios de debate
+
+La API de comentarios para debates de equipo te permite obtener, crear, editar y borrar los comentarios del debate en una publicación de un [debate de equipo](/rest/reference/teams#discussions). Cualquier miembro de la [organización](/rest/reference/orgs) del equipo puede crear y leer los comentarios de un debate público. Para obtener más detalles, consulta la sección "[Acerca de los debates de equipo](/organizations/collaborating-with-your-team/about-team-discussions/)". Esta API solo está disponible para los miembros autenticados de la organization del equipo.
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/rest-reference/teams/discussions.md b/translations/es-ES/data/reusables/rest-reference/teams/discussions.md
new file mode 100644
index 000000000000..7588af4ff197
--- /dev/null
+++ b/translations/es-ES/data/reusables/rest-reference/teams/discussions.md
@@ -0,0 +1,3 @@
+## Discussions
+
+La API de debates de equipo te permite obtener, crear, editar y borrar las publicaciones de un debate en la página de un equipo. Puedes utilizar los debates de equipo para sostener conversaciones que no son específicas de un repositorio o proyecto. Cualquier miembro de la [organización](/rest/reference/orgs) del equipo puede crear y leer las publicaciones de debates públicos. Para obtener más detalles, consulta la sección "[Acerca de los debates de equipo](//organizations/collaborating-with-your-team/about-team-discussions/)". Para aprender más sobre cómo comentar en una publicación de debate, consulta la [API de comentarios para debates de equipo](/rest/reference/teams#discussion-comments). Esta API solo está disponible para los miembros autenticados de la organization del equipo.
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/rest-reference/teams/external-groups.md b/translations/es-ES/data/reusables/rest-reference/teams/external-groups.md
new file mode 100644
index 000000000000..9333f50e3e23
--- /dev/null
+++ b/translations/es-ES/data/reusables/rest-reference/teams/external-groups.md
@@ -0,0 +1,16 @@
+## Grupos externos
+
+La API de grupos externos te permite ver los grupos de proveedor de identidad externos que están disponibles para tu organización, así como administrar la conexión entre los grupos externos y los equipos de tu organziación.
+
+Para utilizar esta API, el usuario autenticado debe ser un mantenedor del equipo o un propietario de la organización asociada con éste.
+
+{% ifversion ghec %}
+{% note %}
+
+**Notas:**
+
+- La API de grupos externos solo se encuentra disponible para aquellas organizaciones que sean parte de una empresa que utilice {% data variables.product.prodname_emus %}. Para obtener más información, consulta la sección "[Acerca de los Usuarios Empresariales Administrados](/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)".
+- Si tu organización utiliza la sincronización de equipos, puedes usar la API de Sincronización de Equipos. Para obtener más información, consulta la "[API de sincronización de equipos](#team-synchronization)".
+
+{% endnote %}
+{% endif %}
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/rest-reference/teams/members.md b/translations/es-ES/data/reusables/rest-reference/teams/members.md
new file mode 100644
index 000000000000..41fdee3a69c6
--- /dev/null
+++ b/translations/es-ES/data/reusables/rest-reference/teams/members.md
@@ -0,0 +1,12 @@
+## Miembros
+
+Esta API solo está disponible para los miembros autenticados de la organization del equipo. Los tokens de acceso de OAuth requieren el [alcance](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/) `read:org`.
+
+{% ifversion fpt or ghes or ghec %}
+{% note %}
+
+**Nota:** Cuando configuras la sincornizacion de equipos para un equipo con el proveedor de identidad (IdP) de tu organización, verás un error si intentas utilizar la API para hacer cambios en la membrecía de dicho equipo. Si tienes acceso para administrar las membrecías de usuario en tu IdP, puedes administrar la membrecía del equipo de GitHub a través de tu proveedor de identidad, lo cual agrega y elimina automáticamente a los miembros en una organización. Para obtener más información, consulta la sección "Sincronizar equipos entre tu proveedor de identidad y GitHub".
+
+{% endnote %}
+
+{% endif %}
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/rest-reference/teams/team-sync.md b/translations/es-ES/data/reusables/rest-reference/teams/team-sync.md
new file mode 100644
index 000000000000..b44452d8f53c
--- /dev/null
+++ b/translations/es-ES/data/reusables/rest-reference/teams/team-sync.md
@@ -0,0 +1,11 @@
+## Sincronización de equipos
+
+La API de sincronización de equipos te permite administrar las conexiones entre los equipos de {% data variables.product.product_name %} y los grupos del proveedor de identidad (IdP) externo. Para utilizar esta API, el usuario autenticado debe ser un mantenedor del equipo o un propietario de la organización asociada con éste. El token que utilizas para autenticarte también necesitará autorizarse para su uso con tu proveedor IdP (SSO). Para obtener más información, consulta la sección "Autorizar un token de acceso personal para su uso con una organización que tiene inicio de sesión único de SAML".
+
+Puedes administrar a los miembros del equipo de GitHub a través de tu IdP con la sincronización de equipos. Ésta se debe habilitar para usar la API de Sincronización de Equipos. Para obtener más información, consulta la sección "Sincronizar equipos entre tu proveedor de identidad y GitHub".
+
+{% note %}
+
+**Nota:** La API de sincronización de equipos no puede utilizarse con {% data variables.product.prodname_emus %}. Para aprender más sobre cómo administrar una {% data variables.product.prodname_emu_org %}, consulta la sección "[API de grupos externos](/enterprise-cloud@latest/rest/reference/teams#external-groups)".
+
+{% endnote %}
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/rest-reference/teams/teams.md b/translations/es-ES/data/reusables/rest-reference/teams/teams.md
new file mode 100644
index 000000000000..5bad9d746a0f
--- /dev/null
+++ b/translations/es-ES/data/reusables/rest-reference/teams/teams.md
@@ -0,0 +1 @@
+Esta API solo está disponible para los miembros autenticados de la [organization](/rest/reference/orgs) del equipo. Los tokens de acceso de OAuth requieren el [alcance](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/) `read:org`. {% data variables.product.prodname_dotcom %} genera el `slug` del equipo a partir del `name` del mismo.
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/rest-reference/users/blocking.md b/translations/es-ES/data/reusables/rest-reference/users/blocking.md
new file mode 100644
index 000000000000..8ab1213c6b6f
--- /dev/null
+++ b/translations/es-ES/data/reusables/rest-reference/users/blocking.md
@@ -0,0 +1 @@
+## Bloquear usuarios
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/rest-reference/users/emails.md b/translations/es-ES/data/reusables/rest-reference/users/emails.md
new file mode 100644
index 000000000000..40e24f4c37ef
--- /dev/null
+++ b/translations/es-ES/data/reusables/rest-reference/users/emails.md
@@ -0,0 +1,3 @@
+## Emails (Correos electrónicos)
+
+Administrar las direcciones de correo electrónico a través de la API requiere que ingreses con la autenticación básica o con OAuth con un alcance correcto para la terminal.
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/rest-reference/users/followers.md b/translations/es-ES/data/reusables/rest-reference/users/followers.md
new file mode 100644
index 000000000000..8a7cd6a06703
--- /dev/null
+++ b/translations/es-ES/data/reusables/rest-reference/users/followers.md
@@ -0,0 +1 @@
+## Seguidores
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/rest-reference/users/gpg-keys.md b/translations/es-ES/data/reusables/rest-reference/users/gpg-keys.md
new file mode 100644
index 000000000000..faa5935e28ac
--- /dev/null
+++ b/translations/es-ES/data/reusables/rest-reference/users/gpg-keys.md
@@ -0,0 +1,3 @@
+## Claves GPG
+
+Los datos que se devuelven en el campo de respuesta de `public_key` no son una llave con formato de GPG. Cuando un usuario carga una llave GPG, se interpreta y la llave pública criptográfica se extrae y se almacena. Esta llave criptográfica es lo que devuelven las API en esta página. Esta llave no es apta para utilizarse directamente con programas como GPG.
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/rest-reference/users/keys.md b/translations/es-ES/data/reusables/rest-reference/users/keys.md
new file mode 100644
index 000000000000..fb0f9bfb15d9
--- /dev/null
+++ b/translations/es-ES/data/reusables/rest-reference/users/keys.md
@@ -0,0 +1 @@
+## Llaves SSH de Git
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/rest-reference/users/users.md b/translations/es-ES/data/reusables/rest-reference/users/users.md
new file mode 100644
index 000000000000..d700fc55bc19
--- /dev/null
+++ b/translations/es-ES/data/reusables/rest-reference/users/users.md
@@ -0,0 +1 @@
+Muchos de los recursos en la API de los usuarios proporcionan un atajo para obtener información acerca del usuario autenticado actualmente. Si una URL de solicitud no incluye un parámetro de `{username}`, entonces la respuesta será para el usuario que inició sesión (y debes pasar la [información de autenticación](/rest/overview/resources-in-the-rest-api#authentication) con tu solicitud).{% ifversion fpt or ghes or ghec %} La información privada adicional, tal como si un usuario tiene habilitada la autenticación bifactorial, se incluye cuando se está autenticado con la autenticación básica o a través de OAuth, con el alcance de `user`.{% endif %}
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/rest-reference/webhooks/repo-config.md b/translations/es-ES/data/reusables/rest-reference/webhooks/repo-config.md
new file mode 100644
index 000000000000..055bbb9fa1fe
--- /dev/null
+++ b/translations/es-ES/data/reusables/rest-reference/webhooks/repo-config.md
@@ -0,0 +1 @@
+## Repository webhook configuration
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/rest-reference/webhooks/repo-deliveries.md b/translations/es-ES/data/reusables/rest-reference/webhooks/repo-deliveries.md
new file mode 100644
index 000000000000..bd0366dee6a4
--- /dev/null
+++ b/translations/es-ES/data/reusables/rest-reference/webhooks/repo-deliveries.md
@@ -0,0 +1 @@
+## Repository webhook deliveries
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/rest-reference/webhooks/repos.md b/translations/es-ES/data/reusables/rest-reference/webhooks/repos.md
new file mode 100644
index 000000000000..b81b73974df8
--- /dev/null
+++ b/translations/es-ES/data/reusables/rest-reference/webhooks/repos.md
@@ -0,0 +1 @@
+## Webhooks de repositorio
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/rest-reference/webhooks/webhooks.md b/translations/es-ES/data/reusables/rest-reference/webhooks/webhooks.md
new file mode 100644
index 000000000000..49fb30d81e42
--- /dev/null
+++ b/translations/es-ES/data/reusables/rest-reference/webhooks/webhooks.md
@@ -0,0 +1,58 @@
+Los webhooks de repositorio te permiten recibir cargas útiles de `POST` por HTTP cuando ciertos eventos suceden en un repositorio. {% data reusables.webhooks.webhooks-rest-api-links %}
+
+Si te gustaría configurar un solo webhook para recibir eventos de todos los repositorios de tu organización, consulta nuestra documentación de la API para los [Webhooks de una Organización](/rest/reference/orgs#webhooks).
+
+Adicionalmente a la API de REST, {% data variables.product.prodname_dotcom %} también puede servir como un punto de [PubSubHubbub](#pubsubhubbub) para los repositorios.
+
+## Recibir Webhooks
+
+Para que {% data variables.product.product_name %} envíe cargas útiles de webhooks, se necesita que se pueda acceder a tu servidor desde la internet. También sugerimos ampliamente utilizar SSL para que podamos enviar cargas útiles cifradas a través de HTTPS.
+
+### Encabezados de Webhook
+
+{% data variables.product.product_name %} enviará varios encabezados de HTTP para diferenciar los tipos de eventos y los identificadores de las cargas útiles. Consulta la sección de [encabezados de webhook](/developers/webhooks-and-events/webhook-events-and-payloads#delivery-headers) para encontrar más detalles.
+
+## PubSubHubbub
+
+GitHub también puede fungir como un centro de [PubSubHubbub](https://github.com/pubsubhubbub/PubSubHubbub) para todos los repositorios. PSHB es un proptocolo simple de publicación/suscripción que permite a los servidores registrarse para recibir actualizaciones de cuándo se actualiza un tema. Las actualizaciones se mandan con una solicitud HTTP de tipo POST a una URL de rellamado. Las URL de tema para las cargas a un repositorio de GitHub están en este formato:
+
+`https://github.com/{owner}/{repo}/events/{event}`
+
+El veneto puede ser cualquier evento de webhook disponible. Para obtener más información, consulta la sección "[eventos y cargas útiles de los webhooks](/developers/webhooks-and-events/webhook-events-and-payloads)".
+
+### Formato de respuesta
+
+El formato predeterminado es lo que [deberían esperar los ganchos de post-recepción](/post-receive-hooks/): Un cuerpo de JSON que se envía como un parámetro de `payload` en un POST. También puedes especificar si quieres recibir el cuerpo en JSON sin procesar, ya sea un encabezado de `Accept` o una extensión `.json`.
+
+ Accept: application/json
+ https://github.com/{owner}/{repo}/events/push.json
+
+### URL de Rellamado
+
+Las URL de rellamado puede utilizar el protocolo `http://`.
+
+ # Send updates to postbin.org
+ http://postbin.org/123
+
+### Suscribirse
+
+La terminal de PubSubHubbub de GitHub es: `{% data variables.product.api_url_code %}/hub`. Una solicitud exitosa con curl se vería así:
+
+``` shell
+curl -u "user" -i \
+ {% data variables.product.api_url_pre %}/hub \
+ -F "hub.mode=subscribe" \
+ -F "hub.topic=https://github.com/{owner}/{repo}/events/push" \
+ -F "hub.callback=http://postbin.org/123"
+```
+
+Las solicitudes de PubSubHubbub pueden enviarse varias veces. Si el gancho ya existe, se modificará de acuerdo con la solicitud.
+
+#### Parámetros
+
+| Nombre | Tipo | Descripción |
+| -------------- | ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `hub.mode` | `secuencia` | **Requerido**. Ya sea `subscribe` o `unsubscribe`. |
+| `hub.topic` | `secuencia` | **Requerido**. La URI del repositorio de GitHub al cual suscribirse. La ruta debe estar en el formato `/{owner}/{repo}/events/{event}`. |
+| `hub.callback` | `secuencia` | La URI para recibir las actualizaciones del tema. |
+| `hub.secret` | `secuencia` | Una llave de secreto compartido que genera una firma de hash del contenido saliente del cuerpo. Puedes verificar si una subida vino de GitHub comparando el cuerpo de la solicitud sin procesar con el contenido de los encabezados de la {% ifversion fpt or ghes > 2.22 or ghec %}`X-Hub-Signature` o `X-Hub-Signature-256`{% elsif ghes < 3.0 %}`X-Hub-Signature`{% elsif ghae %}`X-Hub-Signature-256`{% endif %}. Puedes ver [la documentación de PubSubHubbub](https://pubsubhubbub.github.io/PubSubHubbub/pubsubhubbub-core-0.4.html#authednotify) para obtener más detalles. |
\ No newline at end of file
diff --git a/translations/es-ES/data/ui.yml b/translations/es-ES/data/ui.yml
index 883b910f0da3..a835c13cf07f 100644
--- a/translations/es-ES/data/ui.yml
+++ b/translations/es-ES/data/ui.yml
@@ -1,4 +1,6 @@
---
+meta:
+ default_description: Get started, troubleshoot, and make the most of GitHub. Documentation for new users, developers, administrators, and all of GitHub's products.
header:
github_docs: GitHub Docs
contact: Contacto
@@ -92,6 +94,7 @@ products:
deprecation_notice: Aviso de depreciación
rest:
reference:
+ notes: Notas
parameters: Parámetros
response: Respuesta
code_sample: Ejemplo de código
@@ -101,6 +104,7 @@ products:
see_preview_notice: Ver aviso de previsualización
see_preview_notices: Ver avisos de previsualización
preview_header_is_required: El encabezado es requerido
+ works_with_github_apps: Works with GitHub Apps
footer:
all_rights_reserved: Todos los derechos reservados
terms: Términos
diff --git a/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-java-with-ant.md b/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-java-with-ant.md
index b1d428521add..bf3f9cb086b0 100644
--- a/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-java-with-ant.md
+++ b/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-java-with-ant.md
@@ -78,9 +78,9 @@ jobs:
The default starter workflows are excellent starting points when creating your build and test workflow, and you can customize the starter workflow to suit your project’s needs.
-{% data reusables.github-actions.example-github-runner %}
+{% data reusables.actions.example-github-runner %}
-{% data reusables.github-actions.java-jvm-architecture %}
+{% data reusables.actions.java-jvm-architecture %}
## コードのビルドとテスト
diff --git a/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-java-with-gradle.md b/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-java-with-gradle.md
index 9b265177e3b3..a3f40dd07319 100644
--- a/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-java-with-gradle.md
+++ b/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-java-with-gradle.md
@@ -83,9 +83,9 @@ jobs:
The default starter workflows are excellent starting points when creating your build and test workflow, and you can customize the starter workflow to suit your project’s needs.
-{% data reusables.github-actions.example-github-runner %}
+{% data reusables.actions.example-github-runner %}
-{% data reusables.github-actions.java-jvm-architecture %}
+{% data reusables.actions.java-jvm-architecture %}
## コードのビルドとテスト
diff --git a/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-java-with-maven.md b/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-java-with-maven.md
index 50a207e1ed31..1aa8ed132dd4 100644
--- a/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-java-with-maven.md
+++ b/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-java-with-maven.md
@@ -78,9 +78,9 @@ jobs:
The default starter workflows are excellent starting points when creating your build and test workflow, and you can customize the starter workflow to suit your project’s needs.
-{% data reusables.github-actions.example-github-runner %}
+{% data reusables.actions.example-github-runner %}
-{% data reusables.github-actions.java-jvm-architecture %}
+{% data reusables.actions.java-jvm-architecture %}
## コードのビルドとテスト
diff --git a/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-nodejs.md b/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-nodejs.md
index e630dfeb4f23..fd14259ac61d 100644
--- a/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-nodejs.md
+++ b/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-nodejs.md
@@ -73,7 +73,7 @@ jobs:
```
{% endraw %}
-{% data reusables.github-actions.example-github-runner %}
+{% data reusables.actions.example-github-runner %}
## Node.jsのバージョンの指定
@@ -204,7 +204,7 @@ steps:
### プライベートレジストリの利用と.npmrcファイルの作成の例
-{% data reusables.github-actions.setup-node-intro %}
+{% data reusables.actions.setup-node-intro %}
プライベートレジストリに対して認証するには、npm 認証トークンをシークレットとして保存する必要があります。 たとえば、`NPM_TOKEN` というリポジトリシークレットを作成します。 詳しい情報については、「[暗号化されたシークレットの作成と利用](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)」を参照してください。
diff --git a/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-xamarin-applications.md b/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-xamarin-applications.md
index 160590a18292..10f38928ef52 100644
--- a/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-xamarin-applications.md
+++ b/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-xamarin-applications.md
@@ -31,7 +31,7 @@ For a full list of available Xamarin SDK versions on the {% data variables.produ
* [macOS 10.15](https://github.com/actions/virtual-environments/blob/main/images/macos/macos-10.15-Readme.md#xamarin-bundles)
* [macOS 11](https://github.com/actions/virtual-environments/blob/main/images/macos/macos-11-Readme.md#xamarin-bundles)
-{% data reusables.github-actions.macos-runner-preview %}
+{% data reusables.actions.macos-runner-preview %}
## 必要な環境
diff --git a/translations/ja-JP/content/actions/creating-actions/about-custom-actions.md b/translations/ja-JP/content/actions/creating-actions/about-custom-actions.md
index a1a81cc4f100..dca4b63878ba 100644
--- a/translations/ja-JP/content/actions/creating-actions/about-custom-actions.md
+++ b/translations/ja-JP/content/actions/creating-actions/about-custom-actions.md
@@ -47,13 +47,13 @@ Docker containers package the environment with the {% data variables.product.pro
A Docker container allows you to use specific versions of an operating system, dependencies, tools, and code. For actions that must run in a specific environment configuration, Docker is an ideal option because you can customize the operating system and tools. Because of the latency to build and retrieve the container, Docker container actions are slower than JavaScript actions.
-Docker container actions can only execute on runners with a Linux operating system. {% data reusables.github-actions.self-hosted-runner-reqs-docker %}
+Docker container actions can only execute on runners with a Linux operating system. {% data reusables.actions.self-hosted-runner-reqs-docker %}
### JavaScript actions
JavaScript actions can run directly on a runner machine, and separate the action code from the environment used to run the code. Using a JavaScript action simplifies the action code and executes faster than a Docker container action.
-{% data reusables.github-actions.pure-javascript %}
+{% data reusables.actions.pure-javascript %}
If you're developing a Node.js project, the {% data variables.product.prodname_actions %} Toolkit provides packages that you can use in your project to speed up development. For more information, see the [actions/toolkit](https://github.com/actions/toolkit) repository.
diff --git a/translations/ja-JP/content/actions/creating-actions/creating-a-composite-action.md b/translations/ja-JP/content/actions/creating-actions/creating-a-composite-action.md
index 82aba25cc79c..4b636f3b4355 100644
--- a/translations/ja-JP/content/actions/creating-actions/creating-a-composite-action.md
+++ b/translations/ja-JP/content/actions/creating-actions/creating-a-composite-action.md
@@ -23,7 +23,7 @@ In this guide, you'll learn about the basic components needed to create and use
Once you complete this project, you should understand how to build your own composite action and test it in a workflow.
-{% data reusables.github-actions.context-injection-warning %}
+{% data reusables.actions.context-injection-warning %}
## 必要な環境
diff --git a/translations/ja-JP/content/actions/creating-actions/creating-a-docker-container-action.md b/translations/ja-JP/content/actions/creating-actions/creating-a-docker-container-action.md
index 0af1dc3dad21..12539b997486 100644
--- a/translations/ja-JP/content/actions/creating-actions/creating-a-docker-container-action.md
+++ b/translations/ja-JP/content/actions/creating-actions/creating-a-docker-container-action.md
@@ -27,9 +27,9 @@ shortTitle: Docker container action
このプロジェクトを完了すると、あなたの Docker コンテナのアクションをビルドして、ワークフローでテストする方法が理解できます。
-{% data reusables.github-actions.self-hosted-runner-reqs-docker %}
+{% data reusables.actions.self-hosted-runner-reqs-docker %}
-{% data reusables.github-actions.context-injection-warning %}
+{% data reusables.actions.context-injection-warning %}
## 必要な環境
diff --git a/translations/ja-JP/content/actions/creating-actions/creating-a-javascript-action.md b/translations/ja-JP/content/actions/creating-actions/creating-a-javascript-action.md
index 917db5dfe173..99e8c3b0b6d6 100644
--- a/translations/ja-JP/content/actions/creating-actions/creating-a-javascript-action.md
+++ b/translations/ja-JP/content/actions/creating-actions/creating-a-javascript-action.md
@@ -29,9 +29,9 @@ shortTitle: JavaScript action
このプロジェクトを完了すると、あなたの JavaScript コンテナのアクションをビルドして、ワークフローでテストする方法が理解できます
-{% data reusables.github-actions.pure-javascript %}
+{% data reusables.actions.pure-javascript %}
-{% data reusables.github-actions.context-injection-warning %}
+{% data reusables.actions.context-injection-warning %}
## 必要な環境
diff --git a/translations/ja-JP/content/actions/creating-actions/dockerfile-support-for-github-actions.md b/translations/ja-JP/content/actions/creating-actions/dockerfile-support-for-github-actions.md
index ddaf64d2b565..b86757f9ddc4 100644
--- a/translations/ja-JP/content/actions/creating-actions/dockerfile-support-for-github-actions.md
+++ b/translations/ja-JP/content/actions/creating-actions/dockerfile-support-for-github-actions.md
@@ -105,7 +105,7 @@ Error response from daemon: OCI runtime create failed: container_linux.go:348: s
`Dockerfile`中で`CMD`を使っているなら、以下のガイドラインに従ってください。
-{% data reusables.github-actions.dockerfile-guidelines %}
+{% data reusables.actions.dockerfile-guidelines %}
## サポートされているLinuxの機能
diff --git a/translations/ja-JP/content/actions/creating-actions/metadata-syntax-for-github-actions.md b/translations/ja-JP/content/actions/creating-actions/metadata-syntax-for-github-actions.md
index 3194cb9c3f62..bb586248e19f 100644
--- a/translations/ja-JP/content/actions/creating-actions/metadata-syntax-for-github-actions.md
+++ b/translations/ja-JP/content/actions/creating-actions/metadata-syntax-for-github-actions.md
@@ -272,7 +272,7 @@ runs:
**Optional** You can use the `if` conditional to prevent a step from running unless a condition is met. 条件文を作成するには、サポートされている任意のコンテキストや式が使えます。
-{% data reusables.github-actions.expression-syntax-if %} For more information, see "[Expressions](/actions/learn-github-actions/expressions)."
+{% data reusables.actions.expression-syntax-if %} For more information, see "[Expressions](/actions/learn-github-actions/expressions)."
**Example: Using contexts**
@@ -441,7 +441,7 @@ runs:
`args`は、`Dockerfile`中の`CMD`命令の場所で使われます。 `Dockerfile`中で`CMD`を使うなら、以下の優先順位順のガイドラインを利用してください。
-{% data reusables.github-actions.dockerfile-guidelines %}
+{% data reusables.actions.dockerfile-guidelines %}
環境変数をアクションに渡す必要がある場合は、変数置換を行えるようアクションがコマンドシェルで実行されていることを確認してください。 たとえば、`entrypoint`属性が`"sh -c"`に設定されているなら、`args`はコマンドシェル内で実行されます。 あるいは、`Dockerfile`が`ENTRYPOINT`を使って同じコマンド（`"sh -c"`）を実行しているなら、`args`はコマンドシェル内で実行されます。
diff --git a/translations/ja-JP/content/actions/deployment/targeting-different-environments/using-environments-for-deployment.md b/translations/ja-JP/content/actions/deployment/targeting-different-environments/using-environments-for-deployment.md
index 0311f8801344..3224ab63d190 100644
--- a/translations/ja-JP/content/actions/deployment/targeting-different-environments/using-environments-for-deployment.md
+++ b/translations/ja-JP/content/actions/deployment/targeting-different-environments/using-environments-for-deployment.md
@@ -69,13 +69,13 @@ Organizations that use {% data variables.product.prodname_ghe_cloud %} can confi
## 環境の作成
-{% data reusables.github-actions.permissions-statement-environment %}
+{% data reusables.actions.permissions-statement-environment %}
{% data reusables.repositories.navigate-to-repo %}
{% data reusables.repositories.sidebar-settings %}
-{% data reusables.github-actions.sidebar-environment %}
-{% data reusables.github-actions.new-environment %}
-{% data reusables.github-actions.name-environment %}
+{% data reusables.actions.sidebar-environment %}
+{% data reusables.actions.new-environment %}
+{% data reusables.actions.name-environment %}
1. Optionally, specify people or teams that must approve workflow jobs that use this environment.
1. Select **Required reviewers**.
1. Enter up to 6 people or teams. ジョブが進行するため承認が必要なレビュー担当者は1人だけです。
@@ -107,13 +107,13 @@ Organizations that use {% data variables.product.prodname_ghe_cloud %} can confi
## 環境の削除
-{% data reusables.github-actions.permissions-statement-environment %}
+{% data reusables.actions.permissions-statement-environment %}
環境を削除すると、その環境に関連づけられたすべてのシークレットと保護ルールが削除されます。 削除された環境の保護ルールのために待機していたジョブは、自動的に失敗します。
{% data reusables.repositories.navigate-to-repo %}
{% data reusables.repositories.sidebar-settings %}
-{% data reusables.github-actions.sidebar-environment %}
+{% data reusables.actions.sidebar-environment %}
1. 削除する環境の横にある {% octicon "trash" aria-label="The trash icon" %} をクリックします。
2. **I understand, delete this environment（分かりました、この環境を削除してください）**をクリックしてください。
diff --git a/translations/ja-JP/content/actions/hosting-your-own-runners/about-self-hosted-runners.md b/translations/ja-JP/content/actions/hosting-your-own-runners/about-self-hosted-runners.md
index d2d43e503959..31c4aee2284f 100644
--- a/translations/ja-JP/content/actions/hosting-your-own-runners/about-self-hosted-runners.md
+++ b/translations/ja-JP/content/actions/hosting-your-own-runners/about-self-hosted-runners.md
@@ -18,25 +18,25 @@ type: overview
## About self-hosted runners
-{% data reusables.github-actions.self-hosted-runner-description %} Self-hosted runners can be physical, virtual, in a container, on-premises, or in a cloud.
+{% data reusables.actions.self-hosted-runner-description %} Self-hosted runners can be physical, virtual, in a container, on-premises, or in a cloud.
You can add self-hosted runners at various levels in the management hierarchy:
- Repository-level runners are dedicated to a single repository.
- Organization-level runners can process jobs for multiple repositories in an organization.
- Enterprise-level runners can be assigned to multiple organizations in an enterprise account.
-Your runner machine connects to {% data variables.product.product_name %} using the {% data variables.product.prodname_actions %} self-hosted runner application. {% data reusables.github-actions.runner-app-open-source %} When a new version is released, the runner application automatically updates itself when a job is assigned to the runner, or within a week of release if the runner hasn't been assigned any jobs.
+Your runner machine connects to {% data variables.product.product_name %} using the {% data variables.product.prodname_actions %} self-hosted runner application. {% data reusables.actions.runner-app-open-source %} When a new version is released, the runner application automatically updates itself when a job is assigned to the runner, or within a week of release if the runner hasn't been assigned any jobs.
-{% data reusables.github-actions.self-hosted-runner-auto-removal %}
+{% data reusables.actions.self-hosted-runner-auto-removal %}
For more information about installing and using self-hosted runners, see "[Adding self-hosted runners](/github/automating-your-workflow-with-github-actions/adding-self-hosted-runners)" and "[Using self-hosted runners in a workflow](/github/automating-your-workflow-with-github-actions/using-self-hosted-runners-in-a-workflow)."
-## {% ifversion fpt or ghes %}Differences between {% data variables.product.prodname_dotcom %}-hosted and {% elsif ghae %}Characteristics of {% endif %}self-hosted runners
+## {% ifversion fpt or ghec or ghes %}Differences between {% data variables.product.prodname_dotcom %}-hosted and {% elsif ghae %}Characteristics of {% endif %}self-hosted runners
-{% ifversion fpt or ghes %}
+{% ifversion fpt or ghec or ghes %}
{% data variables.product.prodname_dotcom %}-hosted runners offer a quicker, simpler way to run your workflows, while self-hosted{% elsif ghae %}Self-hosted{% endif %} runners are a highly configurable way to run workflows in your own custom environment. {% ifversion ghae %}Self-hosted runners:{% endif %}
-{% ifversion fpt or ghes %}
+{% ifversion fpt or ghec or ghes %}
**{% data variables.product.prodname_dotcom %}-hosted runners:**
- Receive automatic updates for the operating system, preinstalled packages and tools, and the self-hosted runner application.
- Are managed and maintained by {% data variables.product.prodname_dotcom %}.
@@ -70,15 +70,15 @@ You can automatically increase or decrease the number of self-hosted runners in
There are some limits on {% data variables.product.prodname_actions %} usage when using self-hosted runners. These limits are subject to change.
-{% data reusables.github-actions.usage-workflow-run-time %}
+{% data reusables.actions.usage-workflow-run-time %}
- **Job queue time** - Each job for self-hosted runners can be queued for a maximum of 24 hours. If a self-hosted runner does not start executing the job within this limit, the job is terminated and fails to complete.
-{% data reusables.github-actions.usage-api-requests %}
-- **Job matrix** - {% data reusables.github-actions.usage-matrix-limits %}
-{% data reusables.github-actions.usage-workflow-queue-limits %}
+{% data reusables.actions.usage-api-requests %}
+- **Job matrix** - {% data reusables.actions.usage-matrix-limits %}
+{% data reusables.actions.usage-workflow-queue-limits %}
## Workflow continuity for self-hosted runners
-{% data reusables.github-actions.runner-workflow-continuity %}
+{% data reusables.actions.runner-workflow-continuity %}
## Supported architectures and operating systems for self-hosted runners
@@ -224,7 +224,7 @@ codeload.github.com
{% ifversion fpt or ghec %}
-{% data reusables.github-actions.self-hosted-runner-security %}
+{% data reusables.actions.self-hosted-runner-security %}
{% endif %}
diff --git a/translations/ja-JP/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md b/translations/ja-JP/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md
index 6eb1b638ce45..ff348ada3762 100644
--- a/translations/ja-JP/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md
+++ b/translations/ja-JP/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md
@@ -26,7 +26,7 @@ Organization または Enterprise 管理者の場合は、Organization または
{% ifversion not ghae %}
{% warning %}
-**警告：** {% data reusables.github-actions.self-hosted-runner-security %}
+**警告：** {% data reusables.actions.self-hosted-runner-security %}
詳しい情報については「[セルフホストランナーについて](/github/automating-your-workflow-with-github-actions/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)」を参照してください。
@@ -40,19 +40,19 @@ Organization または Enterprise 管理者の場合は、Organization または
{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5091 %}
{% data reusables.repositories.navigate-to-repo %}
{% data reusables.repositories.sidebar-settings %}
-{% data reusables.github-actions.settings-sidebar-actions %}
-{% data reusables.github-actions.settings-sidebar-actions-runners-updated %}
+{% data reusables.actions.settings-sidebar-actions %}
+{% data reusables.actions.settings-sidebar-actions-runners-updated %}
1. Click **New self-hosted runner**.
-{% data reusables.github-actions.self-hosted-runner-configure %}
+{% data reusables.actions.self-hosted-runner-configure %}
{% elsif ghae or ghes < 3.4 %}
{% data reusables.repositories.navigate-to-repo %}
{% data reusables.repositories.sidebar-settings %}
-{% data reusables.github-actions.settings-sidebar-actions-runners %}
+{% data reusables.actions.settings-sidebar-actions-runners %}
1. GitHub Insightsの
{% ifversion ghes > 3.1 or ghae or ghec %}"ランナー"{% else %}"セルフホストランナー"{% endif %} で、[**Add runner**] をクリックします。
-{% data reusables.github-actions.self-hosted-runner-configure %}
+{% data reusables.actions.self-hosted-runner-configure %}
{% endif %}
-{% data reusables.github-actions.self-hosted-runner-check-installation-success %}
+{% data reusables.actions.self-hosted-runner-check-installation-success %}
## Organizationへのセルフホストランナーの追加
@@ -61,22 +61,22 @@ Organization または Enterprise 管理者の場合は、Organization または
{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5091 %}
{% data reusables.organizations.navigate-to-org %}
{% data reusables.organizations.org_settings %}
-{% data reusables.github-actions.settings-sidebar-actions %}
-{% data reusables.github-actions.settings-sidebar-actions-runners-updated %}
+{% data reusables.actions.settings-sidebar-actions %}
+{% data reusables.actions.settings-sidebar-actions-runners-updated %}
1. Click **New runner**.
-{% data reusables.github-actions.self-hosted-runner-configure %}
+{% data reusables.actions.self-hosted-runner-configure %}
{% elsif ghae or ghes < 3.4 %}
{% data reusables.organizations.navigate-to-org %}
{% data reusables.organizations.org_settings %}
-{% data reusables.github-actions.settings-sidebar-actions-runners %}
+{% data reusables.actions.settings-sidebar-actions-runners %}
1. GitHub Insightsの
{% ifversion ghes > 3.1 or ghae %}"Runners", click **Add new**, then click **New runner**.{% elsif ghes < 3.2 %}"Self-hosted runners", click **Add runner**."{% endif %}
-{% data reusables.github-actions.self-hosted-runner-configure %}
+{% data reusables.actions.self-hosted-runner-configure %}
{% endif %}
-{% data reusables.github-actions.self-hosted-runner-check-installation-success %}
+{% data reusables.actions.self-hosted-runner-check-installation-success %}
-{% data reusables.github-actions.self-hosted-runner-public-repo-access %}
+{% data reusables.actions.self-hosted-runner-public-repo-access %}
## セルフホストランナーを Enterprise に追加する
@@ -94,7 +94,7 @@ Organization または Enterprise 管理者の場合は、Organization または
{% data reusables.enterprise-accounts.actions-tab %}
{% data reusables.enterprise-accounts.actions-runners-tab %}
1. Click **New runner**.
-{% data reusables.github-actions.self-hosted-runner-configure %}
+{% data reusables.actions.self-hosted-runner-configure %}
{% elsif ghae or ghes < 3.4 %}
セルフホストランナーを
{% data variables.product.product_location %} の Enterprise レベルでを追加するには、サイト管理者である必要があります。
@@ -103,11 +103,11 @@ Organization または Enterprise 管理者の場合は、Organization または
{% data reusables.enterprise-accounts.actions-tab %}
{% data reusables.enterprise-accounts.actions-runners-tab %}
1. [**Add new**] をクリックし、[**New runner**] をクリックします。
-{% data reusables.github-actions.self-hosted-runner-configure %}
+{% data reusables.actions.self-hosted-runner-configure %}
{% endif %}
-{% data reusables.github-actions.self-hosted-runner-check-installation-success %}
+{% data reusables.actions.self-hosted-runner-check-installation-success %}
-{% data reusables.github-actions.self-hosted-runner-public-repo-access %}
+{% data reusables.actions.self-hosted-runner-public-repo-access %}
### Enterprise ランナーをリポジトリで利用可能にする
diff --git a/translations/ja-JP/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md b/translations/ja-JP/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md
index 1892c5ab5798..d12d16299ed4 100644
--- a/translations/ja-JP/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md
+++ b/translations/ja-JP/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md
@@ -49,22 +49,22 @@ Enterprise の管理者が Organization にランナーグループへのアク
{% ifversion ghec or ghes > 3.3 or ghae-issue-5091 %}
{% data reusables.organizations.navigate-to-org %}
{% data reusables.organizations.org_settings %}
-{% data reusables.github-actions.settings-sidebar-actions-runner-groups %}
+{% data reusables.actions.settings-sidebar-actions-runner-groups %}
1. In the "Runner groups" section, click **New runner group**.
- {% data reusables.github-actions.runner-group-assign-policy-repo %}
+ {% data reusables.actions.runner-group-assign-policy-repo %}
{% warning %}
- **Warning**: {% indented_data_reference reusables.github-actions.self-hosted-runner-security spaces=3 %}
+ **Warning**: {% indented_data_reference reusables.actions.self-hosted-runner-security spaces=3 %}
詳しい情報については「[セルフホストランナーについて](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)」を参照してください。
{% endwarning %}
-{% data reusables.github-actions.self-hosted-runner-create-group %}
+{% data reusables.actions.self-hosted-runner-create-group %}
{% elsif ghae or ghes < 3.4 %}
{% data reusables.organizations.navigate-to-org %}
{% data reusables.organizations.org_settings %}
-{% data reusables.github-actions.settings-sidebar-actions-runners %}
+{% data reusables.actions.settings-sidebar-actions-runners %}
1. Under {% ifversion ghes > 3.1 or ghae %}"Runners"{% elsif ghes < 3.2 %}"Self-hosted runners"{% endif %}, click **Add new**, and then **New group**.
@@ -76,7 +76,7 @@ Enterprise の管理者が Organization にランナーグループへのアク
**Warning**
- {% indented_data_reference reusables.github-actions.self-hosted-runner-security spaces=3 %}
+ {% indented_data_reference reusables.actions.self-hosted-runner-security spaces=3 %}
詳しい情報については「[セルフホストランナーについて](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)」を参照してください。
@@ -100,18 +100,18 @@ Enterprise は、セルフホストランナーをグループに追加して、
{% data reusables.enterprise-accounts.actions-tab %}
{% data reusables.enterprise-accounts.actions-runner-groups-tab %}
1. Click **New runner group**.
- {% data reusables.github-actions.runner-group-assign-policy-org %}
+ {% data reusables.actions.runner-group-assign-policy-org %}
{% warning %}
**Warning**
- {% indented_data_reference reusables.github-actions.self-hosted-runner-security spaces=3 %}
+ {% indented_data_reference reusables.actions.self-hosted-runner-security spaces=3 %}
詳しい情報については「[セルフホストランナーについて](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)」を参照してください。
{% endwarning %}
-{% data reusables.github-actions.self-hosted-runner-create-group %}
+{% data reusables.actions.self-hosted-runner-create-group %}
{% elsif ghae or ghes < 3.4 %}
{% data reusables.enterprise-accounts.access-enterprise %}
{% data reusables.enterprise-accounts.policies-tab %}
@@ -128,7 +128,7 @@ Enterprise は、セルフホストランナーをグループに追加して、
**Warning**
- {% indented_data_reference reusables.github-actions.self-hosted-runner-security spaces=3 %}
+ {% indented_data_reference reusables.actions.self-hosted-runner-security spaces=3 %}
詳しい情報については「[セルフホストランナーについて](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)」を参照してください。
@@ -143,21 +143,21 @@ Enterprise は、セルフホストランナーをグループに追加して、
ランナーグループのアクセスポリシーを更新したり、ランナーグループの名前を変更したりすることができます。
{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5091 %}
-{% data reusables.github-actions.self-hosted-runner-groups-navigate-to-repo-org-enterprise %}
-{% data reusables.github-actions.settings-sidebar-actions-runner-groups-selection %}
+{% data reusables.actions.self-hosted-runner-groups-navigate-to-repo-org-enterprise %}
+{% data reusables.actions.settings-sidebar-actions-runner-groups-selection %}
1. Modify the access options, or change the runner group name.
{% warning %}
**Warning**
- {% indented_data_reference reusables.github-actions.self-hosted-runner-security spaces=3 %}
+ {% indented_data_reference reusables.actions.self-hosted-runner-security spaces=3 %}
詳しい情報については「[セルフホストランナーについて](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)」を参照してください。
{% endwarning %}
{% elsif ghae or ghes < 3.4 %}
-{% data reusables.github-actions.self-hosted-runner-configure-runner-group-access %}
+{% data reusables.actions.self-hosted-runner-configure-runner-group-access %}
{% endif %}
{% ifversion ghec or ghes or ghae %}
@@ -179,7 +179,7 @@ Could not find any self-hosted runner group named "rg-runnergroup".
If you don't specify a runner group during the registration process, your new self-hosted runners are automatically assigned to the default group, and can then be moved to another group.
-{% data reusables.github-actions.self-hosted-runner-navigate-to-org-enterprise %}
+{% data reusables.actions.self-hosted-runner-navigate-to-org-enterprise %}
{% ifversion ghec or ghes > 3.3 or ghae-issue-5091 %}
1. In the "Runners" list, click the runner that you want to configure.
2. Select the Runner group dropdown menu.
@@ -195,7 +195,7 @@ If you don't specify a runner group during the registration process, your new se
セルフホストランナーは、グループが削除されると自動的にデフォルトグループに戻ります。
{% ifversion ghes > 3.1 or ghae or ghec %}
-{% data reusables.github-actions.self-hosted-runner-groups-navigate-to-repo-org-enterprise %}
+{% data reusables.actions.self-hosted-runner-groups-navigate-to-repo-org-enterprise %}
1. In the list of groups, to the right of the group you want to delete, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}.
2. グループを削除するには、[**Remove group**] をクリックします。
3. 確認プロンプトを確認し、[**Remove this runner group**] をクリックします。
diff --git a/translations/ja-JP/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md b/translations/ja-JP/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md
index 8621853dcd14..9d6baa9ecfe7 100644
--- a/translations/ja-JP/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md
+++ b/translations/ja-JP/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md
@@ -21,10 +21,10 @@ shortTitle: Monitor & troubleshoot
## Checking the status of a self-hosted runner
-{% data reusables.github-actions.self-hosted-runner-management-permissions-required %}
+{% data reusables.actions.self-hosted-runner-management-permissions-required %}
-{% data reusables.github-actions.self-hosted-runner-navigate-repo-and-org %}
-{% data reusables.github-actions.settings-sidebar-actions-runners %}
+{% data reusables.actions.self-hosted-runner-navigate-repo-and-org %}
+{% data reusables.actions.settings-sidebar-actions-runners %}
1. Under {% ifversion fpt or ghes > 3.1 or ghae or ghec %}"Runners"{% else %}"Self-hosted runners"{% endif %}, you can view a list of registered runners, including the runner's name, labels, and status.
The status can be one of the following:
@@ -46,12 +46,12 @@ For example:
{% mac %}
-{% data reusables.github-actions.self-hosted-runner-check-mac-linux %}
+{% data reusables.actions.self-hosted-runner-check-mac-linux %}
{% endmac %}
{% linux %}
-{% data reusables.github-actions.self-hosted-runner-check-mac-linux %}
+{% data reusables.actions.self-hosted-runner-check-mac-linux %}
{% endlinux %}
{% windows %}
diff --git a/translations/ja-JP/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md b/translations/ja-JP/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md
index 8386bc20ff47..30712c5fc215 100644
--- a/translations/ja-JP/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md
+++ b/translations/ja-JP/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md
@@ -21,54 +21,54 @@ shortTitle: Remove self-hosted runners
{% note %}
-**ノート：** {% data reusables.github-actions.self-hosted-runner-removal-impact %}
+**注釈:** {% data reusables.actions.self-hosted-runner-removal-impact %}
-{% data reusables.github-actions.self-hosted-runner-auto-removal %}
+{% data reusables.actions.self-hosted-runner-auto-removal %}
{% endnote %}
ユーザリポジトリからセルフホストランナーを削除するには、リポジトリのオーナーでなければなりません。 Organizationのリポジトリの場合は、Organizationのオーナーであるか、そのリポジトリの管理アクセスを持っていなければなりません。 セルフホストランナーのマシンへもアクセスできるようにしておくことをおすすめします。 For information about how to remove a self-hosted runner with the REST API, see "[Self-hosted runners](/rest/reference/actions#self-hosted-runners)."
-{% data reusables.github-actions.self-hosted-runner-reusing %}
+{% data reusables.actions.self-hosted-runner-reusing %}
{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5091 %}
{% data reusables.repositories.navigate-to-repo %}
{% data reusables.repositories.sidebar-settings %}
-{% data reusables.github-actions.settings-sidebar-actions %}
-{% data reusables.github-actions.settings-sidebar-actions-runners-updated %}
-{% data reusables.github-actions.settings-sidebar-actions-runner-selection %}
-{% data reusables.github-actions.self-hosted-runner-removing-a-runner-updated %}
+{% data reusables.actions.settings-sidebar-actions %}
+{% data reusables.actions.settings-sidebar-actions-runners-updated %}
+{% data reusables.actions.settings-sidebar-actions-runner-selection %}
+{% data reusables.actions.self-hosted-runner-removing-a-runner-updated %}
{% elsif ghae or ghes < 3.4 %}
{% data reusables.repositories.navigate-to-repo %}
{% data reusables.repositories.sidebar-settings %}
-{% data reusables.github-actions.settings-sidebar-actions-runners %}
-{% data reusables.github-actions.self-hosted-runner-removing-a-runner %}
+{% data reusables.actions.settings-sidebar-actions-runners %}
+{% data reusables.actions.self-hosted-runner-removing-a-runner %}
{% endif %}
## Organizationからのランナーの削除
{% note %}
-**ノート：** {% data reusables.github-actions.self-hosted-runner-removal-impact %}
+**注釈:** {% data reusables.actions.self-hosted-runner-removal-impact %}
-{% data reusables.github-actions.self-hosted-runner-auto-removal %}
+{% data reusables.actions.self-hosted-runner-auto-removal %}
{% endnote %}
Organizationからセルフホストランナーを削除するには、Organizationのオーナーでなければなりません。 セルフホストランナーのマシンへもアクセスできるようにしておくことをおすすめします。 For information about how to remove a self-hosted runner with the REST API, see "[Self-hosted runners](/rest/reference/actions#self-hosted-runners)."
-{% data reusables.github-actions.self-hosted-runner-reusing %}
+{% data reusables.actions.self-hosted-runner-reusing %}
{% ifversion fpt or ghes > 3.3 or ghec %}
{% data reusables.organizations.navigate-to-org %}
{% data reusables.organizations.org_settings %}
-{% data reusables.github-actions.settings-sidebar-actions %}
-{% data reusables.github-actions.settings-sidebar-actions-runners-updated %}
-{% data reusables.github-actions.settings-sidebar-actions-runner-selection %}
-{% data reusables.github-actions.self-hosted-runner-removing-a-runner-updated %}
+{% data reusables.actions.settings-sidebar-actions %}
+{% data reusables.actions.settings-sidebar-actions-runners-updated %}
+{% data reusables.actions.settings-sidebar-actions-runner-selection %}
+{% data reusables.actions.self-hosted-runner-removing-a-runner-updated %}
{% elsif ghes < 3.4 or ghae %}
{% data reusables.organizations.navigate-to-org %}
{% data reusables.organizations.org_settings %}
-{% data reusables.github-actions.settings-sidebar-actions-runners %}
-{% data reusables.github-actions.self-hosted-runner-removing-a-runner %}
+{% data reusables.actions.settings-sidebar-actions-runners %}
+{% data reusables.actions.self-hosted-runner-removing-a-runner %}
{% endif %}
## Enterprise からランナーを削除する
@@ -80,27 +80,27 @@ Organizationからセルフホストランナーを削除するには、Organiza
{% ifversion ghec or ghes or ghae %}
{% note %}
-**ノート：** {% data reusables.github-actions.self-hosted-runner-removal-impact %}
+**注釈:** {% data reusables.actions.self-hosted-runner-removal-impact %}
-{% data reusables.github-actions.self-hosted-runner-auto-removal %}
+{% data reusables.actions.self-hosted-runner-auto-removal %}
{% endnote %}
To remove a self-hosted runner from an enterprise, you must be an enterprise owner. セルフホストランナーのマシンへもアクセスできるようにしておくことをおすすめします。 For information about how to remove a self-hosted runner with the REST API, see the enterprise endpoints in the [{% data variables.product.prodname_actions %} REST API](/rest/reference/actions#self-hosted-runners).
-{% data reusables.github-actions.self-hosted-runner-reusing %}
+{% data reusables.actions.self-hosted-runner-reusing %}
{% ifversion ghec or ghes > 3.3 or ghae-issue-5091 %}
{% data reusables.enterprise-accounts.access-enterprise %}
{% data reusables.enterprise-accounts.policies-tab %}
{% data reusables.enterprise-accounts.actions-tab %}
{% data reusables.enterprise-accounts.actions-runners-tab %}
-{% data reusables.github-actions.settings-sidebar-actions-runner-selection %}
-{% data reusables.github-actions.self-hosted-runner-removing-a-runner-updated %}
+{% data reusables.actions.settings-sidebar-actions-runner-selection %}
+{% data reusables.actions.self-hosted-runner-removing-a-runner-updated %}
{% elsif ghae or ghes < 3.4 %}
{% data reusables.enterprise-accounts.access-enterprise %}
{% data reusables.enterprise-accounts.policies-tab %}
{% data reusables.enterprise-accounts.actions-tab %}
{% data reusables.enterprise-accounts.actions-runners-tab %}
-{% data reusables.github-actions.self-hosted-runner-removing-a-runner %}
+{% data reusables.actions.self-hosted-runner-removing-a-runner %}
{% endif %}
{% endif %}
diff --git a/translations/ja-JP/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md b/translations/ja-JP/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md
index 6a9a9e0bc63b..aedde0c93381 100644
--- a/translations/ja-JP/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md
+++ b/translations/ja-JP/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md
@@ -16,54 +16,54 @@ shortTitle: Label runners
特定の種類のセルフホストランナーにジョブをまわすためのラベルの利用方法に関する情報については、「[ワークフロー内でのセルフホストランナーの利用](/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow)」を参照してください。
-{% data reusables.github-actions.self-hosted-runner-management-permissions-required %}
+{% data reusables.actions.self-hosted-runner-management-permissions-required %}
## カスタムラベルの作成
{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5091 %}
-{% data reusables.github-actions.self-hosted-runner-navigate-to-repo-org-enterprise %}
- {% data reusables.github-actions.settings-sidebar-actions-runner-selection %}
+{% data reusables.actions.self-hosted-runner-navigate-to-repo-org-enterprise %}
+ {% data reusables.actions.settings-sidebar-actions-runner-selection %}
1. In the "Labels" section, click {% octicon "gear" aria-label="The Gear icon" %}.
- 1. In the "Find or create a label" field, type the name of your new label and click **Create new label**. カスタムラベルが作成され、セルフホストランナーに割り当てられます。 カスタムラベルをセルフホストランナーから取り除くことはできますが、現在はラベルを手動で削除することはできません。 {% data reusables.github-actions.actions-unused-labels %}
+ 1. In the "Find or create a label" field, type the name of your new label and click **Create new label**. カスタムラベルが作成され、セルフホストランナーに割り当てられます。 カスタムラベルをセルフホストランナーから取り除くことはできますが、現在はラベルを手動で削除することはできません。 {% data reusables.actions.actions-unused-labels %}
{% elsif ghae or ghes < 3.4 %}
-{% data reusables.github-actions.self-hosted-runner-navigate-to-repo-org-enterprise %}
-{% data reusables.github-actions.self-hosted-runner-list %}
-{% data reusables.github-actions.self-hosted-runner-list-group %}
-{% data reusables.github-actions.self-hosted-runner-labels-view-assigned-labels %}
+{% data reusables.actions.self-hosted-runner-navigate-to-repo-org-enterprise %}
+{% data reusables.actions.self-hosted-runner-list %}
+{% data reusables.actions.self-hosted-runner-list-group %}
+{% data reusables.actions.self-hosted-runner-labels-view-assigned-labels %}
1. "Filter labels（フィルターラベル）"フィールドで、新しいラベルの名前を入力し、**Create new label（新しいラベルの作成）**をクリックしてください。 
-カスタムラベルが作成され、セルフホストランナーに割り当てられます。 カスタムラベルをセルフホストランナーから取り除くことはできますが、現在はラベルを手動で削除することはできません。 {% data reusables.github-actions.actions-unused-labels %}
+カスタムラベルが作成され、セルフホストランナーに割り当てられます。 カスタムラベルをセルフホストランナーから取り除くことはできますが、現在はラベルを手動で削除することはできません。 {% data reusables.actions.actions-unused-labels %}
{% endif %}
## セルフホストランナーへのラベルの割り当て
{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5091 %}
-{% data reusables.github-actions.self-hosted-runner-navigate-to-repo-org-enterprise %}
-{% data reusables.github-actions.settings-sidebar-actions-runner-selection %}
-{% data reusables.github-actions.runner-label-settings %}
+{% data reusables.actions.self-hosted-runner-navigate-to-repo-org-enterprise %}
+{% data reusables.actions.settings-sidebar-actions-runner-selection %}
+{% data reusables.actions.runner-label-settings %}
1. To assign a label to your self-hosted runner, in the "Find or create a label" field, click the label.
{% elsif ghae or ghes < 3.4 %}
-{% data reusables.github-actions.self-hosted-runner-navigate-to-repo-org-enterprise %}
-{% data reusables.github-actions.self-hosted-runner-list %}
-{% data reusables.github-actions.self-hosted-runner-list-group %}
-{% data reusables.github-actions.self-hosted-runner-labels-view-assigned-labels %}
+{% data reusables.actions.self-hosted-runner-navigate-to-repo-org-enterprise %}
+{% data reusables.actions.self-hosted-runner-list %}
+{% data reusables.actions.self-hosted-runner-list-group %}
+{% data reusables.actions.self-hosted-runner-labels-view-assigned-labels %}
1. ラベルをクリックして、セルフホストランナーに割り当ててください。
{% endif %}
## カスタムラベルのセルフホストランナーからの削除
{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5091 %}
-{% data reusables.github-actions.self-hosted-runner-navigate-to-repo-org-enterprise %}
-{% data reusables.github-actions.settings-sidebar-actions-runner-selection %}
-{% data reusables.github-actions.runner-label-settings %}
+{% data reusables.actions.self-hosted-runner-navigate-to-repo-org-enterprise %}
+{% data reusables.actions.settings-sidebar-actions-runner-selection %}
+{% data reusables.actions.runner-label-settings %}
1. In the "Find or create a label" field, assigned labels are marked with the
{% octicon "check" aria-label="The Check icon" %} icon. Click on a marked label to unassign it from your self-hosted runner.
{% elsif ghae or ghes < 3.4 %}
-{% data reusables.github-actions.self-hosted-runner-navigate-to-repo-org-enterprise %}
-{% data reusables.github-actions.self-hosted-runner-list %}
-{% data reusables.github-actions.self-hosted-runner-list-group %}
-{% data reusables.github-actions.self-hosted-runner-labels-view-assigned-labels %}
-1. 割り当てられているラベルをクリックして、セルフホストランナーから削除してください。 {% data reusables.github-actions.actions-unused-labels %}
+{% data reusables.actions.self-hosted-runner-navigate-to-repo-org-enterprise %}
+{% data reusables.actions.self-hosted-runner-list %}
+{% data reusables.actions.self-hosted-runner-list-group %}
+{% data reusables.actions.self-hosted-runner-labels-view-assigned-labels %}
+1. 割り当てられているラベルをクリックして、セルフホストランナーから削除してください。 {% data reusables.actions.actions-unused-labels %}
{% endif %}
## 設定スクリプトを使ったラベルの作成と割り当て
diff --git a/translations/ja-JP/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md b/translations/ja-JP/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md
index f744a1c36f13..49735c8cb9c6 100644
--- a/translations/ja-JP/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md
+++ b/translations/ja-JP/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md
@@ -23,7 +23,7 @@ For information on creating custom and default labels, see "[Using labels with s
Labels allow you to send workflow jobs to specific types of self-hosted runners, based on their shared characteristics. For example, if your job requires a particular hardware component or software package, you can assign a custom label to a runner and then configure your job to only execute on runners with that label.
-{% data reusables.github-actions.self-hosted-runner-labels-runs-on %}
+{% data reusables.actions.self-hosted-runner-labels-runs-on %}
For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/github/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idruns-on)."
diff --git a/translations/ja-JP/content/actions/learn-github-actions/contexts.md b/translations/ja-JP/content/actions/learn-github-actions/contexts.md
index 2b99957271af..d29ec68bda2f 100644
--- a/translations/ja-JP/content/actions/learn-github-actions/contexts.md
+++ b/translations/ja-JP/content/actions/learn-github-actions/contexts.md
@@ -31,7 +31,7 @@ You can access contexts using the expression syntax. For more information, see "
`${{ }}`
{% endraw %}
-{% data reusables.github-actions.context-injection-warning %}
+{% data reusables.actions.context-injection-warning %}
| コンテキスト名 | 種類 | 説明 |
| ---------- | -------- | ---------------------------------------------------------------------------------------------------------------------------------------------------- |
@@ -59,7 +59,7 @@ As part of an expression, you can access context information using one of two sy
### コンテキストを使用する場合の判断
-{% data reusables.github-actions.using-context-or-environment-variables %}
+{% data reusables.actions.using-context-or-environment-variables %}
### Context availability
@@ -139,7 +139,7 @@ The following table indicates where each context and special function can be use
You can print the contents of contexts to the log for debugging. The [`toJSON` function](/actions/learn-github-actions/expressions#tojson) is required to pretty-print JSON objects to the log.
-{% data reusables.github-actions.github-context-warning %}
+{% data reusables.actions.github-context-warning %}
{% raw %}
```yaml{:copy}
@@ -170,8 +170,8 @@ jobs:
`github` コンテキストは、ワークフローの実行および、その実行をトリガーしたイベントの情報を含みます。 You can also read most of the `github` context data in environment variables. 環境変数に関する詳しい情報については、「[環境変数の利用](/actions/automating-your-workflow-with-github-actions/using-environment-variables)」を参照してください。
-{% data reusables.github-actions.github-context-warning %}
-{% data reusables.github-actions.context-injection-warning %}
+{% data reusables.actions.github-context-warning %}
+{% data reusables.actions.context-injection-warning %}
| プロパティ名 | 種類 | 説明 |
| -------------------------- | -------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
@@ -194,9 +194,11 @@ jobs:
{%- 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 %} | | `github.ref_type` | `string` | {% data reusables.actions.ref_type-description %}
{%- endif %}
-| `github.path` | `string` | Path on the runner to the file that sets system `PATH` variables from workflow commands. This file is unique to the current step and is a different file for each step in a job. For more information, see "[Workflow commands for {% data variables.product.prodname_actions %}](/actions/learn-github-actions/workflow-commands-for-github-actions#adding-a-system-path)." | | `github.repository` | `string` | The owner and repository name. `Codertocat/Hello-World`などです。 | | `github.repository_owner` | `string` | The repository owner's name. たとえば`Codertocat`。 | | `github.repositoryUrl` | `string` | The Git URL to the repository. For example, `git://github.com/codertocat/hello-world.git`. | | `github.retention_days` | `string` | The number of days that workflow run logs and artifacts are kept. | | `github.run_id` | `string` | {% data reusables.github-actions.run_id_description %} | | `github.run_number` | `string` | {% data reusables.github-actions.run_number_description %}
+| `github.path` | `string` | Path on the runner to the file that sets system `PATH` variables from workflow commands. This file is unique to the current step and is a different file for each step in a job. For more information, see "[Workflow commands for {% data variables.product.prodname_actions %}](/actions/learn-github-actions/workflow-commands-for-github-actions#adding-a-system-path)." | | `github.repository` | `string` | The owner and repository name. `Codertocat/Hello-World`などです。 | | `github.repository_owner` | `string` | The repository owner's name. たとえば`Codertocat`。 | | `github.repositoryUrl` | `string` | The Git URL to the repository. For example, `git://github.com/codertocat/hello-world.git`. | | `github.retention_days` | `string` | The number of days that workflow run logs and artifacts are kept. | | `github.run_id` | `string` | {% data reusables.actions.run_id_description %} | | `github.run_number` | `string` | {% data reusables.actions.run_number_description %}
{%- ifversion fpt or ghec or ghes > 3.5 or ghae-issue-4722 %}
-| `github.run_attempt` | `string` | A unique number for each attempt of a particular workflow run in a repository. This number begins at 1 for the workflow run's first attempt, and increments with each re-run. | |{% endif %}| | `github.server_url` | `string` | The URL of the GitHub server. For example: `https://github.com`. | | `github.sha` | `string` | The commit SHA that triggered the workflow run. | | `github.token` | `string` | A token to authenticate on behalf of the GitHub App installed on your repository. これは機能的に`GITHUB_TOKEN`シークレットに等価です。 For more information, see "[Automatic token authentication](/actions/security-guides/automatic-token-authentication)." | | `github.workflow` | `string` | The name of the workflow. ワークフローファイルで `name` を指定していない場合、このプロパティの値は、リポジトリ内にあるワークフローファイルのフルパスになります。 | | `github.workspace` | `string` | The default working directory on the runner for steps, and the default location of your repository when using the [`checkout`](https://github.com/actions/checkout) action. |
+| `github.run_attempt` | `string` | A unique number for each attempt of a particular workflow run in a repository. This number begins at 1 for the workflow run's first attempt, and increments with each re-run. |
+{%- endif %}
+| `github.server_url` | `string` | The URL of the GitHub server. For example: `https://github.com`. | | `github.sha` | `string` | The commit SHA that triggered the workflow run. | | `github.token` | `string` | A token to authenticate on behalf of the GitHub App installed on your repository. これは機能的に`GITHUB_TOKEN`シークレットに等価です。 For more information, see "[Automatic token authentication](/actions/security-guides/automatic-token-authentication)." | | `github.workflow` | `string` | The name of the workflow. ワークフローファイルで `name` を指定していない場合、このプロパティの値は、リポジトリ内にあるワークフローファイルのフルパスになります。 | | `github.workspace` | `string` | The default working directory on the runner for steps, and the default location of your repository when using the [`checkout`](https://github.com/actions/checkout) action. |
### Example contents of the `github` context
@@ -512,7 +514,7 @@ The `secrets` context contains the names and values of secrets that are availabl
`GITHUB_TOKEN` is a secret that is automatically created for every workflow run, and is always included in the `secrets` context. For more information, see "[Automatic token authentication](/actions/security-guides/automatic-token-authentication)."
-{% data reusables.github-actions.secrets-redaction-warning %}
+{% data reusables.actions.secrets-redaction-warning %}
| プロパティ名 | 種類 | 説明 |
| ----------------------------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
@@ -534,7 +536,7 @@ The following example contents of the `secrets` context shows the automatic `GIT
### Example usage of the `secrets` context
-{% data reusables.github-actions.github_token-input-example %}
+{% data reusables.actions.github_token-input-example %}
## `strategy` context
diff --git a/translations/ja-JP/content/actions/learn-github-actions/environment-variables.md b/translations/ja-JP/content/actions/learn-github-actions/environment-variables.md
index e3a5e853b1d6..a1dc33e6b564 100644
--- a/translations/ja-JP/content/actions/learn-github-actions/environment-variables.md
+++ b/translations/ja-JP/content/actions/learn-github-actions/environment-variables.md
@@ -147,7 +147,7 @@ The default environment variables that {% data variables.product.prodname_dotcom
{%- 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 %} | | `GITHUB_REF_TYPE` | {% data reusables.actions.ref_type-description %}
{%- endif %}
-| `GITHUB_REPOSITORY` | The owner and repository name. `octocat/Hello-World`などです。 | | `GITHUB_REPOSITORY_OWNER` | The repository owner's name. `octocat`などです。 | | `GITHUB_RETENTION_DAYS` | The number of days that workflow run logs and artifacts are kept. For example, `90`. | | `GITHUB_RUN_ATTEMPT` | A unique number for each attempt of a particular workflow run in a repository. This number begins at 1 for the workflow run's first attempt, and increments with each re-run. For example, `3`. | | `GITHUB_RUN_ID` | {% data reusables.github-actions.run_id_description %} For example, `1658821493`. | | `GITHUB_RUN_NUMBER` | {% data reusables.github-actions.run_number_description %} For example, `3`. | | `GITHUB_SERVER_URL`| The URL of the {% data variables.product.product_name %} server. For example: `https://{% data variables.product.product_url %}`. | `GITHUB_SHA` | The commit SHA that triggered the workflow. たとえば、`ffac537e6cbbf934b08745a378932722df287a53`です。 | | `GITHUB_WORKFLOW` | The name of the workflow. For example, `My test workflow`. If the workflow file doesn't specify a `name`, the value of this variable is the full path of the workflow file in the repository. | | `GITHUB_WORKSPACE` | The default working directory on the runner for steps, and the default location of your repository when using the [`checkout`](https://github.com/actions/checkout) action. たとえば、`/home/runner/work/my-repo-name/my-repo-name`となります。 |
+| `GITHUB_REPOSITORY` | The owner and repository name. `octocat/Hello-World`などです。 | | `GITHUB_REPOSITORY_OWNER` | The repository owner's name. `octocat`などです。 | | `GITHUB_RETENTION_DAYS` | The number of days that workflow run logs and artifacts are kept. For example, `90`. | | `GITHUB_RUN_ATTEMPT` | A unique number for each attempt of a particular workflow run in a repository. This number begins at 1 for the workflow run's first attempt, and increments with each re-run. For example, `3`. | | `GITHUB_RUN_ID` | {% data reusables.actions.run_id_description %} For example, `1658821493`. | | `GITHUB_RUN_NUMBER` | {% data reusables.actions.run_number_description %} For example, `3`. | | `GITHUB_SERVER_URL`| The URL of the {% data variables.product.product_name %} server. For example: `https://{% data variables.product.product_url %}`. | `GITHUB_SHA` | The commit SHA that triggered the workflow. たとえば、`ffac537e6cbbf934b08745a378932722df287a53`です。 | | `GITHUB_WORKFLOW` | The name of the workflow. For example, `My test workflow`. If the workflow file doesn't specify a `name`, the value of this variable is the full path of the workflow file in the repository. | | `GITHUB_WORKSPACE` | The default working directory on the runner for steps, and the default location of your repository when using the [`checkout`](https://github.com/actions/checkout) action. たとえば、`/home/runner/work/my-repo-name/my-repo-name`となります。 |
{%- if actions-runner-arch-envvars %}
| `RUNNER_ARCH` | {% data reusables.actions.runner-arch-description %}
{%- endif %}
diff --git a/translations/ja-JP/content/actions/learn-github-actions/expressions.md b/translations/ja-JP/content/actions/learn-github-actions/expressions.md
index f014d3147aaf..73e1e18aa2fc 100644
--- a/translations/ja-JP/content/actions/learn-github-actions/expressions.md
+++ b/translations/ja-JP/content/actions/learn-github-actions/expressions.md
@@ -25,9 +25,9 @@ You can use expressions to programmatically set environment variables in workflo
`${{ }}`
{% endraw %}
-{% data reusables.github-actions.expression-syntax-if %} `if`条件の詳細については、「[{% data variables.product.prodname_actions %}のためのワークフローの構文](/articles/workflow-syntax-for-github-actions/#jobsjob_idif)」を参照してください。
+{% data reusables.actions.expression-syntax-if %} `if`条件の詳細については、「[{% data variables.product.prodname_actions %}のためのワークフローの構文](/articles/workflow-syntax-for-github-actions/#jobsjob_idif)」を参照してください。
-{% data reusables.github-actions.context-injection-warning %}
+{% data reusables.actions.context-injection-warning %}
#### `if` 条件内の式の例
diff --git a/translations/ja-JP/content/actions/learn-github-actions/understanding-github-actions.md b/translations/ja-JP/content/actions/learn-github-actions/understanding-github-actions.md
index 797dc7cdcee4..76b43c595958 100644
--- a/translations/ja-JP/content/actions/learn-github-actions/understanding-github-actions.md
+++ b/translations/ja-JP/content/actions/learn-github-actions/understanding-github-actions.md
@@ -254,7 +254,7 @@ To understand how billing works for {% data variables.product.prodname_actions %
## サポートへの連絡
-{% data reusables.github-actions.contacting-support %}
+{% data reusables.actions.contacting-support %}
## 参考リンク
diff --git a/translations/ja-JP/content/actions/learn-github-actions/usage-limits-billing-and-administration.md b/translations/ja-JP/content/actions/learn-github-actions/usage-limits-billing-and-administration.md
index 0bd9b6232b10..87738c74e083 100644
--- a/translations/ja-JP/content/actions/learn-github-actions/usage-limits-billing-and-administration.md
+++ b/translations/ja-JP/content/actions/learn-github-actions/usage-limits-billing-and-administration.md
@@ -21,7 +21,7 @@ shortTitle: Workflow billing & limits
{% data reusables.repositories.about-github-actions %} For more information, see "[Understanding {% data variables.product.prodname_actions %}](/actions/learn-github-actions/understanding-github-actions){% ifversion fpt %}."{% elsif ghes or ghec %}" and "[About {% data variables.product.prodname_actions %} for enterprises](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises)."{% endif %}
{% ifversion fpt or ghec %}
-{% data reusables.github-actions.actions-billing %} 詳細は「[{% data variables.product.prodname_actions %} の支払いについて](/billing/managing-billing-for-github-actions/about-billing-for-github-actions)」を参照してください。
+{% data reusables.actions.actions-billing %} 詳細は「[{% data variables.product.prodname_actions %} の支払いについて](/billing/managing-billing-for-github-actions/about-billing-for-github-actions)」を参照してください。
{% else %}
GitHub Actions usage is free for {% data variables.product.prodname_ghe_server %} instances that use self-hosted runners. 詳しい情報については「[セルフホストランナーについて](/actions/hosting-your-own-runners/about-self-hosted-runners)」を参照してください。
{% endif %}
@@ -47,8 +47,8 @@ There are some limits on {% data variables.product.prodname_actions %} usage whe
{% endnote %}
- **ジョブの実行時間** - ワークフロー中のそれぞれのジョブは、最大で6時間の間実行できます。 ジョブがこの制限に達すると、ジョブは終了させられ、完了できずに失敗します。
-{% data reusables.github-actions.usage-workflow-run-time %}
-{% data reusables.github-actions.usage-api-requests %}
+{% data reusables.actions.usage-workflow-run-time %}
+{% data reusables.actions.usage-api-requests %}
- **並行ジョブ** - アカウント内で実行できる並行ジョブ数は、以下の表に示すとおり、利用しているGitHubのプランによります。 この制限を超えた場合、超過のジョブはキューイングされます。
| GitHubプラン | 最大同時ジョブ | 最大同時macOSジョブ |
@@ -57,8 +57,8 @@ There are some limits on {% data variables.product.prodname_actions %} usage whe
| Pro | 40 | 5 |
| Team | 60 | 5 |
| Enterprise | 180 | 50 |
-- **ジョブマトリックス** - {% data reusables.github-actions.usage-matrix-limits %}
-{% data reusables.github-actions.usage-workflow-queue-limits %}
+- **ジョブマトリックス** - {% data reusables.actions.usage-matrix-limits %}
+{% data reusables.actions.usage-workflow-queue-limits %}
{% else %}
使用制限は、セルフホストランナーに適用されます。 詳しい情報については「[セルフホストランナーについて](/actions/hosting-your-own-runners/about-self-hosted-runners/#usage-limits)」を参照してください。
@@ -82,7 +82,7 @@ For more information see, "[Reusing workflows](/actions/learn-github-actions/reu
## 成果物とログの保持ポリシー
-You can configure the artifact and log retention period for your repository, organization, or enterprise account.
+リポジトリ、Organization、または Enterprise アカウントの成果物とログの保持期間を設定できます。
{% data reusables.actions.about-artifact-log-retention %}
@@ -94,7 +94,7 @@ You can configure the artifact and log retention period for your repository, org
## リポジトリあるいはOrganizationでの{% data variables.product.prodname_actions %}の無効化もしくは制限
-{% data reusables.github-actions.disabling-github-actions %}
+{% data reusables.actions.disabling-github-actions %}
詳しい情報については、以下を参照してください。
- "[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)"
@@ -103,7 +103,7 @@ You can configure the artifact and log retention period for your repository, org
## ワークフローの無効化と有効化
-You can enable and disable individual workflows in your repository on {% data variables.product.prodname_dotcom %}.
+{% data variables.product.prodname_dotcom %} のリポジトリで個々のワークフローを有効化または無効化できます。
{% data reusables.actions.scheduled-workflows-disabled %}
diff --git a/translations/ja-JP/content/actions/managing-workflow-runs/removing-workflow-artifacts.md b/translations/ja-JP/content/actions/managing-workflow-runs/removing-workflow-artifacts.md
index e08d27650c95..c93e99d754ef 100644
--- a/translations/ja-JP/content/actions/managing-workflow-runs/removing-workflow-artifacts.md
+++ b/translations/ja-JP/content/actions/managing-workflow-runs/removing-workflow-artifacts.md
@@ -22,7 +22,7 @@ shortTitle: Remove workflow artifacts
{% data reusables.repositories.permissions-statement-write %}
-{% data reusables.github-actions.artifact-log-retention-statement %}
+{% data reusables.actions.artifact-log-retention-statement %}
{% data reusables.repositories.navigate-to-repo %}
{% data reusables.repositories.actions-tab %}
diff --git a/translations/ja-JP/content/actions/migrating-to-github-actions/migrating-from-travis-ci-to-github-actions.md b/translations/ja-JP/content/actions/migrating-to-github-actions/migrating-from-travis-ci-to-github-actions.md
index 3edff338ce0f..7a5b2b593f3c 100644
--- a/translations/ja-JP/content/actions/migrating-to-github-actions/migrating-from-travis-ci-to-github-actions.md
+++ b/translations/ja-JP/content/actions/migrating-to-github-actions/migrating-from-travis-ci-to-github-actions.md
@@ -179,7 +179,7 @@ git:
Travis CI と {% data variables.product.prodname_actions %} はどちらも、カスタム環境変数をテストマトリックスに追加できます。これにより、後のステップで変数を参照できます。
-{% data variables.product.prodname_actions %} では、`include` キーを使用して、カスタム環境変数をマトリックスに追加できます。 {% data reusables.github-actions.matrix-variable-example %}
+{% data variables.product.prodname_actions %} では、`include` キーを使用して、カスタム環境変数をマトリックスに追加できます。 {% data reusables.actions.matrix-variable-example %}
## {% data variables.product.prodname_actions %} の主な機能
diff --git a/translations/ja-JP/content/actions/monitoring-and-troubleshooting-workflows/about-monitoring-and-troubleshooting.md b/translations/ja-JP/content/actions/monitoring-and-troubleshooting-workflows/about-monitoring-and-troubleshooting.md
index c02e8d813911..bb5f1a107378 100644
--- a/translations/ja-JP/content/actions/monitoring-and-troubleshooting-workflows/about-monitoring-and-troubleshooting.md
+++ b/translations/ja-JP/content/actions/monitoring-and-troubleshooting-workflows/about-monitoring-and-troubleshooting.md
@@ -18,7 +18,7 @@ miniTocMaxHeadingLevel: 3
{% if github-runner-dashboard %}
### Monitoring your current jobs in your organization or enterprise
-{% data reusables.github-actions.github-hosted-runners-check-concurrency %}
+{% data reusables.actions.github-hosted-runners-check-concurrency %}
{% endif %}
diff --git a/translations/ja-JP/content/actions/monitoring-and-troubleshooting-workflows/enabling-debug-logging.md b/translations/ja-JP/content/actions/monitoring-and-troubleshooting-workflows/enabling-debug-logging.md
index 16e1206f229c..c7e9281ac102 100644
--- a/translations/ja-JP/content/actions/monitoring-and-troubleshooting-workflows/enabling-debug-logging.md
+++ b/translations/ja-JP/content/actions/monitoring-and-troubleshooting-workflows/enabling-debug-logging.md
@@ -15,12 +15,12 @@ versions:
これらの追加ログは、ワークフローを含むリポジトリにシークレットを設定することで有効になるため、同じ権限要件が適用されます。
-- {% data reusables.github-actions.permissions-statement-secrets-repository %}
+- {% data reusables.actions.permissions-statement-secrets-repository %}
{% ifversion fpt or ghes > 3.0 or ghae or ghec %}
-- {% data reusables.github-actions.permissions-statement-secrets-environment %}
+- {% data reusables.actions.permissions-statement-secrets-environment %}
{% endif %}
-- {% data reusables.github-actions.permissions-statement-secrets-organization %}
-- {% data reusables.github-actions.permissions-statement-secrets-api %}
+- {% data reusables.actions.permissions-statement-secrets-organization %}
+- {% data reusables.actions.permissions-statement-secrets-api %}
シークレットの設定に関する詳しい情報については、「[暗号化されたシークレットの作成と利用](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)」を参照してください。
diff --git a/translations/ja-JP/content/actions/monitoring-and-troubleshooting-workflows/using-workflow-run-logs.md b/translations/ja-JP/content/actions/monitoring-and-troubleshooting-workflows/using-workflow-run-logs.md
index 857241eaa50a..5e2c35f47c6a 100644
--- a/translations/ja-JP/content/actions/monitoring-and-troubleshooting-workflows/using-workflow-run-logs.md
+++ b/translations/ja-JP/content/actions/monitoring-and-troubleshooting-workflows/using-workflow-run-logs.md
@@ -19,7 +19,7 @@ versions:
{% data variables.product.prodname_actions %}は、Checks APIを使用してワークフローのステータス、結果、ログを出力します。 {% data variables.product.prodname_dotcom %} は、ワークフローの実行に対してそれぞれ新しいチェックスイートを作成します。 チェックスイートには、ワークフロー内の各ジョブに対するチェック実行が含まれ、各ジョブにはステップが含まれています。 {% data variables.product.prodname_actions %}は、ワークフローのステップとして実行されます。 Checks APIに関する詳しい情報については「[チェック](/rest/reference/checks)」を参照してください。
-{% data reusables.github-actions.invalid-workflow-files %}
+{% data reusables.actions.invalid-workflow-files %}
## ログを表示してエラーを診断する
diff --git a/translations/ja-JP/content/actions/publishing-packages/publishing-docker-images.md b/translations/ja-JP/content/actions/publishing-packages/publishing-docker-images.md
index 4a78858f3b8c..bf831d37801d 100644
--- a/translations/ja-JP/content/actions/publishing-packages/publishing-docker-images.md
+++ b/translations/ja-JP/content/actions/publishing-packages/publishing-docker-images.md
@@ -50,7 +50,7 @@ topics:
## Docker Hubへのイメージの公開
-{% data reusables.github-actions.release-trigger-workflow %}
+{% data reusables.actions.release-trigger-workflow %}
以下のワークフロー例では、Docker の `login-action` アクションと `build-push-action` アクションを使用して Docker イメージをビルドし、ビルドが成功すればそのイメージを Docker Hub にプッシュします。
@@ -108,7 +108,7 @@ The above workflow checks out the {% data variables.product.prodname_dotcom %} r
## {% data variables.product.prodname_registry %}へのイメージの公開
-{% data reusables.github-actions.release-trigger-workflow %}
+{% data reusables.actions.release-trigger-workflow %}
In the example workflow below, we use the Docker `login-action`{% ifversion fpt or ghec %}, `metadata-action`,{% endif %} and `build-push-action` actions to build the Docker image, and if the build succeeds, push the built image to {% data variables.product.prodname_registry %}.
diff --git a/translations/ja-JP/content/actions/publishing-packages/publishing-java-packages-with-gradle.md b/translations/ja-JP/content/actions/publishing-packages/publishing-java-packages-with-gradle.md
index eb7b1c82bae9..dd4ad3149982 100644
--- a/translations/ja-JP/content/actions/publishing-packages/publishing-java-packages-with-gradle.md
+++ b/translations/ja-JP/content/actions/publishing-packages/publishing-java-packages-with-gradle.md
@@ -23,7 +23,7 @@ shortTitle: Java packages with Gradle
## はじめに
-{% data reusables.github-actions.publishing-java-packages-intro %}
+{% data reusables.actions.publishing-java-packages-intro %}
## 必要な環境
@@ -104,7 +104,7 @@ jobs:
MAVEN_PASSWORD: {% raw %}${{ secrets.OSSRH_TOKEN }}{% endraw %}
```
-{% data reusables.github-actions.gradle-workflow-steps %}
+{% data reusables.actions.gradle-workflow-steps %}
1. Runs the [`gradle/gradle-build-action`](https://github.com/gradle/gradle-build-action) action with the `publish` argument to publish to the `OSSRH` Maven repository. 環境変数の`MAVEN_USERNAME`は`OSSRH_USERNAME`シークレットの内容で、環境変数の`MAVEN_PASSWORD`は`OSSRH_TOKEN`シークレットの内容で設定されます。
ワークフロー中でのシークレットの利用に関する詳しい情報については「[暗号化されたシークレットの作成と利用](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)」を参照してください。
@@ -115,7 +115,7 @@ jobs:
_build.gradle_のpublishingブロックには、{% data variables.product.prodname_registry %}を指す新しいMavenリポジトリを定義できます。 そのリポジトリの設定では、CIワークフローの実行で設定された環境変数を活用することもできます。 環境変数の`GITHUB_ACTOR`はユーザ名として利用でき、環境変数の`GITHUB_TOKEN`には`GITHUB_TOKEN`シークレットを設定できます。
-{% data reusables.github-actions.github-token-permissions %}
+{% data reusables.actions.github-token-permissions %}
For example, if your organization is named "octocat" and your repository is named "hello-world", then the {% data variables.product.prodname_registry %} configuration in _build.gradle_ would look similar to the below example.
@@ -174,7 +174,7 @@ jobs:
GITHUB_TOKEN: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
```
-{% data reusables.github-actions.gradle-workflow-steps %}
+{% data reusables.actions.gradle-workflow-steps %}
1. Runs the [`gradle/gradle-build-action`](https://github.com/gradle/gradle-build-action) action with the `publish` argument to publish to {% data variables.product.prodname_registry %}. 環境変数`GITHUB_TOKEN`には、`GITHUB_TOKEN`シークレットの内容が設定されます。 {% ifversion fpt or ghes > 3.1 or ghae or ghec %}The `permissions` key specifies the access that the `GITHUB_TOKEN` secret will allow.{% endif %}
ワークフロー中でのシークレットの利用に関する詳しい情報については「[暗号化されたシークレットの作成と利用](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)」を参照してください。
@@ -255,7 +255,7 @@ jobs:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}{% endraw %}
```
-{% data reusables.github-actions.gradle-workflow-steps %}
+{% data reusables.actions.gradle-workflow-steps %}
1. Runs the [`gradle/gradle-build-action`](https://github.com/gradle/gradle-build-action) action with the `publish` argument to publish to the `OSSRH` Maven repository and {% data variables.product.prodname_registry %}. 環境変数の`MAVEN_USERNAME`は`OSSRH_USERNAME`シークレットの内容で、環境変数の`MAVEN_PASSWORD`は`OSSRH_TOKEN`シークレットの内容で設定されます。 環境変数`GITHUB_TOKEN`には、`GITHUB_TOKEN`シークレットの内容が設定されます。 {% ifversion fpt or ghes > 3.1 or ghae or ghec %}The `permissions` key specifies the access that the `GITHUB_TOKEN` secret will allow.{% endif %}
ワークフロー中でのシークレットの利用に関する詳しい情報については「[暗号化されたシークレットの作成と利用](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)」を参照してください。
diff --git a/translations/ja-JP/content/actions/publishing-packages/publishing-java-packages-with-maven.md b/translations/ja-JP/content/actions/publishing-packages/publishing-java-packages-with-maven.md
index 03531784f87e..76c4ab85a88f 100644
--- a/translations/ja-JP/content/actions/publishing-packages/publishing-java-packages-with-maven.md
+++ b/translations/ja-JP/content/actions/publishing-packages/publishing-java-packages-with-maven.md
@@ -23,7 +23,7 @@ shortTitle: Java packages with Maven
## はじめに
-{% data reusables.github-actions.publishing-java-packages-intro %}
+{% data reusables.actions.publishing-java-packages-intro %}
## 必要な環境
@@ -105,7 +105,7 @@ jobs:
1. プロジェクトのリポジトリのコピーをチェックアウトします。
1. Java JDKをセットアップし、環境変数の`MAVEN_USERNAME`と`MAVEN_PASSWORD`を使って`ossrh`リポジトリに対する認証を追加するためにMavenの_settings.xml_ファイルも設定します。
-1. {% data reusables.github-actions.publish-to-maven-workflow-step %}
+1. {% data reusables.actions.publish-to-maven-workflow-step %}
ワークフロー中でのシークレットの利用に関する詳しい情報については「[暗号化されたシークレットの作成と利用](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)」を参照してください。
@@ -115,7 +115,7 @@ jobs:
このワークフロー内では、`setup-java`アクションを利用できます。 このアクションは、指定されたバージョンのJDKを`PATH`にインストールし、{% data variables.product.prodname_registry %}にパッケージを公開するためにMavenの_settings.xml_もセットアップします。 生成された_settings.xml_は、環境変数の`GITHUB_ACTOR`をユーザ名、`GITHUB_TOKEN`をパスワードとして使い、`github`の`id`でサーバーの認証を定義します。 `GITHUB_TOKEN` 環境変数には、特別な `GITHUB_TOKEN` シークレットの値が割り当てられます。
-{% data reusables.github-actions.github-token-permissions %}
+{% data reusables.actions.github-token-permissions %}
Mavenベースのプロジェクトでは、{% data variables.product.prodname_registry %}のエンドポイントを指す`github`の`id`で_pom.xml_ファイル中に配布リポジトリを作成することによって、これらの設定を利用できます。
@@ -165,7 +165,7 @@ jobs:
1. プロジェクトのリポジトリのコピーをチェックアウトします。
1. Java JDKをセットアップし、自動的にMavenの_settings.xml_ファイルを設定して環境変数の`GITHUB_TOKEN`を使うように`github` Mavenリポジトリの認証を追加します。
-1. {% data reusables.github-actions.publish-to-packages-workflow-step %}
+1. {% data reusables.actions.publish-to-packages-workflow-step %}
ワークフロー中でのシークレットの利用に関する詳しい情報については「[暗号化されたシークレットの作成と利用](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)」を参照してください。
@@ -218,8 +218,8 @@ jobs:
1. プロジェクトのリポジトリのコピーをチェックアウトします。
1. 1回目の`setup-java`の呼び出しを行います。 これはMavenの_settings.xml_ファイルを`ossrh`に対して設定し、認証のオプションを次のステップで定義される環境変数に設定します。
-1. {% data reusables.github-actions.publish-to-maven-workflow-step %}
+1. {% data reusables.actions.publish-to-maven-workflow-step %}
1. 2回目の`setup-java`の呼び出しを行います。 Mavenの_settings.xml_ファイルを{% data variables.product.prodname_registry %}に対して自動的に設定します。
-1. {% data reusables.github-actions.publish-to-packages-workflow-step %}
+1. {% data reusables.actions.publish-to-packages-workflow-step %}
ワークフロー中でのシークレットの利用に関する詳しい情報については「[暗号化されたシークレットの作成と利用](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)」を参照してください。
diff --git a/translations/ja-JP/content/actions/publishing-packages/publishing-nodejs-packages.md b/translations/ja-JP/content/actions/publishing-packages/publishing-nodejs-packages.md
index d98783379d2a..eb58d2695c05 100644
--- a/translations/ja-JP/content/actions/publishing-packages/publishing-nodejs-packages.md
+++ b/translations/ja-JP/content/actions/publishing-packages/publishing-nodejs-packages.md
@@ -43,7 +43,7 @@ Node.jsプロジェクトのためのCIワークフローの作成に関する
*package.json*ファイル中の`name`及び`version`フィールドは、レジストリがパッケージをレジストリにリンクするために利用するユニークな識別子を作成します。 *package.json*ファイル中に`description`を含めることによって、パッケージのリストページのためのまとめを追加できます。 詳しい情報については、npmのドキュメンテーション中の「[package.jsonファイルの作成](https://docs.npmjs.com/creating-a-package-json-file)」及び「[Node.jsモジュールの作成](https://docs.npmjs.com/creating-node-js-modules)」を参照してください。
-ローカルの*.npmrc*ファイルがあり、`registry`の値が指定されている場合、`npm publish`コマンドは*.npmrc*ファイルで設定されたレジストリを使います。 {% data reusables.github-actions.setup-node-intro %}
+ローカルの*.npmrc*ファイルがあり、`registry`の値が指定されている場合、`npm publish`コマンドは*.npmrc*ファイルで設定されたレジストリを使います。 {% data reusables.actions.setup-node-intro %}
`setup-node`アクションを使えば、ランナーにインストールされたNode.jsのバージョンを指定できます。
@@ -115,7 +115,7 @@ Please note that you need to set the `registry-url` to `https://registry.npmjs.o
### 宛先リポジトリへの認証
-ワークフロー中で{% data variables.product.prodname_registry %}レジストリに対して認証を受けた操作をするには、`GITHUB_TOKEN`が使えます。 {% data reusables.github-actions.github-token-permissions %}
+ワークフロー中で{% data variables.product.prodname_registry %}レジストリに対して認証を受けた操作をするには、`GITHUB_TOKEN`が使えます。 {% data reusables.actions.github-token-permissions %}
パッケージを別のリポジトリに公開する場合は、宛先リポジトリ内のパッケージに書き込む権限を持つ個人アクセストークン (PAT) を使用する必要があります。 詳しい情報については、「[個人アクセストークンを作成する](/github/authenticating-to-github/creating-a-personal-access-token)」および「[暗号化されたシークレット](/actions/reference/encrypted-secrets)」を参照してください。
diff --git a/translations/ja-JP/content/actions/security-guides/automatic-token-authentication.md b/translations/ja-JP/content/actions/security-guides/automatic-token-authentication.md
index 16a0f24f9588..a6cdabb850e1 100644
--- a/translations/ja-JP/content/actions/security-guides/automatic-token-authentication.md
+++ b/translations/ja-JP/content/actions/security-guides/automatic-token-authentication.md
@@ -39,11 +39,11 @@ You can use the `GITHUB_TOKEN` by using the standard syntax for referencing secr
{% endnote %}
{% endif %}
-{% data reusables.github-actions.actions-do-not-trigger-workflows %}
+{% data reusables.actions.actions-do-not-trigger-workflows %}
### Example 1: passing the `GITHUB_TOKEN` as an input
-{% data reusables.github-actions.github_token-input-example %}
+{% data reusables.actions.github_token-input-example %}
### Example 2: calling the REST API
@@ -123,7 +123,7 @@ You can see the permissions that `GITHUB_TOKEN` had for a specific job in the "S
You can use the `permissions` key in your workflow file to modify permissions for the `GITHUB_TOKEN` for an entire workflow or for individual jobs. This allows you to configure the minimum required permissions for a workflow or job. When the `permissions` key is used, all unspecified permissions are set to no access, with the exception of the `metadata` scope, which always gets read access.
-{% data reusables.github-actions.forked-write-permission %}
+{% data reusables.actions.forked-write-permission %}
The two workflow examples earlier in this article show the `permissions` key being used at the workflow level, and at the job level. In [Example 1](#example-1-passing-the-github_token-as-an-input) the two permissions are specified for the entire workflow. In [Example 2](#example-2-calling-the-rest-api) write access is granted for one scope for a single job.
diff --git a/translations/ja-JP/content/actions/security-guides/encrypted-secrets.md b/translations/ja-JP/content/actions/security-guides/encrypted-secrets.md
index be53470b6ad8..a603442f413a 100644
--- a/translations/ja-JP/content/actions/security-guides/encrypted-secrets.md
+++ b/translations/ja-JP/content/actions/security-guides/encrypted-secrets.md
@@ -21,7 +21,7 @@ versions:
シークレットは暗号化された環境変数で、Organization{% ifversion fpt or ghes > 3.0 or ghae or ghec %} リポジトリ、あるいはリポジトリ環境{% else %}あるいはリポジトリ{% endif %}に作成できます。 作成したシークレットは、{% data variables.product.prodname_actions %}ワークフローで利用できます。 {% data variables.product.prodname_dotcom %}はシークレットが{% data variables.product.prodname_dotcom %}に到達する前に暗号化され、ワークフローで使用されるまで暗号化されたままになっていることを確実にするのを助けるために[libsodium sealed box](https://libsodium.gitbook.io/doc/public-key_cryptography/sealed_boxes)を使います。
-{% data reusables.github-actions.secrets-org-level-overview %}
+{% data reusables.actions.secrets-org-level-overview %}
{% ifversion fpt or ghes > 3.0 or ghae or ghec %}
環境レベルで保存されたシークレットについては、それらへのアクセスを制御するために必須のレビュー担当者を有効化することができます。 必須の承認者によって許可されるまで、ワークフローのジョブは環境のシークレットにアクセスできません。
@@ -53,7 +53,7 @@ versions:
ファイルを編集するアクセス権を持っていれば、ワークフローファイル中の暗号化されたシークレットを使い、読み取ることができます。 詳細は「[{% data variables.product.prodname_dotcom %} 上のアクセス権限](/github/getting-started-with-github/access-permissions-on-github)」を参照してください。
-{% data reusables.github-actions.secrets-redaction-warning %}
+{% data reusables.actions.secrets-redaction-warning %}
{% ifversion fpt or ghes > 3.0 or ghae or ghec %}
Organization及びリポジトリのシークレットはワークフローの実行がキューイングされた時点で読まれ、環境のシークレットは環境を参照しているジョブが開始された時点で読まれます。
@@ -73,13 +73,13 @@ REST API を使用してシークレットを管理することもできます
## リポジトリに暗号化されたシークレットを作成する
-{% data reusables.github-actions.permissions-statement-secrets-repository %}
+{% data reusables.actions.permissions-statement-secrets-repository %}
{% webui %}
{% data reusables.repositories.navigate-to-repo %}
{% data reusables.repositories.sidebar-settings %}
-{% data reusables.github-actions.sidebar-secret %}
+{% data reusables.actions.sidebar-secret %}
1. **New repository secret（新しいリポジトリのシークレット）**をクリックしてください。
1. **[Name（名前）]** 入力ボックスにシークレットの名前を入力します。
1. シークレットの値を入力します。
@@ -113,13 +113,13 @@ To list all secrets for the repository, use the `gh secret list` subcommand.
## 環境の暗号化されたシークレットの生成
-{% data reusables.github-actions.permissions-statement-secrets-environment %}
+{% data reusables.actions.permissions-statement-secrets-environment %}
{% webui %}
{% data reusables.repositories.navigate-to-repo %}
{% data reusables.repositories.sidebar-settings %}
-{% data reusables.github-actions.sidebar-environment %}
+{% data reusables.actions.sidebar-environment %}
1. シークレットを追加したい環境をクリックしてください。
2. **Environment secrets（環境のシークレット）**の下で、**Add secret（シークレットの追加）**をクリックしてください。
3. **[Name（名前）]** 入力ボックスにシークレットの名前を入力します。
@@ -150,13 +150,13 @@ gh secret list --env environment-name
Organizationでシークレットを作成する場合、ポリシーを使用して、そのシークレットにアクセスできるリポジトリを制限できます。 たとえば、すべてのリポジトリにアクセスを許可したり、プライベート リポジトリまたは指定したリポジトリ のリストのみにアクセスを制限したりできます。
-{% data reusables.github-actions.permissions-statement-secrets-organization %}
+{% data reusables.actions.permissions-statement-secrets-organization %}
{% webui %}
{% data reusables.organizations.navigate-to-org %}
{% data reusables.organizations.org_settings %}
-{% data reusables.github-actions.sidebar-secret %}
+{% data reusables.actions.sidebar-secret %}
1. **New organization secret（新しいOrganizationのシークレット）**をクリックしてください。
1. **[Name（名前）]** 入力ボックスにシークレットの名前を入力します。
1. シークレットの **Value（値）** を入力します。
@@ -209,7 +209,7 @@ Organization内のシークレットに適用されているアクセス ポリ
{% data reusables.organizations.navigate-to-org %}
{% data reusables.organizations.org_settings %}
-{% data reusables.github-actions.sidebar-secret %}
+{% data reusables.actions.sidebar-secret %}
1. シークレットのリストには、設定済みのアクセス許可とポリシーが含まれます。 例: 
1. 各シークレットに設定されているアクセス許可の詳細については、[**Update（更新）**] をクリックしてください。
diff --git a/translations/ja-JP/content/actions/using-containerized-services/about-service-containers.md b/translations/ja-JP/content/actions/using-containerized-services/about-service-containers.md
index fb3ed2f6d125..f3e4e5342cbd 100644
--- a/translations/ja-JP/content/actions/using-containerized-services/about-service-containers.md
+++ b/translations/ja-JP/content/actions/using-containerized-services/about-service-containers.md
@@ -25,7 +25,7 @@ topics:
サービスコンテナは、ワークフロー中のそれぞれのジョブに対して設定できます。 {% data variables.product.prodname_dotcom %}は新しいDockerコンテナをワークフロー中で設定された各サービスに対して作成し、ジョブが完了したときにそのサービスコンテナを破棄します。 ジョブ中のステップは、同じジョブの一部であるすべてのサービスコンテナと通信できます。
-{% data reusables.github-actions.docker-container-os-support %}
+{% data reusables.actions.docker-container-os-support %}
## サービスコンテナとの通信
diff --git a/translations/ja-JP/content/actions/using-containerized-services/creating-postgresql-service-containers.md b/translations/ja-JP/content/actions/using-containerized-services/creating-postgresql-service-containers.md
index db650cbe9cc7..2e97bedd4553 100644
--- a/translations/ja-JP/content/actions/using-containerized-services/creating-postgresql-service-containers.md
+++ b/translations/ja-JP/content/actions/using-containerized-services/creating-postgresql-service-containers.md
@@ -24,11 +24,11 @@ topics:
このガイドでは、Docker Hubの`postgres`イメージを使ってサービスコンテナを設定するワークフローの例を紹介します。 ワークフローの実行スクリプトは、PostgreSQL サービスに接続し、テーブルを作成してから、データを入力します。 ワークフローが PostgreSQL テーブルを作成してデータを入力することをテストするために、スクリプトはテーブルからコンソールにデータを出力します。
-{% data reusables.github-actions.docker-container-os-support %}
+{% data reusables.actions.docker-container-os-support %}
## 必要な環境
-{% data reusables.github-actions.service-container-prereqs %}
+{% data reusables.actions.service-container-prereqs %}
YAML、{% data variables.product.prodname_actions %}の構文、PosgreSQLの基本な理解があれば役立つかも知れません。 詳しい情報については、以下を参照してください。
@@ -37,9 +37,9 @@ YAML、{% data variables.product.prodname_actions %}の構文、PosgreSQLの基
## コンテナ内でのジョブの実行
-{% data reusables.github-actions.container-jobs-intro %}
+{% data reusables.actions.container-jobs-intro %}
-{% data reusables.github-actions.copy-workflow-file %}
+{% data reusables.actions.copy-workflow-file %}
{% raw %}
```yaml{:copy}
@@ -95,9 +95,9 @@ jobs:
### ランナージョブの設定
-{% data reusables.github-actions.service-container-host %}
+{% data reusables.actions.service-container-host %}
-{% data reusables.github-actions.postgres-label-description %}
+{% data reusables.actions.postgres-label-description %}
```yaml{:copy}
jobs:
@@ -127,7 +127,7 @@ jobs:
### ステップの設定
-{% data reusables.github-actions.service-template-steps %}
+{% data reusables.actions.service-template-steps %}
```yaml{:copy}
steps:
@@ -153,7 +153,7 @@ steps:
POSTGRES_PORT: 5432
```
-{% data reusables.github-actions.postgres-environment-variables %}
+{% data reusables.actions.postgres-environment-variables %}
PostgreSQLサービスのホスト名は、ワークフロー中で設定されたラベルで、ここでは`postgres`です。 同じユーザー定義ブリッジネットワーク上のDockerコンテナは、デフォルトですべてのポートをオープンするので、サービスコンテナにはデフォルトのPostgreSQLのポートである5432でアクセスできます。
@@ -161,7 +161,7 @@ PostgreSQLサービスのホスト名は、ワークフロー中で設定され
ランナーマシン上で直接ジョブを実行する場合、サービスコンテナ上のポートをDockerホスト上のポートにマップしなければなりません。 Dockerホストからサービスコンテナへは、`localhost`とDockerホストのポート番号を使ってアクセスできます。
-{% data reusables.github-actions.copy-workflow-file %}
+{% data reusables.actions.copy-workflow-file %}
{% raw %}
```yaml{:copy}
@@ -219,9 +219,9 @@ jobs:
### ランナージョブの設定
-{% data reusables.github-actions.service-container-host-runner %}
+{% data reusables.actions.service-container-host-runner %}
-{% data reusables.github-actions.postgres-label-description %}
+{% data reusables.actions.postgres-label-description %}
このワークフローはPostgreSQLサービスコンテナ上のポート5432をDockerホストにマップします。 `ports`キーワードに関する詳しい情報については「[サービスコンテナについて](/actions/automating-your-workflow-with-github-actions/about-service-containers#mapping-docker-host-and-service-container-ports)」を参照してください。
@@ -254,7 +254,7 @@ jobs:
### ステップの設定
-{% data reusables.github-actions.service-template-steps %}
+{% data reusables.actions.service-template-steps %}
```yaml{:copy}
steps:
@@ -280,9 +280,9 @@ steps:
POSTGRES_PORT: 5432
```
-{% data reusables.github-actions.postgres-environment-variables %}
+{% data reusables.actions.postgres-environment-variables %}
-{% data reusables.github-actions.service-container-localhost %}
+{% data reusables.actions.service-container-localhost %}
## PostgreSQLサービスコンテナのテスト
@@ -290,7 +290,7 @@ steps:
*client.js*を修正して、ワークフローで必要なPostgreSQLの操作を含めることができます。 この例では、スクリプトは PostgreSQL サービスに接続し、`postgres` データベースにテーブルを追加し、プレースホルダーデータを挿入してから、データを取得します。
-{% data reusables.github-actions.service-container-add-script %}
+{% data reusables.actions.service-container-add-script %}
```javascript{:copy}
const { Client } = require('pg');
diff --git a/translations/ja-JP/content/actions/using-containerized-services/creating-redis-service-containers.md b/translations/ja-JP/content/actions/using-containerized-services/creating-redis-service-containers.md
index 2689b71babb3..04603bf8d9bf 100644
--- a/translations/ja-JP/content/actions/using-containerized-services/creating-redis-service-containers.md
+++ b/translations/ja-JP/content/actions/using-containerized-services/creating-redis-service-containers.md
@@ -24,11 +24,11 @@ topics:
このガイドでは、Docker Hubの`redis`イメージを使ってサービスコンテナを設定するワークフローの例を紹介します。 このワークフローは、Redisのクライアントを作成してクライアントにデータを展開するスクリプトを実行します。 Redisクライアントを作成して展開するワークフローをテストするために、このスクリプトはクライアントのデータをコンソールに出力します。
-{% data reusables.github-actions.docker-container-os-support %}
+{% data reusables.actions.docker-container-os-support %}
## 必要な環境
-{% data reusables.github-actions.service-container-prereqs %}
+{% data reusables.actions.service-container-prereqs %}
YAML、{% data variables.product.prodname_actions %}の構文、Redisの基本な理解があれば役立つかも知れません。 詳しい情報については、以下を参照してください。
@@ -37,9 +37,9 @@ YAML、{% data variables.product.prodname_actions %}の構文、Redisの基本
## コンテナ内でのジョブの実行
-{% data reusables.github-actions.container-jobs-intro %}
+{% data reusables.actions.container-jobs-intro %}
-{% data reusables.github-actions.copy-workflow-file %}
+{% data reusables.actions.copy-workflow-file %}
{% raw %}
```yaml{:copy}
@@ -92,9 +92,9 @@ jobs:
### コンテナジョブの設定
-{% data reusables.github-actions.service-container-host %}
+{% data reusables.actions.service-container-host %}
-{% data reusables.github-actions.redis-label-description %}
+{% data reusables.actions.redis-label-description %}
```yaml{:copy}
jobs:
@@ -121,7 +121,7 @@ jobs:
### ステップの設定
-{% data reusables.github-actions.service-template-steps %}
+{% data reusables.actions.service-template-steps %}
```yaml{:copy}
steps:
@@ -146,7 +146,7 @@ steps:
REDIS_PORT: 6379
```
-{% data reusables.github-actions.redis-environment-variables %}
+{% data reusables.actions.redis-environment-variables %}
Redisサービスのホスト名は、ワークフロー中で設定されたラベルで、ここでは`redis`です。 同じユーザー定義ブリッジネットワーク上のDockerコンテナは、デフォルトですべてのポートをオープンするので、サービスコンテナにはデフォルトのRedisのポートである6379でアクセスできます。
@@ -154,7 +154,7 @@ Redisサービスのホスト名は、ワークフロー中で設定されたラ
ランナーマシン上で直接ジョブを実行する場合、サービスコンテナ上のポートをDockerホスト上のポートにマップしなければなりません。 Dockerホストからサービスコンテナへは、`localhost`とDockerホストのポート番号を使ってアクセスできます。
-{% data reusables.github-actions.copy-workflow-file %}
+{% data reusables.actions.copy-workflow-file %}
{% raw %}
```yaml{:copy}
@@ -209,9 +209,9 @@ jobs:
### ランナージョブの設定
-{% data reusables.github-actions.service-container-host-runner %}
+{% data reusables.actions.service-container-host-runner %}
-{% data reusables.github-actions.redis-label-description %}
+{% data reusables.actions.redis-label-description %}
このワークフローはRedisサービスコンテナ上のポート6379をDockerホストにマップします。 `ports`キーワードに関する詳しい情報については「[サービスコンテナについて](/actions/automating-your-workflow-with-github-actions/about-service-containers#mapping-docker-host-and-service-container-ports)」を参照してください。
@@ -241,7 +241,7 @@ jobs:
### ステップの設定
-{% data reusables.github-actions.service-template-steps %}
+{% data reusables.actions.service-template-steps %}
```yaml{:copy}
steps:
@@ -267,9 +267,9 @@ steps:
REDIS_PORT: 6379
```
-{% data reusables.github-actions.redis-environment-variables %}
+{% data reusables.actions.redis-environment-variables %}
-{% data reusables.github-actions.service-container-localhost %}
+{% data reusables.actions.service-container-localhost %}
## Redisサービスコンテナのテスト
@@ -277,7 +277,7 @@ steps:
*client.js*を修正して、ワークフローで必要なRedisの操作を含めることができます。 この例では、スクリプトはRedisクライアントのインスタンスを作成し、プレースホルダーデータを追加し、そしてそのデータを取り出します。
-{% data reusables.github-actions.service-container-add-script %}
+{% data reusables.actions.service-container-add-script %}
```javascript{:copy}
const redis = require("redis");
diff --git a/translations/ja-JP/content/actions/using-github-hosted-runners/about-github-hosted-runners.md b/translations/ja-JP/content/actions/using-github-hosted-runners/about-github-hosted-runners.md
index 662d33b84ffa..0021f07728f9 100644
--- a/translations/ja-JP/content/actions/using-github-hosted-runners/about-github-hosted-runners.md
+++ b/translations/ja-JP/content/actions/using-github-hosted-runners/about-github-hosted-runners.md
@@ -29,7 +29,7 @@ You can specify the runner type for each job in a workflow. Each job in a workfl
{% ifversion not ghes %}
-{% data reusables.github-actions.runner-app-open-source %}
+{% data reusables.actions.runner-app-open-source %}
### Cloud hosts for {% data variables.product.prodname_dotcom %}-hosted runners
@@ -39,7 +39,7 @@ You can specify the runner type for each job in a workflow. Each job in a workfl
### Workflow continuity for {% data variables.product.prodname_dotcom %}-hosted runners
-{% data reusables.github-actions.runner-workflow-continuity %}
+{% data reusables.actions.runner-workflow-continuity %}
In addition, if the workflow run has been successfully queued, but has not been processed by a {% data variables.product.prodname_dotcom %}-hosted runner within 45 minutes, then the queued workflow run is discarded.
@@ -61,7 +61,7 @@ Hardware specification for macOS virtual machines:
- 14 GB of RAM memory
- 14 GB of SSD disk space
-{% data reusables.github-actions.supported-github-runners %}
+{% data reusables.actions.supported-github-runners %}
Workflow logs list the runner used to run a job. For more information, see "[Viewing workflow run history](/actions/managing-workflow-runs/viewing-workflow-run-history)."
diff --git a/translations/ja-JP/content/actions/using-github-hosted-runners/monitoring-your-current-jobs.md b/translations/ja-JP/content/actions/using-github-hosted-runners/monitoring-your-current-jobs.md
index ac5027e2afb7..f1d8a12e1fcf 100644
--- a/translations/ja-JP/content/actions/using-github-hosted-runners/monitoring-your-current-jobs.md
+++ b/translations/ja-JP/content/actions/using-github-hosted-runners/monitoring-your-current-jobs.md
@@ -13,8 +13,8 @@ shortTitle: Monitoring your current jobs
You can get a list of all jobs currently running on {% data variables.product.prodname_dotcom %}-hosted runners in your organization or enterprise.
-{% data reusables.github-actions.github-hosted-runners-navigate-to-repo-org-enterprise %}
-{% data reusables.github-actions.github-hosted-runners-table-entry %}
+{% data reusables.actions.github-hosted-runners-navigate-to-repo-org-enterprise %}
+{% data reusables.actions.github-hosted-runners-table-entry %}
1. Review the "Active jobs" section, which contains a list of all jobs currently running on {% data variables.product.prodname_dotcom %}-hosted runners.
@@ -25,6 +25,6 @@ You can get a list of all jobs currently running on {% data variables.product.pr
The following procedure demonstrates how to check the maximum number of concurrent jobs you can run.
-{% data reusables.github-actions.github-hosted-runners-navigate-to-repo-org-enterprise %}
-{% data reusables.github-actions.github-hosted-runners-table-entry %}
+{% data reusables.actions.github-hosted-runners-navigate-to-repo-org-enterprise %}
+{% data reusables.actions.github-hosted-runners-table-entry %}
1. Review the "All jobs usage" section, which lists the number of active jobs and the maximum number of jobs you can run. In this example, `9` jobs are currently running out of a maximum of `180`. 
diff --git a/translations/ja-JP/content/actions/using-jobs/using-concurrency.md b/translations/ja-JP/content/actions/using-jobs/using-concurrency.md
index 20b1284a9f33..a8280937f2e1 100644
--- a/translations/ja-JP/content/actions/using-jobs/using-concurrency.md
+++ b/translations/ja-JP/content/actions/using-jobs/using-concurrency.md
@@ -20,5 +20,5 @@ miniTocMaxHeadingLevel: 4
{% if github-runner-dashboard %}
## Monitoring your current jobs in your organization or enterprise
-{% data reusables.github-actions.github-hosted-runners-check-concurrency %}
+{% data reusables.actions.github-hosted-runners-check-concurrency %}
{% endif %}
diff --git a/translations/ja-JP/content/actions/using-workflows/events-that-trigger-workflows.md b/translations/ja-JP/content/actions/using-workflows/events-that-trigger-workflows.md
index d09b0f1a615d..3422e391f975 100644
--- a/translations/ja-JP/content/actions/using-workflows/events-that-trigger-workflows.md
+++ b/translations/ja-JP/content/actions/using-workflows/events-that-trigger-workflows.md
@@ -37,7 +37,7 @@ Some events have multiple activity types. For these events, you can specify whic
{% endnote %}
-{% data reusables.github-actions.branch-requirement %}
+{% data reusables.actions.branch-requirement %}
Runs your workflow when branch protection rules in the workflow repository are changed. For more information about branch protection rules, see "[About protected branches](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches)." For information about the branch protection rule APIs, see "[BranchProtectionRule](/graphql/reference/objects#branchprotectionrule)" in the GraphQL API documentation or "[Branches](/rest/reference/branches)" in the REST API documentation.
@@ -64,7 +64,7 @@ on:
{% endnote %}
-{% data reusables.github-actions.branch-requirement %}
+{% data reusables.actions.branch-requirement %}
Runs your workflow when activity related to a check run occurs. チェックの実行は、個別のテストであり、チェックスイートの一機能です。 For information, see "[Getting started with the Checks API](/rest/guides/getting-started-with-the-checks-api)." For information about the check run APIs, see "[CheckRun](/graphql/reference/objects#checkrun)" in the GraphQL API documentation or "[Checks](/rest/reference/checks#runs)" in the REST API documentation.
@@ -88,7 +88,7 @@ on:
{% endnote %}
-{% data reusables.github-actions.branch-requirement %}
+{% data reusables.actions.branch-requirement %}
{% note %}
@@ -133,7 +133,7 @@ on:
| ---------------------------------------------------------------------------------------- | ---------- | ----------------- | ------------ |
| [`delete`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads/#delete) | n/a | デフォルトブランチの直近のコミット | デフォルトブランチ |
-{% data reusables.github-actions.branch-requirement %}
+{% data reusables.actions.branch-requirement %}
{% note %}
@@ -199,7 +199,7 @@ on:
{% endnote %}
-{% data reusables.github-actions.branch-requirement %}
+{% data reusables.actions.branch-requirement %}
{% data reusables.webhooks.discussions-webhooks-beta %}
@@ -225,7 +225,7 @@ on:
{% endnote %}
-{% data reusables.github-actions.branch-requirement %}
+{% data reusables.actions.branch-requirement %}
{% data reusables.webhooks.discussions-webhooks-beta %}
@@ -247,7 +247,7 @@ on:
| ------------------------------------------------------------------------------------ | ---------- | ----------------- | ------------ |
| [`フォーク`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads/#fork) | n/a | デフォルトブランチの直近のコミット | デフォルトブランチ |
-{% data reusables.github-actions.branch-requirement %}
+{% data reusables.actions.branch-requirement %}
Runs your workflow when someone forks a repository. REST API の詳細については、「[フォークの作成](/rest/reference/repos#create-a-fork)」を参照してください。
@@ -264,7 +264,7 @@ on:
| ---------------------------------------------------------------------------------------- | ---------- | ----------------- | ------------ |
| [`gollum`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads/#gollum) | n/a | デフォルトブランチの直近のコミット | デフォルトブランチ |
-{% data reusables.github-actions.branch-requirement %}
+{% data reusables.actions.branch-requirement %}
Runs your workflow when someone creates or updates a Wiki page. 詳細は「[ウィキについて](/communities/documenting-your-project-with-wikis/about-wikis)」を参照してください。
@@ -287,7 +287,7 @@ on:
{% endnote %}
-{% data reusables.github-actions.branch-requirement %}
+{% data reusables.actions.branch-requirement %}
Runs your workflow when an issue or pull request comment is created, edited, or deleted. For information about the issue comment APIs, see "[IssueComment](/graphql/reference/objects#issuecomment)" in the GraphQL API documentation or "[Issue comments](/developers/webhooks-and-events/webhook-events-and-payloads#issue_comment)" in the REST API documentation.
@@ -344,7 +344,7 @@ jobs:
{% endnote %}
-{% data reusables.github-actions.branch-requirement %}
+{% data reusables.actions.branch-requirement %}
Runs your workflow when an issue in the workflow's repository is created or modified. For activity related to comments in an issue, use the [`issue_comment`](#issue_comment) event. Issue に関する詳しい情報については「[Issue について](/issues/tracking-your-work-with-issues/about-issues)」を参照してください。 For information about the issue APIs, see "[Issue](/graphql/reference/objects#issue)" in the GraphQL API documentation or "[Issues](/rest/reference/issues)" in the REST API documentation.
@@ -368,7 +368,7 @@ on:
{% endnote %}
-{% data reusables.github-actions.branch-requirement %}
+{% data reusables.actions.branch-requirement %}
Runs your workflow when a label in your workflow's repository is created or modified. For more information about labels, see "[Managing labels](/issues/using-labels-and-milestones-to-track-work/managing-labels)." For information about the label APIs, see "[Label](/graphql/reference/objects#label)" in the GraphQL API documentation or "[Labels](/rest/reference/issues#labels)" in the REST API documentation.
@@ -394,7 +394,7 @@ on:
{% endnote %}
-{% data reusables.github-actions.branch-requirement %}
+{% data reusables.actions.branch-requirement %}
Runs your workflow when a milestone in the workflow's repository is created or modified. For more information about milestones, see "[About milestones](/issues/using-labels-and-milestones-to-track-work/about-milestones)." For information about the milestone APIs, see "[Milestone](/graphql/reference/objects#milestone)" in the GraphQL API documentation or "[Milestones](/rest/reference/issues#milestones)" in the REST API documentation.
@@ -414,7 +414,7 @@ on:
| ------------------------------------------------------------------------------------------------ | ---------- | ----------------- | ------------ |
| [`page_build`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads/#page_build) | n/a | デフォルトブランチの直近のコミット | n/a |
-{% data reusables.github-actions.branch-requirement %}
+{% data reusables.actions.branch-requirement %}
Runs your workflow when someone pushes to a branch that is the publishing source for {% data variables.product.prodname_pages %}, if {% data variables.product.prodname_pages %} is enabled for the repository. For more information about {% data variables.product.prodname_pages %} publishing sources, see "[Configuring a publishing source for your GitHub Pages site](/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site#choosing-a-publishing-source)." REST API の詳細については、「[ページ](/rest/reference/repos#pages)」を参照してください。
@@ -437,7 +437,7 @@ on:
{% endnote %}
-{% data reusables.github-actions.branch-requirement %}
+{% data reusables.actions.branch-requirement %}
{% note %}
@@ -475,7 +475,7 @@ on:
{% endnote %}
-{% data reusables.github-actions.branch-requirement %}
+{% data reusables.actions.branch-requirement %}
{% note %}
@@ -513,7 +513,7 @@ on:
{% endnote %}
-{% data reusables.github-actions.branch-requirement %}
+{% data reusables.actions.branch-requirement %}
{% note %}
@@ -545,7 +545,7 @@ on:
| ---------------------------------------------------------------------------------------- | ---------- | ----------------- | ------------ |
| [`public`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads/#public) | n/a | デフォルトブランチの直近のコミット | デフォルトブランチ |
-{% data reusables.github-actions.branch-requirement %}
+{% data reusables.actions.branch-requirement %}
Runs your workflow when your workflow's repository changes from private to public. REST API の詳細については、「[リポジトリの編集](/rest/reference/repos#edit)」を参照してください。
@@ -625,7 +625,7 @@ on:
{% note %}
-**Note:** {% data reusables.github-actions.branch-paths-filter %} For example, the following workflow will only run when a pull request that includes a change to a JavaScript (`.js`) file is opened on a branch whose name starts with `releases/`:
+**Note:** {% data reusables.actions.branch-paths-filter %} For example, the following workflow will only run when a pull request that includes a change to a JavaScript (`.js`) file is opened on a branch whose name starts with `releases/`:
```yaml
on:
@@ -670,7 +670,7 @@ on:
{% note %}
-**Note:** {% data reusables.github-actions.branch-paths-filter %} For example, the following workflow will only run when a pull request that includes a change to a JavaScript (`.js`) file is opened on a branch whose name starts with `releases/`:
+**Note:** {% data reusables.actions.branch-paths-filter %} For example, the following workflow will only run when a pull request that includes a change to a JavaScript (`.js`) file is opened on a branch whose name starts with `releases/`:
```yaml
on:
@@ -828,7 +828,7 @@ on:
{% note %}
-**Note:** {% data reusables.github-actions.branch-paths-filter %} For example, the following workflow will only run when a pull request that includes a change to a JavaScript (`.js`) file is opened on a branch whose name starts with `releases/`:
+**Note:** {% data reusables.actions.branch-paths-filter %} For example, the following workflow will only run when a pull request that includes a change to a JavaScript (`.js`) file is opened on a branch whose name starts with `releases/`:
```yaml
on:
@@ -873,7 +873,7 @@ on:
{% note %}
-**Note:** {% data reusables.github-actions.branch-paths-filter %} For example, the following workflow will only run when a pull request that includes a change to a JavaScript (`.js`) file is opened on a branch whose name starts with `releases/`:
+**Note:** {% data reusables.actions.branch-paths-filter %} For example, the following workflow will only run when a pull request that includes a change to a JavaScript (`.js`) file is opened on a branch whose name starts with `releases/`:
```yaml
on:
@@ -950,7 +950,7 @@ on:
{% note %}
-**Note:** {% data reusables.github-actions.branch-paths-filter %} For example, the following workflow will only run when a push that includes a change to a JavaScript (`.js`) file is made to a branch whose name starts with `releases/`:
+**Note:** {% data reusables.actions.branch-paths-filter %} For example, the following workflow will only run when a push that includes a change to a JavaScript (`.js`) file is made to a branch whose name starts with `releases/`:
```yaml
on:
@@ -991,7 +991,7 @@ on:
{% note %}
-**Note:** {% data reusables.github-actions.branch-paths-filter %} For example, the following workflow will only run when a push that includes a change to a JavaScript (`.js`) file is made to a branch whose name starts with `releases/`:
+**Note:** {% data reusables.actions.branch-paths-filter %} For example, the following workflow will only run when a push that includes a change to a JavaScript (`.js`) file is made to a branch whose name starts with `releases/`:
```yaml
on:
@@ -1016,7 +1016,7 @@ on:
{% endnote %}
-{% data reusables.github-actions.branch-requirement %}
+{% data reusables.actions.branch-requirement %}
Runs your workflow when activity related to {% data variables.product.prodname_registry %} occurs in your repository. 詳しい情報については、「[{% data variables.product.prodname_registry %} のドキュメント](/packages)」を参照してください。
@@ -1068,7 +1068,7 @@ on:
| ---------------------------------------------------------------------------------------------------------------- | ---------- | ----------------- | ------------ |
| [repository_dispatch](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads/#repository_dispatch) | カスタム | デフォルトブランチの直近のコミット | デフォルトブランチ |
-{% data reusables.github-actions.branch-requirement %}
+{% data reusables.actions.branch-requirement %}
{% data variables.product.product_name %} の外部で生じるアクティビティのためにワークフローをトリガーしたい場合、{% data variables.product.product_name %} API を使って、[`repository_dispatch`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads/#repository_dispatch) と呼ばれる webhook イベントをトリガーできます。 詳細については、「[リポジトリディスパッチ イベントの作成](/rest/reference/repos#create-a-repository-dispatch-event)」を参照してください。
@@ -1160,7 +1160,7 @@ jobs:
| --------------------------------------------------------------------------------------- | ---------- | ----------------- | ------------ |
| [`ステータス`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads/#status) | n/a | デフォルトブランチの直近のコミット | n/a |
-{% data reusables.github-actions.branch-requirement %}
+{% data reusables.actions.branch-requirement %}
Runs your workflow when the status of a Git commit changes. For example, commits can be marked as `error`, `failure`, `pending`, or `success`. If you want to provide more details about the status change, you may want to use the [`check_run`](#check_run) event. For information about the commit status APIs, see "[Status](/graphql/reference/objects#statue)" in the GraphQL API documentation or "[Statuses](/rest/reference/commits#commit-statuses)" in the REST API documentation.
@@ -1201,7 +1201,7 @@ jobs:
{% endnote %}
-{% data reusables.github-actions.branch-requirement %}
+{% data reusables.actions.branch-requirement %}
Runs your workflow when the workflow's repository is starred. For information about the pull request APIs, see "[addStar](/graphql/reference/mutations#addstar)" in the GraphQL API documentation or "[Starring](/rest/reference/activity#starring)" in the REST API documentation.
@@ -1343,7 +1343,7 @@ jobs:
{% endnote %}
-{% data reusables.github-actions.branch-requirement %}
+{% data reusables.actions.branch-requirement %}
{% note %}
diff --git a/translations/ja-JP/content/actions/using-workflows/sharing-workflows-secrets-and-runners-with-your-organization.md b/translations/ja-JP/content/actions/using-workflows/sharing-workflows-secrets-and-runners-with-your-organization.md
index 9987878f91d6..2d3a051f08f4 100644
--- a/translations/ja-JP/content/actions/using-workflows/sharing-workflows-secrets-and-runners-with-your-organization.md
+++ b/translations/ja-JP/content/actions/using-workflows/sharing-workflows-secrets-and-runners-with-your-organization.md
@@ -50,11 +50,11 @@ Organization 内でシークレットを一元管理し、選択したリポジ
Organizationでシークレットを作成する場合、ポリシーを使用して、そのシークレットにアクセスできるリポジトリを制限できます。 たとえば、すべてのリポジトリにアクセスを許可したり、プライベート リポジトリまたは指定したリポジトリ のリストのみにアクセスを制限したりできます。
-{% data reusables.github-actions.permissions-statement-secrets-organization %}
+{% data reusables.actions.permissions-statement-secrets-organization %}
{% data reusables.organizations.navigate-to-org %}
{% data reusables.organizations.org_settings %}
-{% data reusables.github-actions.sidebar-secret %}
+{% data reusables.actions.sidebar-secret %}
1. [**New secret（新しいシークレット）**] をクリックします。
1. **[Name（名前）]** 入力ボックスにシークレットの名前を入力します。
1. シークレットの **Value（値）** を入力します。
diff --git a/translations/ja-JP/content/actions/using-workflows/storing-workflow-data-as-artifacts.md b/translations/ja-JP/content/actions/using-workflows/storing-workflow-data-as-artifacts.md
index d550fa861d52..e05fdb34574a 100644
--- a/translations/ja-JP/content/actions/using-workflows/storing-workflow-data-as-artifacts.md
+++ b/translations/ja-JP/content/actions/using-workflows/storing-workflow-data-as-artifacts.md
@@ -26,7 +26,7 @@ topics:
Artifacts allow you to persist data after a job has completed, and share that data with another job in the same workflow. An artifact is a file or collection of files produced during a workflow run. For example, you can use artifacts to save your build and test output after a workflow run has ended. {% data reusables.actions.reusable-workflow-artifacts %}
-{% data reusables.github-actions.artifact-log-retention-statement %} The retention period for a pull request restarts each time someone pushes a new commit to the pull request.
+{% data reusables.actions.artifact-log-retention-statement %} The retention period for a pull request restarts each time someone pushes a new commit to the pull request.
These are some of the common artifacts that you can upload:
@@ -37,7 +37,7 @@ These are some of the common artifacts that you can upload:
{% ifversion fpt or ghec %}
-Storing artifacts uses storage space on {% data variables.product.product_name %}. {% data reusables.github-actions.actions-billing %} For more information, see "[Managing billing for {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions)."
+Storing artifacts uses storage space on {% data variables.product.product_name %}. {% data reusables.actions.actions-billing %} For more information, see "[Managing billing for {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions)."
{% else %}
diff --git a/translations/ja-JP/content/actions/using-workflows/triggering-a-workflow.md b/translations/ja-JP/content/actions/using-workflows/triggering-a-workflow.md
index 67b7214800df..98ea9d8202ee 100644
--- a/translations/ja-JP/content/actions/using-workflows/triggering-a-workflow.md
+++ b/translations/ja-JP/content/actions/using-workflows/triggering-a-workflow.md
@@ -41,7 +41,7 @@ Workflow triggers are defined with the `on` key. 詳しい情報については
### Triggering a workflow from a workflow
-{% data reusables.github-actions.actions-do-not-trigger-workflows %} 詳しい情報については「[GITHUB_TOKENでの認証](/actions/configuring-and-managing-workflows/authenticating-with-the-github_token)」を参照してください。
+{% data reusables.actions.actions-do-not-trigger-workflows %} For more information, see "[Authenticating with the GITHUB_TOKEN](/actions/configuring-and-managing-workflows/authenticating-with-the-github_token)."
If you do want to trigger a workflow from within a workflow run, you can use a personal access token instead of `GITHUB_TOKEN` to trigger events that require a token. 個人アクセストークンを作成し、それをシークレットとして保存する必要があります。 {% data variables.product.prodname_actions %}の利用コストを最小化するために、再帰的あるいは意図しないワークフローの実行が生じないようにしてください。 個人アクセストークンの作成に関する詳しい情報については「[個人アクセストークンの作成](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)」を参照してください。 For more information about storing a personal access token as a secret, see "[Creating and storing encrypted secrets](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets)."
@@ -89,23 +89,23 @@ Use the `on` key to specify what events trigger your workflow. For more informat
### Using a single event
-{% data reusables.github-actions.on-single-example %}
+{% data reusables.actions.on-single-example %}
### Using multiple events
-{% data reusables.github-actions.on-multiple-example %}
+{% data reusables.actions.on-multiple-example %}
### Using activity types and filters with multiple events
-You can use activity types and filters to further control when your workflow will run. For more information, see [Using event activity types](#using-event-activity-types) and [Using filters](#using-filters). {% data reusables.github-actions.actions-multiple-types %}
+You can use activity types and filters to further control when your workflow will run. For more information, see [Using event activity types](#using-event-activity-types) and [Using filters](#using-filters). {% data reusables.actions.actions-multiple-types %}
## Using event activity types
-{% data reusables.github-actions.actions-activity-types %}
+{% data reusables.actions.actions-activity-types %}
## Using filters
-{% data reusables.github-actions.actions-filters %}
+{% data reusables.actions.actions-filters %}
### Using filters to target specific branches for pull request events
@@ -125,7 +125,7 @@ You can use activity types and filters to further control when your workflow wil
## Defining inputs for manually triggered workflows
-{% data reusables.github-actions.workflow-dispatch-inputs %}
+{% data reusables.actions.workflow-dispatch-inputs %}
{% ifversion fpt or ghes > 3.3 or ghae-issue-4757 or ghec %}
## Defining inputs, outputs, and secrets for reusable workflows
diff --git a/translations/ja-JP/content/actions/using-workflows/workflow-syntax-for-github-actions.md b/translations/ja-JP/content/actions/using-workflows/workflow-syntax-for-github-actions.md
index e91ce5aabf2d..b7c0e8ab9bdd 100644
--- a/translations/ja-JP/content/actions/using-workflows/workflow-syntax-for-github-actions.md
+++ b/translations/ja-JP/content/actions/using-workflows/workflow-syntax-for-github-actions.md
@@ -173,7 +173,7 @@ A boolean specifying whether the secret must be supplied.
## `on.workflow_dispatch.inputs`
-{% data reusables.github-actions.workflow-dispatch-inputs %}
+{% data reusables.actions.workflow-dispatch-inputs %}
{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
## `permissions`
@@ -184,7 +184,7 @@ A boolean specifying whether the secret must be supplied.
## `env`
-A `map` of environment variables that are available to the steps of all jobs in the workflow. You can also set environment variables that are only available to the steps of a single job or to a single step. For more information, see [`jobs..env`](#jobsjob_idenv) and [`jobs..steps[*].env`](#jobsjob_idstepsenv).
+ワークフロー中のすべてのジョブのステップから利用できる環境変数の`map`です。 1つのジョブのステップ、あるいは1つのステップからだけ利用できる環境変数を設定することもできます。 詳しい情報については「[`jobs..env`](#jobsjob_idenv)」及び「[`jobs..steps[*].env`](#jobsjob_idstepsenv)を参照してください。
{% data reusables.repositories.actions-env-var-note %}
@@ -259,7 +259,7 @@ env:
## `jobs..env`
-A `map` of environment variables that are available to all steps in the job. You can also set environment variables for the entire workflow or an individual step. For more information, see [`env`](#env) and [`jobs..steps[*].env`](#jobsjob_idstepsenv).
+ジョブ中のすべてのステップから利用できる環境変数の`map`です。 ワークフロー全体あるいは個別のステップのための環境変数を設定することもできます。 詳しい情報については[`env`](#env)及び[`jobs..steps[*].env`](#jobsjob_idstepsenv)を参照してください。
{% data reusables.repositories.actions-env-var-note %}
@@ -282,9 +282,9 @@ jobs:
## `jobs..steps`
-A job contains a sequence of tasks called `steps`. Steps can run commands, run setup tasks, or run an action in your repository, a public repository, or an action published in a Docker registry. Not all steps run actions, but all actions run as a step. Each step runs in its own process in the runner environment and has access to the workspace and filesystem. Because steps run in their own process, changes to environment variables are not preserved between steps. {% data variables.product.prodname_dotcom %} provides built-in steps to set up and complete a job.
+1つのジョブには、`steps` (ステップ) と呼ばれる一連のタスクがあります。 ステップでは、コマンドを実行する、設定タスクを実行する、あるいはリポジトリやパブリックリポジトリ、Dockerレジストリで公開されたアクションを実行することができます。 すべてのステップでアクションを実行するとは限りませんが、すべてのアクションはステップとして実行されます。 各ステップは、ランナー環境のそれ自体のプロセスで実行され、ワークスペースとファイルシステムにアクセスします。 ステップはそれ自体のプロセスで実行されるため、環境変数を変更しても、ステップ間では反映されません。 {% data variables.product.prodname_dotcom %}には、ジョブを設定して完了するステップが組み込まれています。
-You can run an unlimited number of steps as long as you are within the workflow usage limits. For more information, see {% ifversion fpt or ghec or ghes %}"[Usage limits and billing](/actions/reference/usage-limits-billing-and-administration)" for {% data variables.product.prodname_dotcom %}-hosted runners and {% endif %}"[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners/#usage-limits){% ifversion fpt or ghec or ghes %}" for self-hosted runner usage limits.{% elsif ghae %}."{% endif %}
+ワークフローの利用限度内であれば、実行するステップ数に限度はありません。 For more information, see {% ifversion fpt or ghec or ghes %}"[Usage limits and billing](/actions/reference/usage-limits-billing-and-administration)" for {% data variables.product.prodname_dotcom %}-hosted runners and {% endif %}"[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners/#usage-limits){% ifversion fpt or ghec or ghes %}" for self-hosted runner usage limits.{% elsif ghae %}."{% endif %}
### サンプル
@@ -312,13 +312,13 @@ jobs:
### `jobs..steps[*].id`
-A unique identifier for the step. `id`を使って、コンテキストのステップを参照することができます。 詳細については、「[コンテキスト](/actions/learn-github-actions/contexts)」を参照してください。
+ステップの一意の識別子。 `id`を使って、コンテキストのステップを参照することができます。 詳細については、「[コンテキスト](/actions/learn-github-actions/contexts)」を参照してください。
### `jobs..steps[*].if`
-You can use the `if` conditional to prevent a step from running unless a condition is met. 条件文を作成するには、サポートされている任意のコンテキストや式が使えます。
+条件文の`if`を使って、条件が満たされなければステップを実行しないようにできます。 条件文を作成するには、サポートされている任意のコンテキストや式が使えます。
-{% data reusables.github-actions.expression-syntax-if %} For more information, see "[Expressions](/actions/learn-github-actions/expressions)."
+{% data reusables.actions.expression-syntax-if %} For more information, see "[Expressions](/actions/learn-github-actions/expressions)."
#### Example: Using contexts
@@ -333,7 +333,7 @@ steps:
#### Example: Using status check functions
-The `my backup step` only runs when the previous step of a job fails. For more information, see "[Expressions](/actions/learn-github-actions/expressions#job-status-check-functions)."
+`my backup step`は、ジョブの前のステップが失敗した場合にのみ実行されます。 For more information, see "[Expressions](/actions/learn-github-actions/expressions#job-status-check-functions)."
```yaml
steps:
@@ -346,20 +346,20 @@ steps:
### `jobs..steps[*].name`
-A name for your step to display on {% data variables.product.prodname_dotcom %}.
+{% data variables.product.prodname_dotcom %}で表示されるステップの名前。
### `jobs..steps[*].uses`
-Selects an action to run as part of a step in your job. アクションとは、再利用可能なコードの単位です。 ワークフロー、パブリックリポジトリ、または[公開されているDockerコンテナイメージ](https://hub.docker.com/)と同じリポジトリで定義されているアクションを使用できます。
+ジョブでステップの一部として実行されるアクションを選択します。 アクションとは、再利用可能なコードの単位です。 ワークフロー、パブリックリポジトリ、または[公開されているDockerコンテナイメージ](https://hub.docker.com/)と同じリポジトリで定義されているアクションを使用できます。
Git ref、SHA、またはDockerタグ番号を指定して、使用しているアクションのバージョンを含めることを強く推奨します。 バージョンを指定しないと、アクションのオーナーがアップデートを公開したときに、ワークフローが中断したり、予期せぬ動作をしたりすることがあります。
- リリースされたアクションバージョンのコミットSHAを使用するのが、安定性とセキュリティのうえで最も安全です。
- 特定のメジャーアクションバージョンを使用すると、互換性を維持したまま重要な修正とセキュリティパッチを受け取ることができます。 ワークフローが引き続き動作することも保証できます。
- アクションのデフォルトブランチを使用すると便利なこともありますが、別のユーザが破壊的変更を加えた新しいメジャーバージョンをリリースすると、ワークフローが動作しなくなる場合があります。
-Some actions require inputs that you must set using the [`with`](#jobsjob_idstepswith) keyword. 必要な入力を判断するには、アクションのREADMEファイルをお読みください。
+入力が必要なアクションもあり、入力を[`with`](#jobsjob_idstepswith)キーワードを使って設定する必要があります。 必要な入力を判断するには、アクションのREADMEファイルをお読みください。
-Actions are either JavaScript files or Docker containers. If the action you're using is a Docker container you must run the job in a Linux environment. For more details, see [`runs-on`](#jobsjob_idruns-on).
+アクションは、JavaScriptのファイルもしくはDockerコンテナです。 使用するアクションがDockerコンテナの場合、ジョブはLinux環境で実行する必要があります。 詳細については[`runs-on`](#jobsjob_idruns-on)を参照してください。
#### Example: Using versioned actions
@@ -397,7 +397,7 @@ jobs:
`{owner}/{repo}/{path}@{ref}`
-A subdirectory in a public {% data variables.product.prodname_dotcom %} repository at a specific branch, ref, or SHA.
+パブリック{% data variables.product.prodname_dotcom %}リポジトリで特定のブランチ、ref、SHAにあるサブディレクトリ。
```yaml
jobs:
@@ -411,7 +411,7 @@ jobs:
`./path/to/dir`
-The path to the directory that contains the action in your workflow's repository. You must check out your repository before using the action.
+ワークフローのリポジトリにあるアクションを含むディレクトリのパス。 アクションを使用する前にリポジトリをチェックアウトする必要があります。
```yaml
jobs:
@@ -427,7 +427,7 @@ jobs:
`docker://{image}:{tag}`
-A Docker image published on [Docker Hub](https://hub.docker.com/).
+[Docker Hub](https://hub.docker.com/)で公開されているDockerイメージ。
```yaml
jobs:
@@ -442,7 +442,7 @@ jobs:
`docker://{host}/{image}:{tag}`
-A Docker image in the {% data variables.product.prodname_registry %} {% data variables.product.prodname_container_registry %}.
+{% data variables.product.prodname_registry %} {% data variables.product.prodname_container_registry %} の Docker イメージ
```yaml
jobs:
@@ -456,7 +456,7 @@ jobs:
`docker://{host}/{image}:{tag}`
-A Docker image in a public registry. This example uses the Google Container Registry at `gcr.io`.
+パブリックレジストリのDockerイメージ。 この例では、`gcr.io` にある Google Container Registry を使用しています。
```yaml
jobs:
@@ -468,9 +468,9 @@ jobs:
#### Example: Using an action inside a different private repository than the workflow
-Your workflow must checkout the private repository and reference the action locally. Generate a personal access token and add the token as an encrypted secret. 詳しい情報については、「[個人アクセストークンを作成する](/github/authenticating-to-github/creating-a-personal-access-token)」および「[暗号化されたシークレット](/actions/reference/encrypted-secrets)」を参照してください。
+ワークフローはプライベートリポジトリをチェックアウトし、アクションをローカルで参照する必要があります。 個人アクセストークンを生成し、暗号化されたシークレットとしてトークンを追加します。 詳しい情報については、「[個人アクセストークンを作成する](/github/authenticating-to-github/creating-a-personal-access-token)」および「[暗号化されたシークレット](/actions/reference/encrypted-secrets)」を参照してください。
-Replace `PERSONAL_ACCESS_TOKEN` in the example with the name of your secret.
+例にある `PERSONAL_ACCESS_TOKEN` をシークレットの名前に置き換えます。
{% raw %}
```yaml
@@ -491,11 +491,11 @@ jobs:
### `jobs..steps[*].run`
-Runs command-line programs using the operating system's shell. If you do not provide a `name`, the step name will default to the text specified in the `run` command.
+オペレーティングシステムのシェルを使用してコマンドラインプログラムを実行します。 `name`を指定しない場合、ステップ名はデフォルトで`run`コマンドで指定された文字列になります。
-Commands run using non-login shells by default. You can choose a different shell and customize the shell used to run commands. For more information, see [`jobs..steps[*].shell`](#jobsjob_idstepsshell).
+コマンドは、デフォルトでは非ログインシェルを使用して実行されます。 別のシェルを選択して、コマンドを実行するシェルをカスタマイズできます。 For more information, see [`jobs..steps[*].shell`](#jobsjob_idstepsshell).
-Each `run` keyword represents a new process and shell in the runner environment. When you provide multi-line commands, each line runs in the same shell. 例:
+`run`キーワードは、それぞれがランナー環境での新しいプロセスとシェルです。 複数行のコマンドを指定すると、各行が同じシェルで実行されます。 例:
* 1行のコマンド：
@@ -513,7 +513,7 @@ Each `run` keyword represents a new process and shell in the runner environment.
npm run build
```
-Using the `working-directory` keyword, you can specify the working directory of where to run the command.
+`working-directory`キーワードを使えば、コマンドが実行されるワーキングディレクトリを指定できます。
```yaml
- name: Clean temp directory
@@ -523,7 +523,7 @@ Using the `working-directory` keyword, you can specify the working directory of
### `jobs..steps[*].shell`
-You can override the default shell settings in the runner's operating system using the `shell` keyword. You can use built-in `shell` keywords, or you can define a custom set of shell options. The shell command that is run internally executes a temporary file that contains the commands specified in the `run` keyword.
+`shell`キーワードを使用して、ランナーのオペレーティングシステムのデフォルトシェルの設定を上書きできます。 組み込みの`shell`キーワードを使用するか、カスタムセットのシェルオプションを定義することができます。 The shell command that is run internally executes a temporary file that contains the commands specified in the `run` keyword.
| サポートされているプラットフォーム | `shell` パラメータ | 説明 | 内部で実行されるコマンド |
| ----------------- | ------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------- |
@@ -584,7 +584,7 @@ steps:
#### カスタムシェル
-You can set the `shell` value to a template string using `command […options] {0} [..more_options]`. {% data variables.product.prodname_dotcom %} interprets the first whitespace-delimited word of the string as the command, and inserts the file name for the temporary script at `{0}`.
+`command […options] {0} [..more_options]`を使用すると、テンプレート文字列に`shell`値を設定できます。 {% data variables.product.prodname_dotcom %}は、空白区切りで最初の文字列をコマンドとして解釈し、`{0}`にある一時的なスクリプトのファイル名を挿入します。
例:
@@ -596,17 +596,17 @@ steps:
shell: perl {0}
```
-The command used, `perl` in this example, must be installed on the runner.
+使われるコマンドは（この例では`perl`）は、ランナーにインストールされていなければなりません。
{% ifversion ghae %}
{% data reusables.actions.self-hosted-runners-software %}
{% elsif fpt or ghec %}
-For information about the software included on GitHub-hosted runners, see "[Specifications for GitHub-hosted runners](/actions/reference/specifications-for-github-hosted-runners#supported-software)."
+GitHubホストランナーに含まれるソフトウェアに関する情報については「[GitHubホストランナーの仕様](/actions/reference/specifications-for-github-hosted-runners#supported-software)」を参照してください。
{% endif %}
#### 終了コードとエラーアクションの環境設定
-For built-in shell keywords, we provide the following defaults that are executed by {% data variables.product.prodname_dotcom %}-hosted runners. You should use these guidelines when running shell scripts.
+組み込みのshellキーワードについては、{% data variables.product.prodname_dotcom %}がホストする実行環境で以下のデフォルトが提供されます。 シェルスクリプトを実行する際には、以下のガイドラインを使ってください。
- `bash`/`sh`:
- `set -eo pipefail`を使用したフェイルファースト動作 : `bash`及び組み込みの`shell`のデフォルト。 Windows以外のプラットフォームでオプションを指定しない場合のデフォルトでもあります。
@@ -624,11 +624,11 @@ For built-in shell keywords, we provide the following defaults that are executed
### `jobs..steps[*].with`
-A `map` of the input parameters defined by the action. 各入力パラメータはキー/値ペアです。 入力パラメータは環境変数として設定されます。 The variable is prefixed with `INPUT_` and converted to upper case.
+アクションによって定義される入力パラメータの`map`。 各入力パラメータはキー/値ペアです。 入力パラメータは環境変数として設定されます。 変数の前には`INPUT_`が付けられ、大文字に変換されます。
#### サンプル
-Defines the three input parameters (`first_name`, `middle_name`, and `last_name`) defined by the `hello_world` action. These input variables will be accessible to the `hello-world` action as `INPUT_FIRST_NAME`, `INPUT_MIDDLE_NAME`, and `INPUT_LAST_NAME` environment variables.
+`hello_world`アクションで定義される3つの入力パラメータ (`first_name`、`middle_name`、`last_name`) を定義します。 `hello-world`アクションからは、これらの入力変数は`INPUT_FIRST_NAME`、`INPUT_MIDDLE_NAME`、`INPUT_LAST_NAME`という環境変数としてアクセスできます。
```yaml
jobs:
@@ -644,7 +644,7 @@ jobs:
### `jobs..steps[*].with.args`
-A `string` that defines the inputs for a Docker container. {% data variables.product.prodname_dotcom %}は、コンテナの起動時に`args`をコンテナの`ENTRYPOINT`に渡します。 An `array of strings` is not supported by this parameter.
+Dockerコンテナへの入力を定義する`文字列`。 {% data variables.product.prodname_dotcom %}は、コンテナの起動時に`args`をコンテナの`ENTRYPOINT`に渡します。 このパラメータは、`文字列の配列`をサポートしません。
#### サンプル
@@ -667,7 +667,7 @@ steps:
### `jobs..steps[*].with.entrypoint`
-Overrides the Docker `ENTRYPOINT` in the `Dockerfile`, or sets it if one wasn't already specified. Unlike the Docker `ENTRYPOINT` instruction which has a shell and exec form, `entrypoint` keyword accepts only a single string defining the executable to be run.
+`Dockerfile`中のDockerの`ENTRYPOINT`をオーバーライドします。あるいは、もしそれが指定されていなかった場合に設定します。 shellやexec形式を持つDockerの`ENTRYPOINT`命令とは異なり、`entrypoint`キーワードは実行する実行可能ファイルを定義する単一の文字列だけを受け付けます。
#### サンプル
@@ -679,15 +679,15 @@ steps:
entrypoint: /a/different/executable
```
-The `entrypoint` keyword is meant to be used with Docker container actions, but you can also use it with JavaScript actions that don't define any inputs.
+`entrypoint`キーワードはDockerコンテナアクションで使われることを意図したものですが、入力を定義しないJavaScriptのアクションでも使うことができます。
### `jobs..steps[*].env`
-Sets environment variables for steps to use in the runner environment. You can also set environment variables for the entire workflow or a job. For more information, see [`env`](#env) and [`jobs..env`](#jobsjob_idenv).
+ランナー環境でステップが使う環境変数を設定します。 ワークフロー全体あるいはジョブのための環境変数を設定することもできます。 詳しい情報については「[`env`](#env)」及び「[`jobs..env`](#jobsjob_idenv)」を参照してください。
{% data reusables.repositories.actions-env-var-note %}
-Public actions may specify expected environment variables in the README file. If you are setting a secret in an environment variable, you must set secrets using the `secrets` context. For more information, see "[Using environment variables](/actions/automating-your-workflow-with-github-actions/using-environment-variables)" and "[Contexts](/actions/learn-github-actions/contexts)."
+パブリックなアクションは、READMEファイル中で期待する環境変数を指定できます。 環境変数にシークレットを設定しようとしている場合、シークレットは`secrets`コンテキストを使って設定しなければなりません。 For more information, see "[Using environment variables](/actions/automating-your-workflow-with-github-actions/using-environment-variables)" and "[Contexts](/actions/learn-github-actions/contexts)."
#### サンプル
@@ -704,15 +704,15 @@ steps:
### `jobs..steps[*].continue-on-error`
-Prevents a job from failing when a step fails. Set to `true` to allow a job to pass when this step fails.
+ステップが失敗してもジョブが失敗にならないようにします。 `true`に設定すれば、このステップが失敗した場合にジョブが次へ進めるようになります。
### `jobs..steps[*].timeout-minutes`
-The maximum number of minutes to run the step before killing the process.
+プロセスがkillされるまでにステップが実行できる最大の分数。
## `jobs..timeout-minutes`
-The maximum number of minutes to let a job run before {% data variables.product.prodname_dotcom %} automatically cancels it. Default: 360
+{% data variables.product.prodname_dotcom %}で自動的にキャンセルされるまでジョブを実行する最長時間 (分)。 デフォルト: 360
If the timeout exceeds the job execution time limit for the runner, the job will be canceled when the execution time limit is met instead. For more information about job execution time limits, see {% ifversion fpt or ghec or ghes %}"[Usage limits and billing](/actions/reference/usage-limits-billing-and-administration#usage-limits)" for {% data variables.product.prodname_dotcom %}-hosted runners and {% endif %}"[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners/#usage-limits){% ifversion fpt or ghec or ghes %}" for self-hosted runner usage limits.{% elsif ghae %}."{% endif %}
@@ -734,11 +734,11 @@ If the timeout exceeds the job execution time limit for the runner, the job will
## `jobs..continue-on-error`
-Prevents a workflow run from failing when a job fails. Set to `true` to allow a workflow run to pass when this job fails.
+ジョブが失敗した時に、ワークフローの実行が失敗にならないようにします。 `true`に設定すれば、ジョブが失敗した時にワークフローの実行が次へ進めるようになります。
### Example: Preventing a specific failing matrix job from failing a workflow run
-You can allow specific jobs in a job matrix to fail without failing the workflow run. For example, if you wanted to only allow an experimental job with `node` set to `15` to fail without failing the workflow run.
+ジョブマトリックス中の特定のジョブが失敗しても、ワークフローの実行が失敗にならないようにすることができます。 For example, if you wanted to only allow an experimental job with `node` set to `15` to fail without failing the workflow run.
{% raw %}
```yaml
@@ -759,7 +759,7 @@ strategy:
## `jobs..container`
-{% data reusables.github-actions.docker-container-os-support %}
+{% data reusables.actions.docker-container-os-support %}
{% data reusables.actions.jobs.section-running-jobs-in-a-container %}
@@ -789,19 +789,19 @@ strategy:
## `jobs..services`
-{% data reusables.github-actions.docker-container-os-support %}
+{% data reusables.actions.docker-container-os-support %}
-Used to host service containers for a job in a workflow. Service containers are useful for creating databases or cache services like Redis. The runner automatically creates a Docker network and manages the life cycle of the service containers.
+ワークフロー中のジョブのためのサービスコンテナをホストするために使われます。 サービスコンテナは、データベースやRedisのようなキャッシュサービスの作成に役立ちます。 ランナーは自動的にDockerネットワークを作成し、サービスコンテナのライフサイクルを管理します。
-If you configure your job to run in a container, or your step uses container actions, you don't need to map ports to access the service or action. Docker automatically exposes all ports between containers on the same Docker user-defined bridge network. You can directly reference the service container by its hostname. The hostname is automatically mapped to the label name you configure for the service in the workflow.
+コンテナを実行するようにジョブを設定した場合、あるいはステップがコンテナアクションを使う場合は、サービスもしくはアクションにアクセスするためにポートをマップする必要はありません。 Dockerは自動的に、同じDockerのユーザ定義ブリッジネットワーク上のコンテナ間のすべてのポートを公開します。 サービスコンテナは、ホスト名で直接参照できます。 ホスト名は自動的に、ワークフロー中のサービスに設定したラベル名にマップされます。
-If you configure the job to run directly on the runner machine and your step doesn't use a container action, you must map any required Docker service container ports to the Docker host (the runner machine). You can access the service container using localhost and the mapped port.
+ランナーマシン上で直接実行されるようにジョブを設定し、ステップがコンテナアクションを使わないのであれば、必要なDockerサービスコンテナのポートはDockerホスト（ランナーマシン）にマップしなければなりません サービスコンテナには、localhostとマップされたポートを使ってアクセスできます。
-For more information about the differences between networking service containers, see "[About service containers](/actions/automating-your-workflow-with-github-actions/about-service-containers)."
+ネットワーキングサービスコンテナ間の差異に関する詳しい情報については「[サービスコンテナについて](/actions/automating-your-workflow-with-github-actions/about-service-containers)」を参照してください。
### Example: Using localhost
-This example creates two services: nginx and redis. Dockerホストのポートを指定して、コンテナのポートを指定しなかった場合、コンテナのポートは空いているポートにランダムに割り当てられます。 {% data variables.product.prodname_dotcom %} sets the assigned container port in the {% raw %}`${{job.services..ports}}`{% endraw %} context. In this example, you can access the service container ports using the {% raw %}`${{ job.services.nginx.ports['8080'] }}`{% endraw %} and {% raw %}`${{ job.services.redis.ports['6379'] }}`{% endraw %} contexts.
+この例では、nginxとredisという2つのサービスを作成します。 Dockerホストのポートを指定して、コンテナのポートを指定しなかった場合、コンテナのポートは空いているポートにランダムに割り当てられます。 {% data variables.product.prodname_dotcom %}は、割り当てられたコンテナポートを{% raw %}`${{job.services..ports}}`{% endraw %}コンテキストに設定します。 以下の例では、サービスコンテナのポートへは{% raw %}`${{ job.services.nginx.ports['8080'] }}`{% endraw %} 及び{% raw %}`${{ job.services.redis.ports['6379'] }}`{% endraw %} コンテキストでアクセスできます。
```yaml
services:
@@ -819,7 +819,7 @@ services:
### `jobs..services..image`
-The Docker image to use as the service container to run the action. The value can be the Docker Hub image name or a registry name.
+アクションを実行するサービスコンテナとして使用するDockerイメージ。 The value can be the Docker Hub image name or a registry name.
### `jobs..services..credentials`
@@ -845,15 +845,15 @@ services:
### `jobs..services..env`
-Sets a `map` of environment variables in the service container.
+サービスコンテナ中の環境変数の`map`を設定します。
### `jobs..services..ports`
-Sets an `array` of ports to expose on the service container.
+サービスコンテナで公開するポートの`array`を設定します。
### `jobs..services..volumes`
-Sets an `array` of volumes for the service container to use. volumes (ボリューム) を使用すると、サービス間で、または1つのジョブのステップ間でデータを共有できます。 指定できるのは、名前付きDockerボリューム、匿名Dockerボリューム、またはホスト上のバインドマウントです。
+使用するサービスコンテナにボリュームの`array`を設定します。 volumes (ボリューム) を使用すると、サービス間で、または1つのジョブのステップ間でデータを共有できます。 指定できるのは、名前付きDockerボリューム、匿名Dockerボリューム、またはホスト上のバインドマウントです。
ボリュームを指定するには、ソースパスとターゲットパスを指定してください。
@@ -872,7 +872,7 @@ volumes:
### `jobs..services..options`
-Additional Docker container resource options. オプションの一覧は、「[`docker create`のオプション](https://docs.docker.com/engine/reference/commandline/create/#options)」を参照してください。
+追加のDockerコンテナリソースのオプション。 オプションの一覧は、「[`docker create`のオプション](https://docs.docker.com/engine/reference/commandline/create/#options)」を参照してください。
{% warning %}
@@ -946,7 +946,7 @@ Allowed expression contexts: `github`, `needs`, and `secrets`.
## フィルタパターンのチートシート
-You can use special characters in path, branch, and tag filters.
+特別なキャラクタをパス、ブランチ、タグフィルタで利用できます。
- `*`ゼロ個以上のキャラクタにマッチしますが、`/`にはマッチしません。 たとえば`Octo*`は`Octocat`にマッチします。
- `**`ゼロ個以上の任意のキャラクタにマッチします。
@@ -955,7 +955,7 @@ You can use special characters in path, branch, and tag filters.
- `[]` 括弧内にリストされた、あるいは範囲に含まれる1つのキャラクタにマッチします。 範囲に含めることができるのは`a-z`、`A-Z`、`0-9`のみです。 たとえば、`[0-9a-z]`という範囲は任意の数字もしくは小文字にマッチします。 たとえば`[CB]at`は`Cat`あるいは`Bat`にマッチし、`[1-2]00`は`100`や`200`にマッチします。
- `!`: パターンの先頭に置くと、肯定のパターンを否定にします。 先頭のキャラクタではない場合は、特別な意味を持ちません。
-The characters `*`, `[`, and `!` are special characters in YAML. If you start a pattern with `*`, `[`, or `!`, you must enclose the pattern in quotes.
+YAMLにおいては、`*`、`[`、`!`は特別なキャラクタです。 パターンを`*`、`[`、`!`で始める場合、そのパターンをクオートで囲まなければなりません。
```yaml
# 有効
@@ -983,7 +983,7 @@ For more information about branch, tag, and path filter syntax, see "[`on.
### ファイルパスにマッチするパターン
-Path patterns must match the whole path, and start from the repository's root.
+パスパターンはパス全体にマッチしなければならず、リポジトリのルートを出発点とします。
| パターン | マッチの説明 | マッチの例 |
| ----------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------ |
diff --git a/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md b/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md
index e92b04b449dd..dfa5276cbebf 100644
--- a/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md
+++ b/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md
@@ -114,7 +114,7 @@ Allows you to find the universally unique identifier (UUID) of your node in `clu
```
{% ifversion ghes %}
-Allows you to exempt a list of users from API rate limits. For more information, see "[Resources in the REST API](/rest/overview/resources-in-the-rest-api#rate-limiting)."
+Allows you to exempt a list of users from API rate limits. A hard limit of 120,000 requests will still apply to these users. For more information, see "[Resources in the REST API](/rest/overview/resources-in-the-rest-api#rate-limiting)."
``` shell
$ ghe-config app.github.rate-limiting-exempt-users "hubotgithub-actions"
diff --git a/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise.md b/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise.md
index fce4620e9c47..1d70ad47bd3d 100644
--- a/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise.md
+++ b/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise.md
@@ -70,4 +70,4 @@ Azure NSG を使用したインスタンスレベルの制限については、E
## IP許可リストで {% data variables.product.prodname_actions %} を使用する
-{% data reusables.github-actions.ip-allow-list-self-hosted-runners %}
+{% data reusables.actions.ip-allow-list-self-hosted-runners %}
diff --git a/translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises.md b/translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises.md
index 64da18c7323a..58face01dba9 100644
--- a/translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises.md
+++ b/translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises.md
@@ -1,7 +1,7 @@
---
title: About GitHub Actions for enterprises
-shortTitle: GitHub Actionsについて
-intro: '{% data variables.product.prodname_actions %} can improve developer productivity by automating your enterprise''s software development cycle.'
+shortTitle: About GitHub Actions
+intro: "{% data variables.product.prodname_actions %} can improve developer productivity by automating your enterprise's software development cycle."
versions:
ghec: '*'
ghes: '*'
@@ -12,31 +12,52 @@ topics:
- Enterprise
---
+{% ifversion ghes < 3.3 %}
+{% note %}
+
+**Note:** {% data reusables.enterprise.upgrade-ghes-for-actions %}
+
+{% endnote %}
+{% endif %}
+
+## About {% data variables.product.prodname_actions %} for enterprises
+
With {% data variables.product.prodname_actions %}, you can improve developer productivity by automating every phase of your enterprise's software development workflow.
-| タスク | 詳細情報 |
-| --------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Automatically test and build your application | [継続的インテグレーションについて](/actions/automating-builds-and-tests/about-continuous-integration) |
-| Deploy your application | "[About continuous deployment](/actions/deployment/about-deployments/about-continuous-deployment)" |
-| Automatically and securely package code into artifacts and containers | "[About packaging with {% data variables.product.prodname_actions %}](/actions/publishing-packages/about-packaging-with-github-actions)" |
-| Automate your project management tasks | "[Using {% data variables.product.prodname_actions %} for project management](/actions/managing-issues-and-pull-requests/using-github-actions-for-project-management)" |
+| Task | More information |
+| ---- | ---------------- |
+| Automatically test and build your application | "[About continuous integration](/actions/automating-builds-and-tests/about-continuous-integration)" |
+| Deploy your application | "[About continuous deployment](/actions/deployment/about-deployments/about-continuous-deployment)" |
+| Automatically and securely package code into artifacts and containers | "[About packaging with {% data variables.product.prodname_actions %}](/actions/publishing-packages/about-packaging-with-github-actions)" |
+| Automate your project management tasks | "[Using {% data variables.product.prodname_actions %} for project management](/actions/managing-issues-and-pull-requests/using-github-actions-for-project-management)" |
{% data variables.product.prodname_actions %} helps your team work faster at scale. When large repositories start using {% data variables.product.prodname_actions %}, teams merge significantly more pull requests per day, and the pull requests are merged significantly faster. For more information, see "[Writing and shipping code faster](https://octoverse.github.com/writing-code-faster/#scale-through-automation)" in the State of the Octoverse.
-{% data variables.product.prodname_actions %} also provides greater control over deployments. For example, you can use environments to require approval for a job to proceed, restrict which branches can trigger a workflow, or limit access to secrets.{% ifversion ghec or ghae-issue-4856 %} If your workflows need to access resources from a cloud provider that supports OpenID Connect (OIDC), you can configure your workflows to authenticate directly to the cloud provider. This will allow you to stop storing credentials as long-lived secrets and provide other security benefits. For more information, see "[About security hardening with OpenID Connect](/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect)."{% endif %}
+You can create your own unique automations, or you can use and adapt workflows from our ecosystem of over 10,000 actions built by industry leaders and the open source community. For more information, see "[Finding and customizing actions](/actions/learn-github-actions/finding-and-customizing-actions)."
{% data variables.product.prodname_actions %} is developer friendly, because it's integrated directly into the familiar {% data variables.product.product_name %} experience.
-You can create your own unique automations, or you can use and adapt workflows from our ecosystem of over 10,000 actions built by industry leaders and the open source community. 詳しい情報については「[アクションの発見とカスタマイズ](/actions/learn-github-actions/finding-and-customizing-actions)」を参照してください。
-
{% ifversion ghec %}You can enjoy the convenience of {% data variables.product.company_short %}-hosted runners, which are maintained and upgraded by {% data variables.product.company_short %}, or you{% else %}You{% endif %} can control your own private CI/CD infrastructure by using self-hosted runners. Self-hosted runners allow you to determine the exact environment and resources that complete your builds, testing, and deployments, without exposing your software development cycle to the internet. For more information, see {% ifversion ghec %}"[About {% data variables.product.company_short %}-hosted runners](/actions/using-github-hosted-runners/about-github-hosted-runners)" and{% endif %} "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners)."
+{% data variables.product.prodname_actions %} provides greater control over deployments. For example, you can use environments to require approval for a job to proceed, restrict which branches can trigger a workflow, or limit access to secrets.{% ifversion ghec or ghae-issue-4856 %} If your workflows need to access resources from a cloud provider that supports OpenID Connect (OIDC), you can configure your workflows to authenticate directly to the cloud provider. OIDC provides security benefits such as eliminating the need to store credentials as long-lived secrets. For more information, see "[About security hardening with OpenID Connect](/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect)."{% endif %}
+
{% data variables.product.prodname_actions %} also includes tools to govern your enterprise's software development cycle and meet compliance obligations. For more information, see "[Enforcing policies for {% data variables.product.prodname_actions %} in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise)."
+## About getting started with {% data variables.product.prodname_actions %}
+
+{% data reusables.actions.introducing-enterprise %}
+
+{% data reusables.actions.migrating-enterprise %}
+
+{% ifversion ghes %}
+{% data reusables.actions.ghes-actions-not-enabled-by-default %} After you finish planning, you can follow the instructions for enabling {% data variables.product.prodname_actions %}. For example, you may need to upgrade the CPU and memory resources for {% data variables.product.product_location %}. For more information, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server)."
+
+{% else %}
+After you finish planning, you can follow the instructions for getting started with {% data variables.product.prodname_actions %}. For more information, see {% ifversion ghec %}"[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_cloud %}](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-cloud)."{% elsif ghae %}"[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_managed %}](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-ae)."{% endif %}
+{% endif %}
-To learn more about how you can successfully adopt {% data variables.product.prodname_actions %} for your enterprise, follow the "[Adopt {% data variables.product.prodname_actions %} for your enterprise](/admin/guides#adopt-github-actions-for-your-enterprise)" learning path.
-## 参考リンク
+## Further reading
- "[Understanding {% data variables.product.prodname_actions %}](/actions/learn-github-actions/understanding-github-actions)"{% ifversion ghec %}
-- "[About billing for {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions/about-billing-for-github-actions)"{% endif %}
+- "[About billing for {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions/about-billing-for-github-actions)"{% endif %}
\ No newline at end of file
diff --git a/translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server.md b/translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server.md
index 8d5d97d5d6c2..e8eaeae8b1d1 100644
--- a/translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server.md
+++ b/translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server.md
@@ -25,7 +25,7 @@ This article explains how site administrators can configure {% data variables.pr
{% data reusables.enterprise.upgrade-ghes-for-actions %}
-{% data variables.product.prodname_actions %} is not enabled for {% data variables.product.prodname_ghe_server %} by default. You'll need to determine whether your instance has adequate CPU and memory resources to handle the load from {% data variables.product.prodname_actions %} without causing performance loss, and possibly increase those resources. You'll also need to decide which storage provider you'll use for the blob storage required to store artifacts generated by workflow runs. Then, you'll enable {% data variables.product.prodname_actions %} for your enterprise, manage access permissions, and add self-hosted runners to run workflows.
+{% data reusables.actions.ghes-actions-not-enabled-by-default %} You'll need to determine whether your instance has adequate CPU and memory resources to handle the load from {% data variables.product.prodname_actions %} without causing performance loss, and possibly increase those resources. You'll also need to decide which storage provider you'll use for the blob storage required to store artifacts generated by workflow runs. Then, you'll enable {% data variables.product.prodname_actions %} for your enterprise, manage access permissions, and add self-hosted runners to run workflows.
{% data reusables.actions.introducing-enterprise %}
diff --git a/translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md b/translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md
index 72d2d899328c..6278c0a8e12d 100644
--- a/translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md
+++ b/translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md
@@ -85,6 +85,12 @@ Whenever your workflow developers want to use an action that's stored in a priva
You should plan for how you'll manage the resources required to use {% data variables.product.prodname_actions %}.
+{% ifversion ghes %}
+### Hardware requirements
+
+You may need to upgrade the CPU and memory resources for {% data variables.product.product_location %} to handle the load from {% data variables.product.prodname_actions %} without causing performance loss. For more information, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server#review-hardware-requirements)."
+{% endif %}
+
### ランナー
{% data variables.product.prodname_actions %} workflows require runners.{% ifversion ghec %} You can choose to use {% data variables.product.prodname_dotcom %}-hosted runners or self-hosted runners. {% data variables.product.prodname_dotcom %}-hosted runners are convenient because they are managed by {% data variables.product.company_short %}, who handles maintenance and upgrades for you. However, you may want to consider self-hosted runners if you need to run a workflow that will access resources behind your firewall or you want more control over the resources, configuration, or geographic location of your runner machines. For more information, see "[About {% data variables.product.prodname_dotcom %}-hosted runners](/actions/using-github-hosted-runners/about-github-hosted-runners)" and "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners)."{% else %} You will need to host your own runners by installing the {% data variables.product.prodname_actions %} self-hosted runner application on your own machines. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners)."{% endif %}
@@ -111,7 +117,7 @@ You must configure external blob storage for these artifacts. Decide which suppo
{% ifversion ghec or ghes %}
-{% data reusables.github-actions.artifact-log-retention-statement %}
+{% data reusables.actions.artifact-log-retention-statement %}
{% endif %}
diff --git a/translations/ja-JP/content/admin/guides.md b/translations/ja-JP/content/admin/guides.md
index 373ad73e690d..183291db4657 100644
--- a/translations/ja-JP/content/admin/guides.md
+++ b/translations/ja-JP/content/admin/guides.md
@@ -136,5 +136,6 @@ includeGuides:
- /admin/user-management/requiring-two-factor-authentication-for-an-organization
- /admin/user-management/suspending-and-unsuspending-users
- /admin/overview/creating-an-enterprise-account
+ - /admin/user-management/managing-organizations-in-your-enterprise/restoring-a-deleted-organization
---
diff --git a/translations/ja-JP/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md b/translations/ja-JP/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md
index 0e0d42f00806..67c4e5d9d0cc 100644
--- a/translations/ja-JP/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md
+++ b/translations/ja-JP/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md
@@ -71,7 +71,7 @@ Enterprise 内のすべての Organization に対して {% data variables.produc
{% data reusables.enterprise-accounts.access-enterprise %}
{% data reusables.enterprise-accounts.policies-tab %}
{% data reusables.enterprise-accounts.actions-tab %}
-{% data reusables.github-actions.change-retention-period-for-artifacts-logs %}
+{% data reusables.actions.change-retention-period-for-artifacts-logs %}
{% endif %}
@@ -88,7 +88,7 @@ You can enforce policies to control how {% data variables.product.prodname_actio
{% data reusables.enterprise-accounts.access-enterprise %}
{% data reusables.enterprise-accounts.policies-tab %}
{% data reusables.enterprise-accounts.actions-tab %}
-{% data reusables.github-actions.workflows-from-public-fork-setting %}
+{% data reusables.actions.workflows-from-public-fork-setting %}
{% data reusables.actions.workflow-run-approve-link %}
@@ -98,16 +98,16 @@ You can enforce policies to control how {% data variables.product.prodname_actio
### Enforcing a policy for fork pull requests in private repositories
-{% data reusables.github-actions.private-repository-forks-overview %}
+{% data reusables.actions.private-repository-forks-overview %}
If a policy is enabled for an enterprise, the policy can be selectively disabled in individual organizations or repositories. If a policy is disabled for an enterprise, individual organizations or repositories cannot enable it.
-{% data reusables.github-actions.private-repository-forks-options %}
+{% data reusables.actions.private-repository-forks-options %}
{% data reusables.enterprise-accounts.access-enterprise %}
{% data reusables.enterprise-accounts.policies-tab %}
{% data reusables.enterprise-accounts.actions-tab %}
-{% data reusables.github-actions.private-repository-forks-configure %}
+{% data reusables.actions.private-repository-forks-configure %}
{% endif %}
@@ -115,11 +115,11 @@ If a policy is enabled for an enterprise, the policy can be selectively disabled
## Enforcing a policy for workflow permissions in your enterprise
-{% data reusables.github-actions.workflow-permissions-intro %}
+{% data reusables.actions.workflow-permissions-intro %}
You can set the default permissions for the `GITHUB_TOKEN` in the settings for your enterprise, organizations, or repositories. If you choose the restricted option as the default in your enterprise settings, this prevents the more permissive setting being chosen in the organization or repository settings.
-{% data reusables.github-actions.workflow-permissions-modifying %}
+{% data reusables.actions.workflow-permissions-modifying %}
{% data reusables.enterprise-accounts.access-enterprise %}
{% data reusables.enterprise-accounts.policies-tab %}
diff --git a/translations/ja-JP/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise.md b/translations/ja-JP/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise.md
index bb2260fdb341..82d6daa54e07 100644
--- a/translations/ja-JP/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise.md
+++ b/translations/ja-JP/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise.md
@@ -116,7 +116,7 @@ Enterprise owners can restrict access to assets owned by organizations in an ent
### IP許可リストで {% data variables.product.prodname_actions %} を使用する
-{% data reusables.github-actions.ip-allow-list-self-hosted-runners %}
+{% data reusables.actions.ip-allow-list-self-hosted-runners %}
{% endif %}
@@ -126,9 +126,11 @@ Enterprise owners can restrict access to assets owned by organizations in an ent
You can use a SSH certificate authorities (CA) to allow members of any organization owned by your enterprise to access that organization's repositories using SSH certificates you provide. {% data reusables.organizations.can-require-ssh-cert %}詳しい情報については、「[SSS 認証局について](/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities)」を参照してください。
+{% data reusables.organizations.add-extension-to-cert %}
+
### SSH 認証局を追加する
-{% data reusables.organizations.add-extension-to-cert %}
+If you require SSH certificates for your enterprise, enterprise members should use a special URL for Git operations over SSH. 詳しい情報については、「[SSH 認証局について](/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities#about-ssh-urls-with-ssh-certificates)」を参照してください。
{% data reusables.enterprise-accounts.access-enterprise %}
{% data reusables.enterprise-accounts.settings-tab %}
diff --git a/translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/index.md b/translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/index.md
index 8d08846c6fdc..66df4be2f7ba 100644
--- a/translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/index.md
+++ b/translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/index.md
@@ -27,6 +27,7 @@ children:
- /streaming-the-audit-logs-for-organizations-in-your-enterprise-account
- /removing-users-from-teams-and-organizations
- /removing-organizations-from-your-enterprise
+ - /restoring-a-deleted-organization
- /managing-projects-using-jira
- /continuous-integration-using-jenkins
shortTitle: Manage organizations
diff --git a/translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/restoring-a-deleted-organization.md b/translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/restoring-a-deleted-organization.md
new file mode 100644
index 000000000000..6cc1e657a28d
--- /dev/null
+++ b/translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/restoring-a-deleted-organization.md
@@ -0,0 +1,53 @@
+---
+title: Restoring a deleted organization
+intro: 'You can partially restore an organization that was previously deleted on {% data variables.product.product_location %}.'
+versions:
+ ghes: '*'
+type: how_to
+topics:
+ - Administrator
+ - Enterprise
+ - Organizations
+shortTitle: Restore organization
+permissions: 'Site administers can restore an organization on {% data variables.product.product_name %}.'
+---
+
+## About organization restoration
+
+You can use the site admin dashboard to restore an organization that was previously deleted on {% data variables.product.product_location %}, as long as the audit log Elasticsearch indices contain the data for the `org.delete` event.
+
+Immediately after you restore an organization, the organization will not be exactly the same as it was prior to the deletion. You'll have to manually restore any repositories that were owned by the organization. 詳しい情報については、「[削除されたリポジトリを復元する](/admin/user-management/managing-repositories-in-your-enterprise/restoring-a-deleted-repository)」を参照してください。
+
+You can also use the audit log to help you manually re-add teams and organization members. For more information, see "[Restoring members and teams](#restoring-members-and-teams)."
+
+## Restoring an organization
+
+{% data reusables.enterprise_site_admin_settings.access-settings %}
+1. Under "Search users, organizations, enterprises, teams, repositories, gists, and applications", search for the organization.
+
+ 
+
+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**.
+
+ 
+
+## Restoring members and teams
+
+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)."
+
+In all the search phrases below, replace ORGANIZATION with the name of the organization and TEAM with the name of the team.
+
+### Restoring organization members
+
+1. To find all users who were added to and removed from the organization, search the audit log for `action:org.add_member org:ORGANIZATION` and `action:org.remove_member org:ORGANIZATION`.
+1. Manually add to the organization each user that should still be a member. For more information, see "[Adding people to your organization](/organizations/managing-membership-in-your-organization/adding-people-to-your-organization)."
+
+### Restoring teams
+
+1. To find each team name, search the audit log for `action:team.create org:ORGANIZATION`.
+1. Manually recreate the team. For more information, see "[Creating a team](/organizations/organizing-members-into-teams/creating-a-team)."
+1. To find the members that have been added to each team, search for `action:team.add_member team:"ORGANIZATION/TEAM"`.
+1. Manually re-add the team members. For more information, see "[Adding organization members to a team](/organizations/organizing-members-into-teams/adding-organization-members-to-a-team)."
+1. To find the repositories that the team was granted access to, search for `action:team.add_repository team:"ORGANIZATION/TEAM"`.
+1. To find the access level that the team was granted for each repository, search for `action:team.update_repository_permission team:"ORGANIZATION/TEAM"`.
+1. Manually give the team access again. For more information, see "[Managing team access to an organization repository](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository)."
diff --git a/translations/ja-JP/content/authentication/managing-commit-signature-verification/checking-for-existing-gpg-keys.md b/translations/ja-JP/content/authentication/managing-commit-signature-verification/checking-for-existing-gpg-keys.md
index cf55844b8111..0d4186a83286 100644
--- a/translations/ja-JP/content/authentication/managing-commit-signature-verification/checking-for-existing-gpg-keys.md
+++ b/translations/ja-JP/content/authentication/managing-commit-signature-verification/checking-for-existing-gpg-keys.md
@@ -28,7 +28,12 @@ shortTitle: Existing GPG keys
{% data reusables.gpg.list-keys-with-note %}
3. コマンドの出力結果を見て、GPG キーペアがあるか確認します。
* GPG キーのペアが存在しないか、既存の GPG キーをコミットやタグへの署名に利用したくない場合、[新しい GPG キーを作成](/articles/generating-a-new-gpg-key)します。
- * GPG キーのペアが存在し、そのキーをコミットやタグへの署名に利用したい場合、[GPG キーを GitHub アカウント](/articles/adding-a-new-gpg-key-to-your-github-account)に追加します。
+ * If there's an existing GPG key pair and you want to use it to sign commits and tags, you can display the public key using the following command, substituting in the GPG key ID you'd like to use. この例では、GPG キー ID は `3AA5C34371567BD2` です。
+ ```shell
+ $ gpg --armor --export 3AA5C34371567BD2
+ # Prints the GPG key ID, in ASCII armor format
+ ```
+ You can then [add your GPG key to your GitHub account](/articles/adding-a-new-gpg-key-to-your-github-account).
## 参考リンク
diff --git a/translations/ja-JP/content/authentication/managing-commit-signature-verification/telling-git-about-your-signing-key.md b/translations/ja-JP/content/authentication/managing-commit-signature-verification/telling-git-about-your-signing-key.md
index 693d9a81789c..a43d10d94153 100644
--- a/translations/ja-JP/content/authentication/managing-commit-signature-verification/telling-git-about-your-signing-key.md
+++ b/translations/ja-JP/content/authentication/managing-commit-signature-verification/telling-git-about-your-signing-key.md
@@ -45,6 +45,12 @@ If you're using a GPG key that matches your committer identity and your verified
$ if [ -r ~/.bash_profile ]; then echo 'export GPG_TTY=$(tty)' >> ~/.bash_profile; \
else echo 'export GPG_TTY=$(tty)' >> ~/.profile; fi
```
+1. Optionally, to prompt you to enter a PIN or passphrase when required, install `pinentry-mac`. For example, using [Homebrew](https://brew.sh/):
+ ```shell
+ $ brew install pinentry-mac
+ $ echo "pinentry-program $(which pinentry-mac)" >> ~/.gnupg/gpg-agent.conf
+ $ killall gpg-agent
+ ```
{% data reusables.gpg.x-509-key %}
diff --git a/translations/ja-JP/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md b/translations/ja-JP/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md
index 815491b82bac..18e4e716a61d 100644
--- a/translations/ja-JP/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md
+++ b/translations/ja-JP/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md
@@ -16,9 +16,9 @@ shortTitle: GitHub Actionsの支払い
## {% data variables.product.prodname_actions %}の支払いについて
-{% data reusables.github-actions.actions-billing %}
+{% data reusables.actions.actions-billing %}
-{% data reusables.github-actions.actions-spending-limit-brief %} 詳しい情報については、「[利用上限について](#about-spending-limits)」を参照してください。
+{% data reusables.actions.actions-spending-limit-brief %} 詳しい情報については、「[利用上限について](#about-spending-limits)」を参照してください。
{% ifversion ghec %}
Microsoft Enterprise Agreement を通じて {% data variables.product.prodname_enterprise %} を購入した場合、Azure サブスクリプション ID を Enterprise アカウントに接続して、アカウントを含む金額を超える {% data variables.product.prodname_actions %} の使用を有効にして支払うことができます。 詳しい情報については、「[Azure サブスクリプションを Enterprise に接続する](/billing/managing-billing-for-your-github-account/connecting-an-azure-subscription-to-your-enterprise)」を参照してください。
@@ -99,7 +99,7 @@ For example, if your organization uses {% data variables.product.prodname_team %
## 利用上限について
-{% data reusables.github-actions.actions-spending-limit-detailed %}
+{% data reusables.actions.actions-spending-limit-detailed %}
アカウントの利用上限の管理と変更については、「[{% data variables.product.prodname_actions %} の利用上限の管理](/billing/managing-billing-for-github-actions/managing-your-spending-limit-for-github-actions)」を参照してください。
diff --git a/translations/ja-JP/content/billing/managing-billing-for-github-actions/managing-your-spending-limit-for-github-actions.md b/translations/ja-JP/content/billing/managing-billing-for-github-actions/managing-your-spending-limit-for-github-actions.md
index 49bcc44244d2..53a4c42664ca 100644
--- a/translations/ja-JP/content/billing/managing-billing-for-github-actions/managing-your-spending-limit-for-github-actions.md
+++ b/translations/ja-JP/content/billing/managing-billing-for-github-actions/managing-your-spending-limit-for-github-actions.md
@@ -19,9 +19,9 @@ shortTitle: Actionsの利用上限
## {% data variables.product.prodname_actions %} の利用上限について
-{% data reusables.github-actions.actions-billing %}
+{% data reusables.actions.actions-billing %}
-{% data reusables.github-actions.actions-spending-limit-brief %}
+{% data reusables.actions.actions-spending-limit-brief %}
{% data reusables.actions.actions-packages-set-spending-limit %} {% data variables.product.prodname_actions %} 使用料金の詳細については、「[{% data variables.product.prodname_actions %} の支払いについて](/billing/managing-billing-for-github-actions/about-billing-for-github-actions)」を参照してください。
diff --git a/translations/ja-JP/content/billing/managing-billing-for-github-actions/viewing-your-github-actions-usage.md b/translations/ja-JP/content/billing/managing-billing-for-github-actions/viewing-your-github-actions-usage.md
index 5a14fdcd05a0..456043233eb5 100644
--- a/translations/ja-JP/content/billing/managing-billing-for-github-actions/viewing-your-github-actions-usage.md
+++ b/translations/ja-JP/content/billing/managing-billing-for-github-actions/viewing-your-github-actions-usage.md
@@ -43,7 +43,7 @@ Enterprise アカウントについては、Enterprise オーナーと支払い
{% note %}
-**注釈:** Enterprise アカウントの支払い詳細には、オペレーティングシステムごとの利用時間 (分) の概要は示されません。 {% data reusables.github-actions.enterprise-billing-details %}
+**注釈:** Enterprise アカウントの支払い詳細には、オペレーティングシステムごとの利用時間 (分) の概要は示されません。 {% data reusables.actions.enterprise-billing-details %}
{% endnote %}
diff --git a/translations/ja-JP/content/billing/managing-billing-for-github-packages/viewing-your-github-packages-usage.md b/translations/ja-JP/content/billing/managing-billing-for-github-packages/viewing-your-github-packages-usage.md
index 443be411386b..32f0732a8f20 100644
--- a/translations/ja-JP/content/billing/managing-billing-for-github-packages/viewing-your-github-packages-usage.md
+++ b/translations/ja-JP/content/billing/managing-billing-for-github-packages/viewing-your-github-packages-usage.md
@@ -42,7 +42,7 @@ Enterprise アカウントについては、Enterprise オーナーと支払い
{% note %}
-**注釈:** Enterprise アカウントの支払い詳細には、Organizationごとのストレージデータ使用状況の概要しか示されません。 {% data reusables.github-actions.enterprise-billing-details %}
+**注釈:** Enterprise アカウントの支払い詳細には、Organizationごとのストレージデータ使用状況の概要しか示されません。 {% data reusables.actions.enterprise-billing-details %}
{% endnote %}
diff --git a/translations/ja-JP/content/billing/managing-your-github-billing-settings/setting-your-billing-email.md b/translations/ja-JP/content/billing/managing-your-github-billing-settings/setting-your-billing-email.md
index 3f054f5e28e9..f6221c42fbb1 100644
--- a/translations/ja-JP/content/billing/managing-your-github-billing-settings/setting-your-billing-email.md
+++ b/translations/ja-JP/content/billing/managing-your-github-billing-settings/setting-your-billing-email.md
@@ -64,3 +64,44 @@ shortTitle: 支払いメール
1. そのユーザのエントリで [**Edit**] をクリックします。 
1. メールアドレスの右の[Edit]ドロップダウンメニューを使い、[**Remove**]をクリックします。 
1. 確認ダイアログを確かめてから、[**Remove**] をクリックします。
+
+{% ifversion ghec %}
+## Setting your enterprise's billing email
+
+Your enterprise's billing email is where {% data variables.product.product_name %} sends receipts and other billing-related communication. The email address does not need to be unique to the enterprise account.
+
+Only enterprise members with the owner or billing manager role can access or change billing settings for your enterprise. For more information, see "[Managing users in your enterprise](/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise)."
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.settings-tab %}
+{% data reusables.enterprise-accounts.billing-tab %}
+1. Click **Billing emails**.
+2. Under "Email recipients", to the right of the billing email address, click **Edit**. 
+2. 有効なメールアドレスを入力し、[**Update**]をクリックします。 
+
+## Managing additional recipients for your enterprise's billing email
+
+支払い請求レポートを受信する必要のあるユーザが複数いる場合は、支払い請求先メールの受信者としてそのユーザのメールアドレスを追加できます。
+
+Only enterprise members with the owner or billing manager role can access or change billing settings for your enterprise. For more information, see "[Managing users in your enterprise](/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise)."
+
+### 支払い通知の受信者を追加する
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.settings-tab %}
+{% data reusables.enterprise-accounts.billing-tab %}
+1. Click **Billing emails**.
+2. Under "Email recipients", to the right of the billing email address, click **Add**. 
+3. 受信者のメールアドレスを入力し、[**Add**] をクリックします。 
+
+### 支払い通知の受信者を削除する
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.settings-tab %}
+{% data reusables.enterprise-accounts.billing-tab %}
+1. Click **Billing emails**.
+2. [Email recipients] で、削除したいメールアドレスを探します。
+3. そのユーザのエントリで [**Edit**] をクリックします。 
+4. メールアドレスの右の[Edit]ドロップダウンメニューを使い、[**Remove**]をクリックします。 
+5. 確認ダイアログを確かめてから、[**Remove**] をクリックします。
+{% endif %}
diff --git a/translations/ja-JP/content/code-security/code-scanning/integrating-with-code-scanning/uploading-a-sarif-file-to-github.md b/translations/ja-JP/content/code-security/code-scanning/integrating-with-code-scanning/uploading-a-sarif-file-to-github.md
index 8f21ec78dff1..0e33d7b940fb 100644
--- a/translations/ja-JP/content/code-security/code-scanning/integrating-with-code-scanning/uploading-a-sarif-file-to-github.md
+++ b/translations/ja-JP/content/code-security/code-scanning/integrating-with-code-scanning/uploading-a-sarif-file-to-github.md
@@ -86,7 +86,11 @@ jobs:
build:
runs-on: ubuntu-latest{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
permissions:
- security-events: write{% endif %}
+ # required for all workflows
+ security-events: write
+ # only required for workflows in private repositories
+ actions: read
+ contents: read{% endif %}
steps:
# This step checks out a copy of your repository.
- name: Checkout repository
@@ -123,7 +127,11 @@ jobs:
build:
runs-on: ubuntu-latest{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
permissions:
- security-events: write{% endif %}
+ # required for all workflows
+ security-events: write
+ # only required for workflows in private repositories
+ actions: read
+ contents: read{% endif %}
steps:
- uses: actions/checkout@v2
- name: Run npm install
diff --git a/translations/ja-JP/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-encrypted-secrets-for-dependabot.md b/translations/ja-JP/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-encrypted-secrets-for-dependabot.md
index 48854a8290fc..4f4bc4a4abfc 100644
--- a/translations/ja-JP/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-encrypted-secrets-for-dependabot.md
+++ b/translations/ja-JP/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-encrypted-secrets-for-dependabot.md
@@ -44,11 +44,11 @@ password: ${{secrets.MY_ARTIFACTORY_PASSWORD}}
## {% data variables.product.prodname_dependabot %} にリポジトリシークレットを追加する
-{% data reusables.github-actions.permissions-statement-secrets-repository %}
+{% data reusables.actions.permissions-statement-secrets-repository %}
{% data reusables.repositories.navigate-to-repo %}
{% data reusables.repositories.sidebar-settings %}
-{% data reusables.github-actions.sidebar-secret %}
+{% data reusables.actions.sidebar-secret %}
{% data reusables.dependabot.dependabot-secrets-button %}
1. **New repository secret（新しいリポジトリのシークレット）**をクリックしてください。
1. **[Name（名前）]** 入力ボックスにシークレットの名前を入力します。
@@ -63,11 +63,11 @@ password: ${{secrets.MY_ARTIFACTORY_PASSWORD}}
Organizationでシークレットを作成する場合、ポリシーを使用して、そのシークレットにアクセスできるリポジトリを制限できます。 たとえば、すべてのリポジトリにアクセスを許可したり、プライベート リポジトリまたは指定したリポジトリ のリストのみにアクセスを制限したりできます。
-{% data reusables.github-actions.permissions-statement-secrets-organization %}
+{% data reusables.actions.permissions-statement-secrets-organization %}
{% data reusables.organizations.navigate-to-org %}
{% data reusables.organizations.org_settings %}
-{% data reusables.github-actions.sidebar-secret %}
+{% data reusables.actions.sidebar-secret %}
{% data reusables.dependabot.dependabot-secrets-button %}
1. **New organization secret（新しいOrganizationのシークレット）**をクリックしてください。
1. **[Name（名前）]** 入力ボックスにシークレットの名前を入力します。
diff --git a/translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces.md b/translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces.md
index cb358f2cbf7a..da98f032a790 100644
--- a/translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces.md
+++ b/translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces.md
@@ -51,7 +51,7 @@ Organization リポジトリのシークレットを作成するには、管理
Organizationでシークレットを作成する場合、ポリシーを使用して、そのシークレットにアクセスできるリポジトリを制限できます。 たとえば、すべてのリポジトリにアクセスを許可したり、プライベート リポジトリまたは指定したリポジトリ のリストのみにアクセスを制限したりできます。
-{% data reusables.github-actions.permissions-statement-secrets-organization %}
+{% data reusables.actions.permissions-statement-secrets-organization %}
{% data reusables.organizations.navigate-to-org %}
{% data reusables.organizations.org_settings %}
@@ -68,7 +68,7 @@ Organization 内のシークレットに適用されているアクセスポリ
{% data reusables.organizations.navigate-to-org %}
{% data reusables.organizations.org_settings %}
-{% data reusables.github-actions.sidebar-secret %}
+{% data reusables.actions.sidebar-secret %}
1. シークレットのリストには、設定済みのアクセス許可とポリシーが含まれます。 例: 
1. 各シークレットに設定されているアクセス許可の詳細については、[**Update（更新）**] をクリックしてください。
diff --git a/translations/ja-JP/content/get-started/learning-about-github/githubs-products.md b/translations/ja-JP/content/get-started/learning-about-github/githubs-products.md
index 67529eb2f187..17a0a0b3b911 100644
--- a/translations/ja-JP/content/get-started/learning-about-github/githubs-products.md
+++ b/translations/ja-JP/content/get-started/learning-about-github/githubs-products.md
@@ -89,7 +89,7 @@ Organizationの{% data variables.product.prodname_free_team %}で利用できる
{% data variables.product.company_short %} bills for {% data variables.product.prodname_team %} on a per-user basis. For more information, see "[About per-user pricing]({% ifversion not fpt %}/free-pro-team@latest{% endif %}/billing/managing-billing-for-your-github-account/about-per-user-pricing){% ifversion fpt %}."{% else %}" in the Free, Pro, & Team documentation.{% endif %}
-{% data reusables.github-actions.actions-billing %}
+{% data reusables.actions.actions-billing %}
## {% data variables.product.prodname_enterprise %}
diff --git a/translations/ja-JP/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-allowed-ip-addresses-for-your-organization.md b/translations/ja-JP/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-allowed-ip-addresses-for-your-organization.md
index 51c518edfa94..34d3c0388ec5 100644
--- a/translations/ja-JP/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-allowed-ip-addresses-for-your-organization.md
+++ b/translations/ja-JP/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-allowed-ip-addresses-for-your-organization.md
@@ -82,4 +82,4 @@ Enterprise アカウントで Organization に対して許可される IP アド
## IP許可リストで {% data variables.product.prodname_actions %} を使用する
-{% data reusables.github-actions.ip-allow-list-self-hosted-runners %}
+{% data reusables.actions.ip-allow-list-self-hosted-runners %}
diff --git a/translations/ja-JP/content/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities.md b/translations/ja-JP/content/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities.md
index df1b92a660cc..e04c30902777 100644
--- a/translations/ja-JP/content/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities.md
+++ b/translations/ja-JP/content/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities.md
@@ -28,9 +28,15 @@ SSH CAをOrganizationまたはEnterpriseアカウントに追加すると、そ
SAMLシングルサインオンが強制されている場合でも、Organizationのメンバーはそれぞれの署名済み証明書を認証に使用できます。 SSH証明書を必須にしている場合を除き、Organizationのメンバーは他の認証方法、たとえばユーザー名とパスワード、個人アクセストークン、独自のSSHキーなどを使用して、GitのOrganizationリソースにアクセスし続けることができます。
{% endif %}
-メンバーは、自分のユーザアカウントが所有するリポジトリのフォークにアクセスする際に、自分の証明書を使うことはできなくなります。
+Members will not be able to use their certificates to access forks of your repositories that are owned by their personal accounts.
-認証エラーを防ぐために、Organization のメンバーは Organization ID を含む特殊な URL を使用し、署名された証明書を使ってリポジトリを複製する必要があります。 リポジトリに対する読み取りアクセス権限がある人は誰でも、リポジトリページでこの URL を確認できます。 詳しい情報については[リポジトリのクローン](/articles/cloning-a-repository)を参照してください。
+## About SSH URLs with SSH certificates
+
+If your organization requires SSH certificates, to prevent authentication errors, organization members should use a special URL that includes the organization ID when performing Git operations over SSH. This special URL allows the client and server to more easily negotiate which key on the member's computer should be used for authentication. If a member uses the normal URL, which starts with `git@github.com`, the SSH client might offer the wrong key, causing the operation to fail.
+
+Anyone with read access to the repository can find this URL by selecting the **Code** dropdown menu on the main page of the repository, then clicking **Use SSH**.
+
+If your organization doesn't require SSH certificates, members can continue to use their own SSH keys, or other means of authentication. In that case, either the special URL or the normal URL, which starts with `git@github.com`, will work.
## 証明書の発行
diff --git a/translations/ja-JP/content/organizations/managing-git-access-to-your-organizations-repositories/managing-your-organizations-ssh-certificate-authorities.md b/translations/ja-JP/content/organizations/managing-git-access-to-your-organizations-repositories/managing-your-organizations-ssh-certificate-authorities.md
index b0932880ac4c..9150c18f2c56 100644
--- a/translations/ja-JP/content/organizations/managing-git-access-to-your-organizations-repositories/managing-your-organizations-ssh-certificate-authorities.md
+++ b/translations/ja-JP/content/organizations/managing-git-access-to-your-organizations-repositories/managing-your-organizations-ssh-certificate-authorities.md
@@ -20,9 +20,11 @@ Organizationのオーナーは、OrganizationのSSH認証局 (CAN) を管理で
SSH CAをOrganizationに追加すると、メンバーはあなたが提供したSSH証明書を使用してOrganizationにアクセスできるようになります。 {% data reusables.organizations.can-require-ssh-cert %}詳細については、「[SSH認証局について](/articles/about-ssh-certificate-authorities)」を参照してください。
+{% data reusables.organizations.add-extension-to-cert %}
+
## SSH 認証局を追加する
-{% data reusables.organizations.add-extension-to-cert %}
+If you require SSH certificates for your enterprise, enterprise members should use a special URL for Git operations over SSH. 詳しい情報については、「[SSH 認証局について](/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities#about-ssh-urls-with-ssh-certificates)」を参照してください。
{% data reusables.profile.access_org %}
{% data reusables.profile.org_settings %}
diff --git a/translations/ja-JP/content/organizations/managing-organization-settings/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-organization.md b/translations/ja-JP/content/organizations/managing-organization-settings/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-organization.md
index 98e6194e44eb..0165ce479228 100644
--- a/translations/ja-JP/content/organizations/managing-organization-settings/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-organization.md
+++ b/translations/ja-JP/content/organizations/managing-organization-settings/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-organization.md
@@ -21,4 +21,4 @@ shortTitle: 保持期間の設定
{% data reusables.organizations.navigate-to-org %}
{% data reusables.organizations.org_settings %}
{% data reusables.organizations.settings-sidebar-actions %}
-{% data reusables.github-actions.change-retention-period-for-artifacts-logs %}
+{% data reusables.actions.change-retention-period-for-artifacts-logs %}
diff --git a/translations/ja-JP/content/organizations/managing-organization-settings/deleting-an-organization-account.md b/translations/ja-JP/content/organizations/managing-organization-settings/deleting-an-organization-account.md
index 35594253833e..6f2c4e80c5aa 100644
--- a/translations/ja-JP/content/organizations/managing-organization-settings/deleting-an-organization-account.md
+++ b/translations/ja-JP/content/organizations/managing-organization-settings/deleting-an-organization-account.md
@@ -12,7 +12,7 @@ versions:
topics:
- Organizations
- Teams
-shortTitle: Organizationアカウントの削除
+shortTitle: Delete organization
---
{% ifversion fpt or ghec %}
@@ -26,7 +26,15 @@ shortTitle: Organizationアカウントの削除
## 1. Organization コンテンツのバックアップ
-Organization を削除すると、GitHub では**コンテンツを復元できません**。 したがって、Organization を削除する前に、アカウントからすべてのリポジトリ、ウィキ、Issue、プロジェクトボードのコピーがあることを確認してください。
+{% ifversion not ghes %} After you delete an organization, {% data variables.product.company_short %} **cannot restore your content**. Therefore, before{% else %}Before{% endif %} you delete your organization, make sure you have a copy of all repositories, wikis, issues, and project boards from the account.
+
+{% ifversion ghes %}
+{% note %}
+
+**Note:** If necessary, a site administrator for {% data variables.product.product_location %} may be able to partially restore a deleted organization. For more information, see "[Restoring a deleted organization](/admin/user-management/managing-organizations-in-your-enterprise/restoring-a-deleted-organization)."
+
+{% endnote %}
+{% endif %}
## 2. Organization の削除
diff --git a/translations/ja-JP/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md b/translations/ja-JP/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md
index d628be18bd61..1ced1cb02a51 100644
--- a/translations/ja-JP/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md
+++ b/translations/ja-JP/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md
@@ -19,11 +19,11 @@ shortTitle: アクションの無効化もしくは制限
## Organization の {% data variables.product.prodname_actions %} 権限について
-{% data reusables.github-actions.disabling-github-actions %} {% data variables.product.prodname_actions %} の詳細は、「[{% data variables.product.prodname_actions %}について](/actions/getting-started-with-github-actions/about-github-actions)」を参照してください。
+{% data reusables.actions.disabling-github-actions %} {% data variables.product.prodname_actions %} の詳細は、「[{% data variables.product.prodname_actions %}について](/actions/getting-started-with-github-actions/about-github-actions)」を参照してください。
-Organization のすべてのリポジトリについて {% data variables.product.prodname_actions %} を有効化することができます。 {% data reusables.github-actions.enabled-actions-description %} Organization のすべてのリポジトリについて 、{% data variables.product.prodname_actions %} を無効化できます。 {% data reusables.github-actions.disabled-actions-description %}
+Organization のすべてのリポジトリについて {% data variables.product.prodname_actions %} を有効化することができます。 {% data reusables.actions.enabled-actions-description %} Organization のすべてのリポジトリについて 、{% data variables.product.prodname_actions %} を無効化できます。 {% data reusables.actions.disabled-actions-description %}
-あるいは、Organization のすべてのリポジトリについて {% data variables.product.prodname_actions %} を有効化したうえで、ワークフローで実行できるアクションを制限することができます。 {% data reusables.github-actions.enabled-local-github-actions %}
+あるいは、Organization のすべてのリポジトリについて {% data variables.product.prodname_actions %} を有効化したうえで、ワークフローで実行できるアクションを制限することができます。 {% data reusables.actions.enabled-local-github-actions %}
## Organization の {% data variables.product.prodname_actions %} 権限の管理
@@ -68,7 +68,7 @@ Organizationのこの動作は、以下の手順で設定できます。 この
{% data reusables.profile.access_org %}
{% data reusables.profile.org_settings %}
{% data reusables.organizations.settings-sidebar-actions %}
-{% data reusables.github-actions.workflows-from-public-fork-setting %}
+{% data reusables.actions.workflows-from-public-fork-setting %}
{% data reusables.actions.workflow-run-approve-link %}
{% endif %}
@@ -76,28 +76,28 @@ Organizationのこの動作は、以下の手順で設定できます。 この
{% ifversion fpt or ghes or ghec %}
## プライベートリポジトリのフォークのワークフローを有効にする
-{% data reusables.github-actions.private-repository-forks-overview %}
+{% data reusables.actions.private-repository-forks-overview %}
{% ifversion ghec or ghae or ghes %}Enterpriseでポリシーが無効化されていると、それをOrganizationで有効化することはできません。{% endif %}Organizationでポリシーが無効化されていると、それをリポジトリで有効化することはできません。 Organizationがポリシーを有効化していると、そのポリシーを個々のリポジトリで無効化することはできません。
-{% data reusables.github-actions.private-repository-forks-options %}
+{% data reusables.actions.private-repository-forks-options %}
### Organization のプライベートフォークポリシーを設定する
{% data reusables.profile.access_org %}
{% data reusables.profile.org_settings %}
{% data reusables.organizations.settings-sidebar-actions %}
-{% data reusables.github-actions.private-repository-forks-configure %}
+{% data reusables.actions.private-repository-forks-configure %}
{% endif %}
{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
## Organizationに対する`GITHUB_TOKEN`の権限の設定
-{% data reusables.github-actions.workflow-permissions-intro %}
+{% data reusables.actions.workflow-permissions-intro %}
Organizationもしくはリポジトリの設定で、`GITHUB_TOKEN`のデフォルト権限を設定できます。 Organizationの設定でデフォルトとして制限付きのオプションを選択した場合、そのオプションはOrganization内のリポジトリの設定でも自動設定され、許可するようなオプションは無効化されます。 Organizationが{% data variables.product.prodname_enterprise %}に属しており、Enterprise設定でさらに制約の強いデフォルトが選択されている場合、Organizationの設定でもっと許可をするようなデフォルトは選択できません。
-{% data reusables.github-actions.workflow-permissions-modifying %}
+{% data reusables.actions.workflow-permissions-modifying %}
### デフォルトの`GITHUB_TOKEN`権限の設定
diff --git a/translations/ja-JP/content/organizations/organizing-members-into-teams/creating-a-team.md b/translations/ja-JP/content/organizations/organizing-members-into-teams/creating-a-team.md
index 1e1da8b8b142..731d1bdb9a10 100644
--- a/translations/ja-JP/content/organizations/organizing-members-into-teams/creating-a-team.md
+++ b/translations/ja-JP/content/organizations/organizing-members-into-teams/creating-a-team.md
@@ -28,7 +28,7 @@ Organization のオーナーと親チームのメンテナだけが親の下に
{% ifversion ghec %}
1. あるいは、OrganizationあるいはEnterpriseアカウントがTeam同期を使っているか、Enterpriseが{% data variables.product.prodname_emus %}を使っているなら、アイデンティティプロバイダのグループをTeamに接続してください。
* Enterpriseが{% data variables.product.prodname_emus %}を使っているなら、"Identity Provider Groups（アイデンティティプロバイダグループ）"ドロップダウンメニューを使い、新しいTeamに接続する1つのアイデンティティプロバイダグループを選択してください。 詳しい情報については「[アイデンティティプロバイダグループとのTeamメンバーシップの管理](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/managing-team-memberships-with-identity-provider-groups)」を参照してください。
- * If your organization or enterprise account uses team synchronization, use the "Identity Provider Groups" drop-down menu, and select up to five identity provider groups to connect to the new team. 詳しい情報については「[アイデンティティプロバイダグループとTeamの同期](/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group)」を参照してください。 
+ * OrganizationもしくはEnterpriseアカウントがTeam同期を使っているなら、"Identity Provider Groups（アイデンティティプロバイダグループ）"ドロップダウンメニューを使い、新しいTeamに接続するアイデンティティプロバイダグループを最大で5つまで選択してください。 詳しい情報については「[アイデンティティプロバイダグループとTeamの同期](/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group)」を参照してください。 
{% endif %}
{% data reusables.organizations.team_visibility %}
{% data reusables.organizations.create_team %}
diff --git a/translations/ja-JP/content/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team.md b/translations/ja-JP/content/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team.md
index 833f1f02fc2f..6d7cdb9e4445 100644
--- a/translations/ja-JP/content/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team.md
+++ b/translations/ja-JP/content/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team.md
@@ -1,6 +1,6 @@
---
-title: Managing code review settings for your team
-intro: You can decrease noise for your team by limiting notifications when your team is requested to review a pull request.
+title: Teamのコードレビュー設定の管理
+intro: TeamがPull Requestのレビューをリクエストされた際の通知を制限することによって、Teamのノイズを減らすことができます。
redirect_from:
- /github/setting-up-and-managing-organizations-and-teams/managing-code-review-assignment-for-your-team
- /organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team
@@ -13,31 +13,31 @@ versions:
topics:
- Organizations
- Teams
-shortTitle: Code review settings
+shortTitle: コードレビューの設定
permissions: Team maintainers and organization owners can configure code review settings.
---
-## About code review settings
+## コードレビューの設定について
{% if only-notify-requested-members %}
-To reduce noise for your team and clarify individual responsibility for pull request reviews, you can configure code review settings.
+Teamのノイズを減らし、Pull Requestレビューに対する個人の責任を明確にするために、コードレビューの設定ができます。
-- Team notifications
-- Auto assignment
+- Teamの通知
+- 自動割り当て
-## About team notifications
+## Team通知について
-When you choose to only notify requested team members, you disable sending notifications to the entire team when the team is requested to review a pull request if a specific member of that team is also requested for review. This is especially useful when a repository is configured with teams as code owners, but contributors to the repository often know a specific individual that would be the correct reviewer for their pull request. 詳細は「[コードオーナーについて](/github/creating-cloning-and-archiving-repositories/about-code-owners)」を参照してください。
+リクエストされたTeamメンバーにのみ通知されるようにした場合、TeamにPull Requestのレビューがリクエストされても、そのTeam内の特定のメンバーにもレビューがリクエストされていたなら、Team全体への通知送信は無効化されることになります。 これは、リポジトリでTeamがコードオーナーとして設定されているものの、しばしば特定の個人が自分たちのPull Requestに対する適切なコードレビュー担当者となるだろうことをリポジトリのコントリビューターたちが知っている場合に、特に役立ちます。 詳細は「[コードオーナーについて](/github/creating-cloning-and-archiving-repositories/about-code-owners)」を参照してください。
-## About auto assignment
+## 自動割り当てについて
{% endif %}
-When you enable auto assignment, any time your team has been requested to review a pull request, the team is removed as a reviewer and a specified subset of team members are assigned in the team's place. コードレビューの割り当てでは、Team がレビューをリクエストされたとき、Team の全体に通知するか、Team メンバーのサブセットのみに通知するかを決めることができます。
+自動割り当てを有効化すると、TeamがPull Requestのレビューをリクエストされた場合、そのチームはレビュー担当者から外され、指定されたTeamメンバーの一部がそのTeamの代わりに割り当てられます。 コードレビューの割り当てでは、Team がレビューをリクエストされたとき、Team の全体に通知するか、Team メンバーのサブセットのみに通知するかを決めることができます。
-When code owners are automatically requested for review, the team is still removed and replaced with individuals unless a branch protection rule is configured to require review from code owners. If such a branch protection rule is in place, the team request cannot be removed and so the individual request will appear in addition.
+コードオーナーが自動的にレビューをリクエストされた場合でも、ブランチ保護ルールがコードオーナーからのレビューを必須として設定されていないかぎり、やはりTeamは外され、個人に置き換えられます。 そういったブランチ保護ルールがある場合、Teamへのリクエストは削除できないので、個人へのリクエストは追加されることになります。
{% ifversion fpt %}
-To further enhance your team's collaboration abilities, you can upgrade to {% data variables.product.prodname_ghe_cloud %}, which includes features like protected branches and code owners on private repositories. {% data reusables.enterprise.link-to-ghec-trial %}
+Teamのコラボレーション能力をさらに拡大するために、保護されたブランチやプライベートリポジトリのコードオーナーといった機能を含む{% data variables.product.prodname_ghe_cloud %}へのアップグレードが可能です。 {% data reusables.enterprise.link-to-ghec-trial %}
{% endif %}
### ルーティングアルゴリズム
@@ -48,33 +48,33 @@ To further enhance your team's collaboration abilities, you can upgrade to {% da
ロードバランスアルゴリズムは、各メンバーの最近のレビューリクエスト合計数に基づいてレビュー担当者を選択し、メンバーごとの未処理レビューの数を考慮します。 ロードバランスアルゴリズムは、各 Teamメンバーが 30 日間に等しい数のプルリクエストをレビューすることを保証しようとします。
-Any team members that have set their status to "Busy" will not be selected for review. If all team members are busy, the pull request will remain assigned to the team itself. For more information about user statuses, see "[Setting a status](/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile#setting-a-status)."
+ステータスを"Busy"に設定したTeamメンバーは、レビューに選択されません。 すべてのTeamメンバーがBusyの場合、Pull RequestはTeam自体に割り当てられたままになります。 ユーザのステータスに関する詳しい情報については「[ステータスの設定](/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile#setting-a-status)」を参照してください。
{% if only-notify-requested-members %}
-## Configuring team notifications
+## Team通知の設定
{% data reusables.profile.access_org %}
{% data reusables.user-settings.access_org %}
{% data reusables.organizations.specific_team %}
{% data reusables.organizations.team_settings %}
{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %}
-1. In the left sidebar, click **{% octicon "code-review" aria-label="The code-review icon" %} Code review**.
+1. 左のサイドバーで**{% octicon "code-review" aria-label="The code-review icon" %} Code review（コードレビュー）**をクリックしてください。
{% else %}
-1. In the left sidebar, click **Code review** 
+1. 左のサイドバーで**Code review（コードレビュー）**をクリックしてください。 
{% endif %}
-1. Select **Only notify requested team members.** 
+1. **Only notify requested team members.（リクエストされたTeamメンバーにのみ通知）**を選択してください。 
1. [**Save changes**] をクリックします。
{% endif %}
-## Configuring auto assignment
+## 自動割り当ての設定
{% data reusables.profile.access_org %}
{% data reusables.user-settings.access_org %}
{% data reusables.organizations.specific_team %}
{% data reusables.organizations.team_settings %}
{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %}
-1. In the left sidebar, click **{% octicon "code-review" aria-label="The code-review icon" %} Code review**.
+1. 左のサイドバーで**{% octicon "code-review" aria-label="The code-review icon" %} Code review（コードレビュー）**をクリックしてください。
{% else %}
-1. In the left sidebar, click **Code review** 
+1. 左のサイドバーで**Code review（コードレビュー）**をクリックしてください。 
{% endif %}
1. [**Enable auto assignment**] を選択します。 
1. [How many team members should be assigned to review?] でドロップダウンメニューを使用し、各プルリクエストに割り当てるレビュー担当者の数を選択します。 ![[Number of reviewers] ドロップダウン](/assets/images/help/teams/review-assignment-number.png)
diff --git a/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork.md b/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork.md
index 676836b7ed03..a2684654824d 100644
--- a/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork.md
+++ b/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork.md
@@ -13,6 +13,7 @@ versions:
ghec: '*'
topics:
- Pull requests
+permissions: People with write access for a forked repository can sync the fork to the upstream repository.
---
{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
@@ -20,8 +21,8 @@ topics:
## Syncing a fork from the web UI
1. On {% data variables.product.product_name %}, navigate to the main page of the forked repository that you want to sync with the upstream repository.
-1. Select the **Fetch upstream** drop-down. 
-1. Review the details about the commits from the upstream repository, then click **Fetch and merge**. 
+2. Select the **Fetch upstream** drop-down. 
+3. Review the details about the commits from the upstream repository, then click **Fetch and merge**. 
If the changes from the upstream repository cause conflicts, {% data variables.product.company_short %} will prompt you to create a pull request to resolve the conflicts.
@@ -33,6 +34,7 @@ If the changes from the upstream repository cause conflicts, {% data variables.p
{% data reusables.command_line.open_the_multi_os_terminal %}
2. ワーキングディレクトリをローカルプロジェクトに変更します。
3. 上流リポジトリから、ブランチと各ブランチのコミットをフェッチします。 `BRANCHNAME` へのコミットは、ローカルブランチ `upstream/BRANCHNAME` に保存されます。
+
```shell
$ git fetch upstream
> remote: Counting objects: 75, done.
@@ -42,12 +44,16 @@ If the changes from the upstream repository cause conflicts, {% data variables.p
> From https://{% data variables.command_line.codeblock %}/ORIGINAL_OWNER/ORIGINAL_REPOSITORY
> * [new branch] main -> upstream/main
```
+
4. フォークのローカルのデフォルトブランチを確認してください。この場合は、`main` を使用します。
+
```shell
$ git checkout main
> Switched to branch 'main'
```
+
5. 上流のデフォルトブランチ (この場合は `upstream/main`) からの変更をローカルのデフォルトブランチにマージします。 これにより、ローカルの変更を失うことなく、フォークのデフォルトブランチが上流リポジトリと同期されます。
+
```shell
$ git merge upstream/main
> Updating a422352..5fdff0f
diff --git a/translations/ja-JP/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/about-commits.md b/translations/ja-JP/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/about-commits.md
index f821fe9aabc2..23c6396aedef 100644
--- a/translations/ja-JP/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/about-commits.md
+++ b/translations/ja-JP/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/about-commits.md
@@ -6,6 +6,7 @@ redirect_from:
- /github/committing-changes-to-your-project/why-are-my-commits-in-the-wrong-order
- /github/committing-changes-to-your-project/about-commits
- /github/committing-changes-to-your-project/creating-and-editing-commits/about-commits
+ - /pull-requests/committing-changes-to-your-project/viewing-and-comparing-commits/commit-branch-and-tag-labels
versions:
fpt: '*'
ghes: '*'
@@ -24,5 +25,20 @@ Organization に代わってコミットを作成することもできます。
リベースを使用すると、一連のコミットを変更したり、タイムラインでのコミットの順序を変更したりできます。 詳しい情報については、「[Git リベースについて](/github/getting-started-with-github/about-git-rebase)」を参照してください。
+## About commit branches and tag labels
+
+You can see which branch a commit is on by looking at the labels beneath the commit on the commit page.
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.navigate-to-commit-page %}
+1. コミットメッセージリンクをクリックしてコミットに移動します。 
+2. To see what branch the commit is on, check the label below the commit message. 
+
+If your commit is not on the default branch (`main`), the label will show the branches which contain the commit. If the commit is part of an unmerged pull request, you can click the link to go to the pull request.
+
+コミットがデフォルトブランチにある場合は、そのコミットを含むタグがすべて表示され、ブランチのリストにはデフォルトブランチのみが表示されます。 For more information on tags, see "[Git Basics - Tagging](https://git-scm.com/book/en/v2/Git-Basics-Tagging)" in the Git documentation.
+
+
+
## 参考リンク
- 「[{% data variables.product.prodname_desktop %} でプロジェクトの変更をコミットしてレビューする](/desktop/contributing-to-projects/committing-and-reviewing-changes-to-your-project#about-commits)」
diff --git a/translations/ja-JP/content/pull-requests/committing-changes-to-your-project/viewing-and-comparing-commits/commit-branch-and-tag-labels.md b/translations/ja-JP/content/pull-requests/committing-changes-to-your-project/viewing-and-comparing-commits/commit-branch-and-tag-labels.md
deleted file mode 100644
index bdb358246fb3..000000000000
--- a/translations/ja-JP/content/pull-requests/committing-changes-to-your-project/viewing-and-comparing-commits/commit-branch-and-tag-labels.md
+++ /dev/null
@@ -1,27 +0,0 @@
----
-title: コミットのブランチおよびタグラベル
-intro: コミットページの、コミットの下にあるラベルを見れば、コミットがどのブランチにあるか簡単に分かります。
-redirect_from:
- - /articles/commit-branch-and-tag-labels
- - /github/committing-changes-to-your-project/commit-branch-and-tag-labels
- - /github/committing-changes-to-your-project/viewing-and-comparing-commits/commit-branch-and-tag-labels
-versions:
- fpt: '*'
- ghes: '*'
- ghae: '*'
- ghec: '*'
-shortTitle: Branch & tag labels
----
-
-コミットがデフォルトブランチにない場合、コミットを含むブランチが表示されます。 コミットがマージされていないプルリクエストの一部である場合は、リンクが表示されます。
-
-
-
-コミットがデフォルトブランチにある場合は、そのコミットを含むタグがすべて表示され、ブランチのリストにはデフォルトブランチのみが表示されます。
-
-
-
-## 参考リンク
-
-* 「[コミットに署名する](/articles/signing-commits)」
-* 「[タグに署名する](/articles/signing-tags)」
diff --git a/translations/ja-JP/content/pull-requests/committing-changes-to-your-project/viewing-and-comparing-commits/index.md b/translations/ja-JP/content/pull-requests/committing-changes-to-your-project/viewing-and-comparing-commits/index.md
index 7861f9bd4a02..9f1e997374c6 100644
--- a/translations/ja-JP/content/pull-requests/committing-changes-to-your-project/viewing-and-comparing-commits/index.md
+++ b/translations/ja-JP/content/pull-requests/committing-changes-to-your-project/viewing-and-comparing-commits/index.md
@@ -10,7 +10,6 @@ versions:
ghae: '*'
ghec: '*'
children:
- - /commit-branch-and-tag-labels
- /comparing-commits
- /differences-between-commit-views
shortTitle: View & compare commits
diff --git a/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/enabling-or-disabling-github-discussions-for-a-repository.md b/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/enabling-or-disabling-github-discussions-for-a-repository.md
index 7bb666ab9ea0..fc646f88f3a3 100644
--- a/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/enabling-or-disabling-github-discussions-for-a-repository.md
+++ b/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/enabling-or-disabling-github-discussions-for-a-repository.md
@@ -11,7 +11,7 @@ topics:
redirect_from:
- /github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository
- /github/administering-a-repository/managing-repository-settings/enabling-or-disabling-github-discussions-for-a-repository
-shortTitle: ディスカッション
+shortTitle: Discussions
---
## Enabling or disabling {% data variables.product.prodname_discussions %} for your repository
diff --git a/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md b/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md
index b978d9f1caf5..110714ced4de 100644
--- a/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md
+++ b/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md
@@ -24,11 +24,11 @@ shortTitle: Manage GitHub Actions settings
## リポジトリの {% data variables.product.prodname_actions %} 権限について
-{% data reusables.github-actions.disabling-github-actions %} {% data variables.product.prodname_actions %} の詳細は、「[{% data variables.product.prodname_actions %}について](/actions/getting-started-with-github-actions/about-github-actions)」を参照してください。
+{% data reusables.actions.disabling-github-actions %} {% data variables.product.prodname_actions %} の詳細は、「[{% data variables.product.prodname_actions %}について](/actions/getting-started-with-github-actions/about-github-actions)」を参照してください。
-リポジトリで {% data variables.product.prodname_actions %} を有効化できます。 {% data reusables.github-actions.enabled-actions-description %} リポジトリの {% data variables.product.prodname_actions %} を完全に無効化することができます。 {% data reusables.github-actions.disabled-actions-description %}
+リポジトリで {% data variables.product.prodname_actions %} を有効化できます。 {% data reusables.actions.enabled-actions-description %} リポジトリの {% data variables.product.prodname_actions %} を完全に無効化することができます。 {% data reusables.actions.disabled-actions-description %}
-または、リポジトリで {% data variables.product.prodname_actions %} を有効化して、ワークフローで実行できるアクションを制限することもできます。 {% data reusables.github-actions.enabled-local-github-actions %}
+または、リポジトリで {% data variables.product.prodname_actions %} を有効化して、ワークフローで実行できるアクションを制限することもできます。 {% data reusables.actions.enabled-local-github-actions %}
## リポジトリの {% data variables.product.prodname_actions %} 権限を管理する
@@ -78,34 +78,34 @@ You can configure this behavior for a repository using the procedure below. Modi
{% data reusables.repositories.navigate-to-repo %}
{% data reusables.repositories.sidebar-settings %}
{% data reusables.repositories.settings-sidebar-actions %}
-{% data reusables.github-actions.workflows-from-public-fork-setting %}
+{% data reusables.actions.workflows-from-public-fork-setting %}
{% data reusables.actions.workflow-run-approve-link %}
{% endif %}
## プライベートリポジトリのフォークのワークフローを有効にする
-{% data reusables.github-actions.private-repository-forks-overview %}
+{% data reusables.actions.private-repository-forks-overview %}
If a policy is disabled for an {% ifversion ghec or ghae or ghes %}enterprise or{% endif %} organization, it cannot be enabled for a repository.
-{% data reusables.github-actions.private-repository-forks-options %}
+{% data reusables.actions.private-repository-forks-options %}
### リポジトリのプライベートフォークポリシーを設定する
{% data reusables.repositories.navigate-to-repo %}
{% data reusables.repositories.sidebar-settings %}
{% data reusables.repositories.settings-sidebar-actions %}
-{% data reusables.github-actions.private-repository-forks-configure %}
+{% data reusables.actions.private-repository-forks-configure %}
{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
## Setting the permissions of the `GITHUB_TOKEN` for your repository
-{% data reusables.github-actions.workflow-permissions-intro %}
+{% data reusables.actions.workflow-permissions-intro %}
The default permissions can also be configured in the organization settings. If the more restricted default has been selected in the organization settings, the same option is auto-selected in your repository settings and the permissive option is disabled.
-{% data reusables.github-actions.workflow-permissions-modifying %}
+{% data reusables.actions.workflow-permissions-modifying %}
### デフォルトの`GITHUB_TOKEN`権限の設定
@@ -141,15 +141,15 @@ You can configure whether {% if internal-actions%}actions and {% endif %}workflo
## Configuring the retention period for {% data variables.product.prodname_actions %} artifacts and logs in your repository
-You can configure the retention period for {% data variables.product.prodname_actions %} artifacts and logs in your repository.
+リポジトリ内の {% data variables.product.prodname_actions %} アーティファクトとログの保持期間を設定できます。
{% data reusables.actions.about-artifact-log-retention %}
-You can also define a custom retention period for a specific artifact created by a workflow. For more information, see "[Setting the retention period for an artifact](/actions/managing-workflow-runs/removing-workflow-artifacts#setting-the-retention-period-for-an-artifact)."
+ワークフローによって作成された特定のアーティファクトのカスタム保存期間を定義することもできます。 詳しい情報については、「[アーティファクトの保持期間を設定する](/actions/managing-workflow-runs/removing-workflow-artifacts#setting-the-retention-period-for-an-artifact)」を参照してください。
## リポジトリの保持期間を設定する
{% data reusables.repositories.navigate-to-repo %}
{% data reusables.repositories.sidebar-settings %}
{% data reusables.repositories.settings-sidebar-actions %}
-{% data reusables.github-actions.change-retention-period-for-artifacts-logs %}
+{% data reusables.actions.change-retention-period-for-artifacts-logs %}
diff --git a/translations/ja-JP/content/rest/overview/index.md b/translations/ja-JP/content/rest/overview/index.md
index 4c0bc5fb16ec..0cb5b29e57e5 100644
--- a/translations/ja-JP/content/rest/overview/index.md
+++ b/translations/ja-JP/content/rest/overview/index.md
@@ -18,5 +18,6 @@ children:
- /libraries
- /openapi-description
- /endpoints-available-for-github-apps
+ - /permissions-required-for-github-apps
---
diff --git a/translations/ja-JP/content/rest/reference/permissions-required-for-github-apps.md b/translations/ja-JP/content/rest/overview/permissions-required-for-github-apps.md
similarity index 99%
rename from translations/ja-JP/content/rest/reference/permissions-required-for-github-apps.md
rename to translations/ja-JP/content/rest/overview/permissions-required-for-github-apps.md
index cc518b6b4d71..a3836540087b 100644
--- a/translations/ja-JP/content/rest/reference/permissions-required-for-github-apps.md
+++ b/translations/ja-JP/content/rest/overview/permissions-required-for-github-apps.md
@@ -3,6 +3,7 @@ title: GitHub Appに必要な権限
intro: '{% data variables.product.prodname_github_app %}互換の各エンドポイントについて、必要な権限を確認できます。'
redirect_from:
- /v3/apps/permissions
+ - /rest/reference/permissions-required-for-github-apps
versions:
fpt: '*'
ghes: '*'
diff --git a/translations/ja-JP/content/rest/reference/actions.md b/translations/ja-JP/content/rest/reference/actions.md
index 0e2a579170c8..51dad1afa298 100644
--- a/translations/ja-JP/content/rest/reference/actions.md
+++ b/translations/ja-JP/content/rest/reference/actions.md
@@ -13,93 +13,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-
-{% data variables.product.prodname_actions %} API では、REST API を使用して {% data variables.product.prodname_actions %} を管理できます。 {% data reusables.actions.actions-authentication %} {% data variables.product.prodname_github_apps %} require the permissions mentioned in each endpoint. 詳しい情報については、「[{% data variables.product.prodname_actions %} のドキュメント](/actions)」を参照してください。
-
-{% for operation in currentRestOperations %}
- {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
-{% endfor %}
-
-## 成果物
-
-成果物 API では、ワークフローの成果物に関する情報をダウンロード、削除、および取得できます。 {% data reusables.actions.about-artifacts %} 詳しい情報については、「[成果物を利用してワークフローのデータを永続化する](/actions/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)」を参照してください。
-
-{% data reusables.actions.actions-authentication %} {% data reusables.actions.actions-app-actions-permissions-api %}
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'artifacts' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% ifversion fpt or ghes > 2.22 or ghae or ghec %}
-## 権限
-
-The Permissions API allows you to set permissions for what enterprises, organizations, and repositories are allowed to run {% data variables.product.prodname_actions %}, and what actions are allowed to run.{% ifversion fpt or ghec or ghes %} For more information, see "[Usage limits, billing, and administration](/actions/reference/usage-limits-billing-and-administration#disabling-or-limiting-github-actions-for-your-repository-or-organization)."{% endif %}
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'permissions' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-{% endif %}
-
-## シークレット
-
-シークレット API では、暗号化されたシークレットに関する情報を作成、更新、削除、および取得できます。 {% data reusables.actions.about-secrets %} 詳しい情報については、「[暗号化されたシークレットの作成と利用](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)」を参照してください。
-
-{% data reusables.actions.actions-authentication %} {% data variables.product.prodname_github_apps %} must have the `secrets` permission to use this API. 認証されたユーザは、シークレットを作成、更新、または読み取るために、リポジトリへのコラボレータアクセス権を持っている必要があります。
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'secrets' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## セルフホストランナー
-
-{% data reusables.actions.ae-self-hosted-runners-notice %}
-
-セルフホストランナー API では、自分のホストランナーの登録、表示、削除ができます。 {% data reusables.actions.about-self-hosted-runners %} 詳しい情報については「[自分のランナーのホスト](/actions/hosting-your-own-runners)」を参照してください。
-
-{% data reusables.actions.actions-authentication %} {% data variables.product.prodname_github_apps %} must have the `administration` permission for repositories the `organization_self_hosted_runners` permission for organizations. Authenticated users must have admin access to repositories or organizations, or the `manage_runners:enterprise` scope for enterprises to use this API.
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'self-hosted-runners' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## セルフホストランナーグループ
-
-{% data reusables.actions.ae-self-hosted-runners-notice %}
-
-セルフホストランナーグループ API を使用すると、セルフホストランナーのグループを管理できます。 詳しい情報については、「[グループを使用したセルフホストランナーへのアクセスを管理する](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups)」を参照してください。
-
-{% data reusables.actions.actions-authentication %} {% data variables.product.prodname_github_apps %} must have the `administration` permission for repositories or the `organization_self_hosted_runners` permission for organizations. Authenticated users must have admin access to repositories or organizations, or the `manage_runners:enterprise` scope for enterprises to use this API.
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'self-hosted-runner-groups' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## ワークフロー
-
-ワークフロー API を使用すると、リポジトリのワークフローを表示できます。 {% data reusables.actions.about-workflows %}詳しい情報については、「[GitHub Actions でワークフローを自動化する](/actions/automating-your-workflow-with-github-actions)」を参照してください。
-
-{% data reusables.actions.actions-authentication %} {% data reusables.actions.actions-app-actions-permissions-api %}
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'workflows' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## ワークフロージョブ
-
-ワークフロージョブ API では、ログとワークフロージョブを表示できます。 {% data reusables.actions.about-workflow-jobs %}詳しい情報については、「[GitHub Actions のワークフロー構文](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions)」を参照してください。
-
-{% data reusables.actions.actions-authentication %} {% data reusables.actions.actions-app-actions-permissions-api %}
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'workflow-jobs' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## ワークフロー実行
-
-ワークフロー実行 API では、ワークフロー実行のログを表示、再実行、キャンセル、表示できます。 {% data reusables.actions.about-workflow-runs %}詳しい情報については、「[ワークフロー実行を管理する](/actions/automating-your-workflow-with-github-actions/managing-a-workflow-run)」を参照してください。
-
-{% data reusables.actions.actions-authentication %} {% data reusables.actions.actions-app-actions-permissions-api %}
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'workflow-runs' %}{% include rest_operation %}{% endif %}
-{% endfor %}
+
diff --git a/translations/ja-JP/content/rest/reference/activity.md b/translations/ja-JP/content/rest/reference/activity.md
index 804b4094d240..35d9ca8aea79 100644
--- a/translations/ja-JP/content/rest/reference/activity.md
+++ b/translations/ja-JP/content/rest/reference/activity.md
@@ -1,5 +1,5 @@
---
-title: Activity
+title: アクティビティ
intro: 'The Activity API allows you to list events and feeds and manage notifications, starring, and watching for the authenticated user.'
redirect_from:
- /v3/activity
@@ -13,186 +13,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-{% for operation in currentRestOperations %}
- {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
-{% endfor %}
-
-## Events
-
-The Events API is a read-only API to the {% data variables.product.prodname_dotcom %} events. These events power the various activity streams on the site.
-
-The Events API can return different types of events triggered by activity on {% data variables.product.product_name %}. For more information about the specific events that you can receive from the Events API, see "[{% data variables.product.prodname_dotcom %} Event types](/developers/webhooks-and-events/github-event-types)." An events API for repository issues is also available. For more information, see the "[Issue Events API](/rest/reference/issues#events)."
-
-Events are optimized for polling with the "ETag" header. If no new events have been triggered, you will see a "304 Not Modified" response, and your current rate limit will be untouched. There is also an "X-Poll-Interval" header that specifies how often (in seconds) you are allowed to poll. In times of high server load, the time may increase. Please obey the header.
-
-``` shell
-$ curl -I {% data variables.product.api_url_pre %}/users/tater/events
-> HTTP/2 200
-> X-Poll-Interval: 60
-> ETag: "a18c3bded88eb5dbb5c849a489412bf3"
-
-# The quotes around the ETag value are important
-$ curl -I {% data variables.product.api_url_pre %}/users/tater/events \
-$ -H 'If-None-Match: "a18c3bded88eb5dbb5c849a489412bf3"'
-> HTTP/2 304
-> X-Poll-Interval: 60
-```
-
-Only events created within the past 90 days will be included in timelines. Events older than 90 days will not be included (even if the total number of events in the timeline is less than 300).
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'events' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## Feeds
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'feeds' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-### Example of getting an Atom feed
-
-To get a feed in Atom format, you must specify the `application/atom+xml` type in the `Accept` header. For example, to get the Atom feed for GitHub security advisories:
-
- curl -H "Accept: application/atom+xml" https://github.com/security-advisories
-
-#### Response
-
-```shell
-HTTP/2 200
-```
-
-```xml
-
-
- tag:github.com,2008:/security-advisories
-
- GitHub Security Advisory Feed
-
- GitHub
-
- 2019-01-14T19:34:52Z
-
- tag:github.com,2008:GHSA-abcd-12ab-23cd
- 2018-07-26T15:14:52Z
- 2019-01-14T19:34:52Z
- [GHSA-abcd-12ab-23cd] Moderate severity vulnerability that affects Octoapp
-
-
- <p>Octoapp node module before 4.17.5 suffers from a Modification of Assumed-Immutable Data (MAID) vulnerability via defaultsDeep, merge, and mergeWith functions, which allows a malicious user to modify the prototype of "Object" via <strong>proto</strong>, causing the addition or modification of an existing property that will exist on all objects.</p>
- <p><strong>Affected Packages</strong></p>
-
- <dl>
- <dt>Octoapp</dt>
- <dd>Ecosystem: npm</dd>
- <dd>Severity: moderate</dd>
- <dd>Versions: < 4.17.5</dd>
- <dd>Fixed in: 4.17.5</dd>
- </dl>
-
- <p><strong>References</strong></p>
-
- <ul>
- <li>https://nvd.nist.gov/vuln/detail/CVE-2018-123</li>
- </ul>
-
-
-
-
-```
-
-## Notifications
-
-Users receive notifications for conversations in repositories they watch including:
-
-* Issues and their comments
-* Pull Requests and their comments
-* Comments on any commits
-
-Notifications are also sent for conversations in unwatched repositories when the user is involved including:
-
-* **@mentions**
-* Issue assignments
-* Commits the user authors or commits
-* Any discussion in which the user actively participates
-
-All Notification API calls require the `notifications` or `repo` API scopes. Doing this will give read-only access to some issue and commit content. You will still need the `repo` scope to access issues and commits from their respective endpoints.
-
-Notifications come back as "threads". A thread contains information about the current discussion of an issue, pull request, or commit.
-
-Notifications are optimized for polling with the `Last-Modified` header. If there are no new notifications, you will see a `304 Not Modified` response, leaving your current rate limit untouched. There is an `X-Poll-Interval` header that specifies how often (in seconds) you are allowed to poll. In times of high server load, the time may increase. Please obey the header.
-
-``` shell
-# Add authentication to your requests
-$ curl -I {% data variables.product.api_url_pre %}/notifications
-HTTP/2 200
-Last-Modified: Thu, 25 Oct 2012 15:16:27 GMT
-X-Poll-Interval: 60
-
-# Pass the Last-Modified header exactly
-$ curl -I {% data variables.product.api_url_pre %}/notifications
-$ -H "If-Modified-Since: Thu, 25 Oct 2012 15:16:27 GMT"
-> HTTP/2 304
-> X-Poll-Interval: 60
-```
-
-### Notification reasons
-
-When retrieving responses from the Notifications API, each payload has a key titled `reason`. These correspond to events that trigger a notification.
-
-Here's a list of potential `reason`s for receiving a notification:
-
-Reason Name | Description
-------------|------------
-`assign` | You were assigned to the issue.
-`author` | You created the thread.
-`comment` | You commented on the thread.
-`ci_activity` | A {% data variables.product.prodname_actions %} workflow run that you triggered was completed.
-`invitation` | You accepted an invitation to contribute to the repository.
-`manual` | You subscribed to the thread (via an issue or pull request).
-`mention` | You were specifically **@mentioned** in the content.
-`review_requested` | You, or a team you're a member of, were requested to review a pull request.{% ifversion fpt or ghec %}
-`security_alert` | {% data variables.product.prodname_dotcom %} discovered a [security vulnerability](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies) in your repository.{% endif %}
-`state_change` | You changed the thread state (for example, closing an issue or merging a pull request).
-`subscribed` | You're watching the repository.
-`team_mention` | You were on a team that was mentioned.
-
-Note that the `reason` is modified on a per-thread basis, and can change, if the `reason` on a later notification is different.
-
-For example, if you are the author of an issue, subsequent notifications on that issue will have a `reason` of `author`. If you're then **@mentioned** on the same issue, the notifications you fetch thereafter will have a `reason` of `mention`. The `reason` remains as `mention`, regardless of whether you're ever mentioned again.
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'notifications' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## Starring
-
-Repository starring is a feature that lets users bookmark repositories. Stars are shown next to repositories to show an approximate level of interest. Stars have no effect on notifications or the activity feed.
-
-### Starring vs. Watching
-
-In August 2012, we [changed the way watching
-works](https://github.com/blog/1204-notifications-stars) on {% data variables.product.prodname_dotcom %}. Many API
-client applications may be using the original "watcher" endpoints for accessing
-this data. You can now start using the "star" endpoints instead (described
-below). For more information, see the [Watcher API Change post](https://developer.github.com/changes/2012-09-05-watcher-api/) and the "[Repository Watching API](/rest/reference/activity#watching)."
-
-### Custom media types for starring
-
-There is one supported custom media type for the Starring REST API. When you use this custom media type, you will receive a response with the `starred_at` timestamp property that indicates the time the star was created. The response also has a second property that includes the resource that is returned when the custom media type is not included. The property that contains the resource will be either `user` or `repo`.
-
- application/vnd.github.v3.star+json
-
-For more information about media types, see "[Custom media types](/rest/overview/media-types)."
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'starring' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## Watching
-
-Watching a repository registers the user to receive notifications on new discussions, as well as events in the user's activity feed. For simple repository bookmarks, see "[Repository starring](/rest/reference/activity#starring)."
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'watching' %}{% include rest_operation %}{% endif %}
-{% endfor %}
+
diff --git a/translations/ja-JP/content/rest/reference/apps.md b/translations/ja-JP/content/rest/reference/apps.md
index b8b59c93ad65..912673d56eef 100644
--- a/translations/ja-JP/content/rest/reference/apps.md
+++ b/translations/ja-JP/content/rest/reference/apps.md
@@ -13,66 +13,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-{% data reusables.apps.general-apps-restrictions %}
-
-このページには、GitHub App として認証されている場合にアクセスできるエンドポイントが一覧表示されています。 詳細については、「[GitHub App として認証する](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-a-github-app)」を参照してださい。
-
-GitHub App として認証されると、GitHub Apps API を使用して、GitHub App に関する大まかな情報と、アプリケーションのインストールに関する具体的な情報を取得できます。
-
-GitHub App として認証されている場合、REST API v3 エンドポイントにアクセスできます。 これらのエンドポイントには、「Works with GitHub Apps」という箇条書きを含む「注釈」セクションがあります。 ユーザとして認証されている場合、これらのエンドポイントにアクセスすることもできます。
-
-REST API v3 エンドポイントのサブセットでは、GitHub App のインストールとして認証する必要があります。 これらのエンドポイントの一覧については、[Installations](/rest/reference/apps#installations) を参照してください。
-
-{% for operation in currentRestOperations %}
- {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
-{% endfor %}
-
-## OAuth アプリケーション API
-
-You can use this API to manage the OAuth tokens an OAuth application uses to access people's accounts on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}.
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'oauth-applications' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## インストール
-
-Installations API を使用すると、GitHub App のインストールに関する情報を取得して、それらのインストール内でアクションを実行できます。 _インストール_とは、アプリケーションをインストールしたユーザまたは Organization のアカウントを指します。 インストレーションとして認証し、特定のリポジトリへのアクセスを制限する方法については、「[インストレーションとして認証する](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation)」を参照してください。
-
-Organization のすべての GitHub App インストレーションを一覧表示するには、「[Organization のアプリケーションインストールの一覧表示](/rest/reference/orgs#list-app-installations-for-an-organization)」を参照してください。
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'installations' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% ifversion fpt or ghec %}
-## Marketplace
-
-{% data variables.product.prodname_marketplace %} の詳細については、「[GitHub Marketplace](/marketplace/)」を参照してください。
-
-{% data variables.product.prodname_marketplace %} API では、価格プランを使用している顧客の確認、顧客の購入の確認、アカウントで有効になっているプランの有無を確認できます。
-
-### スタブされたエンドポイントでテストする
-
-この API には、[**スタブされたデータ**で {% data variables.product.prodname_github_app %} をテスト](/marketplace/integrating-with-the-github-marketplace-api/testing-github-marketplace-apps/)できるエンドポイントが含まれています。 スタブされたデータはハードコードされた偽のデータであり、実際のプランに基づいて変更されることはありません。
-
-スタブされたデータでテストするには、対応する本番環境の代わりにスタブされたエンドポイントを使用します。 This allows you to test whether API logic succeeds before listing {% data variables.product.prodname_github_apps %} on {% data variables.product.prodname_marketplace %}.
-
-{% data variables.product.prodname_github_app %} をデプロイする前に、スタブされたエンドポイントを本番のエンドポイントに置き換えてください。
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'marketplace' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% endif %}
-
-{% ifversion fpt or ghes > 2.22 or ghae or ghec %}
-## webhook
-
-A {% data variables.product.prodname_github_app %}'s webhook allows you to receive HTTP `POST` payloads whenever certain events happen for an app. {% data reusables.webhooks.webhooks-rest-api-links %}
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'webhooks' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% endif %}
+
diff --git a/translations/ja-JP/content/rest/reference/billing.md b/translations/ja-JP/content/rest/reference/billing.md
index bae79da6e320..43e193a099d7 100644
--- a/translations/ja-JP/content/rest/reference/billing.md
+++ b/translations/ja-JP/content/rest/reference/billing.md
@@ -10,8 +10,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-Enterprise の支払情報を取得できます。 詳しい情報については、「[{% data variables.product.prodname_dotcom %} Enterprise 管理](/rest/reference/enterprise-admin#billing)」REST API を参照してください。
-
-{% for operation in currentRestOperations %}
- {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
-{% endfor %}
+
diff --git a/translations/ja-JP/content/rest/reference/branches.md b/translations/ja-JP/content/rest/reference/branches.md
index 2cf2986d3fcc..3495232f521f 100644
--- a/translations/ja-JP/content/rest/reference/branches.md
+++ b/translations/ja-JP/content/rest/reference/branches.md
@@ -12,11 +12,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-{% for operation in currentRestOperations %}
- {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
-{% endfor %}
-
-## 保護されたブランチ
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'branch-protection' %}{% include rest_operation %}{% endif %}
-{% endfor %}
+
diff --git a/translations/ja-JP/content/rest/reference/checks.md b/translations/ja-JP/content/rest/reference/checks.md
index ff71ceb016bd..ea7158337005 100644
--- a/translations/ja-JP/content/rest/reference/checks.md
+++ b/translations/ja-JP/content/rest/reference/checks.md
@@ -13,26 +13,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-継続的インテグレーション、コードの構文チェック、コードのスキャンサービスを実行し、コミットについて詳細なフィードバックを行うアプリを作成できます。 詳しい情報については、「[Checks API を使ってみる](/rest/guides/getting-started-with-the-checks-api)」および「[Checks API で CI テストを作成する](/apps/quickstart-guides/creating-ci-tests-with-the-checks-api/)」を参照してください。
-
-{% for operation in currentRestOperations %}
- {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
-{% endfor %}
-
-## チェックラン
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'runs' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## チェックスイート
-
-{% note %}
-
- **注釈:** コミット SHA を複数のブランチにプッシュした場合でも、GitHub App はコミット SHA ごとに 1 つの [`check_suite`](/webhooks/event-payloads/#check_suite) イベントのみを受け取ります。 ブランチ [`create`](/webhooks/event-payloads/#create) イベントをサブスクライブして、コミット SHA がブランチにプッシュされたタイミングを確認することができます。
-
-{% endnote %}
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'suites' %}{% include rest_operation %}{% endif %}
-{% endfor %}
+
diff --git a/translations/ja-JP/content/rest/reference/code-scanning.md b/translations/ja-JP/content/rest/reference/code-scanning.md
index e7c881c21a49..f10dc933ac04 100644
--- a/translations/ja-JP/content/rest/reference/code-scanning.md
+++ b/translations/ja-JP/content/rest/reference/code-scanning.md
@@ -17,20 +17,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-{% data reusables.code-scanning.beta %}
-
-{% data variables.product.prodname_code_scanning %} APIを使うと、リオジトリから{% data variables.product.prodname_code_scanning %}アラートを取得して更新できます。 このエンドポイントを使って、Organization内で{% data variables.product.prodname_code_scanning %}アラートの自動化されたレポートを作成したり、オフラインの{% data variables.product.prodname_code_scanning %}ツールを使って生成された分析結果をアップロードしたりできます。 詳しい情報については、「[コード内のセキュリティの脆弱性とエラーを検出する](/github/finding-security-vulnerabilities-and-errors-in-your-code)」を参照してください。
-
-{% ifversion fpt or ghes > 3.0 or ghae or ghec %}
-### {% data variables.product.prodname_code_scanning %}のためのカスタムメディアタイプ
-
-{% data variables.product.prodname_code_scanning %} REST API用にサポートされているカスタムメディアタイプが1つあります。
-
- application/sarif+json
-
-これは`/analyses/{analysis_id}`エンドポイントに送信される`GET`リクエストで利用できます。 この操作に関する詳しい情報については「[リポジトリの{% data variables.product.prodname_code_scanning %}分析の取得](#get-a-code-scanning-analysis-for-a-repository)」を参照してください。 この操作でこのメディアタイプを使う場合、レスポンスには指定された分析のまとめではなく、その分析のためにアップロードされた実際のデータのサブセットが含まれます。分析のまとめは、デフォルトのメディアタイプを使った場合に返されます。 このレスポンスには、`github/alertNumber`や`github/alertUrl`プロパティなどの追加データも含まれます。 このデータは、[SARIF version 2.1.0](https://docs.oasis-open.org/sarif/sarif/v2.1.0/cs01/sarif-v2.1.0-cs01.html)でフォーマットされます。
-
-詳しい情報については、「[メディアタイプ](/rest/overview/media-types)」を参照してください。
-{% endif %}
-
-{% include rest_operations_at_current_path %}
+
diff --git a/translations/ja-JP/content/rest/reference/codes-of-conduct.md b/translations/ja-JP/content/rest/reference/codes-of-conduct.md
index 8b44036bee59..9b1714546c57 100644
--- a/translations/ja-JP/content/rest/reference/codes-of-conduct.md
+++ b/translations/ja-JP/content/rest/reference/codes-of-conduct.md
@@ -14,6 +14,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-Codes of Conduct API を使用して、リポジトリの行動規範に関する情報を取得できます。 リポジトリの行動規範を取得するには、「[Get a repository](/rest/reference/repos#get-a-repository)」エンドポイントを使用します。
-
-{% include rest_operations_at_current_path %}
+
diff --git a/translations/ja-JP/content/rest/reference/codespaces.md b/translations/ja-JP/content/rest/reference/codespaces.md
index 8c8c8fdff267..11f28ca6432e 100644
--- a/translations/ja-JP/content/rest/reference/codespaces.md
+++ b/translations/ja-JP/content/rest/reference/codespaces.md
@@ -10,24 +10,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-{% data reusables.codespaces.codespaces-api-beta-note %}
-
-{% data variables.product.prodname_codespaces %} API では、REST API を使用して {% data variables.product.prodname_codespaces %} を管理できます。 This API is available for authenticated users and OAuth Apps, but not GitHub Apps. 詳細は「[{% data variables.product.prodname_codespaces %}](/codespaces)」を参照してください。
-
-{% for operation in currentRestOperations %}
- {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
-{% endfor %}
-
-## Machines
-The Machines API allows a user to determine which machine types are available to create a codespace, either on a given repository or as an authenticated user. For more information, see "[About machine types](/codespaces/developing-in-codespaces/changing-the-machine-type-for-your-codespace#about-machine-types)."
-
-You can also use this information when changing the machine of an existing codespace by updating its `machine` property. The machine update will take place the next time the codespace is restarted. For more information, see "[Changing the machine type for your codespace](/codespaces/developing-in-codespaces/changing-the-machine-type-for-your-codespace)."
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'machines' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## シークレット
-The Secrets API allows a user to create, list, and delete secrets (such as access tokens for cloud services) as well as assign secrets to repositories that the user has access to. These secrets are made available to the codespace at runtime. For more information, see "[Managing encrypted secrets for your codespaces](/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces)."
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'secrets' %}{% include rest_operation %}{% endif %}
-{% endfor %}
+
\ No newline at end of file
diff --git a/translations/ja-JP/content/rest/reference/collaborators.md b/translations/ja-JP/content/rest/reference/collaborators.md
index 62682a1d1577..f53b35d2c867 100644
--- a/translations/ja-JP/content/rest/reference/collaborators.md
+++ b/translations/ja-JP/content/rest/reference/collaborators.md
@@ -12,20 +12,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-{% for operation in currentRestOperations %}
- {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
-{% endfor %}
-
-## 招待
-
-Repository Invitations API を使用すると、他のユーザにリポジトリでコラボレーションするようユーザや外部サービスを招待できます。 招待されたユーザ (または招待されたユーザを代行する外部サービス) は、招待を受諾または拒否できます。
-
-`repo` スコープはコードにも招待にもアクセス権を付与するのに対し、`repo:invite` [OAuth scope](/developers/apps/scopes-for-oauth-apps) は招待のみに絞ってアクセス権を付与し、リポジトリのコードにはアクセス権を付与**しない**ことに注意してください。
-
-### ユーザをリポジトリに招待する
-
-コラボレータを追加するには、API エンドポイントを使用します。 詳しい情報については「[リポジトリコラボレータを追加する](/rest/reference/collaborators#add-a-repository-collaborator)」を参照してください。
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'invitations' %}{% include rest_operation %}{% endif %}
-{% endfor %}
+
diff --git a/translations/ja-JP/content/rest/reference/commits.md b/translations/ja-JP/content/rest/reference/commits.md
index f0c9c20ebbd8..72a860a96e04 100644
--- a/translations/ja-JP/content/rest/reference/commits.md
+++ b/translations/ja-JP/content/rest/reference/commits.md
@@ -12,41 +12,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-{% for operation in currentRestOperations %}
- {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
-{% endfor %}
-
-## コミットのコメント
-
-### コミットコメントのカスタムメディアタイプ
-
-以下がコミットコメントでサポートされているメディアタイプです。 API におけるメディアタイプの使用に関する詳細は、[こちら](/rest/overview/media-types)を参照してください。
-
- application/vnd.github-commitcomment.raw+json
- application/vnd.github-commitcomment.text+json
- application/vnd.github-commitcomment.html+json
- application/vnd.github-commitcomment.full+json
-
-詳しい情報については、「[カスタムメディアタイプ](/rest/overview/media-types)」を参照してください。
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'comments' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## コミットのステータス
-
-ステータス API を使用すると、外部サービスがコミットに `error`、 `failure`、`pending`、`success` ステータスを付けることができ、このステータスはコミットが含まれるプルリクエストに反映されます。
-
-ステータスには、オプションとして `description` と `target_url` を含めることもできます。これにより GitHub UI でステータスをより有用なものにできるので、非常におすすめです。
-
-たとえば、継続的インテグレーションサービスの典型的な使用方法の一つが、ステータスを使用してコミットに合格と不合格の印を付けることです。 `target_url` でビルドの出力先の完全な URL、`description` でビルドで発生したことの概要を示すといったようにします。
-
-ステータスには、どのサービスがそのステータスを提供しているかを示す `context` を含めることができます。 たとえば、継続的インテグレーションサービスのプッシュステータスに `ci` のコンテキストを、セキュリティ監査ツールのプッシュステータスに `security` のコンテキストを含めることができます。 その後、[特定のリファレンス複合的なステータス](/rest/reference/commits#get-the-combined-status-for-a-specific-reference)を使用して、コミットの全体のステータスを取得できます。
-
-`repo` スコープはコードにもステータスにもアクセス権を付与するのに対し、`repo:status` [OAuth scope](/developers/apps/scopes-for-oauth-apps) はステータスのみに絞ってアクセス権を付与し、リポジトリのコードにはアクセス権を付与**しない**ことに注意してください。
-
-GitHub App を開発していて、外部サービスについて詳細な情報を提供したい場合は、[Checks API](/rest/reference/checks) を使用できます。
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'statuses' %}{% include rest_operation %}{% endif %}
-{% endfor %}
+
diff --git a/translations/ja-JP/content/rest/reference/dependabot.md b/translations/ja-JP/content/rest/reference/dependabot.md
index db6403de0b63..5fe2940b7c99 100644
--- a/translations/ja-JP/content/rest/reference/dependabot.md
+++ b/translations/ja-JP/content/rest/reference/dependabot.md
@@ -10,10 +10,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-The {% data variables.product.prodname_dependabot %} Secrets API lets you create, update, delete, and retrieve information about encrypted secrets. {% data reusables.actions.about-secrets %} For more information, see "[Managing encrypted secrets for Dependabot](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-encrypted-secrets-for-dependabot)."
-
-{% data reusables.actions.actions-authentication %} {% data variables.product.prodname_github_apps %} must have the `dependabot_secrets` permission to use this API. 認証されたユーザは、シークレットを作成、更新、または読み取るために、リポジトリへのコラボレータアクセス権を持っている必要があります。
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'secrets' %}{% include rest_operation %}{% endif %}
-{% endfor %}
+
\ No newline at end of file
diff --git a/translations/ja-JP/content/rest/reference/deployments.md b/translations/ja-JP/content/rest/reference/deployments.md
index 69220a0cda72..fb24aca58915 100644
--- a/translations/ja-JP/content/rest/reference/deployments.md
+++ b/translations/ja-JP/content/rest/reference/deployments.md
@@ -12,81 +12,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-デプロイメントとは、特定の ref (ブランチ、SHA、タグ) を配備するためるリクエストです。 GitHub は、 外部サーバーがリッスンでき、新しいデプロイメントが作成されたときに実行される [`deployment` イベント](/developers/webhooks-and-events/webhook-events-and-payloads#deployment)をディスバッチします。 デプロイメントにより、開発者や Organization はデプロイメントを中心として、さまざまな種類のアプリケーション (ウェブ、ネイティブなど) を提供するための実装に関する詳細を気にすることなく、疎結合ツールを構築できます。
-
-デプロイメントのステータスを使用すると、外部サービスがデプロイメントに `error`、`failure`、`pending`、`in_progress`、`queued`、`success` ステータスを付けることができ、[`deployment_status` イベント](/developers/webhooks-and-events/webhook-events-and-payloads#deployment_status)をリッスンするシステムがその情報を使用できます。
-
-デプロイメントのステータスには、オプションとして `description` と `log_url` を含めることもできます。これによりデプロイメントのステータスがより有用なものになるので、非常におすすめです。 `log_url` はデプロイメントの出力の完全な URL で、`description` はデプロイメントで発生したことの概要を示すものです。
-
-GitHub は、新しいデプロイメント、デプロイメントのステータスが作成されたときに、`deployment` イベント、`deployment_status` イベントをディスパッチします。 これらのイベントにより、サードパーティのインテグレーションがデプロイメントのリクエストに対する応答を受けとり、進展があるたびにステータスを更新できます。
-
-以下は、これらの相互作用がどのように機能するかを示す簡単なシーケンス図です。
-
-```
-+---------+ +--------+ +-----------+ +-------------+
-| Tooling | | GitHub | | 3rd Party | | Your Server |
-+---------+ +--------+ +-----------+ +-------------+
- | | | |
- | Create Deployment | | |
- |--------------------->| | |
- | | | |
- | Deployment Created | | |
- |<---------------------| | |
- | | | |
- | | Deployment Event | |
- | |---------------------->| |
- | | | SSH+Deploys |
- | | |-------------------->|
- | | | |
- | | Deployment Status | |
- | |<----------------------| |
- | | | |
- | | | Deploy Completed |
- | | |<--------------------|
- | | | |
- | | Deployment Status | |
- | |<----------------------| |
- | | | |
-```
-
-GitHub は、あなたのサーバーに実際にアクセスすることはないということは覚えておきましょう。 デプロイメントイベントとやり取りするかどうかは、サードパーティインテグレーション次第です。 複数のシステムがデプロイメントイベントをリッスンできます。コードをサーバーにプッシュする、ネイティブコードを構築するなどを行うかどうかは、それぞれのシステムが決めることができます。
-
-Note that the `repo_deployment` [OAuth scope](/developers/apps/scopes-for-oauth-apps) grants targeted access to deployments and deployment statuses **without** granting access to repository code, while the {% ifversion not ghae %}`public_repo` and{% endif %}`repo` scopes grant permission to code as well.
-
-### 非アクティブのデプロイメント
-
-When you set the state of a deployment to `success`, then all prior non-transient, non-production environment deployments in the same repository with the same environment name will become `inactive`. これを回避するには、デプロイメントのステータスを作成する前に、`auto_inactive` を `false` に設定します。
-
-`state` を `inactive` に設定することで、一時的な環境が存在しなくなったことを伝えることができます。 `state` を `inactive` に設定すると、{% data variables.product.prodname_dotcom %} でデプロイメントが `destroyed` と表示され、アクセス権が削除されます。
-
-{% for operation in currentRestOperations %}
- {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
-{% endfor %}
-
-## デプロイメントステータス
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'statuses' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## デプロイキー
-
-{% data reusables.repositories.deploy-keys %}
-
-デプロイキーは、以下の API エンドポイントを使用するか、GitHub を使用することでセットアップできます。 GitHub でデプロイキーを設定する方法については、「[デプロイキーを管理する](/developers/overview/managing-deploy-keys)」を参照してください。
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'keys' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
-## 環境
-
-Environments APIを使うと、環境を作成、設定、削除できます。 For more information about environments, see "[Using environments for deployment](/actions/deployment/using-environments-for-deployment)." 環境のシークレットの管理については「[シークレット](/rest/reference/actions#secrets)」を参照してください。
-
-{% data reusables.gated-features.environments %}
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'environments' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-{% endif %}
+
diff --git a/translations/ja-JP/content/rest/reference/emojis.md b/translations/ja-JP/content/rest/reference/emojis.md
index 95d1a7393bb9..7c9155c1571a 100644
--- a/translations/ja-JP/content/rest/reference/emojis.md
+++ b/translations/ja-JP/content/rest/reference/emojis.md
@@ -14,4 +14,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-{% include rest_operations_at_current_path %}
+
diff --git a/translations/ja-JP/content/rest/reference/enterprise-admin.md b/translations/ja-JP/content/rest/reference/enterprise-admin.md
index 303f997677e8..c1f2d237c5fd 100644
--- a/translations/ja-JP/content/rest/reference/enterprise-admin.md
+++ b/translations/ja-JP/content/rest/reference/enterprise-admin.md
@@ -16,309 +16,6 @@ miniTocMaxHeadingLevel: 3
shortTitle: Enterprise administration
---
-{% ifversion fpt or ghec %}
-
-{% note %}
-
-**Note:** This article applies to {% data variables.product.prodname_ghe_cloud %}. To see the {% data variables.product.prodname_ghe_managed %} or {% data variables.product.prodname_ghe_server %} version, use the **{% data ui.pages.article_version %}** drop-down menu.
-
-{% endnote %}
-
-{% endif %}
-
-### Endpoint URLs
-
-REST API endpoints{% ifversion ghes %}—except [Management Console](#management-console) API endpoints—{% endif %} are prefixed with the following URL:
-
-```shell
-{% data variables.product.api_url_pre %}
-```
-
-{% ifversion fpt or ghec %}
-When endpoints include `{enterprise}`, replace `{enterprise}` with the handle for your enterprise account, which is included in the URL for your enterprise settings. For example, if your enterprise account is located at `https://github.com/enterprises/octo-enterprise`, replace `{enterprise}` with `octo-enterprise`.
-{% endif %}
-
-{% ifversion ghes %}
-[Management Console](#management-console) API endpoints are only prefixed with a hostname:
-
-```shell
-http(s)://hostname/
-```
-{% endif %}
-{% ifversion ghae or ghes %}
-### Authentication
-
-Your {% data variables.product.product_name %} installation's API endpoints accept [the same authentication methods](/rest/overview/resources-in-the-rest-api#authentication) as the GitHub.com API. You can authenticate yourself with **[OAuth tokens](/apps/building-integrations/setting-up-and-registering-oauth-apps/)** {% ifversion ghes %}(which can be created using the [Authorizations API](/rest/reference/oauth-authorizations#create-a-new-authorization)) {% endif %}or **[basic authentication](/rest/overview/resources-in-the-rest-api#basic-authentication)**. {% ifversion ghes %}
-OAuth tokens must have the `site_admin` [OAuth scope](/developers/apps/scopes-for-oauth-apps#available-scopes) when used with Enterprise-specific endpoints.{% endif %}
-
-Enterprise administration API endpoints are only accessible to authenticated {% data variables.product.product_name %} site administrators{% ifversion ghes %}, except for the [Management Console](#management-console) API, which requires the [Management Console password](/enterprise/admin/articles/accessing-the-management-console/){% endif %}.
-
-{% endif %}
-
-{% ifversion ghae or ghes %}
-### Version information
-
-The current version of your enterprise is returned in the response header of every API:
-`X-GitHub-Enterprise-Version: {{currentVersion}}.0`
-You can also read the current version by calling the [meta endpoint](/rest/reference/meta/).
-
-{% for operation in currentRestOperations %}
- {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
-{% endfor %}
-
-{% endif %}
-
-{% ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5528 %}
-
-## Audit log
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'audit-log' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% endif %}
-
-{% ifversion fpt or ghec or ghes > 3.3 %}
-## Billing
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'billing' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% endif %}
-
-{% ifversion ghae or ghes %}
-## Admin stats
-
-The Admin Stats API provides a variety of metrics about your installation. *It is only available to [authenticated](/rest/overview/resources-in-the-rest-api#authentication) site administrators.* Normal users will receive a `404` response if they try to access it.
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'admin-stats' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% endif %}
-
-{% ifversion ghae or ghes > 2.22 %}
-
-## Announcements
-
-The Announcements API allows you to manage the global announcement banner in your enterprise. For more information, see "[Customizing user messages for your enterprise](/admin/user-management/customizing-user-messages-for-your-enterprise#creating-a-global-announcement-banner)."
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'announcement' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% endif %}
-
-{% ifversion ghae or ghes %}
-
-## Global webhooks
-
-Global webhooks are installed on your enterprise. You can use global webhooks to automatically monitor, respond to, or enforce rules for users, organizations, teams, and repositories on your enterprise. Global webhooks can subscribe to the [organization](/developers/webhooks-and-events/webhook-events-and-payloads#organization), [user](/developers/webhooks-and-events/webhook-events-and-payloads#user), [repository](/developers/webhooks-and-events/webhook-events-and-payloads#repository), [team](/developers/webhooks-and-events/webhook-events-and-payloads#team), [member](/developers/webhooks-and-events/webhook-events-and-payloads#member), [membership](/developers/webhooks-and-events/webhook-events-and-payloads#membership), [fork](/developers/webhooks-and-events/webhook-events-and-payloads#fork), and [ping](/developers/webhooks-and-events/about-webhooks#ping-event) event types.
-
-*This API is only available to [authenticated](/rest/overview/resources-in-the-rest-api#authentication) site administrators.* Normal users will receive a `404` response if they try to access it. To learn how to configure global webhooks, see [About global webhooks](/enterprise/admin/user-management/about-global-webhooks).
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'global-webhooks' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% endif %}
-
-{% ifversion ghes %}
-
-## LDAP
-
-You can use the LDAP API to update account relationships between a {% data variables.product.product_name %} user or team and its linked LDAP entry or queue a new synchronization.
-
-With the LDAP mapping endpoints, you're able to update the Distinguished Name (DN) that a user or team maps to. Note that the LDAP endpoints are generally only effective if your {% data variables.product.product_name %} appliance has [LDAP Sync enabled](/enterprise/admin/authentication/using-ldap). The [Update LDAP mapping for a user](#update-ldap-mapping-for-a-user) endpoint can be used when LDAP is enabled, even if LDAP Sync is disabled.
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'ldap' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% endif %}
-
-{% ifversion ghae or ghes %}
-## License
-
-The License API provides information on your Enterprise license. *It is only available to [authenticated](/rest/overview/resources-in-the-rest-api#authentication) site administrators.* Normal users will receive a `404` response if they try to access it.
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'license' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% endif %}
-
-{% ifversion ghes %}
-
-## Management console
-
-The Management Console API helps you manage your {% data variables.product.product_name %} installation.
-
-{% tip %}
-
-You must explicitly set the port number when making API calls to the Management Console. If TLS is enabled on your enterprise, the port number is `8443`; otherwise, the port number is `8080`.
-
-If you don't want to provide a port number, you'll need to configure your tool to automatically follow redirects.
-
-You may also need to add the [`-k` flag](http://curl.haxx.se/docs/manpage.html#-k) when using `curl`, since {% data variables.product.product_name %} uses a self-signed certificate before you [add your own TLS certificate](/enterprise/admin/guides/installation/configuring-tls/).
-
-{% endtip %}
-
-### Authentication
-
-You need to pass your [Management Console password](/enterprise/admin/articles/accessing-the-management-console/) as an authentication token to every Management Console API endpoint except [`/setup/api/start`](#create-a-github-enterprise-server-license).
-
-Use the `api_key` parameter to send this token with each request. For example:
-
-```shell
-$ curl -L 'https://hostname:admin_port/setup/api?api_key=your-amazing-password'
-```
-
-You can also use standard HTTP authentication to send this token. For example:
-
-```shell
-$ curl -L -u "api_key:your-amazing-password" 'https://hostname:admin_port/setup/api'
-```
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'management-console' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% endif %}
-
-{% ifversion ghae or ghes %}
-## Organizations
-
-The Organization Administration API allows you to create organizations on your enterprise. *It is only available to [authenticated](/rest/overview/resources-in-the-rest-api#authentication) site administrators.* Normal users will receive a `404` response if they try to access it.
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'orgs' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% endif %}
-
-{% ifversion ghes %}
-## Organization pre-receive hooks
-
-The Organization Pre-receive Hooks API allows you to view and modify
-enforcement of the pre-receive hooks that are available to an organization.
-
-### Object attributes
-
-| Name | Type | Description |
-|----------------------------------|-----------|-----------------------------------------------------------|
-| `name` | `string` | The name of the hook. |
-| `enforcement` | `string` | The state of enforcement for the hook on this repository. |
-| `allow_downstream_configuration` | `boolean` | Whether repositories can override enforcement. |
-| `configuration_url` | `string` | URL for the endpoint where enforcement is set. |
-
-Possible values for *enforcement* are `enabled`, `disabled` and`testing`. `disabled` indicates the pre-receive hook will not run. `enabled` indicates it will run and reject
-any pushes that result in a non-zero status. `testing` means the script will run but will not cause any pushes to be rejected.
-
-`configuration_url` may be a link to this endpoint or this hook's global
-configuration. Only site admins are able to access the global configuration.
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'org-pre-receive-hooks' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% endif %}
-
-{% ifversion ghes %}
-
-## Pre-receive environments
-
-The Pre-receive Environments API allows you to create, list, update and delete environments for pre-receive hooks. *It is only available to [authenticated](/rest/overview/resources-in-the-rest-api#authentication) site administrators.* Normal users will receive a `404` response if they try to access it.
-
-### Object attributes
-
-#### Pre-receive Environment
-
-| Name | Type | Description |
-|-----------------------|-----------|----------------------------------------------------------------------------|
-| `name` | `string` | The name of the environment as displayed in the UI. |
-| `image_url` | `string` | URL to the tarball that will be downloaded and extracted. |
-| `default_environment` | `boolean` | Whether this is the default environment that ships with {% data variables.product.product_name %}. |
-| `download` | `object` | This environment's download status. |
-| `hooks_count` | `integer` | The number of pre-receive hooks that use this environment. |
-
-#### Pre-receive Environment Download
-
-| Name | Type | Description |
-|-----------------|----------|---------------------------------------------------------|
-| `state` | `string` | The state of the most recent download. |
-| `downloaded_at` | `string` | The time when the most recent download started. |
-| `message` | `string` | On failure, this will have any error messages produced. |
-
-Possible values for `state` are `not_started`, `in_progress`, `success`, `failed`.
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'pre-receive-environments' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% endif %}
-
-{% ifversion ghes %}
-## Pre-receive hooks
-
-The Pre-receive Hooks API allows you to create, list, update and delete pre-receive hooks. *It is only available to
-[authenticated](/rest/overview/resources-in-the-rest-api#authentication) site administrators.* Normal users will receive a `404` response if they try to access it.
-
-### Object attributes
-
-#### Pre-receive Hook
-
-| Name | Type | Description |
-|----------------------------------|-----------|-----------------------------------------------------------------|
-| `name` | `string` | The name of the hook. |
-| `script` | `string` | The script that the hook runs. |
-| `script_repository` | `object` | The GitHub repository where the script is kept. |
-| `environment` | `object` | The pre-receive environment where the script is executed. |
-| `enforcement` | `string` | The state of enforcement for this hook. |
-| `allow_downstream_configuration` | `boolean` | Whether enforcement can be overridden at the org or repo level. |
-
-Possible values for *enforcement* are `enabled`, `disabled` and`testing`. `disabled` indicates the pre-receive hook will not run. `enabled` indicates it will run and reject
-any pushes that result in a non-zero status. `testing` means the script will run but will not cause any pushes to be rejected.
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'pre-receive-hooks' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% endif %}
-
-{% ifversion ghes %}
-
-## Repository pre-receive hooks
-
-The Repository Pre-receive Hooks API allows you to view and modify
-enforcement of the pre-receive hooks that are available to a repository.
-
-### Object attributes
-
-| Name | Type | Description |
-|---------------------|----------|-----------------------------------------------------------|
-| `name` | `string` | The name of the hook. |
-| `enforcement` | `string` | The state of enforcement for the hook on this repository. |
-| `configuration_url` | `string` | URL for the endpoint where enforcement is set. |
-
-Possible values for *enforcement* are `enabled`, `disabled` and`testing`. `disabled` indicates the pre-receive hook will not run. `enabled` indicates it will run and reject any pushes that result in a non-zero status. `testing` means the script will run but will not cause any pushes to be rejected.
-
-`configuration_url` may be a link to this repository, it's organization owner or global configuration. Authorization to access the endpoint at `configuration_url` is determined at the owner or site admin level.
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'repo-pre-receive-hooks' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% endif %}
-
-{% ifversion ghae or ghes %}
-## Users
-
-The User Administration API allows you to suspend{% ifversion ghes %}, unsuspend, promote, and demote{% endif %}{% ifversion ghae %} and unsuspend{% endif %} users on your enterprise. *It is only available to [authenticated](/rest/overview/resources-in-the-rest-api#authentication) site administrators.* Normal users will receive a `403` response if they try to access it.
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'users' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% endif %}
+
\ No newline at end of file
diff --git a/translations/ja-JP/content/rest/reference/gists.md b/translations/ja-JP/content/rest/reference/gists.md
index 57c18000aad3..c9a59dd8d069 100644
--- a/translations/ja-JP/content/rest/reference/gists.md
+++ b/translations/ja-JP/content/rest/reference/gists.md
@@ -13,44 +13,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-### 認証
-
-パブリック Gist {% ifversion ghae or ghes %} を読んで、トークンなしで匿名ユーザ向けに作成できます。{% else %} 匿名でも、Gist を作成するには GitHub にサインインする必要があります。{% endif %}ユーザに代わって Gist を読み書きするには、Gist OAuth スコープとトークンが必要です。 詳しい情報については、「[OAuth App のスコープ](/developers/apps/scopes-for-oauth-apps)」を参照してください。
-
-
-
-### 切り捨て
-
-Gist API は、Gist 内の各ファイルに最大 1 メガバイトのコンテンツを提供します。 API を介して Gist として返される各ファイルには、`truncated` というキーがあります。 `truncated` が `true` の場合、ファイルが大きすぎるためコンテンツの一部のみが `content` で返されました。
-
-ファイルのフルコンテンツが必要な場合は、`raw_url` で指定された URL に `GET` リクエストを送信できます。 10 メガバイトを超えるファイルの場合、`git_pull_url` が提供する URL を介して Gist をクローンする必要があることに注意してください。
-
-ファイル総数が 300 個を超えると、特定のファイルの内容が切り捨てられることに加えて、ファイルリスト全体が切り捨てられる場合があります。 最上位の `truncated` キーが `true` の場合、最初の 300 ファイルのみがファイルリストに返されます。 Gist のファイルをすべてフェッチする必要がある場合は、`git_pull_url` が提供する URL を介して Gist のクローンを作成する必要があります。
-
-### Gist のカスタムメディアタイプ
-
-これらは、Gist コンテンツをフェッチするためにサポートされているメディアタイプです。
-
- application/vnd.github.VERSION.raw
- application/vnd.github.VERSION.base64
-
-詳しい情報については、「[メディアタイプ](/rest/overview/media-types)」を参照してください。
-
-{% for operation in currentRestOperations %}
- {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
-{% endfor %}
-
-## コメント
-
-### Gist コメントのカスタムメディアタイプ
-
-これらは、Gist コメントでサポートされているメディアタイプです。
-
- application/vnd.github.VERSION.raw
- application/vnd.github.VERSION.base64
-
-メディアタイプの詳しい情報については、「[カスタムメディアタイプ](/rest/overview/media-types)」を参照してください。
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'comments' %}{% include rest_operation %}{% endif %}
-{% endfor %}
+
diff --git a/translations/ja-JP/content/rest/reference/git.md b/translations/ja-JP/content/rest/reference/git.md
index 8bf59aa2bc72..0fa81d6eca03 100644
--- a/translations/ja-JP/content/rest/reference/git.md
+++ b/translations/ja-JP/content/rest/reference/git.md
@@ -14,57 +14,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-Git Database APIでは、{% data variables.product.product_name %}上のGitデータベースに対してRaw形式のGitオブジェクトを読み書きしたり、リファレンス (ブランチheadやタグ) をリストおよび更新したりすることができます。 Git Database API の使用方法の詳細については、「[Git データ API の概要](/rest/guides/getting-started-with-the-git-database-api)」を参照してください。
-
-{% for operation in currentRestOperations %}
- {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
-{% endfor %}
-
-## Blob
-
-Git blob (バイナリラージオブジェクト) は、各ファイルのコンテンツをリポジトリに保存する際に使用されるオブジェクトタイプです。 ファイルの SHA-1 ハッシュが計算され、blob オブジェクトに保存されます。 これらのエンドポイントを使用すると、{% data variables.product.product_name %} 上の Git データベースに対して [blob オブジェクト](https://git-scm.com/book/en/v1/Git-Internals-Git-Objects)の読み書きができます。 blob は[これらのカスタムメディアタイプ](#custom-media-types-for-blobs)を利用します。 API でのメディアタイプの使用について詳しくは、[こちら](/rest/overview/media-types)をご覧ください。
-
-### Blob のカスタムメディアタイプ
-
-これらは、blob でサポートされているメディアタイプです。
-
- application/json
- application/vnd.github.VERSION.raw
-
-詳しい情報については、「[メディアタイプ](/rest/overview/media-types)」を参照してください。
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'blobs' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## コミット
-
-Git コミットは、Git リポジトリ内の階層（[Git ツリー](/rest/reference/git#trees)）とファイルのコンテンツ（[Git blob](/rest/reference/git#blobs)）のスナップショットです。 これらのエンドポイントを使用すると、{% data variables.product.product_name %} 上の Git データベースに対して [コミットオブジェクト](https://git-scm.com/book/en/v1/Git-Internals-Git-Objects#Commit-Objects)の読み書きができます。
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'commits' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## リファレンス
-
-Git リファレンス（`git ref`）は、Git コミット SHA-1 ハッシュを含むファイルです。 Gitコミットを参照するときは、ハッシュではなく覚えやすい名前の Git リファレンスを使用できます。 Git リファレンスは、新しいコミットを指すように書き換えることができます。 ブランチは、新しい Git コミットハッシュを保存する Git リファレンスです。 これらのエンドポイントを使用すると、{% data variables.product.product_name %} 上の Git データベースに対して [リファレンス](https://git-scm.com/book/en/v1/Git-Internals-Git-References)の読み書きができます。
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'refs' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## タグ
-
-Git タグは [Git リファレンス](/rest/reference/git#refs)に似ていますが、変更しないことを指す Git コミットです。 Git タグは、特定のリリースを指すときに役立ちます。 これらのエンドポイントを使用すると、{% data variables.product.product_name %} 上の Git データベースに対して [タグオブジェクト](https://git-scm.com/book/en/v1/Git-Internals-Git-References#Tags)の読み書きができます。 Git タグ API は、[アノテーションされたタグオブジェクト](https://git-scm.com/book/en/v1/Git-Internals-Git-References#Tags)のみをサポートし、軽量タグはサポートしません。
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'tags' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## ツリー
-
-Git ツリーオブジェクトは、Git リポジトリ内のファイル間の階層を作成します。 Git ツリーオブジェクトを使用して、ディレクトリとそこに含まれるファイルの関係を作成できます。 これらのエンドポイントを使用すると、{% data variables.product.product_name %} 上の Git データベースに対して [ツリーオブジェクト](https://git-scm.com/book/en/v1/Git-Internals-Git-Objects#Tree-Objects)の読み書きができます。
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'trees' %}{% include rest_operation %}{% endif %}
-{% endfor %}
+
diff --git a/translations/ja-JP/content/rest/reference/gitignore.md b/translations/ja-JP/content/rest/reference/gitignore.md
index 191171051a2a..65610e6aaddc 100644
--- a/translations/ja-JP/content/rest/reference/gitignore.md
+++ b/translations/ja-JP/content/rest/reference/gitignore.md
@@ -13,14 +13,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-When you create a new repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} via the API, you can specify a [.gitignore template](/github/getting-started-with-github/ignoring-files) to apply to the repository upon creation. .gitignore テンプレート API は、{% data variables.product.product_name %} の [.gitignore リポジトリ](https://github.com/github/gitignore)からテンプレートを一覧表示してフェッチします。
-
-### gitignore のカスタムメディアタイプ
-
-gitignore テンプレートを取得するときに、このカスタムメディアタイプを使用できます。
-
- application/vnd.github.VERSION.raw
-
-詳しい情報については、「[メディアタイプ](/rest/overview/media-types)」を参照してください。
-
-{% include rest_operations_at_current_path %}
+
\ No newline at end of file
diff --git a/translations/ja-JP/content/rest/reference/index.md b/translations/ja-JP/content/rest/reference/index.md
index 05dc9b6343d2..bbc7d47c7a38 100644
--- a/translations/ja-JP/content/rest/reference/index.md
+++ b/translations/ja-JP/content/rest/reference/index.md
@@ -51,6 +51,5 @@ children:
- /teams
- /users
- /webhooks
- - /permissions-required-for-github-apps
---
diff --git a/translations/ja-JP/content/rest/reference/interactions.md b/translations/ja-JP/content/rest/reference/interactions.md
index 43e4e1af81f5..174ce78978af 100644
--- a/translations/ja-JP/content/rest/reference/interactions.md
+++ b/translations/ja-JP/content/rest/reference/interactions.md
@@ -11,50 +11,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-リポジトリに対するインタラクションには、コミット、Issueのオープン、プルリクエストの作成があります。 インタラクションAPIを使用すると、オーナーまたは管理者アクセス権のあるユーザはパブリックリポジトリの操作を一時的に特定のユーザのタイプに制限することができます。
-
-{% for operation in currentRestOperations %}
- {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
-{% endfor %}
-
-## Organization
-
-OrganizationのインタラクションAPIを使用すると、OrganizationのオーナーはOrganizationのパブリックリポジトリでコメント、Issueのオープン、プルリクエストの作成ができるユーザのタイプを一時的に制限することができます。 {% data reusables.interactions.interactions-detail %} {% data variables.product.product_name %} ユーザのタイプについては以下を参照してください。
-
-* Organizationの{% data reusables.interactions.existing-user-limit-definition %}
-* Organizationの{% data reusables.interactions.contributor-user-limit-definition %}
-* Organizationの{% data reusables.interactions.collaborator-user-limit-definition %}
-
-Organizationレベルでインタラクション制限を設定すると、Organizationが所有する個々のリポジトリに設定されているインタラクション制限は上書きされます。 Organizationが所有する個々のリポジトリに対して異なるインタラクション制限を設定するには、かわりに[リポジトリ](#repository)インタラクションエンドポイントを使用してください。
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'orgs' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## Repository
-
-リポジトリのインタラクションAPIを使用すると、オーナーまたは管理者アクセス権のあるユーザはパブリックリポジトリでコメント、Issueのオープン、プルリクエストの作成ができるユーザのタイプを一時的に制限することができます。 {% data reusables.interactions.interactions-detail %} {% data variables.product.product_name %} ユーザのタイプについては以下を参照してください。
-
-* リポジトリの{% data reusables.interactions.existing-user-limit-definition %}
-* リポジトリの{% data reusables.interactions.contributor-user-limit-definition %}
-* リポジトリの{% data reusables.interactions.collaborator-user-limit-definition %}
-
-リポジトリを所有しているユーザまたはOrganizationについてインタラクション制限を有効にしている場合、個々のリポジトリについてその制限を変更することはできません。 インタラクション制限を変更するには、[ユーザ](#user)または[Organization](#organization)インタラクションエンドポイントを使用してください。
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'repos' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## ユーザ
-
-ユーザのインタラクションAPIを使用すると、自分のパブリックリポジトリでコメント、Issueのオープン、プルリクエストの作成ができるユーザのタイプを一時的に制限することができます。 {% data reusables.interactions.interactions-detail %} {% data variables.product.product_name %} ユーザのタイプについては以下を参照してください。
-
-* {% data reusables.interactions.existing-user-limit-definition %}が自分のリポジトリの操作を制限されます。
-* {% data reusables.interactions.contributor-user-limit-definition %}が自分のリポジトリの操作を制限されます。
-* {% data reusables.interactions.collaborator-user-limit-definition %}が自分のリポジトリの操作を制限されます。
-
-ユーザレベルでインタラクション制限を設定すると、ユーザが所有する個々のリポジトリに設定されているインタラクション制限は上書きされます。 ユーザが所有する個々のリポジトリに対して異なるインタラクション制限を設定するには、かわりに[リポジトリ](#repository)インタラクションエンドポイントを使用してください。
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'user' %}{% include rest_operation %}{% endif %}
-{% endfor %}
+
diff --git a/translations/ja-JP/content/rest/reference/issues.md b/translations/ja-JP/content/rest/reference/issues.md
index e036a079c86d..0cacdccae2a2 100644
--- a/translations/ja-JP/content/rest/reference/issues.md
+++ b/translations/ja-JP/content/rest/reference/issues.md
@@ -13,63 +13,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-### Issue のカスタムメディアタイプ
-
-Issue についてサポートされているメディアタイプは次のとおりです。
-
- application/vnd.github.VERSION.raw+json
- application/vnd.github.VERSION.text+json
- application/vnd.github.VERSION.html+json
- application/vnd.github.VERSION.full+json
-
-メディアタイプの詳しい情報については、「[カスタムメディアタイプ](/rest/overview/media-types)」を参照してください。
-
-{% for operation in currentRestOperations %}
- {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
-{% endfor %}
-
-## アサインされた人
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'assignees' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## コメント
-
-Issue コメント API は、Issue およびプルリクエストに関するリスト、表示、編集、コメントの作成に対応しています。
-
-Issue コメントは、[3 つのカスタムメディアタイプ](#custom-media-types)を使用します。 API におけるメディアタイプの使用に関する詳細は、[こちら](/rest/overview/media-types)を参照してください。
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'comments' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## イベント
-
-Issue イベント API は、Issue およびプルリクエストでのアクティビティによってトリガーされるイベントのタイプを返します。 The Issue Events API can return different types of events triggered by activity in issues and pull requests. For more information about the specific events that you can receive from the Issue Events API, see "[Issue event types](/developers/webhooks-and-events/issue-event-types)." 詳細は、「[イベント API](/developers/webhooks-and-events/github-event-types)」を参照してください。
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'events' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## ラベル
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'labels' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## マイルストーン
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'milestones' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## タイムライン
-
-タイムラインイベント API は、Issue およびプルリクエストでのタイムラインアクティビティによってトリガーされるイベントのタイプを返します。 The Issue Events API can return different types of events triggered by activity in issues and pull requests. For more information about the specific events that you can receive from the Issue Events API, see "[Issue event types](/developers/webhooks-and-events/issue-event-types)." 詳細は、「[GitHub イベント API](/developers/webhooks-and-events/github-event-types)」を参照してください。
-
-この API を使用すると、Issue およびプルリクエストに関する情報を表示したり、Issue コメントを通知する相手を決定したりできます。
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'timeline' %}{% include rest_operation %}{% endif %}
-{% endfor %}
+
diff --git a/translations/ja-JP/content/rest/reference/licenses.md b/translations/ja-JP/content/rest/reference/licenses.md
index de00bb87bf48..5aff34836893 100644
--- a/translations/ja-JP/content/rest/reference/licenses.md
+++ b/translations/ja-JP/content/rest/reference/licenses.md
@@ -13,27 +13,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-ライセンス API は、広く利用されているオープンソースライセンスに関するメタデータと、特定のプロジェクトのライセンスファイルに関する情報を返します。
-
-ライセンス API は[オープンソースの Ruby Gem ライセンス](https://github.com/benbalter/licensee)を使用して、プロセスのライセンスを特定しようとします。 ライセンシーは、プロジェクトの `LICENSE` ファイル (存在する場合) を既知のライセンスの短いリストと照合します。 そのためライセンス API では、プロジェクト依存関係のライセンス、あるいはプロジェクトのライセンスをドキュメント化するその他の方法、たとえばドキュメントにおけるライセンス名の参照などは考慮されません。
-
-ライセンスが一致した場合、返されるライセンスキーおよび名前は[SPDX 仕様](https://spdx.org/)に適合します。
-
-**注釈:** 以下のエンドポイントも、リポジトリのライセンス情報を返します。
-
-- [リポジトリの取得](/rest/reference/repos#get-a-repository)
-- [ユーザのリポジトリの一覧表示](/rest/reference/repos#list-repositories-for-a-user)
-- [Organization リポジトリの一覧表示](/rest/reference/repos#list-organization-repositories)
-- [フォークの一覧表示](/rest/reference/repos#list-forks)
-- [ユーザが Watch しているリポジトリの一覧表示](/rest/reference/activity#list-repositories-watched-by-a-user)
-- [Team リポジトリの一覧表示](/rest/reference/teams#list-team-repositories)
-
-{% warning %}
-
-GitHub にはいろいろなものがありますが、法律事務所ではありません。 そのため、GitHub が法律上の助言をすることはありません。 ライセンス API を使用したり、それに関して当社にメールを送信したりすることは法律上の助言に該当せず、弁護士と依頼人の関係を確立するものでもありません。 特定のライセンスで許可される範囲について疑問がある場合は、先に進む前にそれぞれの顧問弁護士にご相談ください。 むしろ、法的な結果が想定される、あるいは法律上の権利に影響しうる決定を下す場合には、必ずその前に各自の弁護士にご相談ください。
-
-GitHub は、ユーザがオープンソースライセンスと、それを利用するプロジェクトに関する情報を得るためにライセンス API を作成しました。 お役に立てれば幸いですが、当社は (少なくとも従業員のほとんどは) 弁護士ではなく、他の方と同じように誤りがないとは言えません。 For that reason, GitHub provides the API on an "as-is" basis and makes no warranties regarding any information or licenses provided on or through it, and disclaims liability for damages resulting from using the API.
-
-{% endwarning %}
-
-{% include rest_operations_at_current_path %}
+
diff --git a/translations/ja-JP/content/rest/reference/markdown.md b/translations/ja-JP/content/rest/reference/markdown.md
index bdb12789aed6..e17fb2faa927 100644
--- a/translations/ja-JP/content/rest/reference/markdown.md
+++ b/translations/ja-JP/content/rest/reference/markdown.md
@@ -13,4 +13,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-{% include rest_operations_at_current_path %}
+
\ No newline at end of file
diff --git a/translations/ja-JP/content/rest/reference/meta.md b/translations/ja-JP/content/rest/reference/meta.md
index 138e52e1b391..43a541a79f5b 100644
--- a/translations/ja-JP/content/rest/reference/meta.md
+++ b/translations/ja-JP/content/rest/reference/meta.md
@@ -13,4 +13,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-{% include rest_operations_at_current_path %}
+
diff --git a/translations/ja-JP/content/rest/reference/metrics.md b/translations/ja-JP/content/rest/reference/metrics.md
index 1b147f2d422e..4d174aec373d 100644
--- a/translations/ja-JP/content/rest/reference/metrics.md
+++ b/translations/ja-JP/content/rest/reference/metrics.md
@@ -14,47 +14,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-{% for operation in currentRestOperations %}
- {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
-{% endfor %}
-
-{% ifversion fpt or ghec %}
-## コミュニティ
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'community' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% endif %}
-
-## 統計
-
-Repository Statistics API を使用すると、{% data variables.product.product_name %} がさまざまなタイプのリポジトリのアクティビティを視覚化するために用いるデータをフェッチできます。
-
-### キャッシングについて
-
-リポジトリの統計情報を計算するのは負荷が高い操作なので、可能な限りキャッシュされたデータを返すようにしています。 リポジトリの統計をクエリした際にデータがキャッシュされていなかった場合は、`202` レスポンスを受け取ります。また、この統計をまとめるため、バックグラウンドでジョブが開始します。 このジョブが完了するまで少し待ってから、リクエストを再度サブミットしてください。 ジョブが完了していた場合、リクエストは `200` レスポンスを受けとり、レスポンスの本文には統計情報が含まれています。
-
-リポジトリの統計情報は、リポジトリのデフォルトブランチに SHA でキャッシュされ、デフォルトのブランチにプッシュすると統計情報のキャッシュがリセットされます。
-
-### 統計で除外されるコミットのタイプ
-
-API によって公開される統計は、[別のリポジトリグラフ](/github/visualizing-repository-data-with-graphs/about-repository-graphs)で表示される統計と同じものです。
-
-要約すると、
-- すべての統計は、マージコミットが除外されます。
-- コントリビューター統計では、空のコミットも除外されます。
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'statistics' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% ifversion fpt or ghec %}
-## トラフィック
-
-プッシュアクセスを持つリポジトリに対し、トラフィック API はリポジトリグラフが提供する情報へのアクセスを提供します。 詳細は「リポジトリへのトラフィックを表示する」を参照してください。
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'traffic' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-{% endif %}
+
\ No newline at end of file
diff --git a/translations/ja-JP/content/rest/reference/migrations.md b/translations/ja-JP/content/rest/reference/migrations.md
index cf0966f26fbc..cd1ec7e5425a 100644
--- a/translations/ja-JP/content/rest/reference/migrations.md
+++ b/translations/ja-JP/content/rest/reference/migrations.md
@@ -15,116 +15,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-{% for operation in currentRestOperations %}
- {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
-{% endfor %}
-
-## Organization
-
-移行 API を使用できるのは、認証済みの Organization オーナーのみです。 For more information, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#permission-levels-for-an-organization)" and "[Other authentication methods](/rest/overview/other-authentication-methods)."
-
-{% data variables.migrations.organization_migrations_intro %}
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'orgs' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% ifversion fpt or ghec %}
-## ソースのインポート
-
-{% data variables.migrations.source_imports_intro %}
-
-一般的なソースのインポートでは、まずインポートを開始し、次に (オプションで) 作者を更新したり、インポートに大きいファイルが存在する場合に Git LFS 使用の設定を更新したりします。 [`RepositoryImportEvent`](/developers/webhooks-and-events/webhook-events-and-payloads#repository_import) をリスニングする webhook を作成して、インポートのステータスを確認することもできます。
-
-詳細な例は、次の図を参照してください。
-
-```
-+---------+ +--------+ +---------------------+
-| Tooling | | GitHub | | Original Repository |
-+---------+ +--------+ +---------------------+
- | | |
- | Start import | |
- |----------------------------->| |
- | | |
- | | Download source data |
- | |--------------------------------------------->|
- | | Begin streaming data |
- | |<---------------------------------------------|
- | | |
- | Get import progress | |
- |----------------------------->| |
- | "status": "importing" | |
- |<-----------------------------| |
- | | |
- | Get commit authors | |
- |----------------------------->| |
- | | |
- | Map a commit author | |
- |----------------------------->| |
- | | |
- | | |
- | | Finish streaming data |
- | |<---------------------------------------------|
- | | |
- | | Rewrite commits with mapped authors |
- | |------+ |
- | | | |
- | |<-----+ |
- | | |
- | | Update repository on GitHub |
- | |------+ |
- | | | |
- | |<-----+ |
- | | |
- | Map a commit author | |
- |----------------------------->| |
- | | Rewrite commits with mapped authors |
- | |------+ |
- | | | |
- | |<-----+ |
- | | |
- | | Update repository on GitHub |
- | |------+ |
- | | | |
- | |<-----+ |
- | | |
- | Get large files | |
- |----------------------------->| |
- | | |
- | opt_in to Git LFS | |
- |----------------------------->| |
- | | Rewrite commits for large files |
- | |------+ |
- | | | |
- | |<-----+ |
- | | |
- | | Update repository on GitHub |
- | |------+ |
- | | | |
- | |<-----+ |
- | | |
- | Get import progress | |
- |----------------------------->| |
- | "status": "complete" | |
- |<-----------------------------| |
- | | |
- | | |
-```
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'source-imports' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-{% endif %}
-## ユーザ
-
-ユーザ移行 API を使用できるのは、認証済みのアカウントオーナーのみです。 詳細は、「[その他の認証方式](/rest/overview/other-authentication-methods)」を参照してください。
-
-{% data variables.migrations.user_migrations_intro %}ダウンロードできる移行データのリストは、「[ユーザー移行アーカイブをダウンロードする](#download-a-user-migration-archive)」を参照してください。
-
-アーカイブをダウンロードするには、先にユーザ移行を開始する必要があります。 移行のステータスが `exported` になると、移行をダウンロードできます。
-
-移行アーカイブを作成すると、7 日間ダウンロードできるようになります。 ただし、必要があればユーザ移行アーカイブはそれより以前に削除できます。 移行が `exported` になってからリポジトリのロックを解除すると、リポジトリの使用を再開でき、ソースデータが不要な場合にはリポジトリを削除することもできます。
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'users' %}{% include rest_operation %}{% endif %}
-{% endfor %}
+
diff --git a/translations/ja-JP/content/rest/reference/oauth-authorizations.md b/translations/ja-JP/content/rest/reference/oauth-authorizations.md
index 6d258cd290d3..a7c00b5837c2 100644
--- a/translations/ja-JP/content/rest/reference/oauth-authorizations.md
+++ b/translations/ja-JP/content/rest/reference/oauth-authorizations.md
@@ -8,8 +8,6 @@ versions:
miniTocMaxHeadingLevel: 3
---
-この API を使用すると、OAuth アプリケーションから自分のアカウントへのアクセスを管理することができます。 この API にアクセスするには、ユーザ名とパスワードを使用する [Basic 認証](/rest/overview/other-authentication-methods#basic-authentication) が必要であり、トークンは使用できません。
-
-自分または自分のユーザが 2 要素認証を有効にしている場合は、必ず [2 要素認証の使用方法](/rest/overview/other-authentication-methods#working-with-two-factor-authentication)を理解していることを確認してください。
-
-{% include rest_operations_at_current_path %}
+
diff --git a/translations/ja-JP/content/rest/reference/orgs.md b/translations/ja-JP/content/rest/reference/orgs.md
index 2d3934b17c04..637c7b818e56 100644
--- a/translations/ja-JP/content/rest/reference/orgs.md
+++ b/translations/ja-JP/content/rest/reference/orgs.md
@@ -14,66 +14,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-{% for operation in currentRestOperations %}
- {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
-{% endfor %}
-
-{% ifversion fpt or ghec %}
-## ユーザのブロック
-
-Organization に対するブロック呼び出しを実行するには、呼び出しの認証に使用するトークンに `admin:org` が必要です。 それがない場合には、`HTTP 404` が返されます。
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'blocking' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% endif %}
-
-## メンバー
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'members' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## 外部コラボレーター
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'outside-collaborators' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% ifversion fpt or ghes > 3.4 %}
-## カスタムリポジトリロール
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'custom_roles' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-{% endif %}
-
-## webhook
-
-Organization webhooks allow you to receive HTTP `POST` payloads whenever certain events happen in an organization. {% data reusables.webhooks.webhooks-rest-api-links %}
-
-サブスクライブできるアクションの詳細は、「[{% data variables.product.prodname_dotcom %} のイベントタイプ](/developers/webhooks-and-events/github-event-types)」を参照してください。
-
-### スコープと制限事項
-
-Organization の webhook に対するすべてのアクションでは、認証ユーザが管理対象の Organization の管理者である必要があります。 また、OAuth トークンには `admin:org_hook` スコープが必要です。 詳しい情報については、「[OAuth App のスコープ](/developers/apps/scopes-for-oauth-apps)」を参照してください。
-
-webhook 設定に存在する可能性がある機密データを保護するために、次のアクセス制御ルールも適用します。
-
-- OAuth アプリケーションが、それによって作成されたのではない webhook をリスト、表示、編集することはできません。
-- OAuth アプリケーションによって作成された webhook をユーザがリスト、表示、編集することはできません。
-
-### webhook の受信
-
-{% data variables.product.product_name %} で webhook ペイロードを送信するには、インターネットからサーバーにアクセスできる必要があります。 暗号化されたペイロードを HTTPS 経由で送信できるように、SSL の使用も強く推奨します。
-
-その他のベストプラクティスについては、[ガイド](/guides/best-practices-for-integrators/)を参照してください。
-
-#### webhook ヘッダー
-
-{% data variables.product.product_name %} は、イベントタイプとペイロード識別子を区別するために、複数の HTTP ヘッダーも送信します。 詳細は「[webhook ヘッダー](/webhooks/event-payloads/#delivery-headers)」を参照してください。
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'webhooks' %}{% include rest_operation %}{% endif %}
-{% endfor %}
+
diff --git a/translations/ja-JP/content/rest/reference/packages.md b/translations/ja-JP/content/rest/reference/packages.md
index 8c19ccb3019e..06e5f09b36ac 100644
--- a/translations/ja-JP/content/rest/reference/packages.md
+++ b/translations/ja-JP/content/rest/reference/packages.md
@@ -10,17 +10,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-{% data variables.product.prodname_registry %} APIでは、REST APIを使ってパッケージを管理できます。 パッケージのリストアや削除についてさらに学ぶには、「[パッケージのリストアと削除](/packages/learn-github-packages/deleting-and-restoring-a-package)」を参照してください。
-
-このAPIを使うには、個人アクセストークンを使って認証を受けなければなりません。
- - パッケージメタデータにアクセスするには、トークンに`read:packages`スコープが含まれていなければなりません。
- - パッケージやパッケージのバージョンを削除するには、トークンに`read:packages`及び`delete:packages`スコープが含まれていなければなりません。
- - パッケージやパッケージのバージョンをリストアするには、トークンに`read:packages`及び`write:packages`スコープが含まれていなければなりません。
-
-`package_type`が`npm`、`maven`、`rubygems`、`nuget`のいずれかなら、パッケージは{% data variables.product.prodname_dotcom %}リポジトリからの権限を継承するので、トークンには`repo`スコープも含まれていなければなりません。 パッケージが{% data variables.product.prodname_container_registry %}内にあるなら、`package_type`は`container`であり、この`package_type`のアクセスあるいは管理のためにトークンに`repo`スコープが含まれている必要はありません。 `container`パッケージは、リポジトリは別に詳細な権限を提供します。 詳しい情報については「[{% data variables.product.prodname_registry %}の権限について](/packages/learn-github-packages/about-permissions-for-github-packages#about-scopes-and-permissions-for-package-registries)」を参照してください。
-
-SSOが有効化されたOrganization内のリソースにアクセスするために{% data variables.product.prodname_registry %} APIを使いたい場合は、個人アクセストークンにSSOを有効化しなければなりません。 For more information, see "[Authorizing a personal access token for use with SAML single sign-on](/github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}
-
-{% for operation in currentRestOperations %}
- {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
-{% endfor %}
+
diff --git a/translations/ja-JP/content/rest/reference/pages.md b/translations/ja-JP/content/rest/reference/pages.md
index 58482b1bd091..ace1e6e9b0ad 100644
--- a/translations/ja-JP/content/rest/reference/pages.md
+++ b/translations/ja-JP/content/rest/reference/pages.md
@@ -1,6 +1,6 @@
---
title: Pages
-intro: The GitHub Pages API allows you to interact with GitHub Pages sites and build information.
+intro: 'The GitHub Pages API allows you to interact with GitHub Pages sites and build information.'
allowTitleToDifferFromFilename: true
versions:
fpt: '*'
@@ -12,22 +12,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-{% data variables.product.prodname_pages %} API は、{% data variables.product.prodname_pages %} の設定や、ビルドのステータスについての情報を取得します。 サイトとビルドに関する情報は、{% ifversion not ghae %}Webサイトがパブリックの場合であっても{% endif %}認証を受けたユーザだけがアクセスできます。 詳しい情報については、「[{% data variables.product.prodname_pages %} について](/pages/getting-started-with-github-pages/about-github-pages)」を参照してください。
-
-レスポンスに `status` キーを持つ {% data variables.product.prodname_pages %} API エンドポイントにおいては、値は以下のいずれかになります。
-* `null`: サイトはまだビルドされていません。
-* `queued`: ビルドがリクエストされたが、まだ開始していません。
-* `building`: ビルドが進行中です。
-* `built`: サイトがビルドされています。
-* `errored`: ビルド中にエラーが発生したことを示します。
-
-GitHub Pages サイトの情報を返す {% data variables.product.prodname_pages %} API エンドポイントにおいては、JSON のレスポンスには以下が含まれます。
-* `html_url`: レンダリングされた Pages サイトの絶対 URL (スキームを含む) 。 たとえば、`https://username.github.io` などです。
-* `source`: レンダリングされた Pages サイトのソースブランチおよびディレクトリを含むオブジェクト。 これは以下のものが含まれます。
- - `branch`: [サイトのソースファイル](/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site)を公開するために使用するリポジトリのブランチ。 たとえば、_main_ or _gh-pages_ などです。
- - `path`: サイトの公開元のリポジトリディレクトリ。 `/` または `/docs` のどちらかとなります。
-
-{% comment %}An extra blank line is needed here to make sure the operations below don't continue the list above.{% endcomment %}
-{% for operation in currentRestOperations %}
- {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
-{% endfor %}
+
\ No newline at end of file
diff --git a/translations/ja-JP/content/rest/reference/projects.md b/translations/ja-JP/content/rest/reference/projects.md
index 5c1925db546c..19e3aa4526d1 100644
--- a/translations/ja-JP/content/rest/reference/projects.md
+++ b/translations/ja-JP/content/rest/reference/projects.md
@@ -13,26 +13,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-{% for operation in currentRestOperations %}
- {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
-{% endfor %}
-
-## カード
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'cards' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## コラボレータ
-
-このAPIを使用すると、Organizationのプロジェクトと対話できます。
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'collaborators' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## カラム
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'columns' %}{% include rest_operation %}{% endif %}
-{% endfor %}
+
diff --git a/translations/ja-JP/content/rest/reference/pulls.md b/translations/ja-JP/content/rest/reference/pulls.md
index f5ddb26509f8..35ff9ce4097c 100644
--- a/translations/ja-JP/content/rest/reference/pulls.md
+++ b/translations/ja-JP/content/rest/reference/pulls.md
@@ -13,75 +13,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-Pull Request API を使用すると、Pull Requestを一覧表示、編集、作成、マージできます。 Pull Requestのコメントは、[Issue Comments API](/rest/reference/issues#comments) で管理できます。
-
-すべてのPull Requestは Issue ですが、すべての Issue がPull Requestというわけではありません。 このため、アサインされた人、ラベル、マイルストーンなどの操作といった、両方の機能で共通するアクションは、[Issues API](/rest/reference/issues) で提供されます。
-
-### Pull Requestのカスタムメディアタイプ
-
-以下がPull Requestでサポートされているメディアタイプです。
-
- application/vnd.github.VERSION.raw+json
- application/vnd.github.VERSION.text+json
- application/vnd.github.VERSION.html+json
- application/vnd.github.VERSION.full+json
- application/vnd.github.VERSION.diff
- application/vnd.github.VERSION.patch
-
-詳しい情報については、「[カスタムメディアタイプ](/rest/overview/media-types)」を参照してください。
-
-diff が破損している場合は、{% data variables.contact.contact_support %} にお問い合わせください。 メッセージにはリポジトリ名とPull Request ID を記載してください。
-
-### リンク関係
-
-Pull Requestには以下のリンク関係が含まれる可能性があります。
-
-| 名前 | 説明 |
-| ----------------- | ----------------------------------------------------------------------------------------------------------------- |
-| `self` | Pull Requestの API ロケーション。 |
-| `html` | Pull Requestの HTML ロケーション。 |
-| `Issue` | Pull Requestの [Issue](/rest/reference/issues) の API ロケーション。 |
-| `コメント` | Pull Requestの [Issue コメント](/rest/reference/issues#comments) の API ロケーション。 |
-| `review_comments` | Pull Requestの [レビューコメント](/rest/reference/pulls#comments) の API ロケーション。 |
-| `review_comment` | Pull Requestのリポジトリで、[レビューコメント](/rest/reference/pulls#comments)の API ロケーションを構築するための[URL テンプレート](/rest#hypermedia)。 |
-| `commits` | Pull Requestの [コミット](#list-commits-on-a-pull-request) の API ロケーション。 |
-| `statuses` | Pull Requestの[コミットステータス](/rest/reference/commits#commit-statuses)、すなわち`head` ブランチのステータスの API ロケーション。 |
-
-{% for operation in currentRestOperations %}
- {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
-{% endfor %}
-
-## レビュー
-
-Pull Requestレビューは、Pull Request上のPull Requestレビューコメントのグループで、状態とオプションの本文コメントでグループ化されています。
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'reviews' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## レビューコメント
-
-Pull Requestレビューコメントは、Pull Requestのレビュー中に unified 形式の diff の一部に付けられたコメントです。 コミットコメントおよび Issue コメントは、Pull Requestレビューコメントとは異なります。 コミットコメントはコミットに直接付けるもので、Issue コメントは、unified 形式の diff の一部を参照することなく付けるものです。 詳しい情報については、「[コミットコメントの作成](/rest/reference/commits#create-a-commit-comment)」および「[Issue コメントの作成](/rest/reference/issues#create-an-issue-comment)」を参照してください。
-
-### Pull Requestレビューコメントのカスタムメディアタイプ
-
-以下がPull Requestレビューコメントでサポートされているメディアタイプです。
-
- application/vnd.github.VERSION.raw+json
- application/vnd.github.VERSION.text+json
- application/vnd.github.VERSION.html+json
- application/vnd.github.VERSION.full+json
-
-詳しい情報については、「[カスタムメディアタイプ](/rest/overview/media-types)」を参照してください。
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'comments' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## レビューリクエスト
-
-Pull Requestの作者、リポジトリのオーナー、およびコラボレータは、リポジトリの書き込みアクセスを持つ人にPull Requestレビューをリクエストできます。 リクエストされたレビュー担当者は、Pull Requestレビューをするようあなたが依頼したという通知を受け取ります。
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'review-requests' %}{% include rest_operation %}{% endif %}
-{% endfor %}
+
diff --git a/translations/ja-JP/content/rest/reference/rate-limit.md b/translations/ja-JP/content/rest/reference/rate-limit.md
index b00f0ec03ab9..fbb5451ea954 100644
--- a/translations/ja-JP/content/rest/reference/rate-limit.md
+++ b/translations/ja-JP/content/rest/reference/rate-limit.md
@@ -14,22 +14,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-REST API 概要ドキュメンテーションでは、[レート制限のルール](/rest/overview/resources-in-the-rest-api#rate-limiting)について説明しています。 以下で説明する Rate Limit API を使用して、現在のレート制限ステータスをいつでも確認できます。
-
-### レート制限のステータスを理解する
-
-Search APIは[カスタムのレート制限](/rest/reference/search#rate-limit)を持ち、他のREST APIを管理するレート制限とは分離されています。 GraphQL APIも[カスタムのレート制限]({% ifversion ghec%}/free-pro-team@latest{% endif %}/graphql/overview/resource-limitations#rate-limit)を持ち、REST APIのレート制限とは分離されて別に計算されます。
-
-そのため、Rate Limit APIのレスポンスは、レート制限を分類します。 `resources` の下には、4 つのオブジェクトがあります。
-
-* `core`オブジェクトは、REST API中の検索に関連しないすべてのリソースに関するレート制限のステータスを提供します。
-
-* `search`オブジェクトは、[Search API](/rest/reference/search)に対するレート制限のステータスを提供します。
-
-* `graphql`オブジェクトは、[GraphQL API]({% ifversion ghec%}/free-pro-team@latest{% endif %}/graphql)に対するレート制限のステータスを提供します。
-
-* `integration_manifest`オブジェクトは、[GitHub App Manifest コード変換](/apps/building-github-apps/creating-github-apps-from-a-manifest/#3-you-exchange-the-temporary-code-to-retrieve-the-app-configuration)エンドポイントに対するレート制限のステータスを提供します。
-
-For more information on the headers and values in the rate limit response, see "[Resources in the REST API](/rest/overview/resources-in-the-rest-api#rate-limit-http-headers)."
-
-{% include rest_operations_at_current_path %}
+
diff --git a/translations/ja-JP/content/rest/reference/reactions.md b/translations/ja-JP/content/rest/reference/reactions.md
index 99af8dcb50a2..b9fbe7fa749b 100644
--- a/translations/ja-JP/content/rest/reference/reactions.md
+++ b/translations/ja-JP/content/rest/reference/reactions.md
@@ -13,10 +13,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-### リアクションタイプ
-
-リアクションを作成する際、`content`パラメータで利用可能な値は以下の通りです (参考のため、対応する絵文字も掲載します)。
-
-{% data reusables.repositories.reaction_list %}
-
-{% include rest_operations_at_current_path %}
+
diff --git a/translations/ja-JP/content/rest/reference/releases.md b/translations/ja-JP/content/rest/reference/releases.md
index 5dd4437d745f..dd6a8f256139 100644
--- a/translations/ja-JP/content/rest/reference/releases.md
+++ b/translations/ja-JP/content/rest/reference/releases.md
@@ -12,18 +12,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-{% note %}
-
-**注釈:** Releases API は Downloads API を置き換えるものです。 リリースを返し、アセットをリリースする、この API のエンドポイントからダウンロード数と ブラウザのダウンロード URL を取得できます。
-
-{% endnote %}
-
-{% for operation in currentRestOperations %}
- {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
-{% endfor %}
-
-## Release assets
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'assets' %}{% include rest_operation %}{% endif %}
-{% endfor %}
+
diff --git a/translations/ja-JP/content/rest/reference/repos.md b/translations/ja-JP/content/rest/reference/repos.md
index 290ecafc7582..01bcaaac010f 100644
--- a/translations/ja-JP/content/rest/reference/repos.md
+++ b/translations/ja-JP/content/rest/reference/repos.md
@@ -14,63 +14,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-{% for operation in currentRestOperations %}
- {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
-{% endfor %}
-
-{% ifversion fpt or ghec or ghes > 3.2 or ghae-issue-4742 %}
-## Autolinks
-
-To help streamline your workflow, you can use the API to add autolinks to external resources like JIRA issues and Zendesk tickets. 詳しい情報については「[外部リソースを参照する自動リンクの設定](/github/administering-a-repository/configuring-autolinks-to-reference-external-resources)」を参照してください。
-
-{% data variables.product.prodname_github_apps %} require repository administration permissions with read or write access to use the Autolinks API.
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'autolinks' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-{% endif %}
-
-
-## コンテンツ
-
-これらの API エンドポイントを使用すると、リポジトリ内の Base64 でエンコードされたコンテンツを作成、変更、削除できます。 Raw 形式またはレンダリングされた HTML (サポートされている場合) をリクエストするには、リポジトリのコンテンツにカスタムメディアタイプを使用します。
-
-### リポジトリコンテンツのカスタムメディアタイプ
-
-[README](/rest/reference/repos#get-a-repository-readme)、[ファイル](/rest/reference/repos#get-repository-content)、[シンボリックリンク](/rest/reference/repos#get-repository-content)は以下のカスタムメディアタイプをサポートしています。
-
- application/vnd.github.VERSION.raw
- application/vnd.github.VERSION.html
-
-ファイルのコンテンツを取得するには、`.raw` メディアタイプを使ってください。
-
-Markdown や AsciiDoc などのマークアップファイルでは、`.html` メディアタイプを使用して、レンダリングされた HTML を取得できます。 マークアップ言語は、オープンソースの[マークアップライブラリ](https://github.com/github/markup)を使用して HTML にレンダリングされます。
-
-[すべてのオブジェクト](/rest/reference/repos#get-repository-content)は、以下のカスタムメディアタイプをサポートしています。
-
- application/vnd.github.VERSION.object
-
-コンテンツのタイプに関係なく、一貫したオブジェクトフォーマットを取得するには、`object` メディアタイプパラメータを使用します。 たとえば、レスポンスはディレクトリに対するオブジェクトの配列ではなく、オブジェクトの配列を含む `entries` 属性のオブジェクトになります。
-
-API でのメディアタイプの使用について詳しくは、[こちら](/rest/overview/media-types)をご覧ください。
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'contents' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## フォーク
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'forks' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% ifversion fpt or ghae or ghes > 3.2 or ghec %}
-
-## Git LFS
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'lfs' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% endif %}
-
+
diff --git a/translations/ja-JP/content/rest/reference/scim.md b/translations/ja-JP/content/rest/reference/scim.md
index 6db0d73edb9d..25b12f884424 100644
--- a/translations/ja-JP/content/rest/reference/scim.md
+++ b/translations/ja-JP/content/rest/reference/scim.md
@@ -11,46 +11,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-### Organization 向け SCIM プロビジョニング
-
-SCIM API は SCIM を有効にしたアイデンティティプロバイダ (IdPs) で、{% data variables.product.product_name %} Organization メンバーシップのプロビジョニングを自動化するために用いられます。 The {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API is based on version 2.0 of the [SCIM standard](http://www.simplecloud.info/). IdP が使用するべき {% data variables.product.product_name %} SCIM エンドポイントは、`{% data variables.product.api_url_code %}/scim/v2/organizations/{org}/` です。
-
-{% note %}
-
-**ノート:**
- - The SCIM API is available only to organizations on [{% data variables.product.prodname_ghe_cloud %}](/billing/managing-billing-for-your-github-account/about-billing-for-github-accounts) with [SAML SSO](/rest/overview/other-authentication-methods#authenticating-for-saml-sso) enabled. {% data reusables.scim.enterprise-account-scim %} SCIMに関する詳しい情報については、「[SCIM について](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim) 」を参照してください。
- - The SCIM API cannot be used with {% data variables.product.prodname_emus %}.
-
-{% endnote %}
-
-### SCIM API への呼び出しを認証する
-
-SCIM API を使用するには、{% data variables.product.product_name %} Organization の所有者として認証する必要があります。 API は、[OAuth 2.0 Bearer](/developers/apps/authenticating-with-github-apps) トークンが `Authorization` ヘッダに含まれていることを想定しています。 個人アクセストークンを使用することもできますが、まず [SAML SSO Organizationで使用するためにトークンを承認する](/github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)必要があります。
-
-### SAML および SCIM データのマッピング
-
-{% data reusables.scim.nameid-and-username-must-match %}
-
-### サポートされている SCIM ユーザ属性
-
-| 名前 | 種類 | 説明 |
-| ----------------- | --------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `userName` | `string` | ユーザのユーザ名。 |
-| `name.givenName` | `string` | ユーザーの名。 |
-| `name.familyName` | `string` | ユーザーの姓。 |
-| `emails` | `array` | ユーザのメール一覧。 |
-| `externalId` | `string` | この識別子は SAML プロバイダによって生成され、GitHub ユーザと照合するためにSAML プロバイダによって一意の ID として使用されます。 ユーザの `externalID` は、SAML プロバイダ、または [SCIM プロビジョニング済み ID の一覧表示](#list-scim-provisioned-identities)エンドポイントを使用して、ユーザの GitHub ユーザ名やメールアドレスなどの他の既知の属性でフィルタして見つけることができます。 |
-| `id` | `string` | GitHub SCIM エンドポイントによって生成された識別子。 |
-| `active` | `boolean` | ID がアクティブである（true）か、プロビジョニングを解除する必要がある（false）かを示すために使用する。 |
-
-{% note %}
-
-**注釈:** SCIM API のエンドポイント URL では、大文字と小文字が区別されます。 たとえば、`Users` エンドポイントの最初の文字は大文字にする必要があります。
-
-```shell
-GET /scim/v2/organizations/{org}/Users/{scim_user_id}
-```
-
-{% endnote %}
-
-{% include rest_operations_at_current_path %}
+
diff --git a/translations/ja-JP/content/rest/reference/search.md b/translations/ja-JP/content/rest/reference/search.md
index 804000bd83fb..7e1d33f08db2 100644
--- a/translations/ja-JP/content/rest/reference/search.md
+++ b/translations/ja-JP/content/rest/reference/search.md
@@ -13,150 +13,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-Search API は、見つけたい特定の項目を検索するために役立ちます。 たとえば、リポジトリ内のユーザや特定のファイルを見つけることができます。 Google で検索を実行するのと同じように考えてください。 Search API は、探している 1 つの結果 (または探しているいくつかの結果) を見つけるために役立つよう設計されています。 Google で検索する場合と同じように、ニーズに最も合う項目を見つけるため、検索結果を数ページ表示したい場合もあるでしょう。 こうしたニーズを満たすため、{% data variables.product.product_name %} Search API では**各検索につき 最大 1,000 件の結果**を提供します。
-
-クエリを使って、検索を絞り込めます。 検索クエリ構文の詳細については、「[検索クエリの構築](/rest/reference/search#constructing-a-search-query)」を参照してください。
-
-### 検索結果を順番づける
-
-クエリパラメータとして別のソートオプションが指定されない限り、結果は最も一致するものから降順にソートされます。 最も関連性の高い項目を検索結果の最上位に押し上げるように、複数の要素が組み合わされます。
-
-### レート制限
-
-{% data reusables.enterprise.rate_limit %}
-
-Search API にはカスタムレート制限があります。 リクエストに[基本認証](/rest#authentication)、[OAuth](/rest#authentication)、または[クライアント ID とシークレット](/rest#increasing-the-unauthenticated-rate-limit-for-oauth-applications)を使用する場合は、1 分間に最大 30 件のリクエストが行えます。 認証されていないリクエストでは、レート制限により 1 分間あたり最大 10 件のリクエストが行えます。
-
-現在のレート制限状態を確認する方法の詳細については、[レート制限ドキュメンテーション](/rest/reference/rate-limit)を参照してください。
-
-### 検索クエリの構築
-
-Search API の各エンドポイントでは、{% data variables.product.product_name %} で検索を行うために[クエリパラメータ](https://en.wikipedia.org/wiki/Query_string)を使用します。 エンドポイントとクエリパラメータを含める例については、Search API の個々のエンドポイントを参照してください。
-
-クエリには、{% data variables.product.product_name %} でサポートされている検索修飾子を任意に組み合わせて使用できます。 検索クエリの形式は次のとおりです。
-
-```
-SEARCH_KEYWORD_1 SEARCH_KEYWORD_N QUALIFIER_1 QUALIFIER_N
-```
-
-たとえば、README ファイルに `GitHub` と `Octocat` という言葉が含まれている、`defunkt` が所有する_リポジトリ_をすべて検索する場合、_検索リポジトリ_エンドポイントに次のクエリを使用します。
-
-```
-GitHub Octocat in:readme user:defunkt
-```
-
-**ノート:** クエリ文字列の構築には、使用する言語の優先 HTML エンコーダを必ず使用してしてください。 例:
-```javascript
-// JavaScript
-const queryString = 'q=' + encodeURIComponent('GitHub Octocat in:readme user:defunkt');
-```
-
-See "[Searching on GitHub](/search-github/searching-on-github)" for a complete list of available qualifiers, their format, and an example of how to use them. For information about how to use operators to match specific quantities, dates, or to exclude results, see "[Understanding the search syntax](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax/)."
-
-### クエリの長さの制限
-
-Search API は、以下のクエリをサポートしていません。
-- 256 文字超 (演算子や修飾子は除く)。
-- `AND`、`OR`、`NOT` の演算子が 6 つ以上ある。
-
-こうした検索クエリを使用すると、「Validation failed」というエラーメッセージが返されます。
-
-### タイムアウトと不完全な結果
-
-皆さんが Search API を迅速に使用できるよう、個別のクエリを実行する時間について制限を設けています。 [時間制限を超えた](https://developer.github.com/changes/2014-04-07-understanding-search-results-and-potential-timeouts/)クエリに対しては、API はタイムアウト前に見つかった一致を返し、レスポンスの `incomplete_results` プロパティが `true` に設定されます。
-
-タイムアウトになったことは、必ずしも検索結果が未完了であるということではありません。 もっと多くの検索結果が出たかもしれませんし、出ていないかもしれません。
-
-### アクセスエラーまたは検索結果の欠落
-
-You need to successfully authenticate and have access to the repositories in your search queries, otherwise, you'll see a `422 Unprocessable Entry` error with a "Validation Failed" message. たとえば、{% data variables.product.prodname_dotcom %} にサインインしたときにアクセスできないリソースをリクエストする `repo:`、`user:`、または `org:` 修飾子がクエリに含まれている場合、検索は失敗します。
-
-検索クエリで複数のリソースをリクエストする場合、レスポンスにはあなたがアクセスできるリソースのみが含まれ、返されないリソースを一覧表示するようなエラーメッセージは**表示されません**。
-
-たとえば、検索クエリで `octocat/test` リポジトリと `codertocat/test` リポジトリを検索し、`octocat/test` へのアクセス権しか持っていない場合、`octocat/test` の検索結果が表示され、`codertocat/test` の検索結果は全く表示されません。 この振る舞いは、{% data variables.product.prodname_dotcom %} における検索の仕組みと同じです。
-
-{% include rest_operations_at_current_path %}
-
-
-### テキスト一致メタデータ
-
-GitHub では、コードスニペットが提供するコンテキストとと、検索結果のハイライトが使用できます。 Search API では、検索結果を表示するときに、検索と一致した言葉をハイライトできる付加的なメタデータを用意しています。
-
-
-
-リクエストでは、レスポンスに含まれるテキストフラグメントを受け取ることを選べます。各フラグメントには、一致した各検索用語の正確な場所を特定する数値オフセットが付属しています。
-
-検索結果でこのメタデータを取得するには、`Accept` ヘッダで `text-match` メディアタイプを指定します。
-
-```shell
-application/vnd.github.v3.text-match+json
-```
-
-`text-match` メディアタイプを指定すると、JSON ペイロード内にある `text_matches` と呼ばれる追加の鍵を受け取ります。この鍵は、テキスト内の検索用語の位置と、検索用語を含む `property` についての情報を提供します。 `text_matches` 配列内の各オブジェクトには、以下の属性が含まれています。
-
-| 名前 | 説明 |
-| ------------- | ----------------------------------------------------------------------------------------------------------------------------------- |
-| `object_url` | 検索用語のいずれかに一致する文字列プロパティを含むリソースの URL。 |
-| `object_type` | 指定された `object_url` に存在するリソースのタイプの名前。 |
-| `属性` | `object_url` に存在するリソースのプロパティの名前。 このプロパティは、検索用語のいずれかに一致する文字列です。 (`object_url` から返される JSON では、`fragment` の完全な内容を、この名前でプロパティから検索できます。) |
-| `フラグメント` | `property` の値のサブセット。 これは、1 つ以上の検索用語に一致するテキストフラグメントです。 |
-| `matches` | `fragment` に存在する 1 つ以上の検索用語の配列。 インデックス (すなわち「オフセット」) は、フラグメントと関連しています。 (`property` の_完全な_内容とは関係していません。) |
-
-#### サンプル
-
-cURL と、上記の [Issue 検索例](#search-issues-and-pull-requests) を使用すると、API リクエストは次のようになります。
-
-``` shell
-curl -H 'Accept: application/vnd.github.v3.text-match+json' \
-'{% data variables.product.api_url_pre %}/search/issues?q=windows+label:bug+language:python+state:open&sort=created&order=asc'
-```
-
-レスポンスには、検索結果ごとに `text_matches` 配列が含まれます。 以下の JSON では、`text_matches` 配列に 2 つのオブジェクトがあります。
-
-最初のテキスト一致は、Issue の `body` プロパティで発生しました 。 Issue 本文から、テキストのフラグメントが表示されています。 検索用語 (`windows`) はフラグメント内に 2 回出現し、それぞれにインデックスがあります。
-
-2 番目のテキスト一致は、Issue のコメントのうちの 1 つの `body` プロパティで発生しました。 Issue コメントの URL があります。 そしてもちろん、コメント本文から、テキストのフラグメントが表示されています。 検索用語 (`windows`) は、フラグメント内で 1 回出現しています。
-
-```json
-{
- "text_matches": [
- {
- "object_url": "https://api.github.com/repositories/215335/issues/132",
- "object_type": "Issue",
- "property": "body",
- "fragment": "comprehensive windows font I know of).\n\nIf we can find a commonly distributed windows font that supports them then no problem (we can use html font tags) but otherwise the '(21)' style is probably better.\n",
- "matches": [
- {
- "text": "windows",
- "indices": [
- 14,
- 21
- ]
- },
- {
- "text": "windows",
- "indices": [
- 78,
- 85
- ]
- }
- ]
- },
- {
- "object_url": "https://api.github.com/repositories/215335/issues/comments/25688",
- "object_type": "IssueComment",
- "property": "body",
- "fragment": " right after that are a bit broken IMHO :). I suppose we could have some hack that maxes out at whatever the font does...\n\nI'll check what the state of play is on Windows.\n",
- "matches": [
- {
- "text": "Windows",
- "indices": [
- 163,
- 170
- ]
- }
- ]
- }
- ]
-}
-```
+
diff --git a/translations/ja-JP/content/rest/reference/secret-scanning.md b/translations/ja-JP/content/rest/reference/secret-scanning.md
index 14156065de97..dbf47ab6c599 100644
--- a/translations/ja-JP/content/rest/reference/secret-scanning.md
+++ b/translations/ja-JP/content/rest/reference/secret-scanning.md
@@ -9,14 +9,6 @@ versions:
miniTocMaxHeadingLevel: 3
---
-{% data reusables.secret-scanning.api-beta %}
-
-The {% data variables.product.prodname_secret_scanning %} API lets you{% ifversion fpt or ghec or ghes > 3.1 or ghae %}:
-
-- Enable or disable {% data variables.product.prodname_secret_scanning %} for a repository. For more information, see "[Repositories](/rest/reference/repos#update-a-repository)" in the REST API documentation.
-- Retrieve and update {% data variables.product.prodname_secret_scanning %} alerts from a {% ifversion fpt or ghec %}private {% endif %}repository. For futher details, see the sections below.
-{%- else %} retrieve and update {% data variables.product.prodname_secret_scanning %} alerts from a {% ifversion fpt or ghec %}private {% endif %}repository.{% endif %}
-
-{% data variables.product.prodname_secret_scanning %} の詳細については、「[{% data variables.product.prodname_secret_scanning %} について](/code-security/secret-security/about-secret-scanning)」を参照してください。
-
-{% include rest_operations_at_current_path %}
+
diff --git a/translations/ja-JP/content/rest/reference/teams.md b/translations/ja-JP/content/rest/reference/teams.md
index 9eec16ca07a8..ffab63efb66e 100644
--- a/translations/ja-JP/content/rest/reference/teams.md
+++ b/translations/ja-JP/content/rest/reference/teams.md
@@ -13,84 +13,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-この API は、Team の [Organization](/rest/reference/orgs) の、認証済みメンバーのみが利用できます。 OAuth のアクセストークンは、 `read:org` [スコープ](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/)を必要とします。 {% data variables.product.prodname_dotcom %} は、Team の `name` からTeam の `slug` を生成します。
-
-{% for operation in currentRestOperations %}
- {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
-{% endfor %}
-
-## ディスカッション
-
-Team ディスカッション API を使用すると、Team のページに投稿されたディスカッションを取得、作成、編集、削除できます。 Team のディスカッションは、リポジトリやプロジェクトに原生されない会話をするために利用できます。 Team の [Organization](/rest/reference/orgs) に属する全メンバーが、公開のディスカッション投稿を作成や表示できます。 詳細については「[Teamディスカッションについて](//organizations/collaborating-with-your-team/about-team-discussions/)」を参照してください。 ディスカッションの投稿に対するコメントの詳細については、「[Team ディスカッションのコメント API](/rest/reference/teams#discussion-comments)」を参照してください。 この API は、Team の Organization の、認証済みメンバーのみが利用できます。
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'discussions' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## ディスカッションコメント
-
-Team ディスカッションコメント API を使用すると、[Team ディスカッション](/rest/reference/teams#discussions)投稿のコメントを取得、作成、編集、削除できます。 Team の [Organization](/rest/reference/orgs) に属する全メンバーが、公開のディスカッションについたコメントを作成や表示できます。 詳細については「[Teamディスカッションについて](/organizations/collaborating-with-your-team/about-team-discussions/)」を参照してください。 この API は、Team の Organization の、認証済みメンバーのみが利用できます。
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'discussion-comments' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## メンバー
-
-この API は、Team の Organization の、認証済みメンバーのみが利用できます。 OAuth のアクセストークンは、 `read:org` [スコープ](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/)を必要とします。
-
-{% ifversion fpt or ghes or ghec %}
-{% note %}
-
-**ノート: ** Organizationのアイデンティティプロバイダ（Idp）でTeamに同期をセットアップしている場合、Teamのメンバーシップを変更するためのこのAPIを使おうとすると、エラーが返されます。 グループのメンバーシップを管理するためにIdpにアクセスできるなら、GitHubのTeamメンバーシップをアイデンティティプロバイダを通じて管理できます。そうすれば、Organizationで自動的にTeamメンバーの追加や削除が行われます。 詳しい情報については「アイデンティティプロバイダとGitHub間でのTeamの同期」を参照してください。
-
-{% endnote %}
-
-{% endif %}
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'members' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% ifversion ghec or ghae %}
-## External groups
-
-The external groups API allows you to view the external identity provider groups that are available to your organization and manage the connection between external groups and teams in your organization.
-
-この API を使用するには、認証されたユーザーがチームメンテナまたは Team に関連づけられた Organization のコードオーナーである必要があります。
-
-{% ifversion ghec %}
-{% note %}
-
-**ノート:**
-
-- The external groups API is only available for organizations that are part of a enterprise using {% data variables.product.prodname_emus %}. For more information, see "[About Enterprise Managed Users](/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)."
-- If your organization uses team synchronization, you can use the Team Synchronization API. For more information, see "[Team synchronization API](#team-synchronization)."
-
-{% endnote %}
-{% endif %}
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'external-groups' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% endif %}
-
-{% ifversion fpt or ghes or ghec %}
-## Team の同期
-
-Team Synchronization API では、{% data variables.product.product_name %} Team と外部アイデンティティプロバイダ (IdP) グループとの間の接続を管理できます。 この API を使用するには、認証されたユーザーがチームメンテナまたは Team に関連づけられた Organization のコードオーナーである必要があります。 また、認証に使用するトークンも、お使いの IdP (SSO) プロバイダーで使用するための認可を受けている必要があります。 詳しい情報についてはSAML シングルサインオンの Organization で使うために個人アクセストークンを認可するを参照してください。
-
-Team 同期を使用して、IdPを通じて GitHubTeamメンバーを管理できます。 Team Synchronization API を使用するには、チーム同期が有効である必要があります。 詳しい情報については「アイデンティティプロバイダとGitHub間でのTeamの同期」を参照してください。
-
-{% note %}
-
-**Note:** The Team Synchronization API cannot be used with {% data variables.product.prodname_emus %}. To learn more about managing an {% data variables.product.prodname_emu_org %}, see "[External groups API](/enterprise-cloud@latest/rest/reference/teams#external-groups)".
-
-{% endnote %}
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'team-sync' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% endif %}
+
diff --git a/translations/ja-JP/content/rest/reference/users.md b/translations/ja-JP/content/rest/reference/users.md
index b0162d6cabb1..73db1fa21681 100644
--- a/translations/ja-JP/content/rest/reference/users.md
+++ b/translations/ja-JP/content/rest/reference/users.md
@@ -13,48 +13,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-ユーザ API のリソースの多くには、現在認証されているユーザについての情報を取得するためのショートカットがあります。 リクエスト URL に `{username}` パラメータが含まれていない場合、レスポンスはログインしているユーザに対して行われます (リクエストで [認証情報](/rest/overview/resources-in-the-rest-api#authentication) を渡す必要があります)。{% ifversion fpt or ghes or ghec %}ユーザが 2 要素認証を有効にしているかなど、その他の個人情報は、基本認証または `user` スコープ付きで OAuth 認証されている場合に含まれます。{% endif %}
-
-{% for operation in currentRestOperations %}
- {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
-{% endfor %}
-
-{% ifversion fpt or ghec %}
-## ユーザのブロック
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'blocking' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% endif %}
-
-{% ifversion fpt or ghes or ghec %}
-## Emails
-
-API を通じたメールアドレスの管理には、基本認証、またはエンドポイントに対する正しいスコープの付いた OAuth で認証する必要があります。
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'emails' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% endif %}
-
-## フォロワー
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'followers' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## Git SSHキー
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'keys' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## GPG keys
-
-`public_key` レスポンスフィールドで返されるデータは、GPG 形式のキーではありません。 ユーザが GPG キーをアップロードすると、そのキーは解析され、暗号化された公開鍵が抽出、保存されます。 この暗号鍵が、このページの API によって返されるものです。 この鍵は、GPG のようなプログラムで直接使用するには適していません。
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'gpg-keys' %}{% include rest_operation %}{% endif %}
-{% endfor %}
+
diff --git a/translations/ja-JP/content/rest/reference/webhooks.md b/translations/ja-JP/content/rest/reference/webhooks.md
index 916985728a6c..2afa687c1c87 100644
--- a/translations/ja-JP/content/rest/reference/webhooks.md
+++ b/translations/ja-JP/content/rest/reference/webhooks.md
@@ -12,83 +12,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-Repository webhooks allow you to receive HTTP `POST` payloads whenever certain events happen in a repository. {% data reusables.webhooks.webhooks-rest-api-links %}
-
-Organization のすべてのリポジトリからイベントを受信するため単一の webhook を設定する場合は、[Organization Webhooks](/rest/reference/orgs#webhooks) の API ドキュメントを参照してください。
-
-In addition to the REST API, {% data variables.product.prodname_dotcom %} can also serve as a [PubSubHubbub](#pubsubhubbub) hub for repositories.
-
-{% for operation in currentRestOperations %}
- {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
-{% endfor %}
-
-## リポジトリ webhook
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'repos' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## Repository webhook configuration
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'repo-config' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## Repository webhook deliveries
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'repo-deliveries' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## webhook の受信
-
-{% data variables.product.product_name %} で webhook ペイロードを送信するには、インターネットからサーバーにアクセスできる必要があります。 暗号化されたペイロードを HTTPS 経由で送信できるように、SSL の使用も強く推奨します。
-
-### webhook ヘッダー
-
-{% data variables.product.product_name %} は、イベントタイプとペイロード識別子を区別するために、複数の HTTP ヘッダーも送信します。 詳細は「[webhook ヘッダー](/developers/webhooks-and-events/webhook-events-and-payloads#delivery-headers)」を参照してください。
-
-## PubSubHubbub
-
-GitHub は、すべてのリポジトリに対する [PubSubHubbub](https://github.com/pubsubhubbub/PubSubHubbub) のハブとして機能することもできます。 PSHB はシンプルな公開/サブスクライブプロトコルで、トピックが更新されたときにサーバーが更新を受信できるよう登録できます。 更新は HTTP POST リクエストでコールバック URL に送信されます。 GitHub リポジトリのプッシュに対するトピック URL のフォーマットは以下の通りです。
-
-`https://github.com/{owner}/{repo}/events/{event}`
-
-イベントには、任意の使用可能な webhook イベントを指定します。 詳しい情報については、「[webhook イベントとペイロード](/developers/webhooks-and-events/webhook-events-and-payloads)」を参照してください。
-
-### レスポンスのフォーマット
-
-デフォルトのフォーマットは、[既存の post-receive フックから予想できます](/post-receive-hooks/)。すなわち、POST で `payload` パラメータとして送信される JSON の本文です。 また、`Accept` ヘッダまたは `.json` 拡張子で、Raw 形式の JSON 本文を受信するよう指定できます。
-
- Accept: application/json
- https://github.com/{owner}/{repo}/events/push.json
-
-### コールバック URL
-
-コールバック URL は `http://` プロトコルを使用できます。
-
- # Send updates to postbin.org
- http://postbin.org/123
-
-### サブスクライブ
-
-GitHub PubSubHubbub のエンドポイントは `{% data variables.product.api_url_code %}/hub` です。 curl でリクエストに成功すると、以下のように表示されます。
-
-``` shell
-curl -u "user" -i \
- {% data variables.product.api_url_pre %}/hub \
- -F "hub.mode=subscribe" \
- -F "hub.topic=https://github.com/{owner}/{repo}/events/push" \
- -F "hub.callback=http://postbin.org/123"
-```
-
-PubSubHubbub リクエストは複数回送信できます。 フックがすでに存在する場合は、リクエストに従って変更されます。
-
-#### パラメータ
-
-| 名前 | 種類 | 説明 |
-| -------------- | -------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `hub.mode` | `string` | **必須**。 `subscribe` または `unsubscribe`。 |
-| `hub.topic` | `string` | **必須**。 GitHub リポジトリがサブスクライブする URI。 パスのフォーマットは `/{owner}/{repo}/events/{event}` としてください。 |
-| `hub.callback` | `string` | トピックの更新を受信する URI。 |
-| `hub.secret` | `string` | 送信する本文コンテンツの ハッシュ署名を生成する共有秘密鍵。 GitHubからきたプッシュを、そのリクエストのボディを{% ifversion fpt or ghes > 2.22 or ghec %}`X-Hub-Signature`もしくは`X-Hub-Signature-256`ヘッダ{% elsif ghes < 3.0 %}`X-Hub-Signature`ヘッダ{% elsif ghae %}`X-Hub-Signature-256`ヘッダ{% endif %}と比較して、検証できます。 詳細は、 [PubSubHubbub のドキュメント](https://pubsubhubbub.github.io/PubSubHubbub/pubsubhubbub-core-0.4.html#authednotify)を参照してください。 |
+
diff --git a/translations/ja-JP/data/graphql/ghae/graphql_upcoming_changes.public-ghae.yml b/translations/ja-JP/data/graphql/ghae/graphql_upcoming_changes.public-ghae.yml
index 5a95be5bb4c2..0fc739eed556 100644
--- a/translations/ja-JP/data/graphql/ghae/graphql_upcoming_changes.public-ghae.yml
+++ b/translations/ja-JP/data/graphql/ghae/graphql_upcoming_changes.public-ghae.yml
@@ -112,3 +112,17 @@ upcoming_changes:
date: '2021-10-01T00:00:00+00:00'
criticality: 破壊的
owner: synthead
+ -
+ location: PullRequest.viewerCanOverrideMergeQueue
+ description: '`viewerCanOverrideMergeQueue` will be removed. Use PullRequest.viewerCanMergeAsAdmin instead.'
+ reason: '`viewer_can_override_merge_queue` will be removed'
+ date: '2022-04-01'
+ criticality: 破壊的
+ owner: cbeaman
+ -
+ location: Repository.defaultMergeQueue
+ description: '`defaultMergeQueue` will be removed. Use `Repository.mergeQueue` instead.'
+ reason: '`defaultMergeQueue` will be removed.'
+ date: '2022-04-01'
+ criticality: 破壊的
+ owner: colinshum
diff --git a/translations/ja-JP/data/graphql/ghec/graphql_upcoming_changes.public.yml b/translations/ja-JP/data/graphql/ghec/graphql_upcoming_changes.public.yml
index c234006e0861..d54fd9ec40f3 100644
--- a/translations/ja-JP/data/graphql/ghec/graphql_upcoming_changes.public.yml
+++ b/translations/ja-JP/data/graphql/ghec/graphql_upcoming_changes.public.yml
@@ -126,3 +126,24 @@ upcoming_changes:
date: '2021-10-01T00:00:00+00:00'
criticality: 破壊的
owner: synthead
+ -
+ location: PullRequest.viewerCanOverrideMergeQueue
+ description: '`viewerCanOverrideMergeQueue` will be removed. Use PullRequest.viewerCanMergeAsAdmin instead.'
+ reason: '`viewer_can_override_merge_queue` will be removed'
+ date: '2022-04-01'
+ criticality: 破壊的
+ owner: cbeaman
+ -
+ location: Repository.defaultMergeQueue
+ description: '`defaultMergeQueue` will be removed. Use `Repository.mergeQueue` instead.'
+ reason: '`defaultMergeQueue` will be removed.'
+ date: '2022-04-01'
+ criticality: 破壊的
+ owner: colinshum
+ -
+ location: Query.sponsorables.dependencyEcosystem
+ description: '`dependencyEcosystem` will be removed. Use the ecosystem argument instead.'
+ reason: The type is switching from SecurityAdvisoryEcosystem to DependencyGraphEcosystem.
+ date: '2022-07-01T00:00:00+00:00'
+ criticality: 破壊的
+ owner: cheshire137
diff --git a/translations/ja-JP/data/graphql/graphql_upcoming_changes.public.yml b/translations/ja-JP/data/graphql/graphql_upcoming_changes.public.yml
index c234006e0861..d54fd9ec40f3 100644
--- a/translations/ja-JP/data/graphql/graphql_upcoming_changes.public.yml
+++ b/translations/ja-JP/data/graphql/graphql_upcoming_changes.public.yml
@@ -126,3 +126,24 @@ upcoming_changes:
date: '2021-10-01T00:00:00+00:00'
criticality: 破壊的
owner: synthead
+ -
+ location: PullRequest.viewerCanOverrideMergeQueue
+ description: '`viewerCanOverrideMergeQueue` will be removed. Use PullRequest.viewerCanMergeAsAdmin instead.'
+ reason: '`viewer_can_override_merge_queue` will be removed'
+ date: '2022-04-01'
+ criticality: 破壊的
+ owner: cbeaman
+ -
+ location: Repository.defaultMergeQueue
+ description: '`defaultMergeQueue` will be removed. Use `Repository.mergeQueue` instead.'
+ reason: '`defaultMergeQueue` will be removed.'
+ date: '2022-04-01'
+ criticality: 破壊的
+ owner: colinshum
+ -
+ location: Query.sponsorables.dependencyEcosystem
+ description: '`dependencyEcosystem` will be removed. Use the ecosystem argument instead.'
+ reason: The type is switching from SecurityAdvisoryEcosystem to DependencyGraphEcosystem.
+ date: '2022-07-01T00:00:00+00:00'
+ criticality: 破壊的
+ owner: cheshire137
diff --git a/translations/ja-JP/data/reusables/github-actions/actions-activity-types.md b/translations/ja-JP/data/reusables/actions/actions-activity-types.md
similarity index 100%
rename from translations/ja-JP/data/reusables/github-actions/actions-activity-types.md
rename to translations/ja-JP/data/reusables/actions/actions-activity-types.md
diff --git a/translations/ja-JP/data/reusables/github-actions/actions-billing.md b/translations/ja-JP/data/reusables/actions/actions-billing.md
similarity index 100%
rename from translations/ja-JP/data/reusables/github-actions/actions-billing.md
rename to translations/ja-JP/data/reusables/actions/actions-billing.md
diff --git a/translations/ja-JP/data/reusables/github-actions/actions-do-not-trigger-workflows.md b/translations/ja-JP/data/reusables/actions/actions-do-not-trigger-workflows.md
similarity index 100%
rename from translations/ja-JP/data/reusables/github-actions/actions-do-not-trigger-workflows.md
rename to translations/ja-JP/data/reusables/actions/actions-do-not-trigger-workflows.md
diff --git a/translations/ja-JP/data/reusables/github-actions/actions-filters.md b/translations/ja-JP/data/reusables/actions/actions-filters.md
similarity index 100%
rename from translations/ja-JP/data/reusables/github-actions/actions-filters.md
rename to translations/ja-JP/data/reusables/actions/actions-filters.md
diff --git a/translations/ja-JP/data/reusables/github-actions/actions-multiple-types.md b/translations/ja-JP/data/reusables/actions/actions-multiple-types.md
similarity index 100%
rename from translations/ja-JP/data/reusables/github-actions/actions-multiple-types.md
rename to translations/ja-JP/data/reusables/actions/actions-multiple-types.md
diff --git a/translations/ja-JP/data/reusables/actions/actions-on-examples.md b/translations/ja-JP/data/reusables/actions/actions-on-examples.md
new file mode 100644
index 000000000000..80c7fc67d29b
--- /dev/null
+++ b/translations/ja-JP/data/reusables/actions/actions-on-examples.md
@@ -0,0 +1,19 @@
+### Using a single event
+
+{% data reusables.actions.on-single-example %}
+
+### Using multiple events
+
+{% data reusables.actions.on-multiple-example %}
+
+### Using activity types
+
+{% data reusables.actions.actions-activity-types %}
+
+### Using filters
+
+{% data reusables.actions.actions-filters %}
+
+### Using activity types and filters with multiple events
+
+{% data reusables.actions.actions-multiple-types %}
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/github-actions/actions-spending-limit-brief.md b/translations/ja-JP/data/reusables/actions/actions-spending-limit-brief.md
similarity index 100%
rename from translations/ja-JP/data/reusables/github-actions/actions-spending-limit-brief.md
rename to translations/ja-JP/data/reusables/actions/actions-spending-limit-brief.md
diff --git a/translations/ja-JP/data/reusables/github-actions/actions-spending-limit-detailed.md b/translations/ja-JP/data/reusables/actions/actions-spending-limit-detailed.md
similarity index 88%
rename from translations/ja-JP/data/reusables/github-actions/actions-spending-limit-detailed.md
rename to translations/ja-JP/data/reusables/actions/actions-spending-limit-detailed.md
index 1f38fcef1cef..d3d3b3d52bc4 100644
--- a/translations/ja-JP/data/reusables/github-actions/actions-spending-limit-detailed.md
+++ b/translations/ja-JP/data/reusables/actions/actions-spending-limit-detailed.md
@@ -1,3 +1,3 @@
-{% data reusables.github-actions.actions-spending-limit-brief %}
+{% data reusables.actions.actions-spending-limit-brief %}
If you have an unlimited spending limit or a spending limit set higher than $0 USD, you will be billed for any additional minutes or storage beyond the included amounts in your account, also called overages. {% data variables.product.prodname_dotcom %}は、ワークフローが実行されたリポジトリを所有するアカウントに利用分を課金します。 アカウントのクーポンは、{% data variables.product.prodname_actions %}の超過分には適用されません。
diff --git a/translations/ja-JP/data/reusables/github-actions/actions-unused-labels.md b/translations/ja-JP/data/reusables/actions/actions-unused-labels.md
similarity index 100%
rename from translations/ja-JP/data/reusables/github-actions/actions-unused-labels.md
rename to translations/ja-JP/data/reusables/actions/actions-unused-labels.md
diff --git a/translations/ja-JP/data/reusables/github-actions/artifact-log-retention-statement.md b/translations/ja-JP/data/reusables/actions/artifact-log-retention-statement.md
similarity index 100%
rename from translations/ja-JP/data/reusables/github-actions/artifact-log-retention-statement.md
rename to translations/ja-JP/data/reusables/actions/artifact-log-retention-statement.md
diff --git a/translations/ja-JP/data/reusables/github-actions/branch-paths-filter.md b/translations/ja-JP/data/reusables/actions/branch-paths-filter.md
similarity index 100%
rename from translations/ja-JP/data/reusables/github-actions/branch-paths-filter.md
rename to translations/ja-JP/data/reusables/actions/branch-paths-filter.md
diff --git a/translations/ja-JP/data/reusables/github-actions/branch-requirement.md b/translations/ja-JP/data/reusables/actions/branch-requirement.md
similarity index 100%
rename from translations/ja-JP/data/reusables/github-actions/branch-requirement.md
rename to translations/ja-JP/data/reusables/actions/branch-requirement.md
diff --git a/translations/ja-JP/data/reusables/github-actions/change-retention-period-for-artifacts-logs.md b/translations/ja-JP/data/reusables/actions/change-retention-period-for-artifacts-logs.md
similarity index 100%
rename from translations/ja-JP/data/reusables/github-actions/change-retention-period-for-artifacts-logs.md
rename to translations/ja-JP/data/reusables/actions/change-retention-period-for-artifacts-logs.md
diff --git a/translations/ja-JP/data/reusables/github-actions/contacting-support.md b/translations/ja-JP/data/reusables/actions/contacting-support.md
similarity index 100%
rename from translations/ja-JP/data/reusables/github-actions/contacting-support.md
rename to translations/ja-JP/data/reusables/actions/contacting-support.md
diff --git a/translations/ja-JP/data/reusables/github-actions/container-jobs-intro.md b/translations/ja-JP/data/reusables/actions/container-jobs-intro.md
similarity index 100%
rename from translations/ja-JP/data/reusables/github-actions/container-jobs-intro.md
rename to translations/ja-JP/data/reusables/actions/container-jobs-intro.md
diff --git a/translations/ja-JP/data/reusables/github-actions/context-injection-warning.md b/translations/ja-JP/data/reusables/actions/context-injection-warning.md
similarity index 100%
rename from translations/ja-JP/data/reusables/github-actions/context-injection-warning.md
rename to translations/ja-JP/data/reusables/actions/context-injection-warning.md
diff --git a/translations/ja-JP/data/reusables/github-actions/copy-workflow-file.md b/translations/ja-JP/data/reusables/actions/copy-workflow-file.md
similarity index 100%
rename from translations/ja-JP/data/reusables/github-actions/copy-workflow-file.md
rename to translations/ja-JP/data/reusables/actions/copy-workflow-file.md
diff --git a/translations/ja-JP/data/reusables/github-actions/defaults-override.md b/translations/ja-JP/data/reusables/actions/defaults-override.md
similarity index 100%
rename from translations/ja-JP/data/reusables/github-actions/defaults-override.md
rename to translations/ja-JP/data/reusables/actions/defaults-override.md
diff --git a/translations/ja-JP/data/reusables/github-actions/disabled-actions-description.md b/translations/ja-JP/data/reusables/actions/disabled-actions-description.md
similarity index 100%
rename from translations/ja-JP/data/reusables/github-actions/disabled-actions-description.md
rename to translations/ja-JP/data/reusables/actions/disabled-actions-description.md
diff --git a/translations/ja-JP/data/reusables/github-actions/disabling-github-actions.md b/translations/ja-JP/data/reusables/actions/disabling-github-actions.md
similarity index 100%
rename from translations/ja-JP/data/reusables/github-actions/disabling-github-actions.md
rename to translations/ja-JP/data/reusables/actions/disabling-github-actions.md
diff --git a/translations/ja-JP/data/reusables/github-actions/docker-container-os-support.md b/translations/ja-JP/data/reusables/actions/docker-container-os-support.md
similarity index 100%
rename from translations/ja-JP/data/reusables/github-actions/docker-container-os-support.md
rename to translations/ja-JP/data/reusables/actions/docker-container-os-support.md
diff --git a/translations/ja-JP/data/reusables/github-actions/dockerfile-guidelines.md b/translations/ja-JP/data/reusables/actions/dockerfile-guidelines.md
similarity index 100%
rename from translations/ja-JP/data/reusables/github-actions/dockerfile-guidelines.md
rename to translations/ja-JP/data/reusables/actions/dockerfile-guidelines.md
diff --git a/translations/ja-JP/data/reusables/github-actions/enabled-actions-description.md b/translations/ja-JP/data/reusables/actions/enabled-actions-description.md
similarity index 100%
rename from translations/ja-JP/data/reusables/github-actions/enabled-actions-description.md
rename to translations/ja-JP/data/reusables/actions/enabled-actions-description.md
diff --git a/translations/ja-JP/data/reusables/github-actions/enabled-local-github-actions.md b/translations/ja-JP/data/reusables/actions/enabled-local-github-actions.md
similarity index 100%
rename from translations/ja-JP/data/reusables/github-actions/enabled-local-github-actions.md
rename to translations/ja-JP/data/reusables/actions/enabled-local-github-actions.md
diff --git a/translations/ja-JP/data/reusables/github-actions/enterprise-billing-details.md b/translations/ja-JP/data/reusables/actions/enterprise-billing-details.md
similarity index 100%
rename from translations/ja-JP/data/reusables/github-actions/enterprise-billing-details.md
rename to translations/ja-JP/data/reusables/actions/enterprise-billing-details.md
diff --git a/translations/ja-JP/data/reusables/github-actions/example-github-runner.md b/translations/ja-JP/data/reusables/actions/example-github-runner.md
similarity index 100%
rename from translations/ja-JP/data/reusables/github-actions/example-github-runner.md
rename to translations/ja-JP/data/reusables/actions/example-github-runner.md
diff --git a/translations/ja-JP/data/reusables/github-actions/expression-syntax-if.md b/translations/ja-JP/data/reusables/actions/expression-syntax-if.md
similarity index 100%
rename from translations/ja-JP/data/reusables/github-actions/expression-syntax-if.md
rename to translations/ja-JP/data/reusables/actions/expression-syntax-if.md
diff --git a/translations/ja-JP/data/reusables/github-actions/forked-write-permission.md b/translations/ja-JP/data/reusables/actions/forked-write-permission.md
similarity index 52%
rename from translations/ja-JP/data/reusables/github-actions/forked-write-permission.md
rename to translations/ja-JP/data/reusables/actions/forked-write-permission.md
index 3ff78552d89a..725130f00178 100644
--- a/translations/ja-JP/data/reusables/github-actions/forked-write-permission.md
+++ b/translations/ja-JP/data/reusables/actions/forked-write-permission.md
@@ -1 +1 @@
-`permissions`キーを使って、フォークされたリポジトリの読み取り権限の付与や削除ができますが、通常は書き込みアクセス権を付与することはできません。 この動作の例外としては、管理ユーザが{% data variables.product.prodname_actions %}の設定で**Send write tokens to workflows from pull requests（Pull Requestからワークフローに書き込みトークンを送る）**を選択している場合があります。 For more information, see "[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#enabling-workflows-for-private-repository-forks)."
+`permissions`キーを使って、フォークされたリポジトリの読み取り権限の付与や削除ができますが、通常は書き込みアクセス権を付与することはできません。 この動作の例外としては、管理ユーザが{% data variables.product.prodname_actions %}の設定で**Send write tokens to workflows from pull requests（Pull Requestからワークフローに書き込みトークンを送る）**を選択している場合があります。 詳しい情報については、「[リポジトリの {% data variables.product.prodname_actions %} 設定の管理](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#enabling-workflows-for-private-repository-forks)」を参照してください。
diff --git a/translations/ja-JP/data/reusables/actions/ghes-actions-not-enabled-by-default.md b/translations/ja-JP/data/reusables/actions/ghes-actions-not-enabled-by-default.md
new file mode 100644
index 000000000000..04afb9489221
--- /dev/null
+++ b/translations/ja-JP/data/reusables/actions/ghes-actions-not-enabled-by-default.md
@@ -0,0 +1 @@
+{% data variables.product.prodname_actions %} is not enabled for {% data variables.product.prodname_ghe_server %} by default.
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/github-actions/github-context-warning.md b/translations/ja-JP/data/reusables/actions/github-context-warning.md
similarity index 100%
rename from translations/ja-JP/data/reusables/github-actions/github-context-warning.md
rename to translations/ja-JP/data/reusables/actions/github-context-warning.md
diff --git a/translations/ja-JP/data/reusables/github-actions/github-hosted-runners-check-concurrency.md b/translations/ja-JP/data/reusables/actions/github-hosted-runners-check-concurrency.md
similarity index 100%
rename from translations/ja-JP/data/reusables/github-actions/github-hosted-runners-check-concurrency.md
rename to translations/ja-JP/data/reusables/actions/github-hosted-runners-check-concurrency.md
diff --git a/translations/ja-JP/data/reusables/github-actions/github-hosted-runners-navigate-to-repo-org-enterprise.md b/translations/ja-JP/data/reusables/actions/github-hosted-runners-navigate-to-repo-org-enterprise.md
similarity index 100%
rename from translations/ja-JP/data/reusables/github-actions/github-hosted-runners-navigate-to-repo-org-enterprise.md
rename to translations/ja-JP/data/reusables/actions/github-hosted-runners-navigate-to-repo-org-enterprise.md
diff --git a/translations/ja-JP/data/reusables/github-actions/github-hosted-runners-table-entry.md b/translations/ja-JP/data/reusables/actions/github-hosted-runners-table-entry.md
similarity index 100%
rename from translations/ja-JP/data/reusables/github-actions/github-hosted-runners-table-entry.md
rename to translations/ja-JP/data/reusables/actions/github-hosted-runners-table-entry.md
diff --git a/translations/pt-BR/data/reusables/github-actions/github-token-available-permissions.md b/translations/ja-JP/data/reusables/actions/github-token-available-permissions.md
similarity index 67%
rename from translations/pt-BR/data/reusables/github-actions/github-token-available-permissions.md
rename to translations/ja-JP/data/reusables/actions/github-token-available-permissions.md
index c81659732152..5af40196917d 100644
--- a/translations/pt-BR/data/reusables/github-actions/github-token-available-permissions.md
+++ b/translations/ja-JP/data/reusables/actions/github-token-available-permissions.md
@@ -1,4 +1,4 @@
-Valores de acesso e escopos disponíveis:
+Available scopes and access values:
```yaml
permissions:
@@ -17,9 +17,9 @@ permissions:
statuses: read|write|none
```
-Se você especificar o acesso para qualquer um desses escopos, todos os que não são especificados são definidos como `nenhum`.
+If you specify the access for any of these scopes, all of those that are not specified are set to `none`.
-Você pode usar a sintaxe a seguir para definir o acesso de leitura ou gravação para todos os escopos disponíveis:
+You can use the following syntax to define read or write access for all of the available scopes:
```yaml
permissions: read-all|write-all
diff --git a/translations/ja-JP/data/reusables/github-actions/github-token-permissions.md b/translations/ja-JP/data/reusables/actions/github-token-permissions.md
similarity index 100%
rename from translations/ja-JP/data/reusables/github-actions/github-token-permissions.md
rename to translations/ja-JP/data/reusables/actions/github-token-permissions.md
diff --git a/translations/ja-JP/data/reusables/github-actions/github_token-input-example.md b/translations/ja-JP/data/reusables/actions/github_token-input-example.md
similarity index 100%
rename from translations/ja-JP/data/reusables/github-actions/github_token-input-example.md
rename to translations/ja-JP/data/reusables/actions/github_token-input-example.md
diff --git a/translations/ja-JP/data/reusables/github-actions/gradle-workflow-steps.md b/translations/ja-JP/data/reusables/actions/gradle-workflow-steps.md
similarity index 100%
rename from translations/ja-JP/data/reusables/github-actions/gradle-workflow-steps.md
rename to translations/ja-JP/data/reusables/actions/gradle-workflow-steps.md
diff --git a/translations/ja-JP/data/reusables/github-actions/hosted-runner-configure-runner-group-access.md b/translations/ja-JP/data/reusables/actions/hosted-runner-configure-runner-group-access.md
similarity index 100%
rename from translations/ja-JP/data/reusables/github-actions/hosted-runner-configure-runner-group-access.md
rename to translations/ja-JP/data/reusables/actions/hosted-runner-configure-runner-group-access.md
diff --git a/translations/ja-JP/data/reusables/github-actions/hosted-runner-labels-view-assigned-labels.md b/translations/ja-JP/data/reusables/actions/hosted-runner-labels-view-assigned-labels.md
similarity index 100%
rename from translations/ja-JP/data/reusables/github-actions/hosted-runner-labels-view-assigned-labels.md
rename to translations/ja-JP/data/reusables/actions/hosted-runner-labels-view-assigned-labels.md
diff --git a/translations/ja-JP/data/reusables/github-actions/hosted-runner-list-group.md b/translations/ja-JP/data/reusables/actions/hosted-runner-list-group.md
similarity index 100%
rename from translations/ja-JP/data/reusables/github-actions/hosted-runner-list-group.md
rename to translations/ja-JP/data/reusables/actions/hosted-runner-list-group.md
diff --git a/translations/ja-JP/data/reusables/github-actions/hosted-runner-list.md b/translations/ja-JP/data/reusables/actions/hosted-runner-list.md
similarity index 100%
rename from translations/ja-JP/data/reusables/github-actions/hosted-runner-list.md
rename to translations/ja-JP/data/reusables/actions/hosted-runner-list.md
diff --git a/translations/ja-JP/data/reusables/github-actions/invalid-workflow-files.md b/translations/ja-JP/data/reusables/actions/invalid-workflow-files.md
similarity index 100%
rename from translations/ja-JP/data/reusables/github-actions/invalid-workflow-files.md
rename to translations/ja-JP/data/reusables/actions/invalid-workflow-files.md
diff --git a/translations/ja-JP/data/reusables/actions/ip-allow-list-self-hosted-runners.md b/translations/ja-JP/data/reusables/actions/ip-allow-list-self-hosted-runners.md
new file mode 100644
index 000000000000..46d094744729
--- /dev/null
+++ b/translations/ja-JP/data/reusables/actions/ip-allow-list-self-hosted-runners.md
@@ -0,0 +1,11 @@
+{% ifversion ghae %}
+セルフホストランナーが{% data variables.product.prodname_dotcom %}と通信できるようにするためには、セルフホストランナーのIPアドレスもしくはIPアドレスの範囲をIP許可リストに追加してください。 詳しい情報については「[許可されたIPアドレスの追加](#adding-an-allowed-ip-address)」を参照してください。
+{% else %}
+{% warning %}
+
+**警告**: IP許可リストを使い、{% data variables.product.prodname_actions %}も使いたい場合には、セルフホストランナーを使わなければなりません。 詳しい情報については「[自分のランナーをホストする](/actions/automating-your-workflow-with-github-actions/about-self-hosted-runners)」を参照してください。
+
+{% endwarning %}
+
+セルフホストランナーが{% data variables.product.prodname_dotcom %}と通信できるようにするためには、セルフホストランナーのIPアドレスもしくはIPアドレスの範囲をIP許可リストに追加してください。 詳しい情報については「[許可されたIPアドレスの追加](#adding-an-allowed-ip-address)」を参照してください。
+{% endif %}
diff --git a/translations/ja-JP/data/reusables/github-actions/java-jvm-architecture.md b/translations/ja-JP/data/reusables/actions/java-jvm-architecture.md
similarity index 100%
rename from translations/ja-JP/data/reusables/github-actions/java-jvm-architecture.md
rename to translations/ja-JP/data/reusables/actions/java-jvm-architecture.md
diff --git a/translations/ja-JP/data/reusables/actions/jobs/section-assigning-permissions-to-jobs-specific.md b/translations/ja-JP/data/reusables/actions/jobs/section-assigning-permissions-to-jobs-specific.md
index fbff042d4ed0..c78fbb4834fa 100644
--- a/translations/ja-JP/data/reusables/actions/jobs/section-assigning-permissions-to-jobs-specific.md
+++ b/translations/ja-JP/data/reusables/actions/jobs/section-assigning-permissions-to-jobs-specific.md
@@ -2,8 +2,8 @@ For a specific job, you can use `jobs..permissions` to modify the defaul
ジョブ定義内で権限を指定することで、必要に応じて、ジョブごとに `GITHUB_TOKEN` に異なる権限のセットを設定できます。 または、ワークフロー内のすべてのジョブの権限を指定することもできます。 ワークフローレベルでの権限の定義については、 [`permissions`](/actions/using-workflows/workflow-syntax-for-github-actions#permissions) を参照してください。
-{% data reusables.github-actions.github-token-available-permissions %}
-{% data reusables.github-actions.forked-write-permission %}
+{% data reusables.actions.github-token-available-permissions %}
+{% data reusables.actions.forked-write-permission %}
#### Example: Setting permissions for a specific job
diff --git a/translations/ja-JP/data/reusables/actions/jobs/section-assigning-permissions-to-jobs.md b/translations/ja-JP/data/reusables/actions/jobs/section-assigning-permissions-to-jobs.md
index 979890c3c9d4..c765df4b6ede 100644
--- a/translations/ja-JP/data/reusables/actions/jobs/section-assigning-permissions-to-jobs.md
+++ b/translations/ja-JP/data/reusables/actions/jobs/section-assigning-permissions-to-jobs.md
@@ -2,8 +2,8 @@ You can use `permissions` to modify the default permissions granted to the `GITH
`permissions` は、最上位キーとしてワークフロー内のすべてのジョブに適用するために、または特定のジョブ内で使用できます。 特定のジョブ内に `permissions` キーを追加すると、`GITHUB_TOKEN` を使用するそのジョブ内のすべてのアクションと実行コマンドが、指定したアクセス権を取得します。 詳しい情報については、[`jobs..permissions`](/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idpermissions) を参照してください。
-{% data reusables.github-actions.github-token-available-permissions %}
-{% data reusables.github-actions.forked-write-permission %}
+{% data reusables.actions.github-token-available-permissions %}
+{% data reusables.actions.forked-write-permission %}
### Example: Assigning permissions to GITHUB_TOKEN
diff --git a/translations/ja-JP/data/reusables/actions/jobs/section-choosing-the-runner-for-a-job.md b/translations/ja-JP/data/reusables/actions/jobs/section-choosing-the-runner-for-a-job.md
index 9c00c9154787..b0cfe9970318 100644
--- a/translations/ja-JP/data/reusables/actions/jobs/section-choosing-the-runner-for-a-job.md
+++ b/translations/ja-JP/data/reusables/actions/jobs/section-choosing-the-runner-for-a-job.md
@@ -10,7 +10,7 @@ Use `jobs..runs-on` to define the type of machine to run the job on. {%
利用可能な{% data variables.product.prodname_dotcom %}ホストランナーの種類は以下のとおりです。
-{% data reusables.github-actions.supported-github-runners %}
+{% data reusables.actions.supported-github-runners %}
#### Example: Specifying an operating system
@@ -27,7 +27,7 @@ runs-on: ubuntu-latest
{% data reusables.actions.ae-self-hosted-runners-notice %}
-{% data reusables.github-actions.self-hosted-runner-labels-runs-on %}
+{% data reusables.actions.self-hosted-runner-labels-runs-on %}
#### Example: Using labels for runner selection
diff --git a/translations/ja-JP/data/reusables/actions/jobs/section-using-a-build-matrix-for-your-jobs-matrix.md b/translations/ja-JP/data/reusables/actions/jobs/section-using-a-build-matrix-for-your-jobs-matrix.md
index ca261d36f744..6ed6250ebc36 100644
--- a/translations/ja-JP/data/reusables/actions/jobs/section-using-a-build-matrix-for-your-jobs-matrix.md
+++ b/translations/ja-JP/data/reusables/actions/jobs/section-using-a-build-matrix-for-your-jobs-matrix.md
@@ -1,7 +1,7 @@
Use `jobs..strategy.matrix` to define a matrix of different job configurations. マトリックスによって、単一のジョブの定義内の変数の置き換えを行い、複数のジョブを作成できるようになります。 たとえば、マトリックスを使って複数のサポートされているバージョンのプログラミング言語、オペレーティングシステム、ツールに対するジョブを作成できます。 マトリックスは、ジョブの設定を再利用し、設定した各マトリクスに対してジョブを作成します。
-{% data reusables.github-actions.usage-matrix-limits %}
+{% data reusables.actions.usage-matrix-limits %}
`matrix`内で定義した各オプションは、キーと値を持ちます。 定義したキーは`matrix`コンテキスト中の属性となり、ワークフローファイルの他のエリア内のプロパティを参照できます。 たとえば、オペレーティングシステムの配列を含む`os`というキーを定義したなら、`matrix.os`属性を`runs-on`キーワードの値として使い、それぞれのオペレーティングシステムに対するジョブを作成できます。 詳細については、「[コンテキスト](/actions/learn-github-actions/contexts)」を参照してください。
@@ -123,4 +123,4 @@ strategy:
それぞれのテストの組み合わせに、`include`キーを使ってカスタムの環境変数を追加できます。 そして、後のステップでそのカスタムの環境変数を参照できます。
-{% data reusables.github-actions.matrix-variable-example %}
+{% data reusables.actions.matrix-variable-example %}
diff --git a/translations/ja-JP/data/reusables/actions/jobs/section-using-conditions-to-control-job-execution.md b/translations/ja-JP/data/reusables/actions/jobs/section-using-conditions-to-control-job-execution.md
index 996892dde1e6..0cbda18e93bf 100644
--- a/translations/ja-JP/data/reusables/actions/jobs/section-using-conditions-to-control-job-execution.md
+++ b/translations/ja-JP/data/reusables/actions/jobs/section-using-conditions-to-control-job-execution.md
@@ -1,6 +1,6 @@
You can use the `jobs..if` conditional to prevent a job from running unless a condition is met. 条件文を作成するには、サポートされている任意のコンテキストや式が使えます。
-{% data reusables.github-actions.expression-syntax-if %} For more information, see "[Expressions](/actions/learn-github-actions/expressions)."
+{% data reusables.actions.expression-syntax-if %} For more information, see "[Expressions](/actions/learn-github-actions/expressions)."
### Example: Only run job for specific repository
diff --git a/translations/ja-JP/data/reusables/actions/jobs/setting-default-values-for-jobs-defaults-job-run.md b/translations/ja-JP/data/reusables/actions/jobs/setting-default-values-for-jobs-defaults-job-run.md
index 8e569b26d967..0bdfbacb30b7 100644
--- a/translations/ja-JP/data/reusables/actions/jobs/setting-default-values-for-jobs-defaults-job-run.md
+++ b/translations/ja-JP/data/reusables/actions/jobs/setting-default-values-for-jobs-defaults-job-run.md
@@ -2,7 +2,7 @@ Use `jobs..defaults.run` to provide default `shell` and `working-directo
ジョブ中のすべての[`run`](/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idstepsrun)ステップにデフォルトの`shell`及び`working-directory`を提供できます。 ワークフロー全体について`run`のためのデフォルト設定を設定することもできます。 詳しい情報については[`jobs.defaults.run`](/actions/using-workflows/workflow-syntax-for-github-actions#defaultsrun)を参照してください。 このキーワード中では、コンテキストや式を使うことはできません。
-{% data reusables.github-actions.defaults-override %}
+{% data reusables.actions.defaults-override %}
#### Example: Setting default `run` step options for a job
diff --git a/translations/ja-JP/data/reusables/actions/jobs/setting-default-values-for-jobs-defaults-job.md b/translations/ja-JP/data/reusables/actions/jobs/setting-default-values-for-jobs-defaults-job.md
index 6f4239bd0f7e..3069ccf6fbbe 100644
--- a/translations/ja-JP/data/reusables/actions/jobs/setting-default-values-for-jobs-defaults-job.md
+++ b/translations/ja-JP/data/reusables/actions/jobs/setting-default-values-for-jobs-defaults-job.md
@@ -1,3 +1,3 @@
Use `jobs..defaults` to create a `map` of default settings that will apply to all steps in the job. ワークフロー全体に対してデフォルト設定を設定することもできます。 詳しい情報については[`defaults`](/actions/using-workflows/workflow-syntax-for-github-actions#defaults)を参照してください。
-{% data reusables.github-actions.defaults-override %}
\ No newline at end of file
+{% data reusables.actions.defaults-override %}
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/actions/jobs/setting-default-values-for-jobs-defaults-run.md b/translations/ja-JP/data/reusables/actions/jobs/setting-default-values-for-jobs-defaults-run.md
index ba0ea105b7c4..515ca71ef015 100644
--- a/translations/ja-JP/data/reusables/actions/jobs/setting-default-values-for-jobs-defaults-run.md
+++ b/translations/ja-JP/data/reusables/actions/jobs/setting-default-values-for-jobs-defaults-run.md
@@ -1,6 +1,6 @@
You can use `defaults.run` to provide default `shell` and `working-directory` options for all [`run`](/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idstepsrun) steps in a workflow. 1つのジョブだけで利用できる`run`のデフォルト設定を設定することもできます。 詳しい情報については[`jobs..defaults.run`](/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_iddefaultsrun)を参照してください。 このキーワード中では、コンテキストや式を使うことはできません。
-{% data reusables.github-actions.defaults-override %}
+{% data reusables.actions.defaults-override %}
#### Example: Set the default shell and working directory
diff --git a/translations/ja-JP/data/reusables/actions/jobs/setting-default-values-for-jobs-defaults.md b/translations/ja-JP/data/reusables/actions/jobs/setting-default-values-for-jobs-defaults.md
index 372bbe1f3491..2446bbbd2965 100644
--- a/translations/ja-JP/data/reusables/actions/jobs/setting-default-values-for-jobs-defaults.md
+++ b/translations/ja-JP/data/reusables/actions/jobs/setting-default-values-for-jobs-defaults.md
@@ -1,3 +1,3 @@
Use `defaults` to create a `map` of default settings that will apply to all jobs in the workflow. 1つのジョブだけで利用できるデフォルト設定を設定することもできます。 詳しい情報については[`jobs..defaults`](/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_iddefaults)を参照してください。
-{% data reusables.github-actions.defaults-override %}
\ No newline at end of file
+{% data reusables.actions.defaults-override %}
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/github-actions/macos-runner-preview.md b/translations/ja-JP/data/reusables/actions/macos-runner-preview.md
similarity index 100%
rename from translations/ja-JP/data/reusables/github-actions/macos-runner-preview.md
rename to translations/ja-JP/data/reusables/actions/macos-runner-preview.md
diff --git a/translations/ja-JP/data/reusables/github-actions/matrix-variable-example.md b/translations/ja-JP/data/reusables/actions/matrix-variable-example.md
similarity index 100%
rename from translations/ja-JP/data/reusables/github-actions/matrix-variable-example.md
rename to translations/ja-JP/data/reusables/actions/matrix-variable-example.md
diff --git a/translations/ja-JP/data/reusables/github-actions/name-environment.md b/translations/ja-JP/data/reusables/actions/name-environment.md
similarity index 100%
rename from translations/ja-JP/data/reusables/github-actions/name-environment.md
rename to translations/ja-JP/data/reusables/actions/name-environment.md
diff --git a/translations/ja-JP/data/reusables/github-actions/new-environment.md b/translations/ja-JP/data/reusables/actions/new-environment.md
similarity index 100%
rename from translations/ja-JP/data/reusables/github-actions/new-environment.md
rename to translations/ja-JP/data/reusables/actions/new-environment.md
diff --git a/translations/ja-JP/data/reusables/github-actions/on-multiple-example.md b/translations/ja-JP/data/reusables/actions/on-multiple-example.md
similarity index 100%
rename from translations/ja-JP/data/reusables/github-actions/on-multiple-example.md
rename to translations/ja-JP/data/reusables/actions/on-multiple-example.md
diff --git a/translations/ja-JP/data/reusables/github-actions/on-single-example.md b/translations/ja-JP/data/reusables/actions/on-single-example.md
similarity index 100%
rename from translations/ja-JP/data/reusables/github-actions/on-single-example.md
rename to translations/ja-JP/data/reusables/actions/on-single-example.md
diff --git a/translations/ja-JP/data/reusables/github-actions/permissions-statement-environment.md b/translations/ja-JP/data/reusables/actions/permissions-statement-environment.md
similarity index 100%
rename from translations/ja-JP/data/reusables/github-actions/permissions-statement-environment.md
rename to translations/ja-JP/data/reusables/actions/permissions-statement-environment.md
diff --git a/translations/ja-JP/data/reusables/github-actions/permissions-statement-secrets-api.md b/translations/ja-JP/data/reusables/actions/permissions-statement-secrets-api.md
similarity index 100%
rename from translations/ja-JP/data/reusables/github-actions/permissions-statement-secrets-api.md
rename to translations/ja-JP/data/reusables/actions/permissions-statement-secrets-api.md
diff --git a/translations/ja-JP/data/reusables/github-actions/permissions-statement-secrets-environment.md b/translations/ja-JP/data/reusables/actions/permissions-statement-secrets-environment.md
similarity index 100%
rename from translations/ja-JP/data/reusables/github-actions/permissions-statement-secrets-environment.md
rename to translations/ja-JP/data/reusables/actions/permissions-statement-secrets-environment.md
diff --git a/translations/ja-JP/data/reusables/github-actions/permissions-statement-secrets-organization.md b/translations/ja-JP/data/reusables/actions/permissions-statement-secrets-organization.md
similarity index 100%
rename from translations/ja-JP/data/reusables/github-actions/permissions-statement-secrets-organization.md
rename to translations/ja-JP/data/reusables/actions/permissions-statement-secrets-organization.md
diff --git a/translations/ja-JP/data/reusables/github-actions/permissions-statement-secrets-repository.md b/translations/ja-JP/data/reusables/actions/permissions-statement-secrets-repository.md
similarity index 100%
rename from translations/ja-JP/data/reusables/github-actions/permissions-statement-secrets-repository.md
rename to translations/ja-JP/data/reusables/actions/permissions-statement-secrets-repository.md
diff --git a/translations/ja-JP/data/reusables/github-actions/postgres-environment-variables.md b/translations/ja-JP/data/reusables/actions/postgres-environment-variables.md
similarity index 100%
rename from translations/ja-JP/data/reusables/github-actions/postgres-environment-variables.md
rename to translations/ja-JP/data/reusables/actions/postgres-environment-variables.md
diff --git a/translations/ja-JP/data/reusables/github-actions/postgres-label-description.md b/translations/ja-JP/data/reusables/actions/postgres-label-description.md
similarity index 100%
rename from translations/ja-JP/data/reusables/github-actions/postgres-label-description.md
rename to translations/ja-JP/data/reusables/actions/postgres-label-description.md
diff --git a/translations/ja-JP/data/reusables/github-actions/private-repository-forks-configure.md b/translations/ja-JP/data/reusables/actions/private-repository-forks-configure.md
similarity index 100%
rename from translations/ja-JP/data/reusables/github-actions/private-repository-forks-configure.md
rename to translations/ja-JP/data/reusables/actions/private-repository-forks-configure.md
diff --git a/translations/ja-JP/data/reusables/github-actions/private-repository-forks-options.md b/translations/ja-JP/data/reusables/actions/private-repository-forks-options.md
similarity index 100%
rename from translations/ja-JP/data/reusables/github-actions/private-repository-forks-options.md
rename to translations/ja-JP/data/reusables/actions/private-repository-forks-options.md
diff --git a/translations/ja-JP/data/reusables/github-actions/private-repository-forks-overview.md b/translations/ja-JP/data/reusables/actions/private-repository-forks-overview.md
similarity index 100%
rename from translations/ja-JP/data/reusables/github-actions/private-repository-forks-overview.md
rename to translations/ja-JP/data/reusables/actions/private-repository-forks-overview.md
diff --git a/translations/ja-JP/data/reusables/github-actions/publish-to-maven-workflow-step.md b/translations/ja-JP/data/reusables/actions/publish-to-maven-workflow-step.md
similarity index 100%
rename from translations/ja-JP/data/reusables/github-actions/publish-to-maven-workflow-step.md
rename to translations/ja-JP/data/reusables/actions/publish-to-maven-workflow-step.md
diff --git a/translations/ja-JP/data/reusables/github-actions/publish-to-packages-workflow-step.md b/translations/ja-JP/data/reusables/actions/publish-to-packages-workflow-step.md
similarity index 100%
rename from translations/ja-JP/data/reusables/github-actions/publish-to-packages-workflow-step.md
rename to translations/ja-JP/data/reusables/actions/publish-to-packages-workflow-step.md
diff --git a/translations/ja-JP/data/reusables/github-actions/publishing-java-packages-intro.md b/translations/ja-JP/data/reusables/actions/publishing-java-packages-intro.md
similarity index 100%
rename from translations/ja-JP/data/reusables/github-actions/publishing-java-packages-intro.md
rename to translations/ja-JP/data/reusables/actions/publishing-java-packages-intro.md
diff --git a/translations/ja-JP/data/reusables/github-actions/pure-javascript.md b/translations/ja-JP/data/reusables/actions/pure-javascript.md
similarity index 100%
rename from translations/ja-JP/data/reusables/github-actions/pure-javascript.md
rename to translations/ja-JP/data/reusables/actions/pure-javascript.md
diff --git a/translations/ja-JP/data/reusables/github-actions/redis-environment-variables.md b/translations/ja-JP/data/reusables/actions/redis-environment-variables.md
similarity index 100%
rename from translations/ja-JP/data/reusables/github-actions/redis-environment-variables.md
rename to translations/ja-JP/data/reusables/actions/redis-environment-variables.md
diff --git a/translations/ja-JP/data/reusables/github-actions/redis-label-description.md b/translations/ja-JP/data/reusables/actions/redis-label-description.md
similarity index 100%
rename from translations/ja-JP/data/reusables/github-actions/redis-label-description.md
rename to translations/ja-JP/data/reusables/actions/redis-label-description.md
diff --git a/translations/ja-JP/data/reusables/github-actions/release-trigger-workflow.md b/translations/ja-JP/data/reusables/actions/release-trigger-workflow.md
similarity index 100%
rename from translations/ja-JP/data/reusables/github-actions/release-trigger-workflow.md
rename to translations/ja-JP/data/reusables/actions/release-trigger-workflow.md
diff --git a/translations/ja-JP/data/reusables/github-actions/run_id_description.md b/translations/ja-JP/data/reusables/actions/run_id_description.md
similarity index 100%
rename from translations/ja-JP/data/reusables/github-actions/run_id_description.md
rename to translations/ja-JP/data/reusables/actions/run_id_description.md
diff --git a/translations/ja-JP/data/reusables/github-actions/run_number_description.md b/translations/ja-JP/data/reusables/actions/run_number_description.md
similarity index 100%
rename from translations/ja-JP/data/reusables/github-actions/run_number_description.md
rename to translations/ja-JP/data/reusables/actions/run_number_description.md
diff --git a/translations/ja-JP/data/reusables/github-actions/runner-app-open-source.md b/translations/ja-JP/data/reusables/actions/runner-app-open-source.md
similarity index 100%
rename from translations/ja-JP/data/reusables/github-actions/runner-app-open-source.md
rename to translations/ja-JP/data/reusables/actions/runner-app-open-source.md
diff --git a/translations/ja-JP/data/reusables/github-actions/runner-group-assign-policy-org.md b/translations/ja-JP/data/reusables/actions/runner-group-assign-policy-org.md
similarity index 100%
rename from translations/ja-JP/data/reusables/github-actions/runner-group-assign-policy-org.md
rename to translations/ja-JP/data/reusables/actions/runner-group-assign-policy-org.md
diff --git a/translations/ja-JP/data/reusables/github-actions/runner-group-assign-policy-repo.md b/translations/ja-JP/data/reusables/actions/runner-group-assign-policy-repo.md
similarity index 100%
rename from translations/ja-JP/data/reusables/github-actions/runner-group-assign-policy-repo.md
rename to translations/ja-JP/data/reusables/actions/runner-group-assign-policy-repo.md
diff --git a/translations/ja-JP/data/reusables/github-actions/runner-label-settings.md b/translations/ja-JP/data/reusables/actions/runner-label-settings.md
similarity index 100%
rename from translations/ja-JP/data/reusables/github-actions/runner-label-settings.md
rename to translations/ja-JP/data/reusables/actions/runner-label-settings.md
diff --git a/translations/ja-JP/data/reusables/github-actions/runner-workflow-continuity.md b/translations/ja-JP/data/reusables/actions/runner-workflow-continuity.md
similarity index 100%
rename from translations/ja-JP/data/reusables/github-actions/runner-workflow-continuity.md
rename to translations/ja-JP/data/reusables/actions/runner-workflow-continuity.md
diff --git a/translations/ja-JP/data/reusables/github-actions/secrets-org-level-overview.md b/translations/ja-JP/data/reusables/actions/secrets-org-level-overview.md
similarity index 100%
rename from translations/ja-JP/data/reusables/github-actions/secrets-org-level-overview.md
rename to translations/ja-JP/data/reusables/actions/secrets-org-level-overview.md
diff --git a/translations/ja-JP/data/reusables/github-actions/secrets-redaction-warning.md b/translations/ja-JP/data/reusables/actions/secrets-redaction-warning.md
similarity index 100%
rename from translations/ja-JP/data/reusables/github-actions/secrets-redaction-warning.md
rename to translations/ja-JP/data/reusables/actions/secrets-redaction-warning.md
diff --git a/translations/ja-JP/data/reusables/github-actions/self-hosted-runner-auto-removal.md b/translations/ja-JP/data/reusables/actions/self-hosted-runner-auto-removal.md
similarity index 100%
rename from translations/ja-JP/data/reusables/github-actions/self-hosted-runner-auto-removal.md
rename to translations/ja-JP/data/reusables/actions/self-hosted-runner-auto-removal.md
diff --git a/translations/ja-JP/data/reusables/github-actions/self-hosted-runner-check-installation-success.md b/translations/ja-JP/data/reusables/actions/self-hosted-runner-check-installation-success.md
similarity index 92%
rename from translations/ja-JP/data/reusables/github-actions/self-hosted-runner-check-installation-success.md
rename to translations/ja-JP/data/reusables/actions/self-hosted-runner-check-installation-success.md
index 3810e5fae5e6..ed88aadab40f 100644
--- a/translations/ja-JP/data/reusables/github-actions/self-hosted-runner-check-installation-success.md
+++ b/translations/ja-JP/data/reusables/actions/self-hosted-runner-check-installation-success.md
@@ -5,6 +5,6 @@ After completing the steps to add a self-hosted runner, the runner and its statu
ジョブをランナーが受け付けるためには、セルフホストランナーアプリケーションが動作していなければなりません。 ランナーアプリケーションが{% data variables.product.product_name %}に接続してジョブの受信準備ができたなら、以下のメッセージがマシンのターミナルに表示されます。
-{% data reusables.github-actions.self-hosted-runner-connected-output %}
+{% data reusables.actions.self-hosted-runner-connected-output %}
詳しい情報については「[セルフホストランナーのモニタリングとトラブルシューティング](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners)」を参照してください。
diff --git a/translations/ja-JP/data/reusables/github-actions/self-hosted-runner-check-mac-linux.md b/translations/ja-JP/data/reusables/actions/self-hosted-runner-check-mac-linux.md
similarity index 100%
rename from translations/ja-JP/data/reusables/github-actions/self-hosted-runner-check-mac-linux.md
rename to translations/ja-JP/data/reusables/actions/self-hosted-runner-check-mac-linux.md
diff --git a/translations/ja-JP/data/reusables/github-actions/self-hosted-runner-configure-runner-group-access.md b/translations/ja-JP/data/reusables/actions/self-hosted-runner-configure-runner-group-access.md
similarity index 91%
rename from translations/ja-JP/data/reusables/github-actions/self-hosted-runner-configure-runner-group-access.md
rename to translations/ja-JP/data/reusables/actions/self-hosted-runner-configure-runner-group-access.md
index ce95459b15fc..e44b9eed45f5 100644
--- a/translations/ja-JP/data/reusables/github-actions/self-hosted-runner-configure-runner-group-access.md
+++ b/translations/ja-JP/data/reusables/actions/self-hosted-runner-configure-runner-group-access.md
@@ -6,7 +6,7 @@
**Warning**
- {% indented_data_reference reusables.github-actions.self-hosted-runner-security spaces=3 %}
+ {% indented_data_reference reusables.actions.self-hosted-runner-security spaces=3 %}
詳しい情報については「[セルフホストランナーについて](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)」を参照してください。
diff --git a/translations/ja-JP/data/reusables/github-actions/self-hosted-runner-configure.md b/translations/ja-JP/data/reusables/actions/self-hosted-runner-configure.md
similarity index 100%
rename from translations/ja-JP/data/reusables/github-actions/self-hosted-runner-configure.md
rename to translations/ja-JP/data/reusables/actions/self-hosted-runner-configure.md
diff --git a/translations/ja-JP/data/reusables/github-actions/self-hosted-runner-connected-output.md b/translations/ja-JP/data/reusables/actions/self-hosted-runner-connected-output.md
similarity index 100%
rename from translations/ja-JP/data/reusables/github-actions/self-hosted-runner-connected-output.md
rename to translations/ja-JP/data/reusables/actions/self-hosted-runner-connected-output.md
diff --git a/translations/ja-JP/data/reusables/github-actions/self-hosted-runner-create-group.md b/translations/ja-JP/data/reusables/actions/self-hosted-runner-create-group.md
similarity index 100%
rename from translations/ja-JP/data/reusables/github-actions/self-hosted-runner-create-group.md
rename to translations/ja-JP/data/reusables/actions/self-hosted-runner-create-group.md
diff --git a/translations/ja-JP/data/reusables/github-actions/self-hosted-runner-description.md b/translations/ja-JP/data/reusables/actions/self-hosted-runner-description.md
similarity index 100%
rename from translations/ja-JP/data/reusables/github-actions/self-hosted-runner-description.md
rename to translations/ja-JP/data/reusables/actions/self-hosted-runner-description.md
diff --git a/translations/ja-JP/data/reusables/github-actions/self-hosted-runner-groups-navigate-to-repo-org-enterprise.md b/translations/ja-JP/data/reusables/actions/self-hosted-runner-groups-navigate-to-repo-org-enterprise.md
similarity index 100%
rename from translations/ja-JP/data/reusables/github-actions/self-hosted-runner-groups-navigate-to-repo-org-enterprise.md
rename to translations/ja-JP/data/reusables/actions/self-hosted-runner-groups-navigate-to-repo-org-enterprise.md
diff --git a/translations/ja-JP/data/reusables/github-actions/self-hosted-runner-labels-runs-on.md b/translations/ja-JP/data/reusables/actions/self-hosted-runner-labels-runs-on.md
similarity index 100%
rename from translations/ja-JP/data/reusables/github-actions/self-hosted-runner-labels-runs-on.md
rename to translations/ja-JP/data/reusables/actions/self-hosted-runner-labels-runs-on.md
diff --git a/translations/ja-JP/data/reusables/github-actions/self-hosted-runner-labels-view-assigned-labels.md b/translations/ja-JP/data/reusables/actions/self-hosted-runner-labels-view-assigned-labels.md
similarity index 100%
rename from translations/ja-JP/data/reusables/github-actions/self-hosted-runner-labels-view-assigned-labels.md
rename to translations/ja-JP/data/reusables/actions/self-hosted-runner-labels-view-assigned-labels.md
diff --git a/translations/ja-JP/data/reusables/github-actions/self-hosted-runner-list-group.md b/translations/ja-JP/data/reusables/actions/self-hosted-runner-list-group.md
similarity index 100%
rename from translations/ja-JP/data/reusables/github-actions/self-hosted-runner-list-group.md
rename to translations/ja-JP/data/reusables/actions/self-hosted-runner-list-group.md
diff --git a/translations/ja-JP/data/reusables/github-actions/self-hosted-runner-list.md b/translations/ja-JP/data/reusables/actions/self-hosted-runner-list.md
similarity index 100%
rename from translations/ja-JP/data/reusables/github-actions/self-hosted-runner-list.md
rename to translations/ja-JP/data/reusables/actions/self-hosted-runner-list.md
diff --git a/translations/ja-JP/data/reusables/github-actions/self-hosted-runner-management-permissions-required.md b/translations/ja-JP/data/reusables/actions/self-hosted-runner-management-permissions-required.md
similarity index 100%
rename from translations/ja-JP/data/reusables/github-actions/self-hosted-runner-management-permissions-required.md
rename to translations/ja-JP/data/reusables/actions/self-hosted-runner-management-permissions-required.md
diff --git a/translations/ja-JP/data/reusables/github-actions/self-hosted-runner-navigate-repo-and-org.md b/translations/ja-JP/data/reusables/actions/self-hosted-runner-navigate-repo-and-org.md
similarity index 100%
rename from translations/ja-JP/data/reusables/github-actions/self-hosted-runner-navigate-repo-and-org.md
rename to translations/ja-JP/data/reusables/actions/self-hosted-runner-navigate-repo-and-org.md
diff --git a/translations/ja-JP/data/reusables/github-actions/self-hosted-runner-navigate-to-org-enterprise.md b/translations/ja-JP/data/reusables/actions/self-hosted-runner-navigate-to-org-enterprise.md
similarity index 100%
rename from translations/ja-JP/data/reusables/github-actions/self-hosted-runner-navigate-to-org-enterprise.md
rename to translations/ja-JP/data/reusables/actions/self-hosted-runner-navigate-to-org-enterprise.md
diff --git a/translations/ja-JP/data/reusables/github-actions/self-hosted-runner-navigate-to-repo-org-enterprise.md b/translations/ja-JP/data/reusables/actions/self-hosted-runner-navigate-to-repo-org-enterprise.md
similarity index 100%
rename from translations/ja-JP/data/reusables/github-actions/self-hosted-runner-navigate-to-repo-org-enterprise.md
rename to translations/ja-JP/data/reusables/actions/self-hosted-runner-navigate-to-repo-org-enterprise.md
diff --git a/translations/ja-JP/data/reusables/github-actions/self-hosted-runner-public-repo-access.md b/translations/ja-JP/data/reusables/actions/self-hosted-runner-public-repo-access.md
similarity index 57%
rename from translations/ja-JP/data/reusables/github-actions/self-hosted-runner-public-repo-access.md
rename to translations/ja-JP/data/reusables/actions/self-hosted-runner-public-repo-access.md
index e8fa0664cfa0..f0021bded6af 100644
--- a/translations/ja-JP/data/reusables/github-actions/self-hosted-runner-public-repo-access.md
+++ b/translations/ja-JP/data/reusables/actions/self-hosted-runner-public-repo-access.md
@@ -1,5 +1,5 @@
{% note %}
-**ノート:** セキュリティ上の理由から、デフォルトではパブリックリポジトリはランナーグループ内のランナーを使うことはできません。しかし、これはランナーグループの設定で上書きできます。 詳しい情報については、「[グループを使用したセルフホストランナーへのアクセスを管理する](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#changing-the-access-policy-of-a-self-hosted-runner-group)」を参照してください。
+**ノート:** セキュリティ上の理由から、デフォルトではパブリックリポジトリはランナーグループ内のランナーを使うことはできません。しかし、これはランナーグループの設定で上書きできます。 詳しい情報については、「[グループを使用したセルフホストランナーへのアクセスの管理](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#changing-the-access-policy-of-a-self-hosted-runner-group)」を参照してください。
{% endnote %}
diff --git a/translations/ja-JP/data/reusables/github-actions/self-hosted-runner-removal-impact.md b/translations/ja-JP/data/reusables/actions/self-hosted-runner-removal-impact.md
similarity index 100%
rename from translations/ja-JP/data/reusables/github-actions/self-hosted-runner-removal-impact.md
rename to translations/ja-JP/data/reusables/actions/self-hosted-runner-removal-impact.md
diff --git a/translations/ja-JP/data/reusables/github-actions/self-hosted-runner-removing-a-runner-updated.md b/translations/ja-JP/data/reusables/actions/self-hosted-runner-removing-a-runner-updated.md
similarity index 100%
rename from translations/ja-JP/data/reusables/github-actions/self-hosted-runner-removing-a-runner-updated.md
rename to translations/ja-JP/data/reusables/actions/self-hosted-runner-removing-a-runner-updated.md
diff --git a/translations/ja-JP/data/reusables/github-actions/self-hosted-runner-removing-a-runner.md b/translations/ja-JP/data/reusables/actions/self-hosted-runner-removing-a-runner.md
similarity index 100%
rename from translations/ja-JP/data/reusables/github-actions/self-hosted-runner-removing-a-runner.md
rename to translations/ja-JP/data/reusables/actions/self-hosted-runner-removing-a-runner.md
diff --git a/translations/ja-JP/data/reusables/github-actions/self-hosted-runner-reqs-docker.md b/translations/ja-JP/data/reusables/actions/self-hosted-runner-reqs-docker.md
similarity index 100%
rename from translations/ja-JP/data/reusables/github-actions/self-hosted-runner-reqs-docker.md
rename to translations/ja-JP/data/reusables/actions/self-hosted-runner-reqs-docker.md
diff --git a/translations/ja-JP/data/reusables/github-actions/self-hosted-runner-reusing.md b/translations/ja-JP/data/reusables/actions/self-hosted-runner-reusing.md
similarity index 100%
rename from translations/ja-JP/data/reusables/github-actions/self-hosted-runner-reusing.md
rename to translations/ja-JP/data/reusables/actions/self-hosted-runner-reusing.md
diff --git a/translations/ja-JP/data/reusables/github-actions/self-hosted-runner-security.md b/translations/ja-JP/data/reusables/actions/self-hosted-runner-security.md
similarity index 100%
rename from translations/ja-JP/data/reusables/github-actions/self-hosted-runner-security.md
rename to translations/ja-JP/data/reusables/actions/self-hosted-runner-security.md
diff --git a/translations/ja-JP/data/reusables/github-actions/service-container-add-script.md b/translations/ja-JP/data/reusables/actions/service-container-add-script.md
similarity index 100%
rename from translations/ja-JP/data/reusables/github-actions/service-container-add-script.md
rename to translations/ja-JP/data/reusables/actions/service-container-add-script.md
diff --git a/translations/ja-JP/data/reusables/github-actions/service-container-host-runner.md b/translations/ja-JP/data/reusables/actions/service-container-host-runner.md
similarity index 100%
rename from translations/ja-JP/data/reusables/github-actions/service-container-host-runner.md
rename to translations/ja-JP/data/reusables/actions/service-container-host-runner.md
diff --git a/translations/ja-JP/data/reusables/github-actions/service-container-host.md b/translations/ja-JP/data/reusables/actions/service-container-host.md
similarity index 100%
rename from translations/ja-JP/data/reusables/github-actions/service-container-host.md
rename to translations/ja-JP/data/reusables/actions/service-container-host.md
diff --git a/translations/ja-JP/data/reusables/github-actions/service-container-localhost.md b/translations/ja-JP/data/reusables/actions/service-container-localhost.md
similarity index 100%
rename from translations/ja-JP/data/reusables/github-actions/service-container-localhost.md
rename to translations/ja-JP/data/reusables/actions/service-container-localhost.md
diff --git a/translations/ja-JP/data/reusables/github-actions/service-container-prereqs.md b/translations/ja-JP/data/reusables/actions/service-container-prereqs.md
similarity index 100%
rename from translations/ja-JP/data/reusables/github-actions/service-container-prereqs.md
rename to translations/ja-JP/data/reusables/actions/service-container-prereqs.md
diff --git a/translations/ja-JP/data/reusables/github-actions/service-template-steps.md b/translations/ja-JP/data/reusables/actions/service-template-steps.md
similarity index 100%
rename from translations/ja-JP/data/reusables/github-actions/service-template-steps.md
rename to translations/ja-JP/data/reusables/actions/service-template-steps.md
diff --git a/translations/ja-JP/data/reusables/github-actions/settings-sidebar-actions-runner-groups-selection.md b/translations/ja-JP/data/reusables/actions/settings-sidebar-actions-runner-groups-selection.md
similarity index 100%
rename from translations/ja-JP/data/reusables/github-actions/settings-sidebar-actions-runner-groups-selection.md
rename to translations/ja-JP/data/reusables/actions/settings-sidebar-actions-runner-groups-selection.md
diff --git a/translations/ja-JP/data/reusables/github-actions/settings-sidebar-actions-runner-groups.md b/translations/ja-JP/data/reusables/actions/settings-sidebar-actions-runner-groups.md
similarity index 100%
rename from translations/ja-JP/data/reusables/github-actions/settings-sidebar-actions-runner-groups.md
rename to translations/ja-JP/data/reusables/actions/settings-sidebar-actions-runner-groups.md
diff --git a/translations/ja-JP/data/reusables/github-actions/settings-sidebar-actions-runner-selection.md b/translations/ja-JP/data/reusables/actions/settings-sidebar-actions-runner-selection.md
similarity index 100%
rename from translations/ja-JP/data/reusables/github-actions/settings-sidebar-actions-runner-selection.md
rename to translations/ja-JP/data/reusables/actions/settings-sidebar-actions-runner-selection.md
diff --git a/translations/ja-JP/data/reusables/github-actions/settings-sidebar-actions-runners-updated.md b/translations/ja-JP/data/reusables/actions/settings-sidebar-actions-runners-updated.md
similarity index 100%
rename from translations/ja-JP/data/reusables/github-actions/settings-sidebar-actions-runners-updated.md
rename to translations/ja-JP/data/reusables/actions/settings-sidebar-actions-runners-updated.md
diff --git a/translations/ja-JP/data/reusables/github-actions/settings-sidebar-actions-runners.md b/translations/ja-JP/data/reusables/actions/settings-sidebar-actions-runners.md
similarity index 100%
rename from translations/ja-JP/data/reusables/github-actions/settings-sidebar-actions-runners.md
rename to translations/ja-JP/data/reusables/actions/settings-sidebar-actions-runners.md
diff --git a/translations/ja-JP/data/reusables/github-actions/settings-sidebar-actions.md b/translations/ja-JP/data/reusables/actions/settings-sidebar-actions.md
similarity index 100%
rename from translations/ja-JP/data/reusables/github-actions/settings-sidebar-actions.md
rename to translations/ja-JP/data/reusables/actions/settings-sidebar-actions.md
diff --git a/translations/ja-JP/data/reusables/github-actions/setup-node-intro.md b/translations/ja-JP/data/reusables/actions/setup-node-intro.md
similarity index 100%
rename from translations/ja-JP/data/reusables/github-actions/setup-node-intro.md
rename to translations/ja-JP/data/reusables/actions/setup-node-intro.md
diff --git a/translations/ja-JP/data/reusables/github-actions/sidebar-environment.md b/translations/ja-JP/data/reusables/actions/sidebar-environment.md
similarity index 100%
rename from translations/ja-JP/data/reusables/github-actions/sidebar-environment.md
rename to translations/ja-JP/data/reusables/actions/sidebar-environment.md
diff --git a/translations/ja-JP/data/reusables/github-actions/sidebar-secret.md b/translations/ja-JP/data/reusables/actions/sidebar-secret.md
similarity index 100%
rename from translations/ja-JP/data/reusables/github-actions/sidebar-secret.md
rename to translations/ja-JP/data/reusables/actions/sidebar-secret.md
diff --git a/translations/ja-JP/data/reusables/github-actions/supported-github-runners.md b/translations/ja-JP/data/reusables/actions/supported-github-runners.md
similarity index 93%
rename from translations/ja-JP/data/reusables/github-actions/supported-github-runners.md
rename to translations/ja-JP/data/reusables/actions/supported-github-runners.md
index 71244b328af2..c4adac1069d6 100644
--- a/translations/ja-JP/data/reusables/github-actions/supported-github-runners.md
+++ b/translations/ja-JP/data/reusables/actions/supported-github-runners.md
@@ -12,10 +12,10 @@
Windows Server 2022
-windows-2022
+windows-latestもしくはwindows-2022
-The windows-latest label currently uses the Windows Server 2019 runner image.
+The windows-latest label currently uses the Windows Server 2022 runner image.
@@ -23,7 +23,7 @@ The windows-latest label currently uses the Windows Server 2019 run
Windows Server 2019
-windows-latestもしくはwindows-2019
+windows-2019
diff --git a/translations/ja-JP/data/reusables/github-actions/usage-api-requests.md b/translations/ja-JP/data/reusables/actions/usage-api-requests.md
similarity index 100%
rename from translations/ja-JP/data/reusables/github-actions/usage-api-requests.md
rename to translations/ja-JP/data/reusables/actions/usage-api-requests.md
diff --git a/translations/ja-JP/data/reusables/github-actions/usage-matrix-limits.md b/translations/ja-JP/data/reusables/actions/usage-matrix-limits.md
similarity index 100%
rename from translations/ja-JP/data/reusables/github-actions/usage-matrix-limits.md
rename to translations/ja-JP/data/reusables/actions/usage-matrix-limits.md
diff --git a/translations/ja-JP/data/reusables/github-actions/usage-workflow-queue-limits.md b/translations/ja-JP/data/reusables/actions/usage-workflow-queue-limits.md
similarity index 100%
rename from translations/ja-JP/data/reusables/github-actions/usage-workflow-queue-limits.md
rename to translations/ja-JP/data/reusables/actions/usage-workflow-queue-limits.md
diff --git a/translations/ja-JP/data/reusables/github-actions/usage-workflow-run-time.md b/translations/ja-JP/data/reusables/actions/usage-workflow-run-time.md
similarity index 100%
rename from translations/ja-JP/data/reusables/github-actions/usage-workflow-run-time.md
rename to translations/ja-JP/data/reusables/actions/usage-workflow-run-time.md
diff --git a/translations/ja-JP/data/reusables/github-actions/using-context-or-environment-variables.md b/translations/ja-JP/data/reusables/actions/using-context-or-environment-variables.md
similarity index 100%
rename from translations/ja-JP/data/reusables/github-actions/using-context-or-environment-variables.md
rename to translations/ja-JP/data/reusables/actions/using-context-or-environment-variables.md
diff --git a/translations/ja-JP/data/reusables/github-actions/workflow-dispatch-inputs.md b/translations/ja-JP/data/reusables/actions/workflow-dispatch-inputs.md
similarity index 100%
rename from translations/ja-JP/data/reusables/github-actions/workflow-dispatch-inputs.md
rename to translations/ja-JP/data/reusables/actions/workflow-dispatch-inputs.md
diff --git a/translations/ja-JP/data/reusables/github-actions/workflow-permissions-intro.md b/translations/ja-JP/data/reusables/actions/workflow-permissions-intro.md
similarity index 100%
rename from translations/ja-JP/data/reusables/github-actions/workflow-permissions-intro.md
rename to translations/ja-JP/data/reusables/actions/workflow-permissions-intro.md
diff --git a/translations/ja-JP/data/reusables/github-actions/workflow-permissions-modifying.md b/translations/ja-JP/data/reusables/actions/workflow-permissions-modifying.md
similarity index 100%
rename from translations/ja-JP/data/reusables/github-actions/workflow-permissions-modifying.md
rename to translations/ja-JP/data/reusables/actions/workflow-permissions-modifying.md
diff --git a/translations/ja-JP/data/reusables/github-actions/workflows-from-public-fork-setting.md b/translations/ja-JP/data/reusables/actions/workflows-from-public-fork-setting.md
similarity index 100%
rename from translations/ja-JP/data/reusables/github-actions/workflows-from-public-fork-setting.md
rename to translations/ja-JP/data/reusables/actions/workflows-from-public-fork-setting.md
diff --git a/translations/ja-JP/data/reusables/actions/workflows/section-triggering-a-workflow.md b/translations/ja-JP/data/reusables/actions/workflows/section-triggering-a-workflow.md
index 14f4541b78ea..6a406ff73981 100644
--- a/translations/ja-JP/data/reusables/actions/workflows/section-triggering-a-workflow.md
+++ b/translations/ja-JP/data/reusables/actions/workflows/section-triggering-a-workflow.md
@@ -3,4 +3,4 @@ To automatically trigger a workflow, use `on` to define which events can cause t
You can define single or multiple events that can a trigger workflow, or set a time schedule. You can also restrict the execution of a workflow to only occur for specific files, tags, or branch changes. These options are described in the following sections.
-{% data reusables.github-actions.actions-on-examples %}
+{% data reusables.actions.actions-on-examples %}
diff --git a/translations/ja-JP/data/reusables/github-actions/actions-on-examples.md b/translations/ja-JP/data/reusables/github-actions/actions-on-examples.md
deleted file mode 100644
index 26d4a25747f6..000000000000
--- a/translations/ja-JP/data/reusables/github-actions/actions-on-examples.md
+++ /dev/null
@@ -1,19 +0,0 @@
-### Using a single event
-
-{% data reusables.github-actions.on-single-example %}
-
-### Using multiple events
-
-{% data reusables.github-actions.on-multiple-example %}
-
-### Using activity types
-
-{% data reusables.github-actions.actions-activity-types %}
-
-### Using filters
-
-{% data reusables.github-actions.actions-filters %}
-
-### Using activity types and filters with multiple events
-
-{% data reusables.github-actions.actions-multiple-types %}
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/github-actions/ip-allow-list-self-hosted-runners.md b/translations/ja-JP/data/reusables/github-actions/ip-allow-list-self-hosted-runners.md
deleted file mode 100644
index 3dc0b0d8f702..000000000000
--- a/translations/ja-JP/data/reusables/github-actions/ip-allow-list-self-hosted-runners.md
+++ /dev/null
@@ -1,13 +0,0 @@
-{% ifversion ghae %}
-セルフホストランナーに
-{% data variables.product.prodname_dotcom %}との通信を許可するには、セルフホストランナーのIPアドレスもしくはIPアドレスの範囲をIP許可リストに追加してください。 詳しい情報については「[許可されたIPアドレスの追加](#adding-an-allowed-ip-address)」を参照してください。
-{% else %}
-{% warning %}
-
-**警告**: IP許可リストを使い、{% data variables.product.prodname_actions %}も使いたい場合には、セルフホストランナーを使わなければなりません。 詳しい情報については「[自分のランナーをホストする](/actions/automating-your-workflow-with-github-actions/about-self-hosted-runners)」を参照してください。
-
-{% endwarning %}
-セルフホストランナーに
-
-{% data variables.product.prodname_dotcom %}との通信を許可するには、セルフホストランナーのIPアドレスもしくはIPアドレスの範囲をIP許可リストに追加してください。 詳しい情報については「[許可されたIPアドレスの追加](#adding-an-allowed-ip-address)」を参照してください。
-{% endif %}
diff --git a/translations/ja-JP/data/reusables/repositories/navigate-to-commit-page.md b/translations/ja-JP/data/reusables/repositories/navigate-to-commit-page.md
new file mode 100644
index 000000000000..bec770c79066
--- /dev/null
+++ b/translations/ja-JP/data/reusables/repositories/navigate-to-commit-page.md
@@ -0,0 +1 @@
+1. On the main page of the repository, click the commits to navigate to the commits page. 
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/rest-reference/actions/actions.md b/translations/ja-JP/data/reusables/rest-reference/actions/actions.md
new file mode 100644
index 000000000000..6a09ae57722f
--- /dev/null
+++ b/translations/ja-JP/data/reusables/rest-reference/actions/actions.md
@@ -0,0 +1 @@
+{% data variables.product.prodname_actions %} API では、REST API を使用して {% data variables.product.prodname_actions %} を管理できます。 {% data reusables.actions.actions-authentication %} {% data variables.product.prodname_github_apps %} require the permissions mentioned in each endpoint. 詳しい情報については、「[{% data variables.product.prodname_actions %} のドキュメント](/actions)」を参照してください。
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/rest-reference/actions/artifacts.md b/translations/ja-JP/data/reusables/rest-reference/actions/artifacts.md
new file mode 100644
index 000000000000..d4de62558c16
--- /dev/null
+++ b/translations/ja-JP/data/reusables/rest-reference/actions/artifacts.md
@@ -0,0 +1,5 @@
+## 成果物
+
+成果物 API では、ワークフローの成果物に関する情報をダウンロード、削除、および取得できます。 {% data reusables.actions.about-artifacts %} 詳しい情報については、「[成果物を利用してワークフローのデータを永続化する](/actions/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)」を参照してください。
+
+{% data reusables.actions.actions-authentication %} {% data reusables.actions.actions-app-actions-permissions-api %}
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/rest-reference/actions/permissions.md b/translations/ja-JP/data/reusables/rest-reference/actions/permissions.md
new file mode 100644
index 000000000000..3e09fefcfcda
--- /dev/null
+++ b/translations/ja-JP/data/reusables/rest-reference/actions/permissions.md
@@ -0,0 +1,3 @@
+## 権限
+
+The Permissions API allows you to set permissions for what enterprises, organizations, and repositories are allowed to run {% data variables.product.prodname_actions %}, and what actions are allowed to run.{% ifversion fpt or ghec or ghes %} For more information, see "[Usage limits, billing, and administration](/actions/reference/usage-limits-billing-and-administration#disabling-or-limiting-github-actions-for-your-repository-or-organization)."{% endif %}
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/rest-reference/actions/secrets.md b/translations/ja-JP/data/reusables/rest-reference/actions/secrets.md
new file mode 100644
index 000000000000..4297ae3ecea2
--- /dev/null
+++ b/translations/ja-JP/data/reusables/rest-reference/actions/secrets.md
@@ -0,0 +1,5 @@
+## シークレット
+
+シークレット API では、暗号化されたシークレットに関する情報を作成、更新、削除、および取得できます。 {% data reusables.actions.about-secrets %} 詳しい情報については、「[暗号化されたシークレットの作成と利用](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)」を参照してください。
+
+{% data reusables.actions.actions-authentication %} {% data variables.product.prodname_github_apps %} must have the `secrets` permission to use this API. 認証されたユーザは、シークレットを作成、更新、または読み取るために、リポジトリへのコラボレータアクセス権を持っている必要があります。
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/rest-reference/actions/self-hosted-runner-groups.md b/translations/ja-JP/data/reusables/rest-reference/actions/self-hosted-runner-groups.md
new file mode 100644
index 000000000000..a1016634dc52
--- /dev/null
+++ b/translations/ja-JP/data/reusables/rest-reference/actions/self-hosted-runner-groups.md
@@ -0,0 +1,7 @@
+## セルフホストランナーグループ
+
+{% data reusables.actions.ae-self-hosted-runners-notice %}
+
+セルフホストランナーグループ API を使用すると、セルフホストランナーのグループを管理できます。 詳しい情報については、「[グループを使用したセルフホストランナーへのアクセスを管理する](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups)」を参照してください。
+
+{% data reusables.actions.actions-authentication %} {% data variables.product.prodname_github_apps %} must have the `administration` permission for repositories or the `organization_self_hosted_runners` permission for organizations. Authenticated users must have admin access to repositories or organizations, or the `manage_runners:enterprise` scope for enterprises to use this API.
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/rest-reference/actions/self-hosted-runners.md b/translations/ja-JP/data/reusables/rest-reference/actions/self-hosted-runners.md
new file mode 100644
index 000000000000..a1c74f22ed17
--- /dev/null
+++ b/translations/ja-JP/data/reusables/rest-reference/actions/self-hosted-runners.md
@@ -0,0 +1,7 @@
+## セルフホストランナー
+
+{% data reusables.actions.ae-self-hosted-runners-notice %}
+
+セルフホストランナー API では、自分のホストランナーの登録、表示、削除ができます。 {% data reusables.actions.about-self-hosted-runners %} 詳しい情報については「[自分のランナーのホスト](/actions/hosting-your-own-runners)」を参照してください。
+
+{% data reusables.actions.actions-authentication %} {% data variables.product.prodname_github_apps %} must have the `administration` permission for repositories the `organization_self_hosted_runners` permission for organizations. Authenticated users must have admin access to repositories or organizations, or the `manage_runners:enterprise` scope for enterprises to use this API.
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/rest-reference/actions/workflow-jobs.md b/translations/ja-JP/data/reusables/rest-reference/actions/workflow-jobs.md
new file mode 100644
index 000000000000..3e638f703fb8
--- /dev/null
+++ b/translations/ja-JP/data/reusables/rest-reference/actions/workflow-jobs.md
@@ -0,0 +1,5 @@
+## ワークフロージョブ
+
+ワークフロージョブ API では、ログとワークフロージョブを表示できます。 {% data reusables.actions.about-workflow-jobs %}詳しい情報については、「[GitHub Actions のワークフロー構文](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions)」を参照してください。
+
+{% data reusables.actions.actions-authentication %} {% data reusables.actions.actions-app-actions-permissions-api %}
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/rest-reference/actions/workflow-runs.md b/translations/ja-JP/data/reusables/rest-reference/actions/workflow-runs.md
new file mode 100644
index 000000000000..0f38e2b7a2d9
--- /dev/null
+++ b/translations/ja-JP/data/reusables/rest-reference/actions/workflow-runs.md
@@ -0,0 +1,5 @@
+## Workflow runs
+
+The Workflow Runs API allows you to view, re-run, cancel, and view logs for workflow runs. {% data reusables.actions.about-workflow-runs %} For more information, see "[Managing a workflow run](/actions/automating-your-workflow-with-github-actions/managing-a-workflow-run)."
+
+{% data reusables.actions.actions-authentication %} {% data reusables.actions.actions-app-actions-permissions-api %}
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/rest-reference/actions/workflows.md b/translations/ja-JP/data/reusables/rest-reference/actions/workflows.md
new file mode 100644
index 000000000000..12bb5863664e
--- /dev/null
+++ b/translations/ja-JP/data/reusables/rest-reference/actions/workflows.md
@@ -0,0 +1,5 @@
+## ワークフロー
+
+ワークフロー API を使用すると、リポジトリのワークフローを表示できます。 {% data reusables.actions.about-workflows %}詳しい情報については、「[GitHub Actions でワークフローを自動化する](/actions/automating-your-workflow-with-github-actions)」を参照してください。
+
+{% data reusables.actions.actions-authentication %} {% data reusables.actions.actions-app-actions-permissions-api %}
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/rest-reference/activity/events.md b/translations/ja-JP/data/reusables/rest-reference/activity/events.md
new file mode 100644
index 000000000000..78f65cef3653
--- /dev/null
+++ b/translations/ja-JP/data/reusables/rest-reference/activity/events.md
@@ -0,0 +1,22 @@
+## Events
+
+The Events API is a read-only API to the {% data variables.product.prodname_dotcom %} events. These events power the various activity streams on the site.
+
+The Events API can return different types of events triggered by activity on {% data variables.product.product_name %}. For more information about the specific events that you can receive from the Events API, see "[{% data variables.product.prodname_dotcom %} Event types](/developers/webhooks-and-events/github-event-types)." An events API for repository issues is also available. For more information, see the "[Issue Events API](/rest/reference/issues#events)."
+
+Events are optimized for polling with the "ETag" header. If no new events have been triggered, you will see a "304 Not Modified" response, and your current rate limit will be untouched. There is also an "X-Poll-Interval" header that specifies how often (in seconds) you are allowed to poll. In times of high server load, the time may increase. Please obey the header.
+
+``` shell
+$ curl -I {% data variables.product.api_url_pre %}/users/tater/events
+> HTTP/2 200
+> X-Poll-Interval: 60
+> ETag: "a18c3bded88eb5dbb5c849a489412bf3"
+
+# The quotes around the ETag value are important
+$ curl -I {% data variables.product.api_url_pre %}/users/tater/events \
+$ -H 'If-None-Match: "a18c3bded88eb5dbb5c849a489412bf3"'
+> HTTP/2 304
+> X-Poll-Interval: 60
+```
+
+Only events created within the past 90 days will be included in timelines. Events older than 90 days will not be included (even if the total number of events in the timeline is less than 300).
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/rest-reference/activity/feeds.md b/translations/ja-JP/data/reusables/rest-reference/activity/feeds.md
new file mode 100644
index 000000000000..8b39ad9d7bd9
--- /dev/null
+++ b/translations/ja-JP/data/reusables/rest-reference/activity/feeds.md
@@ -0,0 +1,52 @@
+## フィード
+
+### Example of getting an Atom feed
+
+To get a feed in Atom format, you must specify the `application/atom+xml` type in the `Accept` header. For example, to get the Atom feed for GitHub security advisories:
+
+ curl -H "Accept: application/atom+xml" https://github.com/security-advisories
+
+#### レスポンス
+
+```shell
+HTTP/2 200
+```
+
+```xml
+
+
+ tag:github.com,2008:/security-advisories
+
+ GitHub Security Advisory Feed
+
+ GitHub
+
+ 2019-01-14T19:34:52Z
+
+ tag:github.com,2008:GHSA-abcd-12ab-23cd
+ 2018-07-26T15:14:52Z
+ 2019-01-14T19:34:52Z
+ [GHSA-abcd-12ab-23cd] Moderate severity vulnerability that affects Octoapp
+
+
+ <p>Octoapp node module before 4.17.5 suffers from a Modification of Assumed-Immutable Data (MAID) vulnerability via defaultsDeep, merge, and mergeWith functions, which allows a malicious user to modify the prototype of "Object" via <strong>proto</strong>, causing the addition or modification of an existing property that will exist on all objects.</p>
+ <p><strong>Affected Packages</strong></p>
+
+ <dl>
+ <dt>Octoapp</dt>
+ <dd>Ecosystem: npm</dd>
+ <dd>Severity: moderate</dd>
+ <dd>Versions: < 4.17.5</dd>
+ <dd>Fixed in: 4.17.5</dd>
+ </dl>
+
+ <p><strong>References</strong></p>
+
+ <ul>
+ <li>https://nvd.nist.gov/vuln/detail/CVE-2018-123</li>
+ </ul>
+
+
+
+
+```
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/rest-reference/activity/notifications.md b/translations/ja-JP/data/reusables/rest-reference/activity/notifications.md
new file mode 100644
index 000000000000..0778aea55e72
--- /dev/null
+++ b/translations/ja-JP/data/reusables/rest-reference/activity/notifications.md
@@ -0,0 +1,59 @@
+## 通知
+
+ユーザは、Watch しているリポジトリでの会話の通知を受け取ります。
+
+* Issue とそのコメント
+* プルリクエストとそのコメント
+* コミットに関するコメント
+
+ユーザが関わっている場合、Watch 解除したリポジトリでの会話の通知も送信されます。
+
+* **@メンション**
+* Issue の割り当て
+* ユーザの作者のコミット、またはコミット
+* ユーザが参加しているディスカッション
+
+すべての通知 API 呼び出しには、`notifications` または `repo` API スコープが必要です。 これを行うと、一部の Issue およびコミットコンテンツへの読み取り専用アクセス権が付与されます。 それぞれのエンドポイントから Issue とコミットにアクセスするには、`repo` スコープが必要です。
+
+通知は「スレッド」として返されます。 スレッドには、Issue、プルリクエスト、またはコミットの現在のディスカッションに関する情報が含まれています。
+
+通知は、`Last-Modified` ヘッダでポーリングするために最適化されています。 新しい通知がない場合は、`304 Not Modified` レスポンスが表示され、現在のレート制限は変更されません。 `X-Poll-Interval` ヘッダで、ポーリングを許可する頻度（秒単位）を指定します。 サーバー負荷が高い場合、長時間かかることがあります。 ヘッダに従ってください。
+
+``` shell
+# リクエストに認証を追加
+$ curl -I {% data variables.product.api_url_pre %}/notifications
+HTTP/2 200
+Last-Modified: Thu, 25 Oct 2012 15:16:27 GMT
+X-Poll-Interval: 60
+
+# Last-Modifiedヘッダを正確に渡す
+$ curl -I {% data variables.product.api_url_pre %}/notifications
+$ -H "If-Modified-Since: Thu, 25 Oct 2012 15:16:27 GMT"
+> HTTP/2 304
+> X-Poll-Interval: 60
+```
+
+### 通知理由
+
+通知 API からレスポンスを取得するとき、各ペイロードには `reason` というタイトルのキーがあります。 これらは、通知をトリガーするイベントに対応しています。
+
+通知を受け取る `reason`（理由）には、次のようなものがあります。
+
+| 理由名 | 説明 |
+| ------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `assign` | Issue に割り当てられた。 |
+| `作者` | スレッドを作成した。 |
+| `コメント` | スレッドにコメントした。 |
+| `ci_activity` | A {% data variables.product.prodname_actions %} workflow run that you triggered was completed. |
+| `招待` | リポジトリへのコントリビューションへの招待を承諾した。 |
+| `manual` | スレッドをサブスクライブした（Issue またはプルリクエストを介して）。 |
+| `メンション` | コンテンツで具体的に**@メンション**された。 |
+| `review_requested` | 自分、または自分が所属している Team が、Pull Requestのレビューを求められた。{% ifversion fpt or ghec %}
+| `security_alert` | {% data variables.product.prodname_dotcom %} が、リポジトリに[セキュリティの脆弱性](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)を発見した。{% endif %}
+| `state_change` | スレッドの状態を変更した（たとえば、Issue をクローズしたり、プルリクエストをマージしたりした）。 |
+| `subscribed` | リポジトリを Watch している。 |
+| `team_mention` | メンションされた Team に所属していた。 |
+
+`reason` はスレッドごとに変更され、後の通知の `reason` が異なる場合は変更される可能性があることに注意してください。
+
+たとえば、Issue の作者である場合は、その Issue に関するその後の通知には、`author`（作者）の `reason`（理由）が含まれます。 その後、同じ Issue について**@メンション**されている場合、その後に取得する通知に `mention`（メンション）する `reason`（理由）が含まれます。 その `reason` は、再度メンションされたかどうかにかかわらず、`mention` として残ります。
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/rest-reference/activity/starring.md b/translations/ja-JP/data/reusables/rest-reference/activity/starring.md
new file mode 100644
index 000000000000..2ea6f504979a
--- /dev/null
+++ b/translations/ja-JP/data/reusables/rest-reference/activity/starring.md
@@ -0,0 +1,15 @@
+## Star
+
+リポジトリに Star を付けると、ユーザがリポジトリをブックマークできます。 おおよその関心レベルを示すために、リポジトリの横に Star が表示されます。 Star は通知やアクティビティフィードには影響しません。
+
+### Star と Watch
+
+2012年8月に、{% data variables.product.prodname_dotcom %} での [Watch 方法を変更](https://github.com/blog/1204-notifications-stars)しました。 多くの API クライアントアプリケーションは、このデータへのアクセスに元の「Watchしているユーザ」のエンドポイントを使用しています。 現在、その代わりに「Star」エンドポイントを使用できます（以下で説明）。 詳しい情報については、[Watchしているユーザ API の変更に関する投稿](https://developer.github.com/changes/2012-09-05-watcher-api/)と「[リポジトリを Watch している API](/rest/reference/activity#watching)」を参照してください。
+
+### Star 付きのカスタムメディアタイプ
+
+Star 付きの REST APIでサポートされているカスタムメディアタイプが 1 つあります。 このカスタムメディアタイプを使用すると、Star が作成された時刻を示す `starred_at` タイムスタンププロパティを含むレスポンスを受け取ります。 レスポンスには、カスタムメディアタイプが含まれていない場合に返されるリソースを含む 2 番目のプロパティもあります。 リソースを含むプロパティは、`user` または `repo` のいずれかになります。
+
+ application/vnd.github.v3.star+json
+
+メディアタイプの詳しい情報については、「[カスタムメディアタイプ](/rest/overview/media-types)」を参照してください。
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/rest-reference/activity/watching.md b/translations/ja-JP/data/reusables/rest-reference/activity/watching.md
new file mode 100644
index 000000000000..19ceea2dadb8
--- /dev/null
+++ b/translations/ja-JP/data/reusables/rest-reference/activity/watching.md
@@ -0,0 +1,3 @@
+## Watch の違い
+
+リポジトリを Watch すると、ユーザは登録され、新しいディスカッションやユーザのアクティビティフィードのイベントに関する通知を受け取ります。 基本的なリポジトリブックマークについては、「[リポジトリの Star 付け](/rest/reference/activity#starring)」を参照してください。
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/rest-reference/apps/apps.md b/translations/ja-JP/data/reusables/rest-reference/apps/apps.md
new file mode 100644
index 000000000000..91470db3bf43
--- /dev/null
+++ b/translations/ja-JP/data/reusables/rest-reference/apps/apps.md
@@ -0,0 +1,9 @@
+{% data reusables.apps.general-apps-restrictions %}
+
+このページには、GitHub App として認証されている場合にアクセスできるエンドポイントが一覧表示されています。 詳細については、「[GitHub App として認証する](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-a-github-app)」を参照してださい。
+
+GitHub App として認証されると、GitHub Apps API を使用して、GitHub App に関する大まかな情報と、アプリケーションのインストールに関する具体的な情報を取得できます。
+
+GitHub App として認証されている場合、REST API v3 エンドポイントにアクセスできます。 これらのエンドポイントには、「Works with GitHub Apps」という箇条書きを含む「注釈」セクションがあります。 ユーザとして認証されている場合、これらのエンドポイントにアクセスすることもできます。
+
+REST API v3 エンドポイントのサブセットでは、GitHub App のインストールとして認証する必要があります。 これらのエンドポイントの一覧については、[Installations](/rest/reference/apps#installations) を参照してください。
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/rest-reference/apps/installations.md b/translations/ja-JP/data/reusables/rest-reference/apps/installations.md
new file mode 100644
index 000000000000..56b138e78874
--- /dev/null
+++ b/translations/ja-JP/data/reusables/rest-reference/apps/installations.md
@@ -0,0 +1,5 @@
+## インストール
+
+Installations API を使用すると、GitHub App のインストールに関する情報を取得して、それらのインストール内でアクションを実行できます。 _インストール_とは、アプリケーションをインストールしたユーザまたは Organization のアカウントを指します。 インストレーションとして認証し、特定のリポジトリへのアクセスを制限する方法については、「[インストレーションとして認証する](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation)」を参照してください。
+
+Organization のすべての GitHub App インストレーションを一覧表示するには、「[Organization のアプリケーションインストールの一覧表示](/rest/reference/orgs#list-app-installations-for-an-organization)」を参照してください。
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/rest-reference/apps/marketplace.md b/translations/ja-JP/data/reusables/rest-reference/apps/marketplace.md
new file mode 100644
index 000000000000..dd5fe4b6a217
--- /dev/null
+++ b/translations/ja-JP/data/reusables/rest-reference/apps/marketplace.md
@@ -0,0 +1,13 @@
+## Marketplace
+
+{% data variables.product.prodname_marketplace %} の詳細については、「[GitHub Marketplace](/marketplace/)」を参照してください。
+
+{% data variables.product.prodname_marketplace %} API では、価格プランを使用している顧客の確認、顧客の購入の確認、アカウントで有効になっているプランの有無を確認できます。
+
+### スタブされたエンドポイントでテストする
+
+この API には、[**スタブされたデータ**で {% data variables.product.prodname_github_app %} をテスト](/marketplace/integrating-with-the-github-marketplace-api/testing-github-marketplace-apps/)できるエンドポイントが含まれています。 スタブされたデータはハードコードされた偽のデータであり、実際のプランに基づいて変更されることはありません。
+
+スタブされたデータでテストするには、対応する本番環境の代わりにスタブされたエンドポイントを使用します。 This allows you to test whether API logic succeeds before listing {% data variables.product.prodname_github_apps %} on {% data variables.product.prodname_marketplace %}.
+
+{% data variables.product.prodname_github_app %} をデプロイする前に、スタブされたエンドポイントを本番のエンドポイントに置き換えてください。
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/rest-reference/apps/oauth-applications.md b/translations/ja-JP/data/reusables/rest-reference/apps/oauth-applications.md
new file mode 100644
index 000000000000..a90bf6896a3f
--- /dev/null
+++ b/translations/ja-JP/data/reusables/rest-reference/apps/oauth-applications.md
@@ -0,0 +1,3 @@
+## OAuth アプリケーション API
+
+You can use this API to manage the OAuth tokens an OAuth application uses to access people's accounts on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}.
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/rest-reference/apps/webhooks.md b/translations/ja-JP/data/reusables/rest-reference/apps/webhooks.md
new file mode 100644
index 000000000000..d03c7043ab01
--- /dev/null
+++ b/translations/ja-JP/data/reusables/rest-reference/apps/webhooks.md
@@ -0,0 +1,3 @@
+## webhook
+
+A {% data variables.product.prodname_github_app %}'s webhook allows you to receive HTTP `POST` payloads whenever certain events happen for an app. {% data reusables.webhooks.webhooks-rest-api-links %}
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/rest-reference/billing/billing.md b/translations/ja-JP/data/reusables/rest-reference/billing/billing.md
new file mode 100644
index 000000000000..34d18940c945
--- /dev/null
+++ b/translations/ja-JP/data/reusables/rest-reference/billing/billing.md
@@ -0,0 +1 @@
+Enterprise の支払情報を取得できます。 詳しい情報については、「[{% data variables.product.prodname_dotcom %} Enterprise 管理](/rest/reference/enterprise-admin#billing)」REST API を参照してください。
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/rest-reference/branches/branch-protection.md b/translations/ja-JP/data/reusables/rest-reference/branches/branch-protection.md
new file mode 100644
index 000000000000..0efa8cd2daa9
--- /dev/null
+++ b/translations/ja-JP/data/reusables/rest-reference/branches/branch-protection.md
@@ -0,0 +1 @@
+## 保護されたブランチ
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/rest-reference/checks/checks.md b/translations/ja-JP/data/reusables/rest-reference/checks/checks.md
new file mode 100644
index 000000000000..1bbb7387ae34
--- /dev/null
+++ b/translations/ja-JP/data/reusables/rest-reference/checks/checks.md
@@ -0,0 +1 @@
+継続的インテグレーション、コードの構文チェック、コードのスキャンサービスを実行し、コミットについて詳細なフィードバックを行うアプリを作成できます。 詳しい情報については、「[Checks API を使ってみる](/rest/guides/getting-started-with-the-checks-api)」および「[Checks API で CI テストを作成する](/apps/quickstart-guides/creating-ci-tests-with-the-checks-api/)」を参照してください。
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/rest-reference/checks/runs.md b/translations/ja-JP/data/reusables/rest-reference/checks/runs.md
new file mode 100644
index 000000000000..0f1d66b6742c
--- /dev/null
+++ b/translations/ja-JP/data/reusables/rest-reference/checks/runs.md
@@ -0,0 +1 @@
+## チェックラン
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/rest-reference/checks/suites.md b/translations/ja-JP/data/reusables/rest-reference/checks/suites.md
new file mode 100644
index 000000000000..197df587e36d
--- /dev/null
+++ b/translations/ja-JP/data/reusables/rest-reference/checks/suites.md
@@ -0,0 +1,7 @@
+## チェックスイート
+
+{% note %}
+
+ **注釈:** コミット SHA を複数のブランチにプッシュした場合でも、GitHub App はコミット SHA ごとに 1 つの [`check_suite`](/webhooks/event-payloads/#check_suite) イベントのみを受け取ります。 ブランチ [`create`](/webhooks/event-payloads/#create) イベントをサブスクライブして、コミット SHA がブランチにプッシュされたタイミングを確認することができます。
+
+{% endnote %}
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/rest-reference/code-scanning/code-scanning.md b/translations/ja-JP/data/reusables/rest-reference/code-scanning/code-scanning.md
new file mode 100644
index 000000000000..686d42e2eefc
--- /dev/null
+++ b/translations/ja-JP/data/reusables/rest-reference/code-scanning/code-scanning.md
@@ -0,0 +1,15 @@
+{% data reusables.code-scanning.beta %}
+
+{% data variables.product.prodname_code_scanning %} APIを使うと、リオジトリから{% data variables.product.prodname_code_scanning %}アラートを取得して更新できます。 このエンドポイントを使って、Organization内で{% data variables.product.prodname_code_scanning %}アラートの自動化されたレポートを作成したり、オフラインの{% data variables.product.prodname_code_scanning %}ツールを使って生成された分析結果をアップロードしたりできます。 詳しい情報については、「[コード内のセキュリティの脆弱性とエラーを検出する](/github/finding-security-vulnerabilities-and-errors-in-your-code)」を参照してください。
+
+{% ifversion fpt or ghes > 3.0 or ghae or ghec %}
+### {% data variables.product.prodname_code_scanning %}のためのカスタムメディアタイプ
+
+{% data variables.product.prodname_code_scanning %} REST API用にサポートされているカスタムメディアタイプが1つあります。
+
+ application/sarif+json
+
+これは`/analyses/{analysis_id}`エンドポイントに送信される`GET`リクエストで利用できます。 この操作に関する詳しい情報については「[リポジトリの{% data variables.product.prodname_code_scanning %}分析の取得](#get-a-code-scanning-analysis-for-a-repository)」を参照してください。 この操作でこのメディアタイプを使う場合、レスポンスには指定された分析のまとめではなく、その分析のためにアップロードされた実際のデータのサブセットが含まれます。分析のまとめは、デフォルトのメディアタイプを使った場合に返されます。 このレスポンスには、`github/alertNumber`や`github/alertUrl`プロパティなどの追加データも含まれます。 このデータは、[SARIF version 2.1.0](https://docs.oasis-open.org/sarif/sarif/v2.1.0/cs01/sarif-v2.1.0-cs01.html)でフォーマットされます。
+
+詳しい情報については、「[メディアタイプ](/rest/overview/media-types)」を参照してください。
+{% endif %}
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/rest-reference/codes-of-conduct/codes-of-conduct.md b/translations/ja-JP/data/reusables/rest-reference/codes-of-conduct/codes-of-conduct.md
new file mode 100644
index 000000000000..0bdef00a4618
--- /dev/null
+++ b/translations/ja-JP/data/reusables/rest-reference/codes-of-conduct/codes-of-conduct.md
@@ -0,0 +1,2 @@
+
+Codes of Conduct API を使用して、リポジトリの行動規範に関する情報を取得できます。 リポジトリの行動規範を取得するには、「[Get a repository](/rest/reference/repos#get-a-repository)」エンドポイントを使用します。
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/rest-reference/codespaces/codespaces.md b/translations/ja-JP/data/reusables/rest-reference/codespaces/codespaces.md
new file mode 100644
index 000000000000..68efab4aa472
--- /dev/null
+++ b/translations/ja-JP/data/reusables/rest-reference/codespaces/codespaces.md
@@ -0,0 +1,3 @@
+{% data reusables.codespaces.codespaces-api-beta-note %}
+
+{% data variables.product.prodname_codespaces %} API では、REST API を使用して {% data variables.product.prodname_codespaces %} を管理できます。 This API is available for authenticated users and OAuth Apps, but not GitHub Apps. 詳細は「[{% data variables.product.prodname_codespaces %}](/codespaces)」を参照してください。
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/rest-reference/codespaces/machines.md b/translations/ja-JP/data/reusables/rest-reference/codespaces/machines.md
new file mode 100644
index 000000000000..e8bc5519dade
--- /dev/null
+++ b/translations/ja-JP/data/reusables/rest-reference/codespaces/machines.md
@@ -0,0 +1,4 @@
+## Machines
+The Machines API allows a user to determine which machine types are available to create a codespace, either on a given repository or as an authenticated user. For more information, see "[About machine types](/codespaces/developing-in-codespaces/changing-the-machine-type-for-your-codespace#about-machine-types)."
+
+You can also use this information when changing the machine of an existing codespace by updating its `machine` property. The machine update will take place the next time the codespace is restarted. For more information, see "[Changing the machine type for your codespace](/codespaces/developing-in-codespaces/changing-the-machine-type-for-your-codespace)."
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/rest-reference/codespaces/secrets.md b/translations/ja-JP/data/reusables/rest-reference/codespaces/secrets.md
new file mode 100644
index 000000000000..088502d02057
--- /dev/null
+++ b/translations/ja-JP/data/reusables/rest-reference/codespaces/secrets.md
@@ -0,0 +1,2 @@
+## シークレット
+The Secrets API allows a user to create, list, and delete secrets (such as access tokens for cloud services) as well as assign secrets to repositories that the user has access to. These secrets are made available to the codespace at runtime. For more information, see "[Managing encrypted secrets for your codespaces](/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces)."
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/rest-reference/collaborators/invitations.md b/translations/ja-JP/data/reusables/rest-reference/collaborators/invitations.md
new file mode 100644
index 000000000000..644c97da9099
--- /dev/null
+++ b/translations/ja-JP/data/reusables/rest-reference/collaborators/invitations.md
@@ -0,0 +1,9 @@
+## 招待
+
+Repository Invitations API を使用すると、他のユーザにリポジトリでコラボレーションするようユーザや外部サービスを招待できます。 招待されたユーザ (または招待されたユーザを代行する外部サービス) は、招待を受諾または拒否できます。
+
+`repo` スコープはコードにも招待にもアクセス権を付与するのに対し、`repo:invite` [OAuth scope](/developers/apps/scopes-for-oauth-apps) は招待のみに絞ってアクセス権を付与し、リポジトリのコードにはアクセス権を付与**しない**ことに注意してください。
+
+### ユーザをリポジトリに招待する
+
+コラボレータを追加するには、API エンドポイントを使用します。 詳しい情報については「[リポジトリコラボレータを追加する](/rest/reference/collaborators#add-a-repository-collaborator)」を参照してください。
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/rest-reference/commits/comments.md b/translations/ja-JP/data/reusables/rest-reference/commits/comments.md
new file mode 100644
index 000000000000..331852b915f9
--- /dev/null
+++ b/translations/ja-JP/data/reusables/rest-reference/commits/comments.md
@@ -0,0 +1,12 @@
+## コミットのコメント
+
+### コミットコメントのカスタムメディアタイプ
+
+以下がコミットコメントでサポートされているメディアタイプです。 API におけるメディアタイプの使用に関する詳細は、[こちら](/rest/overview/media-types)を参照してください。
+
+ application/vnd.github-commitcomment.raw+json
+ application/vnd.github-commitcomment.text+json
+ application/vnd.github-commitcomment.html+json
+ application/vnd.github-commitcomment.full+json
+
+詳しい情報については、「[カスタムメディアタイプ](/rest/overview/media-types)」を参照してください。
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/rest-reference/commits/statuses.md b/translations/ja-JP/data/reusables/rest-reference/commits/statuses.md
new file mode 100644
index 000000000000..60d9378212ee
--- /dev/null
+++ b/translations/ja-JP/data/reusables/rest-reference/commits/statuses.md
@@ -0,0 +1,13 @@
+## コミットのステータス
+
+ステータス API を使用すると、外部サービスがコミットに `error`、 `failure`、`pending`、`success` ステータスを付けることができ、このステータスはコミットが含まれるプルリクエストに反映されます。
+
+ステータスには、オプションとして `description` と `target_url` を含めることもできます。これにより GitHub UI でステータスをより有用なものにできるので、非常におすすめです。
+
+たとえば、継続的インテグレーションサービスの典型的な使用方法の一つが、ステータスを使用してコミットに合格と不合格の印を付けることです。 `target_url` でビルドの出力先の完全な URL、`description` でビルドで発生したことの概要を示すといったようにします。
+
+ステータスには、どのサービスがそのステータスを提供しているかを示す `context` を含めることができます。 たとえば、継続的インテグレーションサービスのプッシュステータスに `ci` のコンテキストを、セキュリティ監査ツールのプッシュステータスに `security` のコンテキストを含めることができます。 その後、[特定のリファレンス複合的なステータス](/rest/reference/commits#get-the-combined-status-for-a-specific-reference)を使用して、コミットの全体のステータスを取得できます。
+
+`repo` スコープはコードにもステータスにもアクセス権を付与するのに対し、`repo:status` [OAuth scope](/developers/apps/scopes-for-oauth-apps) はステータスのみに絞ってアクセス権を付与し、リポジトリのコードにはアクセス権を付与**しない**ことに注意してください。
+
+GitHub App を開発していて、外部サービスについて詳細な情報を提供したい場合は、[Checks API](/rest/reference/checks) を使用できます。
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/rest-reference/dependabot/dependabot.md b/translations/ja-JP/data/reusables/rest-reference/dependabot/dependabot.md
new file mode 100644
index 000000000000..29733dde1ed8
--- /dev/null
+++ b/translations/ja-JP/data/reusables/rest-reference/dependabot/dependabot.md
@@ -0,0 +1,3 @@
+The {% data variables.product.prodname_dependabot %} Secrets API lets you create, update, delete, and retrieve information about encrypted secrets. {% data reusables.actions.about-secrets %} For more information, see "[Managing encrypted secrets for Dependabot](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-encrypted-secrets-for-dependabot)."
+
+{% data reusables.actions.actions-authentication %} {% data variables.product.prodname_github_apps %} must have the `dependabot_secrets` permission to use this API. 認証されたユーザは、シークレットを作成、更新、または読み取るために、リポジトリへのコラボレータアクセス権を持っている必要があります。
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/rest-reference/deployments/deployments.md b/translations/ja-JP/data/reusables/rest-reference/deployments/deployments.md
new file mode 100644
index 000000000000..7a0765075b9d
--- /dev/null
+++ b/translations/ja-JP/data/reusables/rest-reference/deployments/deployments.md
@@ -0,0 +1,46 @@
+デプロイメントとは、特定の ref (ブランチ、SHA、タグ) を配備するためるリクエストです。 GitHub は、 外部サーバーがリッスンでき、新しいデプロイメントが作成されたときに実行される [`deployment` イベント](/developers/webhooks-and-events/webhook-events-and-payloads#deployment)をディスバッチします。 デプロイメントにより、開発者や Organization はデプロイメントを中心として、さまざまな種類のアプリケーション (ウェブ、ネイティブなど) を提供するための実装に関する詳細を気にすることなく、疎結合ツールを構築できます。
+
+デプロイメントのステータスを使用すると、外部サービスがデプロイメントに `error`、`failure`、`pending`、`in_progress`、`queued`、`success` ステータスを付けることができ、[`deployment_status` イベント](/developers/webhooks-and-events/webhook-events-and-payloads#deployment_status)をリッスンするシステムがその情報を使用できます。
+
+デプロイメントのステータスには、オプションとして `description` と `log_url` を含めることもできます。これによりデプロイメントのステータスがより有用なものになるので、非常におすすめです。 `log_url` はデプロイメントの出力の完全な URL で、`description` はデプロイメントで発生したことの概要を示すものです。
+
+GitHub は、新しいデプロイメント、デプロイメントのステータスが作成されたときに、`deployment` イベント、`deployment_status` イベントをディスパッチします。 これらのイベントにより、サードパーティのインテグレーションがデプロイメントのリクエストに対する応答を受けとり、進展があるたびにステータスを更新できます。
+
+以下は、これらの相互作用がどのように機能するかを示す簡単なシーケンス図です。
+
+```
++---------+ +--------+ +-----------+ +-------------+
+| Tooling | | GitHub | | 3rd Party | | Your Server |
++---------+ +--------+ +-----------+ +-------------+
+ | | | |
+ | Create Deployment | | |
+ |--------------------->| | |
+ | | | |
+ | Deployment Created | | |
+ |<---------------------| | |
+ | | | |
+ | | Deployment Event | |
+ | |---------------------->| |
+ | | | SSH+Deploys |
+ | | |-------------------->|
+ | | | |
+ | | Deployment Status | |
+ | |<----------------------| |
+ | | | |
+ | | | Deploy Completed |
+ | | |<--------------------|
+ | | | |
+ | | Deployment Status | |
+ | |<----------------------| |
+ | | | |
+```
+
+GitHub は、あなたのサーバーに実際にアクセスすることはないということは覚えておきましょう。 デプロイメントイベントとやり取りするかどうかは、サードパーティインテグレーション次第です。 複数のシステムがデプロイメントイベントをリッスンできます。コードをサーバーにプッシュする、ネイティブコードを構築するなどを行うかどうかは、それぞれのシステムが決めることができます。
+
+Note that the `repo_deployment` [OAuth scope](/developers/apps/scopes-for-oauth-apps) grants targeted access to deployments and deployment statuses **without** granting access to repository code, while the {% ifversion not ghae %}`public_repo` and{% endif %}`repo` scopes grant permission to code as well.
+
+### 非アクティブのデプロイメント
+
+When you set the state of a deployment to `success`, then all prior non-transient, non-production environment deployments in the same repository with the same environment name will become `inactive`. これを回避するには、デプロイメントのステータスを作成する前に、`auto_inactive` を `false` に設定します。
+
+`state` を `inactive` に設定することで、一時的な環境が存在しなくなったことを伝えることができます。 `state` を `inactive` に設定すると、{% data variables.product.prodname_dotcom %} でデプロイメントが `destroyed` と表示され、アクセス権が削除されます。
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/rest-reference/deployments/environments.md b/translations/ja-JP/data/reusables/rest-reference/deployments/environments.md
new file mode 100644
index 000000000000..311a00628296
--- /dev/null
+++ b/translations/ja-JP/data/reusables/rest-reference/deployments/environments.md
@@ -0,0 +1,5 @@
+## 環境
+
+Environments APIを使うと、環境を作成、設定、削除できます。 For more information about environments, see "[Using environments for deployment](/actions/deployment/using-environments-for-deployment)." 環境のシークレットの管理については「[シークレット](/rest/reference/actions#secrets)」を参照してください。
+
+{% data reusables.gated-features.environments %}
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/rest-reference/deployments/keys.md b/translations/ja-JP/data/reusables/rest-reference/deployments/keys.md
new file mode 100644
index 000000000000..ae5ed1ae39bb
--- /dev/null
+++ b/translations/ja-JP/data/reusables/rest-reference/deployments/keys.md
@@ -0,0 +1,5 @@
+## デプロイキー
+
+{% data reusables.repositories.deploy-keys %}
+
+デプロイキーは、以下の API エンドポイントを使用するか、GitHub を使用することでセットアップできます。 GitHub でデプロイキーを設定する方法については、「[デプロイキーを管理する](/developers/overview/managing-deploy-keys)」を参照してください。
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/rest-reference/deployments/statuses.md b/translations/ja-JP/data/reusables/rest-reference/deployments/statuses.md
new file mode 100644
index 000000000000..5e0c64a07370
--- /dev/null
+++ b/translations/ja-JP/data/reusables/rest-reference/deployments/statuses.md
@@ -0,0 +1 @@
+## デプロイメントステータス
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/rest-reference/enterprise-admin/admin-stats.md b/translations/ja-JP/data/reusables/rest-reference/enterprise-admin/admin-stats.md
new file mode 100644
index 000000000000..bce5cee324ac
--- /dev/null
+++ b/translations/ja-JP/data/reusables/rest-reference/enterprise-admin/admin-stats.md
@@ -0,0 +1,3 @@
+## 管理統計
+
+管理統計 API は、インストールに関するさまざまなメトリクスを提供します。 *[認証された](/rest/overview/resources-in-the-rest-api#authentication)サイト管理者のみが使用できます。*通常のユーザがアクセスしようとすると、`404` レスポンスを受け取ります。
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/rest-reference/enterprise-admin/announcements.md b/translations/ja-JP/data/reusables/rest-reference/enterprise-admin/announcements.md
new file mode 100644
index 000000000000..bd7a3dd067ea
--- /dev/null
+++ b/translations/ja-JP/data/reusables/rest-reference/enterprise-admin/announcements.md
@@ -0,0 +1,3 @@
+## アナウンス
+
+アナウンス API を使用すると、Enterprise でグローバルなアナウンスバナーを管理できます。 詳しい情報については「[Enterprise のユーザメッセージをカスタマイズする](/admin/user-management/customizing-user-messages-for-your-enterprise#creating-a-global-announcement-banner)」を参照してください。
diff --git a/translations/ja-JP/data/reusables/rest-reference/enterprise-admin/audit-log.md b/translations/ja-JP/data/reusables/rest-reference/enterprise-admin/audit-log.md
new file mode 100644
index 000000000000..2c3465102287
--- /dev/null
+++ b/translations/ja-JP/data/reusables/rest-reference/enterprise-admin/audit-log.md
@@ -0,0 +1 @@
+## Audit log
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/rest-reference/enterprise-admin/billing.md b/translations/ja-JP/data/reusables/rest-reference/enterprise-admin/billing.md
new file mode 100644
index 000000000000..3d85c5d0c748
--- /dev/null
+++ b/translations/ja-JP/data/reusables/rest-reference/enterprise-admin/billing.md
@@ -0,0 +1 @@
+## 支払い
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/rest-reference/enterprise-admin/enterprise-admin.md b/translations/ja-JP/data/reusables/rest-reference/enterprise-admin/enterprise-admin.md
new file mode 100644
index 000000000000..18c6c334a98b
--- /dev/null
+++ b/translations/ja-JP/data/reusables/rest-reference/enterprise-admin/enterprise-admin.md
@@ -0,0 +1,44 @@
+{% ifversion fpt or ghec %}
+
+{% note %}
+
+**注釈:** この記事は {% data variables.product.prodname_ghe_cloud %} に適用されます。 {% data variables.product.prodname_ghe_managed %}あるいは{% data variables.product.prodname_ghe_server %}のバージョンを見るには、**{% data ui.pages.article_version %}**ドロップダウンメニューを使ってください。
+
+{% endnote %}
+
+{% endif %}
+
+### エンドポイント URL
+
+REST API エンドポイント{% ifversion ghes %}（[管理コンソール](#management-console) API エンドポイントを除く）{% endif %}の前には、次の URL が付けられます。
+
+```shell
+{% data variables.product.api_url_pre %}
+```
+
+{% ifversion fpt or ghec %}
+When endpoints include `{enterprise}`, replace `{enterprise}` with the handle for your enterprise account, which is included in the URL for your enterprise settings. For example, if your enterprise account is located at `https://github.com/enterprises/octo-enterprise`, replace `{enterprise}` with `octo-enterprise`.
+{% endif %}
+
+{% ifversion ghes %}
+[管理コンソール](#management-console) API エンドポイントには、ホスト名のみがプレフィックスとして付加されます。
+
+```shell
+http(s)://hostname/
+```
+{% endif %}
+{% ifversion ghae or ghes %}
+### 認証
+
+{% data variables.product.product_name %} のインストールの API エンドポイントは、GitHub.com APIと[同じ認証方法](/rest/overview/resources-in-the-rest-api#authentication)を受け入れます。 **[OAuth トークン](/apps/building-integrations/setting-up-and-registering-oauth-apps/)**{% ifversion ghes %}（[認証 API](/rest/reference/oauth-authorizations#create-a-new-authorization) を使用して作成可能）{% endif %}または **[Basic 認証](/rest/overview/resources-in-the-rest-api#basic-authentication)**で自分自身を認証できます。 {% ifversion ghes %} Enterprise 固有のエンドポイントで使用する場合、OAuthトークンには `site_admin` [OAuth スコープ](/developers/apps/scopes-for-oauth-apps#available-scopes)が必要です。{% endif %}
+
+Enterprise 管理 API エンドポイントには、認証された {% data variables.product.product_name %} サイト管理者のみがアクセスできます。{% ifversion ghes %}ただし、[Management Console のパスワード](/enterprise/admin/articles/accessing-the-management-console/)が必要な [Management Console](#management-console) API は除きます。{% endif %}
+
+{% endif %}
+
+{% ifversion ghae or ghes %}
+### バージョン情報
+
+Enterprise の現在のバージョンは、すべての API のレスポンスヘッダで返されます: `X-GitHub-Enterprise-Version: {{currentVersion}}.0` [メタエンドポイント](/rest/reference/meta/)を呼び出して、現在のバージョンを読み取ることもできます。
+
+{% endif %}
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/rest-reference/enterprise-admin/global-webhooks.md b/translations/ja-JP/data/reusables/rest-reference/enterprise-admin/global-webhooks.md
new file mode 100644
index 000000000000..6e73404bc52a
--- /dev/null
+++ b/translations/ja-JP/data/reusables/rest-reference/enterprise-admin/global-webhooks.md
@@ -0,0 +1,5 @@
+## グローバル webhook
+
+グローバル webhook は Enterprise にインストールされています。 グローバル webhook を使用して、Engerprise のユーザ、Organization、Team、およびリポジトリのルールを自動的に監視、対応、強制することができます。 グローバル webhook は、[Organization](/developers/webhooks-and-events/webhook-events-and-payloads#organization)、[ユーザ](/developers/webhooks-and-events/webhook-events-and-payloads#user)、[リポジトリ](/developers/webhooks-and-events/webhook-events-and-payloads#repository)、[Team](/developers/webhooks-and-events/webhook-events-and-payloads#team)、[メンバー](/developers/webhooks-and-events/webhook-events-and-payloads#member)、[メンバーシップ](/developers/webhooks-and-events/webhook-events-and-payloads#membership)、[フォーク](/developers/webhooks-and-events/webhook-events-and-payloads#fork)、[ping](/developers/webhooks-and-events/about-webhooks#ping-event) イベントタイプをサブスクライブできます。
+
+*この API は、[認証された](/rest/overview/resources-in-the-rest-api#authentication)サイト管理者のみが使用できます。*通常のユーザがアクセスしようとすると、`404` レスポンスを受け取ります。 グローバル webhook の設定方法については、[グローバル webhookについて](/enterprise/admin/user-management/about-global-webhooks)を参照してください。
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/rest-reference/enterprise-admin/ldap.md b/translations/ja-JP/data/reusables/rest-reference/enterprise-admin/ldap.md
new file mode 100644
index 000000000000..2b3cb9529450
--- /dev/null
+++ b/translations/ja-JP/data/reusables/rest-reference/enterprise-admin/ldap.md
@@ -0,0 +1,5 @@
+## LDAP
+
+LDAP API を使用して、{% data variables.product.product_name %} ユーザまたは Team とそのリンクされた LDAP エントリ間のアカウント関係を更新するか、新しい同期をキューに入れることができます。
+
+LDAP マッピングエンドポイントを使用すると、ユーザまたは Team がマッピングする識別名（DN）を更新できます。 LDAP エンドポイントは通常、{% data variables.product.product_name %} アプライアンスで [LDAP 同期が有効](/enterprise/admin/authentication/using-ldap)になっている場合にのみ有効です。 [ユーザの LDAP マッピングの更新](#update-ldap-mapping-for-a-user)エンドポイントは、LDAP 同期が無効になっている場合でも、LDAP が有効になっていれば使用できます。
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/rest-reference/enterprise-admin/license.md b/translations/ja-JP/data/reusables/rest-reference/enterprise-admin/license.md
new file mode 100644
index 000000000000..5aaab5f56d42
--- /dev/null
+++ b/translations/ja-JP/data/reusables/rest-reference/enterprise-admin/license.md
@@ -0,0 +1,3 @@
+## ライセンス
+
+ライセンス API は、Enterprise ライセンスに関する情報を提供します。 *[認証された](/rest/overview/resources-in-the-rest-api#authentication)サイト管理者のみが使用できます。*通常のユーザがアクセスしようとすると、`404` レスポンスを受け取ります。
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/rest-reference/enterprise-admin/management-console.md b/translations/ja-JP/data/reusables/rest-reference/enterprise-admin/management-console.md
new file mode 100644
index 000000000000..e86fa2e8eb7d
--- /dev/null
+++ b/translations/ja-JP/data/reusables/rest-reference/enterprise-admin/management-console.md
@@ -0,0 +1,29 @@
+## Management Console
+
+管理コンソール API は、{% data variables.product.product_name %} インストールの管理に役立ちます。
+
+{% tip %}
+
+Management Console への API 呼び出しを行うときは、ポート番号を明示的に設定する必要があります。 Enterprise で TLS が有効になっている場合、ポート番号は `8443` です。それ以外の場合、ポート番号は `8080` です。
+
+ポート番号を提供しない場合は、自動的にリダイレクトに従うようにツールを設定する必要があります。
+
+{% data variables.product.product_name %} は、[独自の TLS 証明書](/enterprise/admin/guides/installation/configuring-tls/)を追加する前は自己署名証明書を使用するため、`cURL` を使用するときに [`-k` フラグ](http://curl.haxx.se/docs/manpage.html#-k)を追加する必要もあるかもしれません。
+
+{% endtip %}
+
+### 認証
+
+[Management Console のパスワード](/enterprise/admin/articles/accessing-the-management-console/)を認証トークンとして [`/setup/api/start`](#create-a-github-enterprise-server-license) を除くすべての Management Console API エンドポイントに渡す必要があります。
+
+`api_key` パラメータを使用して、リクエストごとにこのトークンを送信します。 例:
+
+```shell
+$ curl -L 'https://hostname:admin_port/setup/api?api_key=your-amazing-password'
+```
+
+標準の HTTP 認証を使用してこのトークンを送信することもできます。 例:
+
+```shell
+$ curl -L -u "api_key:your-amazing-password" 'https://hostname:admin_port/setup/api'
+```
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/rest-reference/enterprise-admin/org-pre-receive-hooks.md b/translations/ja-JP/data/reusables/rest-reference/enterprise-admin/org-pre-receive-hooks.md
new file mode 100644
index 000000000000..10728b989494
--- /dev/null
+++ b/translations/ja-JP/data/reusables/rest-reference/enterprise-admin/org-pre-receive-hooks.md
@@ -0,0 +1,16 @@
+## Organization pre-receive フック
+
+Organization pre-receive フック API を使用すると、Organization で使用可能な pre-receive フックの適用を表示および変更できます。
+
+### オブジェクトの属性
+
+| 名前 | 種類 | 説明 |
+| -------------------------------- | --------- | ------------------------ |
+| `name` | `string` | フックの名前。 |
+| `enforcement` | `string` | このリポジトリでのフックの適用状態。 |
+| `allow_downstream_configuration` | `boolean` | リポジトリが適用をオーバーライドできるかどうか。 |
+| `configuration_url` | `string` | 適用設定されているエンドポイントの URL。 |
+
+*適用*可能な値は、`enabled`、`disabled`、`testing` です。 `disabled` は、pre-receive フックが実行されないことを示します。 `enabled` は、それが実行され、ゼロ以外の状態になるプッシュを拒否することを示します。 `testing` は、スクリプトは実行されるが、プッシュが拒否されないことを示します。
+
+`configuration_url` は、このエンドポイントまたはこのフックのグローバル設定へのリンクです。 サイトアドミンのみがグローバル設定にアクセスできます。
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/rest-reference/enterprise-admin/orgs.md b/translations/ja-JP/data/reusables/rest-reference/enterprise-admin/orgs.md
new file mode 100644
index 000000000000..551911049413
--- /dev/null
+++ b/translations/ja-JP/data/reusables/rest-reference/enterprise-admin/orgs.md
@@ -0,0 +1,3 @@
+## Organization
+
+Organization 管理 API を使用すると、Enterprise に Organization を作成できます。 *[認証された](/rest/overview/resources-in-the-rest-api#authentication)サイト管理者のみが使用できます。*通常のユーザがアクセスしようとすると、`404` レスポンスを受け取ります。
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/rest-reference/enterprise-admin/pre-receive-environments.md b/translations/ja-JP/data/reusables/rest-reference/enterprise-admin/pre-receive-environments.md
new file mode 100644
index 000000000000..e8fceb4de645
--- /dev/null
+++ b/translations/ja-JP/data/reusables/rest-reference/enterprise-admin/pre-receive-environments.md
@@ -0,0 +1,25 @@
+## pre-receive 環境
+
+pre-receive 環境 API を使用すると、pre-receive フックの環境を作成、一覧表示、更新、および削除できます。 *[認証された](/rest/overview/resources-in-the-rest-api#authentication)サイト管理者のみが使用できます。*通常のユーザがアクセスしようとすると、`404` レスポンスを受け取ります。
+
+### オブジェクトの属性
+
+#### pre-receive 環境
+
+| 名前 | 種類 | 説明 |
+| --------------------- | --------- | ---------------------------------------------------------------- |
+| `name` | `string` | UI に表示される環境の名前。 |
+| `image_url` | `string` | ダウンロードおよび抽出される tarball への URL。 |
+| `default_environment` | `boolean` | これが {% data variables.product.product_name %} に同梱されるデフォルト環境かどうか。 |
+| `download` | `オブジェクト` | この環境のダウンロードステータス。 |
+| `hooks_count` | `integer` | この環境を使用する pre-receive フックの数。 |
+
+#### pre-receive 環境のダウンロード
+
+| 名前 | 種類 | 説明 |
+| --------------- | -------- | --------------------- |
+| `state` | `string` | 最新のダウンロードの状態。 |
+| `downloaded_at` | `string` | 最新のダウンロードの開始時刻。 |
+| `message` | `string` | 失敗時に、エラーメッセージが生成されます。 |
+
+`state`が取り得る値は、`not_started`、`in_progress`、`success`、`failed`です。
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/rest-reference/enterprise-admin/pre-receive-hooks.md b/translations/ja-JP/data/reusables/rest-reference/enterprise-admin/pre-receive-hooks.md
new file mode 100644
index 000000000000..93114d6d8713
--- /dev/null
+++ b/translations/ja-JP/data/reusables/rest-reference/enterprise-admin/pre-receive-hooks.md
@@ -0,0 +1,18 @@
+## pre-receive フック
+
+pre-receive フック API を使用すると、pre-receive フックを作成、一覧表示、更新、および削除できます。 *これは[認証された](/rest/overview/resources-in-the-rest-api#authentication)サイト管理者のみが使用できます。*通常のユーザがアクセスしようとすると、`404` レスポンスを受け取ります。
+
+### オブジェクトの属性
+
+#### pre-receive フック
+
+| 名前 | 種類 | 説明 |
+| -------------------------------- | --------- | ------------------------------------ |
+| `name` | `string` | フックの名前。 |
+| `script` | `string` | フックが実行するスクリプト。 |
+| `script_repository` | `オブジェクト` | スクリプトが保存されているGitHubリポジトリ。 |
+| `environment` | `オブジェクト` | スクリプトが実行される pre-receive 環境。 |
+| `enforcement` | `string` | このフックの適用状態。 |
+| `allow_downstream_configuration` | `boolean` | 適用の Org レベルまたは repo レベルでのオーバーライドの可否。 |
+
+*適用*可能な値は、`enabled`、`disabled`、`testing` です。 `disabled` は、pre-receive フックが実行されないことを示します。 `enabled` は、それが実行され、ゼロ以外の状態になるプッシュを拒否することを示します。 `testing` は、スクリプトは実行されるが、プッシュが拒否されないことを示します。
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/rest-reference/enterprise-admin/repo-pre-receive-hooks.md b/translations/ja-JP/data/reusables/rest-reference/enterprise-admin/repo-pre-receive-hooks.md
new file mode 100644
index 000000000000..b4a47cd12821
--- /dev/null
+++ b/translations/ja-JP/data/reusables/rest-reference/enterprise-admin/repo-pre-receive-hooks.md
@@ -0,0 +1,15 @@
+## リポジトリ pre-receive フック
+
+リポジトリ pre-receive フック API を使用すると、リポジトリで使用可能な pre-receive フックの適用を表示および変更できます。
+
+### オブジェクトの属性
+
+| 名前 | 種類 | 説明 |
+| ------------------- | -------- | ---------------------- |
+| `name` | `string` | フックの名前。 |
+| `enforcement` | `string` | このリポジトリでのフックの適用状態。 |
+| `configuration_url` | `string` | 適用設定されているエンドポイントの URL。 |
+
+*適用*可能な値は、`enabled`、`disabled`、`testing` です。 `disabled` は、pre-receive フックが実行されないことを示します。 `enabled` は、それが実行され、ゼロ以外の状態になるプッシュを拒否することを示します。 `testing` は、スクリプトは実行されるが、プッシュが拒否されないことを示します。
+
+`configuration_url` は、このリポジトリ、その Organization のオーナー、またはグローバル設定へのリンクである場合があります。 `configuration_url` でエンドポイントにアクセスする権限は、所有者またはサイトアドミンレベルで決定されます。
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/rest-reference/enterprise-admin/users.md b/translations/ja-JP/data/reusables/rest-reference/enterprise-admin/users.md
new file mode 100644
index 000000000000..f20c48e7776d
--- /dev/null
+++ b/translations/ja-JP/data/reusables/rest-reference/enterprise-admin/users.md
@@ -0,0 +1,3 @@
+## ユーザ
+
+ユーザ管理 API では、Enterprise でユーザをサスペンド{% ifversion ghes %}、サスペンド解除、昇格、降格、{% endif %}{% ifversion ghae %}およびサスペンド解除{% endif %}できます。 *これは[認証された](/rest/overview/resources-in-the-rest-api#authentication)サイト管理者のみが使用できます。*通常のユーザがアクセスしようとすると、`403` レスポンスを受け取ります。
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/rest-reference/gists/comments.md b/translations/ja-JP/data/reusables/rest-reference/gists/comments.md
new file mode 100644
index 000000000000..5af827bef370
--- /dev/null
+++ b/translations/ja-JP/data/reusables/rest-reference/gists/comments.md
@@ -0,0 +1,10 @@
+## コメント
+
+### Gist コメントのカスタムメディアタイプ
+
+これらは、Gist コメントでサポートされているメディアタイプです。
+
+ application/vnd.github.VERSION.raw
+ application/vnd.github.VERSION.base64
+
+メディアタイプの詳しい情報については、「[カスタムメディアタイプ](/rest/overview/media-types)」を参照してください。
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/rest-reference/gists/gists.md b/translations/ja-JP/data/reusables/rest-reference/gists/gists.md
new file mode 100644
index 000000000000..bfcd0635879e
--- /dev/null
+++ b/translations/ja-JP/data/reusables/rest-reference/gists/gists.md
@@ -0,0 +1,22 @@
+### 認証
+
+パブリック Gist {% ifversion ghae or ghes %} を読んで、トークンなしで匿名ユーザ向けに作成できます。{% else %} 匿名でも、Gist を作成するには GitHub にサインインする必要があります。{% endif %}ユーザに代わって Gist を読み書きするには、Gist OAuth スコープとトークンが必要です。 詳しい情報については、「[OAuth App のスコープ](/developers/apps/scopes-for-oauth-apps)」を参照してください。
+
+
+
+### 切り捨て
+
+Gist API は、Gist 内の各ファイルに最大 1 メガバイトのコンテンツを提供します。 API を介して Gist として返される各ファイルには、`truncated` というキーがあります。 `truncated` が `true` の場合、ファイルが大きすぎるためコンテンツの一部のみが `content` で返されました。
+
+ファイルのフルコンテンツが必要な場合は、`raw_url` で指定された URL に `GET` リクエストを送信できます。 10 メガバイトを超えるファイルの場合、`git_pull_url` が提供する URL を介して Gist をクローンする必要があることに注意してください。
+
+ファイル総数が 300 個を超えると、特定のファイルの内容が切り捨てられることに加えて、ファイルリスト全体が切り捨てられる場合があります。 最上位の `truncated` キーが `true` の場合、最初の 300 ファイルのみがファイルリストに返されます。 Gist のファイルをすべてフェッチする必要がある場合は、`git_pull_url` が提供する URL を介して Gist のクローンを作成する必要があります。
+
+### Gist のカスタムメディアタイプ
+
+これらは、Gist コンテンツをフェッチするためにサポートされているメディアタイプです。
+
+ application/vnd.github.VERSION.raw
+ application/vnd.github.VERSION.base64
+
+詳しい情報については、「[メディアタイプ](/rest/overview/media-types)」を参照してください。
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/rest-reference/git/blobs.md b/translations/ja-JP/data/reusables/rest-reference/git/blobs.md
new file mode 100644
index 000000000000..ee59e76c9363
--- /dev/null
+++ b/translations/ja-JP/data/reusables/rest-reference/git/blobs.md
@@ -0,0 +1,12 @@
+## Blob
+
+Git blob (バイナリラージオブジェクト) は、各ファイルのコンテンツをリポジトリに保存する際に使用されるオブジェクトタイプです。 ファイルの SHA-1 ハッシュが計算され、blob オブジェクトに保存されます。 これらのエンドポイントを使用すると、{% data variables.product.product_name %} 上の Git データベースに対して [blob オブジェクト](https://git-scm.com/book/en/v1/Git-Internals-Git-Objects)の読み書きができます。 blob は[これらのカスタムメディアタイプ](#custom-media-types-for-blobs)を利用します。 API でのメディアタイプの使用について詳しくは、[こちら](/rest/overview/media-types)をご覧ください。
+
+### Blob のカスタムメディアタイプ
+
+これらは、blob でサポートされているメディアタイプです。
+
+ application/json
+ application/vnd.github.VERSION.raw
+
+詳しい情報については、「[メディアタイプ](/rest/overview/media-types)」を参照してください。
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/rest-reference/git/commits.md b/translations/ja-JP/data/reusables/rest-reference/git/commits.md
new file mode 100644
index 000000000000..84652eeda9f9
--- /dev/null
+++ b/translations/ja-JP/data/reusables/rest-reference/git/commits.md
@@ -0,0 +1,3 @@
+## コミット
+
+Git コミットは、Git リポジトリ内の階層（[Git ツリー](/rest/reference/git#trees)）とファイルのコンテンツ（[Git blob](/rest/reference/git#blobs)）のスナップショットです。 これらのエンドポイントを使用すると、{% data variables.product.product_name %} 上の Git データベースに対して [コミットオブジェクト](https://git-scm.com/book/en/v1/Git-Internals-Git-Objects#Commit-Objects)の読み書きができます。
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/rest-reference/git/git.md b/translations/ja-JP/data/reusables/rest-reference/git/git.md
new file mode 100644
index 000000000000..be25fb46ea33
--- /dev/null
+++ b/translations/ja-JP/data/reusables/rest-reference/git/git.md
@@ -0,0 +1 @@
+Git Database APIでは、{% data variables.product.product_name %}上のGitデータベースに対してRaw形式のGitオブジェクトを読み書きしたり、リファレンス (ブランチheadやタグ) をリストおよび更新したりすることができます。 Git Database API の使用方法の詳細については、「[Git データ API の概要](/rest/guides/getting-started-with-the-git-database-api)」を参照してください。
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/rest-reference/git/refs.md b/translations/ja-JP/data/reusables/rest-reference/git/refs.md
new file mode 100644
index 000000000000..9c11b786639c
--- /dev/null
+++ b/translations/ja-JP/data/reusables/rest-reference/git/refs.md
@@ -0,0 +1,3 @@
+## リファレンス
+
+Git リファレンス（`git ref`）は、Git コミット SHA-1 ハッシュを含むファイルです。 Gitコミットを参照するときは、ハッシュではなく覚えやすい名前の Git リファレンスを使用できます。 Git リファレンスは、新しいコミットを指すように書き換えることができます。 ブランチは、新しい Git コミットハッシュを保存する Git リファレンスです。 これらのエンドポイントを使用すると、{% data variables.product.product_name %} 上の Git データベースに対して [リファレンス](https://git-scm.com/book/en/v1/Git-Internals-Git-References)の読み書きができます。
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/rest-reference/git/tags.md b/translations/ja-JP/data/reusables/rest-reference/git/tags.md
new file mode 100644
index 000000000000..70d709864c23
--- /dev/null
+++ b/translations/ja-JP/data/reusables/rest-reference/git/tags.md
@@ -0,0 +1,3 @@
+## タグ
+
+Git タグは [Git リファレンス](/rest/reference/git#refs)に似ていますが、変更しないことを指す Git コミットです。 Git タグは、特定のリリースを指すときに役立ちます。 これらのエンドポイントを使用すると、{% data variables.product.product_name %} 上の Git データベースに対して [タグオブジェクト](https://git-scm.com/book/en/v1/Git-Internals-Git-References#Tags)の読み書きができます。 Git タグ API は、[アノテーションされたタグオブジェクト](https://git-scm.com/book/en/v1/Git-Internals-Git-References#Tags)のみをサポートし、軽量タグはサポートしません。
diff --git a/translations/ja-JP/data/reusables/rest-reference/git/trees.md b/translations/ja-JP/data/reusables/rest-reference/git/trees.md
new file mode 100644
index 000000000000..9ef490c84a7c
--- /dev/null
+++ b/translations/ja-JP/data/reusables/rest-reference/git/trees.md
@@ -0,0 +1,3 @@
+## ツリー
+
+Git ツリーオブジェクトは、Git リポジトリ内のファイル間の階層を作成します。 Git ツリーオブジェクトを使用して、ディレクトリとそこに含まれるファイルの関係を作成できます。 これらのエンドポイントを使用すると、{% data variables.product.product_name %} 上の Git データベースに対して [ツリーオブジェクト](https://git-scm.com/book/en/v1/Git-Internals-Git-Objects#Tree-Objects)の読み書きができます。
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/rest-reference/gitignore/gitignore.md b/translations/ja-JP/data/reusables/rest-reference/gitignore/gitignore.md
new file mode 100644
index 000000000000..f7037eaa9553
--- /dev/null
+++ b/translations/ja-JP/data/reusables/rest-reference/gitignore/gitignore.md
@@ -0,0 +1,9 @@
+When you create a new repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} via the API, you can specify a [.gitignore template](/github/getting-started-with-github/ignoring-files) to apply to the repository upon creation. .gitignore テンプレート API は、{% data variables.product.product_name %} の [.gitignore リポジトリ](https://github.com/github/gitignore)からテンプレートを一覧表示してフェッチします。
+
+### gitignore のカスタムメディアタイプ
+
+gitignore テンプレートを取得するときに、このカスタムメディアタイプを使用できます。
+
+ application/vnd.github.VERSION.raw
+
+詳しい情報については、「[メディアタイプ](/rest/overview/media-types)」を参照してください。
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/rest-reference/interactions/interactions.md b/translations/ja-JP/data/reusables/rest-reference/interactions/interactions.md
new file mode 100644
index 000000000000..8c32b73f4b49
--- /dev/null
+++ b/translations/ja-JP/data/reusables/rest-reference/interactions/interactions.md
@@ -0,0 +1 @@
+リポジトリに対するインタラクションには、コミット、Issueのオープン、プルリクエストの作成があります。 インタラクションAPIを使用すると、オーナーまたは管理者アクセス権のあるユーザはパブリックリポジトリの操作を一時的に特定のユーザのタイプに制限することができます。
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/rest-reference/interactions/orgs.md b/translations/ja-JP/data/reusables/rest-reference/interactions/orgs.md
new file mode 100644
index 000000000000..2f0cd2276ca5
--- /dev/null
+++ b/translations/ja-JP/data/reusables/rest-reference/interactions/orgs.md
@@ -0,0 +1,9 @@
+## Organization
+
+OrganizationのインタラクションAPIを使用すると、OrganizationのオーナーはOrganizationのパブリックリポジトリでコメント、Issueのオープン、プルリクエストの作成ができるユーザのタイプを一時的に制限することができます。 {% data reusables.interactions.interactions-detail %} {% data variables.product.product_name %} ユーザのタイプについては以下を参照してください。
+
+* Organizationの{% data reusables.interactions.existing-user-limit-definition %}
+* Organizationの{% data reusables.interactions.contributor-user-limit-definition %}
+* Organizationの{% data reusables.interactions.collaborator-user-limit-definition %}
+
+Organizationレベルでインタラクション制限を設定すると、Organizationが所有する個々のリポジトリに設定されているインタラクション制限は上書きされます。 Organizationが所有する個々のリポジトリに対して異なるインタラクション制限を設定するには、かわりに[リポジトリ](#repository)インタラクションエンドポイントを使用してください。
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/rest-reference/interactions/repos.md b/translations/ja-JP/data/reusables/rest-reference/interactions/repos.md
new file mode 100644
index 000000000000..e61195588ba6
--- /dev/null
+++ b/translations/ja-JP/data/reusables/rest-reference/interactions/repos.md
@@ -0,0 +1,9 @@
+## リポジトリ
+
+リポジトリのインタラクションAPIを使用すると、オーナーまたは管理者アクセス権のあるユーザはパブリックリポジトリでコメント、Issueのオープン、プルリクエストの作成ができるユーザのタイプを一時的に制限することができます。 {% data reusables.interactions.interactions-detail %} {% data variables.product.product_name %} ユーザのタイプについては以下を参照してください。
+
+* リポジトリの{% data reusables.interactions.existing-user-limit-definition %}
+* リポジトリの{% data reusables.interactions.contributor-user-limit-definition %}
+* リポジトリの{% data reusables.interactions.collaborator-user-limit-definition %}
+
+リポジトリを所有しているユーザまたはOrganizationについてインタラクション制限を有効にしている場合、個々のリポジトリについてその制限を変更することはできません。 インタラクション制限を変更するには、[ユーザ](#user)または[Organization](#organization)インタラクションエンドポイントを使用してください。
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/rest-reference/interactions/users.md b/translations/ja-JP/data/reusables/rest-reference/interactions/users.md
new file mode 100644
index 000000000000..471140cf5309
--- /dev/null
+++ b/translations/ja-JP/data/reusables/rest-reference/interactions/users.md
@@ -0,0 +1,9 @@
+## ユーザ
+
+The User Interactions API allows you to temporarily restrict which type of user can comment, open issues, or create pull requests on your public repositories. {% data reusables.interactions.interactions-detail %} {% data variables.product.product_name %} ユーザのタイプについては以下を参照してください。
+
+* {% data reusables.interactions.existing-user-limit-definition %} from interacting with your repositories.
+* {% data reusables.interactions.contributor-user-limit-definition %} from interacting with your repositories.
+* {% data reusables.interactions.collaborator-user-limit-definition %} from interacting with your repositories.
+
+Setting the interaction limit at the user level will overwrite any interaction limits that are set for individual repositories owned by the user. To set different interaction limits for individual repositories owned by the user, use the [Repository](#repository) interactions endpoints instead.
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/rest-reference/issues/assignees.md b/translations/ja-JP/data/reusables/rest-reference/issues/assignees.md
new file mode 100644
index 000000000000..c5dcc55fe987
--- /dev/null
+++ b/translations/ja-JP/data/reusables/rest-reference/issues/assignees.md
@@ -0,0 +1 @@
+## アサインされた人
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/rest-reference/issues/comments.md b/translations/ja-JP/data/reusables/rest-reference/issues/comments.md
new file mode 100644
index 000000000000..e1bf2213f93b
--- /dev/null
+++ b/translations/ja-JP/data/reusables/rest-reference/issues/comments.md
@@ -0,0 +1,5 @@
+## コメント
+
+Issue コメント API は、Issue およびプルリクエストに関するリスト、表示、編集、コメントの作成に対応しています。
+
+Issue コメントは、[3 つのカスタムメディアタイプ](#custom-media-types)を使用します。 API におけるメディアタイプの使用に関する詳細は、[こちら](/rest/overview/media-types)を参照してください。
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/rest-reference/issues/events.md b/translations/ja-JP/data/reusables/rest-reference/issues/events.md
new file mode 100644
index 000000000000..69cbbf594930
--- /dev/null
+++ b/translations/ja-JP/data/reusables/rest-reference/issues/events.md
@@ -0,0 +1,3 @@
+## イベント
+
+The Issue Events API can return different types of events triggered by activity in issues and pull requests. For more information about the specific events that you can receive from the Issue Events API, see "[Issue event types](/developers/webhooks-and-events/issue-event-types)." For more information about the specific events that you can receive from the Issue Events API, see "[Issue event types](/developers/webhooks-and-events/issue-event-types)." For more information, see the "[Events API](/developers/webhooks-and-events/github-event-types)."
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/rest-reference/issues/issues.md b/translations/ja-JP/data/reusables/rest-reference/issues/issues.md
new file mode 100644
index 000000000000..43f83849e2be
--- /dev/null
+++ b/translations/ja-JP/data/reusables/rest-reference/issues/issues.md
@@ -0,0 +1,10 @@
+### Issue のカスタムメディアタイプ
+
+Issue についてサポートされているメディアタイプは次のとおりです。
+
+ application/vnd.github.VERSION.raw+json
+ application/vnd.github.VERSION.text+json
+ application/vnd.github.VERSION.html+json
+ application/vnd.github.VERSION.full+json
+
+メディアタイプの詳しい情報については、「[カスタムメディアタイプ](/rest/overview/media-types)」を参照してください。
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/rest-reference/issues/labels.md b/translations/ja-JP/data/reusables/rest-reference/issues/labels.md
new file mode 100644
index 000000000000..247a9096c058
--- /dev/null
+++ b/translations/ja-JP/data/reusables/rest-reference/issues/labels.md
@@ -0,0 +1 @@
+## ラベル
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/rest-reference/issues/milestones.md b/translations/ja-JP/data/reusables/rest-reference/issues/milestones.md
new file mode 100644
index 000000000000..1d11cbf43a11
--- /dev/null
+++ b/translations/ja-JP/data/reusables/rest-reference/issues/milestones.md
@@ -0,0 +1 @@
+## マイルストーン
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/rest-reference/issues/timeline.md b/translations/ja-JP/data/reusables/rest-reference/issues/timeline.md
new file mode 100644
index 000000000000..d19043e7f45c
--- /dev/null
+++ b/translations/ja-JP/data/reusables/rest-reference/issues/timeline.md
@@ -0,0 +1,5 @@
+## タイムライン
+
+タイムラインイベント API は、Issue およびプルリクエストでのタイムラインアクティビティによってトリガーされるイベントのタイプを返します。 For more information about the specific events that you can receive from the Issue Events API, see "[Issue event types](/developers/webhooks-and-events/issue-event-types)." For more information about the specific events that you can receive from the Issue Events API, see "[Issue event types](/developers/webhooks-and-events/issue-event-types)." 詳細は、「[GitHub イベント API](/developers/webhooks-and-events/github-event-types)」を参照してください。
+
+この API を使用すると、Issue およびプルリクエストに関する情報を表示したり、Issue コメントを通知する相手を決定したりできます。
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/rest-reference/licenses/licenses.md b/translations/ja-JP/data/reusables/rest-reference/licenses/licenses.md
new file mode 100644
index 000000000000..0e0d0216fb9a
--- /dev/null
+++ b/translations/ja-JP/data/reusables/rest-reference/licenses/licenses.md
@@ -0,0 +1,22 @@
+ライセンス API は、広く利用されているオープンソースライセンスに関するメタデータと、特定のプロジェクトのライセンスファイルに関する情報を返します。
+
+ライセンス API は[オープンソースの Ruby Gem ライセンス](https://github.com/benbalter/licensee)を使用して、プロセスのライセンスを特定しようとします。 ライセンシーは、プロジェクトの `LICENSE` ファイル (存在する場合) を既知のライセンスの短いリストと照合します。 そのためライセンス API では、プロジェクト依存関係のライセンス、あるいはプロジェクトのライセンスをドキュメント化するその他の方法、たとえばドキュメントにおけるライセンス名の参照などは考慮されません。
+
+ライセンスが一致した場合、返されるライセンスキーおよび名前は[SPDX 仕様](https://spdx.org/)に適合します。
+
+**注釈:** 以下のエンドポイントも、リポジトリのライセンス情報を返します。
+
+- [リポジトリの取得](/rest/reference/repos#get-a-repository)
+- [ユーザのリポジトリの一覧表示](/rest/reference/repos#list-repositories-for-a-user)
+- [Organization リポジトリの一覧表示](/rest/reference/repos#list-organization-repositories)
+- [フォークの一覧表示](/rest/reference/repos#list-forks)
+- [ユーザが Watch しているリポジトリの一覧表示](/rest/reference/activity#list-repositories-watched-by-a-user)
+- [Team リポジトリの一覧表示](/rest/reference/teams#list-team-repositories)
+
+{% warning %}
+
+GitHub にはいろいろなものがありますが、法律事務所ではありません。 そのため、GitHub が法律上の助言をすることはありません。 ライセンス API を使用したり、それに関して当社にメールを送信したりすることは法律上の助言に該当せず、弁護士と依頼人の関係を確立するものでもありません。 特定のライセンスで許可される範囲について疑問がある場合は、先に進む前にそれぞれの顧問弁護士にご相談ください。 むしろ、法的な結果が想定される、あるいは法律上の権利に影響しうる決定を下す場合には、必ずその前に各自の弁護士にご相談ください。
+
+GitHub は、ユーザがオープンソースライセンスと、それを利用するプロジェクトに関する情報を得るためにライセンス API を作成しました。 お役に立てれば幸いですが、当社は (少なくとも従業員のほとんどは) 弁護士ではなく、他の方と同じように誤りがないとは言えません。 For that reason, GitHub provides the API on an "as-is" basis and makes no warranties regarding any information or licenses provided on or through it, and disclaims liability for damages resulting from using the API.
+
+{% endwarning %}
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/rest-reference/metrics/community.md b/translations/ja-JP/data/reusables/rest-reference/metrics/community.md
new file mode 100644
index 000000000000..0725fc5aa3c2
--- /dev/null
+++ b/translations/ja-JP/data/reusables/rest-reference/metrics/community.md
@@ -0,0 +1 @@
+## コミュニティ
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/rest-reference/metrics/statistics.md b/translations/ja-JP/data/reusables/rest-reference/metrics/statistics.md
new file mode 100644
index 000000000000..aa3b7bf69834
--- /dev/null
+++ b/translations/ja-JP/data/reusables/rest-reference/metrics/statistics.md
@@ -0,0 +1,17 @@
+## 統計
+
+Repository Statistics API を使用すると、{% data variables.product.product_name %} がさまざまなタイプのリポジトリのアクティビティを視覚化するために用いるデータをフェッチできます。
+
+### キャッシングについて
+
+リポジトリの統計情報を計算するのは負荷が高い操作なので、可能な限りキャッシュされたデータを返すようにしています。 リポジトリの統計をクエリした際にデータがキャッシュされていなかった場合は、`202` レスポンスを受け取ります。また、この統計をまとめるため、バックグラウンドでジョブが開始します。 このジョブが完了するまで少し待ってから、リクエストを再度サブミットしてください。 ジョブが完了していた場合、リクエストは `200` レスポンスを受けとり、レスポンスの本文には統計情報が含まれています。
+
+リポジトリの統計情報は、リポジトリのデフォルトブランチに SHA でキャッシュされ、デフォルトのブランチにプッシュすると統計情報のキャッシュがリセットされます。
+
+### 統計で除外されるコミットのタイプ
+
+API によって公開される統計は、[別のリポジトリグラフ](/github/visualizing-repository-data-with-graphs/about-repository-graphs)で表示される統計と同じものです。
+
+要約すると、
+- すべての統計は、マージコミットが除外されます。
+- コントリビューター統計では、空のコミットも除外されます。
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/rest-reference/metrics/traffic.md b/translations/ja-JP/data/reusables/rest-reference/metrics/traffic.md
new file mode 100644
index 000000000000..76935031f73c
--- /dev/null
+++ b/translations/ja-JP/data/reusables/rest-reference/metrics/traffic.md
@@ -0,0 +1,3 @@
+## トラフィック
+
+プッシュアクセスを持つリポジトリに対し、トラフィック API はリポジトリグラフが提供する情報へのアクセスを提供します。 詳細は「リポジトリへのトラフィックを表示する」を参照してください。
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/rest-reference/migrations/orgs.md b/translations/ja-JP/data/reusables/rest-reference/migrations/orgs.md
new file mode 100644
index 000000000000..7f82d9ee3f28
--- /dev/null
+++ b/translations/ja-JP/data/reusables/rest-reference/migrations/orgs.md
@@ -0,0 +1,5 @@
+## Organization
+
+移行 API を使用できるのは、認証済みの Organization オーナーのみです。 For more information, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#permission-levels-for-an-organization)" and "[Other authentication methods](/rest/overview/other-authentication-methods)."
+
+{% data variables.migrations.organization_migrations_intro %}
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/rest-reference/migrations/source-imports.md b/translations/ja-JP/data/reusables/rest-reference/migrations/source-imports.md
new file mode 100644
index 000000000000..e9e460c309f0
--- /dev/null
+++ b/translations/ja-JP/data/reusables/rest-reference/migrations/source-imports.md
@@ -0,0 +1,80 @@
+## ソースのインポート
+
+{% data variables.migrations.source_imports_intro %}
+
+一般的なソースのインポートでは、まずインポートを開始し、次に (オプションで) 作者を更新したり、インポートに大きいファイルが存在する場合に Git LFS 使用の設定を更新したりします。 [`RepositoryImportEvent`](/developers/webhooks-and-events/webhook-events-and-payloads#repository_import) をリスニングする webhook を作成して、インポートのステータスを確認することもできます。
+
+詳細な例は、次の図を参照してください。
+
+```
++---------+ +--------+ +---------------------+
+| Tooling | | GitHub | | Original Repository |
++---------+ +--------+ +---------------------+
+ | | |
+ | Start import | |
+ |----------------------------->| |
+ | | |
+ | | Download source data |
+ | |--------------------------------------------->|
+ | | Begin streaming data |
+ | |<---------------------------------------------|
+ | | |
+ | Get import progress | |
+ |----------------------------->| |
+ | "status": "importing" | |
+ |<-----------------------------| |
+ | | |
+ | Get commit authors | |
+ |----------------------------->| |
+ | | |
+ | Map a commit author | |
+ |----------------------------->| |
+ | | |
+ | | |
+ | | Finish streaming data |
+ | |<---------------------------------------------|
+ | | |
+ | | Rewrite commits with mapped authors |
+ | |------+ |
+ | | | |
+ | |<-----+ |
+ | | |
+ | | Update repository on GitHub |
+ | |------+ |
+ | | | |
+ | |<-----+ |
+ | | |
+ | Map a commit author | |
+ |----------------------------->| |
+ | | Rewrite commits with mapped authors |
+ | |------+ |
+ | | | |
+ | |<-----+ |
+ | | |
+ | | Update repository on GitHub |
+ | |------+ |
+ | | | |
+ | |<-----+ |
+ | | |
+ | Get large files | |
+ |----------------------------->| |
+ | | |
+ | opt_in to Git LFS | |
+ |----------------------------->| |
+ | | Rewrite commits for large files |
+ | |------+ |
+ | | | |
+ | |<-----+ |
+ | | |
+ | | Update repository on GitHub |
+ | |------+ |
+ | | | |
+ | |<-----+ |
+ | | |
+ | Get import progress | |
+ |----------------------------->| |
+ | "status": "complete" | |
+ |<-----------------------------| |
+ | | |
+ | | |
+```
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/rest-reference/migrations/users.md b/translations/ja-JP/data/reusables/rest-reference/migrations/users.md
new file mode 100644
index 000000000000..c33658d10b52
--- /dev/null
+++ b/translations/ja-JP/data/reusables/rest-reference/migrations/users.md
@@ -0,0 +1,9 @@
+## ユーザ
+
+ユーザ移行 API を使用できるのは、認証済みのアカウントオーナーのみです。 詳細は、「[その他の認証方式](/rest/overview/other-authentication-methods)」を参照してください。
+
+{% data variables.migrations.user_migrations_intro %}ダウンロードできる移行データのリストは、「[ユーザー移行アーカイブをダウンロードする](#download-a-user-migration-archive)」を参照してください。
+
+アーカイブをダウンロードするには、先にユーザ移行を開始する必要があります。 移行のステータスが `exported` になると、移行をダウンロードできます。
+
+移行アーカイブを作成すると、7 日間ダウンロードできるようになります。 ただし、必要があればユーザ移行アーカイブはそれより以前に削除できます。 移行が `exported` になってからリポジトリのロックを解除すると、リポジトリの使用を再開でき、ソースデータが不要な場合にはリポジトリを削除することもできます。
diff --git a/translations/ja-JP/data/reusables/rest-reference/oauth-authorizations/oauth-authorizations.md b/translations/ja-JP/data/reusables/rest-reference/oauth-authorizations/oauth-authorizations.md
new file mode 100644
index 000000000000..b0b3bb095a49
--- /dev/null
+++ b/translations/ja-JP/data/reusables/rest-reference/oauth-authorizations/oauth-authorizations.md
@@ -0,0 +1,3 @@
+この API を使用すると、OAuth アプリケーションから自分のアカウントへのアクセスを管理することができます。 この API にアクセスするには、ユーザ名とパスワードを使用する [Basic 認証](/rest/overview/other-authentication-methods#basic-authentication) が必要であり、トークンは使用できません。
+
+自分または自分のユーザが 2 要素認証を有効にしている場合は、必ず [2 要素認証の使用方法](/rest/overview/other-authentication-methods#working-with-two-factor-authentication)を理解していることを確認してください。
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/rest-reference/orgs/blocking.md b/translations/ja-JP/data/reusables/rest-reference/orgs/blocking.md
new file mode 100644
index 000000000000..e75fef7582c0
--- /dev/null
+++ b/translations/ja-JP/data/reusables/rest-reference/orgs/blocking.md
@@ -0,0 +1,3 @@
+## ユーザのブロック
+
+Organization に対するブロック呼び出しを実行するには、呼び出しの認証に使用するトークンに `admin:org` が必要です。 それがない場合には、`HTTP 404` が返されます。
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/rest-reference/orgs/custom_roles.md b/translations/ja-JP/data/reusables/rest-reference/orgs/custom_roles.md
new file mode 100644
index 000000000000..ccd036183c3c
--- /dev/null
+++ b/translations/ja-JP/data/reusables/rest-reference/orgs/custom_roles.md
@@ -0,0 +1 @@
+## カスタムリポジトリロール
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/rest-reference/orgs/members.md b/translations/ja-JP/data/reusables/rest-reference/orgs/members.md
new file mode 100644
index 000000000000..5076861f3e58
--- /dev/null
+++ b/translations/ja-JP/data/reusables/rest-reference/orgs/members.md
@@ -0,0 +1 @@
+## メンバー
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/rest-reference/orgs/outside-collaborators.md b/translations/ja-JP/data/reusables/rest-reference/orgs/outside-collaborators.md
new file mode 100644
index 000000000000..a61d6c8cc643
--- /dev/null
+++ b/translations/ja-JP/data/reusables/rest-reference/orgs/outside-collaborators.md
@@ -0,0 +1 @@
+## 外部コラボレーター
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/rest-reference/orgs/webhooks.md b/translations/ja-JP/data/reusables/rest-reference/orgs/webhooks.md
new file mode 100644
index 000000000000..398f29fd7b5a
--- /dev/null
+++ b/translations/ja-JP/data/reusables/rest-reference/orgs/webhooks.md
@@ -0,0 +1,24 @@
+## webhook
+
+Organization webhooks allow you to receive HTTP `POST` payloads whenever certain events happen in an organization. {% data reusables.webhooks.webhooks-rest-api-links %}
+
+サブスクライブできるアクションの詳細は、「[{% data variables.product.prodname_dotcom %} のイベントタイプ](/developers/webhooks-and-events/github-event-types)」を参照してください。
+
+### スコープと制限事項
+
+Organization の webhook に対するすべてのアクションでは、認証ユーザが管理対象の Organization の管理者である必要があります。 また、OAuth トークンには `admin:org_hook` スコープが必要です。 詳しい情報については、「[OAuth App のスコープ](/developers/apps/scopes-for-oauth-apps)」を参照してください。
+
+webhook 設定に存在する可能性がある機密データを保護するために、次のアクセス制御ルールも適用します。
+
+- OAuth アプリケーションが、それによって作成されたのではない webhook をリスト、表示、編集することはできません。
+- OAuth アプリケーションによって作成された webhook をユーザがリスト、表示、編集することはできません。
+
+### webhook の受信
+
+{% data variables.product.product_name %} で webhook ペイロードを送信するには、インターネットからサーバーにアクセスできる必要があります。 暗号化されたペイロードを HTTPS 経由で送信できるように、SSL の使用も強く推奨します。
+
+その他のベストプラクティスについては、[ガイド](/guides/best-practices-for-integrators/)を参照してください。
+
+#### webhook ヘッダー
+
+{% data variables.product.product_name %} は、イベントタイプとペイロード識別子を区別するために、複数の HTTP ヘッダーも送信します。 詳細は「[webhook ヘッダー](/webhooks/event-payloads/#delivery-headers)」を参照してください。
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/rest-reference/packages/packages.md b/translations/ja-JP/data/reusables/rest-reference/packages/packages.md
new file mode 100644
index 000000000000..756d5de02e56
--- /dev/null
+++ b/translations/ja-JP/data/reusables/rest-reference/packages/packages.md
@@ -0,0 +1,10 @@
+{% data variables.product.prodname_registry %} APIでは、REST APIを使ってパッケージを管理できます。 パッケージのリストアや削除についてさらに学ぶには、「[パッケージのリストアと削除](/packages/learn-github-packages/deleting-and-restoring-a-package)」を参照してください。
+
+このAPIを使うには、個人アクセストークンを使って認証を受けなければなりません。
+ - パッケージメタデータにアクセスするには、トークンに`read:packages`スコープが含まれていなければなりません。
+ - パッケージやパッケージのバージョンを削除するには、トークンに`read:packages`及び`delete:packages`スコープが含まれていなければなりません。
+ - パッケージやパッケージのバージョンをリストアするには、トークンに`read:packages`及び`write:packages`スコープが含まれていなければなりません。
+
+`package_type`が`npm`、`maven`、`rubygems`、`nuget`のいずれかなら、パッケージは{% data variables.product.prodname_dotcom %}リポジトリからの権限を継承するので、トークンには`repo`スコープも含まれていなければなりません。 パッケージが{% data variables.product.prodname_container_registry %}内にあるなら、`package_type`は`container`であり、この`package_type`のアクセスあるいは管理のためにトークンに`repo`スコープが含まれている必要はありません。 `container`パッケージは、リポジトリは別に詳細な権限を提供します。 詳しい情報については「[{% data variables.product.prodname_registry %}の権限について](/packages/learn-github-packages/about-permissions-for-github-packages#about-scopes-and-permissions-for-package-registries)」を参照してください。
+
+SSOが有効化されたOrganization内のリソースにアクセスするために{% data variables.product.prodname_registry %} APIを使いたい場合は、個人アクセストークンにSSOを有効化しなければなりません。 For more information, see "[Authorizing a personal access token for use with SAML single sign-on](/github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/rest-reference/pages/pages.md b/translations/ja-JP/data/reusables/rest-reference/pages/pages.md
new file mode 100644
index 000000000000..adbea2f01a99
--- /dev/null
+++ b/translations/ja-JP/data/reusables/rest-reference/pages/pages.md
@@ -0,0 +1,14 @@
+{% data variables.product.prodname_pages %} API は、{% data variables.product.prodname_pages %} の設定や、ビルドのステータスについての情報を取得します。 サイトとビルドに関する情報は、{% ifversion not ghae %}Webサイトがパブリックの場合であっても{% endif %}認証を受けたユーザだけがアクセスできます。 詳しい情報については、「[{% data variables.product.prodname_pages %} について](/pages/getting-started-with-github-pages/about-github-pages)」を参照してください。
+
+レスポンスに `status` キーを持つ {% data variables.product.prodname_pages %} API エンドポイントにおいては、値は以下のいずれかになります。
+* `null`: サイトはまだビルドされていません。
+* `queued`: ビルドがリクエストされたが、まだ開始していません。
+* `building`: ビルドが進行中です。
+* `built`: サイトがビルドされています。
+* `errored`: ビルド中にエラーが発生したことを示します。
+
+GitHub Pages サイトの情報を返す {% data variables.product.prodname_pages %} API エンドポイントにおいては、JSON のレスポンスには以下が含まれます。
+* `html_url`: レンダリングされた Pages サイトの絶対 URL (スキームを含む) 。 たとえば、`https://username.github.io` などです。
+* `source`: レンダリングされた Pages サイトのソースブランチおよびディレクトリを含むオブジェクト。 これは以下のものが含まれます。
+ - `branch`: [サイトのソースファイル](/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site)を公開するために使用するリポジトリのブランチ。 たとえば、_main_ or _gh-pages_ などです。
+ - `path`: サイトの公開元のリポジトリディレクトリ。 `/` または `/docs` のどちらかとなります。
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/rest-reference/projects/cards.md b/translations/ja-JP/data/reusables/rest-reference/projects/cards.md
new file mode 100644
index 000000000000..16db48640e82
--- /dev/null
+++ b/translations/ja-JP/data/reusables/rest-reference/projects/cards.md
@@ -0,0 +1 @@
+## カード
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/rest-reference/projects/collaborators.md b/translations/ja-JP/data/reusables/rest-reference/projects/collaborators.md
new file mode 100644
index 000000000000..bf64b17c0b3c
--- /dev/null
+++ b/translations/ja-JP/data/reusables/rest-reference/projects/collaborators.md
@@ -0,0 +1,3 @@
+## コラボレータ
+
+このAPIを使用すると、Organizationのプロジェクトと対話できます。
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/rest-reference/projects/columns.md b/translations/ja-JP/data/reusables/rest-reference/projects/columns.md
new file mode 100644
index 000000000000..8091a483fd9f
--- /dev/null
+++ b/translations/ja-JP/data/reusables/rest-reference/projects/columns.md
@@ -0,0 +1 @@
+## カラム
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/rest-reference/pulls/comments.md b/translations/ja-JP/data/reusables/rest-reference/pulls/comments.md
new file mode 100644
index 000000000000..6647c8872b63
--- /dev/null
+++ b/translations/ja-JP/data/reusables/rest-reference/pulls/comments.md
@@ -0,0 +1,14 @@
+## レビューコメント
+
+Pull Requestレビューコメントは、Pull Requestのレビュー中に unified 形式の diff の一部に付けられたコメントです。 コミットコメントおよび Issue コメントは、Pull Requestレビューコメントとは異なります。 コミットコメントはコミットに直接付けるもので、Issue コメントは、unified 形式の diff の一部を参照することなく付けるものです。 詳しい情報については、「[コミットコメントの作成](/rest/reference/commits#create-a-commit-comment)」および「[Issue コメントの作成](/rest/reference/issues#create-an-issue-comment)」を参照してください。
+
+### Pull Requestレビューコメントのカスタムメディアタイプ
+
+以下がPull Requestレビューコメントでサポートされているメディアタイプです。
+
+ application/vnd.github.VERSION.raw+json
+ application/vnd.github.VERSION.text+json
+ application/vnd.github.VERSION.html+json
+ application/vnd.github.VERSION.full+json
+
+詳しい情報については、「[カスタムメディアタイプ](/rest/overview/media-types)」を参照してください。
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/rest-reference/pulls/pulls.md b/translations/ja-JP/data/reusables/rest-reference/pulls/pulls.md
new file mode 100644
index 000000000000..356da53032cf
--- /dev/null
+++ b/translations/ja-JP/data/reusables/rest-reference/pulls/pulls.md
@@ -0,0 +1,33 @@
+Pull Request API を使用すると、Pull Requestを一覧表示、編集、作成、マージできます。 Pull Requestのコメントは、[Issue Comments API](/rest/reference/issues#comments) で管理できます。
+
+すべてのPull Requestは Issue ですが、すべての Issue がPull Requestというわけではありません。 このため、アサインされた人、ラベル、マイルストーンなどの操作といった、両方の機能で共通するアクションは、[Issues API](/rest/reference/issues) で提供されます。
+
+### Pull Requestのカスタムメディアタイプ
+
+以下がPull Requestでサポートされているメディアタイプです。
+
+ application/vnd.github.VERSION.raw+json
+ application/vnd.github.VERSION.text+json
+ application/vnd.github.VERSION.html+json
+ application/vnd.github.VERSION.full+json
+ application/vnd.github.VERSION.diff
+ application/vnd.github.VERSION.patch
+
+詳しい情報については、「[カスタムメディアタイプ](/rest/overview/media-types)」を参照してください。
+
+diff が破損している場合は、{% data variables.contact.contact_support %} にお問い合わせください。 メッセージにはリポジトリ名とPull Request ID を記載してください。
+
+### リンク関係
+
+Pull Requestには以下のリンク関係が含まれる可能性があります。
+
+| 名前 | 説明 |
+| ----------------- | ----------------------------------------------------------------------------------------------------------------- |
+| `self` | Pull Requestの API ロケーション。 |
+| `html` | Pull Requestの HTML ロケーション。 |
+| `Issue` | Pull Requestの [Issue](/rest/reference/issues) の API ロケーション。 |
+| `コメント` | Pull Requestの [Issue コメント](/rest/reference/issues#comments) の API ロケーション。 |
+| `review_comments` | Pull Requestの [レビューコメント](/rest/reference/pulls#comments) の API ロケーション。 |
+| `review_comment` | Pull Requestのリポジトリで、[レビューコメント](/rest/reference/pulls#comments)の API ロケーションを構築するための[URL テンプレート](/rest#hypermedia)。 |
+| `commits` | Pull Requestの [コミット](#list-commits-on-a-pull-request) の API ロケーション。 |
+| `statuses` | Pull Requestの[コミットステータス](/rest/reference/commits#commit-statuses)、すなわち`head` ブランチのステータスの API ロケーション。 |
diff --git a/translations/ja-JP/data/reusables/rest-reference/pulls/review-requests.md b/translations/ja-JP/data/reusables/rest-reference/pulls/review-requests.md
new file mode 100644
index 000000000000..19f518835b94
--- /dev/null
+++ b/translations/ja-JP/data/reusables/rest-reference/pulls/review-requests.md
@@ -0,0 +1,3 @@
+## レビューリクエスト
+
+Pull Requestの作者、リポジトリのオーナー、およびコラボレータは、リポジトリの書き込みアクセスを持つ人にPull Requestレビューをリクエストできます。 リクエストされたレビュー担当者は、Pull Requestレビューをするようあなたが依頼したという通知を受け取ります。
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/rest-reference/pulls/reviews.md b/translations/ja-JP/data/reusables/rest-reference/pulls/reviews.md
new file mode 100644
index 000000000000..e6940e714fd0
--- /dev/null
+++ b/translations/ja-JP/data/reusables/rest-reference/pulls/reviews.md
@@ -0,0 +1,3 @@
+## レビュー
+
+Pull Requestレビューは、Pull Request上のPull Requestレビューコメントのグループで、状態とオプションの本文コメントでグループ化されています。
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/rest-reference/rate-limit/rate-limit.md b/translations/ja-JP/data/reusables/rest-reference/rate-limit/rate-limit.md
new file mode 100644
index 000000000000..8e26dc7b2630
--- /dev/null
+++ b/translations/ja-JP/data/reusables/rest-reference/rate-limit/rate-limit.md
@@ -0,0 +1,17 @@
+REST API 概要ドキュメンテーションでは、[レート制限のルール](/rest/overview/resources-in-the-rest-api#rate-limiting)について説明しています。 以下で説明する Rate Limit API を使用して、現在のレート制限ステータスをいつでも確認できます。
+
+### レート制限のステータスを理解する
+
+Search APIは[カスタムのレート制限](/rest/reference/search#rate-limit)を持ち、他のREST APIを管理するレート制限とは分離されています。 GraphQL APIも[カスタムのレート制限]({% ifversion ghec%}/free-pro-team@latest{% endif %}/graphql/overview/resource-limitations#rate-limit)を持ち、REST APIのレート制限とは分離されて別に計算されます。
+
+そのため、Rate Limit APIのレスポンスは、レート制限を分類します。 `resources` の下には、4 つのオブジェクトがあります。
+
+* `core`オブジェクトは、REST API中の検索に関連しないすべてのリソースに関するレート制限のステータスを提供します。
+
+* `search`オブジェクトは、[Search API](/rest/reference/search)に対するレート制限のステータスを提供します。
+
+* `graphql`オブジェクトは、[GraphQL API]({% ifversion ghec%}/free-pro-team@latest{% endif %}/graphql)に対するレート制限のステータスを提供します。
+
+* `integration_manifest`オブジェクトは、[GitHub App Manifest コード変換](/apps/building-github-apps/creating-github-apps-from-a-manifest/#3-you-exchange-the-temporary-code-to-retrieve-the-app-configuration)エンドポイントに対するレート制限のステータスを提供します。
+
+For more information on the headers and values in the rate limit response, see "[Resources in the REST API](/rest/overview/resources-in-the-rest-api#rate-limit-http-headers)."
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/rest-reference/reations/reactions.md b/translations/ja-JP/data/reusables/rest-reference/reations/reactions.md
new file mode 100644
index 000000000000..d2feff37dd76
--- /dev/null
+++ b/translations/ja-JP/data/reusables/rest-reference/reations/reactions.md
@@ -0,0 +1,5 @@
+### Reaction types
+
+When creating a reaction, the allowed values for the `content` parameter are as follows (with the corresponding emoji for reference):
+
+{% data reusables.repositories.reaction_list %}
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/rest-reference/releases/assets.md b/translations/ja-JP/data/reusables/rest-reference/releases/assets.md
new file mode 100644
index 000000000000..902620cfeba1
--- /dev/null
+++ b/translations/ja-JP/data/reusables/rest-reference/releases/assets.md
@@ -0,0 +1 @@
+## Release assets
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/rest-reference/releases/releases.md b/translations/ja-JP/data/reusables/rest-reference/releases/releases.md
new file mode 100644
index 000000000000..1ecd10fe4a44
--- /dev/null
+++ b/translations/ja-JP/data/reusables/rest-reference/releases/releases.md
@@ -0,0 +1,5 @@
+{% note %}
+
+**注釈:** Releases API は Downloads API を置き換えるものです。 リリースを返し、アセットをリリースする、この API のエンドポイントからダウンロード数と ブラウザのダウンロード URL を取得できます。
+
+{% endnote %}
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/rest-reference/repos/autolinks.md b/translations/ja-JP/data/reusables/rest-reference/repos/autolinks.md
new file mode 100644
index 000000000000..6be762c89574
--- /dev/null
+++ b/translations/ja-JP/data/reusables/rest-reference/repos/autolinks.md
@@ -0,0 +1,5 @@
+## Autolinks
+
+To help streamline your workflow, you can use the API to add autolinks to external resources like JIRA issues and Zendesk tickets. 詳しい情報については「[外部リソースを参照する自動リンクの設定](/github/administering-a-repository/configuring-autolinks-to-reference-external-resources)」を参照してください。
+
+{% data variables.product.prodname_github_apps %} require repository administration permissions with read or write access to use the Autolinks API.
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/rest-reference/repos/contents.md b/translations/ja-JP/data/reusables/rest-reference/repos/contents.md
new file mode 100644
index 000000000000..f4966727fb42
--- /dev/null
+++ b/translations/ja-JP/data/reusables/rest-reference/repos/contents.md
@@ -0,0 +1,22 @@
+## コンテンツ
+
+これらの API エンドポイントを使用すると、リポジトリ内の Base64 でエンコードされたコンテンツを作成、変更、削除できます。 Raw 形式またはレンダリングされた HTML (サポートされている場合) をリクエストするには、リポジトリのコンテンツにカスタムメディアタイプを使用します。
+
+### リポジトリコンテンツのカスタムメディアタイプ
+
+[README](/rest/reference/repos#get-a-repository-readme)、[ファイル](/rest/reference/repos#get-repository-content)、[シンボリックリンク](/rest/reference/repos#get-repository-content)は以下のカスタムメディアタイプをサポートしています。
+
+ application/vnd.github.VERSION.raw
+ application/vnd.github.VERSION.html
+
+ファイルのコンテンツを取得するには、`.raw` メディアタイプを使ってください。
+
+Markdown や AsciiDoc などのマークアップファイルでは、`.html` メディアタイプを使用して、レンダリングされた HTML を取得できます。 マークアップ言語は、オープンソースの[マークアップライブラリ](https://github.com/github/markup)を使用して HTML にレンダリングされます。
+
+[すべてのオブジェクト](/rest/reference/repos#get-repository-content)は、以下のカスタムメディアタイプをサポートしています。
+
+ application/vnd.github.VERSION.object
+
+コンテンツのタイプに関係なく、一貫したオブジェクトフォーマットを取得するには、`object` メディアタイプパラメータを使用します。 たとえば、レスポンスはディレクトリに対するオブジェクトの配列ではなく、オブジェクトの配列を含む `entries` 属性のオブジェクトになります。
+
+API でのメディアタイプの使用について詳しくは、[こちら](/rest/overview/media-types)をご覧ください。
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/rest-reference/repos/forks.md b/translations/ja-JP/data/reusables/rest-reference/repos/forks.md
new file mode 100644
index 000000000000..888d8715379b
--- /dev/null
+++ b/translations/ja-JP/data/reusables/rest-reference/repos/forks.md
@@ -0,0 +1 @@
+## フォーク
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/rest-reference/repos/lfs.md b/translations/ja-JP/data/reusables/rest-reference/repos/lfs.md
new file mode 100644
index 000000000000..5a48e59434d8
--- /dev/null
+++ b/translations/ja-JP/data/reusables/rest-reference/repos/lfs.md
@@ -0,0 +1,2 @@
+
+## Git LFS
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/rest-reference/scim/scim.md b/translations/ja-JP/data/reusables/rest-reference/scim/scim.md
new file mode 100644
index 000000000000..e28891142ac4
--- /dev/null
+++ b/translations/ja-JP/data/reusables/rest-reference/scim/scim.md
@@ -0,0 +1,41 @@
+### Organization 向け SCIM プロビジョニング
+
+SCIM API は SCIM を有効にしたアイデンティティプロバイダ (IdPs) で、{% data variables.product.product_name %} Organization メンバーシップのプロビジョニングを自動化するために用いられます。 The {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API is based on version 2.0 of the [SCIM standard](http://www.simplecloud.info/). IdP が使用するべき {% data variables.product.product_name %} SCIM エンドポイントは、`{% data variables.product.api_url_code %}/scim/v2/organizations/{org}/` です。
+
+{% note %}
+
+**ノート:**
+ - The SCIM API is available only to organizations on [{% data variables.product.prodname_ghe_cloud %}](/billing/managing-billing-for-your-github-account/about-billing-for-github-accounts) with [SAML SSO](/rest/overview/other-authentication-methods#authenticating-for-saml-sso) enabled. {% data reusables.scim.enterprise-account-scim %} SCIMに関する詳しい情報については、「[SCIM について](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim) 」を参照してください。
+ - The SCIM API cannot be used with {% data variables.product.prodname_emus %}.
+
+{% endnote %}
+
+### SCIM API への呼び出しを認証する
+
+SCIM API を使用するには、{% data variables.product.product_name %} Organization の所有者として認証する必要があります。 API は、[OAuth 2.0 Bearer](/developers/apps/authenticating-with-github-apps) トークンが `Authorization` ヘッダに含まれていることを想定しています。 個人アクセストークンを使用することもできますが、まず [SAML SSO Organizationで使用するためにトークンを承認する](/github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)必要があります。
+
+### SAML および SCIM データのマッピング
+
+{% data reusables.scim.nameid-and-username-must-match %}
+
+### サポートされている SCIM ユーザ属性
+
+| 名前 | 種類 | 説明 |
+| ----------------- | --------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `userName` | `string` | ユーザのユーザ名。 |
+| `name.givenName` | `string` | ユーザーの名。 |
+| `name.familyName` | `string` | ユーザーの姓。 |
+| `emails` | `array` | ユーザのメール一覧。 |
+| `externalId` | `string` | この識別子は SAML プロバイダによって生成され、GitHub ユーザと照合するためにSAML プロバイダによって一意の ID として使用されます。 ユーザの `externalID` は、SAML プロバイダ、または [SCIM プロビジョニング済み ID の一覧表示](#list-scim-provisioned-identities)エンドポイントを使用して、ユーザの GitHub ユーザ名やメールアドレスなどの他の既知の属性でフィルタして見つけることができます。 |
+| `id` | `string` | GitHub SCIM エンドポイントによって生成された識別子。 |
+| `active` | `boolean` | ID がアクティブである（true）か、プロビジョニングを解除する必要がある（false）かを示すために使用する。 |
+
+{% note %}
+
+**注釈:** SCIM API のエンドポイント URL では、大文字と小文字が区別されます。 たとえば、`Users` エンドポイントの最初の文字は大文字にする必要があります。
+
+```shell
+GET /scim/v2/organizations/{org}/Users/{scim_user_id}
+```
+
+{% endnote %}
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/rest-reference/search/search.md b/translations/ja-JP/data/reusables/rest-reference/search/search.md
new file mode 100644
index 000000000000..a50324d07f0b
--- /dev/null
+++ b/translations/ja-JP/data/reusables/rest-reference/search/search.md
@@ -0,0 +1,144 @@
+Search API は、見つけたい特定の項目を検索するために役立ちます。 たとえば、リポジトリ内のユーザや特定のファイルを見つけることができます。 Google で検索を実行するのと同じように考えてください。 Search API は、探している 1 つの結果 (または探しているいくつかの結果) を見つけるために役立つよう設計されています。 Google で検索する場合と同じように、ニーズに最も合う項目を見つけるため、検索結果を数ページ表示したい場合もあるでしょう。 こうしたニーズを満たすため、{% data variables.product.product_name %} Search API では**各検索につき 最大 1,000 件の結果**を提供します。
+
+クエリを使って、検索を絞り込めます。 検索クエリ構文の詳細については、「[検索クエリの構築](/rest/reference/search#constructing-a-search-query)」を参照してください。
+
+### 検索結果を順番づける
+
+クエリパラメータとして別のソートオプションが指定されない限り、結果は最も一致するものから降順にソートされます。 最も関連性の高い項目を検索結果の最上位に押し上げるように、複数の要素が組み合わされます。
+
+### レート制限
+
+{% data reusables.enterprise.rate_limit %}
+
+Search API にはカスタムレート制限があります。 リクエストに[基本認証](/rest#authentication)、[OAuth](/rest#authentication)、または[クライアント ID とシークレット](/rest#increasing-the-unauthenticated-rate-limit-for-oauth-applications)を使用する場合は、1 分間に最大 30 件のリクエストが行えます。 認証されていないリクエストでは、レート制限により 1 分間あたり最大 10 件のリクエストが行えます。
+
+現在のレート制限状態を確認する方法の詳細については、[レート制限ドキュメンテーション](/rest/reference/rate-limit)を参照してください。
+
+### 検索クエリの構築
+
+Search API の各エンドポイントでは、{% data variables.product.product_name %} で検索を行うために[クエリパラメータ](https://en.wikipedia.org/wiki/Query_string)を使用します。 エンドポイントとクエリパラメータを含める例については、Search API の個々のエンドポイントを参照してください。
+
+クエリには、{% data variables.product.product_name %} でサポートされている検索修飾子を任意に組み合わせて使用できます。 検索クエリの形式は次のとおりです。
+
+```
+SEARCH_KEYWORD_1 SEARCH_KEYWORD_N QUALIFIER_1 QUALIFIER_N
+```
+
+たとえば、README ファイルに `GitHub` と `Octocat` という言葉が含まれている、`defunkt` が所有する_リポジトリ_をすべて検索する場合、_検索リポジトリ_エンドポイントに次のクエリを使用します。
+
+```
+GitHub Octocat in:readme user:defunkt
+```
+
+**ノート:** クエリ文字列の構築には、使用する言語の優先 HTML エンコーダを必ず使用してしてください。 例:
+```javascript
+// JavaScript
+const queryString = 'q=' + encodeURIComponent('GitHub Octocat in:readme user:defunkt');
+```
+
+使用可能な修飾子の完全な一覧、フォーマット、使用例については、「[GitHub での検索](/search-github/searching-on-github)」を参照してください。 特定の数量、日付に一致させたり、検索結果から除外したりするために演算子を使う方法の詳細については、「[検索構文を理解する](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax/)」を参照してください。
+
+### クエリの長さの制限
+
+Search API は、以下のクエリをサポートしていません。
+- 256 文字超 (演算子や修飾子は除く)。
+- `AND`、`OR`、`NOT` の演算子が 6 つ以上ある。
+
+こうした検索クエリを使用すると、「Validation failed」というエラーメッセージが返されます。
+
+### タイムアウトと不完全な結果
+
+皆さんが Search API を迅速に使用できるよう、個別のクエリを実行する時間について制限を設けています。 [時間制限を超えた](https://developer.github.com/changes/2014-04-07-understanding-search-results-and-potential-timeouts/)クエリに対しては、API はタイムアウト前に見つかった一致を返し、レスポンスの `incomplete_results` プロパティが `true` に設定されます。
+
+タイムアウトになったことは、必ずしも検索結果が未完了であるということではありません。 もっと多くの検索結果が出たかもしれませんし、出ていないかもしれません。
+
+### アクセスエラーまたは検索結果の欠落
+
+You need to successfully authenticate and have access to the repositories in your search queries, otherwise, you'll see a `422 Unprocessable Entry` error with a "Validation Failed" message. たとえば、{% data variables.product.prodname_dotcom %} にサインインしたときにアクセスできないリソースをリクエストする `repo:`、`user:`、または `org:` 修飾子がクエリに含まれている場合、検索は失敗します。
+
+検索クエリで複数のリソースをリクエストする場合、レスポンスにはあなたがアクセスできるリソースのみが含まれ、返されないリソースを一覧表示するようなエラーメッセージは**表示されません**。
+
+たとえば、検索クエリで `octocat/test` リポジトリと `codertocat/test` リポジトリを検索し、`octocat/test` へのアクセス権しか持っていない場合、`octocat/test` の検索結果が表示され、`codertocat/test` の検索結果は全く表示されません。 この振る舞いは、{% data variables.product.prodname_dotcom %} における検索の仕組みと同じです。
+
+### テキスト一致メタデータ
+
+GitHub では、コードスニペットが提供するコンテキストとと、検索結果のハイライトが使用できます。 Search API では、検索結果を表示するときに、検索と一致した言葉をハイライトできる付加的なメタデータを用意しています。
+
+
+
+リクエストでは、レスポンスに含まれるテキストフラグメントを受け取ることを選べます。各フラグメントには、一致した各検索用語の正確な場所を特定する数値オフセットが付属しています。
+
+検索結果でこのメタデータを取得するには、`Accept` ヘッダで `text-match` メディアタイプを指定します。
+
+```shell
+application/vnd.github.v3.text-match+json
+```
+
+`text-match` メディアタイプを指定すると、JSON ペイロード内にある `text_matches` と呼ばれる追加の鍵を受け取ります。この鍵は、テキスト内の検索用語の位置と、検索用語を含む `property` についての情報を提供します。 `text_matches` 配列内の各オブジェクトには、以下の属性が含まれています。
+
+| 名前 | 説明 |
+| ------------- | ----------------------------------------------------------------------------------------------------------------------------------- |
+| `object_url` | 検索用語のいずれかに一致する文字列プロパティを含むリソースの URL。 |
+| `object_type` | 指定された `object_url` に存在するリソースのタイプの名前。 |
+| `属性` | `object_url` に存在するリソースのプロパティの名前。 このプロパティは、検索用語のいずれかに一致する文字列です。 (`object_url` から返される JSON では、`fragment` の完全な内容を、この名前でプロパティから検索できます。) |
+| `フラグメント` | `property` の値のサブセット。 これは、1 つ以上の検索用語に一致するテキストフラグメントです。 |
+| `matches` | `fragment` に存在する 1 つ以上の検索用語の配列。 インデックス (すなわち「オフセット」) は、フラグメントと関連しています。 (`property` の_完全な_内容とは関係していません。) |
+
+#### サンプル
+
+cURL と、上記の [Issue 検索例](#search-issues-and-pull-requests) を使用すると、API リクエストは次のようになります。
+
+``` shell
+curl -H 'Accept: application/vnd.github.v3.text-match+json' \
+'{% data variables.product.api_url_pre %}/search/issues?q=windows+label:bug+language:python+state:open&sort=created&order=asc'
+```
+
+レスポンスには、検索結果ごとに `text_matches` 配列が含まれます。 以下の JSON では、`text_matches` 配列に 2 つのオブジェクトがあります。
+
+最初のテキスト一致は、Issue の `body` プロパティで発生しました 。 Issue 本文から、テキストのフラグメントが表示されています。 検索用語 (`windows`) はフラグメント内に 2 回出現し、それぞれにインデックスがあります。
+
+2 番目のテキスト一致は、Issue のコメントのうちの 1 つの `body` プロパティで発生しました。 Issue コメントの URL があります。 そしてもちろん、コメント本文から、テキストのフラグメントが表示されています。 検索用語 (`windows`) は、フラグメント内で 1 回出現しています。
+
+```json
+{
+ "text_matches": [
+ {
+ "object_url": "https://api.github.com/repositories/215335/issues/132",
+ "object_type": "Issue",
+ "property": "body",
+ "fragment": "comprehensive windows font I know of).\n\nIf we can find a commonly distributed windows font that supports them then no problem (we can use html font tags) but otherwise the '(21)' style is probably better.\n",
+ "matches": [
+ {
+ "text": "windows",
+ "indices": [
+ 14,
+ 21
+ ]
+ },
+ {
+ "text": "windows",
+ "indices": [
+ 78,
+ 85
+ ]
+ }
+ ]
+ },
+ {
+ "object_url": "https://api.github.com/repositories/215335/issues/comments/25688",
+ "object_type": "IssueComment",
+ "property": "body",
+ "fragment": " right after that are a bit broken IMHO :). I suppose we could have some hack that maxes out at whatever the font does...\n\nI'll check what the state of play is on Windows.\n",
+ "matches": [
+ {
+ "text": "Windows",
+ "indices": [
+ 163,
+ 170
+ ]
+ }
+ ]
+ }
+ ]
+}
+```
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/rest-reference/secret-scanning/secret-scanning.md b/translations/ja-JP/data/reusables/rest-reference/secret-scanning/secret-scanning.md
new file mode 100644
index 000000000000..6c8a7761209b
--- /dev/null
+++ b/translations/ja-JP/data/reusables/rest-reference/secret-scanning/secret-scanning.md
@@ -0,0 +1,9 @@
+{% data reusables.secret-scanning.api-beta %}
+
+The {% data variables.product.prodname_secret_scanning %} API lets you{% ifversion fpt or ghec or ghes > 3.1 or ghae %}:
+
+- Enable or disable {% data variables.product.prodname_secret_scanning %} for a repository. For more information, see "[Repositories](/rest/reference/repos#update-a-repository)" in the REST API documentation.
+- Retrieve and update {% data variables.product.prodname_secret_scanning %} alerts from a {% ifversion fpt or ghec %}private {% endif %}repository. For futher details, see the sections below.
+{%- else %} retrieve and update {% data variables.product.prodname_secret_scanning %} alerts from a {% ifversion fpt or ghec %}private {% endif %}repository.{% endif %}
+
+{% data variables.product.prodname_secret_scanning %} の詳細については、「[{% data variables.product.prodname_secret_scanning %} について](/code-security/secret-security/about-secret-scanning)」を参照してください。
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/rest-reference/teams/discussion-comments.md b/translations/ja-JP/data/reusables/rest-reference/teams/discussion-comments.md
new file mode 100644
index 000000000000..5d14c2443917
--- /dev/null
+++ b/translations/ja-JP/data/reusables/rest-reference/teams/discussion-comments.md
@@ -0,0 +1,3 @@
+## ディスカッションコメント
+
+Team ディスカッションコメント API を使用すると、[Team ディスカッション](/rest/reference/teams#discussions)投稿のコメントを取得、作成、編集、削除できます。 Team の [Organization](/rest/reference/orgs) に属する全メンバーが、公開のディスカッションについたコメントを作成や表示できます。 詳細については「[Teamディスカッションについて](/organizations/collaborating-with-your-team/about-team-discussions/)」を参照してください。 この API は、Team の Organization の、認証済みメンバーのみが利用できます。
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/rest-reference/teams/discussions.md b/translations/ja-JP/data/reusables/rest-reference/teams/discussions.md
new file mode 100644
index 000000000000..fb36aa864218
--- /dev/null
+++ b/translations/ja-JP/data/reusables/rest-reference/teams/discussions.md
@@ -0,0 +1,3 @@
+## Discussions
+
+Team ディスカッション API を使用すると、Team のページに投稿されたディスカッションを取得、作成、編集、削除できます。 Team のディスカッションは、リポジトリやプロジェクトに原生されない会話をするために利用できます。 Team の [Organization](/rest/reference/orgs) に属する全メンバーが、公開のディスカッション投稿を作成や表示できます。 詳細については「[Teamディスカッションについて](//organizations/collaborating-with-your-team/about-team-discussions/)」を参照してください。 ディスカッションの投稿に対するコメントの詳細については、「[Team ディスカッションのコメント API](/rest/reference/teams#discussion-comments)」を参照してください。 この API は、Team の Organization の、認証済みメンバーのみが利用できます。
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/rest-reference/teams/external-groups.md b/translations/ja-JP/data/reusables/rest-reference/teams/external-groups.md
new file mode 100644
index 000000000000..5f4172ef2657
--- /dev/null
+++ b/translations/ja-JP/data/reusables/rest-reference/teams/external-groups.md
@@ -0,0 +1,16 @@
+## External groups
+
+The external groups API allows you to view the external identity provider groups that are available to your organization and manage the connection between external groups and teams in your organization.
+
+この API を使用するには、認証されたユーザーがチームメンテナまたは Team に関連づけられた Organization のコードオーナーである必要があります。
+
+{% ifversion ghec %}
+{% note %}
+
+**ノート:**
+
+- The external groups API is only available for organizations that are part of a enterprise using {% data variables.product.prodname_emus %}. For more information, see "[About Enterprise Managed Users](/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)."
+- If your organization uses team synchronization, you can use the Team Synchronization API. For more information, see "[Team synchronization API](#team-synchronization)."
+
+{% endnote %}
+{% endif %}
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/rest-reference/teams/members.md b/translations/ja-JP/data/reusables/rest-reference/teams/members.md
new file mode 100644
index 000000000000..45ca98812e97
--- /dev/null
+++ b/translations/ja-JP/data/reusables/rest-reference/teams/members.md
@@ -0,0 +1,12 @@
+## メンバー
+
+この API は、Team の Organization の、認証済みメンバーのみが利用できます。 OAuth のアクセストークンは、 `read:org` [スコープ](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/)を必要とします。
+
+{% ifversion fpt or ghes or ghec %}
+{% note %}
+
+**ノート: ** Organizationのアイデンティティプロバイダ（Idp）でTeamに同期をセットアップしている場合、Teamのメンバーシップを変更するためのこのAPIを使おうとすると、エラーが返されます。 グループのメンバーシップを管理するためにIdpにアクセスできるなら、GitHubのTeamメンバーシップをアイデンティティプロバイダを通じて管理できます。そうすれば、Organizationで自動的にTeamメンバーの追加や削除が行われます。 詳しい情報については「アイデンティティプロバイダとGitHub間でのTeamの同期」を参照してください。
+
+{% endnote %}
+
+{% endif %}
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/rest-reference/teams/team-sync.md b/translations/ja-JP/data/reusables/rest-reference/teams/team-sync.md
new file mode 100644
index 000000000000..5ee43536207a
--- /dev/null
+++ b/translations/ja-JP/data/reusables/rest-reference/teams/team-sync.md
@@ -0,0 +1,11 @@
+## Team の同期
+
+Team Synchronization API では、{% data variables.product.product_name %} Team と外部アイデンティティプロバイダ (IdP) グループとの間の接続を管理できます。 この API を使用するには、認証されたユーザーがチームメンテナまたは Team に関連づけられた Organization のコードオーナーである必要があります。 また、認証に使用するトークンも、お使いの IdP (SSO) プロバイダーで使用するための認可を受けている必要があります。 詳しい情報についてはSAML シングルサインオンの Organization で使うために個人アクセストークンを認可するを参照してください。
+
+Team 同期を使用して、IdPを通じて GitHubTeamメンバーを管理できます。 Team Synchronization API を使用するには、チーム同期が有効である必要があります。 詳しい情報については「アイデンティティプロバイダとGitHub間でのTeamの同期」を参照してください。
+
+{% note %}
+
+**Note:** The Team Synchronization API cannot be used with {% data variables.product.prodname_emus %}. To learn more about managing an {% data variables.product.prodname_emu_org %}, see "[External groups API](/enterprise-cloud@latest/rest/reference/teams#external-groups)".
+
+{% endnote %}
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/rest-reference/teams/teams.md b/translations/ja-JP/data/reusables/rest-reference/teams/teams.md
new file mode 100644
index 000000000000..326fec141da3
--- /dev/null
+++ b/translations/ja-JP/data/reusables/rest-reference/teams/teams.md
@@ -0,0 +1 @@
+この API は、Team の [Organization](/rest/reference/orgs) の、認証済みメンバーのみが利用できます。 OAuth のアクセストークンは、 `read:org` [スコープ](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/)を必要とします。 {% data variables.product.prodname_dotcom %} は、Team の `name` からTeam の `slug` を生成します。
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/rest-reference/users/blocking.md b/translations/ja-JP/data/reusables/rest-reference/users/blocking.md
new file mode 100644
index 000000000000..f0ed587b5ffc
--- /dev/null
+++ b/translations/ja-JP/data/reusables/rest-reference/users/blocking.md
@@ -0,0 +1 @@
+## ユーザのブロック
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/rest-reference/users/emails.md b/translations/ja-JP/data/reusables/rest-reference/users/emails.md
new file mode 100644
index 000000000000..288e65fb472a
--- /dev/null
+++ b/translations/ja-JP/data/reusables/rest-reference/users/emails.md
@@ -0,0 +1,3 @@
+## Emails
+
+API を通じたメールアドレスの管理には、基本認証、またはエンドポイントに対する正しいスコープの付いた OAuth で認証する必要があります。
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/rest-reference/users/followers.md b/translations/ja-JP/data/reusables/rest-reference/users/followers.md
new file mode 100644
index 000000000000..0653c04734a0
--- /dev/null
+++ b/translations/ja-JP/data/reusables/rest-reference/users/followers.md
@@ -0,0 +1 @@
+## フォロワー
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/rest-reference/users/gpg-keys.md b/translations/ja-JP/data/reusables/rest-reference/users/gpg-keys.md
new file mode 100644
index 000000000000..90bc8acf43b3
--- /dev/null
+++ b/translations/ja-JP/data/reusables/rest-reference/users/gpg-keys.md
@@ -0,0 +1,3 @@
+## GPG keys
+
+`public_key` レスポンスフィールドで返されるデータは、GPG 形式のキーではありません。 ユーザが GPG キーをアップロードすると、そのキーは解析され、暗号化された公開鍵が抽出、保存されます。 この暗号鍵が、このページの API によって返されるものです。 この鍵は、GPG のようなプログラムで直接使用するには適していません。
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/rest-reference/users/keys.md b/translations/ja-JP/data/reusables/rest-reference/users/keys.md
new file mode 100644
index 000000000000..1cb2d2de99b1
--- /dev/null
+++ b/translations/ja-JP/data/reusables/rest-reference/users/keys.md
@@ -0,0 +1 @@
+## Git SSHキー
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/rest-reference/users/users.md b/translations/ja-JP/data/reusables/rest-reference/users/users.md
new file mode 100644
index 000000000000..d99b85d3129d
--- /dev/null
+++ b/translations/ja-JP/data/reusables/rest-reference/users/users.md
@@ -0,0 +1 @@
+ユーザ API のリソースの多くには、現在認証されているユーザについての情報を取得するためのショートカットがあります。 リクエスト URL に `{username}` パラメータが含まれていない場合、レスポンスはログインしているユーザに対して行われます (リクエストで [認証情報](/rest/overview/resources-in-the-rest-api#authentication) を渡す必要があります)。{% ifversion fpt or ghes or ghec %}ユーザが 2 要素認証を有効にしているかなど、その他の個人情報は、基本認証または `user` スコープ付きで OAuth 認証されている場合に含まれます。{% endif %}
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/rest-reference/webhooks/repo-config.md b/translations/ja-JP/data/reusables/rest-reference/webhooks/repo-config.md
new file mode 100644
index 000000000000..055bbb9fa1fe
--- /dev/null
+++ b/translations/ja-JP/data/reusables/rest-reference/webhooks/repo-config.md
@@ -0,0 +1 @@
+## Repository webhook configuration
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/rest-reference/webhooks/repo-deliveries.md b/translations/ja-JP/data/reusables/rest-reference/webhooks/repo-deliveries.md
new file mode 100644
index 000000000000..bd0366dee6a4
--- /dev/null
+++ b/translations/ja-JP/data/reusables/rest-reference/webhooks/repo-deliveries.md
@@ -0,0 +1 @@
+## Repository webhook deliveries
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/rest-reference/webhooks/repos.md b/translations/ja-JP/data/reusables/rest-reference/webhooks/repos.md
new file mode 100644
index 000000000000..de415ffed004
--- /dev/null
+++ b/translations/ja-JP/data/reusables/rest-reference/webhooks/repos.md
@@ -0,0 +1 @@
+## リポジトリ webhook
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/rest-reference/webhooks/webhooks.md b/translations/ja-JP/data/reusables/rest-reference/webhooks/webhooks.md
new file mode 100644
index 000000000000..d3c037335ec7
--- /dev/null
+++ b/translations/ja-JP/data/reusables/rest-reference/webhooks/webhooks.md
@@ -0,0 +1,58 @@
+Repository webhooks allow you to receive HTTP `POST` payloads whenever certain events happen in a repository. {% data reusables.webhooks.webhooks-rest-api-links %}
+
+Organization のすべてのリポジトリからイベントを受信するため単一の webhook を設定する場合は、[Organization Webhooks](/rest/reference/orgs#webhooks) の API ドキュメントを参照してください。
+
+In addition to the REST API, {% data variables.product.prodname_dotcom %} can also serve as a [PubSubHubbub](#pubsubhubbub) hub for repositories.
+
+## webhook の受信
+
+{% data variables.product.product_name %} で webhook ペイロードを送信するには、インターネットからサーバーにアクセスできる必要があります。 暗号化されたペイロードを HTTPS 経由で送信できるように、SSL の使用も強く推奨します。
+
+### webhook ヘッダー
+
+{% data variables.product.product_name %} は、イベントタイプとペイロード識別子を区別するために、複数の HTTP ヘッダーも送信します。 詳細は「[webhook ヘッダー](/developers/webhooks-and-events/webhook-events-and-payloads#delivery-headers)」を参照してください。
+
+## PubSubHubbub
+
+GitHub は、すべてのリポジトリに対する [PubSubHubbub](https://github.com/pubsubhubbub/PubSubHubbub) のハブとして機能することもできます。 PSHB はシンプルな公開/サブスクライブプロトコルで、トピックが更新されたときにサーバーが更新を受信できるよう登録できます。 更新は HTTP POST リクエストでコールバック URL に送信されます。 GitHub リポジトリのプッシュに対するトピック URL のフォーマットは以下の通りです。
+
+`https://github.com/{owner}/{repo}/events/{event}`
+
+イベントには、任意の使用可能な webhook イベントを指定します。 詳しい情報については、「[webhook イベントとペイロード](/developers/webhooks-and-events/webhook-events-and-payloads)」を参照してください。
+
+### レスポンスのフォーマット
+
+デフォルトのフォーマットは、[既存の post-receive フックから予想できます](/post-receive-hooks/)。すなわち、POST で `payload` パラメータとして送信される JSON の本文です。 また、`Accept` ヘッダまたは `.json` 拡張子で、Raw 形式の JSON 本文を受信するよう指定できます。
+
+ Accept: application/json
+ https://github.com/{owner}/{repo}/events/push.json
+
+### コールバック URL
+
+コールバック URL は `http://` プロトコルを使用できます。
+
+ # Send updates to postbin.org
+ http://postbin.org/123
+
+### サブスクライブ
+
+GitHub PubSubHubbub のエンドポイントは `{% data variables.product.api_url_code %}/hub` です。 curl でリクエストに成功すると、以下のように表示されます。
+
+``` shell
+curl -u "user" -i \
+ {% data variables.product.api_url_pre %}/hub \
+ -F "hub.mode=subscribe" \
+ -F "hub.topic=https://github.com/{owner}/{repo}/events/push" \
+ -F "hub.callback=http://postbin.org/123"
+```
+
+PubSubHubbub リクエストは複数回送信できます。 フックがすでに存在する場合は、リクエストに従って変更されます。
+
+#### パラメータ
+
+| 名前 | 種類 | 説明 |
+| -------------- | -------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `hub.mode` | `string` | **必須**。 `subscribe` または `unsubscribe`。 |
+| `hub.topic` | `string` | **必須**。 GitHub リポジトリがサブスクライブする URI。 パスのフォーマットは `/{owner}/{repo}/events/{event}` としてください。 |
+| `hub.callback` | `string` | トピックの更新を受信する URI。 |
+| `hub.secret` | `string` | 送信する本文コンテンツの ハッシュ署名を生成する共有秘密鍵。 GitHubからきたプッシュを、そのリクエストのボディを{% ifversion fpt or ghes > 2.22 or ghec %}`X-Hub-Signature`もしくは`X-Hub-Signature-256`ヘッダ{% elsif ghes < 3.0 %}`X-Hub-Signature`ヘッダ{% elsif ghae %}`X-Hub-Signature-256`ヘッダ{% endif %}と比較して、検証できます。 詳細は、 [PubSubHubbub のドキュメント](https://pubsubhubbub.github.io/PubSubHubbub/pubsubhubbub-core-0.4.html#authednotify)を参照してください。 |
\ No newline at end of file
diff --git a/translations/ja-JP/data/ui.yml b/translations/ja-JP/data/ui.yml
index 51bd284c8c84..e1007ea7e231 100644
--- a/translations/ja-JP/data/ui.yml
+++ b/translations/ja-JP/data/ui.yml
@@ -1,4 +1,6 @@
---
+meta:
+ default_description: Get started, troubleshoot, and make the most of GitHub. Documentation for new users, developers, administrators, and all of GitHub's products.
header:
github_docs: GitHub Docs
contact: お問い合わせ
@@ -92,6 +94,7 @@ products:
deprecation_notice: 非推奨通知
rest:
reference:
+ notes: 注釈
parameters: パラメータ
response: レスポンス
code_sample: コードサンプル
@@ -101,6 +104,7 @@ products:
see_preview_notice: プレビューの通知を見る
see_preview_notices: プレビューの通知を見る
preview_header_is_required: このヘッダは必須です
+ works_with_github_apps: Works with GitHub Apps
footer:
all_rights_reserved: All rights reserved
terms: 規約
diff --git a/translations/log/cn-resets.csv b/translations/log/cn-resets.csv
index cc3a2a8bf0e2..98bc6a43cf80 100644
--- a/translations/log/cn-resets.csv
+++ b/translations/log/cn-resets.csv
@@ -39,6 +39,7 @@ translations/zh-CN/content/admin/github-actions/enabling-github-actions-for-gith
translations/zh-CN/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-azure-blob-storage.md,broken liquid tags
translations/zh-CN/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-minio-gateway-for-nas-storage.md,broken liquid tags
translations/zh-CN/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/index.md,broken liquid tags
+translations/zh-CN/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises.md,broken liquid tags
translations/zh-CN/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-ae.md,broken liquid tags
translations/zh-CN/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-cloud.md,broken liquid tags
translations/zh-CN/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server.md,broken liquid tags
@@ -158,6 +159,7 @@ translations/zh-CN/content/get-started/learning-about-github/types-of-github-acc
translations/zh-CN/content/get-started/onboarding/getting-started-with-github-ae.md,broken liquid tags
translations/zh-CN/content/get-started/onboarding/getting-started-with-github-enterprise-server.md,broken liquid tags
translations/zh-CN/content/get-started/onboarding/getting-started-with-github-team.md,broken liquid tags
+translations/zh-CN/content/get-started/onboarding/getting-started-with-your-github-account.md,broken liquid tags
translations/zh-CN/content/get-started/privacy-on-github/managing-data-use-settings-for-your-private-repository.md,broken liquid tags
translations/zh-CN/content/get-started/quickstart/communicating-on-github.md,broken liquid tags
translations/zh-CN/content/get-started/quickstart/git-and-github-learning-resources.md,broken liquid tags
@@ -205,11 +207,7 @@ translations/zh-CN/content/rest/guides/getting-started-with-the-rest-api.md,brok
translations/zh-CN/content/rest/overview/other-authentication-methods.md,Listed in localization-support#489
translations/zh-CN/content/rest/overview/other-authentication-methods.md,broken liquid tags
translations/zh-CN/content/rest/overview/resources-in-the-rest-api.md,Listed in localization-support#489
-translations/zh-CN/content/rest/reference/activity.md,broken liquid tags
-translations/zh-CN/content/rest/reference/apps.md,broken liquid tags
translations/zh-CN/content/rest/reference/enterprise-admin.md,broken liquid tags
-translations/zh-CN/content/rest/reference/packages.md,broken liquid tags
-translations/zh-CN/content/rest/reference/secret-scanning.md,broken liquid tags
translations/zh-CN/content/sponsors/getting-started-with-github-sponsors/about-github-sponsors.md,broken liquid tags
translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/about-github-sponsors-for-open-source-contributors.md,broken liquid tags
translations/zh-CN/content/support/contacting-github-support/creating-a-support-ticket.md,broken liquid tags
@@ -226,6 +224,7 @@ translations/zh-CN/data/reusables/actions/enterprise-common-prereqs.md,broken li
translations/zh-CN/data/reusables/actions/enterprise-marketplace-actions.md,broken liquid tags
translations/zh-CN/data/reusables/actions/enterprise-no-internet-actions.md,broken liquid tags
translations/zh-CN/data/reusables/actions/enterprise-postinstall-nextsteps.md,broken liquid tags
+translations/zh-CN/data/reusables/actions/self-hosted-runner-auto-removal.md,broken liquid tags
translations/zh-CN/data/reusables/advanced-security/about-committer-numbers-ghec-ghes.md,broken liquid tags
translations/zh-CN/data/reusables/apps/deprecating_auth_with_query_parameters.md,Listed in localization-support#489
translations/zh-CN/data/reusables/code-scanning/codeql-context-for-actions-and-third-party-tools.md,broken liquid tags
@@ -239,7 +238,6 @@ translations/zh-CN/data/reusables/enterprise_installation/hardware-consideration
translations/zh-CN/data/reusables/enterprise_installation/upgrade-hardware-requirements.md,broken liquid tags
translations/zh-CN/data/reusables/enterprise_management_console/badge_indicator.md,broken liquid tags
translations/zh-CN/data/reusables/getting-started/marketplace.md,broken liquid tags
-translations/zh-CN/data/reusables/github-actions/self-hosted-runner-auto-removal.md,broken liquid tags
translations/zh-CN/data/reusables/github-connect/send-contribution-counts-to-githubcom.md,broken liquid tags
translations/zh-CN/data/reusables/large_files/rejected_pushes.md,broken liquid tags
translations/zh-CN/data/reusables/notifications/vulnerable-dependency-notification-options.md,Listed in localization-support#489
@@ -250,6 +248,10 @@ translations/zh-CN/data/reusables/package_registry/next-steps-for-packages-enter
translations/zh-CN/data/reusables/package_registry/packages-cluster-support.md,broken liquid tags
translations/zh-CN/data/reusables/repositories/deleted_forks_from_private_repositories_warning.md,broken liquid tags
translations/zh-CN/data/reusables/repositories/github-reviews-security-advisories.md,broken liquid tags
+translations/zh-CN/data/reusables/rest-reference/activity/events.md,broken liquid tags
+translations/zh-CN/data/reusables/rest-reference/apps/marketplace.md,broken liquid tags
+translations/zh-CN/data/reusables/rest-reference/packages/packages.md,broken liquid tags
+translations/zh-CN/data/reusables/rest-reference/secret-scanning/secret-scanning.md,broken liquid tags
translations/zh-CN/data/reusables/saml/you-must-periodically-authenticate.md,Listed in localization-support#489
translations/zh-CN/data/reusables/saml/you-must-periodically-authenticate.md,parsing error
translations/zh-CN/data/reusables/scim/after-you-configure-saml.md,broken liquid tags
diff --git a/translations/log/es-resets.csv b/translations/log/es-resets.csv
index 67d1570a42cb..0810ee8f7398 100644
--- a/translations/log/es-resets.csv
+++ b/translations/log/es-resets.csv
@@ -294,7 +294,6 @@ translations/es-ES/content/pull-requests/committing-changes-to-your-project/inde
translations/es-ES/content/pull-requests/committing-changes-to-your-project/troubleshooting-commits/commit-exists-on-github-but-not-in-my-local-clone.md,Listed in localization-support#489
translations/es-ES/content/pull-requests/committing-changes-to-your-project/troubleshooting-commits/index.md,Listed in localization-support#489
translations/es-ES/content/pull-requests/committing-changes-to-your-project/troubleshooting-commits/why-are-my-commits-linked-to-the-wrong-user.md,Listed in localization-support#489
-translations/es-ES/content/pull-requests/committing-changes-to-your-project/viewing-and-comparing-commits/commit-branch-and-tag-labels.md,Listed in localization-support#489
translations/es-ES/content/pull-requests/committing-changes-to-your-project/viewing-and-comparing-commits/comparing-commits.md,Listed in localization-support#489
translations/es-ES/content/pull-requests/committing-changes-to-your-project/viewing-and-comparing-commits/differences-between-commit-views.md,Listed in localization-support#489
translations/es-ES/content/pull-requests/committing-changes-to-your-project/viewing-and-comparing-commits/index.md,Listed in localization-support#489
@@ -325,7 +324,6 @@ translations/es-ES/content/repositories/working-with-files/managing-large-files/
translations/es-ES/content/rest/overview/other-authentication-methods.md,Listed in localization-support#489
translations/es-ES/content/rest/reference/actions.md,Listed in localization-support#489
translations/es-ES/content/rest/reference/activity.md,Listed in localization-support#489
-translations/es-ES/content/rest/reference/activity.md,broken liquid tags
translations/es-ES/content/rest/reference/apps.md,Listed in localization-support#489
translations/es-ES/content/rest/reference/billing.md,Listed in localization-support#489
translations/es-ES/content/rest/reference/checks.md,Listed in localization-support#489
@@ -342,6 +340,7 @@ translations/es-ES/content/support/learning-about-github-support/about-github-su
translations/es-ES/data/release-notes/enterprise-server/3-2/0-rc1.yml,broken liquid tags
translations/es-ES/data/release-notes/enterprise-server/3-2/0.yml,broken liquid tags
translations/es-ES/data/release-notes/github-ae/2021-06/2021-12-06.yml,broken liquid tags
+translations/es-ES/data/reusables/actions/contacting-support.md,broken liquid tags
translations/es-ES/data/reusables/actions/enterprise-marketplace-actions.md,broken liquid tags
translations/es-ES/data/reusables/actions/enterprise-storage-ha-backups.md,broken liquid tags
translations/es-ES/data/reusables/code-scanning/codeql-context-for-actions-and-third-party-tools.md,broken liquid tags
@@ -353,9 +352,9 @@ translations/es-ES/data/reusables/dependabot/dependabot-tos.md,broken liquid tag
translations/es-ES/data/reusables/enterprise_installation/download-appliance.md,broken liquid tags
translations/es-ES/data/reusables/enterprise_management_console/badge_indicator.md,broken liquid tags
translations/es-ES/data/reusables/getting-started/marketplace.md,broken liquid tags
-translations/es-ES/data/reusables/github-actions/contacting-support.md,broken liquid tags
translations/es-ES/data/reusables/github-connect/send-contribution-counts-to-githubcom.md,broken liquid tags
translations/es-ES/data/reusables/organizations/data_saved_for_reinstating_a_former_org_member.md,broken liquid tags
translations/es-ES/data/reusables/package_registry/authenticate-packages.md,Listed in localization-support#489
translations/es-ES/data/reusables/package_registry/authenticate-packages.md,broken liquid tags
translations/es-ES/data/reusables/repositories/deleted_forks_from_private_repositories_warning.md,broken liquid tags
+translations/es-ES/data/reusables/rest-reference/activity/events.md,broken liquid tags
diff --git a/translations/log/ja-resets.csv b/translations/log/ja-resets.csv
index 81c17e5f13ff..f3a7c19c1081 100644
--- a/translations/log/ja-resets.csv
+++ b/translations/log/ja-resets.csv
@@ -42,6 +42,7 @@ translations/ja-JP/content/admin/github-actions/enabling-github-actions-for-gith
translations/ja-JP/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-azure-blob-storage.md,broken liquid tags
translations/ja-JP/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-minio-gateway-for-nas-storage.md,broken liquid tags
translations/ja-JP/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/index.md,broken liquid tags
+translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises.md,broken liquid tags
translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-ae.md,broken liquid tags
translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-cloud.md,broken liquid tags
translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server.md,broken liquid tags
@@ -179,7 +180,6 @@ translations/ja-JP/content/repositories/viewing-activity-and-data-for-your-repos
translations/ja-JP/content/repositories/working-with-files/managing-files/deleting-files-in-a-repository.md,broken liquid tags
translations/ja-JP/content/repositories/working-with-files/managing-large-files/about-git-large-file-storage.md,broken liquid tags
translations/ja-JP/content/repositories/working-with-files/managing-large-files/about-storage-and-bandwidth-usage.md,broken liquid tags
-translations/ja-JP/content/rest/reference/activity.md,broken liquid tags
translations/ja-JP/content/rest/reference/enterprise-admin.md,broken liquid tags
translations/ja-JP/content/sponsors/getting-started-with-github-sponsors/about-github-sponsors.md,broken liquid tags
translations/ja-JP/content/sponsors/receiving-sponsorships-through-github-sponsors/about-github-sponsors-for-open-source-contributors.md,broken liquid tags
@@ -215,10 +215,12 @@ translations/ja-JP/data/release-notes/enterprise-server/3-2/0-rc1.yml,broken liq
translations/ja-JP/data/release-notes/enterprise-server/3-2/0.yml,broken liquid tags
translations/ja-JP/data/release-notes/github-ae/2021-03/2021-03-03.yml,broken liquid tags
translations/ja-JP/data/reusables/actions/allow-specific-actions-intro.md,broken liquid tags
+translations/ja-JP/data/reusables/actions/disabling-github-actions.md,broken liquid tags
translations/ja-JP/data/reusables/actions/enterprise-common-prereqs.md,broken liquid tags
translations/ja-JP/data/reusables/actions/enterprise-marketplace-actions.md,broken liquid tags
translations/ja-JP/data/reusables/actions/enterprise-no-internet-actions.md,broken liquid tags
translations/ja-JP/data/reusables/actions/enterprise-postinstall-nextsteps.md,broken liquid tags
+translations/ja-JP/data/reusables/actions/self-hosted-runner-auto-removal.md,broken liquid tags
translations/ja-JP/data/reusables/advanced-security/about-committer-numbers-ghec-ghes.md,broken liquid tags
translations/ja-JP/data/reusables/code-scanning/enterprise-enable-code-scanning-actions.md,broken liquid tags
translations/ja-JP/data/reusables/code-scanning/enterprise-enable-code-scanning.md,broken liquid tags
@@ -243,8 +245,6 @@ translations/ja-JP/data/reusables/enterprise_management_console/advanced-securit
translations/ja-JP/data/reusables/enterprise_management_console/badge_indicator.md,broken liquid tags
translations/ja-JP/data/reusables/gated-features/code-scanning.md,Listed in localization-support#489
translations/ja-JP/data/reusables/getting-started/marketplace.md,broken liquid tags
-translations/ja-JP/data/reusables/github-actions/disabling-github-actions.md,broken liquid tags
-translations/ja-JP/data/reusables/github-actions/self-hosted-runner-auto-removal.md,broken liquid tags
translations/ja-JP/data/reusables/large_files/can-include-lfs-objects-archives.md,broken liquid tags
translations/ja-JP/data/reusables/large_files/rejected_pushes.md,broken liquid tags
translations/ja-JP/data/reusables/large_files/storage_assets_location.md,broken liquid tags
@@ -258,6 +258,7 @@ translations/ja-JP/data/reusables/pages/choose-visibility.md,broken liquid tags
translations/ja-JP/data/reusables/repositories/about-github-archive-program.md,broken liquid tags
translations/ja-JP/data/reusables/repositories/deleted_forks_from_private_repositories_warning.md,broken liquid tags
translations/ja-JP/data/reusables/rest-api/dotcom-only-guide-note.md,broken liquid tags
+translations/ja-JP/data/reusables/rest-reference/activity/events.md,broken liquid tags
translations/ja-JP/data/reusables/saml/contact-support-if-your-idp-is-unavailable.md,broken liquid tags
translations/ja-JP/data/reusables/scim/after-you-configure-saml.md,broken liquid tags
translations/ja-JP/data/reusables/secret-scanning/enterprise-enable-secret-scanning.md,broken liquid tags
diff --git a/translations/log/pt-resets.csv b/translations/log/pt-resets.csv
index ea91d08a19d8..fd8b96a36bc4 100644
--- a/translations/log/pt-resets.csv
+++ b/translations/log/pt-resets.csv
@@ -40,7 +40,6 @@ translations/pt-BR/content/packages/working-with-a-github-packages-registry/work
translations/pt-BR/content/packages/working-with-a-github-packages-registry/working-with-the-rubygems-registry.md,broken liquid tags
translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md,parsing error
translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/about-email-notifications-for-pushes-to-your-repository.md,broken liquid tags
-translations/pt-BR/content/rest/reference/activity.md,broken liquid tags
translations/pt-BR/content/rest/reference/enterprise-admin.md,Listed in localization-support#489
translations/pt-BR/content/rest/reference/enterprise-admin.md,broken liquid tags
translations/pt-BR/content/rest/reference/gists.md,Listed in localization-support#489
@@ -55,8 +54,6 @@ translations/pt-BR/data/reusables/code-scanning/edit-workflow.md,broken liquid t
translations/pt-BR/data/reusables/dashboard/access-org-dashboard.md,broken liquid tags
translations/pt-BR/data/reusables/enterprise_management_console/badge_indicator.md,broken liquid tags
translations/pt-BR/data/reusables/enterprise_site_admin_settings/business.md,Listed in localization-support#489
-translations/pt-BR/data/reusables/github-actions/self-hosted-runner-management-permissions-required.md,Listed in localization-support#489
-translations/pt-BR/data/reusables/github-actions/self-hosted-runner-navigate-to-repo-org-enterprise.md,Listed in localization-support#489
translations/pt-BR/data/reusables/github-connect/send-contribution-counts-to-githubcom.md,broken liquid tags
translations/pt-BR/data/reusables/package_registry/authenticate-packages.md,broken liquid tags
translations/pt-BR/data/reusables/pages/decide-publishing-source.md,Listed in localization-support#489
@@ -66,3 +63,4 @@ translations/pt-BR/data/reusables/repositories/deleted_forks_from_private_reposi
translations/pt-BR/data/reusables/repositories/security-alerts-x-github-severity.md,Listed in localization-support#489
translations/pt-BR/data/reusables/repositories/squash-and-rebase-linear-commit-hisitory.md,Listed in localization-support#489
translations/pt-BR/data/reusables/repositories/suggest-changes.md,Listed in localization-support#489
+translations/pt-BR/data/reusables/rest-reference/activity/events.md,broken liquid tags
diff --git a/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-java-with-ant.md b/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-java-with-ant.md
index 787af46b7eab..ab62271d9e5b 100644
--- a/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-java-with-ant.md
+++ b/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-java-with-ant.md
@@ -78,9 +78,9 @@ Este fluxo de trabalho executa os seguintes passos:
Os fluxos de trabalho inicial padrão são excelentes pontos de partida ao criar seu fluxo de trabalho de criação e teste, e você pode personalizar o fluxo de trabalho inicial para atender às necessidades do seu projeto.
-{% data reusables.github-actions.example-github-runner %}
+{% data reusables.actions.example-github-runner %}
-{% data reusables.github-actions.java-jvm-architecture %}
+{% data reusables.actions.java-jvm-architecture %}
## Criar e testar seu código
diff --git a/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-java-with-gradle.md b/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-java-with-gradle.md
index 40fbd049e1cc..25c2262200f6 100644
--- a/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-java-with-gradle.md
+++ b/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-java-with-gradle.md
@@ -83,9 +83,9 @@ Este fluxo de trabalho executa os seguintes passos:
Os fluxos de trabalho inicial padrão são excelentes pontos de partida ao criar seu fluxo de trabalho de criação e teste, e você pode personalizar o fluxo de trabalho inicial para atender às necessidades do seu projeto.
-{% data reusables.github-actions.example-github-runner %}
+{% data reusables.actions.example-github-runner %}
-{% data reusables.github-actions.java-jvm-architecture %}
+{% data reusables.actions.java-jvm-architecture %}
## Criar e testar seu código
diff --git a/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-java-with-maven.md b/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-java-with-maven.md
index d1bf976149a3..08c340c40090 100644
--- a/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-java-with-maven.md
+++ b/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-java-with-maven.md
@@ -78,9 +78,9 @@ Este fluxo de trabalho executa os seguintes passos:
Os fluxos de trabalho inicial padrão são excelentes pontos de partida ao criar seu fluxo de trabalho de criação e teste, e você pode personalizar o fluxo de trabalho inicial para atender às necessidades do seu projeto.
-{% data reusables.github-actions.example-github-runner %}
+{% data reusables.actions.example-github-runner %}
-{% data reusables.github-actions.java-jvm-architecture %}
+{% data reusables.actions.java-jvm-architecture %}
## Criar e testar seu código
diff --git a/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-nodejs.md b/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-nodejs.md
index 55903b2c3e74..068200a1d336 100644
--- a/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-nodejs.md
+++ b/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-nodejs.md
@@ -73,7 +73,7 @@ jobs:
```
{% endraw %}
-{% data reusables.github-actions.example-github-runner %}
+{% data reusables.actions.example-github-runner %}
## Especificar a versão do Node.js
@@ -204,7 +204,7 @@ steps:
### Exemplo do uso de um registro privado e de criação o arquivo .npmrc
-{% data reusables.github-actions.setup-node-intro %}
+{% data reusables.actions.setup-node-intro %}
Para efetuar a autenticação com seu registro privado, você precisará armazenar seu token de autenticação npm como um segredo. Por exemplo, crie um repositório secreto denominado `NPM_TOKEN`. Para obter mais informações, consulte "[Criando e usando segredos encriptados](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)".
diff --git a/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-xamarin-applications.md b/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-xamarin-applications.md
index 7388b80c4375..9c11c15850ac 100644
--- a/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-xamarin-applications.md
+++ b/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-xamarin-applications.md
@@ -31,7 +31,7 @@ Para obter uma lista completa das versões Xamarin SDK disponíveis nos executor
* [macOS 10.15](https://github.com/actions/virtual-environments/blob/main/images/macos/macos-10.15-Readme.md#xamarin-bundles)
* [macOS 11](https://github.com/actions/virtual-environments/blob/main/images/macos/macos-11-Readme.md#xamarin-bundles)
-{% data reusables.github-actions.macos-runner-preview %}
+{% data reusables.actions.macos-runner-preview %}
## Pré-requisitos
diff --git a/translations/pt-BR/content/actions/creating-actions/about-custom-actions.md b/translations/pt-BR/content/actions/creating-actions/about-custom-actions.md
index f832337a096b..33dc278994ef 100644
--- a/translations/pt-BR/content/actions/creating-actions/about-custom-actions.md
+++ b/translations/pt-BR/content/actions/creating-actions/about-custom-actions.md
@@ -47,13 +47,13 @@ Os contêineres Docker criam um pacote do ambiente com o código {% data variabl
Um contêiner Docker permite usar versões específicas de um sistema operacional, bem como as dependências, as ferramentas e o código. Para ações a serem executadas em uma configuração específica de ambiente, o Docker é a opção ideal porque permite personalizar o sistema operacional e as ferramentas. Por causa da latência para compilar e recuperar o contêiner, as ações de contêiner Docker são mais lentas que as ações JavaScripts.
-As ações do contêiner Docker podem apenas ser executadas em executores com o sistema operacional Linux. {% data reusables.github-actions.self-hosted-runner-reqs-docker %}
+As ações do contêiner Docker podem apenas ser executadas em executores com o sistema operacional Linux. {% data reusables.actions.self-hosted-runner-reqs-docker %}
### Ações JavaScript
As ações do JavaScript podem ser executadas diretamente em uma máquina executora e separar o código de ação do ambiente usado para executar o código. Usar ações JavaScript simplifica o código da ação e é um processo mais rápido se comparado à opção do contêiner Docker.
-{% data reusables.github-actions.pure-javascript %}
+{% data reusables.actions.pure-javascript %}
Se você estiver desenvolvendo um projeto Node.js, o kit de ferramentas {% data variables.product.prodname_actions %} fornecerá pacotes que você poderá usar para acelerar o desenvolvimento. Para obter mais informações, consulte o repositório [ações/conjuntos de ferramentas](https://github.com/actions/toolkit).
diff --git a/translations/pt-BR/content/actions/creating-actions/creating-a-composite-action.md b/translations/pt-BR/content/actions/creating-actions/creating-a-composite-action.md
index 4964f966f4c2..74cb1a2a8d22 100644
--- a/translations/pt-BR/content/actions/creating-actions/creating-a-composite-action.md
+++ b/translations/pt-BR/content/actions/creating-actions/creating-a-composite-action.md
@@ -23,7 +23,7 @@ Neste guia, você aprenderá os componentes básicos necessários para criar e u
Ao concluir este projeto, você entenderá como criar a sua própria ação composta e testá-la em um fluxo de trabalho.
-{% data reusables.github-actions.context-injection-warning %}
+{% data reusables.actions.context-injection-warning %}
## Pré-requisitos
diff --git a/translations/pt-BR/content/actions/creating-actions/creating-a-docker-container-action.md b/translations/pt-BR/content/actions/creating-actions/creating-a-docker-container-action.md
index 3402afdd5e76..96868f2b2073 100644
--- a/translations/pt-BR/content/actions/creating-actions/creating-a-docker-container-action.md
+++ b/translations/pt-BR/content/actions/creating-actions/creating-a-docker-container-action.md
@@ -27,9 +27,9 @@ Neste guia, você aprenderá os componentes básicos necessários para criar e u
Ao terminar esse projeto, você entenderá como criar sua própria ação de contêiner Docker e poderá testá-la em um fluxo de trabalho.
-{% data reusables.github-actions.self-hosted-runner-reqs-docker %}
+{% data reusables.actions.self-hosted-runner-reqs-docker %}
-{% data reusables.github-actions.context-injection-warning %}
+{% data reusables.actions.context-injection-warning %}
## Pré-requisitos
diff --git a/translations/pt-BR/content/actions/creating-actions/creating-a-javascript-action.md b/translations/pt-BR/content/actions/creating-actions/creating-a-javascript-action.md
index 8c1a06b1f81e..10cd71ef28f6 100644
--- a/translations/pt-BR/content/actions/creating-actions/creating-a-javascript-action.md
+++ b/translations/pt-BR/content/actions/creating-actions/creating-a-javascript-action.md
@@ -29,9 +29,9 @@ Este guia usa o módulo Node.js do kit de ferramentas {% data variables.product.
Ao terminar esse projeto, você entenderá como criar sua própria ação JavaScript e poderá testá-la em um fluxo de trabalho.
-{% data reusables.github-actions.pure-javascript %}
+{% data reusables.actions.pure-javascript %}
-{% data reusables.github-actions.context-injection-warning %}
+{% data reusables.actions.context-injection-warning %}
## Pré-requisitos
diff --git a/translations/pt-BR/content/actions/creating-actions/dockerfile-support-for-github-actions.md b/translations/pt-BR/content/actions/creating-actions/dockerfile-support-for-github-actions.md
index 71d718f64c23..72e76c47130a 100644
--- a/translations/pt-BR/content/actions/creating-actions/dockerfile-support-for-github-actions.md
+++ b/translations/pt-BR/content/actions/creating-actions/dockerfile-support-for-github-actions.md
@@ -105,7 +105,7 @@ Se você definir os `args` no arquivo de metadados da ação, os `args` irão su
Se você usar `CMD` no seu `arquivo Docker`, siga essas diretrizes:
-{% data reusables.github-actions.dockerfile-guidelines %}
+{% data reusables.actions.dockerfile-guidelines %}
## Recursos compatíveis com o Linux
diff --git a/translations/pt-BR/content/actions/creating-actions/metadata-syntax-for-github-actions.md b/translations/pt-BR/content/actions/creating-actions/metadata-syntax-for-github-actions.md
index acb421c414fd..79d3c9f8309a 100644
--- a/translations/pt-BR/content/actions/creating-actions/metadata-syntax-for-github-actions.md
+++ b/translations/pt-BR/content/actions/creating-actions/metadata-syntax-for-github-actions.md
@@ -272,7 +272,7 @@ Para obter mais informações, consulte "[`github context`](/actions/reference/c
**Opcional** Você pode usar o `if` condicional para evitar que uma etapa seja executada, a menos que uma condição seja atendida. Você pode usar qualquer contexto e expressão compatível para criar uma condicional.
-{% data reusables.github-actions.expression-syntax-if %} Para obter mais informações, consulte "[Expressões](/actions/learn-github-actions/expressions)".
+{% data reusables.actions.expression-syntax-if %} Para obter mais informações, consulte "[Expressões](/actions/learn-github-actions/expressions)".
**Exemplo: Usando contextos**
@@ -441,7 +441,7 @@ runs:
`args` são usados em substituição à instrução `CMD` em um `Dockerfile`. Se você usar `CMD` no `Dockerfile`, use as diretrizes ordenadas por preferência:
-{% data reusables.github-actions.dockerfile-guidelines %}
+{% data reusables.actions.dockerfile-guidelines %}
Se você precisar passar variáveis de ambiente para uma ação, certifique-se de que sua ação executa um shell de comando para realizar a substituição de variáveis. Por exemplo, se seu atributo `entrypoint` é definido como `"sh -c"`, os `args` serão executados em um terminal de comando. Como alternativa, se o seu `arquivo Docker` usar um `Entrypoint` para executar o mesmo comando (`"sh-c"`), os `Args` serão executado em um shell de comando.
diff --git a/translations/pt-BR/content/actions/deployment/targeting-different-environments/using-environments-for-deployment.md b/translations/pt-BR/content/actions/deployment/targeting-different-environments/using-environments-for-deployment.md
index 7cff6853c032..619d99ac2a34 100644
--- a/translations/pt-BR/content/actions/deployment/targeting-different-environments/using-environments-for-deployment.md
+++ b/translations/pt-BR/content/actions/deployment/targeting-different-environments/using-environments-for-deployment.md
@@ -69,13 +69,13 @@ Os segredos armazenados em um ambiente só estão disponíveis para trabalhos de
## Criar um ambiente
-{% data reusables.github-actions.permissions-statement-environment %}
+{% data reusables.actions.permissions-statement-environment %}
{% data reusables.repositories.navigate-to-repo %}
{% data reusables.repositories.sidebar-settings %}
-{% data reusables.github-actions.sidebar-environment %}
-{% data reusables.github-actions.new-environment %}
-{% data reusables.github-actions.name-environment %}
+{% data reusables.actions.sidebar-environment %}
+{% data reusables.actions.new-environment %}
+{% data reusables.actions.name-environment %}
1. Opcionalmente, especifique as pessoas ou equipes que devem aprovar os trabalhos do fluxo de trabalho que usam esse ambiente.
1. Selecione **Revisores necessários**.
1. Insira até até 6 pessoas ou equipes. Apenas um dos revisores precisam aprovar o trabalho para que prossiga.
@@ -107,13 +107,13 @@ Quando um fluxo de trabalho faz referência a um ambiente, o ambiente aparecerá
## Excluir um ambiente
-{% data reusables.github-actions.permissions-statement-environment %}
+{% data reusables.actions.permissions-statement-environment %}
A exclusão de um ambiente apagará todos os segredos e regras de proteção associados ao ambiente. Todos os trabalhos que estejam atualmente em espera devido às regras de proteção do ambiente eliminado falharão automaticamente.
{% data reusables.repositories.navigate-to-repo %}
{% data reusables.repositories.sidebar-settings %}
-{% data reusables.github-actions.sidebar-environment %}
+{% data reusables.actions.sidebar-environment %}
1. Ao lado do ambiente que você deseja excluir, clique em {% octicon "trash" aria-label="The trash icon" %}.
2. Clique em **Eu entendi, exclua este ambiente**.
diff --git a/translations/pt-BR/content/actions/hosting-your-own-runners/about-self-hosted-runners.md b/translations/pt-BR/content/actions/hosting-your-own-runners/about-self-hosted-runners.md
index d2d43e503959..31c4aee2284f 100644
--- a/translations/pt-BR/content/actions/hosting-your-own-runners/about-self-hosted-runners.md
+++ b/translations/pt-BR/content/actions/hosting-your-own-runners/about-self-hosted-runners.md
@@ -18,25 +18,25 @@ type: overview
## About self-hosted runners
-{% data reusables.github-actions.self-hosted-runner-description %} Self-hosted runners can be physical, virtual, in a container, on-premises, or in a cloud.
+{% data reusables.actions.self-hosted-runner-description %} Self-hosted runners can be physical, virtual, in a container, on-premises, or in a cloud.
You can add self-hosted runners at various levels in the management hierarchy:
- Repository-level runners are dedicated to a single repository.
- Organization-level runners can process jobs for multiple repositories in an organization.
- Enterprise-level runners can be assigned to multiple organizations in an enterprise account.
-Your runner machine connects to {% data variables.product.product_name %} using the {% data variables.product.prodname_actions %} self-hosted runner application. {% data reusables.github-actions.runner-app-open-source %} When a new version is released, the runner application automatically updates itself when a job is assigned to the runner, or within a week of release if the runner hasn't been assigned any jobs.
+Your runner machine connects to {% data variables.product.product_name %} using the {% data variables.product.prodname_actions %} self-hosted runner application. {% data reusables.actions.runner-app-open-source %} When a new version is released, the runner application automatically updates itself when a job is assigned to the runner, or within a week of release if the runner hasn't been assigned any jobs.
-{% data reusables.github-actions.self-hosted-runner-auto-removal %}
+{% data reusables.actions.self-hosted-runner-auto-removal %}
For more information about installing and using self-hosted runners, see "[Adding self-hosted runners](/github/automating-your-workflow-with-github-actions/adding-self-hosted-runners)" and "[Using self-hosted runners in a workflow](/github/automating-your-workflow-with-github-actions/using-self-hosted-runners-in-a-workflow)."
-## {% ifversion fpt or ghes %}Differences between {% data variables.product.prodname_dotcom %}-hosted and {% elsif ghae %}Characteristics of {% endif %}self-hosted runners
+## {% ifversion fpt or ghec or ghes %}Differences between {% data variables.product.prodname_dotcom %}-hosted and {% elsif ghae %}Characteristics of {% endif %}self-hosted runners
-{% ifversion fpt or ghes %}
+{% ifversion fpt or ghec or ghes %}
{% data variables.product.prodname_dotcom %}-hosted runners offer a quicker, simpler way to run your workflows, while self-hosted{% elsif ghae %}Self-hosted{% endif %} runners are a highly configurable way to run workflows in your own custom environment. {% ifversion ghae %}Self-hosted runners:{% endif %}
-{% ifversion fpt or ghes %}
+{% ifversion fpt or ghec or ghes %}
**{% data variables.product.prodname_dotcom %}-hosted runners:**
- Receive automatic updates for the operating system, preinstalled packages and tools, and the self-hosted runner application.
- Are managed and maintained by {% data variables.product.prodname_dotcom %}.
@@ -70,15 +70,15 @@ You can automatically increase or decrease the number of self-hosted runners in
There are some limits on {% data variables.product.prodname_actions %} usage when using self-hosted runners. These limits are subject to change.
-{% data reusables.github-actions.usage-workflow-run-time %}
+{% data reusables.actions.usage-workflow-run-time %}
- **Job queue time** - Each job for self-hosted runners can be queued for a maximum of 24 hours. If a self-hosted runner does not start executing the job within this limit, the job is terminated and fails to complete.
-{% data reusables.github-actions.usage-api-requests %}
-- **Job matrix** - {% data reusables.github-actions.usage-matrix-limits %}
-{% data reusables.github-actions.usage-workflow-queue-limits %}
+{% data reusables.actions.usage-api-requests %}
+- **Job matrix** - {% data reusables.actions.usage-matrix-limits %}
+{% data reusables.actions.usage-workflow-queue-limits %}
## Workflow continuity for self-hosted runners
-{% data reusables.github-actions.runner-workflow-continuity %}
+{% data reusables.actions.runner-workflow-continuity %}
## Supported architectures and operating systems for self-hosted runners
@@ -224,7 +224,7 @@ codeload.github.com
{% ifversion fpt or ghec %}
-{% data reusables.github-actions.self-hosted-runner-security %}
+{% data reusables.actions.self-hosted-runner-security %}
{% endif %}
diff --git a/translations/pt-BR/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md b/translations/pt-BR/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md
index a43a506f24e3..6be17995b524 100644
--- a/translations/pt-BR/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md
+++ b/translations/pt-BR/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md
@@ -26,7 +26,7 @@ For information on supported operating systems for self-hosted runners, or using
{% ifversion not ghae %}
{% warning %}
-**Warning:** {% data reusables.github-actions.self-hosted-runner-security %}
+**Warning:** {% data reusables.actions.self-hosted-runner-security %}
For more information, see "[About self-hosted runners](/github/automating-your-workflow-with-github-actions/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)."
@@ -40,18 +40,18 @@ You can add self-hosted runners to a single repository. To add a self-hosted run
{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5091 %}
{% data reusables.repositories.navigate-to-repo %}
{% data reusables.repositories.sidebar-settings %}
-{% data reusables.github-actions.settings-sidebar-actions %}
-{% data reusables.github-actions.settings-sidebar-actions-runners-updated %}
+{% data reusables.actions.settings-sidebar-actions %}
+{% data reusables.actions.settings-sidebar-actions-runners-updated %}
1. Click **New self-hosted runner**.
-{% data reusables.github-actions.self-hosted-runner-configure %}
+{% data reusables.actions.self-hosted-runner-configure %}
{% elsif ghae or ghes < 3.4 %}
{% data reusables.repositories.navigate-to-repo %}
{% data reusables.repositories.sidebar-settings %}
-{% data reusables.github-actions.settings-sidebar-actions-runners %}
+{% data reusables.actions.settings-sidebar-actions-runners %}
1. Under {% ifversion ghes > 3.1 or ghae or ghec %}"Runners"{% else %}"Self-hosted runners"{% endif %}, click **Add runner**.
-{% data reusables.github-actions.self-hosted-runner-configure %}
+{% data reusables.actions.self-hosted-runner-configure %}
{% endif %}
-{% data reusables.github-actions.self-hosted-runner-check-installation-success %}
+{% data reusables.actions.self-hosted-runner-check-installation-success %}
## Adding a self-hosted runner to an organization
@@ -60,21 +60,21 @@ You can add self-hosted runners at the organization level, where they can be use
{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5091 %}
{% data reusables.organizations.navigate-to-org %}
{% data reusables.organizations.org_settings %}
-{% data reusables.github-actions.settings-sidebar-actions %}
-{% data reusables.github-actions.settings-sidebar-actions-runners-updated %}
+{% data reusables.actions.settings-sidebar-actions %}
+{% data reusables.actions.settings-sidebar-actions-runners-updated %}
1. Click **New runner**.
-{% data reusables.github-actions.self-hosted-runner-configure %}
+{% data reusables.actions.self-hosted-runner-configure %}
{% elsif ghae or ghes < 3.4 %}
{% data reusables.organizations.navigate-to-org %}
{% data reusables.organizations.org_settings %}
-{% data reusables.github-actions.settings-sidebar-actions-runners %}
+{% data reusables.actions.settings-sidebar-actions-runners %}
1. Under {% ifversion ghes > 3.1 or ghae %}"Runners", click **Add new**, then click **New runner**.{% elsif ghes < 3.2 %}"Self-hosted runners", click **Add runner**."{% endif %}
-{% data reusables.github-actions.self-hosted-runner-configure %}
+{% data reusables.actions.self-hosted-runner-configure %}
{% endif %}
-{% data reusables.github-actions.self-hosted-runner-check-installation-success %}
+{% data reusables.actions.self-hosted-runner-check-installation-success %}
-{% data reusables.github-actions.self-hosted-runner-public-repo-access %}
+{% data reusables.actions.self-hosted-runner-public-repo-access %}
## Adding a self-hosted runner to an enterprise
@@ -92,7 +92,7 @@ To add a self-hosted runner to an enterprise account, you must be an enterprise
{% data reusables.enterprise-accounts.actions-tab %}
{% data reusables.enterprise-accounts.actions-runners-tab %}
1. Click **New runner**.
-{% data reusables.github-actions.self-hosted-runner-configure %}
+{% data reusables.actions.self-hosted-runner-configure %}
{% elsif ghae or ghes < 3.4 %}
To add a self-hosted runner at the enterprise level of {% data variables.product.product_location %}, you must be a site administrator.
{% data reusables.enterprise-accounts.access-enterprise %}
@@ -100,11 +100,11 @@ To add a self-hosted runner at the enterprise level of {% data variables.product
{% data reusables.enterprise-accounts.actions-tab %}
{% data reusables.enterprise-accounts.actions-runners-tab %}
1. Click **Add new**, then click **New runner**.
-{% data reusables.github-actions.self-hosted-runner-configure %}
+{% data reusables.actions.self-hosted-runner-configure %}
{% endif %}
-{% data reusables.github-actions.self-hosted-runner-check-installation-success %}
+{% data reusables.actions.self-hosted-runner-check-installation-success %}
-{% data reusables.github-actions.self-hosted-runner-public-repo-access %}
+{% data reusables.actions.self-hosted-runner-public-repo-access %}
### Making enterprise runners available to repositories
diff --git a/translations/pt-BR/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md b/translations/pt-BR/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md
index 71768aee7308..b00136367833 100644
--- a/translations/pt-BR/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md
+++ b/translations/pt-BR/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md
@@ -49,22 +49,22 @@ Ao criar um grupo, você deverá escolher uma política que defina quais reposit
{% ifversion ghec or ghes > 3.3 or ghae-issue-5091 %}
{% data reusables.organizations.navigate-to-org %}
{% data reusables.organizations.org_settings %}
-{% data reusables.github-actions.settings-sidebar-actions-runner-groups %}
+{% data reusables.actions.settings-sidebar-actions-runner-groups %}
1. Na seção "Grupos de executores", clique em **Novo grupo de executor**.
- {% data reusables.github-actions.runner-group-assign-policy-repo %}
+ {% data reusables.actions.runner-group-assign-policy-repo %}
{% warning %}
- **Aviso**: {% indented_data_reference reusables.github-actions.self-hosted-runner-security spaces=3 %}
+ **Aviso**: {% indented_data_reference reusables.actions.self-hosted-runner-security spaces=3 %}
Para obter mais informações, consulte "[Sobre os executores auto-hospedados](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)."
{% endwarning %}
-{% data reusables.github-actions.self-hosted-runner-create-group %}
+{% data reusables.actions.self-hosted-runner-create-group %}
{% elsif ghae or ghes < 3.4 %}
{% data reusables.organizations.navigate-to-org %}
{% data reusables.organizations.org_settings %}
-{% data reusables.github-actions.settings-sidebar-actions-runners %}
+{% data reusables.actions.settings-sidebar-actions-runners %}
1. Em {% ifversion ghes > 3.1 or ghae %}"Executores"{% elsif ghes < 3.2 %}"Executores auto-hospedados"{% endif %}, clique em **Adicionar novo** e, em seguida, **Novo grupo**.
@@ -76,7 +76,7 @@ Ao criar um grupo, você deverá escolher uma política que defina quais reposit
**Aviso**
- {% indented_data_reference reusables.github-actions.self-hosted-runner-security spaces=3 %}
+ {% indented_data_reference reusables.actions.self-hosted-runner-security spaces=3 %}
Para obter mais informações, consulte "[Sobre os executores auto-hospedados](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)."
@@ -100,18 +100,18 @@ Ao criar um grupo, você deve escolher uma política que defina quais organizaç
{% data reusables.enterprise-accounts.actions-tab %}
{% data reusables.enterprise-accounts.actions-runner-groups-tab %}
1. Clique em **Novo grupo de executores**.
- {% data reusables.github-actions.runner-group-assign-policy-org %}
+ {% data reusables.actions.runner-group-assign-policy-org %}
{% warning %}
**Aviso**
- {% indented_data_reference reusables.github-actions.self-hosted-runner-security spaces=3 %}
+ {% indented_data_reference reusables.actions.self-hosted-runner-security spaces=3 %}
Para obter mais informações, consulte "[Sobre os executores auto-hospedados](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)."
{% endwarning %}
-{% data reusables.github-actions.self-hosted-runner-create-group %}
+{% data reusables.actions.self-hosted-runner-create-group %}
{% elsif ghae or ghes < 3.4 %}
{% data reusables.enterprise-accounts.access-enterprise %}
{% data reusables.enterprise-accounts.policies-tab %}
@@ -128,7 +128,7 @@ Ao criar um grupo, você deve escolher uma política que defina quais organizaç
**Aviso**
- {% indented_data_reference reusables.github-actions.self-hosted-runner-security spaces=3 %}
+ {% indented_data_reference reusables.actions.self-hosted-runner-security spaces=3 %}
Para obter mais informações, consulte "[Sobre os executores auto-hospedados](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)."
@@ -143,21 +143,21 @@ Ao criar um grupo, você deve escolher uma política que defina quais organizaç
Você pode atualizar a política de acesso de um grupo de executores ou renomear um grupo de executores.
{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5091 %}
-{% data reusables.github-actions.self-hosted-runner-groups-navigate-to-repo-org-enterprise %}
-{% data reusables.github-actions.settings-sidebar-actions-runner-groups-selection %}
+{% data reusables.actions.self-hosted-runner-groups-navigate-to-repo-org-enterprise %}
+{% data reusables.actions.settings-sidebar-actions-runner-groups-selection %}
1. Modifique as opções de acesso ou altere o nome do grupo dp executor.
{% warning %}
**Aviso**
- {% indented_data_reference reusables.github-actions.self-hosted-runner-security spaces=3 %}
+ {% indented_data_reference reusables.actions.self-hosted-runner-security spaces=3 %}
Para obter mais informações, consulte "[Sobre os executores auto-hospedados](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)."
{% endwarning %}
{% elsif ghae or ghes < 3.4 %}
-{% data reusables.github-actions.self-hosted-runner-configure-runner-group-access %}
+{% data reusables.actions.self-hosted-runner-configure-runner-group-access %}
{% endif %}
{% ifversion ghec or ghes or ghae %}
@@ -179,7 +179,7 @@ Não foi possível encontrar nenhum grupo de executor auto-hospedado denominado
Se você não especificar o grupo de um executor durante o processo de registro, seus novos executores auto-hospedados são automaticamente atribuídos ao grupo padrão e poderão ser transferidos para outro grupo.
-{% data reusables.github-actions.self-hosted-runner-navigate-to-org-enterprise %}
+{% data reusables.actions.self-hosted-runner-navigate-to-org-enterprise %}
{% ifversion ghec or ghes > 3.3 or ghae-issue-5091 %}
1. Na lista de "Executores", clique no executor que você deseja configurar.
2. Selecione o menu suspenso do grupo do executor.
@@ -195,7 +195,7 @@ Se você não especificar o grupo de um executor durante o processo de registro,
Os executores auto-hospedados são retornados automaticamente ao grupo-padrão quando seu grupo é removido.
{% ifversion ghes > 3.1 or ghae or ghec %}
-{% data reusables.github-actions.self-hosted-runner-groups-navigate-to-repo-org-enterprise %}
+{% data reusables.actions.self-hosted-runner-groups-navigate-to-repo-org-enterprise %}
1. Na lista de grupos, à direita do grupo que você deseja excluir, clique em {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}.
2. Para remover o grupo, clique em **Remover grupo**.
3. Revise os avisos de confirmação e, em seguida, clique em **Remover este grupo de executores**.
diff --git a/translations/pt-BR/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md b/translations/pt-BR/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md
index 8621853dcd14..9d6baa9ecfe7 100644
--- a/translations/pt-BR/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md
+++ b/translations/pt-BR/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md
@@ -21,10 +21,10 @@ shortTitle: Monitor & troubleshoot
## Checking the status of a self-hosted runner
-{% data reusables.github-actions.self-hosted-runner-management-permissions-required %}
+{% data reusables.actions.self-hosted-runner-management-permissions-required %}
-{% data reusables.github-actions.self-hosted-runner-navigate-repo-and-org %}
-{% data reusables.github-actions.settings-sidebar-actions-runners %}
+{% data reusables.actions.self-hosted-runner-navigate-repo-and-org %}
+{% data reusables.actions.settings-sidebar-actions-runners %}
1. Under {% ifversion fpt or ghes > 3.1 or ghae or ghec %}"Runners"{% else %}"Self-hosted runners"{% endif %}, you can view a list of registered runners, including the runner's name, labels, and status.
The status can be one of the following:
@@ -46,12 +46,12 @@ For example:
{% mac %}
-{% data reusables.github-actions.self-hosted-runner-check-mac-linux %}
+{% data reusables.actions.self-hosted-runner-check-mac-linux %}
{% endmac %}
{% linux %}
-{% data reusables.github-actions.self-hosted-runner-check-mac-linux %}
+{% data reusables.actions.self-hosted-runner-check-mac-linux %}
{% endlinux %}
{% windows %}
diff --git a/translations/pt-BR/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md b/translations/pt-BR/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md
index 4cd76cab1bc5..d573cda288ff 100644
--- a/translations/pt-BR/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md
+++ b/translations/pt-BR/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md
@@ -21,54 +21,54 @@ shortTitle: Remover executores auto-hospedados
{% note %}
-**Observação:** {% data reusables.github-actions.self-hosted-runner-removal-impact %}
+**Observação:** {% data reusables.actions.self-hosted-runner-removal-impact %}
-{% data reusables.github-actions.self-hosted-runner-auto-removal %}
+{% data reusables.actions.self-hosted-runner-auto-removal %}
{% endnote %}
Para remover um executor auto-hospedado de um repositório de usuário, você deve ser o proprietário do repositório. Para um repositório da organização, você deve ser um proprietário da organização ou ter acesso de administrador ao repositório. Recomendamos que você também tenha acesso à máquina do executor auto-hospedado. Para obter informações sobre como remover um executor auto-hospedado com a API REST, consulte "[Executores auto-hospedados](/rest/reference/actions#self-hosted-runners)."
-{% data reusables.github-actions.self-hosted-runner-reusing %}
+{% data reusables.actions.self-hosted-runner-reusing %}
{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5091 %}
{% data reusables.repositories.navigate-to-repo %}
{% data reusables.repositories.sidebar-settings %}
-{% data reusables.github-actions.settings-sidebar-actions %}
-{% data reusables.github-actions.settings-sidebar-actions-runners-updated %}
-{% data reusables.github-actions.settings-sidebar-actions-runner-selection %}
-{% data reusables.github-actions.self-hosted-runner-removing-a-runner-updated %}
+{% data reusables.actions.settings-sidebar-actions %}
+{% data reusables.actions.settings-sidebar-actions-runners-updated %}
+{% data reusables.actions.settings-sidebar-actions-runner-selection %}
+{% data reusables.actions.self-hosted-runner-removing-a-runner-updated %}
{% elsif ghae or ghes < 3.4 %}
{% data reusables.repositories.navigate-to-repo %}
{% data reusables.repositories.sidebar-settings %}
-{% data reusables.github-actions.settings-sidebar-actions-runners %}
-{% data reusables.github-actions.self-hosted-runner-removing-a-runner %}
+{% data reusables.actions.settings-sidebar-actions-runners %}
+{% data reusables.actions.self-hosted-runner-removing-a-runner %}
{% endif %}
## Remover um executor de uma organização
{% note %}
-**Observação:** {% data reusables.github-actions.self-hosted-runner-removal-impact %}
+**Observação:** {% data reusables.actions.self-hosted-runner-removal-impact %}
-{% data reusables.github-actions.self-hosted-runner-auto-removal %}
+{% data reusables.actions.self-hosted-runner-auto-removal %}
{% endnote %}
Para remover um executor auto-hospedado de uma organização, você deve ser um proprietário da organização. Recomendamos que você também tenha acesso à máquina do executor auto-hospedado. Para obter informações sobre como remover um executor auto-hospedado com a API REST, consulte "[Executores auto-hospedados](/rest/reference/actions#self-hosted-runners)."
-{% data reusables.github-actions.self-hosted-runner-reusing %}
+{% data reusables.actions.self-hosted-runner-reusing %}
{% ifversion fpt or ghes > 3.3 or ghec %}
{% data reusables.organizations.navigate-to-org %}
{% data reusables.organizations.org_settings %}
-{% data reusables.github-actions.settings-sidebar-actions %}
-{% data reusables.github-actions.settings-sidebar-actions-runners-updated %}
-{% data reusables.github-actions.settings-sidebar-actions-runner-selection %}
-{% data reusables.github-actions.self-hosted-runner-removing-a-runner-updated %}
+{% data reusables.actions.settings-sidebar-actions %}
+{% data reusables.actions.settings-sidebar-actions-runners-updated %}
+{% data reusables.actions.settings-sidebar-actions-runner-selection %}
+{% data reusables.actions.self-hosted-runner-removing-a-runner-updated %}
{% elsif ghes < 3.4 or ghae %}
{% data reusables.organizations.navigate-to-org %}
{% data reusables.organizations.org_settings %}
-{% data reusables.github-actions.settings-sidebar-actions-runners %}
-{% data reusables.github-actions.self-hosted-runner-removing-a-runner %}
+{% data reusables.actions.settings-sidebar-actions-runners %}
+{% data reusables.actions.self-hosted-runner-removing-a-runner %}
{% endif %}
## Remover um executor de uma empresa
@@ -80,27 +80,27 @@ Se você usar
{% ifversion ghec or ghes or ghae %}
{% note %}
-**Observação:** {% data reusables.github-actions.self-hosted-runner-removal-impact %}
+**Observação:** {% data reusables.actions.self-hosted-runner-removal-impact %}
-{% data reusables.github-actions.self-hosted-runner-auto-removal %}
+{% data reusables.actions.self-hosted-runner-auto-removal %}
{% endnote %}
Para remover um executor auto-hospedado de uma empresa, você deverá ser um proprietário corporativo. Recomendamos que você também tenha acesso à máquina do executor auto-hospedado. Para obter informações sobre como remover um executor auto-hospedado com a API REST, consulte os pontos de extremidade corporativos na [API REST de {% data variables.product.prodname_actions %}](/rest/reference/actions#self-hosted-runners).
-{% data reusables.github-actions.self-hosted-runner-reusing %}
+{% data reusables.actions.self-hosted-runner-reusing %}
{% ifversion ghec or ghes > 3.3 or ghae-issue-5091 %}
{% data reusables.enterprise-accounts.access-enterprise %}
{% data reusables.enterprise-accounts.policies-tab %}
{% data reusables.enterprise-accounts.actions-tab %}
{% data reusables.enterprise-accounts.actions-runners-tab %}
-{% data reusables.github-actions.settings-sidebar-actions-runner-selection %}
-{% data reusables.github-actions.self-hosted-runner-removing-a-runner-updated %}
+{% data reusables.actions.settings-sidebar-actions-runner-selection %}
+{% data reusables.actions.self-hosted-runner-removing-a-runner-updated %}
{% elsif ghae or ghes < 3.4 %}
{% data reusables.enterprise-accounts.access-enterprise %}
{% data reusables.enterprise-accounts.policies-tab %}
{% data reusables.enterprise-accounts.actions-tab %}
{% data reusables.enterprise-accounts.actions-runners-tab %}
-{% data reusables.github-actions.self-hosted-runner-removing-a-runner %}
+{% data reusables.actions.self-hosted-runner-removing-a-runner %}
{% endif %}
{% endif %}
diff --git a/translations/pt-BR/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md b/translations/pt-BR/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md
index ceb170b4a8ce..5b76e8d8a28e 100644
--- a/translations/pt-BR/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md
+++ b/translations/pt-BR/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md
@@ -16,54 +16,54 @@ shortTitle: Executores de etiqueta
Para obter informações sobre como usar etiquetas para encaminhar trabalhos para tipos específicos de executores auto-hospedados, consulte "[Usando executores auto-hospedados em um fluxo de trabalho](/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow)."
-{% data reusables.github-actions.self-hosted-runner-management-permissions-required %}
+{% data reusables.actions.self-hosted-runner-management-permissions-required %}
## Criar etiquetas personalizadas
{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5091 %}
-{% data reusables.github-actions.self-hosted-runner-navigate-to-repo-org-enterprise %}
- {% data reusables.github-actions.settings-sidebar-actions-runner-selection %}
+{% data reusables.actions.self-hosted-runner-navigate-to-repo-org-enterprise %}
+ {% data reusables.actions.settings-sidebar-actions-runner-selection %}
1. Na seção "Etiquetas", clique em {% octicon "gear" aria-label="The Gear icon" %}.
- 1. No campo "Encontrar ou criar uma etiqueta", digite o nome da sua nova etiqueta e clique em **Criar nova etiqueta**. O rótulo personalizado é criado e atribuído ao executor auto-hospedado. É possível remover as etiquetas personalizadas dos executores auto-hospedados, mas não é possível excluí-las manualmente. {% data reusables.github-actions.actions-unused-labels %}
+ 1. No campo "Encontrar ou criar uma etiqueta", digite o nome da sua nova etiqueta e clique em **Criar nova etiqueta**. O rótulo personalizado é criado e atribuído ao executor auto-hospedado. É possível remover as etiquetas personalizadas dos executores auto-hospedados, mas não é possível excluí-las manualmente. {% data reusables.actions.actions-unused-labels %}
{% elsif ghae or ghes < 3.4 %}
-{% data reusables.github-actions.self-hosted-runner-navigate-to-repo-org-enterprise %}
-{% data reusables.github-actions.self-hosted-runner-list %}
-{% data reusables.github-actions.self-hosted-runner-list-group %}
-{% data reusables.github-actions.self-hosted-runner-labels-view-assigned-labels %}
+{% data reusables.actions.self-hosted-runner-navigate-to-repo-org-enterprise %}
+{% data reusables.actions.self-hosted-runner-list %}
+{% data reusables.actions.self-hosted-runner-list-group %}
+{% data reusables.actions.self-hosted-runner-labels-view-assigned-labels %}
1. No campo "Filtrar etiquetas", digite o nome da sua nova etiqueta e clique em **Criar nova etiqueta**. 
-O rótulo personalizado é criado e atribuído ao executor auto-hospedado. É possível remover as etiquetas personalizadas dos executores auto-hospedados, mas não é possível excluí-las manualmente. {% data reusables.github-actions.actions-unused-labels %}
+O rótulo personalizado é criado e atribuído ao executor auto-hospedado. É possível remover as etiquetas personalizadas dos executores auto-hospedados, mas não é possível excluí-las manualmente. {% data reusables.actions.actions-unused-labels %}
{% endif %}
## Atribuir uma etiqueta a um executor auto-hospedado
{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5091 %}
-{% data reusables.github-actions.self-hosted-runner-navigate-to-repo-org-enterprise %}
-{% data reusables.github-actions.settings-sidebar-actions-runner-selection %}
-{% data reusables.github-actions.runner-label-settings %}
+{% data reusables.actions.self-hosted-runner-navigate-to-repo-org-enterprise %}
+{% data reusables.actions.settings-sidebar-actions-runner-selection %}
+{% data reusables.actions.runner-label-settings %}
1. Para atribuir uma etiqueta ao executor auto-hospedado, no campo "Localizar ou criar uma etiqueta", clique na etiqueta.
{% elsif ghae or ghes < 3.4 %}
-{% data reusables.github-actions.self-hosted-runner-navigate-to-repo-org-enterprise %}
-{% data reusables.github-actions.self-hosted-runner-list %}
-{% data reusables.github-actions.self-hosted-runner-list-group %}
-{% data reusables.github-actions.self-hosted-runner-labels-view-assigned-labels %}
+{% data reusables.actions.self-hosted-runner-navigate-to-repo-org-enterprise %}
+{% data reusables.actions.self-hosted-runner-list %}
+{% data reusables.actions.self-hosted-runner-list-group %}
+{% data reusables.actions.self-hosted-runner-labels-view-assigned-labels %}
1. Clique em uma etiqueta a ser atribuída ao seu executor auto-hospedado.
{% endif %}
## Remover uma etiqueta personalizada de um executor auto-hospedado
{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5091 %}
-{% data reusables.github-actions.self-hosted-runner-navigate-to-repo-org-enterprise %}
-{% data reusables.github-actions.settings-sidebar-actions-runner-selection %}
-{% data reusables.github-actions.runner-label-settings %}
+{% data reusables.actions.self-hosted-runner-navigate-to-repo-org-enterprise %}
+{% data reusables.actions.settings-sidebar-actions-runner-selection %}
+{% data reusables.actions.runner-label-settings %}
1. No campo "Encontre ou crie uma etiqueta", as etiquetas atribuídas são marcadas com a
Ícone de {% octicon "check" aria-label="The Check icon" %}. Clique em uma etiqueta marcada para cancelar a atribuição do seu executor auto-hospedado.
{% elsif ghae or ghes < 3.4 %}
-{% data reusables.github-actions.self-hosted-runner-navigate-to-repo-org-enterprise %}
-{% data reusables.github-actions.self-hosted-runner-list %}
-{% data reusables.github-actions.self-hosted-runner-list-group %}
-{% data reusables.github-actions.self-hosted-runner-labels-view-assigned-labels %}
-1. Clique na etiqueta atribuída para removê-la do seu executor auto-hospedado. {% data reusables.github-actions.actions-unused-labels %}
+{% data reusables.actions.self-hosted-runner-navigate-to-repo-org-enterprise %}
+{% data reusables.actions.self-hosted-runner-list %}
+{% data reusables.actions.self-hosted-runner-list-group %}
+{% data reusables.actions.self-hosted-runner-labels-view-assigned-labels %}
+1. Clique na etiqueta atribuída para removê-la do seu executor auto-hospedado. {% data reusables.actions.actions-unused-labels %}
{% endif %}
## Usar o script de configuração para criar e atribuir rótulos
diff --git a/translations/pt-BR/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md b/translations/pt-BR/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md
index f744a1c36f13..49735c8cb9c6 100644
--- a/translations/pt-BR/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md
+++ b/translations/pt-BR/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md
@@ -23,7 +23,7 @@ For information on creating custom and default labels, see "[Using labels with s
Labels allow you to send workflow jobs to specific types of self-hosted runners, based on their shared characteristics. For example, if your job requires a particular hardware component or software package, you can assign a custom label to a runner and then configure your job to only execute on runners with that label.
-{% data reusables.github-actions.self-hosted-runner-labels-runs-on %}
+{% data reusables.actions.self-hosted-runner-labels-runs-on %}
For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/github/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idruns-on)."
diff --git a/translations/pt-BR/content/actions/learn-github-actions/contexts.md b/translations/pt-BR/content/actions/learn-github-actions/contexts.md
index c5d3f077982f..9b8d8debf9ab 100644
--- a/translations/pt-BR/content/actions/learn-github-actions/contexts.md
+++ b/translations/pt-BR/content/actions/learn-github-actions/contexts.md
@@ -31,7 +31,7 @@ Você pode acessar contextos usando a sintaxe da expressão. Para obter mais inf
`${{ }}`
{% endraw %}
-{% data reusables.github-actions.context-injection-warning %}
+{% data reusables.actions.context-injection-warning %}
| Nome do contexto | Tipo | Descrição |
| ---------------- | -------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
@@ -59,7 +59,7 @@ Para usar a sintaxe de propriedade de desreferência, o nome da propriedade deve
### Determinar quando usar contextos
-{% data reusables.github-actions.using-context-or-environment-variables %}
+{% data reusables.actions.using-context-or-environment-variables %}
### Disponibilidade do contexto
@@ -139,7 +139,7 @@ A tabela a seguir indica onde cada contexto e função especial pode ser utiliza
Você pode imprimir o conteúdo de contextos no registro para depuração. A função [`toJSON` ](/actions/learn-github-actions/expressions#tojson) é necessária para imprimir objetos do JSON no registro.
-{% data reusables.github-actions.github-context-warning %}
+{% data reusables.actions.github-context-warning %}
{% raw %}
```yaml{:copy}
@@ -170,8 +170,8 @@ jobs:
O contexto `github` context contém informações sobre a execução do fluxo de trabalho e sobre o evento que a acionou. Você também pode ler a maioria dos dados do `github` em variáveis de ambiente. Para obter mais informações sobre as variáveis de ambiente, consulte "[Usando variáveis de ambiente](/actions/automating-your-workflow-with-github-actions/using-environment-variables)".
-{% data reusables.github-actions.github-context-warning %}
-{% data reusables.github-actions.context-injection-warning %}
+{% data reusables.actions.github-context-warning %}
+{% data reusables.actions.context-injection-warning %}
| Nome da propriedade | Tipo | Descrição |
| -------------------------- | -------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
@@ -194,9 +194,11 @@ O contexto `github` context contém informações sobre a execução do fluxo de
{%- 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 %} | | `github.ref_type` | `string` | {% data reusables.actions.ref_type-description %}
{%- endif %}
-| `github.path` | `string` | Caminho no executor no arquivo que define as variáveis do `PATH` do sistema a partir de comandos do fluxo de trabalho. Este arquivo é único para a etapa atual e é um arquivo diferente para cada etapa de um trabalho. Para obter mais informações, consulte "[Comandos do fluxo de trabalho para {% data variables.product.prodname_actions %}](/actions/learn-github-actions/workflow-commands-for-github-actions#adding-a-system-path)." | | `github.repository` | `string` | O proprietário e o nome do repositório. Por exemplo, `Codertocat/Hello-World`. | | `github.repository_owner` | `string` | O nome do proprietário do repositório. Por exemplo, `Codertocat`. | | `github.repositoryUrl` | `string` | A URL do Git para o repositório. Por exemplo, `git://github.com/codertocat/hello-world.git`. | | `github.retention_days` | `string` | O número de dias que os registros e artefatos da execução do fluxo de trabalho são mantidos. | | `github.run_id` | `string` | {% data reusables.github-actions.run_id_description %} | | `github.run_number` | `string` | {% data reusables.github-actions.run_number_description %}
+| `github.path` | `string` | Caminho no executor no arquivo que define as variáveis do `PATH` do sistema a partir de comandos do fluxo de trabalho. Este arquivo é único para a etapa atual e é um arquivo diferente para cada etapa de um trabalho. Para obter mais informações, consulte "[Comandos do fluxo de trabalho para {% data variables.product.prodname_actions %}](/actions/learn-github-actions/workflow-commands-for-github-actions#adding-a-system-path)." | | `github.repository` | `string` | O proprietário e o nome do repositório. Por exemplo, `Codertocat/Hello-World`. | | `github.repository_owner` | `string` | O nome do proprietário do repositório. Por exemplo, `Codertocat`. | | `github.repositoryUrl` | `string` | A URL do Git para o repositório. Por exemplo, `git://github.com/codertocat/hello-world.git`. | | `github.retention_days` | `string` | O número de dias que os registros e artefatos da execução do fluxo de trabalho são mantidos. | | `github.run_id` | `string` | {% data reusables.actions.run_id_description %} | | `github.run_number` | `string` | {% data reusables.actions.run_number_description %}
{%- ifversion fpt or ghec or ghes > 3.5 or ghae-issue-4722 %}
-| `github.run_attempt` | `string` | Um número exclusivo para cada tentativa de execução de um fluxo de trabalho específico em um repositório. Este número começa em 1 para a primeira tentativa de execução do fluxo de trabalho e aumenta a cada nova execução. | |{% endif %}| | `github.server_url` | `string` | O URL do servidor do GitHub. Por exemplo: `https://github.com`. | | `github.sha` | `string` | O SHA do commit que acionou a execução do fluxo de trabalho. | | `github.token` | `string` | Um token para efetuar a autenticação em nome do aplicativo instalado no seu repositório. Isso é funcionalmente equivalente ao segredo `GITHUB_TOKEN`. Para obter mais informações, consulte "[Autenticação automática de tokens](/actions/security-guides/automatic-token-authentication)". | | `github.workflow` | `string` | O nome do fluxo de trabalho. Se o fluxo de trabalho não determina um `name` (nome), o valor desta propriedade é o caminho completo do arquivo do fluxo de trabalho no repositório. | | `github.workspace` | `string` | O diretório de trabalho padrão no executor para as etapas e a localidade padrão do seu repositório ao usar a ação [`checkout`](https://github.com/actions/checkout). |
+| `github.run_attempt` | `string` | Um número exclusivo para cada tentativa de execução de um fluxo de trabalho específico em um repositório. Este número começa em 1 para a primeira tentativa de execução do fluxo de trabalho e aumenta a cada nova execução. |
+{%- endif %}
+| `github.server_url` | `string` | The URL of the GitHub server. Por exemplo: `https://github.com`. | | `github.sha` | `string` | O SHA do commit que acionou a execução do fluxo de trabalho. | | `github.token` | `string` | Um token para efetuar a autenticação em nome do aplicativo instalado no seu repositório. Isso é funcionalmente equivalente ao segredo `GITHUB_TOKEN`. Para obter mais informações, consulte "[Autenticação automática de tokens](/actions/security-guides/automatic-token-authentication)". | | `github.workflow` | `string` | O nome do fluxo de trabalho. Se o fluxo de trabalho não determina um `name` (nome), o valor desta propriedade é o caminho completo do arquivo do fluxo de trabalho no repositório. | | `github.workspace` | `string` | O diretório de trabalho padrão no executor para as etapas e a localidade padrão do seu repositório ao usar a ação [`checkout`](https://github.com/actions/checkout). |
### Exemplo de conteúdo do contexto `github`
@@ -512,7 +514,7 @@ O contexto `segredos` contém os nomes e valores de segredos disponíveis para a
`GITHUB_TOKEN` é um segredo que é criado automaticamente para cada execução de fluxo de trabalho, e é sempre incluído no contexto `segredos`. Para obter mais informações, consulte "[Autenticação automática de tokens](/actions/security-guides/automatic-token-authentication)".
-{% data reusables.github-actions.secrets-redaction-warning %}
+{% data reusables.actions.secrets-redaction-warning %}
| Nome da propriedade | Tipo | Descrição |
| ----------------------------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
@@ -534,7 +536,7 @@ O conteúdo de exemplo do contexto dos `segredos` mostra o `GITHUB_TOKEN` autom
### Exemplo de uso do contexto dos `segredos`
-{% data reusables.github-actions.github_token-input-example %}
+{% data reusables.actions.github_token-input-example %}
## Contexto `estratégia`
diff --git a/translations/pt-BR/content/actions/learn-github-actions/environment-variables.md b/translations/pt-BR/content/actions/learn-github-actions/environment-variables.md
index 224e99084863..e8e36bf8820a 100644
--- a/translations/pt-BR/content/actions/learn-github-actions/environment-variables.md
+++ b/translations/pt-BR/content/actions/learn-github-actions/environment-variables.md
@@ -147,7 +147,7 @@ As variáveis de ambiente padrão que os conjuntos de {% data variables.product.
{%- 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 %} | | `GITHUB_REF_TYPE` | {% data reusables.actions.ref_type-description %}
{%- endif %}
-| `GITHUB_REPOSITORY` | O nome do proprietário e do repositório. Por exemplo, `octocat/Hello-World`. | | `GITHUB_REPOSITORY_OWNER` | O nome do proprietário do repositório. Por exemplo, `octocat`. | | `GITHUB_RETENTION_DAYS` | O número de dias que os registros da execução do fluxo de trabalho e os artefatos são mantidos. Por exemplo, `90`. | | `GITHUB_RUN_ATTEMPT` | Um número único para cada tentativa da execução de um fluxo de trabalho particular em um repositório. Este número começa em 1 para a primeira tentativa de execução do fluxo de trabalho e aumenta a cada nova execução. Por exemplo, `3`. | | `GITHUB_RUN_ID` | {% data reusables.github-actions.run_id_description %} Por exemplo, `1658821493`. | | `GITHUB_RUN_NUMBER` | {% data reusables.github-actions.run_number_description %} Por exemplo, `3`. | | `GITHUB_SERVER_URL`| A URL do servidor de {% data variables.product.product_name %} server. Por exemplo: `https://{% data variables.product.product_url %}`. | `GITHUB_SHA` | O SHA do commit que acionou o fluxo de trabalho. Por exemplo, `ffac537e6cbbf934b08745a378932722df287a53`. | | `GITHUB_WORKFLOW` | O nome do fluxo de trabalho. Por exemplo, `My test workflow`. Se o fluxo de trabalho não determinar um `nome`, o valor desta variável será o caminho completo do arquivo do fluxo de trabalho no repositório. | | `GITHUB_WORKSPACE` | O diretório de trabalho padrão no executor para as etapas e para a localidade padrão do seu repositório ao usar a ação [`checkout`](https://github.com/actions/checkout). Por exemplo, `/home/runner/work/my-repo-name/my-repo-name`. |
+| `GITHUB_REPOSITORY` | O nome do proprietário e do repositório. Por exemplo, `octocat/Hello-World`. | | `GITHUB_REPOSITORY_OWNER` | O nome do proprietário do repositório. Por exemplo, `octocat`. | | `GITHUB_RETENTION_DAYS` | O número de dias que os registros da execução do fluxo de trabalho e os artefatos são mantidos. Por exemplo, `90`. | | `GITHUB_RUN_ATTEMPT` | Um número único para cada tentativa da execução de um fluxo de trabalho particular em um repositório. Este número começa em 1 para a primeira tentativa de execução do fluxo de trabalho e aumenta a cada nova execução. Por exemplo, `3`. | | `GITHUB_RUN_ID` | {% data reusables.actions.run_id_description %} Por exemplo, `1658821493`. | | `GITHUB_RUN_NUMBER` | {% data reusables.actions.run_number_description %} Por exemplo, `3`. | | `GITHUB_SERVER_URL`| A URL do servidor de {% data variables.product.product_name %} server. Por exemplo: `https://{% data variables.product.product_url %}`. | `GITHUB_SHA` | O SHA do commit que acionou o fluxo de trabalho. Por exemplo, `ffac537e6cbbf934b08745a378932722df287a53`. | | `GITHUB_WORKFLOW` | O nome do fluxo de trabalho. Por exemplo, `My test workflow`. Se o fluxo de trabalho não determinar um `nome`, o valor desta variável será o caminho completo do arquivo do fluxo de trabalho no repositório. | | `GITHUB_WORKSPACE` | O diretório de trabalho padrão no executor para as etapas e para a localidade padrão do seu repositório ao usar a ação [`checkout`](https://github.com/actions/checkout). Por exemplo, `/home/runner/work/my-repo-name/my-repo-name`. |
{%- if actions-runner-arch-envvars %}
| `RUNNER_ARCH` | {% data reusables.actions.runner-arch-description %}
{%- endif %}
diff --git a/translations/pt-BR/content/actions/learn-github-actions/expressions.md b/translations/pt-BR/content/actions/learn-github-actions/expressions.md
index 5102ca6e58e9..e2ffc60118d0 100644
--- a/translations/pt-BR/content/actions/learn-github-actions/expressions.md
+++ b/translations/pt-BR/content/actions/learn-github-actions/expressions.md
@@ -25,9 +25,9 @@ Expressões são comumente usadas com a condicional `if` palavra-chave em um arq
`${{ }}`
{% endraw %}
-{% data reusables.github-actions.expression-syntax-if %} Para obter mais informações sobre as condições `se`, consulte "[Sintaxe de fluxo de trabalho para {% data variables.product.prodname_actions %}](/articles/workflow-syntax-for-github-actions/#jobsjob_idif)".
+{% data reusables.actions.expression-syntax-if %} Para obter mais informações sobre as condições `se`, consulte "[Sintaxe de fluxo de trabalho para {% data variables.product.prodname_actions %}](/articles/workflow-syntax-for-github-actions/#jobsjob_idif)".
-{% data reusables.github-actions.context-injection-warning %}
+{% data reusables.actions.context-injection-warning %}
#### Exemplo de expressão em uma condicional `if`
diff --git a/translations/pt-BR/content/actions/learn-github-actions/understanding-github-actions.md b/translations/pt-BR/content/actions/learn-github-actions/understanding-github-actions.md
index 72379ea7147c..a6ff271a16bd 100644
--- a/translations/pt-BR/content/actions/learn-github-actions/understanding-github-actions.md
+++ b/translations/pt-BR/content/actions/learn-github-actions/understanding-github-actions.md
@@ -254,7 +254,7 @@ Para entender como a cobrança funciona para {% data variables.product.prodname_
## Entrar em contato com o suporte
-{% data reusables.github-actions.contacting-support %}
+{% data reusables.actions.contacting-support %}
## Leia mais
diff --git a/translations/pt-BR/content/actions/learn-github-actions/usage-limits-billing-and-administration.md b/translations/pt-BR/content/actions/learn-github-actions/usage-limits-billing-and-administration.md
index 840b939413ff..d6e57a4a1b4a 100644
--- a/translations/pt-BR/content/actions/learn-github-actions/usage-limits-billing-and-administration.md
+++ b/translations/pt-BR/content/actions/learn-github-actions/usage-limits-billing-and-administration.md
@@ -21,7 +21,7 @@ shortTitle: Cobrança do fluxo de trabalho & limites
{% data reusables.repositories.about-github-actions %} Para obter mais informações, consulte "[Entendendo {% data variables.product.prodname_actions %}](/actions/learn-github-actions/understanding-github-actions){% ifversion fpt %}."{% elsif ghes or ghec %}" e "[Sobre {% data variables.product.prodname_actions %} para empresas](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises)."{% endif %}
{% ifversion fpt or ghec %}
-{% data reusables.github-actions.actions-billing %} Para obter mais informações, consulte "[Sobre a cobrança do {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions/about-billing-for-github-actions)".
+{% data reusables.actions.actions-billing %} Para obter mais informações, consulte "[Sobre a cobrança do {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions/about-billing-for-github-actions)".
{% else %}
O uso do GitHub Actions é grátis para instâncias de {% data variables.product.prodname_ghe_server %} que usam executores auto-hospedados. Para obter mais informações, consulte "[Sobre os executores auto-hospedados](/actions/hosting-your-own-runners/about-self-hosted-runners)."
{% endif %}
@@ -47,8 +47,8 @@ Existem alguns limites sobre o uso de {% data variables.product.prodname_actions
{% endnote %}
- **Tempo de execução de tarefas ** - Cada trabalho em um fluxo de trabalho pode ser executado por até 6 horas de tempo de execução. Se um trabalho atingir esse limite, o trabalho será terminado e não será completado.
-{% data reusables.github-actions.usage-workflow-run-time %}
-{% data reusables.github-actions.usage-api-requests %}
+{% data reusables.actions.usage-workflow-run-time %}
+{% data reusables.actions.usage-api-requests %}
- **Tarefas correntes** - O número de trabalhos simultâneos que você pode executar em sua conta depende do seu plano GitHub, conforme indicado na tabela a seguir. Se excedido, quaisquer tarefas adicionais serão colocadas na fila.
| Plano GitHub | Total de tarefas simultâneas | Máximo de tarefas macOS simultâneas |
@@ -57,8 +57,8 @@ Existem alguns limites sobre o uso de {% data variables.product.prodname_actions
| Pro | 40 | 5 |
| Equipe | 60 | 5 |
| Enterprise | 180 | 50 |
-- **Matriz de vagas** - {% data reusables.github-actions.usage-matrix-limits %}
-{% data reusables.github-actions.usage-workflow-queue-limits %}
+- **Matriz de vagas** - {% data reusables.actions.usage-matrix-limits %}
+{% data reusables.actions.usage-workflow-queue-limits %}
{% else %}
Os limites de uso aplicam-se a executores auto-hospedados. Para obter mais informações, consulte "[Sobre os executores auto-hospedados](/actions/hosting-your-own-runners/about-self-hosted-runners/#usage-limits)."
@@ -94,7 +94,7 @@ Para obter mais informações, consulte:
## Desativar ou limitar {% data variables.product.prodname_actions %} para o seu repositório ou organização
-{% data reusables.github-actions.disabling-github-actions %}
+{% data reusables.actions.disabling-github-actions %}
Para obter mais informações, consulte:
- "[Gerenciar configurações de {% data variables.product.prodname_actions %} para um repositório](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository)"
diff --git a/translations/pt-BR/content/actions/managing-workflow-runs/removing-workflow-artifacts.md b/translations/pt-BR/content/actions/managing-workflow-runs/removing-workflow-artifacts.md
index 182b34be6b94..1c632ca2cd0e 100644
--- a/translations/pt-BR/content/actions/managing-workflow-runs/removing-workflow-artifacts.md
+++ b/translations/pt-BR/content/actions/managing-workflow-runs/removing-workflow-artifacts.md
@@ -22,7 +22,7 @@ shortTitle: Remover artefatos de fluxo de trabalho
{% data reusables.repositories.permissions-statement-write %}
-{% data reusables.github-actions.artifact-log-retention-statement %}
+{% data reusables.actions.artifact-log-retention-statement %}
{% data reusables.repositories.navigate-to-repo %}
{% data reusables.repositories.actions-tab %}
diff --git a/translations/pt-BR/content/actions/migrating-to-github-actions/migrating-from-travis-ci-to-github-actions.md b/translations/pt-BR/content/actions/migrating-to-github-actions/migrating-from-travis-ci-to-github-actions.md
index 439f3cff0f7f..aa5e457a62a1 100644
--- a/translations/pt-BR/content/actions/migrating-to-github-actions/migrating-from-travis-ci-to-github-actions.md
+++ b/translations/pt-BR/content/actions/migrating-to-github-actions/migrating-from-travis-ci-to-github-actions.md
@@ -179,7 +179,7 @@ git:
O Travis CI e {% data variables.product.prodname_actions %} podem adicionar variáveis de ambiente personalizadas a uma matriz de teste, que permite que você faça referência à variável em uma etapa posterior.
-Em {% data variables.product.prodname_actions %}, você pode usar a chave `incluir` para adicionar variáveis de ambiente personalizadas a uma matriz. {% data reusables.github-actions.matrix-variable-example %}
+Em {% data variables.product.prodname_actions %}, você pode usar a chave `incluir` para adicionar variáveis de ambiente personalizadas a uma matriz. {% data reusables.actions.matrix-variable-example %}
## Principais recursos em {% data variables.product.prodname_actions %}
diff --git a/translations/pt-BR/content/actions/monitoring-and-troubleshooting-workflows/about-monitoring-and-troubleshooting.md b/translations/pt-BR/content/actions/monitoring-and-troubleshooting-workflows/about-monitoring-and-troubleshooting.md
index 0649487c2a39..18328db5699a 100644
--- a/translations/pt-BR/content/actions/monitoring-and-troubleshooting-workflows/about-monitoring-and-troubleshooting.md
+++ b/translations/pt-BR/content/actions/monitoring-and-troubleshooting-workflows/about-monitoring-and-troubleshooting.md
@@ -18,7 +18,7 @@ miniTocMaxHeadingLevel: 3
{% if github-runner-dashboard %}
### Monitorando os seus trabalhos atuais na sua organização ou empresa
-{% data reusables.github-actions.github-hosted-runners-check-concurrency %}
+{% data reusables.actions.github-hosted-runners-check-concurrency %}
{% endif %}
diff --git a/translations/pt-BR/content/actions/monitoring-and-troubleshooting-workflows/enabling-debug-logging.md b/translations/pt-BR/content/actions/monitoring-and-troubleshooting-workflows/enabling-debug-logging.md
index 8a8a537a0574..e336b27b1fc3 100644
--- a/translations/pt-BR/content/actions/monitoring-and-troubleshooting-workflows/enabling-debug-logging.md
+++ b/translations/pt-BR/content/actions/monitoring-and-troubleshooting-workflows/enabling-debug-logging.md
@@ -15,12 +15,12 @@ versions:
Esses registros adicionais são habilitados pela definição dos segredos no repositório que contém o fluxo de trabalho. Portanto, aplicam-se os mesmos requisitos de permissão:
-- {% data reusables.github-actions.permissions-statement-secrets-repository %}
+- {% data reusables.actions.permissions-statement-secrets-repository %}
{% ifversion fpt or ghes > 3.0 or ghae or ghec %}
-- {% data reusables.github-actions.permissions-statement-secrets-environment %}
+- {% data reusables.actions.permissions-statement-secrets-environment %}
{% endif %}
-- {% data reusables.github-actions.permissions-statement-secrets-organization %}
-- {% data reusables.github-actions.permissions-statement-secrets-api %}
+- {% data reusables.actions.permissions-statement-secrets-organization %}
+- {% data reusables.actions.permissions-statement-secrets-api %}
Para obter mais informações sobre segredos de configuração, consulte "[Criar e usar segredos criptografados](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)".
diff --git a/translations/pt-BR/content/actions/monitoring-and-troubleshooting-workflows/using-workflow-run-logs.md b/translations/pt-BR/content/actions/monitoring-and-troubleshooting-workflows/using-workflow-run-logs.md
index 596b0bba63d3..6222711b9178 100644
--- a/translations/pt-BR/content/actions/monitoring-and-troubleshooting-workflows/using-workflow-run-logs.md
+++ b/translations/pt-BR/content/actions/monitoring-and-troubleshooting-workflows/using-workflow-run-logs.md
@@ -19,7 +19,7 @@ Se a execução estiver concluída, será possível ver se o resultado teve êxi
O {% data variables.product.prodname_actions %} usa a API de Verificação para mostrar os status, resultados e logs de um fluxo de trabalho. O {% data variables.product.prodname_dotcom %} cria um novo conjunto de verificações para cada execução de fluxo de trabalho. O conjunto de verificações contêm uma execução de verificação para cada trabalho no fluxo de trabalho, e cada trabalho inclui etapas. As ações do {% data variables.product.prodname_actions %} são executadas como etapas no fluxo de trabalho. Para obter mais informações sobre a API de verificações, consulte "[Verificações](/rest/reference/checks)".
-{% data reusables.github-actions.invalid-workflow-files %}
+{% data reusables.actions.invalid-workflow-files %}
## Exibir logs para diagnosticar falhas
diff --git a/translations/pt-BR/content/actions/publishing-packages/publishing-docker-images.md b/translations/pt-BR/content/actions/publishing-packages/publishing-docker-images.md
index d21df99eb28a..34e2642be96b 100644
--- a/translations/pt-BR/content/actions/publishing-packages/publishing-docker-images.md
+++ b/translations/pt-BR/content/actions/publishing-packages/publishing-docker-images.md
@@ -50,7 +50,7 @@ Neste guia, usaremos a ação `build-push-action` do Docker para criar a imagem
## Publicar imagens no Docker Hub
-{% data reusables.github-actions.release-trigger-workflow %}
+{% data reusables.actions.release-trigger-workflow %}
No exemplo de fluxo de trabalho, nós usamos as ações de login do Docker `login-action` e `build-push-action` para construir a imagem do Docker e, se a construção for bem-sucedida, faça push da imagem construída para o Docker Hub.
@@ -110,7 +110,7 @@ O fluxo de trabalho acima verifica o repositório {% data variables.product.prod
## Publicar imagens em {% data variables.product.prodname_registry %}
-{% data reusables.github-actions.release-trigger-workflow %}
+{% data reusables.actions.release-trigger-workflow %}
No exemplo abaixo, usamos a `login-action do Docker`{% ifversion fpt or ghec %}, `metadados-ação`,{% endif %} e ações de `build-push-action` para construir a imagem Docker e, se a criação for bem-sucedida, faça push da imagem criada para {% data variables.product.prodname_registry %}.
diff --git a/translations/pt-BR/content/actions/publishing-packages/publishing-java-packages-with-gradle.md b/translations/pt-BR/content/actions/publishing-packages/publishing-java-packages-with-gradle.md
index d4617e623079..3ce51a06479f 100644
--- a/translations/pt-BR/content/actions/publishing-packages/publishing-java-packages-with-gradle.md
+++ b/translations/pt-BR/content/actions/publishing-packages/publishing-java-packages-with-gradle.md
@@ -23,7 +23,7 @@ shortTitle: Pacotes do Java com Gradle
## Introdução
-{% data reusables.github-actions.publishing-java-packages-intro %}
+{% data reusables.actions.publishing-java-packages-intro %}
## Pré-requisitos
@@ -104,7 +104,7 @@ jobs:
MAVEN_PASSWORD: {% raw %}${{ secrets.OSSRH_TOKEN }}{% endraw %}
```
-{% data reusables.github-actions.gradle-workflow-steps %}
+{% data reusables.actions.gradle-workflow-steps %}
1. Executa a ação [`gradle/gradle-build-action`](https://github.com/gradle/gradle-build-action) com o argumento `publicar` para fazer uma publicação no repositório do Maven `OSSRH`. A variável de ambiente `MAVEN_USERNAME` será definida com o conteúdo do seu segredo `OSSRH_USERNAME`, e a variável de ambiente `MAVEN_PASSWORD` será definida com o conteúdo do seu segredo `OSSRH_TOKEN`.
Para obter mais informações sobre o uso de segredos no seu fluxo de trabalho, consulte "[Criando e usando segredos encriptados](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)".
@@ -115,7 +115,7 @@ Cada vez que você criar uma nova versão, você poderá acionar um fluxo de tra
Você pode definir um novo repositório do Maven no bloco de publicação do _build.gradle_ que aponta para {% data variables.product.prodname_registry %}. Nessa configuração do repositório, também é possível aproveitar as variáveis de ambiente definidas na execução do fluxo de trabalho de CI. Você pode usar a variável de ambiente `GITHUB_ACTOR` como um nome de usuário e você pode definir a variável de ambiente `GITHUB_TOKEN` com seu segredo `GITHUB_TOKEN`.
-{% data reusables.github-actions.github-token-permissions %}
+{% data reusables.actions.github-token-permissions %}
Por exemplo, se sua organização é denominado "octocat" e seu repositório é denominado de "hello-world", a configuração do {% data variables.product.prodname_registry %} no _build.gradle_ será parecida ao exemplo abaixo.
@@ -174,7 +174,7 @@ jobs:
GITHUB_TOKEN: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
```
-{% data reusables.github-actions.gradle-workflow-steps %}
+{% data reusables.actions.gradle-workflow-steps %}
1. Executa a ação [`grades/gradle-build-action`](https://github.com/gradle/gradle-build-action) com o argumento `publicar` para publicar em {% data variables.product.prodname_registry %}. A variável de ambiente `GITHUB_TOKEN` será definida com o conteúdo do segredo `GITHUB_TOKEN`. {% ifversion fpt or ghes > 3.1 or ghae or ghec %}A chave de `permissões` especifica o acesso que o segredo `GITHUB_TOKEN` permitirá.{% endif %}
Para obter mais informações sobre o uso de segredos no seu fluxo de trabalho, consulte "[Criando e usando segredos encriptados](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)".
@@ -255,7 +255,7 @@ jobs:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}{% endraw %}
```
-{% data reusables.github-actions.gradle-workflow-steps %}
+{% data reusables.actions.gradle-workflow-steps %}
1. Executa a ação [`grades/gradle-build`](https://github.com/gradle/gradle-build-action) com o argumento `publicar` para publicar no repositório do Maven `OSSRH` e em {% data variables.product.prodname_registry %}. A variável de ambiente `MAVEN_USERNAME` será definida com o conteúdo do seu segredo `OSSRH_USERNAME`, e a variável de ambiente `MAVEN_PASSWORD` será definida com o conteúdo do seu segredo `OSSRH_TOKEN`. A variável de ambiente `GITHUB_TOKEN` será definida com o conteúdo do segredo `GITHUB_TOKEN`. {% ifversion fpt or ghes > 3.1 or ghae or ghec %}A chave de `permissões` especifica o acesso que o segredo `GITHUB_TOKEN` permitirá.{% endif %}
Para obter mais informações sobre o uso de segredos no seu fluxo de trabalho, consulte "[Criando e usando segredos encriptados](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)".
diff --git a/translations/pt-BR/content/actions/publishing-packages/publishing-java-packages-with-maven.md b/translations/pt-BR/content/actions/publishing-packages/publishing-java-packages-with-maven.md
index 2f38d9f9de61..3774e1abcae5 100644
--- a/translations/pt-BR/content/actions/publishing-packages/publishing-java-packages-with-maven.md
+++ b/translations/pt-BR/content/actions/publishing-packages/publishing-java-packages-with-maven.md
@@ -23,7 +23,7 @@ shortTitle: Pacotes Java com Maven
## Introdução
-{% data reusables.github-actions.publishing-java-packages-intro %}
+{% data reusables.actions.publishing-java-packages-intro %}
## Pré-requisitos
@@ -105,7 +105,7 @@ Este fluxo de trabalho executa os seguintes passos:
1. Verifica uma cópia do repositório do projeto.
1. Configura o Java JDK e o arquivo _settings.xml_ do Maven para adicionar autenticação ao repositório `ossrh` usando as variáveis de ambiente `MAVEN_USERNAME` e `MAVEN_PASSWORD`.
-1. {% data reusables.github-actions.publish-to-maven-workflow-step %}
+1. {% data reusables.actions.publish-to-maven-workflow-step %}
Para obter mais informações sobre o uso de segredos no seu fluxo de trabalho, consulte "[Criando e usando segredos encriptados](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)".
@@ -115,7 +115,7 @@ Cada vez que você criar uma nova versão, você poderá acionar um fluxo de tra
Neste fluxo de trabalho, você pode usar a ação `setup-java`. Esta ação instala a versão determinada do JDK no `PATH`, e também configura _settings.xml_ do Maven para a publicação {% data variables.product.prodname_registry %}. O _settings.xml_ gerado define a autenticação para um servidor com um `id` do `github`, usando a variável de ambiente `GITHUB_ACTOR` como o nome de usuário e a variável de ambiente `GITHUB_TOKEN` como a senha. A variável de ambiente `GITHUB_TOKEN` foi atribuída ao valor do segredo especial `GITHUB_TOKEN`.
-{% data reusables.github-actions.github-token-permissions %}
+{% data reusables.actions.github-token-permissions %}
Para um projeto baseado no Maven, você pode usar essas configurações ao criar um repositório de distribuição no seu arquivo _pom.xml_ com um `id` do `github` que aponta para seu ponto final {% data variables.product.prodname_registry %}.
@@ -165,7 +165,7 @@ Este fluxo de trabalho executa os seguintes passos:
1. Verifica uma cópia do repositório do projeto.
1. Configura o Java JDK e também configura automaticamente o arquivo _settings.xml_ do Maven para adicionar autenticação para o repositório do `github` do Maven para usar a variável de ambiente `GITHUB_TOKEN`.
-1. {% data reusables.github-actions.publish-to-packages-workflow-step %}
+1. {% data reusables.actions.publish-to-packages-workflow-step %}
Para obter mais informações sobre o uso de segredos no seu fluxo de trabalho, consulte "[Criando e usando segredos encriptados](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)".
@@ -218,8 +218,8 @@ Este fluxo de trabalho executa os seguintes passos:
1. Verifica uma cópia do repositório do projeto.
1. Chama `setup-java` pela primeira vez. Isso configura o arquivo _settings.xml_ do Maven para o repositório `ossrh` e define as opções de autenticação para variáveis de ambiente definidas na próxima etapa.
-1. {% data reusables.github-actions.publish-to-maven-workflow-step %}
+1. {% data reusables.actions.publish-to-maven-workflow-step %}
1. Chama `setup-java` pela segunda vez. Isso configura automaticamente o arquivo _settings.xml_ do Maven para {% data variables.product.prodname_registry %}.
-1. {% data reusables.github-actions.publish-to-packages-workflow-step %}
+1. {% data reusables.actions.publish-to-packages-workflow-step %}
Para obter mais informações sobre o uso de segredos no seu fluxo de trabalho, consulte "[Criando e usando segredos encriptados](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)".
diff --git a/translations/pt-BR/content/actions/publishing-packages/publishing-nodejs-packages.md b/translations/pt-BR/content/actions/publishing-packages/publishing-nodejs-packages.md
index fc23ed841798..2bd5117c7d05 100644
--- a/translations/pt-BR/content/actions/publishing-packages/publishing-nodejs-packages.md
+++ b/translations/pt-BR/content/actions/publishing-packages/publishing-nodejs-packages.md
@@ -43,7 +43,7 @@ Você também pode achar útil ter um entendimento básico do seguinte:
Os campos `nome` e `versão` no arquivo *package.json* cria um identificador único que os registros usam para vincular seu pacote a um registro. Você pode adicionar um resumo para página de listagem do pacote ao incluir um campo `descrição` no arquivo *package.json*. Para obter mais informações, consulte "[Criando um pacote package.json](https://docs.npmjs.com/creating-a-package-json-file)" e "[Criando módulos Node.js](https://docs.npmjs.com/creating-node-js-modules)" na documentação do npm.
-Quando um arquivo *.npmrc* local existe e tem um valor de `registro` especificado, o comando `publicação do npm` usa o registro configurado no arquivo *.npmrc*. {% data reusables.github-actions.setup-node-intro %}
+Quando um arquivo *.npmrc* local existe e tem um valor de `registro` especificado, o comando `publicação do npm` usa o registro configurado no arquivo *.npmrc*. {% data reusables.actions.setup-node-intro %}
Você pode especificar a versão do Node.js instalada no executor usando a ação `setup-node`.
@@ -115,7 +115,7 @@ No entanto, se você fornecer a chave `repositório`, o repositório nessa chave
### Efetuar a autenticação no repositório de destino
-Para realizar operações autenticadas no registro do {% data variables.product.prodname_registry %} em seu fluxo de trabalho, você pode usar o `GITHUB_TOKEN`. {% data reusables.github-actions.github-token-permissions %}
+Para realizar operações autenticadas no registro do {% data variables.product.prodname_registry %} em seu fluxo de trabalho, você pode usar o `GITHUB_TOKEN`. {% data reusables.actions.github-token-permissions %}
Se você quiser publicar seu pacote em um repositório diferente, você deverá usar um token de acesso pessoal (PAT) que tenha permissão para escrever pacotes no repositório de destino. Para obter mais informações, consulte "[Criar um token de acesso pessoal](/github/authenticating-to-github/creating-a-personal-access-token)" e "[Segredos criptografados](/actions/reference/encrypted-secrets)".
diff --git a/translations/pt-BR/content/actions/security-guides/automatic-token-authentication.md b/translations/pt-BR/content/actions/security-guides/automatic-token-authentication.md
index 8e20621e7d71..467ae7a0e182 100644
--- a/translations/pt-BR/content/actions/security-guides/automatic-token-authentication.md
+++ b/translations/pt-BR/content/actions/security-guides/automatic-token-authentication.md
@@ -39,11 +39,11 @@ Você pode usar o `GITHUB_TOKEN` ao usar a sintaxe padrão para fazer referênci
{% endnote %}
{% endif %}
-{% data reusables.github-actions.actions-do-not-trigger-workflows %}
+{% data reusables.actions.actions-do-not-trigger-workflows %}
### Exemplo 1: Passar o `GITHUB_TOKEN` como uma entrada
-{% data reusables.github-actions.github_token-input-example %}
+{% data reusables.actions.github_token-input-example %}
### Exemplo 2: chamando a API REST
@@ -121,7 +121,7 @@ Você pode ver as permissões que o `GITHUB_TOKEN` tem para uma tarefa específi
Você pode usar a chave de `permissões` no seu arquivo de fluxo de trabalho para modificar as permissões para o `GITHUB_TOKEN` para um fluxo de trabalho inteiro ou para trabalhos individuais. Isso permite que você configure as permissões mínimas necessárias para um fluxo de trabalho ou trabalho. Quando a chave `permissions` for usada, todas as permissões não especificadas são configuradas como sem acesso, com exceção do escopo de `metadados`, que sempre recebe acesso de leitura.
-{% data reusables.github-actions.forked-write-permission %}
+{% data reusables.actions.forked-write-permission %}
Os dois exemplos de fluxo de trabalho anteriores neste artigo mostram a chave de `permissões` usada no nível de fluxo de trabalho e no nível de trabalho. Em [Exemplo 1](#example-1-passing-the-github_token-as-an-input) as duas permissões são especificadas para todo o fluxo de trabalho. No [Exemplo 2](#example-2-calling-the-rest-api) de acesso de gravação é concedido para um único escopo para um único trabalho.
diff --git a/translations/pt-BR/content/actions/security-guides/encrypted-secrets.md b/translations/pt-BR/content/actions/security-guides/encrypted-secrets.md
index 01feec31815d..1a2a66563b7b 100644
--- a/translations/pt-BR/content/actions/security-guides/encrypted-secrets.md
+++ b/translations/pt-BR/content/actions/security-guides/encrypted-secrets.md
@@ -21,7 +21,7 @@ versions:
Os segredos são variáveis de ambiente criptografadas que você cria em uma organização{% ifversion fpt or ghes > 3.0 or ghae or ghec %}, repositório ou ambiente do repositório{% else %} ou repositório{% endif %}. Os segredos que você cria estão disponíveis para utilização nos fluxos de trabalho em {% data variables.product.prodname_actions %}. {% data variables.product.prodname_dotcom %} usa uma [caixa selada libsodium](https://libsodium.gitbook.io/doc/public-key_cryptography/sealed_boxes) para ajudar a garantir que os segredos sejam criptografados antes de chegarem a {% data variables.product.prodname_dotcom %} e permaneçam criptografados até que você os use em um fluxo de trabalho.
-{% data reusables.github-actions.secrets-org-level-overview %}
+{% data reusables.actions.secrets-org-level-overview %}
{% ifversion fpt or ghes > 3.0 or ghae or ghec %}
Para segredos armazenados no nível do ambiente, você pode habilitar os revisores necessários para controlar o acesso aos segredos. Um trabalho de fluxo de trabalho não pode acessar segredos de ambiente até que a aprovação seja concedida por aprovadores necessários.
@@ -53,7 +53,7 @@ Para disponibilizar um segredo para uma ação, você deve configurá-lo como um
Você pode usar e ler segredos encriptados em um arquivo de fluxo de trabalho se tiver permissão para editar o arquivo. Para obter mais informações, consulte "[Permissões de acesso em {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/access-permissions-on-github)."
-{% data reusables.github-actions.secrets-redaction-warning %}
+{% data reusables.actions.secrets-redaction-warning %}
{% ifversion fpt or ghes > 3.0 or ghae or ghec %}
Os segredos da organização e do repositório são lidos quando uma execução de fluxo de trabalho é enfileirada e os segredos de ambiente são lidos quando um trabalho que faz referência ao ambiente é iniciado.
@@ -73,13 +73,13 @@ Ao gerar credenciais, recomendamos que você conceda as permissões mínimas pos
## Criar segredos encriptados para um repositório
-{% data reusables.github-actions.permissions-statement-secrets-repository %}
+{% data reusables.actions.permissions-statement-secrets-repository %}
{% webui %}
{% data reusables.repositories.navigate-to-repo %}
{% data reusables.repositories.sidebar-settings %}
-{% data reusables.github-actions.sidebar-secret %}
+{% data reusables.actions.sidebar-secret %}
1. Clique em **Novo segredo do repositório**.
1. Digite um nome para o seu segredo na caixa de entrada **Nome**.
1. Insira o valor para o seu segredo.
@@ -113,13 +113,13 @@ Para listar todos os segredos para o repositório, use o subcomando da lista `gh
## Criar segredos criptografados para um ambiente
-{% data reusables.github-actions.permissions-statement-secrets-environment %}
+{% data reusables.actions.permissions-statement-secrets-environment %}
{% webui %}
{% data reusables.repositories.navigate-to-repo %}
{% data reusables.repositories.sidebar-settings %}
-{% data reusables.github-actions.sidebar-environment %}
+{% data reusables.actions.sidebar-environment %}
1. Clique no ambiente ao qual você deseja adicionar um segredo.
2. Em **Segredos do ambiente**, clique em **Adicionar segredo**.
3. Digite um nome para o seu segredo na caixa de entrada **Nome**.
@@ -150,13 +150,13 @@ gh secret list --env environment-name
Ao criar um segredo em uma organização, você pode usar uma política para limitar quais repositórios podem acessar esse segredo. Por exemplo, você pode conceder acesso a todos os repositórios ou limitar o acesso a apenas repositórios privados ou a uma lista específica de repositórios.
-{% data reusables.github-actions.permissions-statement-secrets-organization %}
+{% data reusables.actions.permissions-statement-secrets-organization %}
{% webui %}
{% data reusables.organizations.navigate-to-org %}
{% data reusables.organizations.org_settings %}
-{% data reusables.github-actions.sidebar-secret %}
+{% data reusables.actions.sidebar-secret %}
1. Clique em **Novo segredo da organização**.
1. Digite um nome para o seu segredo na caixa de entrada **Nome**.
1. Insira o **Valor** para o seu segredo.
@@ -209,7 +209,7 @@ Você pode verificar quais políticas de acesso são aplicadas a um segredo na s
{% data reusables.organizations.navigate-to-org %}
{% data reusables.organizations.org_settings %}
-{% data reusables.github-actions.sidebar-secret %}
+{% data reusables.actions.sidebar-secret %}
1. A lista de segredos inclui quaisquer permissões e políticas configuradas. Por exemplo: 
1. Para obter mais detalhes sobre as permissões configuradas para cada segredo, clique em **Atualizar**.
diff --git a/translations/pt-BR/content/actions/using-containerized-services/about-service-containers.md b/translations/pt-BR/content/actions/using-containerized-services/about-service-containers.md
index ebea9ba4c86f..23e06265df9a 100644
--- a/translations/pt-BR/content/actions/using-containerized-services/about-service-containers.md
+++ b/translations/pt-BR/content/actions/using-containerized-services/about-service-containers.md
@@ -25,7 +25,7 @@ Os contêineres de serviço são contêineres Docker que fornecem uma forma simp
Você pode configurar os contêineres de serviço para cada trabalho em um fluxo de trabalho. {% data variables.product.prodname_dotcom %} cria um novo contêiner Docker para cada serviço configurado no fluxo de trabalho e destrói o contêiner de serviço quando o trabalho é concluído. As etapas em um trabalho podem comunicar-se com todos os contêineres de serviço que fazem parte do mesmo trabalho.
-{% data reusables.github-actions.docker-container-os-support %}
+{% data reusables.actions.docker-container-os-support %}
## Comunicar-se com os contêineres de serviço
diff --git a/translations/pt-BR/content/actions/using-containerized-services/creating-postgresql-service-containers.md b/translations/pt-BR/content/actions/using-containerized-services/creating-postgresql-service-containers.md
index cba7d4398b20..10b57ce2ee73 100644
--- a/translations/pt-BR/content/actions/using-containerized-services/creating-postgresql-service-containers.md
+++ b/translations/pt-BR/content/actions/using-containerized-services/creating-postgresql-service-containers.md
@@ -24,11 +24,11 @@ topics:
Este guia mostra exemplos de fluxo de trabalho que configuram um contêiner de serviço usando a imagem `postgres` do Docker Hub. O fluxo de trabalho executa um script que se conecta ao serviço do PostgreSQL, cria uma tabela e, em seguida, preenche-a com dados. Para testar se o fluxo de trabalho cria e preenche a tabela do PostgreSQL, o script imprime os dados da tabela para o console.
-{% data reusables.github-actions.docker-container-os-support %}
+{% data reusables.actions.docker-container-os-support %}
## Pré-requisitos
-{% data reusables.github-actions.service-container-prereqs %}
+{% data reusables.actions.service-container-prereqs %}
Também pode ser útil ter um entendimento básico de YAML, a sintaxe para {% data variables.product.prodname_actions %} e PostgreSQL. Para obter mais informações, consulte:
@@ -37,9 +37,9 @@ Também pode ser útil ter um entendimento básico de YAML, a sintaxe para {% da
## Executar trabalhos em contêineres
-{% data reusables.github-actions.container-jobs-intro %}
+{% data reusables.actions.container-jobs-intro %}
-{% data reusables.github-actions.copy-workflow-file %}
+{% data reusables.actions.copy-workflow-file %}
{% raw %}
```yaml{:copy}
@@ -95,9 +95,9 @@ jobs:
### Configurar o trabalho executor
-{% data reusables.github-actions.service-container-host %}
+{% data reusables.actions.service-container-host %}
-{% data reusables.github-actions.postgres-label-description %}
+{% data reusables.actions.postgres-label-description %}
```yaml{:copy}
trabalhos:
@@ -127,7 +127,7 @@ trabalhos:
### Configurar as etapas
-{% data reusables.github-actions.service-template-steps %}
+{% data reusables.actions.service-template-steps %}
```yaml{:copy}
steps:
@@ -153,7 +153,7 @@ steps:
POSTGRES_PORT: 5432
```
-{% data reusables.github-actions.postgres-environment-variables %}
+{% data reusables.actions.postgres-environment-variables %}
O nome do host do serviço do PostgreSQL é a etiqueta que você configurou no seu fluxo de trabalho, nesse caso, `postgres`. Uma vez que os contêineres do Docker na mesma rede da ponte definida pelo usuário abrem todas as portas por padrão, você poderá acessar o contêiner de serviço na porta-padrão 5432 do PostgreSQL.
@@ -161,7 +161,7 @@ O nome do host do serviço do PostgreSQL é a etiqueta que você configurou no s
Ao executar um trabalho diretamente na máquina executora, você deverá mapear as portas no contêiner de serviço com as portas no host do Docker. Você pode acessar os contêineres de serviço do host do Docker usando `localhost` e o número da porta do host do Docker.
-{% data reusables.github-actions.copy-workflow-file %}
+{% data reusables.actions.copy-workflow-file %}
{% raw %}
```yaml{:copy}
@@ -219,9 +219,9 @@ jobs:
### Configurar o trabalho executor
-{% data reusables.github-actions.service-container-host-runner %}
+{% data reusables.actions.service-container-host-runner %}
-{% data reusables.github-actions.postgres-label-description %}
+{% data reusables.actions.postgres-label-description %}
O fluxo de trabalho mapeia a porta 5432 no contêiner de serviço do PostgreSQL com o host do Docker. Para obter mais informações sobre a palavra-chave `portas`, consulte "[Sobre contêineres de serviço](/actions/automating-your-workflow-with-github-actions/about-service-containers#mapping-docker-host-and-service-container-ports)".
@@ -254,7 +254,7 @@ trabalhos:
### Configurar as etapas
-{% data reusables.github-actions.service-template-steps %}
+{% data reusables.actions.service-template-steps %}
```yaml{:copy}
steps:
@@ -280,9 +280,9 @@ steps:
POSTGRES_PORT: 5432
```
-{% data reusables.github-actions.postgres-environment-variables %}
+{% data reusables.actions.postgres-environment-variables %}
-{% data reusables.github-actions.service-container-localhost %}
+{% data reusables.actions.service-container-localhost %}
## Testar o contêiner de serviço do PostgreSQL
@@ -290,7 +290,7 @@ Você pode testar o seu fluxo de trabalho usando o seguinte script, que se conec
Você pode modificar o *client.js* para incluir qualquer operação do PostgreSQL exigida pelo seu fluxo de trabalho. Neste exemplo, o script conecta-se ao serviço do PostgreSQL, adiciona uma tabela ao banco de dados `postgres`, insere alguns dados de espaço reservado e recupera os dados.
-{% data reusables.github-actions.service-container-add-script %}
+{% data reusables.actions.service-container-add-script %}
```javascript{:copy}
const { Client } = require('pg');
diff --git a/translations/pt-BR/content/actions/using-containerized-services/creating-redis-service-containers.md b/translations/pt-BR/content/actions/using-containerized-services/creating-redis-service-containers.md
index 31ee3a57221b..e9933158f095 100644
--- a/translations/pt-BR/content/actions/using-containerized-services/creating-redis-service-containers.md
+++ b/translations/pt-BR/content/actions/using-containerized-services/creating-redis-service-containers.md
@@ -24,11 +24,11 @@ topics:
Este guia mostra os exemplos do seu fluxo de trabalho que configuram um contêiner de serviço usando a imagem `redis` do Docker Hub. O fluxo de trabalho executa um script para criar um cliente Redis e preencher os dados do cliente. Para testar se o fluxo de trabalho cria e preenche o cliente Redis, o script imprime os dados do cliente no console.
-{% data reusables.github-actions.docker-container-os-support %}
+{% data reusables.actions.docker-container-os-support %}
## Pré-requisitos
-{% data reusables.github-actions.service-container-prereqs %}
+{% data reusables.actions.service-container-prereqs %}
Também pode ser útil ter um entendimento básico de YAML, a sintaxe para {% data variables.product.prodname_actions %} e Redis. Para obter mais informações, consulte:
@@ -37,9 +37,9 @@ Também pode ser útil ter um entendimento básico de YAML, a sintaxe para {% da
## Executar trabalhos em contêineres
-{% data reusables.github-actions.container-jobs-intro %}
+{% data reusables.actions.container-jobs-intro %}
-{% data reusables.github-actions.copy-workflow-file %}
+{% data reusables.actions.copy-workflow-file %}
{% raw %}
```yaml{:copy}
@@ -92,9 +92,9 @@ trabalhos:
### Configurar o trabalho do contêiner
-{% data reusables.github-actions.service-container-host %}
+{% data reusables.actions.service-container-host %}
-{% data reusables.github-actions.redis-label-description %}
+{% data reusables.actions.redis-label-description %}
```yaml{:copy}
trabalhos:
@@ -121,7 +121,7 @@ trabalhos:
### Configurar as etapas
-{% data reusables.github-actions.service-template-steps %}
+{% data reusables.actions.service-template-steps %}
```yaml{:copy}
etapas:
@@ -146,7 +146,7 @@ etapas:
REDIS_PORT: 6379
```
-{% data reusables.github-actions.redis-environment-variables %}
+{% data reusables.actions.redis-environment-variables %}
O nome do host do serviço Redis é a etiqueta que você configurou no seu fluxo de trabalho, nesse caso `redis`. Uma vez que os contêineres do Docker na mesma rede da ponte definida pelo usuário abrem todas as portas por padrão, você poderá acessar o contêiner de serviço na porta-padrão 6379 do Redis.
@@ -154,7 +154,7 @@ O nome do host do serviço Redis é a etiqueta que você configurou no seu fluxo
Ao executar um trabalho diretamente na máquina executora, você deverá mapear as portas no contêiner de serviço com as portas no host do Docker. Você pode acessar os contêineres de serviço do host do Docker usando `localhost` e o número da porta do host do Docker.
-{% data reusables.github-actions.copy-workflow-file %}
+{% data reusables.actions.copy-workflow-file %}
{% raw %}
```yaml{:copy}
@@ -209,9 +209,9 @@ trabalhos:
### Configurar o trabalho executor
-{% data reusables.github-actions.service-container-host-runner %}
+{% data reusables.actions.service-container-host-runner %}
-{% data reusables.github-actions.redis-label-description %}
+{% data reusables.actions.redis-label-description %}
O fluxo de trabalho mapeia a porta 6379 no contêiner de serviço do Redis com o host do Docker. Para obter mais informações sobre a palavra-chave `portas`, consulte "[Sobre contêineres de serviço](/actions/automating-your-workflow-with-github-actions/about-service-containers#mapping-docker-host-and-service-container-ports)".
@@ -241,7 +241,7 @@ trabalhos:
### Configurar as etapas
-{% data reusables.github-actions.service-template-steps %}
+{% data reusables.actions.service-template-steps %}
```yaml{:copy}
etapas:
@@ -267,9 +267,9 @@ etapas:
REDIS_PORT: 6379
```
-{% data reusables.github-actions.redis-environment-variables %}
+{% data reusables.actions.redis-environment-variables %}
-{% data reusables.github-actions.service-container-localhost %}
+{% data reusables.actions.service-container-localhost %}
## Testar o contêiner de serviço Redis
@@ -277,7 +277,7 @@ Você pode testar o seu fluxo de trabalho usando o script a seguir, que cria um
Você pode modificar o *client.js* para incluir qualquer operação necessária para o seu fluxo de trabalho. Neste exemplo, o script cria a instância do cliente Redis, cria uma tabela, adiciona dados de espaços reservados e, em seguida, recupera os dados.
-{% data reusables.github-actions.service-container-add-script %}
+{% data reusables.actions.service-container-add-script %}
```javascript{:copy}
const redis = require("redis");
diff --git a/translations/pt-BR/content/actions/using-github-hosted-runners/about-github-hosted-runners.md b/translations/pt-BR/content/actions/using-github-hosted-runners/about-github-hosted-runners.md
index e111f25eccb0..5465c67da074 100644
--- a/translations/pt-BR/content/actions/using-github-hosted-runners/about-github-hosted-runners.md
+++ b/translations/pt-BR/content/actions/using-github-hosted-runners/about-github-hosted-runners.md
@@ -29,7 +29,7 @@ Você pode especificar o tipo de executor para cada trabalho em um fluxo de trab
{% ifversion not ghes %}
-{% data reusables.github-actions.runner-app-open-source %}
+{% data reusables.actions.runner-app-open-source %}
### Hosts da nuvem para os executores hospedados em {% data variables.product.prodname_dotcom %}
@@ -39,7 +39,7 @@ O {% data variables.product.prodname_dotcom %} hospeda executores do Linux e Win
### Continuidade do fluxo de trabalho para executores hospedados em {% data variables.product.prodname_dotcom %}
-{% data reusables.github-actions.runner-workflow-continuity %}
+{% data reusables.actions.runner-workflow-continuity %}
Além disso, se a execução do fluxo de trabalho entrar na fila com sucesso, mas não foi processado por um executor hospedado em {% data variables.product.prodname_dotcom %} dentro de 45 minutos, a execução do fluxo de trabalho na fila será descartada.
@@ -61,7 +61,7 @@ Especificação de hardware para máquinas virtuais do macOS:
- 14 GB de memória RAM
- 14 GB de espaço de disco SSD
-{% data reusables.github-actions.supported-github-runners %}
+{% data reusables.actions.supported-github-runners %}
Lista de registros de fluxo de trabalho do executor usado para executar um trabalho. Para obter mais informações, consulte "[Visualizar histórico de execução de fluxo de trabalho](/actions/managing-workflow-runs/viewing-workflow-run-history)".
diff --git a/translations/pt-BR/content/actions/using-github-hosted-runners/monitoring-your-current-jobs.md b/translations/pt-BR/content/actions/using-github-hosted-runners/monitoring-your-current-jobs.md
index c4f16b9cb576..8ef65516375d 100644
--- a/translations/pt-BR/content/actions/using-github-hosted-runners/monitoring-your-current-jobs.md
+++ b/translations/pt-BR/content/actions/using-github-hosted-runners/monitoring-your-current-jobs.md
@@ -13,8 +13,8 @@ shortTitle: Monitorando seus trabalhos atuais
Você pode obter uma lista de todos os trabalhos atualmente em execução em executores hospedados em {% data variables.product.prodname_dotcom %} na sua organização ou empresa.
-{% data reusables.github-actions.github-hosted-runners-navigate-to-repo-org-enterprise %}
-{% data reusables.github-actions.github-hosted-runners-table-entry %}
+{% data reusables.actions.github-hosted-runners-navigate-to-repo-org-enterprise %}
+{% data reusables.actions.github-hosted-runners-table-entry %}
1. Revise a seção "Trabalhos Ativos", que contém uma lista com todos os trabalhos em execução atualmente nos executores hospedados em {% data variables.product.prodname_dotcom %}.
@@ -25,6 +25,6 @@ Os executores hospedados em {% data variables.product.prodname_dotcom %} permite
O procedimento seguinte demonstra como verificar o número máximo de trabalhos simultâneos que pode ser executado.
-{% data reusables.github-actions.github-hosted-runners-navigate-to-repo-org-enterprise %}
-{% data reusables.github-actions.github-hosted-runners-table-entry %}
+{% data reusables.actions.github-hosted-runners-navigate-to-repo-org-enterprise %}
+{% data reusables.actions.github-hosted-runners-table-entry %}
1. Revise a seção "Uso de todos os trabalhos", que lista o número de trabalhos ativos e o número máximo de trabalhos que você pode executar. Neste exemplo, `9` trabalhos estão atualmente em execução em um total de `180`. 
diff --git a/translations/pt-BR/content/actions/using-jobs/using-concurrency.md b/translations/pt-BR/content/actions/using-jobs/using-concurrency.md
index 696f64d92438..4d731a9d55fb 100644
--- a/translations/pt-BR/content/actions/using-jobs/using-concurrency.md
+++ b/translations/pt-BR/content/actions/using-jobs/using-concurrency.md
@@ -20,5 +20,5 @@ miniTocMaxHeadingLevel: 4
{% if github-runner-dashboard %}
## Monitorando os seus trabalhos atuais na sua organização ou empresa
-{% data reusables.github-actions.github-hosted-runners-check-concurrency %}
+{% data reusables.actions.github-hosted-runners-check-concurrency %}
{% endif %}
diff --git a/translations/pt-BR/content/actions/using-workflows/events-that-trigger-workflows.md b/translations/pt-BR/content/actions/using-workflows/events-that-trigger-workflows.md
index 61112e8e66d8..c2546afc897c 100644
--- a/translations/pt-BR/content/actions/using-workflows/events-that-trigger-workflows.md
+++ b/translations/pt-BR/content/actions/using-workflows/events-that-trigger-workflows.md
@@ -37,7 +37,7 @@ Alguns eventos têm vários tipos de atividades. Para esses eventos, você pode
{% endnote %}
-{% data reusables.github-actions.branch-requirement %}
+{% data reusables.actions.branch-requirement %}
Executa o fluxo de trabalho quando as regras de proteção de branch no repositório do fluxo de trabalho são alteradas. Para obter mais informações sobre as regras de proteção de branches, consulte "[Sobre branches protegidos](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches)". Para informações sobre as APIs das regras de proteção de branch, consulte "[BranchProtectionRule](/graphql/reference/objects#branchprotectionrule)" na documentação da API do GraphQL ou "[Branches](/rest/reference/branches)" na documentação da API REST.
@@ -64,7 +64,7 @@ on:
{% endnote %}
-{% data reusables.github-actions.branch-requirement %}
+{% data reusables.actions.branch-requirement %}
Executa o fluxo de trabalho quando ocorre a atividade relacionada a uma execução de verificação. Uma execução de verificação é um teste individual que faz parte de um conjunto de verificações. Para obter informações, consulte "[Primeiros passos com a API de Verificações](/rest/guides/getting-started-with-the-checks-api)". Para informações sobre as APIs de verificação, consulte "[CheckRun](/graphql/reference/objects#checkrun)" na documentação da API do GraphQL ou "[Verificações](/rest/reference/checks#runs)" na documentação da API REST.
@@ -88,7 +88,7 @@ on:
{% endnote %}
-{% data reusables.github-actions.branch-requirement %}
+{% data reusables.actions.branch-requirement %}
{% note %}
@@ -133,7 +133,7 @@ on:
| ---------------------------------------------------------------------------------------- | ------------------ | ------------------------------ | ------------- |
| [`delete`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads/#delete) | n/a | Último commit no branch padrão | Branch padrão |
-{% data reusables.github-actions.branch-requirement %}
+{% data reusables.actions.branch-requirement %}
{% note %}
@@ -199,7 +199,7 @@ on:
{% endnote %}
-{% data reusables.github-actions.branch-requirement %}
+{% data reusables.actions.branch-requirement %}
{% data reusables.webhooks.discussions-webhooks-beta %}
@@ -225,7 +225,7 @@ on:
{% endnote %}
-{% data reusables.github-actions.branch-requirement %}
+{% data reusables.actions.branch-requirement %}
{% data reusables.webhooks.discussions-webhooks-beta %}
@@ -247,7 +247,7 @@ on:
| ------------------------------------------------------------------------------------------ | ------------------ | ------------------------------ | ------------- |
| [`bifurcação`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads/#fork) | n/a | Último commit no branch padrão | Branch padrão |
-{% data reusables.github-actions.branch-requirement %}
+{% data reusables.actions.branch-requirement %}
Executa o fluxo de trabalho quando alguém bifurca um repositório. Para obter informações sobre a API REST, consulte "[Criar uma bifurcação](/rest/reference/repos#create-a-fork)".
@@ -264,7 +264,7 @@ on:
| ---------------------------------------------------------------------------------------- | ------------------ | ------------------------------ | ------------- |
| [`gollum`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads/#gollum) | n/a | Último commit no branch padrão | Branch padrão |
-{% data reusables.github-actions.branch-requirement %}
+{% data reusables.actions.branch-requirement %}
Executa o fluxo de trabalho quando alguém cria ou atualiza uma página wiki. Para obter mais informações, consulte "[Sobre wikis](/communities/documenting-your-project-with-wikis/about-wikis)."
@@ -287,7 +287,7 @@ on:
{% endnote %}
-{% data reusables.github-actions.branch-requirement %}
+{% data reusables.actions.branch-requirement %}
Executa o fluxo de trabalho quando um problema ou comentário de pull request é criado, editado ou excluído. Para informação sobre as APIs de comentário de problema, consulte "[IssueComment](/graphql/reference/objects#issuecomment)" na documentação da API do GraphQL ou "[Comentários do problema](/developers/webhooks-and-events/webhook-events-and-payloads#issue_comment)" na documentação da API REST.
@@ -344,7 +344,7 @@ jobs:
{% endnote %}
-{% data reusables.github-actions.branch-requirement %}
+{% data reusables.actions.branch-requirement %}
Executa o fluxo de trabalho quando um problema no repositório do fluxo de trabalho é criado ou modificado. Para atividade relacionada a comentários em uma issue, use o evento [`issue_comment`](#issue_comment). Para obter mais informações sobre os problemas, consulte "[Sobre os problemas](/issues/tracking-your-work-with-issues/about-issues)". Para informações sobre as APIs do problema, consulte "[Problema](/graphql/reference/objects#issue)" na documentação da API do GraphQL ou "[Problemas](/rest/reference/issues)" na documentação da API REST.
@@ -368,7 +368,7 @@ on:
{% endnote %}
-{% data reusables.github-actions.branch-requirement %}
+{% data reusables.actions.branch-requirement %}
Executa o fluxo de trabalho quando uma etiqueta no repositório do fluxo de trabalho é criada ou modificada. Para obter mais informações sobre etiquetas, consulte "[Gerenciar etiquetas](/issues/using-labels-and-milestones-to-track-work/managing-labels)". Para obter informações sobre a API da etiqueta, consulte "[Etiqueta](/graphql/reference/objects#label)" na documentação da API do GraphQL ou "[Etiquetas](/rest/reference/issues#labels)" na documentação da API REST.
@@ -394,7 +394,7 @@ on:
{% endnote %}
-{% data reusables.github-actions.branch-requirement %}
+{% data reusables.actions.branch-requirement %}
Executa o fluxo de trabalho quando um marco no repositório do fluxo de trabalho é criado ou modificado. Para obter mais informações sobre marcos, consulte "[Sobre marcos](/issues/using-labels-and-milestones-to-track-work/about-milestones)". Para informações sobre as APIs do marco, consulte "[Marco](/graphql/reference/objects#milestone)" na documentação da API do GraphQL ou "[Marcos](/rest/reference/issues#milestones)" na documentação da API REST.
@@ -414,7 +414,7 @@ on:
| ------------------------------------------------------------------------------------------------ | ------------------ | ------------------------------ | ------------ |
| [`page_build`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads/#page_build) | n/a | Último commit no branch padrão | n/a |
-{% data reusables.github-actions.branch-requirement %}
+{% data reusables.actions.branch-requirement %}
Executa o fluxo de trabalho quando alguém faz push em um branch que é a fonte de publicação para {% data variables.product.prodname_pages %}, se o {% data variables.product.prodname_pages %} estiver habilitado no repositório. Para obter mais informações sobre fontes de publicação {% data variables.product.prodname_pages %}, consulte "[Configurando uma fonte de publicação para o site do GitHub Pages](/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site#choosing-a-publishing-source)". Para obter informações sobre a API REST, consulte "[Páginas](/rest/reference/repos#pages)".
@@ -437,7 +437,7 @@ on:
{% endnote %}
-{% data reusables.github-actions.branch-requirement %}
+{% data reusables.actions.branch-requirement %}
{% note %}
@@ -475,7 +475,7 @@ on:
{% endnote %}
-{% data reusables.github-actions.branch-requirement %}
+{% data reusables.actions.branch-requirement %}
{% note %}
@@ -513,7 +513,7 @@ on:
{% endnote %}
-{% data reusables.github-actions.branch-requirement %}
+{% data reusables.actions.branch-requirement %}
{% note %}
@@ -545,7 +545,7 @@ on:
| ----------------------------------------------------------------------------------------- | ------------------ | ------------------------------ | ------------- |
| [`público`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads/#public) | n/a | Último commit no branch padrão | Branch padrão |
-{% data reusables.github-actions.branch-requirement %}
+{% data reusables.actions.branch-requirement %}
Executa o fluxo de trabalho quando o repositório do fluxo de trabalho é alterado de privado para público. Para obter informações sobre a API REST, consulte "[Editar repositórios](/rest/reference/repos#edit)".
@@ -625,7 +625,7 @@ on:
{% note %}
-**Observação:** {% data reusables.github-actions.branch-paths-filter %} Por exemplo, o fluxo de trabalho a seguir será executado somente quando um pull request que inclui uma mudança para um arquivo (`.js`) do JavaScript for aberto em um branch cujo nome começa com `releases/`:
+**Note:** {% data reusables.actions.branch-paths-filter %} For example, the following workflow will only run when a pull request that includes a change to a JavaScript (`.js`) file is opened on a branch whose name starts with `releases/`:
```yaml
on:
@@ -670,7 +670,7 @@ on:
{% note %}
-**Observação:** {% data reusables.github-actions.branch-paths-filter %} Por exemplo, o fluxo de trabalho a seguir será executado somente quando um pull request que inclui uma mudança para um arquivo (`.js`) do JavaScript for aberto em um branch cujo nome começa com `releases/`:
+**Note:** {% data reusables.actions.branch-paths-filter %} For example, the following workflow will only run when a pull request that includes a change to a JavaScript (`.js`) file is opened on a branch whose name starts with `releases/`:
```yaml
on:
@@ -828,7 +828,7 @@ on:
{% note %}
-**Observação:** {% data reusables.github-actions.branch-paths-filter %} Por exemplo, o fluxo de trabalho a seguir será executado somente quando um pull request que inclui uma mudança para um arquivo (`.js`) do JavaScript for aberto em um branch cujo nome começa com `releases/`:
+**Note:** {% data reusables.actions.branch-paths-filter %} For example, the following workflow will only run when a pull request that includes a change to a JavaScript (`.js`) file is opened on a branch whose name starts with `releases/`:
```yaml
on:
@@ -873,7 +873,7 @@ on:
{% note %}
-**Observação:** {% data reusables.github-actions.branch-paths-filter %} Por exemplo, o fluxo de trabalho a seguir será executado somente quando um pull request que inclui uma mudança para um arquivo (`.js`) do JavaScript for aberto em um branch cujo nome começa com `releases/`:
+**Note:** {% data reusables.actions.branch-paths-filter %} For example, the following workflow will only run when a pull request that includes a change to a JavaScript (`.js`) file is opened on a branch whose name starts with `releases/`:
```yaml
on:
@@ -950,7 +950,7 @@ on:
{% note %}
-**Observação:** {% data reusables.github-actions.branch-paths-filter %} Por exemplo, o fluxo de trabalho a seguir será executado somente quando um push que inclui uma mudança para um arquivo (`.js`) do JavaScript é feito em um branch cujo nome começa com `releases/`:
+**Note:** {% data reusables.actions.branch-paths-filter %} For example, the following workflow will only run when a push that includes a change to a JavaScript (`.js`) file is made to a branch whose name starts with `releases/`:
```yaml
on:
@@ -991,7 +991,7 @@ on:
{% note %}
-**Observação:** {% data reusables.github-actions.branch-paths-filter %} Por exemplo, o fluxo de trabalho a seguir será executado somente quando um push que inclui uma mudança para um arquivo (`.js`) do JavaScript é feito em um branch cujo nome começa com `releases/`:
+**Note:** {% data reusables.actions.branch-paths-filter %} For example, the following workflow will only run when a push that includes a change to a JavaScript (`.js`) file is made to a branch whose name starts with `releases/`:
```yaml
on:
@@ -1016,7 +1016,7 @@ on:
{% endnote %}
-{% data reusables.github-actions.branch-requirement %}
+{% data reusables.actions.branch-requirement %}
Executa o fluxo de trabalho quando uma atividade relacionada ao {% data variables.product.prodname_registry %} ocorre no seu repositório. Para obter mais informações, consulte "[Documentação do {% data variables.product.prodname_registry %}](/packages)".
@@ -1068,7 +1068,7 @@ on:
| ---------------------------------------------------------------------------------------------------------------- | ------------------ | ------------------------------ | ------------- |
| [repository_dispatch](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads/#repository_dispatch) | Personalizado | Último commit no branch padrão | Branch padrão |
-{% data reusables.github-actions.branch-requirement %}
+{% data reusables.actions.branch-requirement %}
Você pode usar a API do {% data variables.product.product_name %} para acionar um evento do webhook denominado [`repository_dispatch`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads/#repository_dispatch) quando quiser acionar um fluxo de trabalho para uma atividade que ocorre fora do {% data variables.product.product_name %}. Para obter mais informações, consulte "[Criar um evento de envio do repositório](/rest/reference/repos#create-a-repository-dispatch-event)".
@@ -1160,7 +1160,7 @@ As notificações de fluxos de trabalho agendados são enviadas ao usuário que
| ---------------------------------------------------------------------------------------- | ------------------ | ------------------------------ | ------------ |
| [`status`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads/#status) | n/a | Último commit no branch padrão | n/a |
-{% data reusables.github-actions.branch-requirement %}
+{% data reusables.actions.branch-requirement %}
Executa o fluxo de trabalho quando o status do commit de Git é alterado. Por exemplo, os commits podem ser marcados como `erro`, `falha`, `pendente` ou `sucesso`. Se você quiser fornecer mais informações sobre a mudança de status, você deverá usar o evento [`check_run`](#check_run). Para obter informações sobre as APIs de status do commit, consulte "[Status](/graphql/reference/objects#statue)" na documentação da API do GraphQL ou "[Status](/rest/reference/commits#commit-statuses)" na documentação da API REST.
@@ -1201,7 +1201,7 @@ jobs:
{% endnote %}
-{% data reusables.github-actions.branch-requirement %}
+{% data reusables.actions.branch-requirement %}
Executa o fluxo de trabalho quando o repositório do fluxo de trabalho é favoritado. Para obter informações sobre as APIs do pull request, consulte "[addStar](/graphql/reference/mutations#addstar)" na documentação da API do GraphQL ou "[Marcando como favorito](/rest/reference/activity#starring)" na documentação da API REST.
@@ -1343,7 +1343,7 @@ jobs:
{% endnote %}
-{% data reusables.github-actions.branch-requirement %}
+{% data reusables.actions.branch-requirement %}
{% note %}
diff --git a/translations/pt-BR/content/actions/using-workflows/sharing-workflows-secrets-and-runners-with-your-organization.md b/translations/pt-BR/content/actions/using-workflows/sharing-workflows-secrets-and-runners-with-your-organization.md
index fc29a230334e..869885706504 100644
--- a/translations/pt-BR/content/actions/using-workflows/sharing-workflows-secrets-and-runners-with-your-organization.md
+++ b/translations/pt-BR/content/actions/using-workflows/sharing-workflows-secrets-and-runners-with-your-organization.md
@@ -50,11 +50,11 @@ Você pode gerenciar seus segredos centralmente dentro de uma organização e, e
Ao criar um segredo em uma organização, você pode usar uma política para limitar quais repositórios podem acessar esse segredo. Por exemplo, você pode conceder acesso a todos os repositórios ou limitar o acesso a apenas repositórios privados ou a uma lista específica de repositórios.
-{% data reusables.github-actions.permissions-statement-secrets-organization %}
+{% data reusables.actions.permissions-statement-secrets-organization %}
{% data reusables.organizations.navigate-to-org %}
{% data reusables.organizations.org_settings %}
-{% data reusables.github-actions.sidebar-secret %}
+{% data reusables.actions.sidebar-secret %}
1. Clique em **Novo segredo**.
1. Digite um nome para o seu segredo na caixa de entrada **Nome**.
1. Insira o **Valor** para o seu segredo.
diff --git a/translations/pt-BR/content/actions/using-workflows/storing-workflow-data-as-artifacts.md b/translations/pt-BR/content/actions/using-workflows/storing-workflow-data-as-artifacts.md
index 2a9010c3b429..cfdbe559cf47 100644
--- a/translations/pt-BR/content/actions/using-workflows/storing-workflow-data-as-artifacts.md
+++ b/translations/pt-BR/content/actions/using-workflows/storing-workflow-data-as-artifacts.md
@@ -26,7 +26,7 @@ topics:
Os artefatos permitem que você persista com os dados após um trabalho ter sido concluído e compartilhe os dados com outro trabalho no mesmo fluxo de trabalho. Um artefato é um arquivo ou uma coleção de arquivos produzidos durante a execução de um fluxo de trabalho. Por exemplo, você pode usar artefatos para salvar a sua criação e testar a saída após uma conclusão da execução do fluxo de trabalho. {% data reusables.actions.reusable-workflow-artifacts %}
-{% data reusables.github-actions.artifact-log-retention-statement %} O período de retenção para um pull request reinicia toda vez que alguém fizer um push de um novo commit para o pull request.
+{% data reusables.actions.artifact-log-retention-statement %} The retention period for a pull request restarts each time someone pushes a new commit to the pull request.
Esses são alguns dos artefatos comuns cujo upload você pode fazer:
@@ -37,7 +37,7 @@ Esses são alguns dos artefatos comuns cujo upload você pode fazer:
{% ifversion fpt or ghec %}
-Armazenar artefatos consome espaço de armazenamento em {% data variables.product.product_name %}. {% data reusables.github-actions.actions-billing %} Para mais informações, consulte "[Gerenciando cobrança para {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions)".
+Armazenar artefatos consome espaço de armazenamento em {% data variables.product.product_name %}. {% data reusables.actions.actions-billing %} For more information, see "[Managing billing for {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions)."
{% else %}
diff --git a/translations/pt-BR/content/actions/using-workflows/triggering-a-workflow.md b/translations/pt-BR/content/actions/using-workflows/triggering-a-workflow.md
index e367075ff407..b0e32f657a95 100644
--- a/translations/pt-BR/content/actions/using-workflows/triggering-a-workflow.md
+++ b/translations/pt-BR/content/actions/using-workflows/triggering-a-workflow.md
@@ -41,7 +41,7 @@ As etapas a seguir ocorrem para acionar a execução de um fluxo de trabalho:
### Acionando um fluxo de trabalho a partir de um fluxo de trabalho
-{% data reusables.github-actions.actions-do-not-trigger-workflows %} Para obter mais informações, consulte "[Efetuando a autenticação com o GITHUB_TOKEN](/actions/configuring-and-managing-workflows/authenticating-with-the-github_token)".
+{% data reusables.actions.actions-do-not-trigger-workflows %} For more information, see "[Authenticating with the GITHUB_TOKEN](/actions/configuring-and-managing-workflows/authenticating-with-the-github_token)."
Se você deseja acionar um fluxo de trabalho de dentro de uma execução de fluxo de trabalho, você pode usar um token de acesso pessoal em vez de `GITHUB_TOKEN` para acionar eventos que exigem um token. Você deverá criar um token de acesso pessoal e armazená-lo como um segredo. Para minimizar seus custos de uso {% data variables.product.prodname_actions %}, certifique-se de que você não cria execução de fluxo de trabalho recursivo ou não intencional. Para obter mais informações sobre a criação de um token de acesso pessoal, consulte[Criando um token de acesso pessoal](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)." Para mais informações sobre como armazenar um token de acesso pessoal como segredo, consulte "[Criar e armazenar segredos criptografados](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets)".
@@ -89,23 +89,23 @@ Use a chave `on` para especificar quais eventos acionam o seu fluxo de trabalho.
### Using a single event
-{% data reusables.github-actions.on-single-example %}
+{% data reusables.actions.on-single-example %}
### Using multiple events
-{% data reusables.github-actions.on-multiple-example %}
+{% data reusables.actions.on-multiple-example %}
### Using activity types and filters with multiple events
-É possível usar tipos de atividade e filtros para controlar ainda mais quando o fluxo de trabalho será executado. Para obter mais informações, consulte [Usando tipos de atividade do evento](#using-event-activity-types) e [Usando filtros](#using-filters). {% data reusables.github-actions.actions-multiple-types %}
+É possível usar tipos de atividade e filtros para controlar ainda mais quando o fluxo de trabalho será executado. Para obter mais informações, consulte [Usando tipos de atividade do evento](#using-event-activity-types) e [Usando filtros](#using-filters). {% data reusables.actions.actions-multiple-types %}
## Usando tipos de atividade do evento
-{% data reusables.github-actions.actions-activity-types %}
+{% data reusables.actions.actions-activity-types %}
## Using filters
-{% data reusables.github-actions.actions-filters %}
+{% data reusables.actions.actions-filters %}
### Usando filtros para direcionar branches específicos para eventos de pull request
@@ -125,7 +125,7 @@ Use a chave `on` para especificar quais eventos acionam o seu fluxo de trabalho.
## Definindo entradas para fluxos de trabalho acionados manualmente
-{% data reusables.github-actions.workflow-dispatch-inputs %}
+{% data reusables.actions.workflow-dispatch-inputs %}
{% ifversion fpt or ghes > 3.3 or ghae-issue-4757 or ghec %}
## Definindo entradas, saídas e segredos para fluxos de trabalho reutilizáveis
diff --git a/translations/pt-BR/content/actions/using-workflows/workflow-syntax-for-github-actions.md b/translations/pt-BR/content/actions/using-workflows/workflow-syntax-for-github-actions.md
index 870d38c28a54..7299b0f245d1 100644
--- a/translations/pt-BR/content/actions/using-workflows/workflow-syntax-for-github-actions.md
+++ b/translations/pt-BR/content/actions/using-workflows/workflow-syntax-for-github-actions.md
@@ -173,7 +173,7 @@ Um booleano que especifica se o segredo deve ser fornecido.
## `on.workflow_dispatch.inputs`
-{% data reusables.github-actions.workflow-dispatch-inputs %}
+{% data reusables.actions.workflow-dispatch-inputs %}
{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
## `permissões`
@@ -318,7 +318,7 @@ Identificador exclusivo da etapa. Você pode usar `id` para fazer referência à
Você pode usar a condicional `if` para evitar que uma etapa trabalho seja executada a não ser que determinada condição seja atendida. Você pode usar qualquer contexto e expressão compatível para criar uma condicional.
-{% data reusables.github-actions.expression-syntax-if %} Para obter mais informações, consulte "[Expressões](/actions/learn-github-actions/expressions)".
+{% data reusables.actions.expression-syntax-if %} Para obter mais informações, consulte "[Expressões](/actions/learn-github-actions/expressions)".
#### Exemplo: Usando contextos
@@ -759,7 +759,7 @@ strategy:
## `jobs..container`
-{% data reusables.github-actions.docker-container-os-support %}
+{% data reusables.actions.docker-container-os-support %}
{% data reusables.actions.jobs.section-running-jobs-in-a-container %}
@@ -789,7 +789,7 @@ strategy:
## `jobs..services`
-{% data reusables.github-actions.docker-container-os-support %}
+{% data reusables.actions.docker-container-os-support %}
Usado para hospedar contêineres de serviço para um trabalho em um fluxo de trabalho. Contêineres de serviço são úteis para a criação de bancos de dados ou serviços armazenamento em cache como o Redis. O executor cria automaticamente uma rede do Docker e gerencia o ciclo de vida dos contêineres do serviço.
diff --git a/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md b/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md
index fec5089e1871..3456d04e3694 100644
--- a/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md
+++ b/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md
@@ -115,7 +115,7 @@ Permite encontrar o identificador universalmente exclusivo (UUID) do seu nó em
```
{% ifversion ghes %}
-Permite isentar uma lista de usuários do limite de taxa de da API. Para obter mais informações, consulte "[Recursos na API REST](/rest/overview/resources-in-the-rest-api#rate-limiting)".
+Permite isentar uma lista de usuários do limite de taxa de da API. A hard limit of 120,000 requests will still apply to these users. Para obter mais informações, consulte "[Recursos na API REST](/rest/overview/resources-in-the-rest-api#rate-limiting)".
``` shell
$ ghe-config app.github.rate-limiting-exempt-users "hubotgithub-actions"
diff --git a/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise.md b/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise.md
index e607bca53ace..95b6229d4c61 100644
--- a/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise.md
+++ b/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise.md
@@ -70,4 +70,4 @@ Para restrições no nível da instância que usam o Azure NSGs, entre em contat
## Usar {% data variables.product.prodname_actions %} com uma lista endereços IP permitidos
-{% data reusables.github-actions.ip-allow-list-self-hosted-runners %}
+{% data reusables.actions.ip-allow-list-self-hosted-runners %}
diff --git a/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises.md b/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises.md
index d56578770691..f76ed137ea76 100644
--- a/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises.md
+++ b/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises.md
@@ -12,6 +12,16 @@ topics:
- Enterprise
---
+{% ifversion ghes < 3.3 %}
+{% note %}
+
+**Observação:** {% data reusables.enterprise.upgrade-ghes-for-actions %}
+
+{% endnote %}
+{% endif %}
+
+## Sobre {% data variables.product.prodname_actions %} para empresas
+
Com {% data variables.product.prodname_actions %}, você pode melhorar a produtividade do desenvolvedor automatizando todas as fases do fluxo de trabalho de desenvolvimento de software da sua empresa.
| Tarefa | Mais informações |
@@ -23,18 +33,29 @@ Com {% data variables.product.prodname_actions %}, você pode melhorar a produti
{% data variables.product.prodname_actions %} ajuda a sua equipe a trabalhar mais rápido e em escala. Quando grandes repositórios começam a usar o {% data variables.product.prodname_actions %}, as equipes fazem merge de um número significativamente maior de pull requests por dia, e os pull requests são mesclados muito mais rapidamente. Para obter mais informações, consulte "[Gravação e envio mais rápido de código](https://octoverse.github.com/writing-code-faster/#scale-through-automation)" no estado do Octoverse.
-{% data variables.product.prodname_actions %} também fornece maior controle sobre implantações. Por exemplo, você pode usar ambientes para exigir aprovação para um trabalho prosseguir ou restringir quais branches podem acionar um fluxo de trabalho, ou limitar o acesso a segredos.{% ifversion ghec or ghae-issue-4856 %} Se os seus fluxos de trabalho precisarem acessar recursos de um provedor de nuvem compatível com o OpenID Connect (OIDC), você poderá configurar seus fluxos de trabalho para efetuar a autenticação diretamente no provedor de nuvem. Isso permitirá que você pare de armazenar credenciais como segredos de longa duração e irá fornecer outros benefícios de segurança. Para obter mais informações, consulte[Sobre segurança fortalecida com OpenID Connect](/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect)."{% endif %}
+Você pode criar suas próprias automações exclusivas ou você pode usar e adaptar os fluxos de trabalho do nosso ecossistema de mais de 10, 00 ações construídas por líderes do setor e pela comunidade de código aberto. Para obter mais informações, consulte "[Localizar e personalizar ações](/actions/learn-github-actions/finding-and-customizing-actions)".
{% data variables.product.prodname_actions %} é intuitivo para o desenvolvedor, pois está integrado diretamente à experiência familiar de {% data variables.product.product_name %}.
-Você pode criar suas próprias automações exclusivas ou você pode usar e adaptar os fluxos de trabalho do nosso ecossistema de mais de 10, 00 ações construídas por líderes do setor e pela comunidade de código aberto. Para obter mais informações, consulte "[Localizar e personalizar ações](/actions/learn-github-actions/finding-and-customizing-actions)".
-
{% ifversion ghec %}Você pode desfrutar da conveniência de executores hospedados em {% data variables.product.company_short %}, que são mantidos e atualizados por {% data variables.product.company_short %} ou você{% else %}{% endif %} pode controlar a sua própria infraestrutura privada de CI/CD usando executores auto-hospedados. Os executores auto-hospedados permitem que você determine o ambiente exato e os recursos que completam suas compilações, testes e implantações sem expor o seu ciclo de desenvolvimento de software à internet. Para obter mais informações, consulte {% ifversion ghec %}"[Sobre executores auto-hospedados em {% data variables.product.company_short %}](/actions/using-github-hosted-runners/about-github-hosted-runners)" e {% endif %} "[Sobre executores auto-hospedados](/actions/hosting-your-own-runners/about-self-hosted-runners)."
+{% data variables.product.prodname_actions %} provides greater control over deployments. Por exemplo, você pode usar ambientes para exigir aprovação para um trabalho prosseguir ou restringir quais branches podem acionar um fluxo de trabalho, ou limitar o acesso a segredos.{% ifversion ghec or ghae-issue-4856 %} Se os seus fluxos de trabalho precisarem acessar recursos de um provedor de nuvem compatível com o OpenID Connect (OIDC), você poderá configurar seus fluxos de trabalho para efetuar a autenticação diretamente no provedor de nuvem. OIDC provides security benefits such as eliminating the need to store credentials as long-lived secrets. Para obter mais informações, consulte[Sobre segurança fortalecida com OpenID Connect](/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect)."{% endif %}
+
{% data variables.product.prodname_actions %} também inclui ferramentas para governar o ciclo de desenvolvimento de software da sua empresa e atender às obrigações de conformidade. Para obter mais informações, consulte "[Aplicar políticas para {% data variables.product.prodname_actions %} na sua empresa](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise)".
+## About getting started with {% data variables.product.prodname_actions %}
+
+{% data reusables.actions.introducing-enterprise %}
+
+{% data reusables.actions.migrating-enterprise %}
+
+{% ifversion ghes %}
+{% data reusables.actions.ghes-actions-not-enabled-by-default %} After you finish planning, you can follow the instructions for enabling {% data variables.product.prodname_actions %}. For example, you may need to upgrade the CPU and memory resources for {% data variables.product.product_location %}. Para obter mais informações, consulte "[Primeiros passos com {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server)".
+
+{% else %}
+After you finish planning, you can follow the instructions for getting started with {% data variables.product.prodname_actions %}. For more information, see {% ifversion ghec %}"[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_cloud %}](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-cloud)."{% elsif ghae %}"[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_managed %}](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-ae)."{% endif %}
+{% endif %}
-Para saber mais sobre como você pode fazer a adoção de {% data variables.product.prodname_actions %} com sucesso para sua empresa, siga o caminho de aprendizado "[Adotando {% data variables.product.prodname_actions %} para a sua empresa](/admin/guides#adopt-github-actions-for-your-enterprise)".
## Leia mais
diff --git a/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server.md b/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server.md
index b127c78388e7..1c224d37948d 100644
--- a/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server.md
+++ b/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server.md
@@ -26,7 +26,7 @@ Este artigo explica como os administradores do site podem configurar {% data var
{% data reusables.enterprise.upgrade-ghes-for-actions %}
-Por padrão, {% data variables.product.prodname_actions %} não está habilitado para {% data variables.product.prodname_ghe_server %}. Você precisará determinar se a sua instância tem recursos adequados de CPU e memória para administrar a carga do {% data variables.product.prodname_actions %} sem causar perda de desempenho, e possivelmente aumentar esses recursos. Você também deverá decidir qual provedor de armazenamento você usará para o armazenamento do blob necessário para armazenar os artefatos gerados pela execução do fluxo de trabalho. Em seguida, você irá habilitar {% data variables.product.prodname_actions %} para a sua empresa, gerenciar permissões de acesso e adicionar executores auto-hospedados para executar fluxos de trabalho.
+{% data reusables.actions.ghes-actions-not-enabled-by-default %} You'll need to determine whether your instance has adequate CPU and memory resources to handle the load from {% data variables.product.prodname_actions %} without causing performance loss, and possibly increase those resources. Você também deverá decidir qual provedor de armazenamento você usará para o armazenamento do blob necessário para armazenar os artefatos gerados pela execução do fluxo de trabalho. Em seguida, você irá habilitar {% data variables.product.prodname_actions %} para a sua empresa, gerenciar permissões de acesso e adicionar executores auto-hospedados para executar fluxos de trabalho.
{% data reusables.actions.introducing-enterprise %}
diff --git a/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md b/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md
index 8df47315f7d9..7b6b91890616 100644
--- a/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md
+++ b/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md
@@ -85,6 +85,12 @@ Sempre que seus desenvolvedores de fluxo de trabalho quiserem usar uma ação qu
Você deve planejar como você gerenciará os recursos necessários para usar o {% data variables.product.prodname_actions %}.
+{% ifversion ghes %}
+### Hardware requirements
+
+You may need to upgrade the CPU and memory resources for {% data variables.product.product_location %} to handle the load from {% data variables.product.prodname_actions %} without causing performance loss. For more information, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server#review-hardware-requirements)."
+{% endif %}
+
### Executores
Os fluxos de trabalho de {% data variables.product.prodname_actions %}} exigem executores.{% ifversion ghec %} Você pode escolher usar executores hospedados em {% data variables.product.prodname_dotcom %} ou executores auto-hospedados. Os executores hospedados em {% data variables.product.prodname_dotcom %} são convenientes porque são gerenciados por {% data variables.product.company_short %}, que administram a manutenção e atualizações para você. No entanto você deverá considerar os executores auto-hospedados se você precisar executar um fluxo de trabalho que terá acesso aos recursos por trás de seu firewall ou você quiser ter mais controle sobre os recursos, configuração, ou localização geográfica das máquinas dos seus executores. Para obter mais informações, consulte "[Sobre executores hospedados em {% data variables.product.prodname_dotcom %}](/actions/using-github-hosted-runners/about-github-hosted-runners)" e "[Sobre executores auto-hospedados](/actions/hosting-your-own-runners/about-self-hosted-runners).{% else %} Você deverá hospedar seus próprios executores instalando o aplicativo de executor auto-hospedado em {% data variables.product.prodname_actions %} nas suas próprias máquinas. Para obter mais informações, consulte "[Sobre executores auto-hospedados](/actions/hosting-your-own-runners/about-self-hosted-runners)."{% endif %}
@@ -111,7 +117,7 @@ Você deve configurar o armazenamento externo de blob para estes artefatos. Esco
{% ifversion ghec or ghes %}
-{% data reusables.github-actions.artifact-log-retention-statement %}
+{% data reusables.actions.artifact-log-retention-statement %}
{% endif %}
diff --git a/translations/pt-BR/content/admin/guides.md b/translations/pt-BR/content/admin/guides.md
index cf22f643c6b6..61e9a080ab37 100644
--- a/translations/pt-BR/content/admin/guides.md
+++ b/translations/pt-BR/content/admin/guides.md
@@ -136,5 +136,6 @@ includeGuides:
- /admin/user-management/requiring-two-factor-authentication-for-an-organization
- /admin/user-management/suspending-and-unsuspending-users
- /admin/overview/creating-an-enterprise-account
+ - /admin/user-management/managing-organizations-in-your-enterprise/restoring-a-deleted-organization
---
diff --git a/translations/pt-BR/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md b/translations/pt-BR/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md
index 576432e2016d..1b4e3d9424d3 100644
--- a/translations/pt-BR/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md
+++ b/translations/pt-BR/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md
@@ -71,7 +71,7 @@ Você pode optar por desativar {% data variables.product.prodname_actions %} par
{% data reusables.enterprise-accounts.access-enterprise %}
{% data reusables.enterprise-accounts.policies-tab %}
{% data reusables.enterprise-accounts.actions-tab %}
-{% data reusables.github-actions.change-retention-period-for-artifacts-logs %}
+{% data reusables.actions.change-retention-period-for-artifacts-logs %}
{% endif %}
@@ -88,7 +88,7 @@ Você pode aplicar políticas para controlar como {% data variables.product.prod
{% data reusables.enterprise-accounts.access-enterprise %}
{% data reusables.enterprise-accounts.policies-tab %}
{% data reusables.enterprise-accounts.actions-tab %}
-{% data reusables.github-actions.workflows-from-public-fork-setting %}
+{% data reusables.actions.workflows-from-public-fork-setting %}
{% data reusables.actions.workflow-run-approve-link %}
@@ -98,16 +98,16 @@ Você pode aplicar políticas para controlar como {% data variables.product.prod
### Aplicando uma política para bifurcar pull requests em repositórios privados
-{% data reusables.github-actions.private-repository-forks-overview %}
+{% data reusables.actions.private-repository-forks-overview %}
Se uma política for habilitada para uma empresa, ela poderá ser desabilitada seletivamente em organizações individuais ou repositórios. Se uma política estiver desabilitada para uma empresa, as organizações individuais ou repositórios não poderão habilitá-la.
-{% data reusables.github-actions.private-repository-forks-options %}
+{% data reusables.actions.private-repository-forks-options %}
{% data reusables.enterprise-accounts.access-enterprise %}
{% data reusables.enterprise-accounts.policies-tab %}
{% data reusables.enterprise-accounts.actions-tab %}
-{% data reusables.github-actions.private-repository-forks-configure %}
+{% data reusables.actions.private-repository-forks-configure %}
{% endif %}
@@ -115,11 +115,11 @@ Se uma política for habilitada para uma empresa, ela poderá ser desabilitada s
## Aplicando uma política de permissões de fluxo de trabalho na sua empresa
-{% data reusables.github-actions.workflow-permissions-intro %}
+{% data reusables.actions.workflow-permissions-intro %}
Você pode definir as permissões padrão para o `GITHUB_TOKEN` nas configurações para sua empresa, organizações ou repositórios. Se você escolher a opção restrita como padrão nas configurações da empresa, isto impedirá que a configuração mais permissiva seja escolhida nas configurações da organização ou repositório.
-{% data reusables.github-actions.workflow-permissions-modifying %}
+{% data reusables.actions.workflow-permissions-modifying %}
{% data reusables.enterprise-accounts.access-enterprise %}
{% data reusables.enterprise-accounts.policies-tab %}
diff --git a/translations/pt-BR/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise.md b/translations/pt-BR/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise.md
index b2060c36c695..988e5de13851 100644
--- a/translations/pt-BR/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise.md
+++ b/translations/pt-BR/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise.md
@@ -116,7 +116,7 @@ Você também pode configurar endereços IP permitidos para uma organização in
### Usar {% data variables.product.prodname_actions %} com uma lista endereços IP permitidos
-{% data reusables.github-actions.ip-allow-list-self-hosted-runners %}
+{% data reusables.actions.ip-allow-list-self-hosted-runners %}
{% endif %}
@@ -126,9 +126,11 @@ Você também pode configurar endereços IP permitidos para uma organização in
Você pode usar as autoridades de certificados SSH (CA) para permitir que os integrantes de qualquer organização pertencente à sua empresa acessem os repositórios da organização usando certificados SSH que você fornecer. {% data reusables.organizations.can-require-ssh-cert %} Para obter mais informações, consulte "[Sobre autoridades certificadas de SSH](/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities)".
+{% data reusables.organizations.add-extension-to-cert %}
+
### Adicionar uma autoridade certificada de SSH
-{% data reusables.organizations.add-extension-to-cert %}
+If you require SSH certificates for your enterprise, enterprise members should use a special URL for Git operations over SSH. Para obter mais informações, consulte "[Sobre autoridades certificadas SSH](/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities#about-ssh-urls-with-ssh-certificates)".
{% data reusables.enterprise-accounts.access-enterprise %}
{% data reusables.enterprise-accounts.settings-tab %}
diff --git a/translations/pt-BR/content/admin/user-management/managing-organizations-in-your-enterprise/index.md b/translations/pt-BR/content/admin/user-management/managing-organizations-in-your-enterprise/index.md
index b2b5289fc9ea..ec2a0e5ffe0d 100644
--- a/translations/pt-BR/content/admin/user-management/managing-organizations-in-your-enterprise/index.md
+++ b/translations/pt-BR/content/admin/user-management/managing-organizations-in-your-enterprise/index.md
@@ -27,6 +27,7 @@ children:
- /streaming-the-audit-logs-for-organizations-in-your-enterprise-account
- /removing-users-from-teams-and-organizations
- /removing-organizations-from-your-enterprise
+ - /restoring-a-deleted-organization
- /managing-projects-using-jira
- /continuous-integration-using-jenkins
shortTitle: Gerenciar organizações
diff --git a/translations/pt-BR/content/admin/user-management/managing-organizations-in-your-enterprise/restoring-a-deleted-organization.md b/translations/pt-BR/content/admin/user-management/managing-organizations-in-your-enterprise/restoring-a-deleted-organization.md
new file mode 100644
index 000000000000..f888f9b7509d
--- /dev/null
+++ b/translations/pt-BR/content/admin/user-management/managing-organizations-in-your-enterprise/restoring-a-deleted-organization.md
@@ -0,0 +1,53 @@
+---
+title: Restoring a deleted organization
+intro: 'You can partially restore an organization that was previously deleted on {% data variables.product.product_location %}.'
+versions:
+ ghes: '*'
+type: how_to
+topics:
+ - Administrator
+ - Enterprise
+ - Organizations
+shortTitle: Restore organization
+permissions: 'Site administers can restore an organization on {% data variables.product.product_name %}.'
+---
+
+## About organization restoration
+
+You can use the site admin dashboard to restore an organization that was previously deleted on {% data variables.product.product_location %}, as long as the audit log Elasticsearch indices contain the data for the `org.delete` event.
+
+Immediately after you restore an organization, the organization will not be exactly the same as it was prior to the deletion. You'll have to manually restore any repositories that were owned by the organization. Para obter mais informações, consulte "[Restaurar um repositório excluído](/admin/user-management/managing-repositories-in-your-enterprise/restoring-a-deleted-repository)".
+
+You can also use the audit log to help you manually re-add teams and organization members. For more information, see "[Restoring members and teams](#restoring-members-and-teams)."
+
+## Restoring an organization
+
+{% data reusables.enterprise_site_admin_settings.access-settings %}
+1. Under "Search users, organizations, enterprises, teams, repositories, gists, and applications", search for the organization.
+
+ 
+
+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**.
+
+ 
+
+## Restoring members and teams
+
+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)."
+
+In all the search phrases below, replace ORGANIZATION with the name of the organization and TEAM with the name of the team.
+
+### Restoring organization members
+
+1. To find all users who were added to and removed from the organization, search the audit log for `action:org.add_member org:ORGANIZATION` and `action:org.remove_member org:ORGANIZATION`.
+1. Manually add to the organization each user that should still be a member. For more information, see "[Adding people to your organization](/organizations/managing-membership-in-your-organization/adding-people-to-your-organization)."
+
+### Restoring teams
+
+1. To find each team name, search the audit log for `action:team.create org:ORGANIZATION`.
+1. Manually recreate the team. For more information, see "[Creating a team](/organizations/organizing-members-into-teams/creating-a-team)."
+1. To find the members that have been added to each team, search for `action:team.add_member team:"ORGANIZATION/TEAM"`.
+1. Manually re-add the team members. For more information, see "[Adding organization members to a team](/organizations/organizing-members-into-teams/adding-organization-members-to-a-team)."
+1. To find the repositories that the team was granted access to, search for `action:team.add_repository team:"ORGANIZATION/TEAM"`.
+1. To find the access level that the team was granted for each repository, search for `action:team.update_repository_permission team:"ORGANIZATION/TEAM"`.
+1. Manually give the team access again. Para obter mais informações, consulte "[Gerenciando o acesso da equipe ao repositório de uma organização](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository)".
diff --git a/translations/pt-BR/content/authentication/managing-commit-signature-verification/checking-for-existing-gpg-keys.md b/translations/pt-BR/content/authentication/managing-commit-signature-verification/checking-for-existing-gpg-keys.md
index 2399e673a030..17aa0eb81151 100644
--- a/translations/pt-BR/content/authentication/managing-commit-signature-verification/checking-for-existing-gpg-keys.md
+++ b/translations/pt-BR/content/authentication/managing-commit-signature-verification/checking-for-existing-gpg-keys.md
@@ -28,7 +28,12 @@ shortTitle: Chaves GPG existentes
{% data reusables.gpg.list-keys-with-note %}
3. Verifique a saída do comando para ver se você tem um par de chaves GPG.
* Se não houver pares de chaves GPG ou se você não quiser usar as que estiverem disponíveis para assinatura de commits e tags, [gere outra chave GPG](/articles/generating-a-new-gpg-key).
- * Se houver um par de chaves GPG e você quiser usá-lo para assinar commits e tags, [adicione a chave GPG à sua conta do GitHub](/articles/adding-a-new-gpg-key-to-your-github-account).
+ * If there's an existing GPG key pair and you want to use it to sign commits and tags, you can display the public key using the following command, substituting in the GPG key ID you'd like to use. Neste exemplo, o ID da chave GPG é `3AA5C34371567BD2`:
+ ```shell
+ $ gpg --armor --export 3AA5C34371567BD2
+ # Prints the GPG key ID, in ASCII armor format
+ ```
+ You can then [add your GPG key to your GitHub account](/articles/adding-a-new-gpg-key-to-your-github-account).
## Leia mais
diff --git a/translations/pt-BR/content/authentication/managing-commit-signature-verification/telling-git-about-your-signing-key.md b/translations/pt-BR/content/authentication/managing-commit-signature-verification/telling-git-about-your-signing-key.md
index 7a3abc67dceb..67138b370715 100644
--- a/translations/pt-BR/content/authentication/managing-commit-signature-verification/telling-git-about-your-signing-key.md
+++ b/translations/pt-BR/content/authentication/managing-commit-signature-verification/telling-git-about-your-signing-key.md
@@ -45,6 +45,12 @@ Se você tiver várias chaves GPG, precisará informar ao Git qual deve ser usad
$ if [ -r ~/.bash_profile ]; then echo 'export GPG_TTY=$(tty)' >> ~/.bash_profile; \
else echo 'export GPG_TTY=$(tty)' >> ~/.profile; fi
```
+1. Optionally, to prompt you to enter a PIN or passphrase when required, install `pinentry-mac`. For example, using [Homebrew](https://brew.sh/):
+ ```shell
+ $ brew install pinentry-mac
+ $ echo "pinentry-program $(which pinentry-mac)" >> ~/.gnupg/gpg-agent.conf
+ $ killall gpg-agent
+ ```
{% data reusables.gpg.x-509-key %}
diff --git a/translations/pt-BR/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md b/translations/pt-BR/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md
index 9e467e05363e..68ff3ecddc40 100644
--- a/translations/pt-BR/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md
+++ b/translations/pt-BR/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md
@@ -16,9 +16,9 @@ shortTitle: Cobrança para o GitHub Actions
## Sobre a cobrança do {% data variables.product.prodname_actions %}
-{% data reusables.github-actions.actions-billing %}
+{% data reusables.actions.actions-billing %}
-{% data reusables.github-actions.actions-spending-limit-brief %} Para obter mais informações, consulte "[Sobre limites de gastos](#about-spending-limits)".
+{% data reusables.actions.actions-spending-limit-brief %} Para obter mais informações, consulte "[Sobre limites de gastos](#about-spending-limits)".
{% ifversion ghec %}
Se você comprou {% data variables.product.prodname_enterprise %} por meio de um Contrato da Microsoft Enterprise, você pode conectar o ID da sua assinatura do Azure à sua conta corporativa para habilitar e pagar pelo uso de {% data variables.product.prodname_actions %} além dos valores incluindo na sua conta. Para obter mais informações, consulte "[Conectar uma assinatura do Azure à sua empresa](/billing/managing-billing-for-your-github-account/connecting-an-azure-subscription-to-your-enterprise)".
@@ -99,7 +99,7 @@ Se uso de {% data variables.product.prodname_actions %} compartilha a data de co
## Sobre limites de gastos
-{% data reusables.github-actions.actions-spending-limit-detailed %}
+{% data reusables.actions.actions-spending-limit-detailed %}
Para obter informações sobre como gerenciar e alterar o limite de gastos da sua conta, consulte "[Gerenciar seu limite de gastos para {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions/managing-your-spending-limit-for-github-actions)".
diff --git a/translations/pt-BR/content/billing/managing-billing-for-github-actions/managing-your-spending-limit-for-github-actions.md b/translations/pt-BR/content/billing/managing-billing-for-github-actions/managing-your-spending-limit-for-github-actions.md
index 86ce94bfec7e..e9fcc55cedc1 100644
--- a/translations/pt-BR/content/billing/managing-billing-for-github-actions/managing-your-spending-limit-for-github-actions.md
+++ b/translations/pt-BR/content/billing/managing-billing-for-github-actions/managing-your-spending-limit-for-github-actions.md
@@ -19,9 +19,9 @@ shortTitle: Limites de gastos para ações
## Sobre sintaxe limites de gastos para o {% data variables.product.prodname_actions %}
-{% data reusables.github-actions.actions-billing %}
+{% data reusables.actions.actions-billing %}
-{% data reusables.github-actions.actions-spending-limit-brief %}
+{% data reusables.actions.actions-spending-limit-brief %}
{% data reusables.actions.actions-packages-set-spending-limit %} Para obter mais informações sobre os preços para uso de {% data variables.product.prodname_actions %}, consulte "[Sobre cobrança para {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions/about-billing-for-github-actions)".
diff --git a/translations/pt-BR/content/billing/managing-billing-for-github-actions/viewing-your-github-actions-usage.md b/translations/pt-BR/content/billing/managing-billing-for-github-actions/viewing-your-github-actions-usage.md
index 1cdf711c40cb..d1b0ae8d6c3f 100644
--- a/translations/pt-BR/content/billing/managing-billing-for-github-actions/viewing-your-github-actions-usage.md
+++ b/translations/pt-BR/content/billing/managing-billing-for-github-actions/viewing-your-github-actions-usage.md
@@ -43,7 +43,7 @@ Proprietários de organizações e gestores de faturamento podem visualizar o us
{% note %}
-**Nota:** Os detalhes de faturamento para contas corporativas não resumem os minutos de uso para cada sistema operacional. {% data reusables.github-actions.enterprise-billing-details %}
+**Nota:** Os detalhes de faturamento para contas corporativas não resumem os minutos de uso para cada sistema operacional. {% data reusables.actions.enterprise-billing-details %}
{% endnote %}
diff --git a/translations/pt-BR/content/billing/managing-billing-for-github-packages/viewing-your-github-packages-usage.md b/translations/pt-BR/content/billing/managing-billing-for-github-packages/viewing-your-github-packages-usage.md
index 730445170ff9..7671db576c86 100644
--- a/translations/pt-BR/content/billing/managing-billing-for-github-packages/viewing-your-github-packages-usage.md
+++ b/translations/pt-BR/content/billing/managing-billing-for-github-packages/viewing-your-github-packages-usage.md
@@ -42,7 +42,7 @@ Proprietários de organizações e gestores de faturamento podem visualizar o us
{% note %}
-**Nota:** Os detalhes de faturamento para contas corporativas somente resumem o uso de dados de armazenamento por organização. {% data reusables.github-actions.enterprise-billing-details %}
+**Nota:** Os detalhes de faturamento para contas corporativas somente resumem o uso de dados de armazenamento por organização. {% data reusables.actions.enterprise-billing-details %}
{% endnote %}
diff --git a/translations/pt-BR/content/billing/managing-your-github-billing-settings/setting-your-billing-email.md b/translations/pt-BR/content/billing/managing-your-github-billing-settings/setting-your-billing-email.md
index 2d8362e6782a..b65585c4b607 100644
--- a/translations/pt-BR/content/billing/managing-your-github-billing-settings/setting-your-billing-email.md
+++ b/translations/pt-BR/content/billing/managing-your-github-billing-settings/setting-your-billing-email.md
@@ -64,3 +64,44 @@ Deve-se sempre designar um endereço como o destinatário principal. O endereço
1. Para inserir o usuário na lista, clique em **Editar**. 
1. À direita do endereço de e-mail, use o menu suspenso "Editar" e clique em **Remover**. 
1. Revise a instrução de confirmação e clique em **Remover**.
+
+{% ifversion ghec %}
+## Setting your enterprise's billing email
+
+Your enterprise's billing email is where {% data variables.product.product_name %} sends receipts and other billing-related communication. The email address does not need to be unique to the enterprise account.
+
+Only enterprise members with the owner or billing manager role can access or change billing settings for your enterprise. For more information, see "[Managing users in your enterprise](/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise)."
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.settings-tab %}
+{% data reusables.enterprise-accounts.billing-tab %}
+1. Click **Billing emails**.
+2. Under "Email recipients", to the right of the billing email address, click **Edit**. 
+2. Insira um endereço de e-mail válido e clique **Atualizar**. 
+
+## Managing additional recipients for your enterprise's billing email
+
+Se você tiver usuários que desejem receber relatórios de cobrança, você poderá adicionar seus endereços de e-mail como destinatários de e-mail de cobrança.
+
+Only enterprise members with the owner or billing manager role can access or change billing settings for your enterprise. For more information, see "[Managing users in your enterprise](/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise)."
+
+### Adicionar um destinatário para notificações de cobrança
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.settings-tab %}
+{% data reusables.enterprise-accounts.billing-tab %}
+1. Click **Billing emails**.
+2. Under "Email recipients", to the right of the billing email address, click **Add**. 
+3. Digite o endereço de e-mail do destinatário e, em seguida, clique em **Adicionar**. 
+
+### Remover um destinatário das notificações de cobrança
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.settings-tab %}
+{% data reusables.enterprise-accounts.billing-tab %}
+1. Click **Billing emails**.
+2. Em "Destinatários de e-mail", encontre o endereço de e-mail que deseja remover.
+3. Para inserir o usuário na lista, clique em **Editar**. 
+4. À direita do endereço de e-mail, use o menu suspenso "Editar" e clique em **Remover**. 
+5. Revise a instrução de confirmação e clique em **Remover**.
+{% endif %}
diff --git a/translations/pt-BR/content/code-security/code-scanning/integrating-with-code-scanning/uploading-a-sarif-file-to-github.md b/translations/pt-BR/content/code-security/code-scanning/integrating-with-code-scanning/uploading-a-sarif-file-to-github.md
index 8f21ec78dff1..0e33d7b940fb 100644
--- a/translations/pt-BR/content/code-security/code-scanning/integrating-with-code-scanning/uploading-a-sarif-file-to-github.md
+++ b/translations/pt-BR/content/code-security/code-scanning/integrating-with-code-scanning/uploading-a-sarif-file-to-github.md
@@ -86,7 +86,11 @@ jobs:
build:
runs-on: ubuntu-latest{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
permissions:
- security-events: write{% endif %}
+ # required for all workflows
+ security-events: write
+ # only required for workflows in private repositories
+ actions: read
+ contents: read{% endif %}
steps:
# This step checks out a copy of your repository.
- name: Checkout repository
@@ -123,7 +127,11 @@ jobs:
build:
runs-on: ubuntu-latest{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
permissions:
- security-events: write{% endif %}
+ # required for all workflows
+ security-events: write
+ # only required for workflows in private repositories
+ actions: read
+ contents: read{% endif %}
steps:
- uses: actions/checkout@v2
- name: Run npm install
diff --git a/translations/pt-BR/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-encrypted-secrets-for-dependabot.md b/translations/pt-BR/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-encrypted-secrets-for-dependabot.md
index 7b0baf31d437..0281f2e30b62 100644
--- a/translations/pt-BR/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-encrypted-secrets-for-dependabot.md
+++ b/translations/pt-BR/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-encrypted-secrets-for-dependabot.md
@@ -44,11 +44,11 @@ O nome de um segredo de {% data variables.product.prodname_dependabot %}:
## Adicionar um repositório secreto para {% data variables.product.prodname_dependabot %}
-{% data reusables.github-actions.permissions-statement-secrets-repository %}
+{% data reusables.actions.permissions-statement-secrets-repository %}
{% data reusables.repositories.navigate-to-repo %}
{% data reusables.repositories.sidebar-settings %}
-{% data reusables.github-actions.sidebar-secret %}
+{% data reusables.actions.sidebar-secret %}
{% data reusables.dependabot.dependabot-secrets-button %}
1. Clique em **Novo segredo do repositório**.
1. Digite um nome para o seu segredo na caixa de entrada **Nome**.
@@ -63,11 +63,11 @@ O nome de um segredo de {% data variables.product.prodname_dependabot %}:
Ao criar um segredo em uma organização, você pode usar uma política para limitar quais repositórios podem acessar esse segredo. Por exemplo, você pode conceder acesso a todos os repositórios ou limitar o acesso a apenas repositórios privados ou a uma lista específica de repositórios.
-{% data reusables.github-actions.permissions-statement-secrets-organization %}
+{% data reusables.actions.permissions-statement-secrets-organization %}
{% data reusables.organizations.navigate-to-org %}
{% data reusables.organizations.org_settings %}
-{% data reusables.github-actions.sidebar-secret %}
+{% data reusables.actions.sidebar-secret %}
{% data reusables.dependabot.dependabot-secrets-button %}
1. Clique em **Novo segredo da organização**.
1. Digite um nome para o seu segredo na caixa de entrada **Nome**.
diff --git a/translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces.md b/translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces.md
index 42daae757806..d83f6e0b73fd 100644
--- a/translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces.md
+++ b/translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces.md
@@ -51,7 +51,7 @@ Para criar segredos para um repositório da organização, você deve ter acesso
Ao criar um segredo em uma organização, você pode usar uma política para limitar quais repositórios podem acessar esse segredo. Por exemplo, você pode conceder acesso a todos os repositórios ou limitar o acesso a apenas repositórios privados ou a uma lista específica de repositórios.
-{% data reusables.github-actions.permissions-statement-secrets-organization %}
+{% data reusables.actions.permissions-statement-secrets-organization %}
{% data reusables.organizations.navigate-to-org %}
{% data reusables.organizations.org_settings %}
@@ -68,7 +68,7 @@ Você pode verificar quais políticas de acesso são aplicadas a um segredo na s
{% data reusables.organizations.navigate-to-org %}
{% data reusables.organizations.org_settings %}
-{% data reusables.github-actions.sidebar-secret %}
+{% data reusables.actions.sidebar-secret %}
1. A lista de segredos inclui quaisquer permissões e políticas configuradas. Por exemplo: 
1. Para obter mais detalhes sobre as permissões configuradas para cada segredo, clique em **Atualizar**.
diff --git a/translations/pt-BR/content/get-started/learning-about-github/githubs-products.md b/translations/pt-BR/content/get-started/learning-about-github/githubs-products.md
index 8f9ef3ed76e9..6956f597ca2b 100644
--- a/translations/pt-BR/content/get-started/learning-about-github/githubs-products.md
+++ b/translations/pt-BR/content/get-started/learning-about-github/githubs-products.md
@@ -89,7 +89,7 @@ Além dos recursos disponíveis no {% data variables.product.prodname_free_team
{% data variables.product.company_short %} realiza a cobrança para {% data variables.product.prodname_team %} por usuário. Para obter mais informações, consulte "[Sobre os preços por usuário]({% ifversion not fpt %}/free-pro-team@latest{% endif %}/billing/managing-billing-for-your-github-account/about-per-user-pricing){% ifversion fpt %}. "{% else %}" na documentação dos planos Grátis, Pro, & Equipe.{% endif %}
-{% data reusables.github-actions.actions-billing %}
+{% data reusables.actions.actions-billing %}
## {% data variables.product.prodname_enterprise %}
diff --git a/translations/pt-BR/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-allowed-ip-addresses-for-your-organization.md b/translations/pt-BR/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-allowed-ip-addresses-for-your-organization.md
index dc77352b83e9..f967c51b5285 100644
--- a/translations/pt-BR/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-allowed-ip-addresses-for-your-organization.md
+++ b/translations/pt-BR/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-allowed-ip-addresses-for-your-organization.md
@@ -82,4 +82,4 @@ Para mais informações sobre como criar uma lista de permissões para uma {% da
## Usar {% data variables.product.prodname_actions %} com uma lista endereços IP permitidos
-{% data reusables.github-actions.ip-allow-list-self-hosted-runners %}
+{% data reusables.actions.ip-allow-list-self-hosted-runners %}
diff --git a/translations/pt-BR/content/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities.md b/translations/pt-BR/content/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities.md
index e1d18ba950b0..29206cf4314e 100644
--- a/translations/pt-BR/content/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities.md
+++ b/translations/pt-BR/content/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities.md
@@ -28,9 +28,15 @@ Por exemplo, você pode desenvolver um sistema interno que emite um novo certifi
Integrantes da organização podem usar os certificados assinados para autenticação mesmo que você tenha aplicado o logon único SAML. A menos que você exija certificados SSH, os integrantes podem continuar a usar outros meios de autenticação para acessar os recursos da organização no Git, como o nome de usuário e senha deles, tokens de acesso pessoais e outras chaves SSH próprias.
{% endif %}
-Os integrantes não poderão usar seus certificados para acessar bifurcações dos seus repositórios que são propriedade das contas de usuário.
+Members will not be able to use their certificates to access forks of your repositories that are owned by their personal accounts.
-Para evitar erros de autenticação, os integrantes da organização devem usar uma URL especial que inclua o ID da organização para clonar repositórios usando certificados assinados. Qualquer pessoa com acesso de leitura no repositório pode localizar essa URL na página do repositório. Para obter mais informações, consulte "[Clonar um repositório](/articles/cloning-a-repository)".
+## About SSH URLs with SSH certificates
+
+If your organization requires SSH certificates, to prevent authentication errors, organization members should use a special URL that includes the organization ID when performing Git operations over SSH. This special URL allows the client and server to more easily negotiate which key on the member's computer should be used for authentication. If a member uses the normal URL, which starts with `git@github.com`, the SSH client might offer the wrong key, causing the operation to fail.
+
+Anyone with read access to the repository can find this URL by selecting the **Code** dropdown menu on the main page of the repository, then clicking **Use SSH**.
+
+If your organization doesn't require SSH certificates, members can continue to use their own SSH keys, or other means of authentication. In that case, either the special URL or the normal URL, which starts with `git@github.com`, will work.
## Emitindo certificados
diff --git a/translations/pt-BR/content/organizations/managing-git-access-to-your-organizations-repositories/managing-your-organizations-ssh-certificate-authorities.md b/translations/pt-BR/content/organizations/managing-git-access-to-your-organizations-repositories/managing-your-organizations-ssh-certificate-authorities.md
index edd2bc3cc1cf..432434f542b3 100644
--- a/translations/pt-BR/content/organizations/managing-git-access-to-your-organizations-repositories/managing-your-organizations-ssh-certificate-authorities.md
+++ b/translations/pt-BR/content/organizations/managing-git-access-to-your-organizations-repositories/managing-your-organizations-ssh-certificate-authorities.md
@@ -20,9 +20,11 @@ Proprietários da organização podem gerenciar as autoridades certificadas (CA,
Você pode permitir que os integrantes acessem os repositórios da organização com certificados SSH fornecidos por você, adicionando um CA SSH à organização. {% data reusables.organizations.can-require-ssh-cert %} Para obter mais informações, consulte "[Sobre autoridades certificadas de SSH](/articles/about-ssh-certificate-authorities)".
+{% data reusables.organizations.add-extension-to-cert %}
+
## Adicionar uma autoridade certificada de SSH
-{% data reusables.organizations.add-extension-to-cert %}
+If you require SSH certificates for your enterprise, enterprise members should use a special URL for Git operations over SSH. Para obter mais informações, consulte "[Sobre autoridades certificadas SSH](/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities#about-ssh-urls-with-ssh-certificates)".
{% data reusables.profile.access_org %}
{% data reusables.profile.org_settings %}
diff --git a/translations/pt-BR/content/organizations/managing-organization-settings/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-organization.md b/translations/pt-BR/content/organizations/managing-organization-settings/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-organization.md
index 1a2de6917ed3..ec106f75f899 100644
--- a/translations/pt-BR/content/organizations/managing-organization-settings/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-organization.md
+++ b/translations/pt-BR/content/organizations/managing-organization-settings/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-organization.md
@@ -21,4 +21,4 @@ shortTitle: Configurar período de retenção
{% data reusables.organizations.navigate-to-org %}
{% data reusables.organizations.org_settings %}
{% data reusables.organizations.settings-sidebar-actions %}
-{% data reusables.github-actions.change-retention-period-for-artifacts-logs %}
+{% data reusables.actions.change-retention-period-for-artifacts-logs %}
diff --git a/translations/pt-BR/content/organizations/managing-organization-settings/deleting-an-organization-account.md b/translations/pt-BR/content/organizations/managing-organization-settings/deleting-an-organization-account.md
index b6151aee7273..7bee24a82eb3 100644
--- a/translations/pt-BR/content/organizations/managing-organization-settings/deleting-an-organization-account.md
+++ b/translations/pt-BR/content/organizations/managing-organization-settings/deleting-an-organization-account.md
@@ -12,7 +12,7 @@ versions:
topics:
- Organizations
- Teams
-shortTitle: Excluir conta da organização
+shortTitle: Delete organization
---
{% ifversion fpt or ghec %}
@@ -26,7 +26,15 @@ shortTitle: Excluir conta da organização
## 1. Fazer backup do conteúdo da organização
-Depois que você exclui uma organização, o GitHub **não pode restaurar o conteúdo que você tem lá**. Portanto, antes de excluir sua organização, certifique-se de ter uma cópia de todos os repositórios, wikis, problemas e quadros de projetos da conta.
+{% ifversion not ghes %} After you delete an organization, {% data variables.product.company_short %} **cannot restore your content**. Therefore, before{% else %}Before{% endif %} you delete your organization, make sure you have a copy of all repositories, wikis, issues, and project boards from the account.
+
+{% ifversion ghes %}
+{% note %}
+
+**Note:** If necessary, a site administrator for {% data variables.product.product_location %} may be able to partially restore a deleted organization. For more information, see "[Restoring a deleted organization](/admin/user-management/managing-organizations-in-your-enterprise/restoring-a-deleted-organization)."
+
+{% endnote %}
+{% endif %}
## 2. Excluir a organização
diff --git a/translations/pt-BR/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md b/translations/pt-BR/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md
index 47e5cf2c933e..b69469e87da4 100644
--- a/translations/pt-BR/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md
+++ b/translations/pt-BR/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md
@@ -19,11 +19,11 @@ shortTitle: Desativar ou limitar ações
## Sobre as permissões de {% data variables.product.prodname_actions %} para a sua organização
-{% data reusables.github-actions.disabling-github-actions %} Para mais informações sobre {% data variables.product.prodname_actions %}, consulte "[Sobre {% data variables.product.prodname_actions %}](/actions/getting-started-with-github-actions/about-github-actions)."
+{% data reusables.actions.disabling-github-actions %} Para mais informações sobre {% data variables.product.prodname_actions %}, consulte "[Sobre {% data variables.product.prodname_actions %}](/actions/getting-started-with-github-actions/about-github-actions)."
-Você pode habilitar o {% data variables.product.prodname_actions %} para todos os repositórios da sua organização. {% data reusables.github-actions.enabled-actions-description %} Você pode desabilitar {% data variables.product.prodname_actions %} para todos os repositórios da sua organização. {% data reusables.github-actions.disabled-actions-description %}
+Você pode habilitar o {% data variables.product.prodname_actions %} para todos os repositórios da sua organização. {% data reusables.actions.enabled-actions-description %} Você pode desabilitar {% data variables.product.prodname_actions %} para todos os repositórios da sua organização. {% data reusables.actions.disabled-actions-description %}
-Como alternativa, você pode habilitar o {% data variables.product.prodname_actions %} para todos os repositórios na sua organização e limitar as ações que um fluxo de trabalho pode executar. {% data reusables.github-actions.enabled-local-github-actions %}
+Como alternativa, você pode habilitar o {% data variables.product.prodname_actions %} para todos os repositórios na sua organização e limitar as ações que um fluxo de trabalho pode executar. {% data reusables.actions.enabled-local-github-actions %}
## Gerenciar as permissões de {% data variables.product.prodname_actions %} para a sua organização
@@ -68,7 +68,7 @@ Você pode configurar esse comportamento para uma organização seguindo o proce
{% data reusables.profile.access_org %}
{% data reusables.profile.org_settings %}
{% data reusables.organizations.settings-sidebar-actions %}
-{% data reusables.github-actions.workflows-from-public-fork-setting %}
+{% data reusables.actions.workflows-from-public-fork-setting %}
{% data reusables.actions.workflow-run-approve-link %}
{% endif %}
@@ -76,28 +76,28 @@ Você pode configurar esse comportamento para uma organização seguindo o proce
{% ifversion fpt or ghes or ghec %}
## Habilitar fluxos de trabalho para bifurcações privadas do repositório
-{% data reusables.github-actions.private-repository-forks-overview %}
+{% data reusables.actions.private-repository-forks-overview %}
{% ifversion ghec or ghae or ghes %}Se uma política estiver desabilitada para uma empresa, ela não poderá ser habilitada para as organizações.{% endif %} Se uma política estiver desabilitada para uma organização, ela não poderá ser habilitada para repositórios. Se uma organização habilitar uma política, a política poderá ser desabilitada para repositórios individuais.
-{% data reusables.github-actions.private-repository-forks-options %}
+{% data reusables.actions.private-repository-forks-options %}
### Configurar a política de bifurcação privada para uma organização
{% data reusables.profile.access_org %}
{% data reusables.profile.org_settings %}
{% data reusables.organizations.settings-sidebar-actions %}
-{% data reusables.github-actions.private-repository-forks-configure %}
+{% data reusables.actions.private-repository-forks-configure %}
{% endif %}
{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
## Definindo as permissões do `GITHUB_TOKEN` para a sua organização
-{% data reusables.github-actions.workflow-permissions-intro %}
+{% data reusables.actions.workflow-permissions-intro %}
Você pode definir as permissões padrão para o `GITHUB_TOKEN` nas configurações para a sua organização ou repositórios. Se você escolher a opção restrita como padrão nas configurações da sua organização, a mesma opção será selecionada automaticamente nas configurações dos repositórios na organização, e a opção permissiva ficará desabilitada. Se sua organização pertence a uma conta {% data variables.product.prodname_enterprise %} e o padrão mais restrito foi selecionado nas configurações corporativas, você não poderá de escolher o padrão mais permissivo nas configurações da organização.
-{% data reusables.github-actions.workflow-permissions-modifying %}
+{% data reusables.actions.workflow-permissions-modifying %}
### Configurar as permissões padrão do `GITHUB_TOKEN`
diff --git a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork.md b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork.md
index 54f9af82813e..5aa1bab640ec 100644
--- a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork.md
+++ b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork.md
@@ -13,6 +13,7 @@ versions:
ghec: '*'
topics:
- Pull requests
+permissions: People with write access for a forked repository can sync the fork to the upstream repository.
---
{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
@@ -20,8 +21,8 @@ topics:
## Sincronizando uma bifurcação a partir da interface de usuário da web
1. Em {% data variables.product.product_name %}, acesse a página principal do repositório bifurcado que você deseja sincronizar com o repositório upstream.
-1. Selecione o menu suspenso **Buscar a upstream**. 
-1. Revise as informações sobre os commits do repositório upstream e, em seguida, clique em **Buscar e merge**. 
+2. Selecione o menu suspenso **Buscar a upstream**. 
+3. Revise as informações sobre os commits do repositório upstream e, em seguida, clique em **Buscar e merge**. 
Se as alterações do repositório a upstream gerarem conflitos, {% data variables.product.company_short %} solicitará a criação de um pull request para resolver os conflitos.
@@ -33,6 +34,7 @@ Para poder sincronizar a bifurcação com o repositório upstream, você deve [c
{% data reusables.command_line.open_the_multi_os_terminal %}
2. Altere o diretório de trabalho atual referente ao seu projeto local.
3. Obtenha os branches e os respectivos commits do repositório upstream. Os commits para `BRANCHNAME` serão armazenados no branch local `upstream/BRANCHNAME`.
+
```shell
$ git fetch upstream
> remote: Counting objects: 75, done.
@@ -42,12 +44,16 @@ Para poder sincronizar a bifurcação com o repositório upstream, você deve [c
> From https://{% data variables.command_line.codeblock %}/ORIGINAL_OWNER/ORIGINAL_REPOSITORY
> * [new branch] main -> upstream/main
```
+
4. Faça o checkout do branch padrão local da sua bifurcação - neste caso, nós usamos o `principal`.
+
```shell
$ git checkout main
> Switched to branch 'main'
```
+
5. Faça merge das alterações do branch padrão upstream - nesse caso, `upstream/main` - no seu branch padrão local. Isso coloca o branch padrão da bifurcação em sincronia com o repositório upstream, sem perder as alterações locais.
+
```shell
$ git merge upstream/main
> Updating a422352..5fdff0f
diff --git a/translations/pt-BR/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/about-commits.md b/translations/pt-BR/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/about-commits.md
index ca83249220dc..386c02f0531c 100644
--- a/translations/pt-BR/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/about-commits.md
+++ b/translations/pt-BR/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/about-commits.md
@@ -6,6 +6,7 @@ redirect_from:
- /github/committing-changes-to-your-project/why-are-my-commits-in-the-wrong-order
- /github/committing-changes-to-your-project/about-commits
- /github/committing-changes-to-your-project/creating-and-editing-commits/about-commits
+ - /pull-requests/committing-changes-to-your-project/viewing-and-comparing-commits/commit-branch-and-tag-labels
versions:
fpt: '*'
ghes: '*'
@@ -24,5 +25,20 @@ Também é possível criar um commit em nome de uma organização. Para obter ma
O rebase permite que você altere uma série de commits e pode modificar a ordem dos commits na sua linha do tempo. Para obter mais informações, consulte "[Sobre o rebase do git](/github/getting-started-with-github/about-git-rebase)".
+## About commit branches and tag labels
+
+You can see which branch a commit is on by looking at the labels beneath the commit on the commit page.
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.navigate-to-commit-page %}
+1. Navegue até o commit clicando no link da mensagem do commit. 
+2. To see what branch the commit is on, check the label below the commit message. 
+
+If your commit is not on the default branch (`main`), the label will show the branches which contain the commit. If the commit is part of an unmerged pull request, you can click the link to go to the pull request.
+
+Assim que o commit estiver no branch padrão, todas as tags que contêm o commit serão mostradas e o branch padrão será o único branch listado. For more information on tags, see "[Git Basics - Tagging](https://git-scm.com/book/en/v2/Git-Basics-Tagging)" in the Git documentation.
+
+
+
## Leia mais
- "[Fazer commit e revisar alterações no seu projeto](/desktop/contributing-to-projects/committing-and-reviewing-changes-to-your-project#about-commits)" em {% data variables.product.prodname_desktop %}
diff --git a/translations/pt-BR/content/pull-requests/committing-changes-to-your-project/viewing-and-comparing-commits/commit-branch-and-tag-labels.md b/translations/pt-BR/content/pull-requests/committing-changes-to-your-project/viewing-and-comparing-commits/commit-branch-and-tag-labels.md
deleted file mode 100644
index 73b963646cd9..000000000000
--- a/translations/pt-BR/content/pull-requests/committing-changes-to-your-project/viewing-and-comparing-commits/commit-branch-and-tag-labels.md
+++ /dev/null
@@ -1,27 +0,0 @@
----
-title: Fazer commit de etiquetas de tag e branch
-intro: Você pode ver facilmente em qual branch um commit está observando as etiquetas abaixo do commit na página do commit.
-redirect_from:
- - /articles/commit-branch-and-tag-labels
- - /github/committing-changes-to-your-project/commit-branch-and-tag-labels
- - /github/committing-changes-to-your-project/viewing-and-comparing-commits/commit-branch-and-tag-labels
-versions:
- fpt: '*'
- ghes: '*'
- ghae: '*'
- ghec: '*'
-shortTitle: Branch & etiquetas de tag
----
-
-Se seu commit não estiver no branch padrão, um indicador mostrará os branches que contêm o commit. Se o commit fizer parte de uma pull request sem merge, ele mostrará um link.
-
-
-
-Assim que o commit estiver no branch padrão, todas as tags que contêm o commit serão mostradas e o branch padrão será o único branch listado.
-
-
-
-## Leia mais
-
-* "[Assinar commits](/articles/signing-commits)"
-* "[Assinar tags](/articles/signing-tags)"
diff --git a/translations/pt-BR/content/pull-requests/committing-changes-to-your-project/viewing-and-comparing-commits/index.md b/translations/pt-BR/content/pull-requests/committing-changes-to-your-project/viewing-and-comparing-commits/index.md
index 28e3310e1660..c19d3e8294d3 100644
--- a/translations/pt-BR/content/pull-requests/committing-changes-to-your-project/viewing-and-comparing-commits/index.md
+++ b/translations/pt-BR/content/pull-requests/committing-changes-to-your-project/viewing-and-comparing-commits/index.md
@@ -10,7 +10,6 @@ versions:
ghae: '*'
ghec: '*'
children:
- - /commit-branch-and-tag-labels
- /comparing-commits
- /differences-between-commit-views
shortTitle: Visualizar & comparar commits
diff --git a/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/enabling-or-disabling-github-discussions-for-a-repository.md b/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/enabling-or-disabling-github-discussions-for-a-repository.md
index d0d075fe89fb..a508c507858d 100644
--- a/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/enabling-or-disabling-github-discussions-for-a-repository.md
+++ b/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/enabling-or-disabling-github-discussions-for-a-repository.md
@@ -11,7 +11,7 @@ topics:
redirect_from:
- /github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository
- /github/administering-a-repository/managing-repository-settings/enabling-or-disabling-github-discussions-for-a-repository
-shortTitle: Discussões
+shortTitle: Discussions
---
## Habilitar ou desabilitar {% data variables.product.prodname_discussions %} no seu repositório
diff --git a/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md b/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md
index cc576bc9c60e..ed2087d06e43 100644
--- a/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md
+++ b/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md
@@ -24,11 +24,11 @@ shortTitle: Manage GitHub Actions settings
## About {% data variables.product.prodname_actions %} permissions for your repository
-{% data reusables.github-actions.disabling-github-actions %} For more information about {% data variables.product.prodname_actions %}, see "[About {% data variables.product.prodname_actions %}](/actions/getting-started-with-github-actions/about-github-actions)."
+{% data reusables.actions.disabling-github-actions %} For more information about {% data variables.product.prodname_actions %}, see "[About {% data variables.product.prodname_actions %}](/actions/getting-started-with-github-actions/about-github-actions)."
-You can enable {% data variables.product.prodname_actions %} for your repository. {% data reusables.github-actions.enabled-actions-description %} You can disable {% data variables.product.prodname_actions %} for your repository altogether. {% data reusables.github-actions.disabled-actions-description %}
+You can enable {% data variables.product.prodname_actions %} for your repository. {% data reusables.actions.enabled-actions-description %} You can disable {% data variables.product.prodname_actions %} for your repository altogether. {% data reusables.actions.disabled-actions-description %}
-Alternatively, you can enable {% data variables.product.prodname_actions %} in your repository but limit the actions a workflow can run. {% data reusables.github-actions.enabled-local-github-actions %}
+Alternatively, you can enable {% data variables.product.prodname_actions %} in your repository but limit the actions a workflow can run. {% data reusables.actions.enabled-local-github-actions %}
## Managing {% data variables.product.prodname_actions %} permissions for your repository
@@ -78,34 +78,34 @@ You can configure this behavior for a repository using the procedure below. Modi
{% data reusables.repositories.navigate-to-repo %}
{% data reusables.repositories.sidebar-settings %}
{% data reusables.repositories.settings-sidebar-actions %}
-{% data reusables.github-actions.workflows-from-public-fork-setting %}
+{% data reusables.actions.workflows-from-public-fork-setting %}
{% data reusables.actions.workflow-run-approve-link %}
{% endif %}
## Enabling workflows for private repository forks
-{% data reusables.github-actions.private-repository-forks-overview %}
+{% data reusables.actions.private-repository-forks-overview %}
If a policy is disabled for an {% ifversion ghec or ghae or ghes %}enterprise or{% endif %} organization, it cannot be enabled for a repository.
-{% data reusables.github-actions.private-repository-forks-options %}
+{% data reusables.actions.private-repository-forks-options %}
### Configuring the private fork policy for a repository
{% data reusables.repositories.navigate-to-repo %}
{% data reusables.repositories.sidebar-settings %}
{% data reusables.repositories.settings-sidebar-actions %}
-{% data reusables.github-actions.private-repository-forks-configure %}
+{% data reusables.actions.private-repository-forks-configure %}
{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
## Setting the permissions of the `GITHUB_TOKEN` for your repository
-{% data reusables.github-actions.workflow-permissions-intro %}
+{% data reusables.actions.workflow-permissions-intro %}
The default permissions can also be configured in the organization settings. If the more restricted default has been selected in the organization settings, the same option is auto-selected in your repository settings and the permissive option is disabled.
-{% data reusables.github-actions.workflow-permissions-modifying %}
+{% data reusables.actions.workflow-permissions-modifying %}
### Configuring the default `GITHUB_TOKEN` permissions
@@ -152,4 +152,4 @@ You can also define a custom retention period for a specific artifact created by
{% data reusables.repositories.navigate-to-repo %}
{% data reusables.repositories.sidebar-settings %}
{% data reusables.repositories.settings-sidebar-actions %}
-{% data reusables.github-actions.change-retention-period-for-artifacts-logs %}
+{% data reusables.actions.change-retention-period-for-artifacts-logs %}
diff --git a/translations/pt-BR/content/rest/overview/index.md b/translations/pt-BR/content/rest/overview/index.md
index 7a5739e7de4a..14ab2aee677f 100644
--- a/translations/pt-BR/content/rest/overview/index.md
+++ b/translations/pt-BR/content/rest/overview/index.md
@@ -18,5 +18,6 @@ children:
- /libraries
- /openapi-description
- /endpoints-available-for-github-apps
+ - /permissions-required-for-github-apps
---
diff --git a/translations/pt-BR/content/rest/reference/permissions-required-for-github-apps.md b/translations/pt-BR/content/rest/overview/permissions-required-for-github-apps.md
similarity index 99%
rename from translations/pt-BR/content/rest/reference/permissions-required-for-github-apps.md
rename to translations/pt-BR/content/rest/overview/permissions-required-for-github-apps.md
index 4d12c54333ce..b79dc9b20201 100644
--- a/translations/pt-BR/content/rest/reference/permissions-required-for-github-apps.md
+++ b/translations/pt-BR/content/rest/overview/permissions-required-for-github-apps.md
@@ -3,6 +3,7 @@ title: Permissões necessárias para os aplicativos GitHub
intro: 'Você pode encontrar as permissões necessárias para cada ponto de extremidade compatível com {% data variables.product.prodname_github_app %}.'
redirect_from:
- /v3/apps/permissions
+ - /rest/reference/permissions-required-for-github-apps
versions:
fpt: '*'
ghes: '*'
diff --git a/translations/pt-BR/content/rest/reference/actions.md b/translations/pt-BR/content/rest/reference/actions.md
index 992cdeebc112..691ef80d14d3 100644
--- a/translations/pt-BR/content/rest/reference/actions.md
+++ b/translations/pt-BR/content/rest/reference/actions.md
@@ -13,93 +13,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-
-A API de {% data variables.product.prodname_actions %} permite que você gerencie {% data variables.product.prodname_actions %} usando a API REST. {% data reusables.actions.actions-authentication %} {% data variables.product.prodname_github_apps %} exige permissões mencionadas em cada ponto de extremidade. Para obter mais informações, consulte "[Documentação do {% data variables.product.prodname_actions %}](/actions)".
-
-{% for operation in currentRestOperations %}
- {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
-{% endfor %}
-
-## Artefatos
-
-A API de Artefatos permite que você faça o download, exclua e recupere informações sobre artefatos de fluxo de trabalho. {% data reusables.actions.about-artifacts %} Para obter mais informações, consulte "[Dados recorrentes do fluxo de trabalho que usam artefatos](/actions/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)".
-
-{% data reusables.actions.actions-authentication %} {% data reusables.actions.actions-app-actions-permissions-api %}
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'artifacts' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% ifversion fpt or ghes > 2.22 or ghae or ghec %}
-## Permissões
-
-A API de Permissões permite que você defina permissões para quais empresas, organizações e repositórios podem executar {% data variables.product.prodname_actions %}, e quais ações podem ser executadas.{% ifversion fpt or ghec or ghes %} Para obter mais informações, consulte "[Limites de uso, cobrança e administração](/actions/reference/usage-limits-billing-and-administration#disabling-or-limiting-github-actions-for-your-repository-or-organization)".{% endif %}
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'permissions' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-{% endif %}
-
-## Segredos
-
-A API Segredos permite criar, atualizar, excluir e recuperar informações sobre segredos criptografados. {% data reusables.actions.about-secrets %} Para obter mais informações, consulte "[Criando e usando segredos encriptados](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)".
-
-{% data reusables.actions.actions-authentication %} {% data variables.product.prodname_github_apps %} deve ter a permissão `segredos` para usar esta API. Os usuários autenticados devem ter acesso de colaborador em um repositório para criar, atualizar ou ler segredos.
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'secrets' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## Executores auto-hospedados
-
-{% data reusables.actions.ae-self-hosted-runners-notice %}
-
-A API de executores auto-hospedados permite que você registre, visualize e exclua executores auto-hospedados. {% data reusables.actions.about-self-hosted-runners %} Para obter mais informações, consulte "[Hospedando seus próprios executores](/actions/hosting-your-own-runners)".
-
-{% data reusables.actions.actions-authentication %} {% data variables.product.prodname_github_apps %} deve ter a permissão de administração `` para repositórios ou a permissão `organization_self_hosted_runners` para as organizações. Os usuários autenticados devem ter acesso de administrador a repositórios ou organizações ou ao escopo `manage_runners:corporativo` para que as empresas usem esta API.
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'self-hosted-runners' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## Grupos de runner auto-hospedados
-
-{% data reusables.actions.ae-self-hosted-runners-notice %}
-
-A API dos Grupos de Runners auto-hospedados permite que você gerencie grupos de runners auto-hospedados. Para obter mais informações, consulte "[Gerenciando acesso a runners auto-hospedados usando grupos](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups)".
-
-{% data reusables.actions.actions-authentication %} {% data variables.product.prodname_github_apps %} deve ter a permissão de administração `` para repositórios ou a permissão `organization_self_hosted_runners` para as organizações. Os usuários autenticados devem ter acesso de administrador a repositórios ou organizações ou ao escopo `manage_runners:corporativo` para que as empresas usem esta API.
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'self-hosted-runner-groups' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## Fluxos de trabalho
-
-A API de fluxos de trabalho permite que você veja fluxos de trabalho para um repositório. {% data reusables.actions.about-workflows %} Para obter mais informações, consulte "[Automatizando seu fluxo de trabalho com o GitHub Actions](/actions/automating-your-workflow-with-github-actions)".
-
-{% data reusables.actions.actions-authentication %} {% data reusables.actions.actions-app-actions-permissions-api %}
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'workflows' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## Trabalhos de fluxo de trabalho
-
-A API de Trabalhos de Fluxo de Trabalho permite que você visualize logs e trabalhos de fluxo de trabalho. {% data reusables.actions.about-workflow-jobs %} Para obter mais informações, consulte "[Sintaxe de fluxo de trabalho para GitHub Actions](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions)".
-
-{% data reusables.actions.actions-authentication %} {% data reusables.actions.actions-app-actions-permissions-api %}
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'workflow-jobs' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## Execução de fluxo de trabalho
-
-A API de execução de fluxo de trabalho permite que você visualize, execute novamente, cancele e visualize os logs para executar o fluxo de trabalho. {% data reusables.actions.about-workflow-runs %} Para obter mais informações, consulte "[Gerenciando uma execução de fluxo de trabalho](/actions/automating-your-workflow-with-github-actions/managing-a-workflow-run)".
-
-{% data reusables.actions.actions-authentication %} {% data reusables.actions.actions-app-actions-permissions-api %}
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'workflow-runs' %}{% include rest_operation %}{% endif %}
-{% endfor %}
+
diff --git a/translations/pt-BR/content/rest/reference/activity.md b/translations/pt-BR/content/rest/reference/activity.md
index 804b4094d240..4cd50bbf17a8 100644
--- a/translations/pt-BR/content/rest/reference/activity.md
+++ b/translations/pt-BR/content/rest/reference/activity.md
@@ -1,6 +1,6 @@
---
-title: Activity
-intro: 'The Activity API allows you to list events and feeds and manage notifications, starring, and watching for the authenticated user.'
+title: Atividade
+intro: 'A API de atividade permite que você liste eventos, alimenta e gerencia notificações, favoritos e inspeciona o usuário autenticado.'
redirect_from:
- /v3/activity
versions:
@@ -13,186 +13,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-{% for operation in currentRestOperations %}
- {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
-{% endfor %}
-
-## Events
-
-The Events API is a read-only API to the {% data variables.product.prodname_dotcom %} events. These events power the various activity streams on the site.
-
-The Events API can return different types of events triggered by activity on {% data variables.product.product_name %}. For more information about the specific events that you can receive from the Events API, see "[{% data variables.product.prodname_dotcom %} Event types](/developers/webhooks-and-events/github-event-types)." An events API for repository issues is also available. For more information, see the "[Issue Events API](/rest/reference/issues#events)."
-
-Events are optimized for polling with the "ETag" header. If no new events have been triggered, you will see a "304 Not Modified" response, and your current rate limit will be untouched. There is also an "X-Poll-Interval" header that specifies how often (in seconds) you are allowed to poll. In times of high server load, the time may increase. Please obey the header.
-
-``` shell
-$ curl -I {% data variables.product.api_url_pre %}/users/tater/events
-> HTTP/2 200
-> X-Poll-Interval: 60
-> ETag: "a18c3bded88eb5dbb5c849a489412bf3"
-
-# The quotes around the ETag value are important
-$ curl -I {% data variables.product.api_url_pre %}/users/tater/events \
-$ -H 'If-None-Match: "a18c3bded88eb5dbb5c849a489412bf3"'
-> HTTP/2 304
-> X-Poll-Interval: 60
-```
-
-Only events created within the past 90 days will be included in timelines. Events older than 90 days will not be included (even if the total number of events in the timeline is less than 300).
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'events' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## Feeds
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'feeds' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-### Example of getting an Atom feed
-
-To get a feed in Atom format, you must specify the `application/atom+xml` type in the `Accept` header. For example, to get the Atom feed for GitHub security advisories:
-
- curl -H "Accept: application/atom+xml" https://github.com/security-advisories
-
-#### Response
-
-```shell
-HTTP/2 200
-```
-
-```xml
-
-
- tag:github.com,2008:/security-advisories
-
- GitHub Security Advisory Feed
-
- GitHub
-
- 2019-01-14T19:34:52Z
-
- tag:github.com,2008:GHSA-abcd-12ab-23cd
- 2018-07-26T15:14:52Z
- 2019-01-14T19:34:52Z
- [GHSA-abcd-12ab-23cd] Moderate severity vulnerability that affects Octoapp
-
-
- <p>Octoapp node module before 4.17.5 suffers from a Modification of Assumed-Immutable Data (MAID) vulnerability via defaultsDeep, merge, and mergeWith functions, which allows a malicious user to modify the prototype of "Object" via <strong>proto</strong>, causing the addition or modification of an existing property that will exist on all objects.</p>
- <p><strong>Affected Packages</strong></p>
-
- <dl>
- <dt>Octoapp</dt>
- <dd>Ecosystem: npm</dd>
- <dd>Severity: moderate</dd>
- <dd>Versions: < 4.17.5</dd>
- <dd>Fixed in: 4.17.5</dd>
- </dl>
-
- <p><strong>References</strong></p>
-
- <ul>
- <li>https://nvd.nist.gov/vuln/detail/CVE-2018-123</li>
- </ul>
-
-
-
-
-```
-
-## Notifications
-
-Users receive notifications for conversations in repositories they watch including:
-
-* Issues and their comments
-* Pull Requests and their comments
-* Comments on any commits
-
-Notifications are also sent for conversations in unwatched repositories when the user is involved including:
-
-* **@mentions**
-* Issue assignments
-* Commits the user authors or commits
-* Any discussion in which the user actively participates
-
-All Notification API calls require the `notifications` or `repo` API scopes. Doing this will give read-only access to some issue and commit content. You will still need the `repo` scope to access issues and commits from their respective endpoints.
-
-Notifications come back as "threads". A thread contains information about the current discussion of an issue, pull request, or commit.
-
-Notifications are optimized for polling with the `Last-Modified` header. If there are no new notifications, you will see a `304 Not Modified` response, leaving your current rate limit untouched. There is an `X-Poll-Interval` header that specifies how often (in seconds) you are allowed to poll. In times of high server load, the time may increase. Please obey the header.
-
-``` shell
-# Add authentication to your requests
-$ curl -I {% data variables.product.api_url_pre %}/notifications
-HTTP/2 200
-Last-Modified: Thu, 25 Oct 2012 15:16:27 GMT
-X-Poll-Interval: 60
-
-# Pass the Last-Modified header exactly
-$ curl -I {% data variables.product.api_url_pre %}/notifications
-$ -H "If-Modified-Since: Thu, 25 Oct 2012 15:16:27 GMT"
-> HTTP/2 304
-> X-Poll-Interval: 60
-```
-
-### Notification reasons
-
-When retrieving responses from the Notifications API, each payload has a key titled `reason`. These correspond to events that trigger a notification.
-
-Here's a list of potential `reason`s for receiving a notification:
-
-Reason Name | Description
-------------|------------
-`assign` | You were assigned to the issue.
-`author` | You created the thread.
-`comment` | You commented on the thread.
-`ci_activity` | A {% data variables.product.prodname_actions %} workflow run that you triggered was completed.
-`invitation` | You accepted an invitation to contribute to the repository.
-`manual` | You subscribed to the thread (via an issue or pull request).
-`mention` | You were specifically **@mentioned** in the content.
-`review_requested` | You, or a team you're a member of, were requested to review a pull request.{% ifversion fpt or ghec %}
-`security_alert` | {% data variables.product.prodname_dotcom %} discovered a [security vulnerability](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies) in your repository.{% endif %}
-`state_change` | You changed the thread state (for example, closing an issue or merging a pull request).
-`subscribed` | You're watching the repository.
-`team_mention` | You were on a team that was mentioned.
-
-Note that the `reason` is modified on a per-thread basis, and can change, if the `reason` on a later notification is different.
-
-For example, if you are the author of an issue, subsequent notifications on that issue will have a `reason` of `author`. If you're then **@mentioned** on the same issue, the notifications you fetch thereafter will have a `reason` of `mention`. The `reason` remains as `mention`, regardless of whether you're ever mentioned again.
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'notifications' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## Starring
-
-Repository starring is a feature that lets users bookmark repositories. Stars are shown next to repositories to show an approximate level of interest. Stars have no effect on notifications or the activity feed.
-
-### Starring vs. Watching
-
-In August 2012, we [changed the way watching
-works](https://github.com/blog/1204-notifications-stars) on {% data variables.product.prodname_dotcom %}. Many API
-client applications may be using the original "watcher" endpoints for accessing
-this data. You can now start using the "star" endpoints instead (described
-below). For more information, see the [Watcher API Change post](https://developer.github.com/changes/2012-09-05-watcher-api/) and the "[Repository Watching API](/rest/reference/activity#watching)."
-
-### Custom media types for starring
-
-There is one supported custom media type for the Starring REST API. When you use this custom media type, you will receive a response with the `starred_at` timestamp property that indicates the time the star was created. The response also has a second property that includes the resource that is returned when the custom media type is not included. The property that contains the resource will be either `user` or `repo`.
-
- application/vnd.github.v3.star+json
-
-For more information about media types, see "[Custom media types](/rest/overview/media-types)."
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'starring' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## Watching
-
-Watching a repository registers the user to receive notifications on new discussions, as well as events in the user's activity feed. For simple repository bookmarks, see "[Repository starring](/rest/reference/activity#starring)."
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'watching' %}{% include rest_operation %}{% endif %}
-{% endfor %}
+
diff --git a/translations/pt-BR/content/rest/reference/apps.md b/translations/pt-BR/content/rest/reference/apps.md
index c0411304411e..4d7fcd8aa101 100644
--- a/translations/pt-BR/content/rest/reference/apps.md
+++ b/translations/pt-BR/content/rest/reference/apps.md
@@ -13,66 +13,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-{% data reusables.apps.general-apps-restrictions %}
-
-Esta página lista os pontos de extremidade que você pode acessar enquanto autenticado como um aplicativo GitHub. Consulte "[Efetuar a autenticação como um aplicativo GitHub](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-a-github-app)" para saber mais.
-
-Quando autenticado como um aplicativo GitHub, a API dos aplicativos GitHub permite que você obtenha informações de alto nível sobre um aplicativo GitHub, bem como informações específicas sobre instalações de um aplicativo.
-
-Você pode acessar os pontos de extremidade da API v3 de REST enquanto autenticado como um aplicativo GitHub. Estes pontos de extremidade têm uma seção de "Observação" que contém um ponto que diz "Funciona com aplicativos GitHub". Você também pode acessar esses pontos de extremidade enquanto estiver autenticado como usuário.
-
-Um subconjunto de pontos de extremidade da API v2 de REST exige autenticação como uma instalação do aplicativo GitHub. Consulte [Instalações](/rest/reference/apps#installations) para obter uma lista desses pontos de extremidade.
-
-{% for operation in currentRestOperations %}
- {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
-{% endfor %}
-
-## API de aplicativos do OAuth
-
-Você pode usar esta API para gerenciar os tokens do OAuth que um aplicativo OAuth usa para acessar as contas das pessoas em {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}.
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'oauth-applications' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## Instalações
-
-A API de instalações permite que você obtenha informações sobre as instalações do seu aplicativo GitHub e execute ações nessas instalações. Uma _instalação_ refere-se a qualquer usuário ou conta de organização que instalou o aplicativo. Para obter informações sobre como efetuar a autenticação como uma instalação e limitar o acesso a repositórios específicos, consulte "[Efetuar a autenticação como uma instalação](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation)".
-
-Para listar todas as instalações do aplicativo GitHub para uma organização, consulte "[Listar instalações de aplicativos para uma organização](/rest/reference/orgs#list-app-installations-for-an-organization)".
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'installations' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% ifversion fpt or ghec %}
-## Marketplace
-
-Para obter mais informações sobre {% data variables.product.prodname_marketplace %}, consulte "[GitHub Marketplace](/marketplace/)".
-
-A API de {% data variables.product.prodname_marketplace %} permite que você veja quais clientes estão usando um plano de preços, as compras de um cliente e se uma conta tem uma assinatura ativa.
-
-### Fazer testes com pontos de extremidades de amostra
-
-Esta API inclui pontos de extremidade que permitem que você [teste o seu {% data variables.product.prodname_github_app %}](/marketplace/integrating-with-the-github-marketplace-api/testing-github-marketplace-apps/) com **dados de amostra**. Os dados do de amostra têm código rígido, dados falsos e não serão alterados com base em assinaturas reais.
-
-Para fazer teste com dados de amostra, use um pontos de extremidade de amostra no lugar da sua contraparte de produção. Isso permite que você teste se a lógica da API é bem-sucedida antes de anunciar {% data variables.product.prodname_github_apps %} em {% data variables.product.prodname_marketplace %}.
-
-Certifique-se de substituir pontos de extremidades de amostra pelos pontos de extremidades de produção antes de implantar seu {% data variables.product.prodname_github_app %}.
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'marketplace' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% endif %}
-
-{% ifversion fpt or ghes > 2.22 or ghae or ghec %}
-## Webhooks
-
-O webhook de {% data variables.product.prodname_github_app %} permite que você receba cargas `POST` de HTTP sempre que certos eventos ocorrerem para um aplicativo. {% data reusables.webhooks.webhooks-rest-api-links %}
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'webhooks' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% endif %}
+
diff --git a/translations/pt-BR/content/rest/reference/billing.md b/translations/pt-BR/content/rest/reference/billing.md
index 5cd7d7d8d5f6..9edb8371d686 100644
--- a/translations/pt-BR/content/rest/reference/billing.md
+++ b/translations/pt-BR/content/rest/reference/billing.md
@@ -10,8 +10,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-Você pode obter informações de cobrança para uma empresa. Para obter mais informações, consulte a API REST "[{% data variables.product.prodname_dotcom %} administração de Enterprise](/rest/reference/enterprise-admin#billing)".
-
-{% for operation in currentRestOperations %}
- {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
-{% endfor %}
+
diff --git a/translations/pt-BR/content/rest/reference/branches.md b/translations/pt-BR/content/rest/reference/branches.md
index ebb377795fc5..59241aa8809a 100644
--- a/translations/pt-BR/content/rest/reference/branches.md
+++ b/translations/pt-BR/content/rest/reference/branches.md
@@ -12,11 +12,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-{% for operation in currentRestOperations %}
- {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
-{% endfor %}
-
-## Branches protegidos
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'branch-protection' %}{% include rest_operation %}{% endif %}
-{% endfor %}
+
diff --git a/translations/pt-BR/content/rest/reference/checks.md b/translations/pt-BR/content/rest/reference/checks.md
index 46ca73a48518..0188f9d76667 100644
--- a/translations/pt-BR/content/rest/reference/checks.md
+++ b/translations/pt-BR/content/rest/reference/checks.md
@@ -13,26 +13,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-Você pode criar os aplicativos que realizam integração contínua, linting ou serviços de varredura de código e fornecem feedback detalhado sobre commits. Para mais informações, consulte "[Começar com a API de verificações](/rest/guides/getting-started-with-the-checks-api)" e "[Criar testes de CI com a API de verificações](/apps/quickstart-guides/creating-ci-tests-with-the-checks-api/)".
-
-{% for operation in currentRestOperations %}
- {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
-{% endfor %}
-
-## Execuções de verificação
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'runs' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## conjuntos de verificações
-
-{% note %}
-
- **Observação:** Um aplicativo GitHub recebe apenas um evento [`check_suite`](/webhooks/event-payloads/#check_suite) por SHA de commit SHA, mesmo se você fizer push do SHA do commit para mais de um branch. Para descobrir quando um SHA do commit é enviado para um branch, você pode assinar os eventos do branch [`criar`](/webhooks/event-payloads/#create).
-
-{% endnote %}
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'suites' %}{% include rest_operation %}{% endif %}
-{% endfor %}
+
diff --git a/translations/pt-BR/content/rest/reference/code-scanning.md b/translations/pt-BR/content/rest/reference/code-scanning.md
index d71197479694..50021c48d590 100644
--- a/translations/pt-BR/content/rest/reference/code-scanning.md
+++ b/translations/pt-BR/content/rest/reference/code-scanning.md
@@ -17,20 +17,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-{% data reusables.code-scanning.beta %}
-
-A API de {% data variables.product.prodname_code_scanning %} permite que você recupere e atualize alertas de {% data variables.product.prodname_code_scanning %} alertas de um repositório. Você pode usar os pontos de extremidade para criar relatórios automatizados para os alertas de {% data variables.product.prodname_code_scanning %} em uma organização ou fazer upload dos resultados de análise gerados usando as ferramentas off-line de {% data variables.product.prodname_code_scanning %}. Para obter mais informações, consulte "[Encontrar vulnerabilidades e erros de segurança no seu código](/github/finding-security-vulnerabilities-and-errors-in-your-code).
-
-{% ifversion fpt or ghes > 3.0 or ghae or ghec %}
-### Tipo de mídia personalizada para {% data variables.product.prodname_code_scanning %}
-
-Existe um tipo de mídia personalizada com suporte para a API REST de {% data variables.product.prodname_code_scanning %}.
-
- application/sarif+json
-
-Você pode usar isso com solicitações de `GET` enviadas para o ponto de extremidade `/analyes/{analysis_id}`. Para obter mais informações sobre esta operação, consulte "[Obter uma análise de {% data variables.product.prodname_code_scanning %} para um repositório](#get-a-code-scanning-analysis-for-a-repository)". Ao usar este tipo de mídia com esta operação, a resposta inclui um subconjunto dos dados reais que foram enviados para a análise especificada, em vez do resumo da análise que é retornada quando você usa o tipo de mídia padrão. A resposta também inclui dados adicionais como as propriedades `github/alertNumber` e `github/alertUrl`. Os dados estão formatados como [SARIF versão 2.1.0](https://docs.oasis-open.org/sarif/sarif/v2.1.0/cs01/sarif-v2.1.0-cs01.html).
-
-Para obter mais informações, consulte "[Tipos de mídia](/rest/overview/media-types)".
-{% endif %}
-
-{% include rest_operations_at_current_path %}
+
diff --git a/translations/pt-BR/content/rest/reference/codes-of-conduct.md b/translations/pt-BR/content/rest/reference/codes-of-conduct.md
index eec4ad3abaf6..1b2304f09423 100644
--- a/translations/pt-BR/content/rest/reference/codes-of-conduct.md
+++ b/translations/pt-BR/content/rest/reference/codes-of-conduct.md
@@ -14,6 +14,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-Você pode usar a API de Códigos de Conduta para recuperar informações sobre o código de conduta de um repositório. Para obter o código de conduta de um repositório, use o ponto de extremidade "[Obter um repositório](/rest/reference/repos#get-a-repository).
-
-{% include rest_operations_at_current_path %}
+
diff --git a/translations/pt-BR/content/rest/reference/codespaces.md b/translations/pt-BR/content/rest/reference/codespaces.md
index 79373723caf7..2db1a5092f78 100644
--- a/translations/pt-BR/content/rest/reference/codespaces.md
+++ b/translations/pt-BR/content/rest/reference/codespaces.md
@@ -10,24 +10,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-{% data reusables.codespaces.codespaces-api-beta-note %}
-
-A API de {% data variables.product.prodname_codespaces %} permite que você gerencie {% data variables.product.prodname_codespaces %} usando a API REST. Esta API está disponível para usuários autenticados e aplicativos OAuth, mas não para aplicativos GitHub. Para obter mais informações, consulte "[{% data variables.product.prodname_codespaces %}](/codespaces)".
-
-{% for operation in currentRestOperations %}
- {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
-{% endfor %}
-
-## Máquinas
-A API de Máquinas permite que um usuário determine quais tipos de máquina estão disponíveis para criar um codespace, seja em um determinado repositório ou como um usuário autenticado. Para obter mais informações, consulte "[Sobre tipos de máquinas](/codespaces/developing-in-codespaces/changing-the-machine-type-for-your-codespace#about-machine-types)".
-
-Você também pode usar essas informações alterando a máquina de um codespace existente, atualizando a propriedade `máquina`. A atualização da máquina ocorrerá na próxima vez que o codespace for reiniciado. Para obter mais informações, consulte "["Mudar o tipo de máquina para seu codespace](/codespaces/developing-in-codespaces/changing-the-machine-type-for-your-codespace)."
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'machines' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## Segredos
-A API de Segredos permite que um usuário crie, liste e exclua segredos (como tokens de acesso para serviços de nuvem), além de atribuir segredos para repositórios aos quais o usuário tem acesso. Estes segredos são disponibilizados para o codespace em tempo de execução. Para obter mais informações, consulte "[Gerenciar segredos criptografados para seus codespaces](/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces)".
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'secrets' %}{% include rest_operation %}{% endif %}
-{% endfor %}
+
diff --git a/translations/pt-BR/content/rest/reference/collaborators.md b/translations/pt-BR/content/rest/reference/collaborators.md
index a8e6988000bd..dd57a139e315 100644
--- a/translations/pt-BR/content/rest/reference/collaborators.md
+++ b/translations/pt-BR/content/rest/reference/collaborators.md
@@ -12,20 +12,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-{% for operation in currentRestOperations %}
- {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
-{% endfor %}
-
-## Convites
-
-A API de Convites do Repositório permite que usuários ou serviços externos convidem outros usuários para colaborar em um repositório. Os usuários convidados (ou serviços externos em nome dos usuários convidados) podem optar por aceitar ou recusar os convites.
-
-Observe que o [Escopo OAuth](/developers/apps/scopes-for-oauth-apps) `repo:invite` concede acesso direcionado aos convites **sem** conceder também acesso ao código do repositório. enquanto o escopo `repo` concede permissão ao código e aos convites convites.
-
-### Convidar um usuário para um repositório
-
-Use o ponto de extremidade da API para adicionar um colaborador. Para obter mais informações, consulte "[Adicionar um colaborador de repositório](/rest/reference/collaborators#add-a-repository-collaborator)".
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'invitations' %}{% include rest_operation %}{% endif %}
-{% endfor %}
+
diff --git a/translations/pt-BR/content/rest/reference/commits.md b/translations/pt-BR/content/rest/reference/commits.md
index 280c43423439..2420044d3443 100644
--- a/translations/pt-BR/content/rest/reference/commits.md
+++ b/translations/pt-BR/content/rest/reference/commits.md
@@ -12,41 +12,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-{% for operation in currentRestOperations %}
- {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
-{% endfor %}
-
-## Comentários de commit
-
-### Tipos de mídia personalizados para comentários de commit
-
-Estes são os tipos de mídia compatíveis com os comentários do commit. Você pode ler mais sobre o uso de tipos de mídia na API [aqui](/rest/overview/media-types).
-
- application/vnd.github-commitcomment.raw+json
- application/vnd.github-commitcomment.text+json
- application/vnd.github-commitcomment.html+json
- application/vnd.github-commitcomment.full+json
-
-Para obter mais informações, consulte "[tipos de mídia personalizados](/rest/overview/media-types)".
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'comments' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## Status do commit
-
-A API de status permite que serviços externos marquem commits com status de `erro`, `falha`, `pendente` ou `sucesso`, o que é refletido em pull requests que envolvem esses commits.
-
-Os status também podem incluir uma `descrição` opcional e `target_url`, e é altamente recomendável fornecê-los, pois tornam o status muito mais útil na interface de usuário do GitHub.
-
-Como exemplo, um uso comum é para serviços de integração contínua para marcar commits como criações que passam ou que falham usando o status. O `target_url` seria a URL completa para a saída da criação, e a `descrição` seria o resumo de alto nível do que aconteceu com a criação.
-
-Os status podem incluir um `contexto` para indicar qual serviço está fornecendo esse status. Por exemplo, você pode fazer com que o seu serviço de integração contínua faça push status com um contexto de `ci`, e uma ferramenta de auditoria de segurança faça push dos status com um contexto de `segurança`. Você pode usar [Obter o status combinado para uma referência específica](/rest/reference/commits#get-the-combined-status-for-a-specific-reference) para recuperar todo o status de um commit.
-
-Observe que o `escopo do OAuth` [repo:status](/developers/apps/scopes-for-oauth-apps) concede acesso direcionado a status **sem** conceder acesso ao código do repositório, enquanto o escopo `repo` concede permissão para o código e para status.
-
-Se você está desenvolvendo um aplicativo GitHub e deseja fornecer informações mais detalhadas sobre um serviço externo, você deverá usar a [API de verificação](/rest/reference/checks).
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'statuses' %}{% include rest_operation %}{% endif %}
-{% endfor %}
+
diff --git a/translations/pt-BR/content/rest/reference/dependabot.md b/translations/pt-BR/content/rest/reference/dependabot.md
index a3c3ae918dad..c04bd788816e 100644
--- a/translations/pt-BR/content/rest/reference/dependabot.md
+++ b/translations/pt-BR/content/rest/reference/dependabot.md
@@ -10,10 +10,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-A API de segredos {% data variables.product.prodname_dependabot %} permite criar, atualizar, excluir e recuperar informações sobre segredos criptografados. {% data reusables.actions.about-secrets %} Para obter mais informações, consulte "[Gerenciar segredos criptografados para o dependabot](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-encrypted-secrets-for-dependabot)."
-
-{% data reusables.actions.actions-authentication %} {% data variables.product.prodname_github_apps %} deve ter a permissão `dependabot_secrets` para usar esta API. Os usuários autenticados devem ter acesso de colaborador em um repositório para criar, atualizar ou ler segredos.
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'secrets' %}{% include rest_operation %}{% endif %}
-{% endfor %}
+
diff --git a/translations/pt-BR/content/rest/reference/deployments.md b/translations/pt-BR/content/rest/reference/deployments.md
index 60a7def46c41..e3455e2c4056 100644
--- a/translations/pt-BR/content/rest/reference/deployments.md
+++ b/translations/pt-BR/content/rest/reference/deployments.md
@@ -12,81 +12,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-As implantações são solicitações para implantar um ref específico (branch, SHA, tag). O GitHub envia um [ evento de `implantação`](/developers/webhooks-and-events/webhook-events-and-payloads#deployment) pelo qual os serviços externos podem ouvir e atuar quando novas implantações são criadas. As implantações permitem que os desenvolvedores e as organizações construam ferramentas associadas em torno de implantações sem ter que se preocupar com os detalhes de implementação da entrega de diferentes tipos de aplicativos (p. ex., web, nativo).
-
-Os status de implantação externos permitem marcar implantações com `error`, `failure`, `pending`, `in_progress`, `queued` ou `success` afirmar que os sistemas que estão escutando os eventos [`deployment_status`](/developers/webhooks-and-events/webhook-events-and-payloads#deployment_status) podem consumir.
-
-Os status de implantação também podem incluir uma `descrição` opcional e `log_url`, que são altamente recomendados porque tornam o status de implantação mais útil. O `log_url` é a URL completa para a saída de implantação e a `descrição` é um resumo de alto nível do que aconteceu com a implantação.
-
-O GitHub envia os eventos de `implantação` e `deployment_status` quando novas implantações de status de implantação são criadas. Esses eventos permitem que as integrações de terceiros recebam resposta para solicitações de implantação e atualizem o status de implantação conforme o progresso é feito.
-
-Abaixo está um diagrama de sequência sobre para como essas interações funcionariam.
-
-```
-+---------+ +--------+ +-----------+ +-------------+
-| Tooling | | GitHub | | 3rd Party | | Your Server |
-+---------+ +--------+ +-----------+ +-------------+
- | | | |
- | Create Deployment | | |
- |--------------------->| | |
- | | | |
- | Deployment Created | | |
- |<---------------------| | |
- | | | |
- | | Deployment Event | |
- | |---------------------->| |
- | | | SSH+Deploys |
- | | |-------------------->|
- | | | |
- | | Deployment Status | |
- | |<----------------------| |
- | | | |
- | | | Deploy Completed |
- | | |<--------------------|
- | | | |
- | | Deployment Status | |
- | |<----------------------| |
- | | | |
-```
-
-Tenha em mente que o GitHub nunca terá acesso aos seus servidores. Cabe à sua integração de terceiros interagir com os eventos de implantação. Vários sistemas podem ouvir eventos de implantação, e cabe a cada um desses sistemas decidir se serão responsáveis por retirar o código dos seus servidores, criar código nativo, etc.
-
-Observe que o `repo_deployment` [OAuth escopo](/developers/apps/scopes-for-oauth-apps) concede acesso direcionado a implantações e status **sem** conceder acesso ao código do repositório, enquanto os es escopos {% ifversion not ghae %}`public_repo` e{% endif %}`repositório` também concedem permissão para codificar.
-
-### Implantações inativas
-
-Ao definir o estado de uma implantação como `sucesso`, todas as implantações de ambiente de não produção e não transitórios anteriores no mesmo nome do ambiente irão tornar-se `inativas`. Para evitar isso, você pode definir `auto_inactive` como `falso` ao criar o status de implantação.
-
-Você pode informar que um ambiente transitório não existe mais definindo seu `estado` como `inativo`. Definir o `estado` como `inativo` mostra a implantação como `destruída` em {% data variables.product.prodname_dotcom %} e remove o acesso a ela.
-
-{% for operation in currentRestOperations %}
- {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
-{% endfor %}
-
-## Status da implantação
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'statuses' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## Chaves de implantação
-
-{% data reusables.repositories.deploy-keys %}
-
-Chaves de implantação podem ser configuradas usando os seguintes pontos de extremidades da API ou usando o GitHub. Para saber como configurar as chaves de implantação no GitHub, consulte "[Gerenciar chaves de implantação](/developers/overview/managing-deploy-keys)".
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'keys' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
-## Ambientes
-
-A API de Ambientes permite que você crie, configure e exclua ambientes. Para obter mais informações sobre ambientes, consulte "[Usando ambientes para implantação](/actions/deployment/using-environments-for-deployment)". Para gerenciar segredos de ambiente, consulte "[Segredos](/rest/reference/actions#secrets)".
-
-{% data reusables.gated-features.environments %}
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'environments' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-{% endif %}
+
diff --git a/translations/pt-BR/content/rest/reference/emojis.md b/translations/pt-BR/content/rest/reference/emojis.md
index 8e5f2a6dd460..be8029dfda91 100644
--- a/translations/pt-BR/content/rest/reference/emojis.md
+++ b/translations/pt-BR/content/rest/reference/emojis.md
@@ -14,4 +14,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-{% include rest_operations_at_current_path %}
+
diff --git a/translations/pt-BR/content/rest/reference/enterprise-admin.md b/translations/pt-BR/content/rest/reference/enterprise-admin.md
index 303f997677e8..c1f2d237c5fd 100644
--- a/translations/pt-BR/content/rest/reference/enterprise-admin.md
+++ b/translations/pt-BR/content/rest/reference/enterprise-admin.md
@@ -16,309 +16,6 @@ miniTocMaxHeadingLevel: 3
shortTitle: Enterprise administration
---
-{% ifversion fpt or ghec %}
-
-{% note %}
-
-**Note:** This article applies to {% data variables.product.prodname_ghe_cloud %}. To see the {% data variables.product.prodname_ghe_managed %} or {% data variables.product.prodname_ghe_server %} version, use the **{% data ui.pages.article_version %}** drop-down menu.
-
-{% endnote %}
-
-{% endif %}
-
-### Endpoint URLs
-
-REST API endpoints{% ifversion ghes %}—except [Management Console](#management-console) API endpoints—{% endif %} are prefixed with the following URL:
-
-```shell
-{% data variables.product.api_url_pre %}
-```
-
-{% ifversion fpt or ghec %}
-When endpoints include `{enterprise}`, replace `{enterprise}` with the handle for your enterprise account, which is included in the URL for your enterprise settings. For example, if your enterprise account is located at `https://github.com/enterprises/octo-enterprise`, replace `{enterprise}` with `octo-enterprise`.
-{% endif %}
-
-{% ifversion ghes %}
-[Management Console](#management-console) API endpoints are only prefixed with a hostname:
-
-```shell
-http(s)://hostname/
-```
-{% endif %}
-{% ifversion ghae or ghes %}
-### Authentication
-
-Your {% data variables.product.product_name %} installation's API endpoints accept [the same authentication methods](/rest/overview/resources-in-the-rest-api#authentication) as the GitHub.com API. You can authenticate yourself with **[OAuth tokens](/apps/building-integrations/setting-up-and-registering-oauth-apps/)** {% ifversion ghes %}(which can be created using the [Authorizations API](/rest/reference/oauth-authorizations#create-a-new-authorization)) {% endif %}or **[basic authentication](/rest/overview/resources-in-the-rest-api#basic-authentication)**. {% ifversion ghes %}
-OAuth tokens must have the `site_admin` [OAuth scope](/developers/apps/scopes-for-oauth-apps#available-scopes) when used with Enterprise-specific endpoints.{% endif %}
-
-Enterprise administration API endpoints are only accessible to authenticated {% data variables.product.product_name %} site administrators{% ifversion ghes %}, except for the [Management Console](#management-console) API, which requires the [Management Console password](/enterprise/admin/articles/accessing-the-management-console/){% endif %}.
-
-{% endif %}
-
-{% ifversion ghae or ghes %}
-### Version information
-
-The current version of your enterprise is returned in the response header of every API:
-`X-GitHub-Enterprise-Version: {{currentVersion}}.0`
-You can also read the current version by calling the [meta endpoint](/rest/reference/meta/).
-
-{% for operation in currentRestOperations %}
- {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
-{% endfor %}
-
-{% endif %}
-
-{% ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5528 %}
-
-## Audit log
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'audit-log' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% endif %}
-
-{% ifversion fpt or ghec or ghes > 3.3 %}
-## Billing
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'billing' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% endif %}
-
-{% ifversion ghae or ghes %}
-## Admin stats
-
-The Admin Stats API provides a variety of metrics about your installation. *It is only available to [authenticated](/rest/overview/resources-in-the-rest-api#authentication) site administrators.* Normal users will receive a `404` response if they try to access it.
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'admin-stats' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% endif %}
-
-{% ifversion ghae or ghes > 2.22 %}
-
-## Announcements
-
-The Announcements API allows you to manage the global announcement banner in your enterprise. For more information, see "[Customizing user messages for your enterprise](/admin/user-management/customizing-user-messages-for-your-enterprise#creating-a-global-announcement-banner)."
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'announcement' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% endif %}
-
-{% ifversion ghae or ghes %}
-
-## Global webhooks
-
-Global webhooks are installed on your enterprise. You can use global webhooks to automatically monitor, respond to, or enforce rules for users, organizations, teams, and repositories on your enterprise. Global webhooks can subscribe to the [organization](/developers/webhooks-and-events/webhook-events-and-payloads#organization), [user](/developers/webhooks-and-events/webhook-events-and-payloads#user), [repository](/developers/webhooks-and-events/webhook-events-and-payloads#repository), [team](/developers/webhooks-and-events/webhook-events-and-payloads#team), [member](/developers/webhooks-and-events/webhook-events-and-payloads#member), [membership](/developers/webhooks-and-events/webhook-events-and-payloads#membership), [fork](/developers/webhooks-and-events/webhook-events-and-payloads#fork), and [ping](/developers/webhooks-and-events/about-webhooks#ping-event) event types.
-
-*This API is only available to [authenticated](/rest/overview/resources-in-the-rest-api#authentication) site administrators.* Normal users will receive a `404` response if they try to access it. To learn how to configure global webhooks, see [About global webhooks](/enterprise/admin/user-management/about-global-webhooks).
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'global-webhooks' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% endif %}
-
-{% ifversion ghes %}
-
-## LDAP
-
-You can use the LDAP API to update account relationships between a {% data variables.product.product_name %} user or team and its linked LDAP entry or queue a new synchronization.
-
-With the LDAP mapping endpoints, you're able to update the Distinguished Name (DN) that a user or team maps to. Note that the LDAP endpoints are generally only effective if your {% data variables.product.product_name %} appliance has [LDAP Sync enabled](/enterprise/admin/authentication/using-ldap). The [Update LDAP mapping for a user](#update-ldap-mapping-for-a-user) endpoint can be used when LDAP is enabled, even if LDAP Sync is disabled.
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'ldap' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% endif %}
-
-{% ifversion ghae or ghes %}
-## License
-
-The License API provides information on your Enterprise license. *It is only available to [authenticated](/rest/overview/resources-in-the-rest-api#authentication) site administrators.* Normal users will receive a `404` response if they try to access it.
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'license' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% endif %}
-
-{% ifversion ghes %}
-
-## Management console
-
-The Management Console API helps you manage your {% data variables.product.product_name %} installation.
-
-{% tip %}
-
-You must explicitly set the port number when making API calls to the Management Console. If TLS is enabled on your enterprise, the port number is `8443`; otherwise, the port number is `8080`.
-
-If you don't want to provide a port number, you'll need to configure your tool to automatically follow redirects.
-
-You may also need to add the [`-k` flag](http://curl.haxx.se/docs/manpage.html#-k) when using `curl`, since {% data variables.product.product_name %} uses a self-signed certificate before you [add your own TLS certificate](/enterprise/admin/guides/installation/configuring-tls/).
-
-{% endtip %}
-
-### Authentication
-
-You need to pass your [Management Console password](/enterprise/admin/articles/accessing-the-management-console/) as an authentication token to every Management Console API endpoint except [`/setup/api/start`](#create-a-github-enterprise-server-license).
-
-Use the `api_key` parameter to send this token with each request. For example:
-
-```shell
-$ curl -L 'https://hostname:admin_port/setup/api?api_key=your-amazing-password'
-```
-
-You can also use standard HTTP authentication to send this token. For example:
-
-```shell
-$ curl -L -u "api_key:your-amazing-password" 'https://hostname:admin_port/setup/api'
-```
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'management-console' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% endif %}
-
-{% ifversion ghae or ghes %}
-## Organizations
-
-The Organization Administration API allows you to create organizations on your enterprise. *It is only available to [authenticated](/rest/overview/resources-in-the-rest-api#authentication) site administrators.* Normal users will receive a `404` response if they try to access it.
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'orgs' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% endif %}
-
-{% ifversion ghes %}
-## Organization pre-receive hooks
-
-The Organization Pre-receive Hooks API allows you to view and modify
-enforcement of the pre-receive hooks that are available to an organization.
-
-### Object attributes
-
-| Name | Type | Description |
-|----------------------------------|-----------|-----------------------------------------------------------|
-| `name` | `string` | The name of the hook. |
-| `enforcement` | `string` | The state of enforcement for the hook on this repository. |
-| `allow_downstream_configuration` | `boolean` | Whether repositories can override enforcement. |
-| `configuration_url` | `string` | URL for the endpoint where enforcement is set. |
-
-Possible values for *enforcement* are `enabled`, `disabled` and`testing`. `disabled` indicates the pre-receive hook will not run. `enabled` indicates it will run and reject
-any pushes that result in a non-zero status. `testing` means the script will run but will not cause any pushes to be rejected.
-
-`configuration_url` may be a link to this endpoint or this hook's global
-configuration. Only site admins are able to access the global configuration.
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'org-pre-receive-hooks' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% endif %}
-
-{% ifversion ghes %}
-
-## Pre-receive environments
-
-The Pre-receive Environments API allows you to create, list, update and delete environments for pre-receive hooks. *It is only available to [authenticated](/rest/overview/resources-in-the-rest-api#authentication) site administrators.* Normal users will receive a `404` response if they try to access it.
-
-### Object attributes
-
-#### Pre-receive Environment
-
-| Name | Type | Description |
-|-----------------------|-----------|----------------------------------------------------------------------------|
-| `name` | `string` | The name of the environment as displayed in the UI. |
-| `image_url` | `string` | URL to the tarball that will be downloaded and extracted. |
-| `default_environment` | `boolean` | Whether this is the default environment that ships with {% data variables.product.product_name %}. |
-| `download` | `object` | This environment's download status. |
-| `hooks_count` | `integer` | The number of pre-receive hooks that use this environment. |
-
-#### Pre-receive Environment Download
-
-| Name | Type | Description |
-|-----------------|----------|---------------------------------------------------------|
-| `state` | `string` | The state of the most recent download. |
-| `downloaded_at` | `string` | The time when the most recent download started. |
-| `message` | `string` | On failure, this will have any error messages produced. |
-
-Possible values for `state` are `not_started`, `in_progress`, `success`, `failed`.
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'pre-receive-environments' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% endif %}
-
-{% ifversion ghes %}
-## Pre-receive hooks
-
-The Pre-receive Hooks API allows you to create, list, update and delete pre-receive hooks. *It is only available to
-[authenticated](/rest/overview/resources-in-the-rest-api#authentication) site administrators.* Normal users will receive a `404` response if they try to access it.
-
-### Object attributes
-
-#### Pre-receive Hook
-
-| Name | Type | Description |
-|----------------------------------|-----------|-----------------------------------------------------------------|
-| `name` | `string` | The name of the hook. |
-| `script` | `string` | The script that the hook runs. |
-| `script_repository` | `object` | The GitHub repository where the script is kept. |
-| `environment` | `object` | The pre-receive environment where the script is executed. |
-| `enforcement` | `string` | The state of enforcement for this hook. |
-| `allow_downstream_configuration` | `boolean` | Whether enforcement can be overridden at the org or repo level. |
-
-Possible values for *enforcement* are `enabled`, `disabled` and`testing`. `disabled` indicates the pre-receive hook will not run. `enabled` indicates it will run and reject
-any pushes that result in a non-zero status. `testing` means the script will run but will not cause any pushes to be rejected.
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'pre-receive-hooks' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% endif %}
-
-{% ifversion ghes %}
-
-## Repository pre-receive hooks
-
-The Repository Pre-receive Hooks API allows you to view and modify
-enforcement of the pre-receive hooks that are available to a repository.
-
-### Object attributes
-
-| Name | Type | Description |
-|---------------------|----------|-----------------------------------------------------------|
-| `name` | `string` | The name of the hook. |
-| `enforcement` | `string` | The state of enforcement for the hook on this repository. |
-| `configuration_url` | `string` | URL for the endpoint where enforcement is set. |
-
-Possible values for *enforcement* are `enabled`, `disabled` and`testing`. `disabled` indicates the pre-receive hook will not run. `enabled` indicates it will run and reject any pushes that result in a non-zero status. `testing` means the script will run but will not cause any pushes to be rejected.
-
-`configuration_url` may be a link to this repository, it's organization owner or global configuration. Authorization to access the endpoint at `configuration_url` is determined at the owner or site admin level.
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'repo-pre-receive-hooks' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% endif %}
-
-{% ifversion ghae or ghes %}
-## Users
-
-The User Administration API allows you to suspend{% ifversion ghes %}, unsuspend, promote, and demote{% endif %}{% ifversion ghae %} and unsuspend{% endif %} users on your enterprise. *It is only available to [authenticated](/rest/overview/resources-in-the-rest-api#authentication) site administrators.* Normal users will receive a `403` response if they try to access it.
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'users' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% endif %}
+
\ No newline at end of file
diff --git a/translations/pt-BR/content/rest/reference/gists.md b/translations/pt-BR/content/rest/reference/gists.md
index 8792ea924206..7bc85d1badb8 100644
--- a/translations/pt-BR/content/rest/reference/gists.md
+++ b/translations/pt-BR/content/rest/reference/gists.md
@@ -13,44 +13,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-### Authentication
-
-You can read public gists {% ifversion ghae or ghes %}and create them for anonymous users without a token.{% else %} anonymously, but you must be signed into GitHub to create gists.{% endif %} To read or write gists on a user's behalf, you need the gist OAuth scope and a token. For more information, see "[Scopes for OAuth Apps](/developers/apps/scopes-for-oauth-apps)."
-
-
-
-### Truncation
-
-The Gist API provides up to one megabyte of content for each file in the gist. Each file returned for a gist through the API has a key called `truncated`. If `truncated` is `true`, the file is too large and only a portion of the contents were returned in `content`.
-
-If you need the full contents of the file, you can make a `GET` request to the URL specified by `raw_url`. Be aware that for files larger than ten megabytes, you'll need to clone the gist via the URL provided by `git_pull_url`.
-
-In addition to a specific file's contents being truncated, the entire files list may be truncated if the total number exceeds 300 files. If the top level `truncated` key is `true`, only the first 300 files have been returned in the files list. If you need to fetch all of the gist's files, you'll need to clone the gist via the URL provided by `git_pull_url`.
-
-### Custom media types for gists
-
-These are the supported media types for fetching gist contents.
-
- application/vnd.github.VERSION.raw
- application/vnd.github.VERSION.base64
-
-For more information, see "[Media types](/rest/overview/media-types)."
-
-{% for operation in currentRestOperations %}
- {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
-{% endfor %}
-
-## Comments
-
-### Custom media types for Gist comments
-
-These are the supported media types for gist comments.
-
- application/vnd.github.VERSION.raw
- application/vnd.github.VERSION.base64
-
-For more information about media types, see "[Custom media types](/rest/overview/media-types)."
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'comments' %}{% include rest_operation %}{% endif %}
-{% endfor %}
+
\ No newline at end of file
diff --git a/translations/pt-BR/content/rest/reference/git.md b/translations/pt-BR/content/rest/reference/git.md
index 4a6a2fb5f0a7..1be4a836b97b 100644
--- a/translations/pt-BR/content/rest/reference/git.md
+++ b/translations/pt-BR/content/rest/reference/git.md
@@ -14,57 +14,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-A API do banco de dados do Git dá acesso para ler e gravar objetos do Git sem processamento no seu banco de dados do Git no {% data variables.product.product_name %} e para listar e atualizar suas referências (cabeçalhos de branch e etiquetas). Para obter mais informações sobre como usar a API do banco de dados do Git, consulte "[Começar com a API de dados do Git](/rest/guides/getting-started-with-the-git-database-api)".
-
-{% for operation in currentRestOperations %}
- {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
-{% endfor %}
-
-## Blobs
-
-Um blob (objeto binário grande) do Git é o tipo de objeto usado para armazenar o conteúdo de cada arquivo em um repositório. O hash SHA-1 do arquivo é calculado e armazenado no objeto do blob. Estes pontos de extremidade permitem ler e escrever [objetos do blob](https://git-scm.com/book/en/v1/Git-Internals-Git-Objects) em seu banco de dados d Git em {% data variables.product.product_name %}. Os blobs aproveitam [esses tipos de mídia personalizados](#custom-media-types-for-blobs). Você pode ler mais sobre o uso de tipos de mídia na API [aqui](/rest/overview/media-types).
-
-### Tipos de mídia personalizados para os blobs
-
-Estes são os tipos de mídia compatíveis com blobs.
-
- application/json
- application/vnd.github.VERSION.raw
-
-Para obter mais informações, consulte "[Tipos de mídia](/rest/overview/media-types)".
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'blobs' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## Commits
-
-Um commit do Git é um instantâneo da hierarquia ([árvore do Git](/rest/reference/git#trees)) e o conteúdo dos arquivos ([Blob do Git](/rest/reference/git#blobs)) em um repositório do Git. Estes pontos de extremidade permitem ler e escrever [objetos de commit](https://git-scm.com/book/en/v1/Git-Internals-Git-Objects#Commit-Objects) no seu banco de dados do Git em {% data variables.product.product_name %}.
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'commits' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## Referências
-
-Uma referência do Git (`git ref`) é apenas um arquivo que contém um hash SHA-1 do commit do Git. Ao referir-se a um commit do Git, você pode usar a referência do Git, que é um nome fácil de lembrar, em vez do hash. A referência do Git pode ser reescrita para apontar para um novo commit. Um branch é apenas uma referência do Git que armazena o novo hash de commit do Git. Estes pontos de extremidade permitem ler e escrever [referências](https://git-scm.com/book/en/v1/Git-Internals-Git-References) para o seu banco de dados do Git em {% data variables.product.product_name %}.
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'refs' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## Tags
-
-Uma tag do Git é semelhante a uma [Referência do Git](/rest/reference/git#refs), mas o commit do Git para o qual ela aponta nunca muda. As tags do Git são úteis quando você deseja apontar para versões específicas. Esses pontos de extremidade permitem ler e escrever [tags dos objetos](https://git-scm.com/book/en/v1/Git-Internals-Git-References#Tags) em seu banco de dados Git em {% data variables.product.product_name %}. A API de tags do Git é compatível apenas com [objetos de tags anotadas](https://git-scm.com/book/en/v1/Git-Internals-Git-References#Tags), não tags leves.
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'tags' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## Árvores
-
-Um objeto da árvore do Git cria a hierarquia entre arquivos em um repositório do Git. Você pode usar o objeto da árvore do Git para criar a relação entre diretórios e os arquivos que eles contêm. Estes pontos de extremidade permitem que você leia e escreva [objetos de árvore](https://git-scm.com/book/en/v1/Git-Internals-Git-Objects#Tree-Objects) em seu banco de dados do Git em {% data variables.product.product_name %}.
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'trees' %}{% include rest_operation %}{% endif %}
-{% endfor %}
+
diff --git a/translations/pt-BR/content/rest/reference/gitignore.md b/translations/pt-BR/content/rest/reference/gitignore.md
index 739dd8cbb8dd..2e14f392e166 100644
--- a/translations/pt-BR/content/rest/reference/gitignore.md
+++ b/translations/pt-BR/content/rest/reference/gitignore.md
@@ -13,14 +13,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-Ao criar um novo repositório em {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} por meio da API, você pode especificar um [.gitignore template](/github/getting-started-with-github/ignoring-files) para que seja aplicado ao repositório após a criação. A API de modlos do .gitignore lista e recupera modelos do repositório de [.gitignore](https://github.com/github/gitignore) de {% data variables.product.product_name %}.
-
-### Tipos de mídia personalizados para gitignore
-
-Você pode usar este tipo de mídia personalizada ao obter um modelo de gitignore.
-
- application/vnd.github.VERSION.raw
-
-Para obter mais informações, consulte "[Tipos de mídia](/rest/overview/media-types)".
-
-{% include rest_operations_at_current_path %}
+
diff --git a/translations/pt-BR/content/rest/reference/index.md b/translations/pt-BR/content/rest/reference/index.md
index 006c501c383e..8589197328b9 100644
--- a/translations/pt-BR/content/rest/reference/index.md
+++ b/translations/pt-BR/content/rest/reference/index.md
@@ -51,6 +51,5 @@ children:
- /teams
- /users
- /webhooks
- - /permissions-required-for-github-apps
---
diff --git a/translations/pt-BR/content/rest/reference/interactions.md b/translations/pt-BR/content/rest/reference/interactions.md
index 45fd432dddf9..69705267a6c7 100644
--- a/translations/pt-BR/content/rest/reference/interactions.md
+++ b/translations/pt-BR/content/rest/reference/interactions.md
@@ -11,50 +11,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-Os usuários interagem com repositórios comentando, abrindo problemas e criando pull requests. As APIs de interações permitem que as pessoas com acesso de proprietário ou administrador restrinjam temporariamente a interação com repositórios públicos para um determinado tipo de usuário.
-
-{% for operation in currentRestOperations %}
- {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
-{% endfor %}
-
-## organização
-
-A API de Interações da Organização permite que os proprietários da organização restrinjam temporariamente quais tipos de usuário podem comentar, abrir problemas ou criar pull requests nos repositórios públicos da organização. {% data reusables.interactions.interactions-detail %} Veja mais sobre os tipos de usuários de {% data variables.product.product_name %}:
-
-* {% data reusables.interactions.existing-user-limit-definition %} na organização.
-* {% data reusables.interactions.contributor-user-limit-definition %} na organização.
-* {% data reusables.interactions.collaborator-user-limit-definition %} na organização.
-
-Definir o limite de interação no nível da organização sobrescreverá quaisquer limites de interação definidos para repositórios individuais pertencentes à organização. Para definir diferentes limites de interação para repositórios individuais pertencentes à organização, use os pontos de extremidade das interações do [Repositório](#repository).
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'orgs' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## Repositório
-
-A API de Interações do Repositório permite que pessoas com acesso de proprietário ou administrador restrinjam temporariamente qual tipo de usuário pode comentar, abrir problemas ou criar pull requests em um repositório público. {% data reusables.interactions.interactions-detail %} Veja mais sobre os tipos de usuários de {% data variables.product.product_name %}:
-
-* {% data reusables.interactions.existing-user-limit-definition %} in the respository.
-* {% data reusables.interactions.contributor-user-limit-definition %} in the respository.
-* {% data reusables.interactions.collaborator-user-limit-definition %} in the respository.
-
-Se um limite de interação for habilitado para o usuário ou organização proprietária do repositório, o limite não poderá ser alterado para o repositório individual. Em vez disso, use os pontos de extremidade de [Usuário](#user) ou [Organização](#organization) para alterar o limite de interação.
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'repos' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## Usuário
-
-A API de Interações do Usuário permite restringir temporariamente que tipo de usuário pode comentar, abrir problemas ou criar pull requests nos seus repositórios públicos. {% data reusables.interactions.interactions-detail %} Veja mais sobre os tipos de usuários de {% data variables.product.product_name %}:
-
-* {% data reusables.interactions.existing-user-limit-definition %} de interagir com seus repositórios.
-* {% data reusables.interactions.contributor-user-limit-definition %} de interagir com seus repositórios.
-* {% data reusables.interactions.collaborator-user-limit-definition %} de interagir com seus repositórios.
-
-Definir o limite de interação no nível do usuário sobrescreverá quaisquer limites de interação definidos para repositórios individuais pertencentes ao usuário. Para definir diferentes limites de interação para repositórios individuais pertencentes ao usuário, use os pontos de extremidade das interações do [Repositório](#repository).
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'user' %}{% include rest_operation %}{% endif %}
-{% endfor %}
+
diff --git a/translations/pt-BR/content/rest/reference/issues.md b/translations/pt-BR/content/rest/reference/issues.md
index 069b3225f148..38a3571f1a58 100644
--- a/translations/pt-BR/content/rest/reference/issues.md
+++ b/translations/pt-BR/content/rest/reference/issues.md
@@ -13,63 +13,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-### Tipos de mídia personalizados para problemas
-
-Estes são os tipos de mídia compatíveis para problemas.
-
- application/vnd.github.VERSION.raw+json
- application/vnd.github.VERSION.text+json
- application/vnd.github.VERSION.html+json
- application/vnd.github.VERSION.full+json
-
-Para obter mais informações sobre os tipos de mídia, consulte "[Tipos de mídia personalizados](/rest/overview/media-types)".
-
-{% for operation in currentRestOperations %}
- {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
-{% endfor %}
-
-## Responsáveis
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'assignees' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## Comentários
-
-A API de Comentários do Problema é compatível com listagem, visualização, edição e criação de comentários em problemas e pull requests.
-
-Os comentários do problema usam [estes tipos de mídia personalizados](#custom-media-types). Você pode ler mais sobre o uso de tipos de mídia na API [aqui](/rest/overview/media-types).
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'comments' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## Eventos
-
-A API de Eventos de problema pode retornar diferentes tipos de eventos desencadeados por atividades em problemas e pull requests. The Issue Events API can return different types of events triggered by activity in issues and pull requests. For more information about the specific events that you can receive from the Issue Events API, see "[Issue event types](/developers/webhooks-and-events/issue-event-types)." Para obter mais informações, consulte a "[API de Eventos](/developers/webhooks-and-events/github-event-types)".
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'events' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## Etiquetas
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'labels' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## Marcos
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'milestones' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## Linha do tempo
-
-A API de Eventos da Linha do Tempo pode retornar diferentes tipos de eventos acionados pela atividade da linha do tempo em problemas e pull requests. The Issue Events API can return different types of events triggered by activity in issues and pull requests. For more information about the specific events that you can receive from the Issue Events API, see "[Issue event types](/developers/webhooks-and-events/issue-event-types)." Para obter mais informações, consulte a "[API de Eventos do GitHub](/developers/webhooks-and-events/github-event-types)".
-
-Você pode usar esta API para exibir informações sobre problemas e pull request ou determinar quem deve ser notificado sobre os comentários de problema.
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'timeline' %}{% include rest_operation %}{% endif %}
-{% endfor %}
+
diff --git a/translations/pt-BR/content/rest/reference/licenses.md b/translations/pt-BR/content/rest/reference/licenses.md
index 503cf273a75b..770a3d97c24a 100644
--- a/translations/pt-BR/content/rest/reference/licenses.md
+++ b/translations/pt-BR/content/rest/reference/licenses.md
@@ -13,27 +13,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-A API de Licenças retorna metadados sobre as licenças de código aberto populares e informações sobre o arquivo de licença de um determinado projeto.
-
-A API de Licenças usa [a Licença de código aberto do Gem do Ruby](https://github.com/benbalter/licensee) para tentar identificar a licença do projeto. A licença corresponde ao conteúdo do arquivo `LICENÇA` de um projeto (se existir) em comparação com uma pequena lista de licenças conhecidas. Como resultado, a API não leva em conta as licenças das dependências do projeto ou outros meios de documentar a licença de um projeto, como, por exemplo, referências ao nome da licença na documentação.
-
-Se uma licença for correspondida, a chave da licença e o nome retornados serão conformes à [especificação SPDX](https://spdx.org/).
-
-**Observação:** Estes pontos de extremidade também retornarão informações de licença de um repositório:
-
-- [Obter um repositório](/rest/reference/repos#get-a-repository)
-- [Listar repositórios para um usuário](/rest/reference/repos#list-repositories-for-a-user)
-- [Listar repositórios da organização](/rest/reference/repos#list-organization-repositories)
-- [Listar bifurcações](/rest/reference/repos#list-forks)
-- [Listar repositórios inspecionados por um usuário](/rest/reference/activity#list-repositories-watched-by-a-user)
-- [Listar repositórios da equipe](/rest/reference/teams#list-team-repositories)
-
-{% warning %}
-
-O GitHub pode ser muitas coisas, mas não é um escritório de advocacia. Como tal, o GitHub não oferece aconselhamento jurídico. Usar a API de licenças ou enviar-nos um e-mail sobre a mesma não constitui aconselhamento jurídico, nem cria uma relação advogado e cliente. Em caso de dúvida sobre o que se pode e não se pode fazer com uma licença específica, antes de avançar, você deverá buscar orientação jurídica antes de seguir em frente. Na verdade, você deve sempre consultar o seu próprio advogado antes de tomar decisões que possam ter desdobramentos jurídicos ou que possam afetar seus direitos.
-
-O GitHub criou a API da licença para ajudar os usuários a obter informações sobre licenças de código aberto e os projetos que as utilizam. Esperamos que ajude. No entanto, tenha em mente que não somos advogados (pelo menos a maioria de nós) e que cometemos erros como qualquer um. Por esse motivo, o GitHub fornece a API numa base "como se apresenta" e não faz garantias sobre quaisquer informações ou licenças fornecidas em ou através dela, além de eximir-se da responsabilidade por danos resultantes do uso da API.
-
-{% endwarning %}
-
-{% include rest_operations_at_current_path %}
+
diff --git a/translations/pt-BR/content/rest/reference/markdown.md b/translations/pt-BR/content/rest/reference/markdown.md
index 8af643361da4..963b93f428aa 100644
--- a/translations/pt-BR/content/rest/reference/markdown.md
+++ b/translations/pt-BR/content/rest/reference/markdown.md
@@ -13,4 +13,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-{% include rest_operations_at_current_path %}
+
diff --git a/translations/pt-BR/content/rest/reference/meta.md b/translations/pt-BR/content/rest/reference/meta.md
index aa2a65994b4f..fc77dde1388a 100644
--- a/translations/pt-BR/content/rest/reference/meta.md
+++ b/translations/pt-BR/content/rest/reference/meta.md
@@ -13,4 +13,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-{% include rest_operations_at_current_path %}
+
diff --git a/translations/pt-BR/content/rest/reference/metrics.md b/translations/pt-BR/content/rest/reference/metrics.md
index 9c933e092131..325b7baff4e8 100644
--- a/translations/pt-BR/content/rest/reference/metrics.md
+++ b/translations/pt-BR/content/rest/reference/metrics.md
@@ -14,47 +14,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-{% for operation in currentRestOperations %}
- {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
-{% endfor %}
-
-{% ifversion fpt or ghec %}
-## Comunidade
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'community' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% endif %}
-
-## Estatísticas
-
-A API de Estatísticas do Repositório permite que você recupere os dados que o {% data variables.product.product_name %} usa para visualizar diferentes tipos de atividade do repositório.
-
-### Umas palavras sobre o armazenamento em cache
-
-Computar as estatísticas do repositório é uma operação cara. Por esse motivo, tentamos retornar dados armazenados em cache sempre que possível. Se os dados não forem armazenados em cache nas estatísticas de um repositório, você receberá uma resposta de `202`; um trabalho em segundo plano também é acionado para começar a compilar estas estatísticas. Dê ao trabalho alguns instantes para que seja concluído e, em seguida, envie a solicitação novamente. Se o trabalho foi concluído, essa solicitação receberá uma resposta de `200` com as estatísticas no texto da resposta.
-
-As estatísticas do repositório são armazenadas em cache pelo SHA do branch-padrão do repositório; fazer push para o branch-padrão redefine o armazenamento em cache de estatísticas.
-
-### As estatísticas excluem alguns tipos de commits
-
-As estatísticas expostas pela API correspondem às estatísticas mostradas pelos [diferentes gráficos de repositórios](/github/visualizing-repository-data-with-graphs/about-repository-graphs).
-
-Resumo:
-- Todas as estatísticas excluem commits de merge.
-- As estatísticas do contribuidor também excluem commits vazios.
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'statistics' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% ifversion fpt or ghec %}
-## Tráfego
-
-Para repositórios aos quais você tem acesso de push, a API de tráfego fornece acesso às informações fornecidas no seu gráfico de repositório. Para obter mais informações, consulte "Visualizar tráfego para um repositório. "
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'traffic' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-{% endif %}
+
diff --git a/translations/pt-BR/content/rest/reference/migrations.md b/translations/pt-BR/content/rest/reference/migrations.md
index 5b192e8a74eb..6c1fd90fe8a2 100644
--- a/translations/pt-BR/content/rest/reference/migrations.md
+++ b/translations/pt-BR/content/rest/reference/migrations.md
@@ -15,116 +15,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-{% for operation in currentRestOperations %}
- {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
-{% endfor %}
-
-## organização
-
-A API de migrações só está disponível para os proprietários de organizações autenticadas. Para obter mais informações, consulte "[Funções em organização](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#permission-levels-for-an-organization)" e "[Outros métodos de autenticação](/rest/overview/other-authentication-methods)".
-
-{% data variables.migrations.organization_migrations_intro %}
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'orgs' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% ifversion fpt or ghec %}
-## Importações de código-fonte
-
-{% data variables.migrations.source_imports_intro %}
-
-Uma importação de código-fonte típica iniciaria a importação e, em seguida, (opcionalmente) atualizaria os autores e/ou atualizaria a preferência pelo uso do LFS do Git se existirem arquivos grandes na importação. Também é possível criar um webhook que ouve o [`ReposityImportEvent`](/developers/webhooks-and-events/webhook-events-and-payloads#repository_import) para descobrir o status da importação.
-
-Um exemplo mais detalhado pode ser visto neste diagrama:
-
-```
-+---------+ +--------+ +---------------------+
-| Tooling | | GitHub | | Original Repository |
-+---------+ +--------+ +---------------------+
- | | |
- | Start import | |
- |----------------------------->| |
- | | |
- | | Download source data |
- | |--------------------------------------------->|
- | | Begin streaming data |
- | |<---------------------------------------------|
- | | |
- | Get import progress | |
- |----------------------------->| |
- | "status": "importing" | |
- |<-----------------------------| |
- | | |
- | Get commit authors | |
- |----------------------------->| |
- | | |
- | Map a commit author | |
- |----------------------------->| |
- | | |
- | | |
- | | Finish streaming data |
- | |<---------------------------------------------|
- | | |
- | | Rewrite commits with mapped authors |
- | |------+ |
- | | | |
- | |<-----+ |
- | | |
- | | Update repository on GitHub |
- | |------+ |
- | | | |
- | |<-----+ |
- | | |
- | Map a commit author | |
- |----------------------------->| |
- | | Rewrite commits with mapped authors |
- | |------+ |
- | | | |
- | |<-----+ |
- | | |
- | | Update repository on GitHub |
- | |------+ |
- | | | |
- | |<-----+ |
- | | |
- | Get large files | |
- |----------------------------->| |
- | | |
- | opt_in to Git LFS | |
- |----------------------------->| |
- | | Rewrite commits for large files |
- | |------+ |
- | | | |
- | |<-----+ |
- | | |
- | | Update repository on GitHub |
- | |------+ |
- | | | |
- | |<-----+ |
- | | |
- | Get import progress | |
- |----------------------------->| |
- | "status": "complete" | |
- |<-----------------------------| |
- | | |
- | | |
-```
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'source-imports' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-{% endif %}
-## Usuário
-
-A API de migrações do usuário só está disponível para proprietários de contas autenticadas. Para obter mais informações, consulte "[Outros métodos de autenticação](/rest/overview/other-authentication-methods)".
-
-{% data variables.migrations.user_migrations_intro %} Para obter uma lista dos dados de migração que você pode baixar, consulte "[Fazer download de um arquivo de migração do usuário](#download-a-user-migration-archive)".
-
-Para fazer o download de um arquivo, você deverá iniciar uma migração de usuário primeiro. Uma vez que o status da migração é `exportado`, você pode fazer o download da migração.
-
-Ao criar um arquivo de migração, ele ficará disponível para download por sete dias. No entanto, você pode excluir o arquivo de migração do usuário mais cedo, se desejar. Você pode desbloquear o repositório quando a migração for `exportada` para começar a usar seu repositório novamente ou excluir o repositório se não precisar mais dos dados do código-fonte.
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'users' %}{% include rest_operation %}{% endif %}
-{% endfor %}
+
diff --git a/translations/pt-BR/content/rest/reference/oauth-authorizations.md b/translations/pt-BR/content/rest/reference/oauth-authorizations.md
index a55d182d5cc3..270e607c9218 100644
--- a/translations/pt-BR/content/rest/reference/oauth-authorizations.md
+++ b/translations/pt-BR/content/rest/reference/oauth-authorizations.md
@@ -8,8 +8,6 @@ versions:
miniTocMaxHeadingLevel: 3
---
-Você pode usar esta API para gerenciar o acesso do aplicativo OAuth à sua conta. Você só pode acessar esta API através da [Autenticação básica](/rest/overview/other-authentication-methods#basic-authentication) usando seu nome de usuário e senha, não tokens.
-
-Se você ou seus usuários tiverem a autenticação de dois fatores habilitada, certifique-se de entender como [trabalhar com autenticação de dois fatores](/rest/overview/other-authentication-methods#working-with-two-factor-authentication).
-
-{% include rest_operations_at_current_path %}
+
diff --git a/translations/pt-BR/content/rest/reference/orgs.md b/translations/pt-BR/content/rest/reference/orgs.md
index dcf024c1c036..d7b3719e775d 100644
--- a/translations/pt-BR/content/rest/reference/orgs.md
+++ b/translations/pt-BR/content/rest/reference/orgs.md
@@ -14,66 +14,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-{% for operation in currentRestOperations %}
- {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
-{% endfor %}
-
-{% ifversion fpt or ghec %}
-## Bloquear usuários
-
-O token usado para autenticar a chamada deve ter o escopo `admin:org` para fazer quaisquer chamadas de bloqueio para uma organização. Caso contrário, a resposta retornará `HTTP 404`.
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'blocking' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% endif %}
-
-## Integrantes
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'members' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## Colaboradores externos
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'outside-collaborators' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% ifversion fpt or ghes > 3.4 %}
-## Funções de repositório personalizadas
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'custom_roles' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-{% endif %}
-
-## Webhooks
-
-Os webhooks da organização permitem que você receba cargas de HTTP do tipo `POST` sempre que certos eventos ocorrerem dentro da organização. {% data reusables.webhooks.webhooks-rest-api-links %}
-
-Para obter mais informações sobre ações que você pode assinar, consulte "[ tipos de evento de {% data variables.product.prodname_dotcom %}](/developers/webhooks-and-events/github-event-types)".
-
-### Escopos & Restrições
-
-Todas as ações contra webhooks da organização exigem que o usuário autenticado seja um administrador da organização que está sendo gerenciada. Além disso, os tokens do OAuth requerem o escopo `admin:org_hook`. Para obter mais informações, consulte "[Escopos para aplicativos OAuth](/developers/apps/scopes-for-oauth-apps)."
-
-Para proteger dados sensíveis que podem estar presentes nas configurações do webhook, também aplicamos as seguintes regras de controle de acesso:
-
-- Os aplicativos OAuth não podem listar, visualizar ou editar webhooks que não criaram.
-- Os usuários não podem listar, visualizar ou editar webhooks que foram criados por aplicativos OAuth.
-
-### Receber Webhooks
-
-Para que {% data variables.product.product_name %} envie cargas de webhook, seu servidor deve ser acessível pela internet. É altamente recomendável o uso de SSL para que possamos enviar cargas criptografadas por HTTPS.
-
-Para obter mais práticas recomendadas, [consulte nosso guia](/guides/best-practices-for-integrators/).
-
-#### Cabeçalhos de webhook
-
-{% data variables.product.product_name %} enviará ao longo de vários cabeçalhos de HTTP para diferenciar entre tipos de evento e identificadores de carga. Consulte [cabeçalhos de webhook](/webhooks/event-payloads/#delivery-headers) para obter informações.
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'webhooks' %}{% include rest_operation %}{% endif %}
-{% endfor %}
+
diff --git a/translations/pt-BR/content/rest/reference/packages.md b/translations/pt-BR/content/rest/reference/packages.md
index ad1d91d929c4..8337307add6c 100644
--- a/translations/pt-BR/content/rest/reference/packages.md
+++ b/translations/pt-BR/content/rest/reference/packages.md
@@ -10,17 +10,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-A API de {% data variables.product.prodname_registry %} permite gerenciar pacotes usando a API REST. Para saber mais sobre como restaurar ou excluir pacotes, consulte "[Restaurar e excluir pacotes](/packages/learn-github-packages/deleting-and-restoring-a-package)"".
-
-Para usar essa API, você deve efetuar a autenticação usando um token de acesso pessoal.
- - Para acessar os metadados do pacote, seu token deve incluir o escopo `read:packages`.
- - Para excluir pacotes e versões de pacote, seu token deverá incluir os escopos `read:packages` e `delete:packages`.
- - Para restaurar pacotes e versões do pacote, o seu token deve incluir os escopos `read:packages` e `write:packages`.
-
-Se seu `package_type` for `npm`, `maven`, `rubygems` ou `nuget`, o seu token também deverá incluir o escopo `repo` já que o pacote herda as permissões de um repositório de {% data variables.product.prodname_dotcom %}. Se seu pacote estiver em {% data variables.product.prodname_container_registry %}, seu `package_type` será `container` e seu token não precisará do escopo `repositório` para acessar ou gerenciar este `package_type`. Os pacotes de `contêiner` oferecem permissões granulares separadas de um repositório. Para obter mais informações, consulte "[Sobre permissões para {% data variables.product.prodname_registry %}](/packages/learn-github-packages/about-permissions-for-github-packages#about-scopes-and-permissions-for-package-registries)".
-
-Se você quiser usar a API de {% data variables.product.prodname_registry %} para acessar os recursos em uma organização com SSO habilitado, então você deve habilitar o SSO para o seu token de acesso pessoal. Para mais informações consulte "[Autorizando um token de acesso pessoal para usar com lgon único SAML](/github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on){% ifversion fpt %}" na documentação de {% data variables.product.prodname_ghe_cloud %}.{% else %}."{% endif %}
-
-{% for operation in currentRestOperations %}
- {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
-{% endfor %}
+
diff --git a/translations/pt-BR/content/rest/reference/pages.md b/translations/pt-BR/content/rest/reference/pages.md
index 7d95cfc61984..a5aad5c76a53 100644
--- a/translations/pt-BR/content/rest/reference/pages.md
+++ b/translations/pt-BR/content/rest/reference/pages.md
@@ -12,22 +12,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-A API de {% data variables.product.prodname_pages %} recupera informações sobre a sua configuração do {% data variables.product.prodname_pages %} e os status das suas criações. Informações sobre o site e as criações só podem ser acessadas pelos proprietários autenticados{% ifversion not ghae %}, mesmo que os sites sejam públicos{% endif %}. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages)".
-
-Nos pontos de extremidade da API de {% data variables.product.prodname_pages %} com uma chave de `status` na sua resposta, o valor pode ser:
-* `null`: O site ainda não foi criado.
-* `queued`: A criação foi solicitada, mas ainda não começou.
-* `building`:A criaçãoestá em andamento.
-* `built`: O site foi criado.
-* `errored`: Indica que ocorreu um erro durante a criação.
-
-Nos pontos de extremidade da API de {% data variables.product.prodname_pages %} que devolvem as informações do site do GitHub Pages, as respostas do JSON incluem esses campos:
-* `html_url`: A URL absoluta (incluindo o esquema) do site de páginas interpretadas. Por exemplo, `https://username.github.io`.
-* `source`: Um objeto que contém o branch de origem e o diretório do site de páginas interpretadas. Isto inclui:
- - `branch`: O branch do repositório utilizado para publicar os [arquivos de origem do site](/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site). Por exemplo, _principal_ ou _gh-pages_.
- - `path`: O diretório do repositório a partir do qual o site é publicado. Será `/` ou `/docs`.
-
-{% comment %}É necessária uma linha em branco adicional aqui para garantir que as operações abaixo não deem continuidade à lista acima.{% endcomment %}
-{% for operation in currentRestOperations %}
- {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
-{% endfor %}
+
diff --git a/translations/pt-BR/content/rest/reference/projects.md b/translations/pt-BR/content/rest/reference/projects.md
index 92fd3323c313..9b23ff6c0f66 100644
--- a/translations/pt-BR/content/rest/reference/projects.md
+++ b/translations/pt-BR/content/rest/reference/projects.md
@@ -13,26 +13,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-{% for operation in currentRestOperations %}
- {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
-{% endfor %}
-
-## Cartões
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'cards' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## Colaboradores
-
-Esta API permite que você interaja com os projetos de uma organização.
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'collaborators' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## Colunas
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'columns' %}{% include rest_operation %}{% endif %}
-{% endfor %}
+
diff --git a/translations/pt-BR/content/rest/reference/pulls.md b/translations/pt-BR/content/rest/reference/pulls.md
index f4a422f297d6..d16a1904eafb 100644
--- a/translations/pt-BR/content/rest/reference/pulls.md
+++ b/translations/pt-BR/content/rest/reference/pulls.md
@@ -13,75 +13,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-A API do Pull Request permite que você liste, visualize, edite, crie e até mesmo faça merge de pull requests. Comentários em pull requests podem ser gerenciados através da [API de Comentários do Problema](/rest/reference/issues#comments).
-
-Cada pull request é um problema, mas nem todos os problemas são um pull request. Por este motivo, as ações "compartilhadas" para ambos os recursos, como a manipulação de responsáveis, etiquetas e marcos são fornecidos dentro de [a API de problemas](/rest/reference/issues).
-
-### Tipos de mídia personalizados para pull requests
-
-Estes são os tipos de mídia compatíveis com pull requests.
-
- application/vnd.github.VERSION.raw+json
- application/vnd.github.VERSION.text+json
- application/vnd.github.VERSION.html+json
- application/vnd.github.VERSION.full+json
- application/vnd.github.VERSION.diff
- application/vnd.github.VERSION.patch
-
-Para obter mais informações, consulte "[tipos de mídia personalizados](/rest/overview/media-types)".
-
-Se um diff estiver corrompido, entre em contato com {% data variables.contact.contact_support %}. Inclua o nome e o ID do pull request do repositório na sua mensagem.
-
-### Relações do Link
-
-Pull Requests têm estas relações de link possíveis:
-
-| Nome | Descrição |
-| ----------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `self` | O local da API deste Pull Request. |
-| `html` | O locl do HTML deste Pull Request. |
-| `problema` | O local da API do [Problema](/rest/reference/issues) deste Pull Request. |
-| `comentários` | O local da API dos [comentários do problema](/rest/reference/issues#comments) deste Pull Request. |
-| `review_comments` | O local da API dos [comentários da revisão](/rest/reference/pulls#comments) deste Pull Request. |
-| `review_comment` | O [modelo de URL](/rest#hypermedia) para construir o local da API para um [comentário de revisão](/rest/reference/pulls#comments) no repositório deste Pull Request. |
-| `commits` | O local da API dos [commits](#list-commits-on-a-pull-request) deste Pull Request. |
-| `Status` | O local da API dos [status do commit](/rest/reference/commits#commit-statuses) deste pull request, que são os status no seu branch `principal`. |
-
-{% for operation in currentRestOperations %}
- {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
-{% endfor %}
-
-## Revisões
-
-As revisões de pull request são grupos de comentários de revisão de pull request no Pull Request, agrupados e com um status e comentário de texto opcional.
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'reviews' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## Comentários de revisão
-
-Os comentários de revisão de pull request são comentários em uma parte do diff unificado feitos durante uma revisão de pull request. Comentários de commit e comentários de problemas são são diferentes dos comentários de revisão de pull request. Você aplica comentários de submissão diretamente para um commit e aplica comentários de problema sem fazer referência a uma parte do diff unificado. Para obter mais informações, consulte "[Criar um comentário de commit](/rest/reference/commits#create-a-commit-comment)" e "[Criar um comentário de problema](/rest/reference/issues#create-an-issue-comment)".
-
-### Tipos de mídia personalizados para comentários de revisão de pull request
-
-Estes são os tipos de mídia compatíveis com os comentários de revisão de pull request.
-
- application/vnd.github.VERSION.raw+json
- application/vnd.github.VERSION.text+json
- application/vnd.github.VERSION.html+json
- application/vnd.github.VERSION.full+json
-
-Para obter mais informações, consulte "[tipos de mídia personalizados](/rest/overview/media-types)".
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'comments' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## Solicitações de revisão
-
-Os autores dos pull request e os proprietários e colaboradores dos repositórios podem solicitar uma revisão de pull request para qualquer pessoa com acesso de gravação ao repositório. Cada revisor solicitado receberá uma notificação pedindo-lhes para revisar o pull request.
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'review-requests' %}{% include rest_operation %}{% endif %}
-{% endfor %}
+
diff --git a/translations/pt-BR/content/rest/reference/rate-limit.md b/translations/pt-BR/content/rest/reference/rate-limit.md
index d95ccfe6f59d..876a13775ec2 100644
--- a/translations/pt-BR/content/rest/reference/rate-limit.md
+++ b/translations/pt-BR/content/rest/reference/rate-limit.md
@@ -14,22 +14,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-A documentação geral da API REST descreve as [regras de limite de taxa](/rest/overview/resources-in-the-rest-api#rate-limiting). Você pode verificar seu status de limite de taxa atual a qualquer momento usando a API de limite de taxa descrita abaixo.
-
-### Entender o seu status de limite de taxa
-
-A API de pesquisa tem um [limite de taxa personalizado](/rest/reference/search#rate-limit), separado do limite de taxa que rege o restante da API REST. A API do GraphQL também tem um [limite de taxa personalizado]({% ifversion ghec%}/free-pro-team@latest{% endif %}/graphql/overview/resource-limitations#rate-limit), que é separado e calculado de forma diferente dos limites de taxa na API REST.
-
-Por esses motivos, a resposta da API do limite de taxa categoriza o seu limite de taxa. Em `recursos`, você verá quatro objetos:
-
-* O objeto `principal` fornece o status do limite de taxa para todos os recursos não relacionados à pesquisa na API REST.
-
-* O objeto `de pesquisa` fornece o status do limite de taxa para a [API de pesquisa](/rest/reference/search).
-
-* O objeto `graphql` fornece o status do limite de taxa para a [API do GraphQL]({% ifversion ghec%}/free-pro-team@latest{% endif %}/graphql).
-
-* O objeto `integration_manifest` fornece o status do limite de taxa para o ponto de extremidade [Conversão do código de manifesto do aplicativo GitHub](/apps/building-github-apps/creating-github-apps-from-a-manifest/#3-you-exchange-the-temporary-code-to-retrieve-the-app-configuration).
-
-Para obter mais informações sobre os cabeçalhos e valores na resposta de limite de taxa, consulte "[Recursos na API REST](/rest/overview/resources-in-the-rest-api#rate-limit-http-headers)".
-
-{% include rest_operations_at_current_path %}
+
diff --git a/translations/pt-BR/content/rest/reference/reactions.md b/translations/pt-BR/content/rest/reference/reactions.md
index dfe73dcd0518..144bab449904 100644
--- a/translations/pt-BR/content/rest/reference/reactions.md
+++ b/translations/pt-BR/content/rest/reference/reactions.md
@@ -13,10 +13,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-### Tipos de reação
-
-Ao criar uma reação, os valores permitidos para o parâmetro `conteúdo` são os seguintes (com o emoji correspondente para referência):
-
-{% data reusables.repositories.reaction_list %}
-
-{% include rest_operations_at_current_path %}
+
diff --git a/translations/pt-BR/content/rest/reference/releases.md b/translations/pt-BR/content/rest/reference/releases.md
index 21f534fad403..bdd25fffcf7d 100644
--- a/translations/pt-BR/content/rest/reference/releases.md
+++ b/translations/pt-BR/content/rest/reference/releases.md
@@ -12,18 +12,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-{% note %}
-
-**Observação:** A API de versões substitui a API de Downloads. Você pode recuperar a contagem de download e a URL de download do navegador a partir dos pontos de extremidades nesta API que retornam versões e liberam ativos.
-
-{% endnote %}
-
-{% for operation in currentRestOperations %}
- {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
-{% endfor %}
-
-## Ativos de versões
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'assets' %}{% include rest_operation %}{% endif %}
-{% endfor %}
+
diff --git a/translations/pt-BR/content/rest/reference/repos.md b/translations/pt-BR/content/rest/reference/repos.md
index 89a55881b8e8..51710d0f0ccc 100644
--- a/translations/pt-BR/content/rest/reference/repos.md
+++ b/translations/pt-BR/content/rest/reference/repos.md
@@ -14,64 +14,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-{% for operation in currentRestOperations %}
- {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
-{% endfor %}
-
-{% ifversion fpt or ghec or ghes > 3.2 or ghae-issue-4742 %}
-## Autolinks
-
-To help streamline your workflow, you can use the API to add autolinks to external resources like JIRA issues and Zendesk tickets. For more information, see "[Configuring autolinks to reference external resources](/github/administering-a-repository/configuring-autolinks-to-reference-external-resources)."
-
-{% data variables.product.prodname_github_apps %} require repository administration permissions with read or write access to use the Autolinks API.
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'autolinks' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-{% endif %}
-
-
-## Contents
-
-These API endpoints let you create, modify, and delete Base64 encoded content in a repository. To request the raw format or rendered HTML (when supported), use custom media types for repository contents.
-
-### Custom media types for repository contents
-
-[READMEs](/rest/reference/repos#get-a-repository-readme), [files](/rest/reference/repos#get-repository-content), and [symlinks](/rest/reference/repos#get-repository-content) support the following custom media types:
-
- application/vnd.github.VERSION.raw
- application/vnd.github.VERSION.html
-
-Use the `.raw` media type to retrieve the contents of the file.
-
-For markup files such as Markdown or AsciiDoc, you can retrieve the rendered HTML using the `.html` media type. Markup languages are rendered to HTML using our open-source [Markup library](https://github.com/github/markup).
-
-[All objects](/rest/reference/repos#get-repository-content) support the following custom media type:
-
- application/vnd.github.VERSION.object
-
-Use the `object` media type parameter to retrieve the contents in a consistent object format regardless of the content type. For example, instead of an array of objects
-for a directory, the response will be an object with an `entries` attribute containing the array of objects.
-
-You can read more about the use of media types in the API [here](/rest/overview/media-types).
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'contents' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## Forks
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'forks' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% ifversion fpt or ghae or ghes > 3.2 or ghec %}
-
-## Git LFS
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'lfs' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% endif %}
-
+
\ No newline at end of file
diff --git a/translations/pt-BR/content/rest/reference/scim.md b/translations/pt-BR/content/rest/reference/scim.md
index 7d95dd6fe2d9..beab0ce90422 100644
--- a/translations/pt-BR/content/rest/reference/scim.md
+++ b/translations/pt-BR/content/rest/reference/scim.md
@@ -11,46 +11,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-### Provisionamento de SCIM para Organizações
-
-A API do SCIM é usada pelos provedores de identidade (IdPs) habilitados pelo SCIM para automatizar o provisionamento de integrantes da organização de {% data variables.product.product_name %}. A {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API tem por base a versão 2.0 do [Padrão do SCIM](http://www.simplecloud.info/). O ponto de extremidade do SCIM do {% data variables.product.product_name %} que um IdP deve usar é: `{% data variables.product.api_url_code %}/scim/v2/organizations/{org}/`.
-
-{% note %}
-
-**Notas:**
- - A API do SCIM está disponível apenas para organizações em [{% data variables.product.prodname_ghe_cloud %}](/billing/managing-billing-for-your-github-account/about-billing-for-github-accounts) com o [SAML SSO](/rest/overview/other-authentication-methods#authenticating-for-saml-sso) habilitado. {% data reusables.scim.enterprise-account-scim %} Para obter mais informações sobre o SCIM, consulte "[Sobre o SCIM](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim)".
- - A API SCIM não pode ser usada com {% data variables.product.prodname_emus %}.
-
-{% endnote %}
-
-### Autenticar chamadas para a API de SCIM
-
-Você deve efetuar a autenticação como dono de uma organização do {% data variables.product.product_name %} para usar sua API do SCIM. A API espera que um token [OAuth 2.0](/developers/apps/authenticating-with-github-apps) seja incluído no cabeçalho da `Autorização`. Você também pode usar um token de acesso pessoal, mas primeiro deve [autorizá-lo para uso com sua organização SAML SSO](/github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on).
-
-### Mapear dados do SAML e SCIM
-
-{% data reusables.scim.nameid-and-username-must-match %}
-
-### Atributos de usuário de SCIM compatíveis
-
-| Nome | Tipo | Descrição |
-| ----------------- | --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| `userName` | `string` | O nome de usuário para o usuário. |
-| `name.givenName` | `string` | O primeiro nome do usuário. |
-| `name.familyName` | `string` | O sobrenome do usuário. |
-| `emails` | `array` | Lista de e-mails dos usuários. |
-| `externalId` | `string` | Este identificador é gerado pelo provedor do SAML e é usado como um ID exclusivo pelo provedor do SAML para corresponder ao usuário do GitHub. Você pode encontrar o `externalID` para um usuário no provedor do SAML ou usar a [listar identidades fornecidas pelo ponto de extremidade do SCIM](#list-scim-provisioned-identities) e filtrar outros atributos conhecidos, como, por exemplo, o nome de usuário no GitHub ou endereço de e-mail de usuário. |
-| `id` | `string` | Identificador gerado pelo ponto de extremidade do SCIM do GitHub. |
-| `ativo` | `boolean` | Usado para indicar se a identidade está ativa (verdadeira) ou se deve ser desprovisionada (falso). |
-
-{% note %}
-
-**Observação:** As URLs de Endpoint para a API SCIM são sensíveis a maiúsculas e minúsculas. Por exemplo, a primeira letra no endpoint `Usuários` deve ser maiúscula:
-
-```shell
-GET /scim/v2/organizations/{org}/Users/{scim_user_id}
-```
-
-{% endnote %}
-
-{% include rest_operations_at_current_path %}
+
diff --git a/translations/pt-BR/content/rest/reference/search.md b/translations/pt-BR/content/rest/reference/search.md
index cd1854c50932..7c65683ceead 100644
--- a/translations/pt-BR/content/rest/reference/search.md
+++ b/translations/pt-BR/content/rest/reference/search.md
@@ -13,150 +13,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-A API de pesquisa ajuda a pesquisar o item específico que você deseja encontrar. Por exemplo, você pode encontrar um usuário ou um arquivo específico em um repositório. Pense nisso da mesma forma que você pensa em realizar uma pesquisa no Google. Ele é projetado para ajudá-lo a encontrar o resultado que você está procurando (ou talvez os poucos resultados que você está procurando). Assim como pesquisar no Google, às vezes, você quer ver algumas páginas com resultados de pesquisa para que você possa encontrar o item que melhor atenda às suas necessidades. Para atender a essa necessidade, a API de pesquisa do {% data variables.product.product_name %} fornece **até 1.000 resultados para cada pesquisa**.
-
-Você pode restringir sua pesquisa usando as consultas. Para saber mais sobre a sintaxe de consultas de pesquisa, consulte "[Criar uma consulta de pesquisa](/rest/reference/search#constructing-a-search-query)".
-
-### Resultados da pesquisa de classificação
-
-A menos que outra opção de ordenamento seja fornecida como um parâmetro de consulta, os resultados são ordenados pela melhor correspondência e em ordem decrescente. Vários fatores são combinados para impulsionar o item mais relevante para a parte superior da lista de resultados.
-
-### Limite de taxa
-
-{% data reusables.enterprise.rate_limit %}
-
-A API de pesquisa tem um limite de taxa personalizado. Para solicitações que usam a [Autenticação Básica](/rest#authentication)[OAuth ](/rest#authentication) ou [ID e segredo do cliente e](/rest#increasing-the-unauthenticated-rate-limit-for-oauth-applications), você pode fazer até 30 solicitações por minuto. Para solicitações não autenticadas, o limite de taxa permite que você faça até 10 solicitações por minuto.
-
-Veja a [documentação do limite de taxa](/rest/reference/rate-limit) para obter informações sobre a determinação do seu status atual de limite de taxa.
-
-### Criar uma consulta de pesquisa
-
-Cada ponto de extremidade na API de Pesquisa usa [parâmetros de consulta](https://en.wikipedia.org/wiki/Query_string) para realizar pesquisas no {% data variables.product.product_name %}. Veja o ponto de extremidade individual na API de pesquisa para obter um exemplo que inclui o ponto de extremidade de parâmetros de consulta.
-
-Uma consulta pode conter qualquer combinação de qualificadores de pesquisa compatíveis em {% data variables.product.product_name %}. O formato da consulta de pesquisa é:
-
-```
-SEARCH_KEYWORD_1 SEARCH_KEYWORD_N QUALIFIER_1 QUALIFIER_N
-```
-
-Por exemplo, se você quisesse pesquisar todos os _repositórios_ de propriedade de `defunkt` que continham a palavra `GitHub` e `Octocat` no arquivo README, você usaria a consulta seguinte com o ponto de extremidade _pesquisar repositórios_:
-
-```
-GitHub Octocat in:readme user:defunkt
-```
-
-**Observação:** Certifique-se de usar o codificador HTML preferido do seu idioma para construir suas strings de consulta. Por exemplo:
-```javascript
-// JavaScript
-const queryString = 'q=' + encodeURIComponent('GitHub Octocat in:readme user:defunkt');
-```
-
-Consulte "[Pesquisar no GitHub](/search-github/searching-on-github)" para obter uma lista completa de qualificadores disponíveis, seu formato e um exemplo de como usá-los. Para obter informações sobre como usar operadores para corresponder a quantidades e datas específicas ou para excluir resultados, consulte "[Entender a sintaxe de pesquisa](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax/)".
-
-### Limitações no tamanho da consulta
-
-A API de pesquisa não é compatível com consultas que:
-- têm tamanho superior a 256 caracteres (não incluindo operadores ou qualificadores).
-- têm mais de cinco operadores de `E`, `OU` ou `NÃO` operadores.
-
-Estas consultas de pesquisa irão retornar uma mensagem de erro "Ocorreu uma falha na validação".
-
-### Tempo esgotado e resultados incompletos
-
-Para manter a API de pesquisa rápida para todos, limitamos quanto tempo todas as consulta individual podem ser executadas. Para consultas que [excedem o tempo limite](https://developer.github.com/changes/2014-04-07-understanding-search-results-and-potential-timeouts/), a API retorna as correspondências que já foram encontradas antes do tempo limite, e a resposta tem a propriedade `incomplete_results` definida como `verdadeiro`.
-
-Atingir um tempo limite não significa necessariamente que os resultados da pesquisa estão incompletos. É possível que mais resultados tenham sido, mas também é possível que não.
-
-### Erros de acesso ou resultados de pesquisa ausentes
-
-Você precisa efetuar a autenticação com sucesso e ter acesso aos repositórios nas consultas de pesquisa. Caso contrário, você verá um erro `422 Unprocessable Entry` com uma mensagem "Falha na validação". Por exemplo, sua pesquisa irá falhar se sua consulta incluir qualificadores `repo:`, `user:` ou `org:` que solicitam recursos aos quais você não tem acesso ao efetuar login em {% data variables.product.prodname_dotcom %}.
-
-Quando sua consulta de pesquisa solicitar vários recursos, a resposta só conterá os recursos aos quais você tem acesso e **não** fornecerá uma mensagem de erro listando os recursos que não foram retornados.
-
-Por exemplo, se sua consulta de pesquisa pesquisar os repositórios `octocat/test` e `codertocat/test`, mas você só tem acesso a `octocat/test`, a sua resposta mostrará resultados de pesquisa para `octocat/test` e nenhum resultado para `codertocat/teste`. Este comportamento imita como a pesquisa que funciona no {% data variables.product.prodname_dotcom %}.
-
-{% include rest_operations_at_current_path %}
-
-
-### Metadados da correspondência de texto
-
-No GitHub, você pode usar o contexto fornecido por trechos de código e destaques nos resultados de pesquisa. A API de pesquisa oferece metadados adicionais que permitem que você destaque os termos de pesquisa correspondentes ao exibir resultados de busca.
-
-
-
-As solicitações podem optar por receber esses fragmentos de texto na resposta, e cada fragmento é acompanhado de ajustes numéricos que identificam a localização exata de cada termo de pesquisa correspondente.
-
-Para obter esses metadados nos resultados da sua pesquisa, especifique o tipo de mídia de `text-match` no seu cabeçalho `Aceitar`.
-
-```shell
-application/vnd.github.v3.text-match+json
-```
-
-Ao fornecer o tipo de mídia `text-match`, você receberá uma chave extra na carga do JSON denominada `text_matches`, que fornece informações sobre a posição dos seus termos de pesquisa dentro do texto e da `propriedade` que inclui o termo de pesquisa. Dentro do array `text_match`, cada objeto inclui os atributos a seguir:
-
-| Nome | Descrição |
-| ------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `object_url` | A URL para o recurso que contém uma propriedade de string que corresponde a um dos termos de pesquisa. |
-| `object_type` | O nome para o tipo de recurso que existe em determinado `object_url`. |
-| `propriedade` | O nome de uma propriedade do recurso que existe em `object_url`. Esta propriedade é uma string que corresponde a um dos termos de pesquisa. (No JSON retornado a partir de `object_url`, o conteúdo completo do `fragmento` será encontrado na propriedade com este nome.) |
-| `fragmento` | Um subconjunto do valor de `propriedade`. Este é o fragmento de texto que corresponde a um ou mais dos termos de pesquisa. |
-| `matches` | Um array de um ou mais termos de pesquisa que estão presentes no `fragmento`. Os índices (ou seja, "ajustes") são relativos ao fragmento. (Eles não são relativos ao conteúdo _completo_ de `propriedade`.) |
-
-#### Exemplo
-
-Se usarmos cURL e o [exemplo de pesquisa de problemas](#search-issues-and-pull-requests) acima, nossa solicitação de API seria da seguinte forma:
-
-``` shell
-curl -H 'Accept: application/vnd.github.v3.text-match+json' \
-'{% data variables.product.api_url_pre %}/search/issues?q=windows+label:bug+language:python+state:open&sort=created&order=asc'
-```
-
-A resposta incluirá um array `text_matches` para cada resultado de pesquisa. No JSON abaixo, temos dois objetos no array `text_matches`.
-
-A primeira correspondência de texto ocorreu na propriedade do `texto` do problema. Vemos um fragmento de texto a partir do texto do problema. O termo da pesquisa (`windows`) aparece duas vezes dentro desse fragmento, e temos os índices para cada ocorrência.
-
-A segunda correspondência de texto ocorreu na propriedade do `texto` de um dos comentários do problema. Nós temos a URL do comentário do problema. E, evidentemente, vemos um fragmento de texto do comentário. O termo de pesquisa (`windows`) aparece uma vez dentro desse fragmento.
-
-```json
-{
- "text_matches": [
- {
- "object_url": "https://api.github.com/repositories/215335/issues/132",
- "object_type": "Issue",
- "property": "body",
- "fragment": "comprehensive windows font I know of).\n\nIf we can find a commonly distributed windows font that supports them then no problem (we can use html font tags) but otherwise the '(21)' style is probably better.\n",
- "matches": [
- {
- "text": "windows",
- "indices": [
- 14,
- 21
- ]
- },
- {
- "text": "windows",
- "indices": [
- 78,
- 85
- ]
- }
- ]
- },
- {
- "object_url": "https://api.github.com/repositories/215335/issues/comments/25688",
- "object_type": "IssueComment",
- "property": "body",
- "fragment": " right after that are a bit broken IMHO :). I suppose we could have some hack that maxes out at whatever the font does...\n\nI'll check what the state of play is on Windows.\n",
- "matches": [
- {
- "text": "Windows",
- "indices": [
- 163,
- 170
- ]
- }
- ]
- }
- ]
-}
-```
+
diff --git a/translations/pt-BR/content/rest/reference/secret-scanning.md b/translations/pt-BR/content/rest/reference/secret-scanning.md
index a5f3e0390bd8..741acf9c0615 100644
--- a/translations/pt-BR/content/rest/reference/secret-scanning.md
+++ b/translations/pt-BR/content/rest/reference/secret-scanning.md
@@ -9,14 +9,6 @@ versions:
miniTocMaxHeadingLevel: 3
---
-{% data reusables.secret-scanning.api-beta %}
-
-A API de {% data variables.product.prodname_secret_scanning %} permite que você{% ifversion fpt or ghec or ghes > 3.1 or ghae %}:
-
-- Habilitar ou desabilitar {% data variables.product.prodname_secret_scanning %} para um repositório. Para obter mais informações, consulte "[Repositórios](/rest/reference/repos#update-a-repository)" na documentação da API REST.
-- Recuperar e atualizar alertas de {% data variables.product.prodname_secret_scanning %} a partir de um repositório {% ifversion fpt or ghec %}privado {% endif %}. Para obter detalhes adicionais, consulte as seções abaixo.
-{%- else %} recuperar e atualizar alertas de {% data variables.product.prodname_secret_scanning %} a partir de um repositório {% ifversion fpt or ghec %}privado{% endif %}.{% endif %}
-
-Para obter mais informações sobre {% data variables.product.prodname_secret_scanning %}, consulte "[Sobre {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/about-secret-scanning)."
-
-{% include rest_operations_at_current_path %}
+
diff --git a/translations/pt-BR/content/rest/reference/teams.md b/translations/pt-BR/content/rest/reference/teams.md
index d5790631d39d..037c457dae40 100644
--- a/translations/pt-BR/content/rest/reference/teams.md
+++ b/translations/pt-BR/content/rest/reference/teams.md
@@ -13,84 +13,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-Esta API só está disponível para os integrantes autenticados da [organização](/rest/reference/orgs) da equipe. Os tokens de acesso do OAuth exigem o escopo `read:org` [](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/). {% data variables.product.prodname_dotcom %} gera o `slug` da equipe a partir do `nome` da equipe.
-
-{% for operation in currentRestOperations %}
- {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
-{% endfor %}
-
-## Discussões
-
-A API de discussões de equipe permite que você obtenha, crie, edite e exclua postagens de discussão na página de uma equipe. Você pode usar discussões da equipe para ter conversas que não são específicas para um repositório ou projeto. Qualquer integrante da [organização](/rest/reference/orgs) da equipe pode criar e ler posts de discussão públicos. Para obter mais informações, consulte "[Sobre discussões de equipe](//organizations/collaborating-with-your-team/about-team-discussions/)". Para aprender mais sobre comentários em uma publicação de discussão, consulte [a API de comentários de discussão em equipe](/rest/reference/teams#discussion-comments). Esta API só está disponível para os integrantes autenticados da organização da equipe.
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'discussions' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## Comentários da discussão
-
-A API de comentários de discussão em equipe permite que você obtenha, crie, edite e exclua comentários de discussão em um post de [discussão de equipe](/rest/reference/teams#discussions). Qualquer integrante da organização da [organização](/rest/reference/orgs) da equipe pode criar e ler comentários em uma discussão pública. Para obter mais informações, consulte "[Sobre discussões de equipe](/organizations/collaborating-with-your-team/about-team-discussions/)". Esta API só está disponível para os integrantes autenticados da organização da equipe.
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'discussion-comments' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## Integrantes
-
-Esta API só está disponível para os integrantes autenticados da organização da equipe. Os tokens de acesso do OAuth exigem o escopo `read:org` [](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/).
-
-{% ifversion fpt or ghes or ghec %}
-{% note %}
-
-**Observação:** Quando você tiver configurado a sincronização da equipe para uma equipe com o provedor de identidade (IdP) da sua organização, você receberá uma mensagem de erro se tentar usar a API para fazer alterações na associação da equipe. Se você tiver acesso para administrar a associação do grupo em seu IdP, você pode administrar a associação da equipe do GitHub através do seu provedor de identidade, que adiciona e remove automaticamente os integrantes da equipe em uma organização. Para obter mais informações, consulte "Sincronizar equipes entre seu provedor de identidade e o GitHub".
-
-{% endnote %}
-
-{% endif %}
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'members' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% ifversion ghec or ghae %}
-## Grupos externos
-
-A API de grupos externos permite que você visualize os grupos de provedores de identidade externos que estão disponíveis para sua organização e gerencie a conexão entre grupos externos e equipes na sua organização.
-
-Para usar esta API, o usuário autenticado deve ser um mantenedor de equipe ou um proprietário da organização associada à equipe.
-
-{% ifversion ghec %}
-{% note %}
-
-**Notas:**
-
-- A API de grupos externos está disponível apenas para organizações que fazem parte de uma empresa que usa {% data variables.product.prodname_emus %}. Para obter mais informações, consulte[Sobre usuários gerenciados pela empresa](/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)".
-- Se sua organização usar a sincronização de equipe, você poderá usar a API de sincronização de equipe. Para obter mais informações, consulte "[API de sincronização de equipe](#team-synchronization)".
-
-{% endnote %}
-{% endif %}
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'external-groups' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% endif %}
-
-{% ifversion fpt or ghes or ghec %}
-## Sincronização de equipes
-
-A API de Sincronização da Equipe permite que você gerencie as conexões entre equipes de {% data variables.product.product_name %} e grupos de provedor de identidade externo (IdP). Para usar esta API, o usuário autenticado deve ser um mantenedor de equipe ou um proprietário da organização associada à equipe. O token que você usa para efetuar a autenticação também deverá ser autorizado para uso com o provedor de IdP (SSO). Para obter mais informações, consulte "Autorizando um token de acesso pessoal para uso com uma organização de logon único SAML".
-
-Você pode gerenciar os integrantes da equipe do GitHub através do seu IdP com a sincronização de equipe. A sincronização de equipe deve estar habilitada para usar a API de sincronização de equipe. Para obter mais informações, consulte "Sincronizar equipes entre seu provedor de identidade e o GitHub".
-
-{% note %}
-
-**Observação:** A API de sincronização de equipe não pode ser usada com {% data variables.product.prodname_emus %}. Para saber mais sobre como gerenciar um {% data variables.product.prodname_emu_org %}, consulte "[API de grupos externos](/enterprise-cloud@latest/rest/reference/teams#external-groups)".
-
-{% endnote %}
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'team-sync' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% endif %}
+
diff --git a/translations/pt-BR/content/rest/reference/users.md b/translations/pt-BR/content/rest/reference/users.md
index 964832d86b1a..724375934b67 100644
--- a/translations/pt-BR/content/rest/reference/users.md
+++ b/translations/pt-BR/content/rest/reference/users.md
@@ -13,48 +13,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-Muitos dos recursos na API de usuários fornecem um atalho para obter informações sobre o usuário autenticado atualmente. Se uma URL de solicitação não incluir um parâmetro `{username}`, a resposta será para o usuário conectado (e você deve passar [informações de autenticação](/rest/overview/resources-in-the-rest-api#authentication) com sua solicitação).{% ifversion fpt or ghes or ghec %} Informações privadas adicionais, como se um usuário tem autenticação de dois fatores habilitada, estão incluídas quando a autenticação é efetuada por meio da autenticação básica ou OAuth com o escopo do `usuário` .{% endif %}
-
-{% for operation in currentRestOperations %}
- {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
-{% endfor %}
-
-{% ifversion fpt or ghec %}
-## Bloquear usuários
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'blocking' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% endif %}
-
-{% ifversion fpt or ghes or ghec %}
-## E-mails
-
-O gerenciamento de endereços de e-mail através da API requer que você efetue a autenticação por meio de autenticação básica, ou através do OAuth com um escopo correto para o ponto de extremidade.
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'emails' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% endif %}
-
-## Seguidores
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'followers' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## Chaves SSH do Git
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'keys' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## Chaves GPG
-
-Os dados retornados no campo de resposta `public_key` não são uma chave com formato GPG. Quando um usuário faz o upload de uma chave GPG, ela é analisada e a chave pública criptográfica é extraída e armazenada. Essa chave criptográfica é o que é retornado pelas APIs nesta página. Esta chave não é adequada para ser usada diretamente por programas como o GPG.
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'gpg-keys' %}{% include rest_operation %}{% endif %}
-{% endfor %}
+
diff --git a/translations/pt-BR/content/rest/reference/webhooks.md b/translations/pt-BR/content/rest/reference/webhooks.md
index be3c51cfe1b2..d7d2a3911c80 100644
--- a/translations/pt-BR/content/rest/reference/webhooks.md
+++ b/translations/pt-BR/content/rest/reference/webhooks.md
@@ -12,83 +12,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-Os webhooks de repositório permitem que você receba cargas de `POST` de HTTP sempre que certos eventos ocorrerem em um repositório. {% data reusables.webhooks.webhooks-rest-api-links %}
-
-Se você deseja configurar um único webhook para receber eventos de todos os repositórios da organização, consulte nossa documentação de API para [Webhooks de organização](/rest/reference/orgs#webhooks).
-
-Além da API REST, {% data variables.product.prodname_dotcom %} também pode servir como um núcleo de [PubSubHubbub](#pubsubhubbub) para repositórios.
-
-{% for operation in currentRestOperations %}
- {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
-{% endfor %}
-
-## Webhooks do repositório
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'repos' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## Configuração de webhook do repositório
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'repo-config' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## Entregas do webhook do repositório
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'repo-deliveries' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## Receber Webhooks
-
-Para que {% data variables.product.product_name %} envie cargas de webhook, seu servidor deve ser acessível pela internet. É altamente recomendável o uso de SSL para que possamos enviar cargas criptografadas por HTTPS.
-
-### Cabeçalhos de webhook
-
-{% data variables.product.product_name %} enviará ao longo de vários cabeçalhos de HTTP para diferenciar entre tipos de evento e identificadores de carga. Consulte [cabeçalhos de webhook](/developers/webhooks-and-events/webhook-events-and-payloads#delivery-headers) para obter informações.
-
-## PubSubHubbub
-
-O GitHub também pode servir como um centro de [PubSubHubbub](https://github.com/pubsubhubbub/PubSubHubbub) para todos os repositórios. O PSHB é um simples protocolo de publicação/assinatura que permite o registro de servidores para receber atualizações quando um tópico é atualizado. As atualizações são enviadas com uma solicitação HTTP do tipo POST para uma URL de chamada de retorno. As URLs dos tópicos dos pushes de um repositório do GitHub estão neste formato:
-
-`https://github.com/{owner}/{repo}/events/{event}`
-
-O evento pode ser qualquer evento de webhook disponível. Para obter mais informações, consulte "[Eventos e cargas de Webhook](/developers/webhooks-and-events/webhook-events-and-payloads)".
-
-### Formato de resposta
-
-O formato padrão é o que [os hooks post-receive existentes devem esperar](/post-receive-hooks/): Um texto JSON enviado como parâmetro `payload` em um POST. Você também pode especificar para receber o texto do JSON sem processar com um cabeçalho `Aceitar` ou uma extensão `.json`.
-
- Accept: application/json
- https://github.com/{owner}/{repo}/events/push.json
-
-### URLs de chamada de retorno
-
-As URLs de chamada de retorno podem usar o protocolo `http://`.
-
- # Send updates to postbin.org
- http://postbin.org/123
-
-### Assinar
-
-O ponto de extremidade do GitHub PubSubHubbub é: `{% data variables.product.api_url_code %}/hub`. Uma solicitação bem-sucedida com o curl parece como:
-
-``` shell
-curl -u "user" -i \
- {% data variables.product.api_url_pre %}/hub \
- -F "hub.mode=subscribe" \
- -F "hub.topic=https://github.com/{owner}/{repo}/events/push" \
- -F "hub.callback=http://postbin.org/123"
-```
-
-Solicitações do PubSubHubbub podem ser enviadas várias vezes. Se o hook já existe, ele será modificado de acordo com a solicitação.
-
-#### Parâmetros
-
-| Nome | Tipo | Descrição |
-| -------------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `hub.mode` | `string` | **Obrigatório**. `Assine` ou `cancele a assinatura`. |
-| `hub.topic` | `string` | **Obrigatório**. A URI do repositório do GitHub a ser assinada. O caminho deve estar no formato `/{owner}/{repo}/events/{event}`. |
-| `hub.callback` | `string` | A URI para receber as atualizações do tópico. |
-| `hub.secret` | `string` | Uma chave de segredo compartilhado que gera uma assinatura de hash do conteúdo de saída do texto. Você pode verificar se um push veio do GitHub comparando o texto da solicitação sem processar com o conteúdo dos cabeçalho do {% ifversion fpt or ghes > 2.22 or ghec %}`X-Hub-Signature` ou `X-Hub-Signature-256` {% elsif ghes < 3.0 %}`X-Hub-Signature` {% elsif ghae %}cabeçalho `X-Hub-Signature-256` {% endif %}. Você pode ver [a documentação do PubSubHubbub](https://pubsubhubbub.github.io/PubSubHubbub/pubsubhubbub-core-0.4.html#authednotify) para obter mais informações. |
+
diff --git a/translations/pt-BR/data/graphql/ghae/graphql_upcoming_changes.public-ghae.yml b/translations/pt-BR/data/graphql/ghae/graphql_upcoming_changes.public-ghae.yml
index 7ec32796da06..732b5cc50567 100644
--- a/translations/pt-BR/data/graphql/ghae/graphql_upcoming_changes.public-ghae.yml
+++ b/translations/pt-BR/data/graphql/ghae/graphql_upcoming_changes.public-ghae.yml
@@ -112,3 +112,17 @@ upcoming_changes:
date: '2021-10-01T00:00:00+00:00'
criticality: breaking
owner: synthead
+ -
+ location: PullRequest.viewerCanOverrideMergeQueue
+ description: '`viewerCanOverrideMergeQueue` will be removed. Use PullRequest.viewerCanMergeAsAdmin instead.'
+ reason: '`viewer_can_override_merge_queue` will be removed'
+ date: '2022-04-01'
+ criticality: breaking
+ owner: cbeaman
+ -
+ location: Repository.defaultMergeQueue
+ description: '`defaultMergeQueue` will be removed. Use `Repository.mergeQueue` instead.'
+ reason: '`defaultMergeQueue` will be removed.'
+ date: '2022-04-01'
+ criticality: breaking
+ owner: colinshum
diff --git a/translations/pt-BR/data/graphql/ghec/graphql_upcoming_changes.public.yml b/translations/pt-BR/data/graphql/ghec/graphql_upcoming_changes.public.yml
index 0d924c23dc60..048df6cade6b 100644
--- a/translations/pt-BR/data/graphql/ghec/graphql_upcoming_changes.public.yml
+++ b/translations/pt-BR/data/graphql/ghec/graphql_upcoming_changes.public.yml
@@ -126,3 +126,24 @@ upcoming_changes:
date: '2021-10-01T00:00:00+00:00'
criticality: breaking
owner: synthead
+ -
+ location: PullRequest.viewerCanOverrideMergeQueue
+ description: '`viewerCanOverrideMergeQueue` will be removed. Use PullRequest.viewerCanMergeAsAdmin instead.'
+ reason: '`viewer_can_override_merge_queue` will be removed'
+ date: '2022-04-01'
+ criticality: breaking
+ owner: cbeaman
+ -
+ location: Repository.defaultMergeQueue
+ description: '`defaultMergeQueue` will be removed. Use `Repository.mergeQueue` instead.'
+ reason: '`defaultMergeQueue` will be removed.'
+ date: '2022-04-01'
+ criticality: breaking
+ owner: colinshum
+ -
+ location: Query.sponsorables.dependencyEcosystem
+ description: '`dependencyEcosystem` will be removed. Use the ecosystem argument instead.'
+ reason: The type is switching from SecurityAdvisoryEcosystem to DependencyGraphEcosystem.
+ date: '2022-07-01T00:00:00+00:00'
+ criticality: breaking
+ owner: cheshire137
diff --git a/translations/pt-BR/data/graphql/graphql_upcoming_changes.public.yml b/translations/pt-BR/data/graphql/graphql_upcoming_changes.public.yml
index 0d924c23dc60..048df6cade6b 100644
--- a/translations/pt-BR/data/graphql/graphql_upcoming_changes.public.yml
+++ b/translations/pt-BR/data/graphql/graphql_upcoming_changes.public.yml
@@ -126,3 +126,24 @@ upcoming_changes:
date: '2021-10-01T00:00:00+00:00'
criticality: breaking
owner: synthead
+ -
+ location: PullRequest.viewerCanOverrideMergeQueue
+ description: '`viewerCanOverrideMergeQueue` will be removed. Use PullRequest.viewerCanMergeAsAdmin instead.'
+ reason: '`viewer_can_override_merge_queue` will be removed'
+ date: '2022-04-01'
+ criticality: breaking
+ owner: cbeaman
+ -
+ location: Repository.defaultMergeQueue
+ description: '`defaultMergeQueue` will be removed. Use `Repository.mergeQueue` instead.'
+ reason: '`defaultMergeQueue` will be removed.'
+ date: '2022-04-01'
+ criticality: breaking
+ owner: colinshum
+ -
+ location: Query.sponsorables.dependencyEcosystem
+ description: '`dependencyEcosystem` will be removed. Use the ecosystem argument instead.'
+ reason: The type is switching from SecurityAdvisoryEcosystem to DependencyGraphEcosystem.
+ date: '2022-07-01T00:00:00+00:00'
+ criticality: breaking
+ owner: cheshire137
diff --git a/translations/pt-BR/data/reusables/github-actions/actions-activity-types.md b/translations/pt-BR/data/reusables/actions/actions-activity-types.md
similarity index 100%
rename from translations/pt-BR/data/reusables/github-actions/actions-activity-types.md
rename to translations/pt-BR/data/reusables/actions/actions-activity-types.md
diff --git a/translations/pt-BR/data/reusables/github-actions/actions-billing.md b/translations/pt-BR/data/reusables/actions/actions-billing.md
similarity index 100%
rename from translations/pt-BR/data/reusables/github-actions/actions-billing.md
rename to translations/pt-BR/data/reusables/actions/actions-billing.md
diff --git a/translations/pt-BR/data/reusables/github-actions/actions-do-not-trigger-workflows.md b/translations/pt-BR/data/reusables/actions/actions-do-not-trigger-workflows.md
similarity index 100%
rename from translations/pt-BR/data/reusables/github-actions/actions-do-not-trigger-workflows.md
rename to translations/pt-BR/data/reusables/actions/actions-do-not-trigger-workflows.md
diff --git a/translations/pt-BR/data/reusables/github-actions/actions-filters.md b/translations/pt-BR/data/reusables/actions/actions-filters.md
similarity index 100%
rename from translations/pt-BR/data/reusables/github-actions/actions-filters.md
rename to translations/pt-BR/data/reusables/actions/actions-filters.md
diff --git a/translations/pt-BR/data/reusables/github-actions/actions-multiple-types.md b/translations/pt-BR/data/reusables/actions/actions-multiple-types.md
similarity index 100%
rename from translations/pt-BR/data/reusables/github-actions/actions-multiple-types.md
rename to translations/pt-BR/data/reusables/actions/actions-multiple-types.md
diff --git a/translations/pt-BR/data/reusables/actions/actions-on-examples.md b/translations/pt-BR/data/reusables/actions/actions-on-examples.md
new file mode 100644
index 000000000000..80c7fc67d29b
--- /dev/null
+++ b/translations/pt-BR/data/reusables/actions/actions-on-examples.md
@@ -0,0 +1,19 @@
+### Using a single event
+
+{% data reusables.actions.on-single-example %}
+
+### Using multiple events
+
+{% data reusables.actions.on-multiple-example %}
+
+### Using activity types
+
+{% data reusables.actions.actions-activity-types %}
+
+### Using filters
+
+{% data reusables.actions.actions-filters %}
+
+### Using activity types and filters with multiple events
+
+{% data reusables.actions.actions-multiple-types %}
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/github-actions/actions-spending-limit-brief.md b/translations/pt-BR/data/reusables/actions/actions-spending-limit-brief.md
similarity index 100%
rename from translations/pt-BR/data/reusables/github-actions/actions-spending-limit-brief.md
rename to translations/pt-BR/data/reusables/actions/actions-spending-limit-brief.md
diff --git a/translations/pt-BR/data/reusables/github-actions/actions-spending-limit-detailed.md b/translations/pt-BR/data/reusables/actions/actions-spending-limit-detailed.md
similarity index 87%
rename from translations/pt-BR/data/reusables/github-actions/actions-spending-limit-detailed.md
rename to translations/pt-BR/data/reusables/actions/actions-spending-limit-detailed.md
index e2d06772791a..f5b6c230fab5 100644
--- a/translations/pt-BR/data/reusables/github-actions/actions-spending-limit-detailed.md
+++ b/translations/pt-BR/data/reusables/actions/actions-spending-limit-detailed.md
@@ -1,3 +1,3 @@
-{% data reusables.github-actions.actions-spending-limit-brief %}
+{% data reusables.actions.actions-spending-limit-brief %}
If you have an unlimited spending limit or a spending limit set higher than $0 USD, you will be billed for any additional minutes or storage beyond the included amounts in your account, also called overages. {% data variables.product.prodname_dotcom %} cobra o uso da conta do repositório em que um fluxo de trabalho é executado. Quaisquer cupons em sua conta não se aplicam a {% data variables.product.prodname_actions %} excessos.
diff --git a/translations/pt-BR/data/reusables/github-actions/actions-unused-labels.md b/translations/pt-BR/data/reusables/actions/actions-unused-labels.md
similarity index 100%
rename from translations/pt-BR/data/reusables/github-actions/actions-unused-labels.md
rename to translations/pt-BR/data/reusables/actions/actions-unused-labels.md
diff --git a/translations/pt-BR/data/reusables/github-actions/artifact-log-retention-statement.md b/translations/pt-BR/data/reusables/actions/artifact-log-retention-statement.md
similarity index 100%
rename from translations/pt-BR/data/reusables/github-actions/artifact-log-retention-statement.md
rename to translations/pt-BR/data/reusables/actions/artifact-log-retention-statement.md
diff --git a/translations/pt-BR/data/reusables/github-actions/branch-paths-filter.md b/translations/pt-BR/data/reusables/actions/branch-paths-filter.md
similarity index 100%
rename from translations/pt-BR/data/reusables/github-actions/branch-paths-filter.md
rename to translations/pt-BR/data/reusables/actions/branch-paths-filter.md
diff --git a/translations/pt-BR/data/reusables/github-actions/branch-requirement.md b/translations/pt-BR/data/reusables/actions/branch-requirement.md
similarity index 100%
rename from translations/pt-BR/data/reusables/github-actions/branch-requirement.md
rename to translations/pt-BR/data/reusables/actions/branch-requirement.md
diff --git a/translations/pt-BR/data/reusables/github-actions/change-retention-period-for-artifacts-logs.md b/translations/pt-BR/data/reusables/actions/change-retention-period-for-artifacts-logs.md
similarity index 100%
rename from translations/pt-BR/data/reusables/github-actions/change-retention-period-for-artifacts-logs.md
rename to translations/pt-BR/data/reusables/actions/change-retention-period-for-artifacts-logs.md
diff --git a/translations/pt-BR/data/reusables/github-actions/contacting-support.md b/translations/pt-BR/data/reusables/actions/contacting-support.md
similarity index 100%
rename from translations/pt-BR/data/reusables/github-actions/contacting-support.md
rename to translations/pt-BR/data/reusables/actions/contacting-support.md
diff --git a/translations/pt-BR/data/reusables/github-actions/container-jobs-intro.md b/translations/pt-BR/data/reusables/actions/container-jobs-intro.md
similarity index 100%
rename from translations/pt-BR/data/reusables/github-actions/container-jobs-intro.md
rename to translations/pt-BR/data/reusables/actions/container-jobs-intro.md
diff --git a/translations/pt-BR/data/reusables/github-actions/context-injection-warning.md b/translations/pt-BR/data/reusables/actions/context-injection-warning.md
similarity index 100%
rename from translations/pt-BR/data/reusables/github-actions/context-injection-warning.md
rename to translations/pt-BR/data/reusables/actions/context-injection-warning.md
diff --git a/translations/pt-BR/data/reusables/github-actions/copy-workflow-file.md b/translations/pt-BR/data/reusables/actions/copy-workflow-file.md
similarity index 100%
rename from translations/pt-BR/data/reusables/github-actions/copy-workflow-file.md
rename to translations/pt-BR/data/reusables/actions/copy-workflow-file.md
diff --git a/translations/pt-BR/data/reusables/github-actions/defaults-override.md b/translations/pt-BR/data/reusables/actions/defaults-override.md
similarity index 100%
rename from translations/pt-BR/data/reusables/github-actions/defaults-override.md
rename to translations/pt-BR/data/reusables/actions/defaults-override.md
diff --git a/translations/pt-BR/data/reusables/github-actions/disabled-actions-description.md b/translations/pt-BR/data/reusables/actions/disabled-actions-description.md
similarity index 100%
rename from translations/pt-BR/data/reusables/github-actions/disabled-actions-description.md
rename to translations/pt-BR/data/reusables/actions/disabled-actions-description.md
diff --git a/translations/pt-BR/data/reusables/github-actions/disabling-github-actions.md b/translations/pt-BR/data/reusables/actions/disabling-github-actions.md
similarity index 100%
rename from translations/pt-BR/data/reusables/github-actions/disabling-github-actions.md
rename to translations/pt-BR/data/reusables/actions/disabling-github-actions.md
diff --git a/translations/pt-BR/data/reusables/github-actions/docker-container-os-support.md b/translations/pt-BR/data/reusables/actions/docker-container-os-support.md
similarity index 100%
rename from translations/pt-BR/data/reusables/github-actions/docker-container-os-support.md
rename to translations/pt-BR/data/reusables/actions/docker-container-os-support.md
diff --git a/translations/pt-BR/data/reusables/github-actions/dockerfile-guidelines.md b/translations/pt-BR/data/reusables/actions/dockerfile-guidelines.md
similarity index 100%
rename from translations/pt-BR/data/reusables/github-actions/dockerfile-guidelines.md
rename to translations/pt-BR/data/reusables/actions/dockerfile-guidelines.md
diff --git a/translations/pt-BR/data/reusables/github-actions/enabled-actions-description.md b/translations/pt-BR/data/reusables/actions/enabled-actions-description.md
similarity index 100%
rename from translations/pt-BR/data/reusables/github-actions/enabled-actions-description.md
rename to translations/pt-BR/data/reusables/actions/enabled-actions-description.md
diff --git a/translations/pt-BR/data/reusables/github-actions/enabled-local-github-actions.md b/translations/pt-BR/data/reusables/actions/enabled-local-github-actions.md
similarity index 100%
rename from translations/pt-BR/data/reusables/github-actions/enabled-local-github-actions.md
rename to translations/pt-BR/data/reusables/actions/enabled-local-github-actions.md
diff --git a/translations/pt-BR/data/reusables/github-actions/enterprise-billing-details.md b/translations/pt-BR/data/reusables/actions/enterprise-billing-details.md
similarity index 100%
rename from translations/pt-BR/data/reusables/github-actions/enterprise-billing-details.md
rename to translations/pt-BR/data/reusables/actions/enterprise-billing-details.md
diff --git a/translations/pt-BR/data/reusables/github-actions/example-github-runner.md b/translations/pt-BR/data/reusables/actions/example-github-runner.md
similarity index 100%
rename from translations/pt-BR/data/reusables/github-actions/example-github-runner.md
rename to translations/pt-BR/data/reusables/actions/example-github-runner.md
diff --git a/translations/pt-BR/data/reusables/github-actions/expression-syntax-if.md b/translations/pt-BR/data/reusables/actions/expression-syntax-if.md
similarity index 100%
rename from translations/pt-BR/data/reusables/github-actions/expression-syntax-if.md
rename to translations/pt-BR/data/reusables/actions/expression-syntax-if.md
diff --git a/translations/pt-BR/data/reusables/github-actions/forked-write-permission.md b/translations/pt-BR/data/reusables/actions/forked-write-permission.md
similarity index 51%
rename from translations/pt-BR/data/reusables/github-actions/forked-write-permission.md
rename to translations/pt-BR/data/reusables/actions/forked-write-permission.md
index c9b68598b0e2..625ed14a6d9e 100644
--- a/translations/pt-BR/data/reusables/github-actions/forked-write-permission.md
+++ b/translations/pt-BR/data/reusables/actions/forked-write-permission.md
@@ -1 +1 @@
-Você pode usar a chave de `permissões` para adicionar e remover permissões de leitura para repositórios bifurcados, mas, normalmente, você não pode conceder acesso de gravação. A exceção para esse comportamento é quando um usuário administrador selecionou a opção **Enviar tokens para fluxos de trabalho de pull requests** nas configurações do {% data variables.product.prodname_actions %}. For more information, see "[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#enabling-workflows-for-private-repository-forks)."
+Você pode usar a chave de `permissões` para adicionar e remover permissões de leitura para repositórios bifurcados, mas, normalmente, você não pode conceder acesso de gravação. A exceção para esse comportamento é quando um usuário administrador selecionou a opção **Enviar tokens para fluxos de trabalho de pull requests** nas configurações do {% data variables.product.prodname_actions %}. Para obter mais informações, consulte "[Gerenciar configurações de {% data variables.product.prodname_actions %} para um repositório](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#enabling-workflows-for-private-repository-forks)".
diff --git a/translations/pt-BR/data/reusables/actions/ghes-actions-not-enabled-by-default.md b/translations/pt-BR/data/reusables/actions/ghes-actions-not-enabled-by-default.md
new file mode 100644
index 000000000000..ba7a3362edaf
--- /dev/null
+++ b/translations/pt-BR/data/reusables/actions/ghes-actions-not-enabled-by-default.md
@@ -0,0 +1 @@
+Por padrão, {% data variables.product.prodname_actions %} não está habilitado para {% data variables.product.prodname_ghe_server %}.
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/github-actions/github-context-warning.md b/translations/pt-BR/data/reusables/actions/github-context-warning.md
similarity index 100%
rename from translations/pt-BR/data/reusables/github-actions/github-context-warning.md
rename to translations/pt-BR/data/reusables/actions/github-context-warning.md
diff --git a/translations/pt-BR/data/reusables/github-actions/github-hosted-runners-check-concurrency.md b/translations/pt-BR/data/reusables/actions/github-hosted-runners-check-concurrency.md
similarity index 100%
rename from translations/pt-BR/data/reusables/github-actions/github-hosted-runners-check-concurrency.md
rename to translations/pt-BR/data/reusables/actions/github-hosted-runners-check-concurrency.md
diff --git a/translations/pt-BR/data/reusables/github-actions/github-hosted-runners-navigate-to-repo-org-enterprise.md b/translations/pt-BR/data/reusables/actions/github-hosted-runners-navigate-to-repo-org-enterprise.md
similarity index 100%
rename from translations/pt-BR/data/reusables/github-actions/github-hosted-runners-navigate-to-repo-org-enterprise.md
rename to translations/pt-BR/data/reusables/actions/github-hosted-runners-navigate-to-repo-org-enterprise.md
diff --git a/translations/pt-BR/data/reusables/github-actions/github-hosted-runners-table-entry.md b/translations/pt-BR/data/reusables/actions/github-hosted-runners-table-entry.md
similarity index 100%
rename from translations/pt-BR/data/reusables/github-actions/github-hosted-runners-table-entry.md
rename to translations/pt-BR/data/reusables/actions/github-hosted-runners-table-entry.md
diff --git a/translations/ja-JP/data/reusables/github-actions/github-token-available-permissions.md b/translations/pt-BR/data/reusables/actions/github-token-available-permissions.md
similarity index 60%
rename from translations/ja-JP/data/reusables/github-actions/github-token-available-permissions.md
rename to translations/pt-BR/data/reusables/actions/github-token-available-permissions.md
index bf0c6b91432a..5af40196917d 100644
--- a/translations/ja-JP/data/reusables/github-actions/github-token-available-permissions.md
+++ b/translations/pt-BR/data/reusables/actions/github-token-available-permissions.md
@@ -1,4 +1,4 @@
-利用できるスコープとアクセスの値は以下のとおりです。
+Available scopes and access values:
```yaml
permissions:
@@ -17,9 +17,9 @@ permissions:
statuses: read|write|none
```
-これらのスコープのいずれかに対してアクセスを指定した場合、指定されなかったスコープは`none`に設定されます。
+If you specify the access for any of these scopes, all of those that are not specified are set to `none`.
-利用可能なすべてのスコープに対する読み取りあるいは書き込みアクセス権を定義するためには、以下の構文が使えます。
+You can use the following syntax to define read or write access for all of the available scopes:
```yaml
permissions: read-all|write-all
diff --git a/translations/pt-BR/data/reusables/github-actions/github-token-permissions.md b/translations/pt-BR/data/reusables/actions/github-token-permissions.md
similarity index 100%
rename from translations/pt-BR/data/reusables/github-actions/github-token-permissions.md
rename to translations/pt-BR/data/reusables/actions/github-token-permissions.md
diff --git a/translations/pt-BR/data/reusables/github-actions/github_token-input-example.md b/translations/pt-BR/data/reusables/actions/github_token-input-example.md
similarity index 100%
rename from translations/pt-BR/data/reusables/github-actions/github_token-input-example.md
rename to translations/pt-BR/data/reusables/actions/github_token-input-example.md
diff --git a/translations/pt-BR/data/reusables/github-actions/gradle-workflow-steps.md b/translations/pt-BR/data/reusables/actions/gradle-workflow-steps.md
similarity index 100%
rename from translations/pt-BR/data/reusables/github-actions/gradle-workflow-steps.md
rename to translations/pt-BR/data/reusables/actions/gradle-workflow-steps.md
diff --git a/translations/pt-BR/data/reusables/github-actions/hosted-runner-configure-runner-group-access.md b/translations/pt-BR/data/reusables/actions/hosted-runner-configure-runner-group-access.md
similarity index 100%
rename from translations/pt-BR/data/reusables/github-actions/hosted-runner-configure-runner-group-access.md
rename to translations/pt-BR/data/reusables/actions/hosted-runner-configure-runner-group-access.md
diff --git a/translations/pt-BR/data/reusables/github-actions/hosted-runner-labels-view-assigned-labels.md b/translations/pt-BR/data/reusables/actions/hosted-runner-labels-view-assigned-labels.md
similarity index 100%
rename from translations/pt-BR/data/reusables/github-actions/hosted-runner-labels-view-assigned-labels.md
rename to translations/pt-BR/data/reusables/actions/hosted-runner-labels-view-assigned-labels.md
diff --git a/translations/pt-BR/data/reusables/github-actions/hosted-runner-list-group.md b/translations/pt-BR/data/reusables/actions/hosted-runner-list-group.md
similarity index 100%
rename from translations/pt-BR/data/reusables/github-actions/hosted-runner-list-group.md
rename to translations/pt-BR/data/reusables/actions/hosted-runner-list-group.md
diff --git a/translations/pt-BR/data/reusables/github-actions/hosted-runner-list.md b/translations/pt-BR/data/reusables/actions/hosted-runner-list.md
similarity index 100%
rename from translations/pt-BR/data/reusables/github-actions/hosted-runner-list.md
rename to translations/pt-BR/data/reusables/actions/hosted-runner-list.md
diff --git a/translations/pt-BR/data/reusables/github-actions/invalid-workflow-files.md b/translations/pt-BR/data/reusables/actions/invalid-workflow-files.md
similarity index 100%
rename from translations/pt-BR/data/reusables/github-actions/invalid-workflow-files.md
rename to translations/pt-BR/data/reusables/actions/invalid-workflow-files.md
diff --git a/translations/pt-BR/data/reusables/actions/ip-allow-list-self-hosted-runners.md b/translations/pt-BR/data/reusables/actions/ip-allow-list-self-hosted-runners.md
new file mode 100644
index 000000000000..6ad55b73043e
--- /dev/null
+++ b/translations/pt-BR/data/reusables/actions/ip-allow-list-self-hosted-runners.md
@@ -0,0 +1,11 @@
+{% ifversion ghae %}
+Para permitir que seus executores auto-hospedados se comuniquem com {% data variables.product.prodname_dotcom %}, adicione o endereço IP ou o intervalo de endereços IP dos seus executores auto-hospedados para à lista de permitir IP. Para obter mais informações, consulte "[Adding an allowed IP address](#adding-an-allowed-ip-address)."
+{% else %}
+{% warning %}
+
+**Aviso**: Se você usar uma lista de permitir IP e também gostaria de usar {% data variables.product.prodname_actions %}, você deve usar executores auto-hospedados. Para obter mais informações, consulte "[Hosting your own runners](/actions/automating-your-workflow-with-github-actions/about-self-hosted-runners)."
+
+{% endwarning %}
+
+Para permitir que seus executores auto-hospedados se comuniquem com {% data variables.product.prodname_dotcom %}, adicione o endereço IP ou o intervalo de endereços IP dos seus executores auto-hospedados para à lista de permitir IP. Para obter mais informações, consulte "[Adding an allowed IP address](#adding-an-allowed-ip-address)."
+{% endif %}
diff --git a/translations/pt-BR/data/reusables/github-actions/java-jvm-architecture.md b/translations/pt-BR/data/reusables/actions/java-jvm-architecture.md
similarity index 100%
rename from translations/pt-BR/data/reusables/github-actions/java-jvm-architecture.md
rename to translations/pt-BR/data/reusables/actions/java-jvm-architecture.md
diff --git a/translations/pt-BR/data/reusables/actions/jobs/section-assigning-permissions-to-jobs-specific.md b/translations/pt-BR/data/reusables/actions/jobs/section-assigning-permissions-to-jobs-specific.md
index 3b742b9d2cc4..4191bc8a5898 100644
--- a/translations/pt-BR/data/reusables/actions/jobs/section-assigning-permissions-to-jobs-specific.md
+++ b/translations/pt-BR/data/reusables/actions/jobs/section-assigning-permissions-to-jobs-specific.md
@@ -2,8 +2,8 @@ Para um trabalho específico, você pode usar `jobs..permissions` para m
Ao especificar a permissão de uma definição de trabalho, você pode configurar um conjunto diferente de permissões para o `GITHUB_TOKEN` para cada trabalho, se necessário. Como alternativa, você pode especificar as permissões para todas as tarefas do fluxo de trabalho. Para informações sobre como definir permissões no nível do fluxo de trabalho, consulte [`permissões`](/actions/using-workflows/workflow-syntax-for-github-actions#permissions).
-{% data reusables.github-actions.github-token-available-permissions %}
-{% data reusables.github-actions.forked-write-permission %}
+{% data reusables.actions.github-token-available-permissions %}
+{% data reusables.actions.forked-write-permission %}
#### Exemplo: Configurar permissões para um trabalho específico
diff --git a/translations/pt-BR/data/reusables/actions/jobs/section-assigning-permissions-to-jobs.md b/translations/pt-BR/data/reusables/actions/jobs/section-assigning-permissions-to-jobs.md
index 2cdde46e52f2..76c46e7a7ffe 100644
--- a/translations/pt-BR/data/reusables/actions/jobs/section-assigning-permissions-to-jobs.md
+++ b/translations/pt-BR/data/reusables/actions/jobs/section-assigning-permissions-to-jobs.md
@@ -2,8 +2,8 @@ Você pode usar as `permissões` para modificar as permissões padrão concedida
Você pode usar as permissões de `` como uma chave de nível superior, para aplicar a todos os trabalhos do fluxo de trabalho ou em trabalhos específicos. Ao adicionar a chave das `permissões` em um trabalho específico, todas as ações e comandos de execução dentro desse trabalho que usam o `GITHUB_TOKEN` ganham os direitos de acesso que você especificar. Para obter mais informações, consulte [`jobs..permissions`](/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idpermissions).
-{% data reusables.github-actions.github-token-available-permissions %}
-{% data reusables.github-actions.forked-write-permission %}
+{% data reusables.actions.github-token-available-permissions %}
+{% data reusables.actions.forked-write-permission %}
### Exemplo: Atribuindo permissões ao GITHUB_TOKEN
diff --git a/translations/pt-BR/data/reusables/actions/jobs/section-choosing-the-runner-for-a-job.md b/translations/pt-BR/data/reusables/actions/jobs/section-choosing-the-runner-for-a-job.md
index 349be91971ca..c1a66ce8c5ab 100644
--- a/translations/pt-BR/data/reusables/actions/jobs/section-choosing-the-runner-for-a-job.md
+++ b/translations/pt-BR/data/reusables/actions/jobs/section-choosing-the-runner-for-a-job.md
@@ -10,7 +10,7 @@ Se você usar um executor hospedado no {% data variables.product.prodname_dotcom
Os tipos de executor disponíveis para {% data variables.product.prodname_dotcom %} são:
-{% data reusables.github-actions.supported-github-runners %}
+{% data reusables.actions.supported-github-runners %}
#### Exemplo: Especificar um sistema operacional
@@ -27,7 +27,7 @@ Para obter mais informações, consulte "[Ambientes virtuais para executores hos
{% data reusables.actions.ae-self-hosted-runners-notice %}
-{% data reusables.github-actions.self-hosted-runner-labels-runs-on %}
+{% data reusables.actions.self-hosted-runner-labels-runs-on %}
#### Exemplo: Usando etiquetas para seleção do executor
diff --git a/translations/pt-BR/data/reusables/actions/jobs/section-using-a-build-matrix-for-your-jobs-matrix.md b/translations/pt-BR/data/reusables/actions/jobs/section-using-a-build-matrix-for-your-jobs-matrix.md
index 5e36a2d81d51..ee255cdb2870 100644
--- a/translations/pt-BR/data/reusables/actions/jobs/section-using-a-build-matrix-for-your-jobs-matrix.md
+++ b/translations/pt-BR/data/reusables/actions/jobs/section-using-a-build-matrix-for-your-jobs-matrix.md
@@ -1,7 +1,7 @@
Use `jobs..strategy.matrix` to define a matrix of different job configurations. Uma matriz permite que você crie vários trabalhos que realizam a substituição de variável em uma definição de trabalho único. Por exemplo, você pode usar uma matriz para criar trabalhos para mais de uma versão compatível de uma linguagem de programação, sistema operacional ou ferramenta. Uma matriz reutiliza a configuração do trabalho e cria trabalho para cada matriz que você configurar.
-{% data reusables.github-actions.usage-matrix-limits %}
+{% data reusables.actions.usage-matrix-limits %}
Cada opção que você define na `matriz` tem uma chave e um valor. As chaves que você define tornam-se propriedades no contexto da `matriz` e você pode fazer referência à propriedade em outras áreas do seu arquivo de fluxo de trabalho. Por exemplo, se você definir a chave `os` que contém um array de sistemas operacionais, você poderá usar a propriedade `matrix.os` como o valor da palavra-chave `runs-on` para criar um trabalho para cada sistema operacional. Para obter mais informações, consulte "[Contextos](/actions/learn-github-actions/contexts)".
@@ -123,4 +123,4 @@ strategy:
Você pode adicionar variáveis de ambiente personalizadas para cada combinação de testes usando a chave `include`. Em seguida, você pode se referir às variáveis de ambiente personalizadas em um passo posterior.
-{% data reusables.github-actions.matrix-variable-example %}
+{% data reusables.actions.matrix-variable-example %}
diff --git a/translations/pt-BR/data/reusables/actions/jobs/section-using-conditions-to-control-job-execution.md b/translations/pt-BR/data/reusables/actions/jobs/section-using-conditions-to-control-job-execution.md
index 91e048497455..0050d3e599d1 100644
--- a/translations/pt-BR/data/reusables/actions/jobs/section-using-conditions-to-control-job-execution.md
+++ b/translations/pt-BR/data/reusables/actions/jobs/section-using-conditions-to-control-job-execution.md
@@ -1,6 +1,6 @@
Você pode usar a condicional `jobs..if` para evitar que um trabalho seja executado a não ser que determinada condição seja atendida. Você pode usar qualquer contexto e expressão compatível para criar uma condicional.
-{% data reusables.github-actions.expression-syntax-if %} Para obter mais informações, consulte "[Expressões](/actions/learn-github-actions/expressions)".
+{% data reusables.actions.expression-syntax-if %} Para obter mais informações, consulte "[Expressões](/actions/learn-github-actions/expressions)".
### Exemplo: Somente executar o trabalho para um repositório específico
diff --git a/translations/pt-BR/data/reusables/actions/jobs/setting-default-values-for-jobs-defaults-job-run.md b/translations/pt-BR/data/reusables/actions/jobs/setting-default-values-for-jobs-defaults-job-run.md
index 6e46edad1e6a..572f0e67717a 100644
--- a/translations/pt-BR/data/reusables/actions/jobs/setting-default-values-for-jobs-defaults-job-run.md
+++ b/translations/pt-BR/data/reusables/actions/jobs/setting-default-values-for-jobs-defaults-job-run.md
@@ -2,7 +2,7 @@ Use `jobs..defaults.run` para fornecer o `shell` padrão e `workdirector
Você pode fornecer as opções-padrão de `shell` e `working-directory` para todas as etapas de [`execução`](/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idstepsrun) de um trabalho. Você também pode definir as configurações-padrão para `execução` para todo o fluxo de trabalho. Para obter mais informações, consulte [`jobs.defaults.run`](/actions/using-workflows/workflow-syntax-for-github-actions#defaultsrun). Você não pode usar contextos ou expressões nesta palavra-chave.
-{% data reusables.github-actions.defaults-override %}
+{% data reusables.actions.defaults-override %}
#### Exemplo: Configuração padrão da etapa `executar` para um trabalho
diff --git a/translations/pt-BR/data/reusables/actions/jobs/setting-default-values-for-jobs-defaults-job.md b/translations/pt-BR/data/reusables/actions/jobs/setting-default-values-for-jobs-defaults-job.md
index cb8af45fee10..a9182e7c1a16 100644
--- a/translations/pt-BR/data/reusables/actions/jobs/setting-default-values-for-jobs-defaults-job.md
+++ b/translations/pt-BR/data/reusables/actions/jobs/setting-default-values-for-jobs-defaults-job.md
@@ -1,3 +1,3 @@
Use `jobs..defaults` para criar um `mapa` das configurações padrão que será aplicado a todas as etapas do trabalho. Você também pode definir as configurações-padrão para todo o fluxo de trabalho. Para obter mais informações, consulte [`padrão`](/actions/using-workflows/workflow-syntax-for-github-actions#defaults).
-{% data reusables.github-actions.defaults-override %}
\ No newline at end of file
+{% data reusables.actions.defaults-override %}
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/actions/jobs/setting-default-values-for-jobs-defaults-run.md b/translations/pt-BR/data/reusables/actions/jobs/setting-default-values-for-jobs-defaults-run.md
index 2f9dab109daa..da1903ee6da1 100644
--- a/translations/pt-BR/data/reusables/actions/jobs/setting-default-values-for-jobs-defaults-run.md
+++ b/translations/pt-BR/data/reusables/actions/jobs/setting-default-values-for-jobs-defaults-run.md
@@ -1,6 +1,6 @@
Você pode usar `defaults.run` para fornecer o `shell` padrão e as opções de `working-directory` para todas as etapas de [`execução`](/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idstepsrun) em um fluxo de trabalho. Você também pode definir as configurações-padrão para `execução` apenas disponíveis para um trabalho. Para obter mais informações, consulte [`jobs..defaults.run`](/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_iddefaultsrun). Você não pode usar contextos ou expressões nesta palavra-chave.
-{% data reusables.github-actions.defaults-override %}
+{% data reusables.actions.defaults-override %}
#### Exemplo: Defina o shell padrão e o diretório de trabalho
diff --git a/translations/pt-BR/data/reusables/actions/jobs/setting-default-values-for-jobs-defaults.md b/translations/pt-BR/data/reusables/actions/jobs/setting-default-values-for-jobs-defaults.md
index d8d62391398a..f442ca47eb4d 100644
--- a/translations/pt-BR/data/reusables/actions/jobs/setting-default-values-for-jobs-defaults.md
+++ b/translations/pt-BR/data/reusables/actions/jobs/setting-default-values-for-jobs-defaults.md
@@ -1,3 +1,3 @@
Use `padrões` para criar um `mapa` das configurações padrão que serão aplicadas a todos os trabalhos do fluxo de trabalho. Você também pode definir as configurações-padrão disponíveis para um trabalho. Para obter mais informações, consulte [`jobs..defaults`](/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_iddefaults).
-{% data reusables.github-actions.defaults-override %}
\ No newline at end of file
+{% data reusables.actions.defaults-override %}
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/github-actions/macos-runner-preview.md b/translations/pt-BR/data/reusables/actions/macos-runner-preview.md
similarity index 100%
rename from translations/pt-BR/data/reusables/github-actions/macos-runner-preview.md
rename to translations/pt-BR/data/reusables/actions/macos-runner-preview.md
diff --git a/translations/pt-BR/data/reusables/github-actions/matrix-variable-example.md b/translations/pt-BR/data/reusables/actions/matrix-variable-example.md
similarity index 100%
rename from translations/pt-BR/data/reusables/github-actions/matrix-variable-example.md
rename to translations/pt-BR/data/reusables/actions/matrix-variable-example.md
diff --git a/translations/pt-BR/data/reusables/github-actions/name-environment.md b/translations/pt-BR/data/reusables/actions/name-environment.md
similarity index 100%
rename from translations/pt-BR/data/reusables/github-actions/name-environment.md
rename to translations/pt-BR/data/reusables/actions/name-environment.md
diff --git a/translations/pt-BR/data/reusables/github-actions/new-environment.md b/translations/pt-BR/data/reusables/actions/new-environment.md
similarity index 100%
rename from translations/pt-BR/data/reusables/github-actions/new-environment.md
rename to translations/pt-BR/data/reusables/actions/new-environment.md
diff --git a/translations/pt-BR/data/reusables/github-actions/on-multiple-example.md b/translations/pt-BR/data/reusables/actions/on-multiple-example.md
similarity index 100%
rename from translations/pt-BR/data/reusables/github-actions/on-multiple-example.md
rename to translations/pt-BR/data/reusables/actions/on-multiple-example.md
diff --git a/translations/pt-BR/data/reusables/github-actions/on-single-example.md b/translations/pt-BR/data/reusables/actions/on-single-example.md
similarity index 100%
rename from translations/pt-BR/data/reusables/github-actions/on-single-example.md
rename to translations/pt-BR/data/reusables/actions/on-single-example.md
diff --git a/translations/pt-BR/data/reusables/github-actions/permissions-statement-environment.md b/translations/pt-BR/data/reusables/actions/permissions-statement-environment.md
similarity index 100%
rename from translations/pt-BR/data/reusables/github-actions/permissions-statement-environment.md
rename to translations/pt-BR/data/reusables/actions/permissions-statement-environment.md
diff --git a/translations/pt-BR/data/reusables/github-actions/permissions-statement-secrets-api.md b/translations/pt-BR/data/reusables/actions/permissions-statement-secrets-api.md
similarity index 100%
rename from translations/pt-BR/data/reusables/github-actions/permissions-statement-secrets-api.md
rename to translations/pt-BR/data/reusables/actions/permissions-statement-secrets-api.md
diff --git a/translations/pt-BR/data/reusables/github-actions/permissions-statement-secrets-environment.md b/translations/pt-BR/data/reusables/actions/permissions-statement-secrets-environment.md
similarity index 100%
rename from translations/pt-BR/data/reusables/github-actions/permissions-statement-secrets-environment.md
rename to translations/pt-BR/data/reusables/actions/permissions-statement-secrets-environment.md
diff --git a/translations/pt-BR/data/reusables/github-actions/permissions-statement-secrets-organization.md b/translations/pt-BR/data/reusables/actions/permissions-statement-secrets-organization.md
similarity index 100%
rename from translations/pt-BR/data/reusables/github-actions/permissions-statement-secrets-organization.md
rename to translations/pt-BR/data/reusables/actions/permissions-statement-secrets-organization.md
diff --git a/translations/pt-BR/data/reusables/github-actions/permissions-statement-secrets-repository.md b/translations/pt-BR/data/reusables/actions/permissions-statement-secrets-repository.md
similarity index 100%
rename from translations/pt-BR/data/reusables/github-actions/permissions-statement-secrets-repository.md
rename to translations/pt-BR/data/reusables/actions/permissions-statement-secrets-repository.md
diff --git a/translations/pt-BR/data/reusables/github-actions/postgres-environment-variables.md b/translations/pt-BR/data/reusables/actions/postgres-environment-variables.md
similarity index 100%
rename from translations/pt-BR/data/reusables/github-actions/postgres-environment-variables.md
rename to translations/pt-BR/data/reusables/actions/postgres-environment-variables.md
diff --git a/translations/pt-BR/data/reusables/github-actions/postgres-label-description.md b/translations/pt-BR/data/reusables/actions/postgres-label-description.md
similarity index 100%
rename from translations/pt-BR/data/reusables/github-actions/postgres-label-description.md
rename to translations/pt-BR/data/reusables/actions/postgres-label-description.md
diff --git a/translations/pt-BR/data/reusables/github-actions/private-repository-forks-configure.md b/translations/pt-BR/data/reusables/actions/private-repository-forks-configure.md
similarity index 100%
rename from translations/pt-BR/data/reusables/github-actions/private-repository-forks-configure.md
rename to translations/pt-BR/data/reusables/actions/private-repository-forks-configure.md
diff --git a/translations/pt-BR/data/reusables/github-actions/private-repository-forks-options.md b/translations/pt-BR/data/reusables/actions/private-repository-forks-options.md
similarity index 100%
rename from translations/pt-BR/data/reusables/github-actions/private-repository-forks-options.md
rename to translations/pt-BR/data/reusables/actions/private-repository-forks-options.md
diff --git a/translations/pt-BR/data/reusables/github-actions/private-repository-forks-overview.md b/translations/pt-BR/data/reusables/actions/private-repository-forks-overview.md
similarity index 100%
rename from translations/pt-BR/data/reusables/github-actions/private-repository-forks-overview.md
rename to translations/pt-BR/data/reusables/actions/private-repository-forks-overview.md
diff --git a/translations/pt-BR/data/reusables/github-actions/publish-to-maven-workflow-step.md b/translations/pt-BR/data/reusables/actions/publish-to-maven-workflow-step.md
similarity index 100%
rename from translations/pt-BR/data/reusables/github-actions/publish-to-maven-workflow-step.md
rename to translations/pt-BR/data/reusables/actions/publish-to-maven-workflow-step.md
diff --git a/translations/pt-BR/data/reusables/github-actions/publish-to-packages-workflow-step.md b/translations/pt-BR/data/reusables/actions/publish-to-packages-workflow-step.md
similarity index 100%
rename from translations/pt-BR/data/reusables/github-actions/publish-to-packages-workflow-step.md
rename to translations/pt-BR/data/reusables/actions/publish-to-packages-workflow-step.md
diff --git a/translations/pt-BR/data/reusables/github-actions/publishing-java-packages-intro.md b/translations/pt-BR/data/reusables/actions/publishing-java-packages-intro.md
similarity index 100%
rename from translations/pt-BR/data/reusables/github-actions/publishing-java-packages-intro.md
rename to translations/pt-BR/data/reusables/actions/publishing-java-packages-intro.md
diff --git a/translations/pt-BR/data/reusables/github-actions/pure-javascript.md b/translations/pt-BR/data/reusables/actions/pure-javascript.md
similarity index 100%
rename from translations/pt-BR/data/reusables/github-actions/pure-javascript.md
rename to translations/pt-BR/data/reusables/actions/pure-javascript.md
diff --git a/translations/pt-BR/data/reusables/github-actions/redis-environment-variables.md b/translations/pt-BR/data/reusables/actions/redis-environment-variables.md
similarity index 100%
rename from translations/pt-BR/data/reusables/github-actions/redis-environment-variables.md
rename to translations/pt-BR/data/reusables/actions/redis-environment-variables.md
diff --git a/translations/pt-BR/data/reusables/github-actions/redis-label-description.md b/translations/pt-BR/data/reusables/actions/redis-label-description.md
similarity index 100%
rename from translations/pt-BR/data/reusables/github-actions/redis-label-description.md
rename to translations/pt-BR/data/reusables/actions/redis-label-description.md
diff --git a/translations/pt-BR/data/reusables/github-actions/release-trigger-workflow.md b/translations/pt-BR/data/reusables/actions/release-trigger-workflow.md
similarity index 100%
rename from translations/pt-BR/data/reusables/github-actions/release-trigger-workflow.md
rename to translations/pt-BR/data/reusables/actions/release-trigger-workflow.md
diff --git a/translations/pt-BR/data/reusables/github-actions/run_id_description.md b/translations/pt-BR/data/reusables/actions/run_id_description.md
similarity index 100%
rename from translations/pt-BR/data/reusables/github-actions/run_id_description.md
rename to translations/pt-BR/data/reusables/actions/run_id_description.md
diff --git a/translations/pt-BR/data/reusables/github-actions/run_number_description.md b/translations/pt-BR/data/reusables/actions/run_number_description.md
similarity index 100%
rename from translations/pt-BR/data/reusables/github-actions/run_number_description.md
rename to translations/pt-BR/data/reusables/actions/run_number_description.md
diff --git a/translations/pt-BR/data/reusables/github-actions/runner-app-open-source.md b/translations/pt-BR/data/reusables/actions/runner-app-open-source.md
similarity index 100%
rename from translations/pt-BR/data/reusables/github-actions/runner-app-open-source.md
rename to translations/pt-BR/data/reusables/actions/runner-app-open-source.md
diff --git a/translations/pt-BR/data/reusables/github-actions/runner-group-assign-policy-org.md b/translations/pt-BR/data/reusables/actions/runner-group-assign-policy-org.md
similarity index 100%
rename from translations/pt-BR/data/reusables/github-actions/runner-group-assign-policy-org.md
rename to translations/pt-BR/data/reusables/actions/runner-group-assign-policy-org.md
diff --git a/translations/pt-BR/data/reusables/github-actions/runner-group-assign-policy-repo.md b/translations/pt-BR/data/reusables/actions/runner-group-assign-policy-repo.md
similarity index 100%
rename from translations/pt-BR/data/reusables/github-actions/runner-group-assign-policy-repo.md
rename to translations/pt-BR/data/reusables/actions/runner-group-assign-policy-repo.md
diff --git a/translations/pt-BR/data/reusables/github-actions/runner-label-settings.md b/translations/pt-BR/data/reusables/actions/runner-label-settings.md
similarity index 100%
rename from translations/pt-BR/data/reusables/github-actions/runner-label-settings.md
rename to translations/pt-BR/data/reusables/actions/runner-label-settings.md
diff --git a/translations/pt-BR/data/reusables/github-actions/runner-workflow-continuity.md b/translations/pt-BR/data/reusables/actions/runner-workflow-continuity.md
similarity index 100%
rename from translations/pt-BR/data/reusables/github-actions/runner-workflow-continuity.md
rename to translations/pt-BR/data/reusables/actions/runner-workflow-continuity.md
diff --git a/translations/pt-BR/data/reusables/github-actions/secrets-org-level-overview.md b/translations/pt-BR/data/reusables/actions/secrets-org-level-overview.md
similarity index 100%
rename from translations/pt-BR/data/reusables/github-actions/secrets-org-level-overview.md
rename to translations/pt-BR/data/reusables/actions/secrets-org-level-overview.md
diff --git a/translations/pt-BR/data/reusables/github-actions/secrets-redaction-warning.md b/translations/pt-BR/data/reusables/actions/secrets-redaction-warning.md
similarity index 100%
rename from translations/pt-BR/data/reusables/github-actions/secrets-redaction-warning.md
rename to translations/pt-BR/data/reusables/actions/secrets-redaction-warning.md
diff --git a/translations/pt-BR/data/reusables/github-actions/self-hosted-runner-auto-removal.md b/translations/pt-BR/data/reusables/actions/self-hosted-runner-auto-removal.md
similarity index 100%
rename from translations/pt-BR/data/reusables/github-actions/self-hosted-runner-auto-removal.md
rename to translations/pt-BR/data/reusables/actions/self-hosted-runner-auto-removal.md
diff --git a/translations/pt-BR/data/reusables/github-actions/self-hosted-runner-check-installation-success.md b/translations/pt-BR/data/reusables/actions/self-hosted-runner-check-installation-success.md
similarity index 91%
rename from translations/pt-BR/data/reusables/github-actions/self-hosted-runner-check-installation-success.md
rename to translations/pt-BR/data/reusables/actions/self-hosted-runner-check-installation-success.md
index eec874bebaec..229fdc18986c 100644
--- a/translations/pt-BR/data/reusables/github-actions/self-hosted-runner-check-installation-success.md
+++ b/translations/pt-BR/data/reusables/actions/self-hosted-runner-check-installation-success.md
@@ -5,6 +5,6 @@ After completing the steps to add a self-hosted runner, the runner and its statu
A aplicação dos executores auto-hospedados deve estar activa para que o executor aceite os trabalhos. Quando o aplicativo do executor estiver conectado a {% data variables.product.product_name %} e pronto para receber trabalhos, você verá a seguinte mensagem no terminal da máquina.
-{% data reusables.github-actions.self-hosted-runner-connected-output %}
+{% data reusables.actions.self-hosted-runner-connected-output %}
Para obter mais informações, consulte "[Monitoring and troubleshooting self-hosted runners](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners)."
diff --git a/translations/pt-BR/data/reusables/github-actions/self-hosted-runner-check-mac-linux.md b/translations/pt-BR/data/reusables/actions/self-hosted-runner-check-mac-linux.md
similarity index 100%
rename from translations/pt-BR/data/reusables/github-actions/self-hosted-runner-check-mac-linux.md
rename to translations/pt-BR/data/reusables/actions/self-hosted-runner-check-mac-linux.md
diff --git a/translations/pt-BR/data/reusables/github-actions/self-hosted-runner-configure-runner-group-access.md b/translations/pt-BR/data/reusables/actions/self-hosted-runner-configure-runner-group-access.md
similarity index 90%
rename from translations/pt-BR/data/reusables/github-actions/self-hosted-runner-configure-runner-group-access.md
rename to translations/pt-BR/data/reusables/actions/self-hosted-runner-configure-runner-group-access.md
index 98fddc1f958b..20825c184251 100644
--- a/translations/pt-BR/data/reusables/github-actions/self-hosted-runner-configure-runner-group-access.md
+++ b/translations/pt-BR/data/reusables/actions/self-hosted-runner-configure-runner-group-access.md
@@ -6,7 +6,7 @@
**Aviso**
- {% indented_data_reference reusables.github-actions.self-hosted-runner-security spaces=3 %}
+ {% indented_data_reference reusables.actions.self-hosted-runner-security spaces=3 %}
Para obter mais informações, consulte "[Sobre os executores auto-hospedados](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)."
diff --git a/translations/pt-BR/data/reusables/github-actions/self-hosted-runner-configure.md b/translations/pt-BR/data/reusables/actions/self-hosted-runner-configure.md
similarity index 100%
rename from translations/pt-BR/data/reusables/github-actions/self-hosted-runner-configure.md
rename to translations/pt-BR/data/reusables/actions/self-hosted-runner-configure.md
diff --git a/translations/pt-BR/data/reusables/github-actions/self-hosted-runner-connected-output.md b/translations/pt-BR/data/reusables/actions/self-hosted-runner-connected-output.md
similarity index 100%
rename from translations/pt-BR/data/reusables/github-actions/self-hosted-runner-connected-output.md
rename to translations/pt-BR/data/reusables/actions/self-hosted-runner-connected-output.md
diff --git a/translations/pt-BR/data/reusables/github-actions/self-hosted-runner-create-group.md b/translations/pt-BR/data/reusables/actions/self-hosted-runner-create-group.md
similarity index 100%
rename from translations/pt-BR/data/reusables/github-actions/self-hosted-runner-create-group.md
rename to translations/pt-BR/data/reusables/actions/self-hosted-runner-create-group.md
diff --git a/translations/pt-BR/data/reusables/github-actions/self-hosted-runner-description.md b/translations/pt-BR/data/reusables/actions/self-hosted-runner-description.md
similarity index 100%
rename from translations/pt-BR/data/reusables/github-actions/self-hosted-runner-description.md
rename to translations/pt-BR/data/reusables/actions/self-hosted-runner-description.md
diff --git a/translations/pt-BR/data/reusables/github-actions/self-hosted-runner-groups-navigate-to-repo-org-enterprise.md b/translations/pt-BR/data/reusables/actions/self-hosted-runner-groups-navigate-to-repo-org-enterprise.md
similarity index 100%
rename from translations/pt-BR/data/reusables/github-actions/self-hosted-runner-groups-navigate-to-repo-org-enterprise.md
rename to translations/pt-BR/data/reusables/actions/self-hosted-runner-groups-navigate-to-repo-org-enterprise.md
diff --git a/translations/pt-BR/data/reusables/github-actions/self-hosted-runner-labels-runs-on.md b/translations/pt-BR/data/reusables/actions/self-hosted-runner-labels-runs-on.md
similarity index 100%
rename from translations/pt-BR/data/reusables/github-actions/self-hosted-runner-labels-runs-on.md
rename to translations/pt-BR/data/reusables/actions/self-hosted-runner-labels-runs-on.md
diff --git a/translations/pt-BR/data/reusables/github-actions/self-hosted-runner-labels-view-assigned-labels.md b/translations/pt-BR/data/reusables/actions/self-hosted-runner-labels-view-assigned-labels.md
similarity index 100%
rename from translations/pt-BR/data/reusables/github-actions/self-hosted-runner-labels-view-assigned-labels.md
rename to translations/pt-BR/data/reusables/actions/self-hosted-runner-labels-view-assigned-labels.md
diff --git a/translations/pt-BR/data/reusables/github-actions/self-hosted-runner-list-group.md b/translations/pt-BR/data/reusables/actions/self-hosted-runner-list-group.md
similarity index 100%
rename from translations/pt-BR/data/reusables/github-actions/self-hosted-runner-list-group.md
rename to translations/pt-BR/data/reusables/actions/self-hosted-runner-list-group.md
diff --git a/translations/pt-BR/data/reusables/github-actions/self-hosted-runner-list.md b/translations/pt-BR/data/reusables/actions/self-hosted-runner-list.md
similarity index 100%
rename from translations/pt-BR/data/reusables/github-actions/self-hosted-runner-list.md
rename to translations/pt-BR/data/reusables/actions/self-hosted-runner-list.md
diff --git a/translations/pt-BR/data/reusables/actions/self-hosted-runner-management-permissions-required.md b/translations/pt-BR/data/reusables/actions/self-hosted-runner-management-permissions-required.md
new file mode 100644
index 000000000000..01c5b13250e9
--- /dev/null
+++ b/translations/pt-BR/data/reusables/actions/self-hosted-runner-management-permissions-required.md
@@ -0,0 +1,9 @@
+Um executor auto-hospedado pode ser localizado no seu repositório, organização, ou {% ifversion fpt or ghec %}configurações da conta corporativa em {% data variables.product.prodname_dotcom %}{% elsif ghes or ghae %} configurações corporativas em {% data variables.product.product_location %}{% endif %}. Para gerenciar um executor auto-hospedado, você deve ter as seguintes permissões, dependendo de onde o executor auto-hospedado foi adicionado:
+- **Repositório de Usuário**: Você deve ser o proprietário do repositório.
+- **Organização**: Você deve ser um proprietário da organização.
+- **Repositório da organização**: Você deve ser o proprietário da organização ou ter acesso de administrador ao repositório.
+{% ifversion ghec %}
+- **Conta corporativa**: Você deve ser proprietário de uma empresa.
+{% elsif ghes or ghae %}
+- **Empresa**: Você deve ser um administrador do site de {% data variables.product.prodname_enterprise %}
+{% endif %}
diff --git a/translations/pt-BR/data/reusables/github-actions/self-hosted-runner-navigate-repo-and-org.md b/translations/pt-BR/data/reusables/actions/self-hosted-runner-navigate-repo-and-org.md
similarity index 100%
rename from translations/pt-BR/data/reusables/github-actions/self-hosted-runner-navigate-repo-and-org.md
rename to translations/pt-BR/data/reusables/actions/self-hosted-runner-navigate-repo-and-org.md
diff --git a/translations/pt-BR/data/reusables/github-actions/self-hosted-runner-navigate-to-org-enterprise.md b/translations/pt-BR/data/reusables/actions/self-hosted-runner-navigate-to-org-enterprise.md
similarity index 100%
rename from translations/pt-BR/data/reusables/github-actions/self-hosted-runner-navigate-to-org-enterprise.md
rename to translations/pt-BR/data/reusables/actions/self-hosted-runner-navigate-to-org-enterprise.md
diff --git a/translations/pt-BR/data/reusables/github-actions/self-hosted-runner-navigate-to-repo-org-enterprise.md b/translations/pt-BR/data/reusables/actions/self-hosted-runner-navigate-to-repo-org-enterprise.md
similarity index 64%
rename from translations/pt-BR/data/reusables/github-actions/self-hosted-runner-navigate-to-repo-org-enterprise.md
rename to translations/pt-BR/data/reusables/actions/self-hosted-runner-navigate-to-repo-org-enterprise.md
index afa35a6828c6..144db20a7188 100644
--- a/translations/pt-BR/data/reusables/github-actions/self-hosted-runner-navigate-to-repo-org-enterprise.md
+++ b/translations/pt-BR/data/reusables/actions/self-hosted-runner-navigate-to-repo-org-enterprise.md
@@ -1,17 +1,17 @@
{% ifversion fpt %}
1. Navigate to the main page of the organization or repository where your self-hosted runner group is registered.
2. Click {% octicon "gear" aria-label="The Settings gear" %} **Settings**.
-3. In the left sidebar, click **Actions**.
+3. Na barra lateral esquerda, clique em **Actions** (Ações).
4. Click **Runners**.
{% elsif ghec or ghes or ghae %}
-1. Navigate to where your self-hosted runner is registered:
- * **In an organization or repository**: navigate to the main page and click {% octicon "gear" aria-label="The Settings gear" %} **Settings**. {% ifversion ghec %}
+1. Navegue por onde seu runner auto-hospedado está registrado:
+ * **Em uma organização ou repositório**: navegue até a página principal e clique em {% octicon "gear" aria-label="The Settings gear" %} **Configurações**. {% ifversion ghec %}
* **If using an enterprise account**: navigate to your enterprise account by clicking your profile photo in the top-right corner of {% data variables.product.prodname_dotcom_the_website %}, then clicking **Your enterprises**, then clicking the enterprise.{% elsif ghes or ghae %}
- * **If using an enterprise-level runner**:
- 1. In the upper-right corner of any page, click {% octicon "rocket" aria-label="The rocket ship" %}.
- 2. In the left sidebar, click **Enterprise overview**.
+ * **Se estiver usando um executor de nível corporativo**:
+ 1. No canto superior direito de qualquer página, clique em {% octicon "rocket" aria-label="The rocket ship" %}.
+ 2. Na barra lateral esquerda, clique em **Visão geral da empresa**.
3. In the enterprise sidebar, click {% octicon "law" aria-label="The law icon" %} **Policies**.{% endif %}
-2. Navigate to the {% data variables.product.prodname_actions %} settings:
+2. Navegue até as configurações {% data variables.product.prodname_actions %}:
* **In an organization or repository**: Click **Actions** in the left sidebar{% ifversion fpt or ghes > 3.1 or ghae or ghec %}, then click **Runners**{% endif %}.{% ifversion ghec or ghae or ghes %}
* {% ifversion ghec %}**If using an enterprise account**:{% elsif ghes or ghae %}**If using an enterprise-level runner**:{% endif %} Click **Actions** under "{% octicon "law" aria-label="The law icon" %} Policies"{% ifversion ghes > 3.1 or ghae or ghec %}, then click the **Runners** tab{% endif %}.{% endif %}
{% endif %}
diff --git a/translations/pt-BR/data/reusables/github-actions/self-hosted-runner-public-repo-access.md b/translations/pt-BR/data/reusables/actions/self-hosted-runner-public-repo-access.md
similarity index 100%
rename from translations/pt-BR/data/reusables/github-actions/self-hosted-runner-public-repo-access.md
rename to translations/pt-BR/data/reusables/actions/self-hosted-runner-public-repo-access.md
diff --git a/translations/pt-BR/data/reusables/github-actions/self-hosted-runner-removal-impact.md b/translations/pt-BR/data/reusables/actions/self-hosted-runner-removal-impact.md
similarity index 100%
rename from translations/pt-BR/data/reusables/github-actions/self-hosted-runner-removal-impact.md
rename to translations/pt-BR/data/reusables/actions/self-hosted-runner-removal-impact.md
diff --git a/translations/pt-BR/data/reusables/github-actions/self-hosted-runner-removing-a-runner-updated.md b/translations/pt-BR/data/reusables/actions/self-hosted-runner-removing-a-runner-updated.md
similarity index 100%
rename from translations/pt-BR/data/reusables/github-actions/self-hosted-runner-removing-a-runner-updated.md
rename to translations/pt-BR/data/reusables/actions/self-hosted-runner-removing-a-runner-updated.md
diff --git a/translations/pt-BR/data/reusables/github-actions/self-hosted-runner-removing-a-runner.md b/translations/pt-BR/data/reusables/actions/self-hosted-runner-removing-a-runner.md
similarity index 100%
rename from translations/pt-BR/data/reusables/github-actions/self-hosted-runner-removing-a-runner.md
rename to translations/pt-BR/data/reusables/actions/self-hosted-runner-removing-a-runner.md
diff --git a/translations/pt-BR/data/reusables/github-actions/self-hosted-runner-reqs-docker.md b/translations/pt-BR/data/reusables/actions/self-hosted-runner-reqs-docker.md
similarity index 100%
rename from translations/pt-BR/data/reusables/github-actions/self-hosted-runner-reqs-docker.md
rename to translations/pt-BR/data/reusables/actions/self-hosted-runner-reqs-docker.md
diff --git a/translations/pt-BR/data/reusables/github-actions/self-hosted-runner-reusing.md b/translations/pt-BR/data/reusables/actions/self-hosted-runner-reusing.md
similarity index 100%
rename from translations/pt-BR/data/reusables/github-actions/self-hosted-runner-reusing.md
rename to translations/pt-BR/data/reusables/actions/self-hosted-runner-reusing.md
diff --git a/translations/pt-BR/data/reusables/github-actions/self-hosted-runner-security.md b/translations/pt-BR/data/reusables/actions/self-hosted-runner-security.md
similarity index 100%
rename from translations/pt-BR/data/reusables/github-actions/self-hosted-runner-security.md
rename to translations/pt-BR/data/reusables/actions/self-hosted-runner-security.md
diff --git a/translations/pt-BR/data/reusables/github-actions/service-container-add-script.md b/translations/pt-BR/data/reusables/actions/service-container-add-script.md
similarity index 100%
rename from translations/pt-BR/data/reusables/github-actions/service-container-add-script.md
rename to translations/pt-BR/data/reusables/actions/service-container-add-script.md
diff --git a/translations/pt-BR/data/reusables/github-actions/service-container-host-runner.md b/translations/pt-BR/data/reusables/actions/service-container-host-runner.md
similarity index 100%
rename from translations/pt-BR/data/reusables/github-actions/service-container-host-runner.md
rename to translations/pt-BR/data/reusables/actions/service-container-host-runner.md
diff --git a/translations/pt-BR/data/reusables/github-actions/service-container-host.md b/translations/pt-BR/data/reusables/actions/service-container-host.md
similarity index 100%
rename from translations/pt-BR/data/reusables/github-actions/service-container-host.md
rename to translations/pt-BR/data/reusables/actions/service-container-host.md
diff --git a/translations/pt-BR/data/reusables/github-actions/service-container-localhost.md b/translations/pt-BR/data/reusables/actions/service-container-localhost.md
similarity index 100%
rename from translations/pt-BR/data/reusables/github-actions/service-container-localhost.md
rename to translations/pt-BR/data/reusables/actions/service-container-localhost.md
diff --git a/translations/pt-BR/data/reusables/github-actions/service-container-prereqs.md b/translations/pt-BR/data/reusables/actions/service-container-prereqs.md
similarity index 100%
rename from translations/pt-BR/data/reusables/github-actions/service-container-prereqs.md
rename to translations/pt-BR/data/reusables/actions/service-container-prereqs.md
diff --git a/translations/pt-BR/data/reusables/github-actions/service-template-steps.md b/translations/pt-BR/data/reusables/actions/service-template-steps.md
similarity index 100%
rename from translations/pt-BR/data/reusables/github-actions/service-template-steps.md
rename to translations/pt-BR/data/reusables/actions/service-template-steps.md
diff --git a/translations/pt-BR/data/reusables/github-actions/settings-sidebar-actions-runner-groups-selection.md b/translations/pt-BR/data/reusables/actions/settings-sidebar-actions-runner-groups-selection.md
similarity index 100%
rename from translations/pt-BR/data/reusables/github-actions/settings-sidebar-actions-runner-groups-selection.md
rename to translations/pt-BR/data/reusables/actions/settings-sidebar-actions-runner-groups-selection.md
diff --git a/translations/pt-BR/data/reusables/github-actions/settings-sidebar-actions-runner-groups.md b/translations/pt-BR/data/reusables/actions/settings-sidebar-actions-runner-groups.md
similarity index 100%
rename from translations/pt-BR/data/reusables/github-actions/settings-sidebar-actions-runner-groups.md
rename to translations/pt-BR/data/reusables/actions/settings-sidebar-actions-runner-groups.md
diff --git a/translations/pt-BR/data/reusables/github-actions/settings-sidebar-actions-runner-selection.md b/translations/pt-BR/data/reusables/actions/settings-sidebar-actions-runner-selection.md
similarity index 100%
rename from translations/pt-BR/data/reusables/github-actions/settings-sidebar-actions-runner-selection.md
rename to translations/pt-BR/data/reusables/actions/settings-sidebar-actions-runner-selection.md
diff --git a/translations/pt-BR/data/reusables/github-actions/settings-sidebar-actions-runners-updated.md b/translations/pt-BR/data/reusables/actions/settings-sidebar-actions-runners-updated.md
similarity index 100%
rename from translations/pt-BR/data/reusables/github-actions/settings-sidebar-actions-runners-updated.md
rename to translations/pt-BR/data/reusables/actions/settings-sidebar-actions-runners-updated.md
diff --git a/translations/pt-BR/data/reusables/github-actions/settings-sidebar-actions-runners.md b/translations/pt-BR/data/reusables/actions/settings-sidebar-actions-runners.md
similarity index 100%
rename from translations/pt-BR/data/reusables/github-actions/settings-sidebar-actions-runners.md
rename to translations/pt-BR/data/reusables/actions/settings-sidebar-actions-runners.md
diff --git a/translations/pt-BR/data/reusables/github-actions/settings-sidebar-actions.md b/translations/pt-BR/data/reusables/actions/settings-sidebar-actions.md
similarity index 100%
rename from translations/pt-BR/data/reusables/github-actions/settings-sidebar-actions.md
rename to translations/pt-BR/data/reusables/actions/settings-sidebar-actions.md
diff --git a/translations/pt-BR/data/reusables/github-actions/setup-node-intro.md b/translations/pt-BR/data/reusables/actions/setup-node-intro.md
similarity index 100%
rename from translations/pt-BR/data/reusables/github-actions/setup-node-intro.md
rename to translations/pt-BR/data/reusables/actions/setup-node-intro.md
diff --git a/translations/pt-BR/data/reusables/github-actions/sidebar-environment.md b/translations/pt-BR/data/reusables/actions/sidebar-environment.md
similarity index 100%
rename from translations/pt-BR/data/reusables/github-actions/sidebar-environment.md
rename to translations/pt-BR/data/reusables/actions/sidebar-environment.md
diff --git a/translations/pt-BR/data/reusables/github-actions/sidebar-secret.md b/translations/pt-BR/data/reusables/actions/sidebar-secret.md
similarity index 100%
rename from translations/pt-BR/data/reusables/github-actions/sidebar-secret.md
rename to translations/pt-BR/data/reusables/actions/sidebar-secret.md
diff --git a/translations/pt-BR/data/reusables/github-actions/supported-github-runners.md b/translations/pt-BR/data/reusables/actions/supported-github-runners.md
similarity index 94%
rename from translations/pt-BR/data/reusables/github-actions/supported-github-runners.md
rename to translations/pt-BR/data/reusables/actions/supported-github-runners.md
index a5c50a96c536..08643187db60 100644
--- a/translations/pt-BR/data/reusables/github-actions/supported-github-runners.md
+++ b/translations/pt-BR/data/reusables/actions/supported-github-runners.md
@@ -12,10 +12,10 @@
Windows Server 2022
-windows-2022
+windows-latest ou windows-2022
-The windows-latest label currently uses the Windows Server 2019 runner image.
+The windows-latest label currently uses the Windows Server 2022 runner image.
@@ -23,7 +23,7 @@ The windows-latest label currently uses the Windows Server 2019 run
Windows Server 2019
-windows-latest ou windows-2019
+windows-2019
diff --git a/translations/pt-BR/data/reusables/github-actions/usage-api-requests.md b/translations/pt-BR/data/reusables/actions/usage-api-requests.md
similarity index 100%
rename from translations/pt-BR/data/reusables/github-actions/usage-api-requests.md
rename to translations/pt-BR/data/reusables/actions/usage-api-requests.md
diff --git a/translations/pt-BR/data/reusables/github-actions/usage-matrix-limits.md b/translations/pt-BR/data/reusables/actions/usage-matrix-limits.md
similarity index 100%
rename from translations/pt-BR/data/reusables/github-actions/usage-matrix-limits.md
rename to translations/pt-BR/data/reusables/actions/usage-matrix-limits.md
diff --git a/translations/pt-BR/data/reusables/github-actions/usage-workflow-queue-limits.md b/translations/pt-BR/data/reusables/actions/usage-workflow-queue-limits.md
similarity index 100%
rename from translations/pt-BR/data/reusables/github-actions/usage-workflow-queue-limits.md
rename to translations/pt-BR/data/reusables/actions/usage-workflow-queue-limits.md
diff --git a/translations/pt-BR/data/reusables/github-actions/usage-workflow-run-time.md b/translations/pt-BR/data/reusables/actions/usage-workflow-run-time.md
similarity index 100%
rename from translations/pt-BR/data/reusables/github-actions/usage-workflow-run-time.md
rename to translations/pt-BR/data/reusables/actions/usage-workflow-run-time.md
diff --git a/translations/pt-BR/data/reusables/github-actions/using-context-or-environment-variables.md b/translations/pt-BR/data/reusables/actions/using-context-or-environment-variables.md
similarity index 100%
rename from translations/pt-BR/data/reusables/github-actions/using-context-or-environment-variables.md
rename to translations/pt-BR/data/reusables/actions/using-context-or-environment-variables.md
diff --git a/translations/pt-BR/data/reusables/github-actions/workflow-dispatch-inputs.md b/translations/pt-BR/data/reusables/actions/workflow-dispatch-inputs.md
similarity index 100%
rename from translations/pt-BR/data/reusables/github-actions/workflow-dispatch-inputs.md
rename to translations/pt-BR/data/reusables/actions/workflow-dispatch-inputs.md
diff --git a/translations/pt-BR/data/reusables/github-actions/workflow-permissions-intro.md b/translations/pt-BR/data/reusables/actions/workflow-permissions-intro.md
similarity index 100%
rename from translations/pt-BR/data/reusables/github-actions/workflow-permissions-intro.md
rename to translations/pt-BR/data/reusables/actions/workflow-permissions-intro.md
diff --git a/translations/pt-BR/data/reusables/github-actions/workflow-permissions-modifying.md b/translations/pt-BR/data/reusables/actions/workflow-permissions-modifying.md
similarity index 100%
rename from translations/pt-BR/data/reusables/github-actions/workflow-permissions-modifying.md
rename to translations/pt-BR/data/reusables/actions/workflow-permissions-modifying.md
diff --git a/translations/pt-BR/data/reusables/github-actions/workflows-from-public-fork-setting.md b/translations/pt-BR/data/reusables/actions/workflows-from-public-fork-setting.md
similarity index 100%
rename from translations/pt-BR/data/reusables/github-actions/workflows-from-public-fork-setting.md
rename to translations/pt-BR/data/reusables/actions/workflows-from-public-fork-setting.md
diff --git a/translations/pt-BR/data/reusables/actions/workflows/section-triggering-a-workflow.md b/translations/pt-BR/data/reusables/actions/workflows/section-triggering-a-workflow.md
index b3e15bd3f724..759c436067cf 100644
--- a/translations/pt-BR/data/reusables/actions/workflows/section-triggering-a-workflow.md
+++ b/translations/pt-BR/data/reusables/actions/workflows/section-triggering-a-workflow.md
@@ -3,4 +3,4 @@ Para acionar automaticamente um fluxo de trabalho, use `on` para definir quais e
Você pode definir um ou vários eventos que possam acionar um fluxo de trabalho ou definir um cronograma. Também é possível restringir a execução de um fluxo de trabalho para que ocorra apenas para altearções específicas para arquivos, tags ou alterações no branch. Estas opções são descritas nas seguintes seções.
-{% data reusables.github-actions.actions-on-examples %}
+{% data reusables.actions.actions-on-examples %}
diff --git a/translations/pt-BR/data/reusables/github-actions/actions-on-examples.md b/translations/pt-BR/data/reusables/github-actions/actions-on-examples.md
deleted file mode 100644
index 26d4a25747f6..000000000000
--- a/translations/pt-BR/data/reusables/github-actions/actions-on-examples.md
+++ /dev/null
@@ -1,19 +0,0 @@
-### Using a single event
-
-{% data reusables.github-actions.on-single-example %}
-
-### Using multiple events
-
-{% data reusables.github-actions.on-multiple-example %}
-
-### Using activity types
-
-{% data reusables.github-actions.actions-activity-types %}
-
-### Using filters
-
-{% data reusables.github-actions.actions-filters %}
-
-### Using activity types and filters with multiple events
-
-{% data reusables.github-actions.actions-multiple-types %}
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/github-actions/ip-allow-list-self-hosted-runners.md b/translations/pt-BR/data/reusables/github-actions/ip-allow-list-self-hosted-runners.md
deleted file mode 100644
index b3dfa137e09f..000000000000
--- a/translations/pt-BR/data/reusables/github-actions/ip-allow-list-self-hosted-runners.md
+++ /dev/null
@@ -1,13 +0,0 @@
-{% ifversion ghae %}
-Para permitir que os seus executores auto-hospedados se comuniquem com
-{% data variables.product.prodname_dotcom %}, adicione o endereço IP ou o intervalo de endereços IP dos seus executores auto-hospedados à lista de permissões de IP. Para obter mais informações, consulte "[Adding an allowed IP address](#adding-an-allowed-ip-address)."
-{% else %}
-{% warning %}
-
-**Aviso**: Se você usar uma lista de permitir IP e também gostaria de usar {% data variables.product.prodname_actions %}, você deve usar executores auto-hospedados. Para obter mais informações, consulte "[Hosting your own runners](/actions/automating-your-workflow-with-github-actions/about-self-hosted-runners)."
-
-{% endwarning %}
-Para permitir que os seus executores auto-hospedados se comuniquem com
-
-{% data variables.product.prodname_dotcom %}, adicione o endereço IP ou o intervalo de endereços IP dos seus executores auto-hospedados à lista de permissões de IP. Para obter mais informações, consulte "[Adding an allowed IP address](#adding-an-allowed-ip-address)."
-{% endif %}
diff --git a/translations/pt-BR/data/reusables/github-actions/self-hosted-runner-management-permissions-required.md b/translations/pt-BR/data/reusables/github-actions/self-hosted-runner-management-permissions-required.md
deleted file mode 100644
index 847f487696a7..000000000000
--- a/translations/pt-BR/data/reusables/github-actions/self-hosted-runner-management-permissions-required.md
+++ /dev/null
@@ -1,9 +0,0 @@
-A self-hosted runner can be located in either your repository, organization, or {% ifversion fpt or ghec %}enterprise account settings on {% data variables.product.prodname_dotcom %}{% elsif ghes or ghae %} enterprise settings on {% data variables.product.product_location %}{% endif %}. To manage a self-hosted runner, you must have the following permissions, depending on where the self-hosted runner was added:
-- **User repository**: You must be the repository owner.
-- **Organization**: You must be an organization owner.
-- **Organization repository**: You must be an organization owner, or have admin access to the repository.
-{% ifversion ghec %}
-- **Enterprise account**: You must be an enterprise owner.
-{% elsif ghes or ghae %}
-- **Enterprise**: You must be a {% data variables.product.prodname_enterprise %} site administrator.
-{% endif %}
diff --git a/translations/pt-BR/data/reusables/repositories/navigate-to-commit-page.md b/translations/pt-BR/data/reusables/repositories/navigate-to-commit-page.md
new file mode 100644
index 000000000000..bec770c79066
--- /dev/null
+++ b/translations/pt-BR/data/reusables/repositories/navigate-to-commit-page.md
@@ -0,0 +1 @@
+1. On the main page of the repository, click the commits to navigate to the commits page. 
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/rest-reference/actions/actions.md b/translations/pt-BR/data/reusables/rest-reference/actions/actions.md
new file mode 100644
index 000000000000..1c3414f8743e
--- /dev/null
+++ b/translations/pt-BR/data/reusables/rest-reference/actions/actions.md
@@ -0,0 +1 @@
+A API de {% data variables.product.prodname_actions %} permite que você gerencie {% data variables.product.prodname_actions %} usando a API REST. {% data reusables.actions.actions-authentication %} {% data variables.product.prodname_github_apps %} exige permissões mencionadas em cada ponto de extremidade. Para obter mais informações, consulte "[Documentação do {% data variables.product.prodname_actions %}](/actions)".
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/rest-reference/actions/artifacts.md b/translations/pt-BR/data/reusables/rest-reference/actions/artifacts.md
new file mode 100644
index 000000000000..3d9c0170a6d6
--- /dev/null
+++ b/translations/pt-BR/data/reusables/rest-reference/actions/artifacts.md
@@ -0,0 +1,5 @@
+## Artefatos
+
+A API de Artefatos permite que você faça o download, exclua e recupere informações sobre artefatos de fluxo de trabalho. {% data reusables.actions.about-artifacts %} Para obter mais informações, consulte "[Dados recorrentes do fluxo de trabalho que usam artefatos](/actions/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)".
+
+{% data reusables.actions.actions-authentication %} {% data reusables.actions.actions-app-actions-permissions-api %}
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/rest-reference/actions/permissions.md b/translations/pt-BR/data/reusables/rest-reference/actions/permissions.md
new file mode 100644
index 000000000000..77f0c78a568d
--- /dev/null
+++ b/translations/pt-BR/data/reusables/rest-reference/actions/permissions.md
@@ -0,0 +1,3 @@
+## Permissões
+
+A API de Permissões permite que você defina permissões para quais empresas, organizações e repositórios podem executar {% data variables.product.prodname_actions %}, e quais ações podem ser executadas.{% ifversion fpt or ghec or ghes %} Para obter mais informações, consulte "[Limites de uso, cobrança e administração](/actions/reference/usage-limits-billing-and-administration#disabling-or-limiting-github-actions-for-your-repository-or-organization)".{% endif %}
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/rest-reference/actions/secrets.md b/translations/pt-BR/data/reusables/rest-reference/actions/secrets.md
new file mode 100644
index 000000000000..abb0e801ce03
--- /dev/null
+++ b/translations/pt-BR/data/reusables/rest-reference/actions/secrets.md
@@ -0,0 +1,5 @@
+## Segredos
+
+A API Segredos permite criar, atualizar, excluir e recuperar informações sobre segredos criptografados. {% data reusables.actions.about-secrets %} Para obter mais informações, consulte "[Criando e usando segredos encriptados](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)".
+
+{% data reusables.actions.actions-authentication %} {% data variables.product.prodname_github_apps %} deve ter a permissão `segredos` para usar esta API. Os usuários autenticados devem ter acesso de colaborador em um repositório para criar, atualizar ou ler segredos.
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/rest-reference/actions/self-hosted-runner-groups.md b/translations/pt-BR/data/reusables/rest-reference/actions/self-hosted-runner-groups.md
new file mode 100644
index 000000000000..553a014580de
--- /dev/null
+++ b/translations/pt-BR/data/reusables/rest-reference/actions/self-hosted-runner-groups.md
@@ -0,0 +1,7 @@
+## Grupos de runner auto-hospedados
+
+{% data reusables.actions.ae-self-hosted-runners-notice %}
+
+A API dos Grupos de Runners auto-hospedados permite que você gerencie grupos de runners auto-hospedados. Para obter mais informações, consulte "[Gerenciando acesso a runners auto-hospedados usando grupos](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups)".
+
+{% data reusables.actions.actions-authentication %} {% data variables.product.prodname_github_apps %} deve ter a permissão de administração `` para repositórios ou a permissão `organization_self_hosted_runners` para as organizações. Os usuários autenticados devem ter acesso de administrador a repositórios ou organizações ou ao escopo `manage_runners:corporativo` para que as empresas usem esta API.
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/rest-reference/actions/self-hosted-runners.md b/translations/pt-BR/data/reusables/rest-reference/actions/self-hosted-runners.md
new file mode 100644
index 000000000000..551db44dbf5e
--- /dev/null
+++ b/translations/pt-BR/data/reusables/rest-reference/actions/self-hosted-runners.md
@@ -0,0 +1,7 @@
+## Executores auto-hospedados
+
+{% data reusables.actions.ae-self-hosted-runners-notice %}
+
+A API de executores auto-hospedados permite que você registre, visualize e exclua executores auto-hospedados. {% data reusables.actions.about-self-hosted-runners %} Para obter mais informações, consulte "[Hospedando seus próprios executores](/actions/hosting-your-own-runners)".
+
+{% data reusables.actions.actions-authentication %} {% data variables.product.prodname_github_apps %} deve ter a permissão de administração `` para repositórios ou a permissão `organization_self_hosted_runners` para as organizações. Os usuários autenticados devem ter acesso de administrador a repositórios ou organizações ou ao escopo `manage_runners:corporativo` para que as empresas usem esta API.
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/rest-reference/actions/workflow-jobs.md b/translations/pt-BR/data/reusables/rest-reference/actions/workflow-jobs.md
new file mode 100644
index 000000000000..0b8b388eadda
--- /dev/null
+++ b/translations/pt-BR/data/reusables/rest-reference/actions/workflow-jobs.md
@@ -0,0 +1,5 @@
+## Trabalhos de fluxo de trabalho
+
+A API de Trabalhos de Fluxo de Trabalho permite que você visualize logs e trabalhos de fluxo de trabalho. {% data reusables.actions.about-workflow-jobs %} Para obter mais informações, consulte "[Sintaxe de fluxo de trabalho para GitHub Actions](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions)".
+
+{% data reusables.actions.actions-authentication %} {% data reusables.actions.actions-app-actions-permissions-api %}
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/rest-reference/actions/workflow-runs.md b/translations/pt-BR/data/reusables/rest-reference/actions/workflow-runs.md
new file mode 100644
index 000000000000..0f38e2b7a2d9
--- /dev/null
+++ b/translations/pt-BR/data/reusables/rest-reference/actions/workflow-runs.md
@@ -0,0 +1,5 @@
+## Workflow runs
+
+The Workflow Runs API allows you to view, re-run, cancel, and view logs for workflow runs. {% data reusables.actions.about-workflow-runs %} For more information, see "[Managing a workflow run](/actions/automating-your-workflow-with-github-actions/managing-a-workflow-run)."
+
+{% data reusables.actions.actions-authentication %} {% data reusables.actions.actions-app-actions-permissions-api %}
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/rest-reference/actions/workflows.md b/translations/pt-BR/data/reusables/rest-reference/actions/workflows.md
new file mode 100644
index 000000000000..59924726651e
--- /dev/null
+++ b/translations/pt-BR/data/reusables/rest-reference/actions/workflows.md
@@ -0,0 +1,5 @@
+## Fluxos de trabalho
+
+A API de fluxos de trabalho permite que você veja fluxos de trabalho para um repositório. {% data reusables.actions.about-workflows %} Para obter mais informações, consulte "[Automatizando seu fluxo de trabalho com o GitHub Actions](/actions/automating-your-workflow-with-github-actions)".
+
+{% data reusables.actions.actions-authentication %} {% data reusables.actions.actions-app-actions-permissions-api %}
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/rest-reference/activity/events.md b/translations/pt-BR/data/reusables/rest-reference/activity/events.md
new file mode 100644
index 000000000000..78f65cef3653
--- /dev/null
+++ b/translations/pt-BR/data/reusables/rest-reference/activity/events.md
@@ -0,0 +1,22 @@
+## Events
+
+The Events API is a read-only API to the {% data variables.product.prodname_dotcom %} events. These events power the various activity streams on the site.
+
+The Events API can return different types of events triggered by activity on {% data variables.product.product_name %}. For more information about the specific events that you can receive from the Events API, see "[{% data variables.product.prodname_dotcom %} Event types](/developers/webhooks-and-events/github-event-types)." An events API for repository issues is also available. For more information, see the "[Issue Events API](/rest/reference/issues#events)."
+
+Events are optimized for polling with the "ETag" header. If no new events have been triggered, you will see a "304 Not Modified" response, and your current rate limit will be untouched. There is also an "X-Poll-Interval" header that specifies how often (in seconds) you are allowed to poll. In times of high server load, the time may increase. Please obey the header.
+
+``` shell
+$ curl -I {% data variables.product.api_url_pre %}/users/tater/events
+> HTTP/2 200
+> X-Poll-Interval: 60
+> ETag: "a18c3bded88eb5dbb5c849a489412bf3"
+
+# The quotes around the ETag value are important
+$ curl -I {% data variables.product.api_url_pre %}/users/tater/events \
+$ -H 'If-None-Match: "a18c3bded88eb5dbb5c849a489412bf3"'
+> HTTP/2 304
+> X-Poll-Interval: 60
+```
+
+Only events created within the past 90 days will be included in timelines. Events older than 90 days will not be included (even if the total number of events in the timeline is less than 300).
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/rest-reference/activity/feeds.md b/translations/pt-BR/data/reusables/rest-reference/activity/feeds.md
new file mode 100644
index 000000000000..bf74ce8bb89f
--- /dev/null
+++ b/translations/pt-BR/data/reusables/rest-reference/activity/feeds.md
@@ -0,0 +1,52 @@
+## Feeds
+
+### Example of getting an Atom feed
+
+To get a feed in Atom format, you must specify the `application/atom+xml` type in the `Accept` header. For example, to get the Atom feed for GitHub security advisories:
+
+ curl -H "Accept: application/atom+xml" https://github.com/security-advisories
+
+#### Resposta
+
+```shell
+HTTP/2 200
+```
+
+```xml
+
+
+ tag:github.com,2008:/security-advisories
+
+ GitHub Security Advisory Feed
+
+ GitHub
+
+ 2019-01-14T19:34:52Z
+
+ tag:github.com,2008:GHSA-abcd-12ab-23cd
+ 2018-07-26T15:14:52Z
+ 2019-01-14T19:34:52Z
+ [GHSA-abcd-12ab-23cd] Moderate severity vulnerability that affects Octoapp
+
+
+ <p>Octoapp node module before 4.17.5 suffers from a Modification of Assumed-Immutable Data (MAID) vulnerability via defaultsDeep, merge, and mergeWith functions, which allows a malicious user to modify the prototype of "Object" via <strong>proto</strong>, causing the addition or modification of an existing property that will exist on all objects.</p>
+ <p><strong>Affected Packages</strong></p>
+
+ <dl>
+ <dt>Octoapp</dt>
+ <dd>Ecosystem: npm</dd>
+ <dd>Severity: moderate</dd>
+ <dd>Versions: < 4.17.5</dd>
+ <dd>Fixed in: 4.17.5</dd>
+ </dl>
+
+ <p><strong>References</strong></p>
+
+ <ul>
+ <li>https://nvd.nist.gov/vuln/detail/CVE-2018-123</li>
+ </ul>
+
+
+
+
+```
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/rest-reference/activity/notifications.md b/translations/pt-BR/data/reusables/rest-reference/activity/notifications.md
new file mode 100644
index 000000000000..df9bbea397f5
--- /dev/null
+++ b/translations/pt-BR/data/reusables/rest-reference/activity/notifications.md
@@ -0,0 +1,59 @@
+## Notificações
+
+Os usuários recebem notificações de conversas em repositórios que inspecionam, incluindo:
+
+* Problemas e seus comentários
+* Pull Requests e seus comentários
+* Comentários em quaisquer commits
+
+As notificações também são enviadas para conversas em repositórios não inspecionados quando o usuário está envolvido, incluindo:
+
+* **@mentions**
+* Tarefas de problemas
+* Commits que o usuário cria ou faz commit
+* Qualquer discussão de que o usuário participa ativamente
+
+Todas as chamadas de notificação da API requerem escopos da API para `notificações` ou `repositórios`. Fazer isto dará acesso somente-leitura a algum problema e fará commit do conteúdo. Você ainda precisará do escopo de `repositório` para acessar problemas e commits de seus respectivos pontos de extremidade.
+
+Notificações retornam como "correntes". Uma corrente contém informações sobre a discussão atual de um problema, pull request ou commit.
+
+As notificações são otimizadas para sondagem com o cabeçalho `Last-Modified`. Se não houver novas notificações, você verá uma resposta `304 Not Modified`, deixando a sua taxa de limite atual inalterada. Há um cabeçalho `X-Poll-Interval` que especifica com que frequência (em segundos) que você pode fazer a sondagem. Em tempos de alta carga do servidor, o tempo pode aumentar. Obedeça o cabeçalho.
+
+``` shell
+# Add authentication to your requests
+$ curl -I {% data variables.product.api_url_pre %}/notifications
+HTTP/2 200
+Last-Modified: Thu, 25 Oct 2012 15:16:27 GMT
+X-Poll-Interval: 60
+
+# Pass the Last-Modified header exactly
+$ curl -I {% data variables.product.api_url_pre %}/notifications
+$ -H "If-Modified-Since: Thu, 25 Oct 2012 15:16:27 GMT"
+> HTTP/2 304
+> X-Poll-Interval: 60
+```
+
+### Motivos de notificação
+
+Ao recuperar respostas da API de Notificações, cada carga tem uma carga denominada `drazão`. Estas correspondem a eventos que ativam uma notificação.
+
+Aqui está uma lista da potencial `razão` para receber uma notificação:
+
+| Nome da razão | Descrição |
+| ------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `assign` | O problema foi atribuído a você. |
+| `autor` | Você criou a corrente. |
+| `comentário` | Você comentou na corrente. |
+| `ci_activity` | A execução de um fluxo de trabalho {% data variables.product.prodname_actions %} que você acionou foi concluída. |
+| `convite` | Você aceitou um convite para contribuir com o repositório. |
+| `manual` | Você assinou a corrente (por meio de um problema ou pull request). |
+| `menção` | Você foi especificamente **@mentioned** no conteúdo. |
+| `review_requested` | Foi solicitado que você ou uma equipe da qual você é integrante revise um pull request.{% ifversion fpt or ghec %}
+| `security_alert` | O {% data variables.product.prodname_dotcom %} descobriu uma [vulnerabilidade de segurança](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies) no seu repositório.{% endif %}
+| `state_change` | Você alterou o estado da corrente (por exemplo, fechando um problema ou mesclando um pull request). |
+| `assinado` | Você está inspecionando o repositório. |
+| `team_mention` | Você estava em uma equipe que foi mencionada. |
+
+Observe que a `razão` é modificada em uma base de corrente e pode mudar se a `razão` em uma notificação posterior for diferente.
+
+Por exemplo, se você é o autor de um problema, as notificações subsequentes sobre essa problema terão uma `razão` do `autor`. Portanto, se você for **@mentioned** no mesmo problema, as notificações que você buscar subsequentemente terão uma `razão` a `mencionar`. A `razão` permanece como `menção`, independentemente se você já foi mencionado novamente.
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/rest-reference/activity/starring.md b/translations/pt-BR/data/reusables/rest-reference/activity/starring.md
new file mode 100644
index 000000000000..6f794b741bca
--- /dev/null
+++ b/translations/pt-BR/data/reusables/rest-reference/activity/starring.md
@@ -0,0 +1,15 @@
+## Marcar com uma estrela
+
+Marcar o repositório como uma estrela é uma funcionalidade que permite aos usuários favoritar os repositórios. As estrelas são exibidas ao lado dos repositórios para mostrar um nível de interesse aproximado. As estrelas não têm efeito nas notificações ou no feed da atividade.
+
+### Marcar como estrela vs. Inspecionar
+
+Em agosto de 2012, [mudamos a forma como a inspeção funciona](https://github.com/blog/1204-notifications-stars) em {% data variables.product.prodname_dotcom %}. Muitas aplicações de cliente da API podem estar usando os pontos de extremidade originais de "inspetor" para acessar estes dados. Agora você pode começar a usar os pontos de extremidade "estrela" (descritos abaixo). Para obter mais informações, consulte a [Post de alteração da API de Inspeção](https://developer.github.com/changes/2012-09-05-watcher-api/) e a [API de Inspeção do repositório](/rest/reference/activity#watching)".
+
+### Tipos de mídia personalizados para marcar como estrela
+
+Existe um tipo de mídia personalizado com suporte para a API REST estrelada. Ao usar este tipo de mídia personalizada, você receberá uma resposta com a propriedade do registro de tempo `starred_at`, que indica o tempo que a estrela foi criada. A resposta também tem uma segunda propriedade que inclui o recurso retornado quando o tipo de mídia personalizado não está incluído. A propriedade que contém o recurso será `usuário` ou `repositório`.
+
+ application/vnd.github.v3.star+json
+
+Para obter mais informações sobre os tipos de mídia, consulte "[Tipos de mídia personalizados](/rest/overview/media-types)".
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/rest-reference/activity/watching.md b/translations/pt-BR/data/reusables/rest-reference/activity/watching.md
new file mode 100644
index 000000000000..cfea52533f5f
--- /dev/null
+++ b/translations/pt-BR/data/reusables/rest-reference/activity/watching.md
@@ -0,0 +1,3 @@
+## Inspecionando
+
+Inspecionar um repositório registra o usuário para receber notificações de novas discussões, bem como eventos no feed de atividade do usuário. Para favoritar um repositório de forma simples, consulte "[Marcar repositórios com uma estrela](/rest/reference/activity#starring)".
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/rest-reference/apps/apps.md b/translations/pt-BR/data/reusables/rest-reference/apps/apps.md
new file mode 100644
index 000000000000..b94a66e1d7f6
--- /dev/null
+++ b/translations/pt-BR/data/reusables/rest-reference/apps/apps.md
@@ -0,0 +1,9 @@
+{% data reusables.apps.general-apps-restrictions %}
+
+Esta página lista os pontos de extremidade que você pode acessar enquanto autenticado como um aplicativo GitHub. Consulte "[Efetuar a autenticação como um aplicativo GitHub](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-a-github-app)" para saber mais.
+
+Quando autenticado como um aplicativo GitHub, a API dos aplicativos GitHub permite que você obtenha informações de alto nível sobre um aplicativo GitHub, bem como informações específicas sobre instalações de um aplicativo.
+
+Você pode acessar os pontos de extremidade da API v3 de REST enquanto autenticado como um aplicativo GitHub. Estes pontos de extremidade têm uma seção de "Observação" que contém um ponto que diz "Funciona com aplicativos GitHub". Você também pode acessar esses pontos de extremidade enquanto estiver autenticado como usuário.
+
+Um subconjunto de pontos de extremidade da API v2 de REST exige autenticação como uma instalação do aplicativo GitHub. Consulte [Instalações](/rest/reference/apps#installations) para obter uma lista desses pontos de extremidade.
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/rest-reference/apps/installations.md b/translations/pt-BR/data/reusables/rest-reference/apps/installations.md
new file mode 100644
index 000000000000..189896c82385
--- /dev/null
+++ b/translations/pt-BR/data/reusables/rest-reference/apps/installations.md
@@ -0,0 +1,5 @@
+## Instalações
+
+A API de instalações permite que você obtenha informações sobre as instalações do seu aplicativo GitHub e execute ações nessas instalações. Uma _instalação_ refere-se a qualquer usuário ou conta de organização que instalou o aplicativo. Para obter informações sobre como efetuar a autenticação como uma instalação e limitar o acesso a repositórios específicos, consulte "[Efetuar a autenticação como uma instalação](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation)".
+
+Para listar todas as instalações do aplicativo GitHub para uma organização, consulte "[Listar instalações de aplicativos para uma organização](/rest/reference/orgs#list-app-installations-for-an-organization)".
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/rest-reference/apps/marketplace.md b/translations/pt-BR/data/reusables/rest-reference/apps/marketplace.md
new file mode 100644
index 000000000000..ab66f590eabc
--- /dev/null
+++ b/translations/pt-BR/data/reusables/rest-reference/apps/marketplace.md
@@ -0,0 +1,13 @@
+## Marketplace
+
+Para obter mais informações sobre {% data variables.product.prodname_marketplace %}, consulte "[GitHub Marketplace](/marketplace/)".
+
+A API de {% data variables.product.prodname_marketplace %} permite que você veja quais clientes estão usando um plano de preços, as compras de um cliente e se uma conta tem uma assinatura ativa.
+
+### Fazer testes com pontos de extremidades de amostra
+
+Esta API inclui pontos de extremidade que permitem que você [teste o seu {% data variables.product.prodname_github_app %}](/marketplace/integrating-with-the-github-marketplace-api/testing-github-marketplace-apps/) com **dados de amostra**. Os dados do de amostra têm código rígido, dados falsos e não serão alterados com base em assinaturas reais.
+
+Para fazer teste com dados de amostra, use um pontos de extremidade de amostra no lugar da sua contraparte de produção. Isso permite que você teste se a lógica da API é bem-sucedida antes de anunciar {% data variables.product.prodname_github_apps %} em {% data variables.product.prodname_marketplace %}.
+
+Certifique-se de substituir pontos de extremidades de amostra pelos pontos de extremidades de produção antes de implantar seu {% data variables.product.prodname_github_app %}.
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/rest-reference/apps/oauth-applications.md b/translations/pt-BR/data/reusables/rest-reference/apps/oauth-applications.md
new file mode 100644
index 000000000000..fa48a2a5b7e7
--- /dev/null
+++ b/translations/pt-BR/data/reusables/rest-reference/apps/oauth-applications.md
@@ -0,0 +1,3 @@
+## API de aplicativos do OAuth
+
+Você pode usar esta API para gerenciar os tokens do OAuth que um aplicativo OAuth usa para acessar as contas das pessoas em {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}.
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/rest-reference/apps/webhooks.md b/translations/pt-BR/data/reusables/rest-reference/apps/webhooks.md
new file mode 100644
index 000000000000..7ae5665f8bbc
--- /dev/null
+++ b/translations/pt-BR/data/reusables/rest-reference/apps/webhooks.md
@@ -0,0 +1,3 @@
+## Webhooks
+
+A {% data variables.product.prodname_github_app %}'s webhook allows you to receive HTTP `POST` payloads whenever certain events happen for an app. {% data reusables.webhooks.webhooks-rest-api-links %}
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/rest-reference/billing/billing.md b/translations/pt-BR/data/reusables/rest-reference/billing/billing.md
new file mode 100644
index 000000000000..f3320ff752ec
--- /dev/null
+++ b/translations/pt-BR/data/reusables/rest-reference/billing/billing.md
@@ -0,0 +1 @@
+Você pode obter informações de cobrança para uma empresa. Para obter mais informações, consulte a API REST "[{% data variables.product.prodname_dotcom %} administração de Enterprise](/rest/reference/enterprise-admin#billing)".
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/rest-reference/branches/branch-protection.md b/translations/pt-BR/data/reusables/rest-reference/branches/branch-protection.md
new file mode 100644
index 000000000000..4473664d5762
--- /dev/null
+++ b/translations/pt-BR/data/reusables/rest-reference/branches/branch-protection.md
@@ -0,0 +1 @@
+## Branches protegidos
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/rest-reference/checks/checks.md b/translations/pt-BR/data/reusables/rest-reference/checks/checks.md
new file mode 100644
index 000000000000..9136647420b4
--- /dev/null
+++ b/translations/pt-BR/data/reusables/rest-reference/checks/checks.md
@@ -0,0 +1 @@
+Você pode criar os aplicativos que realizam integração contínua, linting ou serviços de varredura de código e fornecem feedback detalhado sobre commits. Para mais informações, consulte "[Começar com a API de verificações](/rest/guides/getting-started-with-the-checks-api)" e "[Criar testes de CI com a API de verificações](/apps/quickstart-guides/creating-ci-tests-with-the-checks-api/)".
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/rest-reference/checks/runs.md b/translations/pt-BR/data/reusables/rest-reference/checks/runs.md
new file mode 100644
index 000000000000..f261876afe3d
--- /dev/null
+++ b/translations/pt-BR/data/reusables/rest-reference/checks/runs.md
@@ -0,0 +1 @@
+## Execuções de verificação
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/rest-reference/checks/suites.md b/translations/pt-BR/data/reusables/rest-reference/checks/suites.md
new file mode 100644
index 000000000000..b78e3c0d3bd8
--- /dev/null
+++ b/translations/pt-BR/data/reusables/rest-reference/checks/suites.md
@@ -0,0 +1,7 @@
+## conjuntos de verificações
+
+{% note %}
+
+ **Observação:** Um aplicativo GitHub recebe apenas um evento [`check_suite`](/webhooks/event-payloads/#check_suite) por SHA de commit SHA, mesmo se você fizer push do SHA do commit para mais de um branch. Para descobrir quando um SHA do commit é enviado para um branch, você pode assinar os eventos do branch [`criar`](/webhooks/event-payloads/#create).
+
+{% endnote %}
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/rest-reference/code-scanning/code-scanning.md b/translations/pt-BR/data/reusables/rest-reference/code-scanning/code-scanning.md
new file mode 100644
index 000000000000..c196f32909c6
--- /dev/null
+++ b/translations/pt-BR/data/reusables/rest-reference/code-scanning/code-scanning.md
@@ -0,0 +1,15 @@
+{% data reusables.code-scanning.beta %}
+
+A API de {% data variables.product.prodname_code_scanning %} permite que você recupere e atualize alertas de {% data variables.product.prodname_code_scanning %} alertas de um repositório. Você pode usar os pontos de extremidade para criar relatórios automatizados para os alertas de {% data variables.product.prodname_code_scanning %} em uma organização ou fazer upload dos resultados de análise gerados usando as ferramentas off-line de {% data variables.product.prodname_code_scanning %}. Para obter mais informações, consulte "[Encontrar vulnerabilidades e erros de segurança no seu código](/github/finding-security-vulnerabilities-and-errors-in-your-code).
+
+{% ifversion fpt or ghes > 3.0 or ghae or ghec %}
+### Tipo de mídia personalizada para {% data variables.product.prodname_code_scanning %}
+
+Existe um tipo de mídia personalizada com suporte para a API REST de {% data variables.product.prodname_code_scanning %}.
+
+ application/sarif+json
+
+Você pode usar isso com solicitações de `GET` enviadas para o ponto de extremidade `/analyes/{analysis_id}`. Para obter mais informações sobre esta operação, consulte "[Obter uma análise de {% data variables.product.prodname_code_scanning %} para um repositório](#get-a-code-scanning-analysis-for-a-repository)". Ao usar este tipo de mídia com esta operação, a resposta inclui um subconjunto dos dados reais que foram enviados para a análise especificada, em vez do resumo da análise que é retornada quando você usa o tipo de mídia padrão. A resposta também inclui dados adicionais como as propriedades `github/alertNumber` e `github/alertUrl`. Os dados estão formatados como [SARIF versão 2.1.0](https://docs.oasis-open.org/sarif/sarif/v2.1.0/cs01/sarif-v2.1.0-cs01.html).
+
+Para obter mais informações, consulte "[Tipos de mídia](/rest/overview/media-types)".
+{% endif %}
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/rest-reference/codes-of-conduct/codes-of-conduct.md b/translations/pt-BR/data/reusables/rest-reference/codes-of-conduct/codes-of-conduct.md
new file mode 100644
index 000000000000..d6accdfae155
--- /dev/null
+++ b/translations/pt-BR/data/reusables/rest-reference/codes-of-conduct/codes-of-conduct.md
@@ -0,0 +1,2 @@
+
+Você pode usar a API de Códigos de Conduta para recuperar informações sobre o código de conduta de um repositório. Para obter o código de conduta de um repositório, use o ponto de extremidade "[Obter um repositório](/rest/reference/repos#get-a-repository).
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/rest-reference/codespaces/codespaces.md b/translations/pt-BR/data/reusables/rest-reference/codespaces/codespaces.md
new file mode 100644
index 000000000000..c467b9cbfe23
--- /dev/null
+++ b/translations/pt-BR/data/reusables/rest-reference/codespaces/codespaces.md
@@ -0,0 +1,3 @@
+{% data reusables.codespaces.codespaces-api-beta-note %}
+
+A API de {% data variables.product.prodname_codespaces %} permite que você gerencie {% data variables.product.prodname_codespaces %} usando a API REST. Esta API está disponível para usuários autenticados e aplicativos OAuth, mas não para aplicativos GitHub. Para obter mais informações, consulte "[{% data variables.product.prodname_codespaces %}](/codespaces)".
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/rest-reference/codespaces/machines.md b/translations/pt-BR/data/reusables/rest-reference/codespaces/machines.md
new file mode 100644
index 000000000000..4132126ef518
--- /dev/null
+++ b/translations/pt-BR/data/reusables/rest-reference/codespaces/machines.md
@@ -0,0 +1,4 @@
+## Máquinas
+A API de Máquinas permite que um usuário determine quais tipos de máquina estão disponíveis para criar um codespace, seja em um determinado repositório ou como um usuário autenticado. Para obter mais informações, consulte "[Sobre tipos de máquinas](/codespaces/developing-in-codespaces/changing-the-machine-type-for-your-codespace#about-machine-types)".
+
+Você também pode usar essas informações alterando a máquina de um codespace existente, atualizando a propriedade `máquina`. A atualização da máquina ocorrerá na próxima vez que o codespace for reiniciado. Para obter mais informações, consulte "["Mudar o tipo de máquina para seu codespace](/codespaces/developing-in-codespaces/changing-the-machine-type-for-your-codespace)."
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/rest-reference/codespaces/secrets.md b/translations/pt-BR/data/reusables/rest-reference/codespaces/secrets.md
new file mode 100644
index 000000000000..848811f60eaa
--- /dev/null
+++ b/translations/pt-BR/data/reusables/rest-reference/codespaces/secrets.md
@@ -0,0 +1,2 @@
+## Segredos
+A API de Segredos permite que um usuário crie, liste e exclua segredos (como tokens de acesso para serviços de nuvem), além de atribuir segredos para repositórios aos quais o usuário tem acesso. Estes segredos são disponibilizados para o codespace em tempo de execução. Para obter mais informações, consulte "[Gerenciar segredos criptografados para seus codespaces](/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces)".
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/rest-reference/collaborators/invitations.md b/translations/pt-BR/data/reusables/rest-reference/collaborators/invitations.md
new file mode 100644
index 000000000000..a359892684a8
--- /dev/null
+++ b/translations/pt-BR/data/reusables/rest-reference/collaborators/invitations.md
@@ -0,0 +1,9 @@
+## Convites
+
+A API de Convites do Repositório permite que usuários ou serviços externos convidem outros usuários para colaborar em um repositório. Os usuários convidados (ou serviços externos em nome dos usuários convidados) podem optar por aceitar ou recusar os convites.
+
+Observe que o [Escopo OAuth](/developers/apps/scopes-for-oauth-apps) `repo:invite` concede acesso direcionado aos convites **sem** conceder também acesso ao código do repositório. enquanto o escopo `repo` concede permissão ao código e aos convites convites.
+
+### Convidar um usuário para um repositório
+
+Use o ponto de extremidade da API para adicionar um colaborador. Para obter mais informações, consulte "[Adicionar um colaborador de repositório](/rest/reference/collaborators#add-a-repository-collaborator)".
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/rest-reference/commits/comments.md b/translations/pt-BR/data/reusables/rest-reference/commits/comments.md
new file mode 100644
index 000000000000..5db1bdcb85f7
--- /dev/null
+++ b/translations/pt-BR/data/reusables/rest-reference/commits/comments.md
@@ -0,0 +1,12 @@
+## Comentários de commit
+
+### Tipos de mídia personalizados para comentários de commit
+
+Estes são os tipos de mídia compatíveis com os comentários do commit. Você pode ler mais sobre o uso de tipos de mídia na API [aqui](/rest/overview/media-types).
+
+ application/vnd.github-commitcomment.raw+json
+ application/vnd.github-commitcomment.text+json
+ application/vnd.github-commitcomment.html+json
+ application/vnd.github-commitcomment.full+json
+
+Para obter mais informações, consulte "[tipos de mídia personalizados](/rest/overview/media-types)".
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/rest-reference/commits/statuses.md b/translations/pt-BR/data/reusables/rest-reference/commits/statuses.md
new file mode 100644
index 000000000000..232690ba39a8
--- /dev/null
+++ b/translations/pt-BR/data/reusables/rest-reference/commits/statuses.md
@@ -0,0 +1,13 @@
+## Status do commit
+
+A API de status permite que serviços externos marquem commits com status de `erro`, `falha`, `pendente` ou `sucesso`, o que é refletido em pull requests que envolvem esses commits.
+
+Os status também podem incluir uma `descrição` opcional e `target_url`, e é altamente recomendável fornecê-los, pois tornam o status muito mais útil na interface de usuário do GitHub.
+
+Como exemplo, um uso comum é para serviços de integração contínua para marcar commits como criações que passam ou que falham usando o status. O `target_url` seria a URL completa para a saída da criação, e a `descrição` seria o resumo de alto nível do que aconteceu com a criação.
+
+Os status podem incluir um `contexto` para indicar qual serviço está fornecendo esse status. Por exemplo, você pode fazer com que o seu serviço de integração contínua faça push status com um contexto de `ci`, e uma ferramenta de auditoria de segurança faça push dos status com um contexto de `segurança`. Você pode usar [Obter o status combinado para uma referência específica](/rest/reference/commits#get-the-combined-status-for-a-specific-reference) para recuperar todo o status de um commit.
+
+Observe que o `escopo do OAuth` [repo:status](/developers/apps/scopes-for-oauth-apps) concede acesso direcionado a status **sem** conceder acesso ao código do repositório, enquanto o escopo `repo` concede permissão para o código e para status.
+
+Se você está desenvolvendo um aplicativo GitHub e deseja fornecer informações mais detalhadas sobre um serviço externo, você deverá usar a [API de verificação](/rest/reference/checks).
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/rest-reference/dependabot/dependabot.md b/translations/pt-BR/data/reusables/rest-reference/dependabot/dependabot.md
new file mode 100644
index 000000000000..c71e6083d2f6
--- /dev/null
+++ b/translations/pt-BR/data/reusables/rest-reference/dependabot/dependabot.md
@@ -0,0 +1,3 @@
+A API de segredos {% data variables.product.prodname_dependabot %} permite criar, atualizar, excluir e recuperar informações sobre segredos criptografados. {% data reusables.actions.about-secrets %} Para obter mais informações, consulte "[Gerenciar segredos criptografados para o dependabot](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-encrypted-secrets-for-dependabot)."
+
+{% data reusables.actions.actions-authentication %} {% data variables.product.prodname_github_apps %} deve ter a permissão `dependabot_secrets` para usar esta API. Os usuários autenticados devem ter acesso de colaborador em um repositório para criar, atualizar ou ler segredos.
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/rest-reference/deployments/deployments.md b/translations/pt-BR/data/reusables/rest-reference/deployments/deployments.md
new file mode 100644
index 000000000000..6c707417f825
--- /dev/null
+++ b/translations/pt-BR/data/reusables/rest-reference/deployments/deployments.md
@@ -0,0 +1,46 @@
+As implantações são solicitações para implantar um ref específico (branch, SHA, tag). O GitHub envia um [ evento de `implantação`](/developers/webhooks-and-events/webhook-events-and-payloads#deployment) pelo qual os serviços externos podem ouvir e atuar quando novas implantações são criadas. As implantações permitem que os desenvolvedores e as organizações construam ferramentas associadas em torno de implantações sem ter que se preocupar com os detalhes de implementação da entrega de diferentes tipos de aplicativos (p. ex., web, nativo).
+
+Os status de implantação externos permitem marcar implantações com `error`, `failure`, `pending`, `in_progress`, `queued` ou `success` afirmar que os sistemas que estão escutando os eventos [`deployment_status`](/developers/webhooks-and-events/webhook-events-and-payloads#deployment_status) podem consumir.
+
+Os status de implantação também podem incluir uma `descrição` opcional e `log_url`, que são altamente recomendados porque tornam o status de implantação mais útil. O `log_url` é a URL completa para a saída de implantação e a `descrição` é um resumo de alto nível do que aconteceu com a implantação.
+
+O GitHub envia os eventos de `implantação` e `deployment_status` quando novas implantações de status de implantação são criadas. Esses eventos permitem que as integrações de terceiros recebam resposta para solicitações de implantação e atualizem o status de implantação conforme o progresso é feito.
+
+Abaixo está um diagrama de sequência sobre para como essas interações funcionariam.
+
+```
++---------+ +--------+ +-----------+ +-------------+
+| Tooling | | GitHub | | 3rd Party | | Your Server |
++---------+ +--------+ +-----------+ +-------------+
+ | | | |
+ | Create Deployment | | |
+ |--------------------->| | |
+ | | | |
+ | Deployment Created | | |
+ |<---------------------| | |
+ | | | |
+ | | Deployment Event | |
+ | |---------------------->| |
+ | | | SSH+Deploys |
+ | | |-------------------->|
+ | | | |
+ | | Deployment Status | |
+ | |<----------------------| |
+ | | | |
+ | | | Deploy Completed |
+ | | |<--------------------|
+ | | | |
+ | | Deployment Status | |
+ | |<----------------------| |
+ | | | |
+```
+
+Tenha em mente que o GitHub nunca terá acesso aos seus servidores. Cabe à sua integração de terceiros interagir com os eventos de implantação. Vários sistemas podem ouvir eventos de implantação, e cabe a cada um desses sistemas decidir se serão responsáveis por retirar o código dos seus servidores, criar código nativo, etc.
+
+Observe que o `repo_deployment` [OAuth escopo](/developers/apps/scopes-for-oauth-apps) concede acesso direcionado a implantações e status **sem** conceder acesso ao código do repositório, enquanto os es escopos {% ifversion not ghae %}`public_repo` e{% endif %}`repositório` também concedem permissão para codificar.
+
+### Implantações inativas
+
+Ao definir o estado de uma implantação como `sucesso`, todas as implantações de ambiente de não produção e não transitórios anteriores no mesmo nome do ambiente irão tornar-se `inativas`. Para evitar isso, você pode definir `auto_inactive` como `falso` ao criar o status de implantação.
+
+Você pode informar que um ambiente transitório não existe mais definindo seu `estado` como `inativo`. Definir o `estado` como `inativo` mostra a implantação como `destruída` em {% data variables.product.prodname_dotcom %} e remove o acesso a ela.
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/rest-reference/deployments/environments.md b/translations/pt-BR/data/reusables/rest-reference/deployments/environments.md
new file mode 100644
index 000000000000..2c40e62a816d
--- /dev/null
+++ b/translations/pt-BR/data/reusables/rest-reference/deployments/environments.md
@@ -0,0 +1,5 @@
+## Ambientes
+
+A API de Ambientes permite que você crie, configure e exclua ambientes. Para obter mais informações sobre ambientes, consulte "[Usando ambientes para implantação](/actions/deployment/using-environments-for-deployment)". Para gerenciar segredos de ambiente, consulte "[Segredos](/rest/reference/actions#secrets)".
+
+{% data reusables.gated-features.environments %}
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/rest-reference/deployments/keys.md b/translations/pt-BR/data/reusables/rest-reference/deployments/keys.md
new file mode 100644
index 000000000000..0fdc32077349
--- /dev/null
+++ b/translations/pt-BR/data/reusables/rest-reference/deployments/keys.md
@@ -0,0 +1,5 @@
+## Chaves de implantação
+
+{% data reusables.repositories.deploy-keys %}
+
+Chaves de implantação podem ser configuradas usando os seguintes pontos de extremidades da API ou usando o GitHub. Para saber como configurar as chaves de implantação no GitHub, consulte "[Gerenciar chaves de implantação](/developers/overview/managing-deploy-keys)".
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/rest-reference/deployments/statuses.md b/translations/pt-BR/data/reusables/rest-reference/deployments/statuses.md
new file mode 100644
index 000000000000..705e961cd0d0
--- /dev/null
+++ b/translations/pt-BR/data/reusables/rest-reference/deployments/statuses.md
@@ -0,0 +1 @@
+## Status da implantação
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/rest-reference/enterprise-admin/admin-stats.md b/translations/pt-BR/data/reusables/rest-reference/enterprise-admin/admin-stats.md
new file mode 100644
index 000000000000..07d4b0cfa88a
--- /dev/null
+++ b/translations/pt-BR/data/reusables/rest-reference/enterprise-admin/admin-stats.md
@@ -0,0 +1,3 @@
+## Estatísticas de admin
+
+A API de Estatísticas Administrativas fornece uma variedade de métricas sobre sua instalação. *Só está disponível para [administradores do site](/rest/overview/resources-in-the-rest-api#authentication) autenticados.* Usuários normais receberão uma mensagem `404` se tentarem acessá-la.
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/rest-reference/enterprise-admin/announcements.md b/translations/pt-BR/data/reusables/rest-reference/enterprise-admin/announcements.md
new file mode 100644
index 000000000000..69d935e7c7ee
--- /dev/null
+++ b/translations/pt-BR/data/reusables/rest-reference/enterprise-admin/announcements.md
@@ -0,0 +1,3 @@
+## Anúncios
+
+A API de anúncios permite que você gerencie o banner de anúncio global na sua empresa. Para obter mais informações, consulte "[Personalizar mensagens de usuários para a sua empresa](/admin/user-management/customizing-user-messages-for-your-enterprise#creating-a-global-announcement-banner)".
diff --git a/translations/pt-BR/data/reusables/rest-reference/enterprise-admin/audit-log.md b/translations/pt-BR/data/reusables/rest-reference/enterprise-admin/audit-log.md
new file mode 100644
index 000000000000..ed2126689253
--- /dev/null
+++ b/translations/pt-BR/data/reusables/rest-reference/enterprise-admin/audit-log.md
@@ -0,0 +1 @@
+## Log de auditoria
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/rest-reference/enterprise-admin/billing.md b/translations/pt-BR/data/reusables/rest-reference/enterprise-admin/billing.md
new file mode 100644
index 000000000000..dd246ae46234
--- /dev/null
+++ b/translations/pt-BR/data/reusables/rest-reference/enterprise-admin/billing.md
@@ -0,0 +1 @@
+## Cobrança
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/rest-reference/enterprise-admin/enterprise-admin.md b/translations/pt-BR/data/reusables/rest-reference/enterprise-admin/enterprise-admin.md
new file mode 100644
index 000000000000..82d00bc8435e
--- /dev/null
+++ b/translations/pt-BR/data/reusables/rest-reference/enterprise-admin/enterprise-admin.md
@@ -0,0 +1,44 @@
+{% ifversion fpt or ghec %}
+
+{% note %}
+
+**Observação:** Este artigo aplica-se a {% data variables.product.prodname_ghe_cloud %}. Para visualizar a versão de {% data variables.product.prodname_ghe_managed %} ou de {% data variables.product.prodname_ghe_server %}, use o menu suspenso **{% data ui.pages.article_version %}**.
+
+{% endnote %}
+
+{% endif %}
+
+### URLs do ponto de extremidade
+
+Pontos de extremidade da API REST{% ifversion ghes %}—exceto os pontos de extremidades da API REST do [Console de gerenciamento](#management-console) -{% endif %} são prefixados com a seguinte URL:
+
+```shell
+{% data variables.product.api_url_pre %}
+```
+
+{% ifversion fpt or ghec %}
+Quando os pontos de extremidade incluirem `{enterprise}`, substitua `{enterprise}` pelo identificador da conta corporativa, que está incluído no URL das configurações da sua empresa. Por exemplo, se a sua conta corporativa estiver localizada em `https://github.com/enterprises/octo-enterprise`, substitua `{enterprise}` por `octo-enterprise`.
+{% endif %}
+
+{% ifversion ghes %}
+Os endpoints de API [Console de gerenciamento](#management-console) somente são prefixados com um nome de host:
+
+```shell
+http(s)://hostname/
+```
+{% endif %}
+{% ifversion ghae or ghes %}
+### Autenticação
+
+Os endpoints de API da sua instalação do {% data variables.product.product_name %} aceitam [os mesmos métodos de autenticação](/rest/overview/resources-in-the-rest-api#authentication) da API do GitHub.com. Você pode efetuar a autenticação com **[tokens do OAuth](/apps/building-integrations/setting-up-and-registering-oauth-apps/)** {% ifversion ghes %}(que podem ser criado usando a [API de Autorizações](/rest/reference/oauth-authorizations#create-a-new-authorization)) {% endif %}ou **[autenticação básica](/rest/overview/resources-in-the-rest-api#basic-authentication)**. {% ifversion ghes %} Os tokens OAuth devem ter o `site_admin` [escopo OAuth](/developers/apps/scopes-for-oauth-apps#available-scopes) quando usados com endpoints específicos da Enterprise.{% endif %}
+
+Os pontos de extremidade da API da administração da empresa podem ser acessados por administradores do site de {% data variables.product.product_name %}autenticados{% ifversion ghes %}, exceto a API do [Console de Gerenciamento](#management-console), que exige a [senha do console de gerenciamento](/enterprise/admin/articles/accessing-the-management-console/){% endif %}.
+
+{% endif %}
+
+{% ifversion ghae or ghes %}
+### Informações da versão
+
+A versão atual da sua empresa é retornada no cabeçalho de resposta de cada API: `X-GitHub-Enterprise-Version: {{currentVersion}}.0` Você também pode ler a versão atual chamando o [ponto de extremidade de meta](/rest/reference/meta/).
+
+{% endif %}
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/rest-reference/enterprise-admin/global-webhooks.md b/translations/pt-BR/data/reusables/rest-reference/enterprise-admin/global-webhooks.md
new file mode 100644
index 000000000000..539892b3ee48
--- /dev/null
+++ b/translations/pt-BR/data/reusables/rest-reference/enterprise-admin/global-webhooks.md
@@ -0,0 +1,5 @@
+## Webhooks globais
+
+Webhooks globais são instalados na sua empresa. Você pode usar webhooks globais para monitorar, responder ou aplicar regras automaticamente para usuários, organizações, equipes e repositórios na sua empresa. Webhooks globais podem se inscrever para os tipos de eventos [organização](/developers/webhooks-and-events/webhook-events-and-payloads#organization), [usuário](/developers/webhooks-and-events/webhook-events-and-payloads#user), [repositório](/developers/webhooks-and-events/webhook-events-and-payloads#repository), [equipe](/developers/webhooks-and-events/webhook-events-and-payloads#team), [integrante](/developers/webhooks-and-events/webhook-events-and-payloads#member), [filiação](/developers/webhooks-and-events/webhook-events-and-payloads#membership), [bifurcação](/developers/webhooks-and-events/webhook-events-and-payloads#fork)e [ping](/developers/webhooks-and-events/about-webhooks#ping-event).
+
+*Esta API está disponível somente para [administradores do site](/rest/overview/resources-in-the-rest-api#authentication) autenticados.* Usuários normais receberão uma mensagem `404` se tentarem acessá-la. Para aprender como configurar webhooks globais, consulte [Sobre webhooks globais](/enterprise/admin/user-management/about-global-webhooks).
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/rest-reference/enterprise-admin/ldap.md b/translations/pt-BR/data/reusables/rest-reference/enterprise-admin/ldap.md
new file mode 100644
index 000000000000..7387e70fb756
--- /dev/null
+++ b/translations/pt-BR/data/reusables/rest-reference/enterprise-admin/ldap.md
@@ -0,0 +1,5 @@
+## LDAP
+
+Você pode usar a API LDAP para atualizar as relações de conta entre um usuário ou equipe {% data variables.product.product_name %} e sua entrada LDAP vinculada ou enfileirar uma nova sincronização.
+
+Com os endpoints de mapeamento LDAP, você é capaz de atualizar o Nome Distinto (DN) para o qual um usuário ou uma equipe mapeia. Note que os endpoints LDAP são geralmente eficazes apenas se o seu aplicativo de {% data variables.product.product_name %} tiver [Sincronização LDAP habilitada](/enterprise/admin/authentication/using-ldap). O endpoint [mapeamento LDAP de atualização para um usuário](#update-ldap-mapping-for-a-user) pode ser usado quando o LDAP é habilitado, mesmo que a sincronização LDAP esteja desativada.
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/rest-reference/enterprise-admin/license.md b/translations/pt-BR/data/reusables/rest-reference/enterprise-admin/license.md
new file mode 100644
index 000000000000..e70e36348755
--- /dev/null
+++ b/translations/pt-BR/data/reusables/rest-reference/enterprise-admin/license.md
@@ -0,0 +1,3 @@
+## Licença
+
+A API de Licença fornece informações sobre sua licença empresarial. *Só está disponível para [administradores do site](/rest/overview/resources-in-the-rest-api#authentication) autenticados.* Usuários normais receberão uma mensagem `404` se tentarem acessá-la.
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/rest-reference/enterprise-admin/management-console.md b/translations/pt-BR/data/reusables/rest-reference/enterprise-admin/management-console.md
new file mode 100644
index 000000000000..2ec10479c8a5
--- /dev/null
+++ b/translations/pt-BR/data/reusables/rest-reference/enterprise-admin/management-console.md
@@ -0,0 +1,29 @@
+## Console de gerenciamento
+
+A API do Console de Gerenciamento ajuda você a gerenciar sua instalação do {% data variables.product.product_name %}.
+
+{% tip %}
+
+Você deve definir explicitamente o número da porta ao fazer chamadas de API para o Console de Gerenciamento. Se o TLS estiver habilitado na sua empresa, o número da porta será `8443`; caso contrário, o número da porta será `8080`.
+
+Se não quiser fornecer um número da porta, você precisará configurar sua ferramenta para seguir os redirecionamentos automaticamente.
+
+Talvez você também precise adicionar o [`sinalizador`-k](http://curl.haxx.se/docs/manpage.html#-k) quando estiver usando `cURL`, pois {% data variables.product.product_name %} usa um certificado autoassinado antes de você [adicionar seu próprio certificado TLS](/enterprise/admin/guides/installation/configuring-tls/).
+
+{% endtip %}
+
+### Autenticação
+
+Você precisa passar a sua [senha do Console de Gerenciamento](/enterprise/admin/articles/accessing-the-management-console/) como token de autenticação para cada endpoint de API do Console de Gerenciamento, exceto [`/setup/api/start`](#create-a-github-enterprise-server-license).
+
+Use o parâmetro `api_key` para enviar este token com cada solicitação. Por exemplo:
+
+```shell
+$ curl -L 'https://hostname:admin_port/setup/api?api_key=your-amazing-password'
+```
+
+Você também pode usar a autenticação HTTP padrão para enviar esse token. Por exemplo:
+
+```shell
+$ curl -L -u "api_key:your-amazing-password" 'https://hostname:admin_port/setup/api'
+```
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/rest-reference/enterprise-admin/org-pre-receive-hooks.md b/translations/pt-BR/data/reusables/rest-reference/enterprise-admin/org-pre-receive-hooks.md
new file mode 100644
index 000000000000..b5b08ea801db
--- /dev/null
+++ b/translations/pt-BR/data/reusables/rest-reference/enterprise-admin/org-pre-receive-hooks.md
@@ -0,0 +1,16 @@
+## Hooks pre-receive da organização
+
+A API de Hooks pre-receive da Organização permite que você veja e modifique a aplicação dos hooks pre-receive disponíveis para uma organização.
+
+### Atributos do objeto
+
+| Nome | Tipo | Descrição |
+| -------------------------------- | --------- | -------------------------------------------------------------- |
+| `name` | `string` | O nome do hook. |
+| `enforcement` | `string` | O estado de aplicação para o hook neste repositório. |
+| `allow_downstream_configuration` | `boolean` | Se os repositórios podem substituir a imposição. |
+| `configuration_url` | `string` | URL para o ponto de extremidade em que a aplicação é definida. |
+
+Os valores possíveis para *aplicação* são `habilitado`, `desabilitado` e`testando`. `desabilitado` indica que o hook pre-receive não será executado. `habilitado` indica que será executado e rejeitará quaisquer pushes que resultem em um status diferente de zero. `testando` significa que o script será executado, mas não fará com que quaisquer pushes sejam rejeitados.
+
+`configuration_url` pode ser um link para este endpoint ou configuração global deste hook. Apenas administradores do site podem acessar a configuração global.
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/rest-reference/enterprise-admin/orgs.md b/translations/pt-BR/data/reusables/rest-reference/enterprise-admin/orgs.md
new file mode 100644
index 000000000000..e555d58e3cd1
--- /dev/null
+++ b/translations/pt-BR/data/reusables/rest-reference/enterprise-admin/orgs.md
@@ -0,0 +1,3 @@
+## Organizações
+
+A API de administração da organização permite a criação de organizações na sua empresa. *Só está disponível para [administradores do site](/rest/overview/resources-in-the-rest-api#authentication) autenticados.* Usuários normais receberão uma mensagem `404` se tentarem acessá-la.
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/rest-reference/enterprise-admin/pre-receive-environments.md b/translations/pt-BR/data/reusables/rest-reference/enterprise-admin/pre-receive-environments.md
new file mode 100644
index 000000000000..b5b5b3710d68
--- /dev/null
+++ b/translations/pt-BR/data/reusables/rest-reference/enterprise-admin/pre-receive-environments.md
@@ -0,0 +1,25 @@
+## Ambientes pre-receive
+
+A API de Ambientes Pre-receive permite que você crie, liste, atualize e apague ambientes para hooks pre-receive. *Só está disponível para [administradores do site](/rest/overview/resources-in-the-rest-api#authentication) autenticados.* Usuários normais receberão uma mensagem `404` se tentarem acessá-la.
+
+### Atributos do objeto
+
+#### Ambiente pre-receive
+
+| Nome | Tipo | Descrição |
+| --------------------- | --------- | ---------------------------------------------------------------------------------- |
+| `name` | `string` | O nome do ambiente conforme exibido na interface do usuário. |
+| `image_url` | `string` | URL do tarball que será baixado e extraído. |
+| `default_environment` | `boolean` | Se este é o ambiente-padrão que vem com {% data variables.product.product_name %}. |
+| `download` | `objeto` | Status do download deste ambiente. |
+| `hooks_count` | `inteiro` | O número de hooks de pre-receive que usam este ambiente. |
+
+#### Download do ambiente pre-receive
+
+| Nome | Tipo | Descrição |
+| --------------- | -------- | ----------------------------------------------------- |
+| `estado` | `string` | O estado do download mais recente. |
+| `downloaded_at` | `string` | A hora em que o download mais recente começou. |
+| `mensagem` | `string` | Em caso de falha, serão produzidas mensagens de erro. |
+
+Os valores possíveis para o `estado` são `not_started,` `in_progress,` `sucesso` `falhado`.
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/rest-reference/enterprise-admin/pre-receive-hooks.md b/translations/pt-BR/data/reusables/rest-reference/enterprise-admin/pre-receive-hooks.md
new file mode 100644
index 000000000000..6edfe6e74b60
--- /dev/null
+++ b/translations/pt-BR/data/reusables/rest-reference/enterprise-admin/pre-receive-hooks.md
@@ -0,0 +1,18 @@
+## Hooks pre-receive
+
+A API de hooks pre-receive permite que você crie, liste, atualize e apague hooks pre-receive. *Só está disponível para [administradores do site](/rest/overview/resources-in-the-rest-api#authentication) autenticados.* Usuários normais receberão uma mensagem `404` se tentarem acessá-la.
+
+### Atributos do objeto
+
+#### Hook pre-receive
+
+| Nome | Tipo | Descrição |
+| -------------------------------- | --------- | ------------------------------------------------------------------------------ |
+| `name` | `string` | O nome do hook. |
+| `script` | `string` | O script que o hook executa. |
+| `script_repository` | `objeto` | O repositório do GitHub onde o script é mantido. |
+| `ambiente` | `objeto` | O ambiente de pre-receive onde o script é executado. |
+| `enforcement` | `string` | O estado de aplicação para este hook. |
+| `allow_downstream_configuration` | `boolean` | Se a aplicação pode ser substituída no nível da organização ou do repositório. |
+
+Os valores possíveis para *aplicação* são `habilitado`, `desabilitado` e`testando`. `desabilitado` indica que o hook pre-receive não será executado. `habilitado` indica que será executado e rejeitará quaisquer pushes que resultem em um status diferente de zero. `testando` significa que o script será executado, mas não fará com que quaisquer pushes sejam rejeitados.
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/rest-reference/enterprise-admin/repo-pre-receive-hooks.md b/translations/pt-BR/data/reusables/rest-reference/enterprise-admin/repo-pre-receive-hooks.md
new file mode 100644
index 000000000000..4c236e9998d4
--- /dev/null
+++ b/translations/pt-BR/data/reusables/rest-reference/enterprise-admin/repo-pre-receive-hooks.md
@@ -0,0 +1,15 @@
+## Hooks pre-receive do repositório
+
+A API de Hooks pre-receive do Repositório permite que você veja e modifique a aplicação dos hooks pre-receive disponíveis para um repositório.
+
+### Atributos do objeto
+
+| Nome | Tipo | Descrição |
+| ------------------- | -------- | -------------------------------------------------------------- |
+| `name` | `string` | O nome do hook. |
+| `enforcement` | `string` | O estado de aplicação para o hook neste repositório. |
+| `configuration_url` | `string` | URL para o ponto de extremidade em que a aplicação é definida. |
+
+Os valores possíveis para *aplicação* são `habilitado`, `desabilitado` e`testando`. `desabilitado` indica que o hook pre-receive não será executado. `habilitado` indica que será executado e rejeitará quaisquer pushes que resultem em um estado diferente de zero. `testando` significa que o script será executado, mas não fará com que quaisquer pushes sejam rejeitados.
+
+`configuration_url` pode ser um link para este repositório, seu proprietário da organização ou configuração global. A autorização para acessar o ponto de extremidade no `configuration_url` é determinada no nível de proprietário ou administrador do site.
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/rest-reference/enterprise-admin/users.md b/translations/pt-BR/data/reusables/rest-reference/enterprise-admin/users.md
new file mode 100644
index 000000000000..709eeaac0c65
--- /dev/null
+++ b/translations/pt-BR/data/reusables/rest-reference/enterprise-admin/users.md
@@ -0,0 +1,3 @@
+## Usuários
+
+A API de Administração do Usuário permite que você suspenda{% ifversion ghes %}, cancele a suspensão, promova e rebaixe{% endif %}{% ifversion ghae %} e cancele a suspensão{% endif %} dos usuários da sua empresa. *Só está disponível para [administradores do site](/rest/overview/resources-in-the-rest-api#authentication) autenticados.* Usuários normais receberão uma mensagem `403` se tentarem acessá-la.
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/rest-reference/gists/comments.md b/translations/pt-BR/data/reusables/rest-reference/gists/comments.md
new file mode 100644
index 000000000000..831fa67646b1
--- /dev/null
+++ b/translations/pt-BR/data/reusables/rest-reference/gists/comments.md
@@ -0,0 +1,10 @@
+## Comentários
+
+### Tipos de mídia personalizados para comentários do Gist
+
+Estes são os tipos de mídia compatíveis para comentários de gist.
+
+ application/vnd.github.VERSION.raw
+ application/vnd.github.VERSION.base64
+
+Para obter mais informações sobre os tipos de mídia, consulte "[Tipos de mídia personalizados](/rest/overview/media-types)".
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/rest-reference/gists/gists.md b/translations/pt-BR/data/reusables/rest-reference/gists/gists.md
new file mode 100644
index 000000000000..4348e1ded218
--- /dev/null
+++ b/translations/pt-BR/data/reusables/rest-reference/gists/gists.md
@@ -0,0 +1,22 @@
+### Autenticação
+
+Você pode ler listas públicas {% ifversion ghae or ghes %}e criá-las para usuários anônimos sem um token.{% else %} anonimamente, mas você precisa conectar-se ao GitHub para criar gist.{% endif %} Para ler ou escrever gists em nome de um usuário, você precisa do escopo do OAuth e de um token. Para obter mais informações, consulte "[Escopos para aplicativos OAuth](/developers/apps/scopes-for-oauth-apps)."
+
+
+
+### Truncamento
+
+A API de Gist fornece até um megabyte de conteúdo para cada arquivo no gist. Cada arquivo retornado por um gist através da API tem uma chave denominada `truncada`. Se `truncado` for `verdadeiro`, significa que arquivo é muito grande e apenas uma parte do conteúdo foi retornado em `conteúdo`.
+
+Se você precisar do conteúdo completo do arquivo, você pode fazer uma solicitação `GET` para a URL especificada por `raw_url`. Tenha em mente que, para arquivos maiores que dez megabytes, você deverá clonar o gist através da URL fornecida por `git_pull_url`.
+
+Além do conteúdo de um arquivo específico ser truncado, toda a lista de arquivos pode ser truncada se o número total exceder 300 arquivos. Se a chave de nível superior `truncado` é `verdadeira`, apenas os primeiros 300 arquivos foram retornados na lista de arquivos. Se você precisar buscar todos os arquivos do gist, você deverá clonar o gist através da URL fornecida por `git_pull_url`.
+
+### Tipos de mídia personalizados para gists
+
+Estes são os tipos de mídia compatíveis para buscar conteúdo geral.
+
+ application/vnd.github.VERSION.raw
+ application/vnd.github.VERSION.base64
+
+Para obter mais informações, consulte "[Tipos de mídia](/rest/overview/media-types)".
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/rest-reference/git/blobs.md b/translations/pt-BR/data/reusables/rest-reference/git/blobs.md
new file mode 100644
index 000000000000..4379959328b9
--- /dev/null
+++ b/translations/pt-BR/data/reusables/rest-reference/git/blobs.md
@@ -0,0 +1,12 @@
+## Blobs
+
+Um blob (objeto binário grande) do Git é o tipo de objeto usado para armazenar o conteúdo de cada arquivo em um repositório. O hash SHA-1 do arquivo é calculado e armazenado no objeto do blob. Estes pontos de extremidade permitem ler e escrever [objetos do blob](https://git-scm.com/book/en/v1/Git-Internals-Git-Objects) em seu banco de dados d Git em {% data variables.product.product_name %}. Os blobs aproveitam [esses tipos de mídia personalizados](#custom-media-types-for-blobs). Você pode ler mais sobre o uso de tipos de mídia na API [aqui](/rest/overview/media-types).
+
+### Tipos de mídia personalizados para os blobs
+
+Estes são os tipos de mídia compatíveis com blobs.
+
+ application/json
+ application/vnd.github.VERSION.raw
+
+Para obter mais informações, consulte "[Tipos de mídia](/rest/overview/media-types)".
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/rest-reference/git/commits.md b/translations/pt-BR/data/reusables/rest-reference/git/commits.md
new file mode 100644
index 000000000000..4abfb4b9c101
--- /dev/null
+++ b/translations/pt-BR/data/reusables/rest-reference/git/commits.md
@@ -0,0 +1,3 @@
+## Commits
+
+Um commit do Git é um instantâneo da hierarquia ([árvore do Git](/rest/reference/git#trees)) e o conteúdo dos arquivos ([Blob do Git](/rest/reference/git#blobs)) em um repositório do Git. Estes pontos de extremidade permitem ler e escrever [objetos de commit](https://git-scm.com/book/en/v1/Git-Internals-Git-Objects#Commit-Objects) no seu banco de dados do Git em {% data variables.product.product_name %}.
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/rest-reference/git/git.md b/translations/pt-BR/data/reusables/rest-reference/git/git.md
new file mode 100644
index 000000000000..a7af06d84b38
--- /dev/null
+++ b/translations/pt-BR/data/reusables/rest-reference/git/git.md
@@ -0,0 +1 @@
+A API do banco de dados do Git dá acesso para ler e gravar objetos do Git sem processamento no seu banco de dados do Git no {% data variables.product.product_name %} e para listar e atualizar suas referências (cabeçalhos de branch e etiquetas). Para obter mais informações sobre como usar a API do banco de dados do Git, consulte "[Começar com a API de dados do Git](/rest/guides/getting-started-with-the-git-database-api)".
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/rest-reference/git/refs.md b/translations/pt-BR/data/reusables/rest-reference/git/refs.md
new file mode 100644
index 000000000000..f91bb9204acd
--- /dev/null
+++ b/translations/pt-BR/data/reusables/rest-reference/git/refs.md
@@ -0,0 +1,3 @@
+## Referências
+
+Uma referência do Git (`git ref`) é apenas um arquivo que contém um hash SHA-1 do commit do Git. Ao referir-se a um commit do Git, você pode usar a referência do Git, que é um nome fácil de lembrar, em vez do hash. A referência do Git pode ser reescrita para apontar para um novo commit. Um branch é apenas uma referência do Git que armazena o novo hash de commit do Git. Estes pontos de extremidade permitem ler e escrever [referências](https://git-scm.com/book/en/v1/Git-Internals-Git-References) para o seu banco de dados do Git em {% data variables.product.product_name %}.
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/rest-reference/git/tags.md b/translations/pt-BR/data/reusables/rest-reference/git/tags.md
new file mode 100644
index 000000000000..253fc0c62ded
--- /dev/null
+++ b/translations/pt-BR/data/reusables/rest-reference/git/tags.md
@@ -0,0 +1,3 @@
+## Tags
+
+Uma tag do Git é semelhante a uma [Referência do Git](/rest/reference/git#refs), mas o commit do Git para o qual ela aponta nunca muda. As tags do Git são úteis quando você deseja apontar para versões específicas. Esses pontos de extremidade permitem ler e escrever [tags dos objetos](https://git-scm.com/book/en/v1/Git-Internals-Git-References#Tags) em seu banco de dados Git em {% data variables.product.product_name %}. A API de tags do Git é compatível apenas com [objetos de tags anotadas](https://git-scm.com/book/en/v1/Git-Internals-Git-References#Tags), não tags leves.
diff --git a/translations/pt-BR/data/reusables/rest-reference/git/trees.md b/translations/pt-BR/data/reusables/rest-reference/git/trees.md
new file mode 100644
index 000000000000..14c7a1e4fc96
--- /dev/null
+++ b/translations/pt-BR/data/reusables/rest-reference/git/trees.md
@@ -0,0 +1,3 @@
+## Árvores
+
+Um objeto da árvore do Git cria a hierarquia entre arquivos em um repositório do Git. Você pode usar o objeto da árvore do Git para criar a relação entre diretórios e os arquivos que eles contêm. Estes pontos de extremidade permitem que você leia e escreva [objetos de árvore](https://git-scm.com/book/en/v1/Git-Internals-Git-Objects#Tree-Objects) em seu banco de dados do Git em {% data variables.product.product_name %}.
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/rest-reference/gitignore/gitignore.md b/translations/pt-BR/data/reusables/rest-reference/gitignore/gitignore.md
new file mode 100644
index 000000000000..0f4a4386feab
--- /dev/null
+++ b/translations/pt-BR/data/reusables/rest-reference/gitignore/gitignore.md
@@ -0,0 +1,9 @@
+Ao criar um novo repositório em {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} por meio da API, você pode especificar um [.gitignore template](/github/getting-started-with-github/ignoring-files) para que seja aplicado ao repositório após a criação. A API de modlos do .gitignore lista e recupera modelos do repositório de [.gitignore](https://github.com/github/gitignore) de {% data variables.product.product_name %}.
+
+### Tipos de mídia personalizados para gitignore
+
+Você pode usar este tipo de mídia personalizada ao obter um modelo de gitignore.
+
+ application/vnd.github.VERSION.raw
+
+Para obter mais informações, consulte "[Tipos de mídia](/rest/overview/media-types)".
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/rest-reference/interactions/interactions.md b/translations/pt-BR/data/reusables/rest-reference/interactions/interactions.md
new file mode 100644
index 000000000000..f375083a454b
--- /dev/null
+++ b/translations/pt-BR/data/reusables/rest-reference/interactions/interactions.md
@@ -0,0 +1 @@
+Os usuários interagem com repositórios comentando, abrindo problemas e criando pull requests. As APIs de interações permitem que as pessoas com acesso de proprietário ou administrador restrinjam temporariamente a interação com repositórios públicos para um determinado tipo de usuário.
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/rest-reference/interactions/orgs.md b/translations/pt-BR/data/reusables/rest-reference/interactions/orgs.md
new file mode 100644
index 000000000000..7998b59afb91
--- /dev/null
+++ b/translations/pt-BR/data/reusables/rest-reference/interactions/orgs.md
@@ -0,0 +1,9 @@
+## organização
+
+A API de Interações da Organização permite que os proprietários da organização restrinjam temporariamente quais tipos de usuário podem comentar, abrir problemas ou criar pull requests nos repositórios públicos da organização. {% data reusables.interactions.interactions-detail %} Veja mais sobre os tipos de usuários de {% data variables.product.product_name %}:
+
+* {% data reusables.interactions.existing-user-limit-definition %} na organização.
+* {% data reusables.interactions.contributor-user-limit-definition %} na organização.
+* {% data reusables.interactions.collaborator-user-limit-definition %} na organização.
+
+Definir o limite de interação no nível da organização sobrescreverá quaisquer limites de interação definidos para repositórios individuais pertencentes à organização. Para definir diferentes limites de interação para repositórios individuais pertencentes à organização, use os pontos de extremidade das interações do [Repositório](#repository).
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/rest-reference/interactions/repos.md b/translations/pt-BR/data/reusables/rest-reference/interactions/repos.md
new file mode 100644
index 000000000000..3aca6e1f8db1
--- /dev/null
+++ b/translations/pt-BR/data/reusables/rest-reference/interactions/repos.md
@@ -0,0 +1,9 @@
+## Repositório
+
+A API de Interações do Repositório permite que pessoas com acesso de proprietário ou administrador restrinjam temporariamente qual tipo de usuário pode comentar, abrir problemas ou criar pull requests em um repositório público. {% data reusables.interactions.interactions-detail %} Veja mais sobre os tipos de usuários de {% data variables.product.product_name %}:
+
+* {% data reusables.interactions.existing-user-limit-definition %} in the respository.
+* {% data reusables.interactions.contributor-user-limit-definition %} in the respository.
+* {% data reusables.interactions.collaborator-user-limit-definition %} in the respository.
+
+Se um limite de interação for habilitado para o usuário ou organização proprietária do repositório, o limite não poderá ser alterado para o repositório individual. Em vez disso, use os pontos de extremidade de [Usuário](#user) ou [Organização](#organization) para alterar o limite de interação.
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/rest-reference/interactions/users.md b/translations/pt-BR/data/reusables/rest-reference/interactions/users.md
new file mode 100644
index 000000000000..1eb2735ee383
--- /dev/null
+++ b/translations/pt-BR/data/reusables/rest-reference/interactions/users.md
@@ -0,0 +1,9 @@
+## Usuário
+
+The User Interactions API allows you to temporarily restrict which type of user can comment, open issues, or create pull requests on your public repositories. {% data reusables.interactions.interactions-detail %} Veja mais sobre os tipos de usuários de {% data variables.product.product_name %}:
+
+* {% data reusables.interactions.existing-user-limit-definition %} from interacting with your repositories.
+* {% data reusables.interactions.contributor-user-limit-definition %} from interacting with your repositories.
+* {% data reusables.interactions.collaborator-user-limit-definition %} from interacting with your repositories.
+
+Setting the interaction limit at the user level will overwrite any interaction limits that are set for individual repositories owned by the user. To set different interaction limits for individual repositories owned by the user, use the [Repository](#repository) interactions endpoints instead.
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/rest-reference/issues/assignees.md b/translations/pt-BR/data/reusables/rest-reference/issues/assignees.md
new file mode 100644
index 000000000000..9f4e94cd0bdf
--- /dev/null
+++ b/translations/pt-BR/data/reusables/rest-reference/issues/assignees.md
@@ -0,0 +1 @@
+## Responsáveis
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/rest-reference/issues/comments.md b/translations/pt-BR/data/reusables/rest-reference/issues/comments.md
new file mode 100644
index 000000000000..aa980e453290
--- /dev/null
+++ b/translations/pt-BR/data/reusables/rest-reference/issues/comments.md
@@ -0,0 +1,5 @@
+## Comentários
+
+A API de Comentários do Problema é compatível com listagem, visualização, edição e criação de comentários em problemas e pull requests.
+
+Os comentários do problema usam [estes tipos de mídia personalizados](#custom-media-types). Você pode ler mais sobre o uso de tipos de mídia na API [aqui](/rest/overview/media-types).
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/rest-reference/issues/events.md b/translations/pt-BR/data/reusables/rest-reference/issues/events.md
new file mode 100644
index 000000000000..9462a2422e28
--- /dev/null
+++ b/translations/pt-BR/data/reusables/rest-reference/issues/events.md
@@ -0,0 +1,3 @@
+## Eventos
+
+The Issue Events API can return different types of events triggered by activity in issues and pull requests. For more information about the specific events that you can receive from the Issue Events API, see "[Issue event types](/developers/webhooks-and-events/issue-event-types)." For more information about the specific events that you can receive from the Issue Events API, see "[Issue event types](/developers/webhooks-and-events/issue-event-types)." For more information, see the "[Events API](/developers/webhooks-and-events/github-event-types)."
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/rest-reference/issues/issues.md b/translations/pt-BR/data/reusables/rest-reference/issues/issues.md
new file mode 100644
index 000000000000..61b105ff4400
--- /dev/null
+++ b/translations/pt-BR/data/reusables/rest-reference/issues/issues.md
@@ -0,0 +1,10 @@
+### Tipos de mídia personalizados para problemas
+
+Estes são os tipos de mídia compatíveis para problemas.
+
+ application/vnd.github.VERSION.raw+json
+ application/vnd.github.VERSION.text+json
+ application/vnd.github.VERSION.html+json
+ application/vnd.github.VERSION.full+json
+
+Para obter mais informações sobre os tipos de mídia, consulte "[Tipos de mídia personalizados](/rest/overview/media-types)".
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/rest-reference/issues/labels.md b/translations/pt-BR/data/reusables/rest-reference/issues/labels.md
new file mode 100644
index 000000000000..e01b345a6b03
--- /dev/null
+++ b/translations/pt-BR/data/reusables/rest-reference/issues/labels.md
@@ -0,0 +1 @@
+## Etiquetas
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/rest-reference/issues/milestones.md b/translations/pt-BR/data/reusables/rest-reference/issues/milestones.md
new file mode 100644
index 000000000000..e9ad7bda9913
--- /dev/null
+++ b/translations/pt-BR/data/reusables/rest-reference/issues/milestones.md
@@ -0,0 +1 @@
+## Marcos
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/rest-reference/issues/timeline.md b/translations/pt-BR/data/reusables/rest-reference/issues/timeline.md
new file mode 100644
index 000000000000..8e518ac1523e
--- /dev/null
+++ b/translations/pt-BR/data/reusables/rest-reference/issues/timeline.md
@@ -0,0 +1,5 @@
+## Linha do tempo
+
+A API de Eventos da Linha do Tempo pode retornar diferentes tipos de eventos acionados pela atividade da linha do tempo em problemas e pull requests. For more information about the specific events that you can receive from the Issue Events API, see "[Issue event types](/developers/webhooks-and-events/issue-event-types)." For more information about the specific events that you can receive from the Issue Events API, see "[Issue event types](/developers/webhooks-and-events/issue-event-types)." Para obter mais informações, consulte a "[API de Eventos do GitHub](/developers/webhooks-and-events/github-event-types)".
+
+Você pode usar esta API para exibir informações sobre problemas e pull request ou determinar quem deve ser notificado sobre os comentários de problema.
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/rest-reference/licenses/licenses.md b/translations/pt-BR/data/reusables/rest-reference/licenses/licenses.md
new file mode 100644
index 000000000000..a12f154219dc
--- /dev/null
+++ b/translations/pt-BR/data/reusables/rest-reference/licenses/licenses.md
@@ -0,0 +1,22 @@
+A API de Licenças retorna metadados sobre as licenças de código aberto populares e informações sobre o arquivo de licença de um determinado projeto.
+
+A API de Licenças usa [a Licença de código aberto do Gem do Ruby](https://github.com/benbalter/licensee) para tentar identificar a licença do projeto. A licença corresponde ao conteúdo do arquivo `LICENÇA` de um projeto (se existir) em comparação com uma pequena lista de licenças conhecidas. Como resultado, a API não leva em conta as licenças das dependências do projeto ou outros meios de documentar a licença de um projeto, como, por exemplo, referências ao nome da licença na documentação.
+
+Se uma licença for correspondida, a chave da licença e o nome retornados serão conformes à [especificação SPDX](https://spdx.org/).
+
+**Observação:** Estes pontos de extremidade também retornarão informações de licença de um repositório:
+
+- [Obter um repositório](/rest/reference/repos#get-a-repository)
+- [Listar repositórios para um usuário](/rest/reference/repos#list-repositories-for-a-user)
+- [Listar repositórios da organização](/rest/reference/repos#list-organization-repositories)
+- [Listar bifurcações](/rest/reference/repos#list-forks)
+- [Listar repositórios inspecionados por um usuário](/rest/reference/activity#list-repositories-watched-by-a-user)
+- [Listar repositórios da equipe](/rest/reference/teams#list-team-repositories)
+
+{% warning %}
+
+O GitHub pode ser muitas coisas, mas não é um escritório de advocacia. Como tal, o GitHub não oferece aconselhamento jurídico. Usar a API de licenças ou enviar-nos um e-mail sobre a mesma não constitui aconselhamento jurídico, nem cria uma relação advogado e cliente. Em caso de dúvida sobre o que se pode e não se pode fazer com uma licença específica, antes de avançar, você deverá buscar orientação jurídica antes de seguir em frente. Na verdade, você deve sempre consultar o seu próprio advogado antes de tomar decisões que possam ter desdobramentos jurídicos ou que possam afetar seus direitos.
+
+O GitHub criou a API da licença para ajudar os usuários a obter informações sobre licenças de código aberto e os projetos que as utilizam. Esperamos que ajude. No entanto, tenha em mente que não somos advogados (pelo menos a maioria de nós) e que cometemos erros como qualquer um. Por esse motivo, o GitHub fornece a API numa base "como se apresenta" e não faz garantias sobre quaisquer informações ou licenças fornecidas em ou através dela, além de eximir-se da responsabilidade por danos resultantes do uso da API.
+
+{% endwarning %}
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/rest-reference/metrics/community.md b/translations/pt-BR/data/reusables/rest-reference/metrics/community.md
new file mode 100644
index 000000000000..f4468c7c2fe6
--- /dev/null
+++ b/translations/pt-BR/data/reusables/rest-reference/metrics/community.md
@@ -0,0 +1 @@
+## Comunidade
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/rest-reference/metrics/statistics.md b/translations/pt-BR/data/reusables/rest-reference/metrics/statistics.md
new file mode 100644
index 000000000000..d12efa80e348
--- /dev/null
+++ b/translations/pt-BR/data/reusables/rest-reference/metrics/statistics.md
@@ -0,0 +1,17 @@
+## Estatísticas
+
+A API de Estatísticas do Repositório permite que você recupere os dados que o {% data variables.product.product_name %} usa para visualizar diferentes tipos de atividade do repositório.
+
+### Umas palavras sobre o armazenamento em cache
+
+Computar as estatísticas do repositório é uma operação cara. Por esse motivo, tentamos retornar dados armazenados em cache sempre que possível. Se os dados não forem armazenados em cache nas estatísticas de um repositório, você receberá uma resposta de `202`; um trabalho em segundo plano também é acionado para começar a compilar estas estatísticas. Dê ao trabalho alguns instantes para que seja concluído e, em seguida, envie a solicitação novamente. Se o trabalho foi concluído, essa solicitação receberá uma resposta de `200` com as estatísticas no texto da resposta.
+
+As estatísticas do repositório são armazenadas em cache pelo SHA do branch-padrão do repositório; fazer push para o branch-padrão redefine o armazenamento em cache de estatísticas.
+
+### As estatísticas excluem alguns tipos de commits
+
+As estatísticas expostas pela API correspondem às estatísticas mostradas pelos [diferentes gráficos de repositórios](/github/visualizing-repository-data-with-graphs/about-repository-graphs).
+
+Resumo:
+- Todas as estatísticas excluem commits de merge.
+- As estatísticas do contribuidor também excluem commits vazios.
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/rest-reference/metrics/traffic.md b/translations/pt-BR/data/reusables/rest-reference/metrics/traffic.md
new file mode 100644
index 000000000000..5b7475ec37bb
--- /dev/null
+++ b/translations/pt-BR/data/reusables/rest-reference/metrics/traffic.md
@@ -0,0 +1,3 @@
+## Tráfego
+
+Para repositórios aos quais você tem acesso de push, a API de tráfego fornece acesso às informações fornecidas no seu gráfico de repositório. Para obter mais informações, consulte "Visualizar tráfego para um repositório. "
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/rest-reference/migrations/orgs.md b/translations/pt-BR/data/reusables/rest-reference/migrations/orgs.md
new file mode 100644
index 000000000000..3e857a3c8f51
--- /dev/null
+++ b/translations/pt-BR/data/reusables/rest-reference/migrations/orgs.md
@@ -0,0 +1,5 @@
+## organização
+
+A API de migrações só está disponível para os proprietários de organizações autenticadas. Para obter mais informações, consulte "[Funções em organização](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#permission-levels-for-an-organization)" e "[Outros métodos de autenticação](/rest/overview/other-authentication-methods)".
+
+{% data variables.migrations.organization_migrations_intro %}
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/rest-reference/migrations/source-imports.md b/translations/pt-BR/data/reusables/rest-reference/migrations/source-imports.md
new file mode 100644
index 000000000000..9176ca90ef4f
--- /dev/null
+++ b/translations/pt-BR/data/reusables/rest-reference/migrations/source-imports.md
@@ -0,0 +1,80 @@
+## Importações de código-fonte
+
+{% data variables.migrations.source_imports_intro %}
+
+Uma importação de código-fonte típica iniciaria a importação e, em seguida, (opcionalmente) atualizaria os autores e/ou atualizaria a preferência pelo uso do LFS do Git se existirem arquivos grandes na importação. Também é possível criar um webhook que ouve o [`ReposityImportEvent`](/developers/webhooks-and-events/webhook-events-and-payloads#repository_import) para descobrir o status da importação.
+
+Um exemplo mais detalhado pode ser visto neste diagrama:
+
+```
++---------+ +--------+ +---------------------+
+| Tooling | | GitHub | | Original Repository |
++---------+ +--------+ +---------------------+
+ | | |
+ | Start import | |
+ |----------------------------->| |
+ | | |
+ | | Download source data |
+ | |--------------------------------------------->|
+ | | Begin streaming data |
+ | |<---------------------------------------------|
+ | | |
+ | Get import progress | |
+ |----------------------------->| |
+ | "status": "importing" | |
+ |<-----------------------------| |
+ | | |
+ | Get commit authors | |
+ |----------------------------->| |
+ | | |
+ | Map a commit author | |
+ |----------------------------->| |
+ | | |
+ | | |
+ | | Finish streaming data |
+ | |<---------------------------------------------|
+ | | |
+ | | Rewrite commits with mapped authors |
+ | |------+ |
+ | | | |
+ | |<-----+ |
+ | | |
+ | | Update repository on GitHub |
+ | |------+ |
+ | | | |
+ | |<-----+ |
+ | | |
+ | Map a commit author | |
+ |----------------------------->| |
+ | | Rewrite commits with mapped authors |
+ | |------+ |
+ | | | |
+ | |<-----+ |
+ | | |
+ | | Update repository on GitHub |
+ | |------+ |
+ | | | |
+ | |<-----+ |
+ | | |
+ | Get large files | |
+ |----------------------------->| |
+ | | |
+ | opt_in to Git LFS | |
+ |----------------------------->| |
+ | | Rewrite commits for large files |
+ | |------+ |
+ | | | |
+ | |<-----+ |
+ | | |
+ | | Update repository on GitHub |
+ | |------+ |
+ | | | |
+ | |<-----+ |
+ | | |
+ | Get import progress | |
+ |----------------------------->| |
+ | "status": "complete" | |
+ |<-----------------------------| |
+ | | |
+ | | |
+```
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/rest-reference/migrations/users.md b/translations/pt-BR/data/reusables/rest-reference/migrations/users.md
new file mode 100644
index 000000000000..61e8d1f01959
--- /dev/null
+++ b/translations/pt-BR/data/reusables/rest-reference/migrations/users.md
@@ -0,0 +1,9 @@
+## Usuário
+
+A API de migrações do usuário só está disponível para proprietários de contas autenticadas. Para obter mais informações, consulte "[Outros métodos de autenticação](/rest/overview/other-authentication-methods)".
+
+{% data variables.migrations.user_migrations_intro %} Para obter uma lista dos dados de migração que você pode baixar, consulte "[Fazer download de um arquivo de migração do usuário](#download-a-user-migration-archive)".
+
+Para fazer o download de um arquivo, você deverá iniciar uma migração de usuário primeiro. Uma vez que o status da migração é `exportado`, você pode fazer o download da migração.
+
+Ao criar um arquivo de migração, ele ficará disponível para download por sete dias. No entanto, você pode excluir o arquivo de migração do usuário mais cedo, se desejar. Você pode desbloquear o repositório quando a migração for `exportada` para começar a usar seu repositório novamente ou excluir o repositório se não precisar mais dos dados do código-fonte.
diff --git a/translations/pt-BR/data/reusables/rest-reference/oauth-authorizations/oauth-authorizations.md b/translations/pt-BR/data/reusables/rest-reference/oauth-authorizations/oauth-authorizations.md
new file mode 100644
index 000000000000..2df8e2e9a278
--- /dev/null
+++ b/translations/pt-BR/data/reusables/rest-reference/oauth-authorizations/oauth-authorizations.md
@@ -0,0 +1,3 @@
+Você pode usar esta API para gerenciar o acesso do aplicativo OAuth à sua conta. Você só pode acessar esta API através da [Autenticação básica](/rest/overview/other-authentication-methods#basic-authentication) usando seu nome de usuário e senha, não tokens.
+
+Se você ou seus usuários tiverem a autenticação de dois fatores habilitada, certifique-se de entender como [trabalhar com autenticação de dois fatores](/rest/overview/other-authentication-methods#working-with-two-factor-authentication).
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/rest-reference/orgs/blocking.md b/translations/pt-BR/data/reusables/rest-reference/orgs/blocking.md
new file mode 100644
index 000000000000..07cedf97eaae
--- /dev/null
+++ b/translations/pt-BR/data/reusables/rest-reference/orgs/blocking.md
@@ -0,0 +1,3 @@
+## Bloquear usuários
+
+O token usado para autenticar a chamada deve ter o escopo `admin:org` para fazer quaisquer chamadas de bloqueio para uma organização. Caso contrário, a resposta retornará `HTTP 404`.
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/rest-reference/orgs/custom_roles.md b/translations/pt-BR/data/reusables/rest-reference/orgs/custom_roles.md
new file mode 100644
index 000000000000..ebd3cce84369
--- /dev/null
+++ b/translations/pt-BR/data/reusables/rest-reference/orgs/custom_roles.md
@@ -0,0 +1 @@
+## Funções de repositório personalizadas
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/rest-reference/orgs/members.md b/translations/pt-BR/data/reusables/rest-reference/orgs/members.md
new file mode 100644
index 000000000000..fa0b179e1a43
--- /dev/null
+++ b/translations/pt-BR/data/reusables/rest-reference/orgs/members.md
@@ -0,0 +1 @@
+## Integrantes
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/rest-reference/orgs/outside-collaborators.md b/translations/pt-BR/data/reusables/rest-reference/orgs/outside-collaborators.md
new file mode 100644
index 000000000000..e4b68bef01f8
--- /dev/null
+++ b/translations/pt-BR/data/reusables/rest-reference/orgs/outside-collaborators.md
@@ -0,0 +1 @@
+## Colaboradores externos
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/rest-reference/orgs/webhooks.md b/translations/pt-BR/data/reusables/rest-reference/orgs/webhooks.md
new file mode 100644
index 000000000000..e5b031df6698
--- /dev/null
+++ b/translations/pt-BR/data/reusables/rest-reference/orgs/webhooks.md
@@ -0,0 +1,24 @@
+## Webhooks
+
+Os webhooks da organização permitem que você receba cargas de HTTP do tipo `POST` sempre que certos eventos ocorrerem dentro da organização. {% data reusables.webhooks.webhooks-rest-api-links %}
+
+Para obter mais informações sobre ações que você pode assinar, consulte "[ tipos de evento de {% data variables.product.prodname_dotcom %}](/developers/webhooks-and-events/github-event-types)".
+
+### Escopos & Restrições
+
+Todas as ações contra webhooks da organização exigem que o usuário autenticado seja um administrador da organização que está sendo gerenciada. Além disso, os tokens do OAuth requerem o escopo `admin:org_hook`. Para obter mais informações, consulte "[Escopos para aplicativos OAuth](/developers/apps/scopes-for-oauth-apps)."
+
+Para proteger dados sensíveis que podem estar presentes nas configurações do webhook, também aplicamos as seguintes regras de controle de acesso:
+
+- Os aplicativos OAuth não podem listar, visualizar ou editar webhooks que não criaram.
+- Os usuários não podem listar, visualizar ou editar webhooks que foram criados por aplicativos OAuth.
+
+### Receber Webhooks
+
+Para que {% data variables.product.product_name %} envie cargas de webhook, seu servidor deve ser acessível pela internet. É altamente recomendável o uso de SSL para que possamos enviar cargas criptografadas por HTTPS.
+
+Para obter mais práticas recomendadas, [consulte nosso guia](/guides/best-practices-for-integrators/).
+
+#### Cabeçalhos de webhook
+
+{% data variables.product.product_name %} enviará ao longo de vários cabeçalhos de HTTP para diferenciar entre tipos de evento e identificadores de carga. Consulte [cabeçalhos de webhook](/webhooks/event-payloads/#delivery-headers) para obter informações.
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/rest-reference/packages/packages.md b/translations/pt-BR/data/reusables/rest-reference/packages/packages.md
new file mode 100644
index 000000000000..e35aa6855006
--- /dev/null
+++ b/translations/pt-BR/data/reusables/rest-reference/packages/packages.md
@@ -0,0 +1,10 @@
+A API de {% data variables.product.prodname_registry %} permite gerenciar pacotes usando a API REST. Para saber mais sobre como restaurar ou excluir pacotes, consulte "[Restaurar e excluir pacotes](/packages/learn-github-packages/deleting-and-restoring-a-package)"".
+
+Para usar essa API, você deve efetuar a autenticação usando um token de acesso pessoal.
+ - Para acessar os metadados do pacote, seu token deve incluir o escopo `read:packages`.
+ - Para excluir pacotes e versões de pacote, seu token deverá incluir os escopos `read:packages` e `delete:packages`.
+ - Para restaurar pacotes e versões do pacote, o seu token deve incluir os escopos `read:packages` e `write:packages`.
+
+Se seu `package_type` for `npm`, `maven`, `rubygems` ou `nuget`, o seu token também deverá incluir o escopo `repo` já que o pacote herda as permissões de um repositório de {% data variables.product.prodname_dotcom %}. Se seu pacote estiver em {% data variables.product.prodname_container_registry %}, seu `package_type` será `container` e seu token não precisará do escopo `repositório` para acessar ou gerenciar este `package_type`. Os pacotes de `contêiner` oferecem permissões granulares separadas de um repositório. Para obter mais informações, consulte "[Sobre permissões para {% data variables.product.prodname_registry %}](/packages/learn-github-packages/about-permissions-for-github-packages#about-scopes-and-permissions-for-package-registries)".
+
+Se você quiser usar a API de {% data variables.product.prodname_registry %} para acessar os recursos em uma organização com SSO habilitado, então você deve habilitar o SSO para o seu token de acesso pessoal. Para mais informações consulte "[Autorizando um token de acesso pessoal para usar com lgon único SAML](/github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on){% ifversion fpt %}" na documentação de {% data variables.product.prodname_ghe_cloud %}.{% else %}."{% endif %}
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/rest-reference/pages/pages.md b/translations/pt-BR/data/reusables/rest-reference/pages/pages.md
new file mode 100644
index 000000000000..1699cdb9b044
--- /dev/null
+++ b/translations/pt-BR/data/reusables/rest-reference/pages/pages.md
@@ -0,0 +1,14 @@
+A API de {% data variables.product.prodname_pages %} recupera informações sobre a sua configuração do {% data variables.product.prodname_pages %} e os status das suas criações. Informações sobre o site e as criações só podem ser acessadas pelos proprietários autenticados{% ifversion not ghae %}, mesmo que os sites sejam públicos{% endif %}. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages)".
+
+Nos pontos de extremidade da API de {% data variables.product.prodname_pages %} com uma chave de `status` na sua resposta, o valor pode ser:
+* `null`: O site ainda não foi criado.
+* `queued`: A criação foi solicitada, mas ainda não começou.
+* `building`:A criaçãoestá em andamento.
+* `built`: O site foi criado.
+* `errored`: Indica que ocorreu um erro durante a criação.
+
+Nos pontos de extremidade da API de {% data variables.product.prodname_pages %} que devolvem as informações do site do GitHub Pages, as respostas do JSON incluem esses campos:
+* `html_url`: A URL absoluta (incluindo o esquema) do site de páginas interpretadas. Por exemplo, `https://username.github.io`.
+* `source`: Um objeto que contém o branch de origem e o diretório do site de páginas interpretadas. Isto inclui:
+ - `branch`: O branch do repositório utilizado para publicar os [arquivos de origem do site](/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site). Por exemplo, _principal_ ou _gh-pages_.
+ - `path`: O diretório do repositório a partir do qual o site é publicado. Será `/` ou `/docs`.
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/rest-reference/projects/cards.md b/translations/pt-BR/data/reusables/rest-reference/projects/cards.md
new file mode 100644
index 000000000000..14adde288d5a
--- /dev/null
+++ b/translations/pt-BR/data/reusables/rest-reference/projects/cards.md
@@ -0,0 +1 @@
+## Cartões
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/rest-reference/projects/collaborators.md b/translations/pt-BR/data/reusables/rest-reference/projects/collaborators.md
new file mode 100644
index 000000000000..3abd53c2c5c9
--- /dev/null
+++ b/translations/pt-BR/data/reusables/rest-reference/projects/collaborators.md
@@ -0,0 +1,3 @@
+## Colaboradores
+
+Esta API permite que você interaja com os projetos de uma organização.
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/rest-reference/projects/columns.md b/translations/pt-BR/data/reusables/rest-reference/projects/columns.md
new file mode 100644
index 000000000000..54a7ee250daa
--- /dev/null
+++ b/translations/pt-BR/data/reusables/rest-reference/projects/columns.md
@@ -0,0 +1 @@
+## Colunas
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/rest-reference/pulls/comments.md b/translations/pt-BR/data/reusables/rest-reference/pulls/comments.md
new file mode 100644
index 000000000000..325526038119
--- /dev/null
+++ b/translations/pt-BR/data/reusables/rest-reference/pulls/comments.md
@@ -0,0 +1,14 @@
+## Comentários de revisão
+
+Os comentários de revisão de pull request são comentários em uma parte do diff unificado feitos durante uma revisão de pull request. Comentários de commit e comentários de problemas são são diferentes dos comentários de revisão de pull request. Você aplica comentários de submissão diretamente para um commit e aplica comentários de problema sem fazer referência a uma parte do diff unificado. Para obter mais informações, consulte "[Criar um comentário de commit](/rest/reference/commits#create-a-commit-comment)" e "[Criar um comentário de problema](/rest/reference/issues#create-an-issue-comment)".
+
+### Tipos de mídia personalizados para comentários de revisão de pull request
+
+Estes são os tipos de mídia compatíveis com os comentários de revisão de pull request.
+
+ application/vnd.github.VERSION.raw+json
+ application/vnd.github.VERSION.text+json
+ application/vnd.github.VERSION.html+json
+ application/vnd.github.VERSION.full+json
+
+Para obter mais informações, consulte "[tipos de mídia personalizados](/rest/overview/media-types)".
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/rest-reference/pulls/pulls.md b/translations/pt-BR/data/reusables/rest-reference/pulls/pulls.md
new file mode 100644
index 000000000000..a9364585a2a3
--- /dev/null
+++ b/translations/pt-BR/data/reusables/rest-reference/pulls/pulls.md
@@ -0,0 +1,33 @@
+A API do Pull Request permite que você liste, visualize, edite, crie e até mesmo faça merge de pull requests. Comentários em pull requests podem ser gerenciados através da [API de Comentários do Problema](/rest/reference/issues#comments).
+
+Cada pull request é um problema, mas nem todos os problemas são um pull request. Por este motivo, as ações "compartilhadas" para ambos os recursos, como a manipulação de responsáveis, etiquetas e marcos são fornecidos dentro de [a API de problemas](/rest/reference/issues).
+
+### Tipos de mídia personalizados para pull requests
+
+Estes são os tipos de mídia compatíveis com pull requests.
+
+ application/vnd.github.VERSION.raw+json
+ application/vnd.github.VERSION.text+json
+ application/vnd.github.VERSION.html+json
+ application/vnd.github.VERSION.full+json
+ application/vnd.github.VERSION.diff
+ application/vnd.github.VERSION.patch
+
+Para obter mais informações, consulte "[tipos de mídia personalizados](/rest/overview/media-types)".
+
+Se um diff estiver corrompido, entre em contato com {% data variables.contact.contact_support %}. Inclua o nome e o ID do pull request do repositório na sua mensagem.
+
+### Relações do Link
+
+Pull Requests têm estas relações de link possíveis:
+
+| Nome | Descrição |
+| ----------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `self` | O local da API deste Pull Request. |
+| `html` | O locl do HTML deste Pull Request. |
+| `problema` | O local da API do [Problema](/rest/reference/issues) deste Pull Request. |
+| `comentários` | O local da API dos [comentários do problema](/rest/reference/issues#comments) deste Pull Request. |
+| `review_comments` | O local da API dos [comentários da revisão](/rest/reference/pulls#comments) deste Pull Request. |
+| `review_comment` | O [modelo de URL](/rest#hypermedia) para construir o local da API para um [comentário de revisão](/rest/reference/pulls#comments) no repositório deste Pull Request. |
+| `commits` | O local da API dos [commits](#list-commits-on-a-pull-request) deste Pull Request. |
+| `Status` | O local da API dos [status do commit](/rest/reference/commits#commit-statuses) deste pull request, que são os status no seu branch `principal`. |
diff --git a/translations/pt-BR/data/reusables/rest-reference/pulls/review-requests.md b/translations/pt-BR/data/reusables/rest-reference/pulls/review-requests.md
new file mode 100644
index 000000000000..23aa1a323a0c
--- /dev/null
+++ b/translations/pt-BR/data/reusables/rest-reference/pulls/review-requests.md
@@ -0,0 +1,3 @@
+## Solicitações de revisão
+
+Os autores dos pull request e os proprietários e colaboradores dos repositórios podem solicitar uma revisão de pull request para qualquer pessoa com acesso de gravação ao repositório. Cada revisor solicitado receberá uma notificação pedindo-lhes para revisar o pull request.
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/rest-reference/pulls/reviews.md b/translations/pt-BR/data/reusables/rest-reference/pulls/reviews.md
new file mode 100644
index 000000000000..34145cd705ed
--- /dev/null
+++ b/translations/pt-BR/data/reusables/rest-reference/pulls/reviews.md
@@ -0,0 +1,3 @@
+## Revisões
+
+As revisões de pull request são grupos de comentários de revisão de pull request no Pull Request, agrupados e com um status e comentário de texto opcional.
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/rest-reference/rate-limit/rate-limit.md b/translations/pt-BR/data/reusables/rest-reference/rate-limit/rate-limit.md
new file mode 100644
index 000000000000..be26e4ce487d
--- /dev/null
+++ b/translations/pt-BR/data/reusables/rest-reference/rate-limit/rate-limit.md
@@ -0,0 +1,17 @@
+A documentação geral da API REST descreve as [regras de limite de taxa](/rest/overview/resources-in-the-rest-api#rate-limiting). Você pode verificar seu status de limite de taxa atual a qualquer momento usando a API de limite de taxa descrita abaixo.
+
+### Entender o seu status de limite de taxa
+
+A API de pesquisa tem um [limite de taxa personalizado](/rest/reference/search#rate-limit), separado do limite de taxa que rege o restante da API REST. A API do GraphQL também tem um [limite de taxa personalizado]({% ifversion ghec%}/free-pro-team@latest{% endif %}/graphql/overview/resource-limitations#rate-limit), que é separado e calculado de forma diferente dos limites de taxa na API REST.
+
+Por esses motivos, a resposta da API do limite de taxa categoriza o seu limite de taxa. Em `recursos`, você verá quatro objetos:
+
+* O objeto `principal` fornece o status do limite de taxa para todos os recursos não relacionados à pesquisa na API REST.
+
+* O objeto `de pesquisa` fornece o status do limite de taxa para a [API de pesquisa](/rest/reference/search).
+
+* O objeto `graphql` fornece o status do limite de taxa para a [API do GraphQL]({% ifversion ghec%}/free-pro-team@latest{% endif %}/graphql).
+
+* O objeto `integration_manifest` fornece o status do limite de taxa para o ponto de extremidade [Conversão do código de manifesto do aplicativo GitHub](/apps/building-github-apps/creating-github-apps-from-a-manifest/#3-you-exchange-the-temporary-code-to-retrieve-the-app-configuration).
+
+Para obter mais informações sobre os cabeçalhos e valores na resposta de limite de taxa, consulte "[Recursos na API REST](/rest/overview/resources-in-the-rest-api#rate-limit-http-headers)".
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/rest-reference/reations/reactions.md b/translations/pt-BR/data/reusables/rest-reference/reations/reactions.md
new file mode 100644
index 000000000000..d2feff37dd76
--- /dev/null
+++ b/translations/pt-BR/data/reusables/rest-reference/reations/reactions.md
@@ -0,0 +1,5 @@
+### Reaction types
+
+When creating a reaction, the allowed values for the `content` parameter are as follows (with the corresponding emoji for reference):
+
+{% data reusables.repositories.reaction_list %}
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/rest-reference/releases/assets.md b/translations/pt-BR/data/reusables/rest-reference/releases/assets.md
new file mode 100644
index 000000000000..0b0f48e0111e
--- /dev/null
+++ b/translations/pt-BR/data/reusables/rest-reference/releases/assets.md
@@ -0,0 +1 @@
+## Ativos de versões
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/rest-reference/releases/releases.md b/translations/pt-BR/data/reusables/rest-reference/releases/releases.md
new file mode 100644
index 000000000000..ac7b6f76a786
--- /dev/null
+++ b/translations/pt-BR/data/reusables/rest-reference/releases/releases.md
@@ -0,0 +1,5 @@
+{% note %}
+
+**Observação:** A API de versões substitui a API de Downloads. Você pode recuperar a contagem de download e a URL de download do navegador a partir dos pontos de extremidades nesta API que retornam versões e liberam ativos.
+
+{% endnote %}
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/rest-reference/repos/autolinks.md b/translations/pt-BR/data/reusables/rest-reference/repos/autolinks.md
new file mode 100644
index 000000000000..24a54b3541a7
--- /dev/null
+++ b/translations/pt-BR/data/reusables/rest-reference/repos/autolinks.md
@@ -0,0 +1,5 @@
+## Links automáticos
+
+Para ajudar a agilizar o seu fluxo de trabalho, você pode usar a API para adicionar os links automáticos a recursos externos, como problemas do JIRA e tíquetes do Zendesk. Para obter mais informações, consulte "[Configurar links automáticos para fazer referência a recursos externos](/github/administering-a-repository/configuring-autolinks-to-reference-external-resources)".
+
+{% data variables.product.prodname_github_apps %} exige permissões de administração do repositório com acesso de leitura ou gravação para usar a API de links automáticos.
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/rest-reference/repos/contents.md b/translations/pt-BR/data/reusables/rest-reference/repos/contents.md
new file mode 100644
index 000000000000..3a544c880485
--- /dev/null
+++ b/translations/pt-BR/data/reusables/rest-reference/repos/contents.md
@@ -0,0 +1,22 @@
+## Conteúdo
+
+Estes pontos de extremidade da API permitem criar, modificar e excluir conteúdo codificado em Base64 em um repositório. Para solicitar o formato sem processar ou HTML interpretado (quando compatível), use os tipos de mídia personalizados para o conteúdo do repositório.
+
+### Tipos de mídia personalizados para conteúdo do repositório
+
+Os [READMEs](/rest/reference/repos#get-a-repository-readme), [arquivos](/rest/reference/repos#get-repository-content) e [links simbólicos](/rest/reference/repos#get-repository-content) são compatíveis com os seguintes tipos de mídia personalizados:
+
+ application/vnd.github.VERSION.raw
+ application/vnd.github.VERSION.html
+
+Use o tipo de mídia `.raw` para recuperar o conteúdo do arquivo.
+
+Para arquivos de markup, como Markdown ou AsciiDoc, você pode recuperar o HTML interpretado usando o tipo de mídia `.html`. As linguagens de markup são processadas em HTML usando nossa [biblioteca de markup](https://github.com/github/markup) de código aberto.
+
+[Todos os objetos](/rest/reference/repos#get-repository-content) são compatíveis com o seguinte tipo de mídia personalizado:
+
+ application/vnd.github.VERSION.object
+
+Use o parâmetro do tipo de mídia do `objeto` para recuperar o conteúdo em um formato de objeto consistente independentemente do tipo de conteúdo. Por exemplo, em vez de um array de objetos para um diretório, a resposta será um objeto com um atributo de `entrada` contendo o array de objetos.
+
+Você pode ler mais sobre o uso de tipos de mídia na API [aqui](/rest/overview/media-types).
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/rest-reference/repos/forks.md b/translations/pt-BR/data/reusables/rest-reference/repos/forks.md
new file mode 100644
index 000000000000..968bd76f82de
--- /dev/null
+++ b/translations/pt-BR/data/reusables/rest-reference/repos/forks.md
@@ -0,0 +1 @@
+## Bifurcações
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/rest-reference/repos/lfs.md b/translations/pt-BR/data/reusables/rest-reference/repos/lfs.md
new file mode 100644
index 000000000000..5a48e59434d8
--- /dev/null
+++ b/translations/pt-BR/data/reusables/rest-reference/repos/lfs.md
@@ -0,0 +1,2 @@
+
+## Git LFS
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/rest-reference/scim/scim.md b/translations/pt-BR/data/reusables/rest-reference/scim/scim.md
new file mode 100644
index 000000000000..70c7a7009cc9
--- /dev/null
+++ b/translations/pt-BR/data/reusables/rest-reference/scim/scim.md
@@ -0,0 +1,41 @@
+### Provisionamento de SCIM para Organizações
+
+A API do SCIM é usada pelos provedores de identidade (IdPs) habilitados pelo SCIM para automatizar o provisionamento de integrantes da organização de {% data variables.product.product_name %}. A {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API tem por base a versão 2.0 do [Padrão do SCIM](http://www.simplecloud.info/). O ponto de extremidade do SCIM do {% data variables.product.product_name %} que um IdP deve usar é: `{% data variables.product.api_url_code %}/scim/v2/organizations/{org}/`.
+
+{% note %}
+
+**Notas:**
+ - A API do SCIM está disponível apenas para organizações em [{% data variables.product.prodname_ghe_cloud %}](/billing/managing-billing-for-your-github-account/about-billing-for-github-accounts) com o [SAML SSO](/rest/overview/other-authentication-methods#authenticating-for-saml-sso) habilitado. {% data reusables.scim.enterprise-account-scim %} Para obter mais informações sobre o SCIM, consulte "[Sobre o SCIM](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim)".
+ - A API SCIM não pode ser usada com {% data variables.product.prodname_emus %}.
+
+{% endnote %}
+
+### Autenticar chamadas para a API de SCIM
+
+Você deve efetuar a autenticação como dono de uma organização do {% data variables.product.product_name %} para usar sua API do SCIM. A API espera que um token [OAuth 2.0](/developers/apps/authenticating-with-github-apps) seja incluído no cabeçalho da `Autorização`. Você também pode usar um token de acesso pessoal, mas primeiro deve [autorizá-lo para uso com sua organização SAML SSO](/github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on).
+
+### Mapear dados do SAML e SCIM
+
+{% data reusables.scim.nameid-and-username-must-match %}
+
+### Atributos de usuário de SCIM compatíveis
+
+| Nome | Tipo | Descrição |
+| ----------------- | --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `userName` | `string` | O nome de usuário para o usuário. |
+| `name.givenName` | `string` | O primeiro nome do usuário. |
+| `name.familyName` | `string` | O sobrenome do usuário. |
+| `emails` | `array` | Lista de e-mails dos usuários. |
+| `externalId` | `string` | Este identificador é gerado pelo provedor do SAML e é usado como um ID exclusivo pelo provedor do SAML para corresponder ao usuário do GitHub. Você pode encontrar o `externalID` para um usuário no provedor do SAML ou usar a [listar identidades fornecidas pelo ponto de extremidade do SCIM](#list-scim-provisioned-identities) e filtrar outros atributos conhecidos, como, por exemplo, o nome de usuário no GitHub ou endereço de e-mail de usuário. |
+| `id` | `string` | Identificador gerado pelo ponto de extremidade do SCIM do GitHub. |
+| `ativo` | `boolean` | Usado para indicar se a identidade está ativa (verdadeira) ou se deve ser desprovisionada (falso). |
+
+{% note %}
+
+**Observação:** As URLs de Endpoint para a API SCIM são sensíveis a maiúsculas e minúsculas. Por exemplo, a primeira letra no endpoint `Usuários` deve ser maiúscula:
+
+```shell
+GET /scim/v2/organizations/{org}/Users/{scim_user_id}
+```
+
+{% endnote %}
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/rest-reference/search/search.md b/translations/pt-BR/data/reusables/rest-reference/search/search.md
new file mode 100644
index 000000000000..6b27490004d2
--- /dev/null
+++ b/translations/pt-BR/data/reusables/rest-reference/search/search.md
@@ -0,0 +1,144 @@
+A API de pesquisa ajuda a pesquisar o item específico que você deseja encontrar. Por exemplo, você pode encontrar um usuário ou um arquivo específico em um repositório. Pense nisso da mesma forma que você pensa em realizar uma pesquisa no Google. Ele é projetado para ajudá-lo a encontrar o resultado que você está procurando (ou talvez os poucos resultados que você está procurando). Assim como pesquisar no Google, às vezes, você quer ver algumas páginas com resultados de pesquisa para que você possa encontrar o item que melhor atenda às suas necessidades. Para atender a essa necessidade, a API de pesquisa do {% data variables.product.product_name %} fornece **até 1.000 resultados para cada pesquisa**.
+
+Você pode restringir sua pesquisa usando as consultas. Para saber mais sobre a sintaxe de consultas de pesquisa, consulte "[Criar uma consulta de pesquisa](/rest/reference/search#constructing-a-search-query)".
+
+### Resultados da pesquisa de classificação
+
+A menos que outra opção de ordenamento seja fornecida como um parâmetro de consulta, os resultados são ordenados pela melhor correspondência e em ordem decrescente. Vários fatores são combinados para impulsionar o item mais relevante para a parte superior da lista de resultados.
+
+### Limite de taxa
+
+{% data reusables.enterprise.rate_limit %}
+
+A API de pesquisa tem um limite de taxa personalizado. Para solicitações que usam a [Autenticação Básica](/rest#authentication)[OAuth ](/rest#authentication) ou [ID e segredo do cliente e](/rest#increasing-the-unauthenticated-rate-limit-for-oauth-applications), você pode fazer até 30 solicitações por minuto. Para solicitações não autenticadas, o limite de taxa permite que você faça até 10 solicitações por minuto.
+
+Veja a [documentação do limite de taxa](/rest/reference/rate-limit) para obter informações sobre a determinação do seu status atual de limite de taxa.
+
+### Criar uma consulta de pesquisa
+
+Cada ponto de extremidade na API de Pesquisa usa [parâmetros de consulta](https://en.wikipedia.org/wiki/Query_string) para realizar pesquisas no {% data variables.product.product_name %}. Veja o ponto de extremidade individual na API de pesquisa para obter um exemplo que inclui o ponto de extremidade de parâmetros de consulta.
+
+Uma consulta pode conter qualquer combinação de qualificadores de pesquisa compatíveis em {% data variables.product.product_name %}. O formato da consulta de pesquisa é:
+
+```
+SEARCH_KEYWORD_1 SEARCH_KEYWORD_N QUALIFIER_1 QUALIFIER_N
+```
+
+Por exemplo, se você quisesse pesquisar todos os _repositórios_ de propriedade de `defunkt` que continham a palavra `GitHub` e `Octocat` no arquivo README, você usaria a consulta seguinte com o ponto de extremidade _pesquisar repositórios_:
+
+```
+GitHub Octocat in:readme user:defunkt
+```
+
+**Observação:** Certifique-se de usar o codificador HTML preferido do seu idioma para construir suas strings de consulta. Por exemplo:
+```javascript
+// JavaScript
+const queryString = 'q=' + encodeURIComponent('GitHub Octocat in:readme user:defunkt');
+```
+
+Consulte "[Pesquisar no GitHub](/search-github/searching-on-github)" para obter uma lista completa de qualificadores disponíveis, seu formato e um exemplo de como usá-los. Para obter informações sobre como usar operadores para corresponder a quantidades e datas específicas ou para excluir resultados, consulte "[Entender a sintaxe de pesquisa](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax/)".
+
+### Limitações no tamanho da consulta
+
+A API de pesquisa não é compatível com consultas que:
+- têm tamanho superior a 256 caracteres (não incluindo operadores ou qualificadores).
+- têm mais de cinco operadores de `E`, `OU` ou `NÃO` operadores.
+
+Estas consultas de pesquisa irão retornar uma mensagem de erro "Ocorreu uma falha na validação".
+
+### Tempo esgotado e resultados incompletos
+
+Para manter a API de pesquisa rápida para todos, limitamos quanto tempo todas as consulta individual podem ser executadas. Para consultas que [excedem o tempo limite](https://developer.github.com/changes/2014-04-07-understanding-search-results-and-potential-timeouts/), a API retorna as correspondências que já foram encontradas antes do tempo limite, e a resposta tem a propriedade `incomplete_results` definida como `verdadeiro`.
+
+Atingir um tempo limite não significa necessariamente que os resultados da pesquisa estão incompletos. É possível que mais resultados tenham sido, mas também é possível que não.
+
+### Erros de acesso ou resultados de pesquisa ausentes
+
+Você precisa efetuar a autenticação com sucesso e ter acesso aos repositórios nas consultas de pesquisa. Caso contrário, você verá um erro `422 Unprocessable Entry` com uma mensagem "Falha na validação". Por exemplo, sua pesquisa irá falhar se sua consulta incluir qualificadores `repo:`, `user:` ou `org:` que solicitam recursos aos quais você não tem acesso ao efetuar login em {% data variables.product.prodname_dotcom %}.
+
+Quando sua consulta de pesquisa solicitar vários recursos, a resposta só conterá os recursos aos quais você tem acesso e **não** fornecerá uma mensagem de erro listando os recursos que não foram retornados.
+
+Por exemplo, se sua consulta de pesquisa pesquisar os repositórios `octocat/test` e `codertocat/test`, mas você só tem acesso a `octocat/test`, a sua resposta mostrará resultados de pesquisa para `octocat/test` e nenhum resultado para `codertocat/teste`. Este comportamento imita como a pesquisa que funciona no {% data variables.product.prodname_dotcom %}.
+
+### Metadados da correspondência de texto
+
+No GitHub, você pode usar o contexto fornecido por trechos de código e destaques nos resultados de pesquisa. A API de pesquisa oferece metadados adicionais que permitem que você destaque os termos de pesquisa correspondentes ao exibir resultados de busca.
+
+
+
+As solicitações podem optar por receber esses fragmentos de texto na resposta, e cada fragmento é acompanhado de ajustes numéricos que identificam a localização exata de cada termo de pesquisa correspondente.
+
+Para obter esses metadados nos resultados da sua pesquisa, especifique o tipo de mídia de `text-match` no seu cabeçalho `Aceitar`.
+
+```shell
+application/vnd.github.v3.text-match+json
+```
+
+Ao fornecer o tipo de mídia `text-match`, você receberá uma chave extra na carga do JSON denominada `text_matches`, que fornece informações sobre a posição dos seus termos de pesquisa dentro do texto e da `propriedade` que inclui o termo de pesquisa. Dentro do array `text_match`, cada objeto inclui os atributos a seguir:
+
+| Nome | Descrição |
+| ------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `object_url` | A URL para o recurso que contém uma propriedade de string que corresponde a um dos termos de pesquisa. |
+| `object_type` | O nome para o tipo de recurso que existe em determinado `object_url`. |
+| `propriedade` | O nome de uma propriedade do recurso que existe em `object_url`. Esta propriedade é uma string que corresponde a um dos termos de pesquisa. (No JSON retornado a partir de `object_url`, o conteúdo completo do `fragmento` será encontrado na propriedade com este nome.) |
+| `fragmento` | Um subconjunto do valor de `propriedade`. Este é o fragmento de texto que corresponde a um ou mais dos termos de pesquisa. |
+| `matches` | Um array de um ou mais termos de pesquisa que estão presentes no `fragmento`. Os índices (ou seja, "ajustes") são relativos ao fragmento. (Eles não são relativos ao conteúdo _completo_ de `propriedade`.) |
+
+#### Exemplo
+
+Se usarmos cURL e o [exemplo de pesquisa de problemas](#search-issues-and-pull-requests) acima, nossa solicitação de API seria da seguinte forma:
+
+``` shell
+curl -H 'Accept: application/vnd.github.v3.text-match+json' \
+'{% data variables.product.api_url_pre %}/search/issues?q=windows+label:bug+language:python+state:open&sort=created&order=asc'
+```
+
+A resposta incluirá um array `text_matches` para cada resultado de pesquisa. No JSON abaixo, temos dois objetos no array `text_matches`.
+
+A primeira correspondência de texto ocorreu na propriedade do `texto` do problema. Vemos um fragmento de texto a partir do texto do problema. O termo da pesquisa (`windows`) aparece duas vezes dentro desse fragmento, e temos os índices para cada ocorrência.
+
+A segunda correspondência de texto ocorreu na propriedade do `texto` de um dos comentários do problema. Nós temos a URL do comentário do problema. E, evidentemente, vemos um fragmento de texto do comentário. O termo de pesquisa (`windows`) aparece uma vez dentro desse fragmento.
+
+```json
+{
+ "text_matches": [
+ {
+ "object_url": "https://api.github.com/repositories/215335/issues/132",
+ "object_type": "Issue",
+ "property": "body",
+ "fragment": "comprehensive windows font I know of).\n\nIf we can find a commonly distributed windows font that supports them then no problem (we can use html font tags) but otherwise the '(21)' style is probably better.\n",
+ "matches": [
+ {
+ "text": "windows",
+ "indices": [
+ 14,
+ 21
+ ]
+ },
+ {
+ "text": "windows",
+ "indices": [
+ 78,
+ 85
+ ]
+ }
+ ]
+ },
+ {
+ "object_url": "https://api.github.com/repositories/215335/issues/comments/25688",
+ "object_type": "IssueComment",
+ "property": "body",
+ "fragment": " right after that are a bit broken IMHO :). I suppose we could have some hack that maxes out at whatever the font does...\n\nI'll check what the state of play is on Windows.\n",
+ "matches": [
+ {
+ "text": "Windows",
+ "indices": [
+ 163,
+ 170
+ ]
+ }
+ ]
+ }
+ ]
+}
+```
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/rest-reference/secret-scanning/secret-scanning.md b/translations/pt-BR/data/reusables/rest-reference/secret-scanning/secret-scanning.md
new file mode 100644
index 000000000000..349fc600332f
--- /dev/null
+++ b/translations/pt-BR/data/reusables/rest-reference/secret-scanning/secret-scanning.md
@@ -0,0 +1,9 @@
+{% data reusables.secret-scanning.api-beta %}
+
+A API de {% data variables.product.prodname_secret_scanning %} permite que você{% ifversion fpt or ghec or ghes > 3.1 or ghae %}:
+
+- Habilitar ou desabilitar {% data variables.product.prodname_secret_scanning %} para um repositório. Para obter mais informações, consulte "[Repositórios](/rest/reference/repos#update-a-repository)" na documentação da API REST.
+- Recuperar e atualizar alertas de {% data variables.product.prodname_secret_scanning %} a partir de um repositório {% ifversion fpt or ghec %}privado {% endif %}. Para obter detalhes adicionais, consulte as seções abaixo.
+{%- else %} recuperar e atualizar alertas de {% data variables.product.prodname_secret_scanning %} a partir de um repositório {% ifversion fpt or ghec %}privado{% endif %}.{% endif %}
+
+Para obter mais informações sobre {% data variables.product.prodname_secret_scanning %}, consulte "[Sobre {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/about-secret-scanning)."
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/rest-reference/teams/discussion-comments.md b/translations/pt-BR/data/reusables/rest-reference/teams/discussion-comments.md
new file mode 100644
index 000000000000..8b7f610392a0
--- /dev/null
+++ b/translations/pt-BR/data/reusables/rest-reference/teams/discussion-comments.md
@@ -0,0 +1,3 @@
+## Comentários da discussão
+
+A API de comentários de discussão em equipe permite que você obtenha, crie, edite e exclua comentários de discussão em um post de [discussão de equipe](/rest/reference/teams#discussions). Qualquer integrante da organização da [organização](/rest/reference/orgs) da equipe pode criar e ler comentários em uma discussão pública. Para obter mais informações, consulte "[Sobre discussões de equipe](/organizations/collaborating-with-your-team/about-team-discussions/)". Esta API só está disponível para os integrantes autenticados da organização da equipe.
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/rest-reference/teams/discussions.md b/translations/pt-BR/data/reusables/rest-reference/teams/discussions.md
new file mode 100644
index 000000000000..d5480af797a8
--- /dev/null
+++ b/translations/pt-BR/data/reusables/rest-reference/teams/discussions.md
@@ -0,0 +1,3 @@
+## Discussions
+
+A API de discussões de equipe permite que você obtenha, crie, edite e exclua postagens de discussão na página de uma equipe. Você pode usar discussões da equipe para ter conversas que não são específicas para um repositório ou projeto. Qualquer integrante da [organização](/rest/reference/orgs) da equipe pode criar e ler posts de discussão públicos. Para obter mais informações, consulte "[Sobre discussões de equipe](//organizations/collaborating-with-your-team/about-team-discussions/)". Para aprender mais sobre comentários em uma publicação de discussão, consulte [a API de comentários de discussão em equipe](/rest/reference/teams#discussion-comments). Esta API só está disponível para os integrantes autenticados da organização da equipe.
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/rest-reference/teams/external-groups.md b/translations/pt-BR/data/reusables/rest-reference/teams/external-groups.md
new file mode 100644
index 000000000000..9d252fceeb63
--- /dev/null
+++ b/translations/pt-BR/data/reusables/rest-reference/teams/external-groups.md
@@ -0,0 +1,16 @@
+## Grupos externos
+
+A API de grupos externos permite que você visualize os grupos de provedores de identidade externos que estão disponíveis para sua organização e gerencie a conexão entre grupos externos e equipes na sua organização.
+
+Para usar esta API, o usuário autenticado deve ser um mantenedor de equipe ou um proprietário da organização associada à equipe.
+
+{% ifversion ghec %}
+{% note %}
+
+**Notas:**
+
+- A API de grupos externos está disponível apenas para organizações que fazem parte de uma empresa que usa {% data variables.product.prodname_emus %}. Para obter mais informações, consulte[Sobre usuários gerenciados pela empresa](/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)".
+- Se sua organização usar a sincronização de equipe, você poderá usar a API de sincronização de equipe. Para obter mais informações, consulte "[API de sincronização de equipe](#team-synchronization)".
+
+{% endnote %}
+{% endif %}
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/rest-reference/teams/members.md b/translations/pt-BR/data/reusables/rest-reference/teams/members.md
new file mode 100644
index 000000000000..36a45d0857fe
--- /dev/null
+++ b/translations/pt-BR/data/reusables/rest-reference/teams/members.md
@@ -0,0 +1,12 @@
+## Integrantes
+
+Esta API só está disponível para os integrantes autenticados da organização da equipe. Os tokens de acesso do OAuth exigem o escopo `read:org` [](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/).
+
+{% ifversion fpt or ghes or ghec %}
+{% note %}
+
+**Observação:** Quando você tiver configurado a sincronização da equipe para uma equipe com o provedor de identidade (IdP) da sua organização, você receberá uma mensagem de erro se tentar usar a API para fazer alterações na associação da equipe. Se você tiver acesso para administrar a associação do grupo em seu IdP, você pode administrar a associação da equipe do GitHub através do seu provedor de identidade, que adiciona e remove automaticamente os integrantes da equipe em uma organização. Para obter mais informações, consulte "Sincronizar equipes entre seu provedor de identidade e o GitHub".
+
+{% endnote %}
+
+{% endif %}
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/rest-reference/teams/team-sync.md b/translations/pt-BR/data/reusables/rest-reference/teams/team-sync.md
new file mode 100644
index 000000000000..0563f24290b2
--- /dev/null
+++ b/translations/pt-BR/data/reusables/rest-reference/teams/team-sync.md
@@ -0,0 +1,11 @@
+## Sincronização de equipes
+
+A API de Sincronização da Equipe permite que você gerencie as conexões entre equipes de {% data variables.product.product_name %} e grupos de provedor de identidade externo (IdP). Para usar esta API, o usuário autenticado deve ser um mantenedor de equipe ou um proprietário da organização associada à equipe. O token que você usa para efetuar a autenticação também deverá ser autorizado para uso com o provedor de IdP (SSO). Para obter mais informações, consulte "Autorizando um token de acesso pessoal para uso com uma organização de logon único SAML".
+
+Você pode gerenciar os integrantes da equipe do GitHub através do seu IdP com a sincronização de equipe. A sincronização de equipe deve estar habilitada para usar a API de sincronização de equipe. Para obter mais informações, consulte "Sincronizar equipes entre seu provedor de identidade e o GitHub".
+
+{% note %}
+
+**Observação:** A API de sincronização de equipe não pode ser usada com {% data variables.product.prodname_emus %}. Para saber mais sobre como gerenciar um {% data variables.product.prodname_emu_org %}, consulte "[API de grupos externos](/enterprise-cloud@latest/rest/reference/teams#external-groups)".
+
+{% endnote %}
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/rest-reference/teams/teams.md b/translations/pt-BR/data/reusables/rest-reference/teams/teams.md
new file mode 100644
index 000000000000..0285f3e62e15
--- /dev/null
+++ b/translations/pt-BR/data/reusables/rest-reference/teams/teams.md
@@ -0,0 +1 @@
+Esta API só está disponível para os integrantes autenticados da [organização](/rest/reference/orgs) da equipe. Os tokens de acesso do OAuth exigem o escopo `read:org` [](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/). {% data variables.product.prodname_dotcom %} gera o `slug` da equipe a partir do `nome` da equipe.
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/rest-reference/users/blocking.md b/translations/pt-BR/data/reusables/rest-reference/users/blocking.md
new file mode 100644
index 000000000000..a68a52766128
--- /dev/null
+++ b/translations/pt-BR/data/reusables/rest-reference/users/blocking.md
@@ -0,0 +1 @@
+## Bloquear usuários
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/rest-reference/users/emails.md b/translations/pt-BR/data/reusables/rest-reference/users/emails.md
new file mode 100644
index 000000000000..7a219753a6aa
--- /dev/null
+++ b/translations/pt-BR/data/reusables/rest-reference/users/emails.md
@@ -0,0 +1,3 @@
+## E-mails
+
+O gerenciamento de endereços de e-mail através da API requer que você efetue a autenticação por meio de autenticação básica, ou através do OAuth com um escopo correto para o ponto de extremidade.
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/rest-reference/users/followers.md b/translations/pt-BR/data/reusables/rest-reference/users/followers.md
new file mode 100644
index 000000000000..8a7cd6a06703
--- /dev/null
+++ b/translations/pt-BR/data/reusables/rest-reference/users/followers.md
@@ -0,0 +1 @@
+## Seguidores
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/rest-reference/users/gpg-keys.md b/translations/pt-BR/data/reusables/rest-reference/users/gpg-keys.md
new file mode 100644
index 000000000000..dcae34fd167e
--- /dev/null
+++ b/translations/pt-BR/data/reusables/rest-reference/users/gpg-keys.md
@@ -0,0 +1,3 @@
+## Chaves GPG
+
+Os dados retornados no campo de resposta `public_key` não são uma chave com formato GPG. Quando um usuário faz o upload de uma chave GPG, ela é analisada e a chave pública criptográfica é extraída e armazenada. Essa chave criptográfica é o que é retornado pelas APIs nesta página. Esta chave não é adequada para ser usada diretamente por programas como o GPG.
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/rest-reference/users/keys.md b/translations/pt-BR/data/reusables/rest-reference/users/keys.md
new file mode 100644
index 000000000000..e18e1127121f
--- /dev/null
+++ b/translations/pt-BR/data/reusables/rest-reference/users/keys.md
@@ -0,0 +1 @@
+## Chaves SSH do Git
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/rest-reference/users/users.md b/translations/pt-BR/data/reusables/rest-reference/users/users.md
new file mode 100644
index 000000000000..860da9105c57
--- /dev/null
+++ b/translations/pt-BR/data/reusables/rest-reference/users/users.md
@@ -0,0 +1 @@
+Muitos dos recursos na API de usuários fornecem um atalho para obter informações sobre o usuário autenticado atualmente. Se uma URL de solicitação não incluir um parâmetro `{username}`, a resposta será para o usuário conectado (e você deve passar [informações de autenticação](/rest/overview/resources-in-the-rest-api#authentication) com sua solicitação).{% ifversion fpt or ghes or ghec %} Informações privadas adicionais, como se um usuário tem autenticação de dois fatores habilitada, estão incluídas quando a autenticação é efetuada por meio da autenticação básica ou OAuth com o escopo do `usuário` .{% endif %}
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/rest-reference/webhooks/repo-config.md b/translations/pt-BR/data/reusables/rest-reference/webhooks/repo-config.md
new file mode 100644
index 000000000000..2841871ead76
--- /dev/null
+++ b/translations/pt-BR/data/reusables/rest-reference/webhooks/repo-config.md
@@ -0,0 +1 @@
+## Configuração de webhook do repositório
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/rest-reference/webhooks/repo-deliveries.md b/translations/pt-BR/data/reusables/rest-reference/webhooks/repo-deliveries.md
new file mode 100644
index 000000000000..105c4128bc5b
--- /dev/null
+++ b/translations/pt-BR/data/reusables/rest-reference/webhooks/repo-deliveries.md
@@ -0,0 +1 @@
+## Entregas do webhook do repositório
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/rest-reference/webhooks/repos.md b/translations/pt-BR/data/reusables/rest-reference/webhooks/repos.md
new file mode 100644
index 000000000000..b0ac909198c0
--- /dev/null
+++ b/translations/pt-BR/data/reusables/rest-reference/webhooks/repos.md
@@ -0,0 +1 @@
+## Webhooks do repositório
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/rest-reference/webhooks/webhooks.md b/translations/pt-BR/data/reusables/rest-reference/webhooks/webhooks.md
new file mode 100644
index 000000000000..2e0f5ce0a0bc
--- /dev/null
+++ b/translations/pt-BR/data/reusables/rest-reference/webhooks/webhooks.md
@@ -0,0 +1,58 @@
+Os webhooks de repositório permitem que você receba cargas de `POST` de HTTP sempre que certos eventos ocorrerem em um repositório. {% data reusables.webhooks.webhooks-rest-api-links %}
+
+Se você deseja configurar um único webhook para receber eventos de todos os repositórios da organização, consulte nossa documentação de API para [Webhooks de organização](/rest/reference/orgs#webhooks).
+
+Além da API REST, {% data variables.product.prodname_dotcom %} também pode servir como um núcleo de [PubSubHubbub](#pubsubhubbub) para repositórios.
+
+## Receber Webhooks
+
+Para que {% data variables.product.product_name %} envie cargas de webhook, seu servidor deve ser acessível pela internet. É altamente recomendável o uso de SSL para que possamos enviar cargas criptografadas por HTTPS.
+
+### Cabeçalhos de webhook
+
+{% data variables.product.product_name %} enviará ao longo de vários cabeçalhos de HTTP para diferenciar entre tipos de evento e identificadores de carga. Consulte [cabeçalhos de webhook](/developers/webhooks-and-events/webhook-events-and-payloads#delivery-headers) para obter informações.
+
+## PubSubHubbub
+
+O GitHub também pode servir como um centro de [PubSubHubbub](https://github.com/pubsubhubbub/PubSubHubbub) para todos os repositórios. O PSHB é um simples protocolo de publicação/assinatura que permite o registro de servidores para receber atualizações quando um tópico é atualizado. As atualizações são enviadas com uma solicitação HTTP do tipo POST para uma URL de chamada de retorno. As URLs dos tópicos dos pushes de um repositório do GitHub estão neste formato:
+
+`https://github.com/{owner}/{repo}/events/{event}`
+
+O evento pode ser qualquer evento de webhook disponível. Para obter mais informações, consulte "[Eventos e cargas de Webhook](/developers/webhooks-and-events/webhook-events-and-payloads)".
+
+### Formato de resposta
+
+O formato padrão é o que [os hooks post-receive existentes devem esperar](/post-receive-hooks/): Um texto JSON enviado como parâmetro `payload` em um POST. Você também pode especificar para receber o texto do JSON sem processar com um cabeçalho `Aceitar` ou uma extensão `.json`.
+
+ Accept: application/json
+ https://github.com/{owner}/{repo}/events/push.json
+
+### URLs de chamada de retorno
+
+As URLs de chamada de retorno podem usar o protocolo `http://`.
+
+ # Send updates to postbin.org
+ http://postbin.org/123
+
+### Assinar
+
+O ponto de extremidade do GitHub PubSubHubbub é: `{% data variables.product.api_url_code %}/hub`. Uma solicitação bem-sucedida com o curl parece como:
+
+``` shell
+curl -u "user" -i \
+ {% data variables.product.api_url_pre %}/hub \
+ -F "hub.mode=subscribe" \
+ -F "hub.topic=https://github.com/{owner}/{repo}/events/push" \
+ -F "hub.callback=http://postbin.org/123"
+```
+
+Solicitações do PubSubHubbub podem ser enviadas várias vezes. Se o hook já existe, ele será modificado de acordo com a solicitação.
+
+#### Parâmetros
+
+| Nome | Tipo | Descrição |
+| -------------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `hub.mode` | `string` | **Obrigatório**. `Assine` ou `cancele a assinatura`. |
+| `hub.topic` | `string` | **Obrigatório**. A URI do repositório do GitHub a ser assinada. O caminho deve estar no formato `/{owner}/{repo}/events/{event}`. |
+| `hub.callback` | `string` | A URI para receber as atualizações do tópico. |
+| `hub.secret` | `string` | Uma chave de segredo compartilhado que gera uma assinatura de hash do conteúdo de saída do texto. Você pode verificar se um push veio do GitHub comparando o texto da solicitação sem processar com o conteúdo dos cabeçalho do {% ifversion fpt or ghes > 2.22 or ghec %}`X-Hub-Signature` ou `X-Hub-Signature-256` {% elsif ghes < 3.0 %}`X-Hub-Signature` {% elsif ghae %}cabeçalho `X-Hub-Signature-256` {% endif %}. Você pode ver [a documentação do PubSubHubbub](https://pubsubhubbub.github.io/PubSubHubbub/pubsubhubbub-core-0.4.html#authednotify) para obter mais informações. |
\ No newline at end of file
diff --git a/translations/pt-BR/data/ui.yml b/translations/pt-BR/data/ui.yml
index f42403c91964..7b090c64eda3 100644
--- a/translations/pt-BR/data/ui.yml
+++ b/translations/pt-BR/data/ui.yml
@@ -1,4 +1,6 @@
---
+meta:
+ default_description: Get started, troubleshoot, and make the most of GitHub. Documentation for new users, developers, administrators, and all of GitHub's products.
header:
github_docs: GitHub Docs
contact: Contato
@@ -92,6 +94,7 @@ products:
deprecation_notice: Aviso de descontinuação
rest:
reference:
+ notes: Observações
parameters: Parâmetros
response: Resposta
code_sample: Amostra de código
@@ -101,6 +104,7 @@ products:
see_preview_notice: Ver aviso de pré-visualização
see_preview_notices: Ver avisos de pré-visualização
preview_header_is_required: Este cabeçalho é obrigatório
+ works_with_github_apps: Works with GitHub Apps
footer:
all_rights_reserved: Todos os direitos reservados
terms: Termos
diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-security-and-analysis-settings-for-your-user-account.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-security-and-analysis-settings-for-your-user-account.md
index 83b947aef99b..2fd6ceee7cd7 100644
--- a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-security-and-analysis-settings-for-your-user-account.md
+++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-security-and-analysis-settings-for-your-user-account.md
@@ -19,7 +19,7 @@ shortTitle: 管理安全和分析
您仍然可以管理单个仓库的安全和分析功能。 更多信息请参阅“[管理仓库的安全和分析设置](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)”。
-You can also review the security log for all activity on your user account. 更多信息请参阅“[查看安全日志](/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log)”。
+您还可以查看用户帐户上所有活动的安全日志。 更多信息请参阅“[查看安全日志](/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log)”。
{% data reusables.security.some-security-and-analysis-features-are-enabled-by-default %}
@@ -33,7 +33,7 @@ You can also review the security log for all activity on your user account. 更
{% data reusables.user-settings.security-analysis %}
3. 在“Configure security and analysis features（配置安全性和分析功能）”下，单击功能右侧的 **Disable all（全部禁用）**或 **Enable all（全部启用）**。
{% ifversion ghes > 3.2 %}{% else %}{% endif %}
-6. Optionally, enable the feature by default for new repositories that you own.
+6. （可选）默认情况下为您拥有的新存储库启用该功能。
{% ifversion ghes > 3.2 %}{% else %}{% endif %}
7. 单击 **Disable FEATURE（禁用功能）**或 **Enable FEATURE（启用功能）**以禁用或启用您拥有的所有仓库的功能。
{% ifversion ghes > 3.2 %}{% else %}{% endif %}
@@ -44,7 +44,7 @@ You can also review the security log for all activity on your user account. 更
{% data reusables.user-settings.access_settings %}
{% data reusables.user-settings.security-analysis %}
-3. Under "Configure security and analysis features", to the right of the feature, enable or disable the feature by default for new repositories that you own.
+3. 在“Configure security and analysis features（配置安全和分析功能）”下，在功能右侧，默认为您拥有的新存储库启用或禁用该功能。
{% ifversion ghes > 3.2 %}{% else %}{% endif %}
## 延伸阅读
diff --git a/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-java-with-ant.md b/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-java-with-ant.md
index 9d735c7c5a3e..1ce2228c191a 100644
--- a/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-java-with-ant.md
+++ b/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-java-with-ant.md
@@ -78,9 +78,9 @@ jobs:
The default starter workflows are excellent starting points when creating your build and test workflow, and you can customize the starter workflow to suit your project’s needs.
-{% data reusables.github-actions.example-github-runner %}
+{% data reusables.actions.example-github-runner %}
-{% data reusables.github-actions.java-jvm-architecture %}
+{% data reusables.actions.java-jvm-architecture %}
## 构建和测试代码
diff --git a/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-java-with-gradle.md b/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-java-with-gradle.md
index 15b7173f8f4d..eb63dc902dfb 100644
--- a/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-java-with-gradle.md
+++ b/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-java-with-gradle.md
@@ -83,9 +83,9 @@ jobs:
The default starter workflows are excellent starting points when creating your build and test workflow, and you can customize the starter workflow to suit your project’s needs.
-{% data reusables.github-actions.example-github-runner %}
+{% data reusables.actions.example-github-runner %}
-{% data reusables.github-actions.java-jvm-architecture %}
+{% data reusables.actions.java-jvm-architecture %}
## 构建和测试代码
diff --git a/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-java-with-maven.md b/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-java-with-maven.md
index 0d05bba37ac4..f5b6c1f7bacf 100644
--- a/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-java-with-maven.md
+++ b/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-java-with-maven.md
@@ -78,9 +78,9 @@ jobs:
The default starter workflows are excellent starting points when creating your build and test workflow, and you can customize the starter workflow to suit your project’s needs.
-{% data reusables.github-actions.example-github-runner %}
+{% data reusables.actions.example-github-runner %}
-{% data reusables.github-actions.java-jvm-architecture %}
+{% data reusables.actions.java-jvm-architecture %}
## 构建和测试代码
diff --git a/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-nodejs.md b/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-nodejs.md
index ba85b448bf6e..e95ee8666cc6 100644
--- a/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-nodejs.md
+++ b/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-nodejs.md
@@ -73,7 +73,7 @@ jobs:
```
{% endraw %}
-{% data reusables.github-actions.example-github-runner %}
+{% data reusables.actions.example-github-runner %}
## 指定 Node.js 版本
@@ -204,7 +204,7 @@ steps:
### 使用私有注册表并创建 .npmrc 文件的示例
-{% data reusables.github-actions.setup-node-intro %}
+{% data reusables.actions.setup-node-intro %}
要验证您的私有注册表，需要将 npm 身份验证令牌存储为密码。 例如，创建名为 `NPM_TOKEN` 的仓库密码。 更多信息请参阅“[创建和使用加密密码](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)”。
diff --git a/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-xamarin-applications.md b/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-xamarin-applications.md
index c4cfb2eafa2b..034318469d96 100644
--- a/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-xamarin-applications.md
+++ b/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-xamarin-applications.md
@@ -31,7 +31,7 @@ shortTitle: 构建和测试 Xamarin 应用程序
* [macOS 10.15](https://github.com/actions/virtual-environments/blob/main/images/macos/macos-10.15-Readme.md#xamarin-bundles)
* [macOS 11](https://github.com/actions/virtual-environments/blob/main/images/macos/macos-11-Readme.md#xamarin-bundles)
-{% data reusables.github-actions.macos-runner-preview %}
+{% data reusables.actions.macos-runner-preview %}
## 基本要求
diff --git a/translations/zh-CN/content/actions/creating-actions/about-custom-actions.md b/translations/zh-CN/content/actions/creating-actions/about-custom-actions.md
index 7723f4542e98..598d6034b045 100644
--- a/translations/zh-CN/content/actions/creating-actions/about-custom-actions.md
+++ b/translations/zh-CN/content/actions/creating-actions/about-custom-actions.md
@@ -47,13 +47,13 @@ Docker 容器使用 {% data variables.product.prodname_actions %} 代码封装
Docker 容器允许使用特定版本的操作系统、依赖项、工具和代码。 对于必须在特定环境配置中运行的操作，Docker 是一个理想的选择，因为您可以自定义操作系统和工具。 由于创建和检索容器的延时，Docker 容器操作慢于 JavaScript 操作。
-Docker 容器操作只能在使用 Linux 操作系统的运行器上执行。 {% data reusables.github-actions.self-hosted-runner-reqs-docker %}
+Docker 容器操作只能在使用 Linux 操作系统的运行器上执行。 {% data reusables.actions.self-hosted-runner-reqs-docker %}
### JavaScript 操作
JavaScript 操作可以直接在运行器计算机上运行，并将操作代码与用于运行代码的环境分开。 使用 JavaScript 操作可简化操作代码，执行速度快于 Docker 容器操作。
-{% data reusables.github-actions.pure-javascript %}
+{% data reusables.actions.pure-javascript %}
如果您正在开发 Node.js 项目，{% data variables.product.prodname_actions %} 工具包提供可用于项目中加速开发的软件包。 更多信息请参阅 [actions/toolkit](https://github.com/actions/toolkit) 仓库。
diff --git a/translations/zh-CN/content/actions/creating-actions/creating-a-composite-action.md b/translations/zh-CN/content/actions/creating-actions/creating-a-composite-action.md
index 256bb3fe4167..0396f68729b5 100644
--- a/translations/zh-CN/content/actions/creating-actions/creating-a-composite-action.md
+++ b/translations/zh-CN/content/actions/creating-actions/creating-a-composite-action.md
@@ -23,7 +23,7 @@ In this guide, you'll learn about the basic components needed to create and use
Once you complete this project, you should understand how to build your own composite action and test it in a workflow.
-{% data reusables.github-actions.context-injection-warning %}
+{% data reusables.actions.context-injection-warning %}
## 基本要求
diff --git a/translations/zh-CN/content/actions/creating-actions/creating-a-docker-container-action.md b/translations/zh-CN/content/actions/creating-actions/creating-a-docker-container-action.md
index 5fabeae91b20..7d5ef502c61b 100644
--- a/translations/zh-CN/content/actions/creating-actions/creating-a-docker-container-action.md
+++ b/translations/zh-CN/content/actions/creating-actions/creating-a-docker-container-action.md
@@ -27,9 +27,9 @@ shortTitle: Docker 容器操作
完成此项目后，您应了解如何构建自己的 Docker 容器操作和在工作流程测试该操作。
-{% data reusables.github-actions.self-hosted-runner-reqs-docker %}
+{% data reusables.actions.self-hosted-runner-reqs-docker %}
-{% data reusables.github-actions.context-injection-warning %}
+{% data reusables.actions.context-injection-warning %}
## 基本要求
diff --git a/translations/zh-CN/content/actions/creating-actions/creating-a-javascript-action.md b/translations/zh-CN/content/actions/creating-actions/creating-a-javascript-action.md
index e25ab3e0d1c0..edf4c0b6861b 100644
--- a/translations/zh-CN/content/actions/creating-actions/creating-a-javascript-action.md
+++ b/translations/zh-CN/content/actions/creating-actions/creating-a-javascript-action.md
@@ -29,9 +29,9 @@ shortTitle: JavaScript 操作
完成此项目后，您应了解如何构建自己的 JavaScript 操作和在工作流程测试该操作。
-{% data reusables.github-actions.pure-javascript %}
+{% data reusables.actions.pure-javascript %}
-{% data reusables.github-actions.context-injection-warning %}
+{% data reusables.actions.context-injection-warning %}
## 基本要求
diff --git a/translations/zh-CN/content/actions/creating-actions/dockerfile-support-for-github-actions.md b/translations/zh-CN/content/actions/creating-actions/dockerfile-support-for-github-actions.md
index 2e70f1799dbb..4fede1c2ce9c 100644
--- a/translations/zh-CN/content/actions/creating-actions/dockerfile-support-for-github-actions.md
+++ b/translations/zh-CN/content/actions/creating-actions/dockerfile-support-for-github-actions.md
@@ -105,7 +105,7 @@ Error response from daemon: OCI runtime create failed: container_linux.go:348: s
如果在 `Dockerfile` 中使用 `CMD`，请遵循以下指导方针：
-{% data reusables.github-actions.dockerfile-guidelines %}
+{% data reusables.actions.dockerfile-guidelines %}
## 支持的 Linux 功能
diff --git a/translations/zh-CN/content/actions/creating-actions/metadata-syntax-for-github-actions.md b/translations/zh-CN/content/actions/creating-actions/metadata-syntax-for-github-actions.md
index 886eb87718dc..7b5099989bfe 100644
--- a/translations/zh-CN/content/actions/creating-actions/metadata-syntax-for-github-actions.md
+++ b/translations/zh-CN/content/actions/creating-actions/metadata-syntax-for-github-actions.md
@@ -350,7 +350,7 @@ runs:
**可选** 您可以使用 `if` 条件使步骤仅在满足条件时才运行。 您可以使用任何支持上下文和表达式来创建条件。
-{% data reusables.github-actions.expression-syntax-if %} For more information, see "[Expressions](/actions/learn-github-actions/expressions)."
+{% data reusables.actions.expression-syntax-if %} For more information, see "[Expressions](/actions/learn-github-actions/expressions)."
**示例：使用上下文**
@@ -578,7 +578,7 @@ runs:
`args` 用来代替 `Dockerfile` 中的 `CMD` 指令。 如果在 `Dockerfile` 中使用 `CMD`，请遵循按偏好顺序排序的指导方针：
-{% data reusables.github-actions.dockerfile-guidelines %}
+{% data reusables.actions.dockerfile-guidelines %}
如果需要将环境变量传递到操作中，请确保操作运行命令 shell 以执行变量替换。 例如，如果 `entrypoint` 属性设置为 `"sh -c"`，`args` 将在命令 shell 中运行。 或者，如果 `Dockerfile` 使用 `ENTRYPOINT` 运行同一命令 (`"sh -c"`)，`args` 将在命令 shell 中执行。
diff --git a/translations/zh-CN/content/actions/deployment/targeting-different-environments/using-environments-for-deployment.md b/translations/zh-CN/content/actions/deployment/targeting-different-environments/using-environments-for-deployment.md
index 88a9e1c5ffd1..387ef721bf20 100644
--- a/translations/zh-CN/content/actions/deployment/targeting-different-environments/using-environments-for-deployment.md
+++ b/translations/zh-CN/content/actions/deployment/targeting-different-environments/using-environments-for-deployment.md
@@ -27,7 +27,7 @@ Environments are used to describe a general deployment target like `production`,
**Note:** You can only configure environments for public repositories. 如果您将仓库从公开转换为私密，任何配置的保护规则或环境机密将被忽略， 并且您将无法配置任何环境。 如果将仓库转换回公共，您将有权访问以前配置的任何保护规则和环境机密。
-Organizations that use {% data variables.product.prodname_ghe_cloud %} can configure environments for private repositories. For more information, see the [{% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/actions/deployment/targeting-different-environments/using-environments-for-deployment). {% data reusables.enterprise.link-to-ghec-trial %}
+Organizations that use {% data variables.product.prodname_ghe_cloud %} can configure environments for private repositories. 更多信息请参阅 [{% data variables.product.prodname_ghe_cloud %} 文档](/enterprise-cloud@latest/actions/deployment/targeting-different-environments/using-environments-for-deployment)。 {% data reusables.enterprise.link-to-ghec-trial %}
{% endnote %}
{% endif %}
@@ -69,13 +69,13 @@ Organizations that use {% data variables.product.prodname_ghe_cloud %} can confi
## 创建环境
-{% data reusables.github-actions.permissions-statement-environment %}
+{% data reusables.actions.permissions-statement-environment %}
{% data reusables.repositories.navigate-to-repo %}
{% data reusables.repositories.sidebar-settings %}
-{% data reusables.github-actions.sidebar-environment %}
-{% data reusables.github-actions.new-environment %}
-{% data reusables.github-actions.name-environment %}
+{% data reusables.actions.sidebar-environment %}
+{% data reusables.actions.new-environment %}
+{% data reusables.actions.name-environment %}
1. Optionally, specify people or teams that must approve workflow jobs that use this environment.
1. Select **Required reviewers**.
1. Enter up to 6 people or teams. 只有一个必需的审查者需要批准该作业才能继续。
@@ -107,13 +107,13 @@ Organizations that use {% data variables.product.prodname_ghe_cloud %} can confi
## 删除环境
-{% data reusables.github-actions.permissions-statement-environment %}
+{% data reusables.actions.permissions-statement-environment %}
删除环境将删除与环境关联的所有机密和保护规则。 由于已删除环境的保护规则而正在等待的任何作业将自动失败。
{% data reusables.repositories.navigate-to-repo %}
{% data reusables.repositories.sidebar-settings %}
-{% data reusables.github-actions.sidebar-environment %}
+{% data reusables.actions.sidebar-environment %}
1. 在要删除的环境旁边，单击 {% octicon "trash" aria-label="The trash icon" %}。
2. 单击 **I understand, delete this environment（我了解，删除此环境）**。
diff --git a/translations/zh-CN/content/actions/hosting-your-own-runners/about-self-hosted-runners.md b/translations/zh-CN/content/actions/hosting-your-own-runners/about-self-hosted-runners.md
index d2d43e503959..31c4aee2284f 100644
--- a/translations/zh-CN/content/actions/hosting-your-own-runners/about-self-hosted-runners.md
+++ b/translations/zh-CN/content/actions/hosting-your-own-runners/about-self-hosted-runners.md
@@ -18,25 +18,25 @@ type: overview
## About self-hosted runners
-{% data reusables.github-actions.self-hosted-runner-description %} Self-hosted runners can be physical, virtual, in a container, on-premises, or in a cloud.
+{% data reusables.actions.self-hosted-runner-description %} Self-hosted runners can be physical, virtual, in a container, on-premises, or in a cloud.
You can add self-hosted runners at various levels in the management hierarchy:
- Repository-level runners are dedicated to a single repository.
- Organization-level runners can process jobs for multiple repositories in an organization.
- Enterprise-level runners can be assigned to multiple organizations in an enterprise account.
-Your runner machine connects to {% data variables.product.product_name %} using the {% data variables.product.prodname_actions %} self-hosted runner application. {% data reusables.github-actions.runner-app-open-source %} When a new version is released, the runner application automatically updates itself when a job is assigned to the runner, or within a week of release if the runner hasn't been assigned any jobs.
+Your runner machine connects to {% data variables.product.product_name %} using the {% data variables.product.prodname_actions %} self-hosted runner application. {% data reusables.actions.runner-app-open-source %} When a new version is released, the runner application automatically updates itself when a job is assigned to the runner, or within a week of release if the runner hasn't been assigned any jobs.
-{% data reusables.github-actions.self-hosted-runner-auto-removal %}
+{% data reusables.actions.self-hosted-runner-auto-removal %}
For more information about installing and using self-hosted runners, see "[Adding self-hosted runners](/github/automating-your-workflow-with-github-actions/adding-self-hosted-runners)" and "[Using self-hosted runners in a workflow](/github/automating-your-workflow-with-github-actions/using-self-hosted-runners-in-a-workflow)."
-## {% ifversion fpt or ghes %}Differences between {% data variables.product.prodname_dotcom %}-hosted and {% elsif ghae %}Characteristics of {% endif %}self-hosted runners
+## {% ifversion fpt or ghec or ghes %}Differences between {% data variables.product.prodname_dotcom %}-hosted and {% elsif ghae %}Characteristics of {% endif %}self-hosted runners
-{% ifversion fpt or ghes %}
+{% ifversion fpt or ghec or ghes %}
{% data variables.product.prodname_dotcom %}-hosted runners offer a quicker, simpler way to run your workflows, while self-hosted{% elsif ghae %}Self-hosted{% endif %} runners are a highly configurable way to run workflows in your own custom environment. {% ifversion ghae %}Self-hosted runners:{% endif %}
-{% ifversion fpt or ghes %}
+{% ifversion fpt or ghec or ghes %}
**{% data variables.product.prodname_dotcom %}-hosted runners:**
- Receive automatic updates for the operating system, preinstalled packages and tools, and the self-hosted runner application.
- Are managed and maintained by {% data variables.product.prodname_dotcom %}.
@@ -70,15 +70,15 @@ You can automatically increase or decrease the number of self-hosted runners in
There are some limits on {% data variables.product.prodname_actions %} usage when using self-hosted runners. These limits are subject to change.
-{% data reusables.github-actions.usage-workflow-run-time %}
+{% data reusables.actions.usage-workflow-run-time %}
- **Job queue time** - Each job for self-hosted runners can be queued for a maximum of 24 hours. If a self-hosted runner does not start executing the job within this limit, the job is terminated and fails to complete.
-{% data reusables.github-actions.usage-api-requests %}
-- **Job matrix** - {% data reusables.github-actions.usage-matrix-limits %}
-{% data reusables.github-actions.usage-workflow-queue-limits %}
+{% data reusables.actions.usage-api-requests %}
+- **Job matrix** - {% data reusables.actions.usage-matrix-limits %}
+{% data reusables.actions.usage-workflow-queue-limits %}
## Workflow continuity for self-hosted runners
-{% data reusables.github-actions.runner-workflow-continuity %}
+{% data reusables.actions.runner-workflow-continuity %}
## Supported architectures and operating systems for self-hosted runners
@@ -224,7 +224,7 @@ codeload.github.com
{% ifversion fpt or ghec %}
-{% data reusables.github-actions.self-hosted-runner-security %}
+{% data reusables.actions.self-hosted-runner-security %}
{% endif %}
diff --git a/translations/zh-CN/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md b/translations/zh-CN/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md
index a43a506f24e3..6be17995b524 100644
--- a/translations/zh-CN/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md
+++ b/translations/zh-CN/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md
@@ -26,7 +26,7 @@ For information on supported operating systems for self-hosted runners, or using
{% ifversion not ghae %}
{% warning %}
-**Warning:** {% data reusables.github-actions.self-hosted-runner-security %}
+**Warning:** {% data reusables.actions.self-hosted-runner-security %}
For more information, see "[About self-hosted runners](/github/automating-your-workflow-with-github-actions/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)."
@@ -40,18 +40,18 @@ You can add self-hosted runners to a single repository. To add a self-hosted run
{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5091 %}
{% data reusables.repositories.navigate-to-repo %}
{% data reusables.repositories.sidebar-settings %}
-{% data reusables.github-actions.settings-sidebar-actions %}
-{% data reusables.github-actions.settings-sidebar-actions-runners-updated %}
+{% data reusables.actions.settings-sidebar-actions %}
+{% data reusables.actions.settings-sidebar-actions-runners-updated %}
1. Click **New self-hosted runner**.
-{% data reusables.github-actions.self-hosted-runner-configure %}
+{% data reusables.actions.self-hosted-runner-configure %}
{% elsif ghae or ghes < 3.4 %}
{% data reusables.repositories.navigate-to-repo %}
{% data reusables.repositories.sidebar-settings %}
-{% data reusables.github-actions.settings-sidebar-actions-runners %}
+{% data reusables.actions.settings-sidebar-actions-runners %}
1. Under {% ifversion ghes > 3.1 or ghae or ghec %}"Runners"{% else %}"Self-hosted runners"{% endif %}, click **Add runner**.
-{% data reusables.github-actions.self-hosted-runner-configure %}
+{% data reusables.actions.self-hosted-runner-configure %}
{% endif %}
-{% data reusables.github-actions.self-hosted-runner-check-installation-success %}
+{% data reusables.actions.self-hosted-runner-check-installation-success %}
## Adding a self-hosted runner to an organization
@@ -60,21 +60,21 @@ You can add self-hosted runners at the organization level, where they can be use
{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5091 %}
{% data reusables.organizations.navigate-to-org %}
{% data reusables.organizations.org_settings %}
-{% data reusables.github-actions.settings-sidebar-actions %}
-{% data reusables.github-actions.settings-sidebar-actions-runners-updated %}
+{% data reusables.actions.settings-sidebar-actions %}
+{% data reusables.actions.settings-sidebar-actions-runners-updated %}
1. Click **New runner**.
-{% data reusables.github-actions.self-hosted-runner-configure %}
+{% data reusables.actions.self-hosted-runner-configure %}
{% elsif ghae or ghes < 3.4 %}
{% data reusables.organizations.navigate-to-org %}
{% data reusables.organizations.org_settings %}
-{% data reusables.github-actions.settings-sidebar-actions-runners %}
+{% data reusables.actions.settings-sidebar-actions-runners %}
1. Under {% ifversion ghes > 3.1 or ghae %}"Runners", click **Add new**, then click **New runner**.{% elsif ghes < 3.2 %}"Self-hosted runners", click **Add runner**."{% endif %}
-{% data reusables.github-actions.self-hosted-runner-configure %}
+{% data reusables.actions.self-hosted-runner-configure %}
{% endif %}
-{% data reusables.github-actions.self-hosted-runner-check-installation-success %}
+{% data reusables.actions.self-hosted-runner-check-installation-success %}
-{% data reusables.github-actions.self-hosted-runner-public-repo-access %}
+{% data reusables.actions.self-hosted-runner-public-repo-access %}
## Adding a self-hosted runner to an enterprise
@@ -92,7 +92,7 @@ To add a self-hosted runner to an enterprise account, you must be an enterprise
{% data reusables.enterprise-accounts.actions-tab %}
{% data reusables.enterprise-accounts.actions-runners-tab %}
1. Click **New runner**.
-{% data reusables.github-actions.self-hosted-runner-configure %}
+{% data reusables.actions.self-hosted-runner-configure %}
{% elsif ghae or ghes < 3.4 %}
To add a self-hosted runner at the enterprise level of {% data variables.product.product_location %}, you must be a site administrator.
{% data reusables.enterprise-accounts.access-enterprise %}
@@ -100,11 +100,11 @@ To add a self-hosted runner at the enterprise level of {% data variables.product
{% data reusables.enterprise-accounts.actions-tab %}
{% data reusables.enterprise-accounts.actions-runners-tab %}
1. Click **Add new**, then click **New runner**.
-{% data reusables.github-actions.self-hosted-runner-configure %}
+{% data reusables.actions.self-hosted-runner-configure %}
{% endif %}
-{% data reusables.github-actions.self-hosted-runner-check-installation-success %}
+{% data reusables.actions.self-hosted-runner-check-installation-success %}
-{% data reusables.github-actions.self-hosted-runner-public-repo-access %}
+{% data reusables.actions.self-hosted-runner-public-repo-access %}
### Making enterprise runners available to repositories
diff --git a/translations/zh-CN/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md b/translations/zh-CN/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md
index 98789359aa79..c4295d60de9a 100644
--- a/translations/zh-CN/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md
+++ b/translations/zh-CN/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md
@@ -49,22 +49,22 @@ shortTitle: 管理运行器组
{% ifversion ghec or ghes > 3.3 or ghae-issue-5091 %}
{% data reusables.organizations.navigate-to-org %}
{% data reusables.organizations.org_settings %}
-{% data reusables.github-actions.settings-sidebar-actions-runner-groups %}
+{% data reusables.actions.settings-sidebar-actions-runner-groups %}
1. 在“Runner groups（运行器组）”部分，单击 **New runner group（新运行器组）**。
- {% data reusables.github-actions.runner-group-assign-policy-repo %}
+ {% data reusables.actions.runner-group-assign-policy-repo %}
{% warning %}
- **警告：** {% indented_data_reference reusables.github-actions.self-hosted-runner-security spaces=3 %}
+ **警告：** {% indented_data_reference reusables.actions.self-hosted-runner-security spaces=3 %}
更多信息请参阅“[关于自托管运行器](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)”。
{% endwarning %}
-{% data reusables.github-actions.self-hosted-runner-create-group %}
+{% data reusables.actions.self-hosted-runner-create-group %}
{% elsif ghae or ghes < 3.4 %}
{% data reusables.organizations.navigate-to-org %}
{% data reusables.organizations.org_settings %}
-{% data reusables.github-actions.settings-sidebar-actions-runners %}
+{% data reusables.actions.settings-sidebar-actions-runners %}
1. 在 {% ifversion ghes > 3.1 or ghae %}“Runners（运行器）”{% elsif ghes < 3.2 %}“Self-hosted runners（自托管运行器）”{% endif %} 下，单击 **Add new（新增）**，然后单击 **New group（新建组）**。
@@ -76,7 +76,7 @@ shortTitle: 管理运行器组
**警告**
- {% indented_data_reference reusables.github-actions.self-hosted-runner-security spaces=3 %}
+ {% indented_data_reference reusables.actions.self-hosted-runner-security spaces=3 %}
更多信息请参阅“[关于自托管运行器](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)”。
@@ -100,18 +100,18 @@ shortTitle: 管理运行器组
{% data reusables.enterprise-accounts.actions-tab %}
{% data reusables.enterprise-accounts.actions-runner-groups-tab %}
1. 单击 **New runner group（新运行器组）**。
- {% data reusables.github-actions.runner-group-assign-policy-org %}
+ {% data reusables.actions.runner-group-assign-policy-org %}
{% warning %}
**警告**
- {% indented_data_reference reusables.github-actions.self-hosted-runner-security spaces=3 %}
+ {% indented_data_reference reusables.actions.self-hosted-runner-security spaces=3 %}
更多信息请参阅“[关于自托管运行器](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)”。
{% endwarning %}
-{% data reusables.github-actions.self-hosted-runner-create-group %}
+{% data reusables.actions.self-hosted-runner-create-group %}
{% elsif ghae or ghes < 3.4 %}
{% data reusables.enterprise-accounts.access-enterprise %}
{% data reusables.enterprise-accounts.policies-tab %}
@@ -128,7 +128,7 @@ shortTitle: 管理运行器组
**警告**
- {% indented_data_reference reusables.github-actions.self-hosted-runner-security spaces=3 %}
+ {% indented_data_reference reusables.actions.self-hosted-runner-security spaces=3 %}
更多信息请参阅“[关于自托管运行器](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)”。
@@ -143,21 +143,21 @@ shortTitle: 管理运行器组
您可以更新运行器组的访问策略，或重命名运行器组。
{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5091 %}
-{% data reusables.github-actions.self-hosted-runner-groups-navigate-to-repo-org-enterprise %}
-{% data reusables.github-actions.settings-sidebar-actions-runner-groups-selection %}
+{% data reusables.actions.self-hosted-runner-groups-navigate-to-repo-org-enterprise %}
+{% data reusables.actions.settings-sidebar-actions-runner-groups-selection %}
1. 修改访问选项或更改运行器组名称。
{% warning %}
**警告**
- {% indented_data_reference reusables.github-actions.self-hosted-runner-security spaces=3 %}
+ {% indented_data_reference reusables.actions.self-hosted-runner-security spaces=3 %}
更多信息请参阅“[关于自托管运行器](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)”。
{% endwarning %}
{% elsif ghae or ghes < 3.4 %}
-{% data reusables.github-actions.self-hosted-runner-configure-runner-group-access %}
+{% data reusables.actions.self-hosted-runner-configure-runner-group-access %}
{% endif %}
{% ifversion ghec or ghes or ghae %}
@@ -179,7 +179,7 @@ shortTitle: 管理运行器组
如果您在注册过程中没有指定运行器组，新的自托管运行器将自动分配到默认组，然后可以移到另一个组。
-{% data reusables.github-actions.self-hosted-runner-navigate-to-org-enterprise %}
+{% data reusables.actions.self-hosted-runner-navigate-to-org-enterprise %}
{% ifversion ghec or ghes > 3.3 or ghae-issue-5091 %}
1. 在“Runners（运行器）”列表中，单击您要配置的运行器。
2. 选择运行器组下拉菜单。
@@ -195,7 +195,7 @@ shortTitle: 管理运行器组
自托管运行器在其组被删除时将自动返回到默认组。
{% ifversion ghes > 3.1 or ghae or ghec %}
-{% data reusables.github-actions.self-hosted-runner-groups-navigate-to-repo-org-enterprise %}
+{% data reusables.actions.self-hosted-runner-groups-navigate-to-repo-org-enterprise %}
1. 在组列表中，在要删除的组右侧，单击 {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}。
2. 要删除组，请单击 **Remove group（删除组）**。
3. 查看确认提示，然后单击 **Remove this runner group（删除此运行器组）**。
diff --git a/translations/zh-CN/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md b/translations/zh-CN/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md
index 8621853dcd14..9d6baa9ecfe7 100644
--- a/translations/zh-CN/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md
+++ b/translations/zh-CN/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md
@@ -21,10 +21,10 @@ shortTitle: Monitor & troubleshoot
## Checking the status of a self-hosted runner
-{% data reusables.github-actions.self-hosted-runner-management-permissions-required %}
+{% data reusables.actions.self-hosted-runner-management-permissions-required %}
-{% data reusables.github-actions.self-hosted-runner-navigate-repo-and-org %}
-{% data reusables.github-actions.settings-sidebar-actions-runners %}
+{% data reusables.actions.self-hosted-runner-navigate-repo-and-org %}
+{% data reusables.actions.settings-sidebar-actions-runners %}
1. Under {% ifversion fpt or ghes > 3.1 or ghae or ghec %}"Runners"{% else %}"Self-hosted runners"{% endif %}, you can view a list of registered runners, including the runner's name, labels, and status.
The status can be one of the following:
@@ -46,12 +46,12 @@ For example:
{% mac %}
-{% data reusables.github-actions.self-hosted-runner-check-mac-linux %}
+{% data reusables.actions.self-hosted-runner-check-mac-linux %}
{% endmac %}
{% linux %}
-{% data reusables.github-actions.self-hosted-runner-check-mac-linux %}
+{% data reusables.actions.self-hosted-runner-check-mac-linux %}
{% endlinux %}
{% windows %}
diff --git a/translations/zh-CN/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md b/translations/zh-CN/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md
index 538925cb35df..b8f8830105a4 100644
--- a/translations/zh-CN/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md
+++ b/translations/zh-CN/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md
@@ -21,54 +21,54 @@ shortTitle: 删除自托管的运行器
{% note %}
-**注意：** {% data reusables.github-actions.self-hosted-runner-removal-impact %}
+**注：**{% data reusables.actions.self-hosted-runner-removal-impact %}
-{% data reusables.github-actions.self-hosted-runner-auto-removal %}
+{% data reusables.actions.self-hosted-runner-auto-removal %}
{% endnote %}
要从用户仓库删除自托管的运行器，您必须是仓库所有者。 对于组织仓库，您必须是组织所有者或拥有该仓库管理员的权限。 建议您也访问自托管的运行器机器。 有关如何使用 REST API 删除自托管运行器的信息，请参阅“[自托管运行器](/rest/reference/actions#self-hosted-runners)”。
-{% data reusables.github-actions.self-hosted-runner-reusing %}
+{% data reusables.actions.self-hosted-runner-reusing %}
{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5091 %}
{% data reusables.repositories.navigate-to-repo %}
{% data reusables.repositories.sidebar-settings %}
-{% data reusables.github-actions.settings-sidebar-actions %}
-{% data reusables.github-actions.settings-sidebar-actions-runners-updated %}
-{% data reusables.github-actions.settings-sidebar-actions-runner-selection %}
-{% data reusables.github-actions.self-hosted-runner-removing-a-runner-updated %}
+{% data reusables.actions.settings-sidebar-actions %}
+{% data reusables.actions.settings-sidebar-actions-runners-updated %}
+{% data reusables.actions.settings-sidebar-actions-runner-selection %}
+{% data reusables.actions.self-hosted-runner-removing-a-runner-updated %}
{% elsif ghae or ghes < 3.4 %}
{% data reusables.repositories.navigate-to-repo %}
{% data reusables.repositories.sidebar-settings %}
-{% data reusables.github-actions.settings-sidebar-actions-runners %}
-{% data reusables.github-actions.self-hosted-runner-removing-a-runner %}
+{% data reusables.actions.settings-sidebar-actions-runners %}
+{% data reusables.actions.self-hosted-runner-removing-a-runner %}
{% endif %}
## 从组织中删除运行器
{% note %}
-**注意：** {% data reusables.github-actions.self-hosted-runner-removal-impact %}
+**注：**{% data reusables.actions.self-hosted-runner-removal-impact %}
-{% data reusables.github-actions.self-hosted-runner-auto-removal %}
+{% data reusables.actions.self-hosted-runner-auto-removal %}
{% endnote %}
要从组织删除自托管的运行器，您必须是组织所有者。 建议您也访问自托管的运行器机器。 有关如何使用 REST API 删除自托管运行器的信息，请参阅“[自托管运行器](/rest/reference/actions#self-hosted-runners)”。
-{% data reusables.github-actions.self-hosted-runner-reusing %}
+{% data reusables.actions.self-hosted-runner-reusing %}
{% ifversion fpt or ghes > 3.3 or ghec %}
{% data reusables.organizations.navigate-to-org %}
{% data reusables.organizations.org_settings %}
-{% data reusables.github-actions.settings-sidebar-actions %}
-{% data reusables.github-actions.settings-sidebar-actions-runners-updated %}
-{% data reusables.github-actions.settings-sidebar-actions-runner-selection %}
-{% data reusables.github-actions.self-hosted-runner-removing-a-runner-updated %}
+{% data reusables.actions.settings-sidebar-actions %}
+{% data reusables.actions.settings-sidebar-actions-runners-updated %}
+{% data reusables.actions.settings-sidebar-actions-runner-selection %}
+{% data reusables.actions.self-hosted-runner-removing-a-runner-updated %}
{% elsif ghes < 3.4 or ghae %}
{% data reusables.organizations.navigate-to-org %}
{% data reusables.organizations.org_settings %}
-{% data reusables.github-actions.settings-sidebar-actions-runners %}
-{% data reusables.github-actions.self-hosted-runner-removing-a-runner %}
+{% data reusables.actions.settings-sidebar-actions-runners %}
+{% data reusables.actions.self-hosted-runner-removing-a-runner %}
{% endif %}
## 从企业中删除运行器
@@ -80,27 +80,27 @@ shortTitle: 删除自托管的运行器
{% ifversion ghec or ghes or ghae %}
{% note %}
-**注意：** {% data reusables.github-actions.self-hosted-runner-removal-impact %}
+**注：**{% data reusables.actions.self-hosted-runner-removal-impact %}
-{% data reusables.github-actions.self-hosted-runner-auto-removal %}
+{% data reusables.actions.self-hosted-runner-auto-removal %}
{% endnote %}
要从企业帐户删除自托管运行器，您必须是企业所有者。 建议您也访问自托管的运行器机器。 有关如何使用 REST API 删除自托管运行器的信息，请参阅 [{% data variables.product.prodname_actions %} REST API](/rest/reference/actions#self-hosted-runners) 中的企业端点。
-{% data reusables.github-actions.self-hosted-runner-reusing %}
+{% data reusables.actions.self-hosted-runner-reusing %}
{% ifversion ghec or ghes > 3.3 or ghae-issue-5091 %}
{% data reusables.enterprise-accounts.access-enterprise %}
{% data reusables.enterprise-accounts.policies-tab %}
{% data reusables.enterprise-accounts.actions-tab %}
{% data reusables.enterprise-accounts.actions-runners-tab %}
-{% data reusables.github-actions.settings-sidebar-actions-runner-selection %}
-{% data reusables.github-actions.self-hosted-runner-removing-a-runner-updated %}
+{% data reusables.actions.settings-sidebar-actions-runner-selection %}
+{% data reusables.actions.self-hosted-runner-removing-a-runner-updated %}
{% elsif ghae or ghes < 3.4 %}
{% data reusables.enterprise-accounts.access-enterprise %}
{% data reusables.enterprise-accounts.policies-tab %}
{% data reusables.enterprise-accounts.actions-tab %}
{% data reusables.enterprise-accounts.actions-runners-tab %}
-{% data reusables.github-actions.self-hosted-runner-removing-a-runner %}
+{% data reusables.actions.self-hosted-runner-removing-a-runner %}
{% endif %}
{% endif %}
diff --git a/translations/zh-CN/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md b/translations/zh-CN/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md
index e8637250d7f1..43416744caa2 100644
--- a/translations/zh-CN/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md
+++ b/translations/zh-CN/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md
@@ -16,54 +16,54 @@ shortTitle: 标签运行器
有关如何使用标签将作业路由到特定类型的自托管运行器的信息，请参阅“[在工作流程中使用自托管的运行器](/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow)”。
-{% data reusables.github-actions.self-hosted-runner-management-permissions-required %}
+{% data reusables.actions.self-hosted-runner-management-permissions-required %}
## 创建自定义标签
{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5091 %}
-{% data reusables.github-actions.self-hosted-runner-navigate-to-repo-org-enterprise %}
- {% data reusables.github-actions.settings-sidebar-actions-runner-selection %}
+{% data reusables.actions.self-hosted-runner-navigate-to-repo-org-enterprise %}
+ {% data reusables.actions.settings-sidebar-actions-runner-selection %}
1. 在“Labels（标签）”部分，单击 {% octicon "gear" aria-label="The Gear icon" %}。
- 1. 在“Find or create a label（查找或创建标签）”字段中，键入新标签的名称，并单击 **Create new label（创建新标签）**。 将创建自定义标签并分配给自托管运行器。 可以从自托管的运行器中删除自定义标签，但当前无法手动删除。 {% data reusables.github-actions.actions-unused-labels %}
+ 1. 在“Find or create a label（查找或创建标签）”字段中，键入新标签的名称，并单击 **Create new label（创建新标签）**。 将创建自定义标签并分配给自托管运行器。 可以从自托管的运行器中删除自定义标签，但当前无法手动删除。 {% data reusables.actions.actions-unused-labels %}
{% elsif ghae or ghes < 3.4 %}
-{% data reusables.github-actions.self-hosted-runner-navigate-to-repo-org-enterprise %}
-{% data reusables.github-actions.self-hosted-runner-list %}
-{% data reusables.github-actions.self-hosted-runner-list-group %}
-{% data reusables.github-actions.self-hosted-runner-labels-view-assigned-labels %}
+{% data reusables.actions.self-hosted-runner-navigate-to-repo-org-enterprise %}
+{% data reusables.actions.self-hosted-runner-list %}
+{% data reusables.actions.self-hosted-runner-list-group %}
+{% data reusables.actions.self-hosted-runner-labels-view-assigned-labels %}
1. 在“Filter labels（过滤标签）”字段中，键入新标签的名称，并单击 **Create new label（创建新标签）**。 
-将创建自定义标签并分配给自托管运行器。 可以从自托管的运行器中删除自定义标签，但当前无法手动删除。 {% data reusables.github-actions.actions-unused-labels %}
+将创建自定义标签并分配给自托管运行器。 可以从自托管的运行器中删除自定义标签，但当前无法手动删除。 {% data reusables.actions.actions-unused-labels %}
{% endif %}
## 分配标签给自托管的运行器
{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5091 %}
-{% data reusables.github-actions.self-hosted-runner-navigate-to-repo-org-enterprise %}
-{% data reusables.github-actions.settings-sidebar-actions-runner-selection %}
-{% data reusables.github-actions.runner-label-settings %}
+{% data reusables.actions.self-hosted-runner-navigate-to-repo-org-enterprise %}
+{% data reusables.actions.settings-sidebar-actions-runner-selection %}
+{% data reusables.actions.runner-label-settings %}
1. 要将标签分配给您的自托管运行器，在“Find or create a label（查找或创建标签）”字段中单击标签。
{% elsif ghae or ghes < 3.4 %}
-{% data reusables.github-actions.self-hosted-runner-navigate-to-repo-org-enterprise %}
-{% data reusables.github-actions.self-hosted-runner-list %}
-{% data reusables.github-actions.self-hosted-runner-list-group %}
-{% data reusables.github-actions.self-hosted-runner-labels-view-assigned-labels %}
+{% data reusables.actions.self-hosted-runner-navigate-to-repo-org-enterprise %}
+{% data reusables.actions.self-hosted-runner-list %}
+{% data reusables.actions.self-hosted-runner-list-group %}
+{% data reusables.actions.self-hosted-runner-labels-view-assigned-labels %}
1. 单击标签以将其分配给您的自托管运行器。
{% endif %}
## 删除自托管运行器中的自定义标签
{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5091 %}
-{% data reusables.github-actions.self-hosted-runner-navigate-to-repo-org-enterprise %}
-{% data reusables.github-actions.settings-sidebar-actions-runner-selection %}
-{% data reusables.github-actions.runner-label-settings %}
+{% data reusables.actions.self-hosted-runner-navigate-to-repo-org-enterprise %}
+{% data reusables.actions.settings-sidebar-actions-runner-selection %}
+{% data reusables.actions.runner-label-settings %}
1. 在“Find or create a label（查找或创建标签）”字段中，分配的标签使用
{% octicon "check" aria-label="The Check icon" %} 图标来标记。 单击标记的标签以将其从您的自托管运行器取消分配。
{% elsif ghae or ghes < 3.4 %}
-{% data reusables.github-actions.self-hosted-runner-navigate-to-repo-org-enterprise %}
-{% data reusables.github-actions.self-hosted-runner-list %}
-{% data reusables.github-actions.self-hosted-runner-list-group %}
-{% data reusables.github-actions.self-hosted-runner-labels-view-assigned-labels %}
-1. 单击分配的标签以将其从您的自托管运行器中删除。 {% data reusables.github-actions.actions-unused-labels %}
+{% data reusables.actions.self-hosted-runner-navigate-to-repo-org-enterprise %}
+{% data reusables.actions.self-hosted-runner-list %}
+{% data reusables.actions.self-hosted-runner-list-group %}
+{% data reusables.actions.self-hosted-runner-labels-view-assigned-labels %}
+1. 单击分配的标签以将其从您的自托管运行器中删除。 {% data reusables.actions.actions-unused-labels %}
{% endif %}
## 使用配置脚本创建和分配标签
diff --git a/translations/zh-CN/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md b/translations/zh-CN/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md
index 1e23b72056ea..0ed90b933bab 100644
--- a/translations/zh-CN/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md
+++ b/translations/zh-CN/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md
@@ -23,7 +23,7 @@ shortTitle: 在工作流程中使用运行器
标签允许您根据其共同特征向特定类型的自托管运行器发送工作流程作业。 例如，如果您的作业需要特定的硬件组件或软件包。 您可以将一个自定义标签分配给运行器，然后将您的作业配置为仅在带该标签的运行器中执行。
-{% data reusables.github-actions.self-hosted-runner-labels-runs-on %}
+{% data reusables.actions.self-hosted-runner-labels-runs-on %}
更多信息请参阅“[{% data variables.product.prodname_actions %} 的工作流程语法](/github/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idruns-on)”。
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 31ce76762d35..25a45286fb42 100644
--- a/translations/zh-CN/content/actions/learn-github-actions/contexts.md
+++ b/translations/zh-CN/content/actions/learn-github-actions/contexts.md
@@ -31,7 +31,7 @@ You can access contexts using the expression syntax. For more information, see "
`${{ }}`
{% endraw %}
-{% data reusables.github-actions.context-injection-warning %}
+{% data reusables.actions.context-injection-warning %}
| 上下文名称 | 类型 | 描述 |
| ---------- | ---- | ---------------------------------------------------------------------------------------------------------------------------------------------------- |
@@ -59,7 +59,7 @@ As part of an expression, you can access context information using one of two sy
### 确定何时使用上下文
-{% data reusables.github-actions.using-context-or-environment-variables %}
+{% data reusables.actions.using-context-or-environment-variables %}
### 上下文可用性
@@ -139,7 +139,7 @@ As part of an expression, you can access context information using one of two sy
You can print the contents of contexts to the log for debugging. The [`toJSON` function](/actions/learn-github-actions/expressions#tojson) is required to pretty-print JSON objects to the log.
-{% data reusables.github-actions.github-context-warning %}
+{% data reusables.actions.github-context-warning %}
{% raw %}
```yaml{:copy}
@@ -170,8 +170,8 @@ jobs:
`github` 上下文包含有关工作流程运行以及触发运行的事件相关信息。 You can also read most of the `github` context data in environment variables. 有关环境变量的更多信息，请参阅“[使用环境变量](/actions/automating-your-workflow-with-github-actions/using-environment-variables)”。
-{% data reusables.github-actions.github-context-warning %}
-{% data reusables.github-actions.context-injection-warning %}
+{% data reusables.actions.github-context-warning %}
+{% data reusables.actions.context-injection-warning %}
| 属性名称 | 类型 | 描述 |
| -------------------------- | ----- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
@@ -194,9 +194,11 @@ jobs:
{%- 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 %} | | `github.ref_type` | `string` | {% data reusables.actions.ref_type-description %}
{%- endif %}
-| `github.path` | `string` | Path on the runner to the file that sets system `PATH` variables from workflow commands. This file is unique to the current step and is a different file for each step in a job. For more information, see "[Workflow commands for {% data variables.product.prodname_actions %}](/actions/learn-github-actions/workflow-commands-for-github-actions#adding-a-system-path)." | | `github.repository` | `string` | The owner and repository name. 例如 `Codertocat/Hello-World`。 | | `github.repository_owner` | `string` | The repository owner's name. 例如 `Codertocat`。 | | `github.repositoryUrl` | `string` | The Git URL to the repository. For example, `git://github.com/codertocat/hello-world.git`. | | `github.retention_days` | `string` | The number of days that workflow run logs and artifacts are kept. | | `github.run_id` | `string` | {% data reusables.github-actions.run_id_description %} | | `github.run_number` | `string` | {% data reusables.github-actions.run_number_description %}
+| `github.path` | `string` | Path on the runner to the file that sets system `PATH` variables from workflow commands. This file is unique to the current step and is a different file for each step in a job. For more information, see "[Workflow commands for {% data variables.product.prodname_actions %}](/actions/learn-github-actions/workflow-commands-for-github-actions#adding-a-system-path)." | | `github.repository` | `string` | The owner and repository name. 例如 `Codertocat/Hello-World`。 | | `github.repository_owner` | `string` | The repository owner's name. 例如 `Codertocat`。 | | `github.repositoryUrl` | `string` | The Git URL to the repository. For example, `git://github.com/codertocat/hello-world.git`. | | `github.retention_days` | `string` | The number of days that workflow run logs and artifacts are kept. | | `github.run_id` | `string` | {% data reusables.actions.run_id_description %} | | `github.run_number` | `string` | {% data reusables.actions.run_number_description %}
{%- ifversion fpt or ghec or ghes > 3.5 or ghae-issue-4722 %}
-| `github.run_attempt` | `string` | A unique number for each attempt of a particular workflow run in a repository. This number begins at 1 for the workflow run's first attempt, and increments with each re-run. | |{% endif %}| | `github.server_url` | `string` | The URL of the GitHub server. 例如：`https://github.com`。 | | `github.sha` | `string` | The commit SHA that triggered the workflow run. | | `github.token` | `string` | A token to authenticate on behalf of the GitHub App installed on your repository. 这在功能上等同于 `GITHUB_TOKEN` 密码。 For more information, see "[Automatic token authentication](/actions/security-guides/automatic-token-authentication)." | | `github.workflow` | `string` | The name of the workflow. 如果工作流程文件未指定 `name`，此属性的值将是仓库中工作流程文件的完整路径。 | | `github.workspace` | `string` | The default working directory on the runner for steps, and the default location of your repository when using the [`checkout`](https://github.com/actions/checkout) action. |
+| `github.run_attempt` | `string` | A unique number for each attempt of a particular workflow run in a repository. This number begins at 1 for the workflow run's first attempt, and increments with each re-run. |
+{%- endif %}
+| `github.server_url` | `string` | The URL of the GitHub server. 例如：`https://github.com`。 | | `github.sha` | `string` | The commit SHA that triggered the workflow run. | | `github.token` | `string` | A token to authenticate on behalf of the GitHub App installed on your repository. 这在功能上等同于 `GITHUB_TOKEN` 密码。 For more information, see "[Automatic token authentication](/actions/security-guides/automatic-token-authentication)." | | `github.workflow` | `string` | The name of the workflow. 如果工作流程文件未指定 `name`，此属性的值将是仓库中工作流程文件的完整路径。 | | `github.workspace` | `string` | The default working directory on the runner for steps, and the default location of your repository when using the [`checkout`](https://github.com/actions/checkout) action. |
### Example contents of the `github` context
@@ -512,7 +514,7 @@ The `secrets` context contains the names and values of secrets that are availabl
`GITHUB_TOKEN` is a secret that is automatically created for every workflow run, and is always included in the `secrets` context. For more information, see "[Automatic token authentication](/actions/security-guides/automatic-token-authentication)."
-{% data reusables.github-actions.secrets-redaction-warning %}
+{% data reusables.actions.secrets-redaction-warning %}
| 属性名称 | 类型 | 描述 |
| ----------------------------- | ----- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
@@ -534,7 +536,7 @@ The following example contents of the `secrets` context shows the automatic `GIT
### Example usage of the `secrets` context
-{% data reusables.github-actions.github_token-input-example %}
+{% data reusables.actions.github_token-input-example %}
## `strategy` context
diff --git a/translations/zh-CN/content/actions/learn-github-actions/environment-variables.md b/translations/zh-CN/content/actions/learn-github-actions/environment-variables.md
index 1fe6b1e3e5b2..3c37234146de 100644
--- a/translations/zh-CN/content/actions/learn-github-actions/environment-variables.md
+++ b/translations/zh-CN/content/actions/learn-github-actions/environment-variables.md
@@ -147,7 +147,7 @@ The default environment variables that {% data variables.product.prodname_dotcom
{%- 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 %} | | `GITHUB_REF_TYPE` | {% data reusables.actions.ref_type-description %}
{%- endif %}
-| `GITHUB_REPOSITORY` | The owner and repository name. 例如 `octocat/Hello-World`。 | | `GITHUB_REPOSITORY_OWNER` | The repository owner's name. 例如 `octocat`。 | | `GITHUB_RETENTION_DAYS` | The number of days that workflow run logs and artifacts are kept. For example, `90`. | | `GITHUB_RUN_ATTEMPT` | A unique number for each attempt of a particular workflow run in a repository. This number begins at 1 for the workflow run's first attempt, and increments with each re-run. For example, `3`. | | `GITHUB_RUN_ID` | {% data reusables.github-actions.run_id_description %} For example, `1658821493`. | | `GITHUB_RUN_NUMBER` | {% data reusables.github-actions.run_number_description %} For example, `3`. | | `GITHUB_SERVER_URL`| The URL of the {% data variables.product.product_name %} server. For example: `https://{% data variables.product.product_url %}`. | `GITHUB_SHA` | The commit SHA that triggered the workflow. 例如 `ffac537e6cbbf934b08745a378932722df287a53`。 | | `GITHUB_WORKFLOW` | The name of the workflow. For example, `My test workflow`. If the workflow file doesn't specify a `name`, the value of this variable is the full path of the workflow file in the repository. | | `GITHUB_WORKSPACE` | The default working directory on the runner for steps, and the default location of your repository when using the [`checkout`](https://github.com/actions/checkout) action. 例如 `/home/runner/work/my-repo-name/my-repo-name`。 |
+| `GITHUB_REPOSITORY` | The owner and repository name. 例如 `octocat/Hello-World`。 | | `GITHUB_REPOSITORY_OWNER` | The repository owner's name. 例如 `octocat`。 | | `GITHUB_RETENTION_DAYS` | The number of days that workflow run logs and artifacts are kept. For example, `90`. | | `GITHUB_RUN_ATTEMPT` | A unique number for each attempt of a particular workflow run in a repository. This number begins at 1 for the workflow run's first attempt, and increments with each re-run. For example, `3`. | | `GITHUB_RUN_ID` | {% data reusables.actions.run_id_description %} For example, `1658821493`. | | `GITHUB_RUN_NUMBER` | {% data reusables.actions.run_number_description %} For example, `3`. | | `GITHUB_SERVER_URL`| The URL of the {% data variables.product.product_name %} server. For example: `https://{% data variables.product.product_url %}`. | `GITHUB_SHA` | The commit SHA that triggered the workflow. 例如 `ffac537e6cbbf934b08745a378932722df287a53`。 | | `GITHUB_WORKFLOW` | The name of the workflow. For example, `My test workflow`. If the workflow file doesn't specify a `name`, the value of this variable is the full path of the workflow file in the repository. | | `GITHUB_WORKSPACE` | The default working directory on the runner for steps, and the default location of your repository when using the [`checkout`](https://github.com/actions/checkout) action. 例如 `/home/runner/work/my-repo-name/my-repo-name`。 |
{%- if actions-runner-arch-envvars %}
| `RUNNER_ARCH` | {% data reusables.actions.runner-arch-description %}
{%- endif %}
diff --git a/translations/zh-CN/content/actions/learn-github-actions/expressions.md b/translations/zh-CN/content/actions/learn-github-actions/expressions.md
index 88e983d799d0..bca162dca8d5 100644
--- a/translations/zh-CN/content/actions/learn-github-actions/expressions.md
+++ b/translations/zh-CN/content/actions/learn-github-actions/expressions.md
@@ -25,9 +25,9 @@ You can use expressions to programmatically set environment variables in workflo
`${{ }}`
{% endraw %}
-{% data reusables.github-actions.expression-syntax-if %}有关 `if` 条件的更多信息，请参阅“[{% data variables.product.prodname_actions %} 的工作流程语法](/articles/workflow-syntax-for-github-actions/#jobsjob_idif)”。
+{% data reusables.actions.expression-syntax-if %}有关 `if` 条件的更多信息，请参阅“[{% data variables.product.prodname_actions %} 的工作流程语法](/articles/workflow-syntax-for-github-actions/#jobsjob_idif)”。
-{% data reusables.github-actions.context-injection-warning %}
+{% data reusables.actions.context-injection-warning %}
#### `if` 条件的示例表达式
diff --git a/translations/zh-CN/content/actions/learn-github-actions/understanding-github-actions.md b/translations/zh-CN/content/actions/learn-github-actions/understanding-github-actions.md
index 5a6fe5642d70..c30e6ef6956b 100644
--- a/translations/zh-CN/content/actions/learn-github-actions/understanding-github-actions.md
+++ b/translations/zh-CN/content/actions/learn-github-actions/understanding-github-actions.md
@@ -254,7 +254,7 @@ _操作_是 {% data variables.product.prodname_actions %} 平台的自定义应
## 联系支持
-{% data reusables.github-actions.contacting-support %}
+{% data reusables.actions.contacting-support %}
## 延伸阅读
diff --git a/translations/zh-CN/content/actions/learn-github-actions/usage-limits-billing-and-administration.md b/translations/zh-CN/content/actions/learn-github-actions/usage-limits-billing-and-administration.md
index bc81a0d5b2e8..0ad788be83cd 100644
--- a/translations/zh-CN/content/actions/learn-github-actions/usage-limits-billing-and-administration.md
+++ b/translations/zh-CN/content/actions/learn-github-actions/usage-limits-billing-and-administration.md
@@ -21,7 +21,7 @@ shortTitle: 工作流程计费和限制
{% data reusables.repositories.about-github-actions %} For more information, see "[Understanding {% data variables.product.prodname_actions %}](/actions/learn-github-actions/understanding-github-actions){% ifversion fpt %}."{% elsif ghes or ghec %}" and "[About {% data variables.product.prodname_actions %} for enterprises](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises)."{% endif %}
{% ifversion fpt or ghec %}
-{% data reusables.github-actions.actions-billing %} 更多信息请参阅“[关于 {% data variables.product.prodname_actions %} 的计费](/billing/managing-billing-for-github-actions/about-billing-for-github-actions)”。
+{% data reusables.actions.actions-billing %} 更多信息请参阅“[关于 {% data variables.product.prodname_actions %} 的计费](/billing/managing-billing-for-github-actions/about-billing-for-github-actions)”。
{% else %}
GitHub Actions usage is free for {% data variables.product.prodname_ghe_server %} instances that use self-hosted runners. 更多信息请参阅“[关于自托管运行器](/actions/hosting-your-own-runners/about-self-hosted-runners)”。
{% endif %}
@@ -47,8 +47,8 @@ There are some limits on {% data variables.product.prodname_actions %} usage whe
{% endnote %}
- **作业执行时间** - 工作流程中的每个作业最多可以运行 6 个小时。 如果作业达到此限制，该作业将会终止而无法完成。
-{% data reusables.github-actions.usage-workflow-run-time %}
-{% data reusables.github-actions.usage-api-requests %}
+{% data reusables.actions.usage-workflow-run-time %}
+{% data reusables.actions.usage-api-requests %}
- **并发作业** - 您的帐户中可并发运行的作业数量，具体取决于您的 GitHub 计划，如下表所示。 如果超出，任何额外的作业都会排队。
| GitHub 计划 | 同时运行的作业总数 | MacOS 作业同时运行的最大数量 |
@@ -57,8 +57,8 @@ There are some limits on {% data variables.product.prodname_actions %} usage whe
| Pro | 40 | 5 |
| 团队 | 60 | 5 |
| 企业 | 180 | 50 |
-- **作业矩阵** - {% data reusables.github-actions.usage-matrix-limits %}
-{% data reusables.github-actions.usage-workflow-queue-limits %}
+- **作业矩阵** - {% data reusables.actions.usage-matrix-limits %}
+{% data reusables.actions.usage-workflow-queue-limits %}
{% else %}
使用限制适用于自托管运行器。 更多信息请参阅“[关于自托管运行器](/actions/hosting-your-own-runners/about-self-hosted-runners/#usage-limits)”。
@@ -82,7 +82,7 @@ For more information see, "[Reusing workflows](/actions/learn-github-actions/reu
## 构件和日志保留策略
-You can configure the artifact and log retention period for your repository, organization, or enterprise account.
+您可以为仓库、组织或企业帐户配置构件和日志保留期。
{% data reusables.actions.about-artifact-log-retention %}
@@ -94,7 +94,7 @@ You can configure the artifact and log retention period for your repository, org
## 禁用或限制仓库或组织的 {% data variables.product.prodname_actions %}
-{% data reusables.github-actions.disabling-github-actions %}
+{% data reusables.actions.disabling-github-actions %}
更多信息请参阅：
- “[管理仓库的 {% data variables.product.prodname_actions %} 设置](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository)”
@@ -103,7 +103,7 @@ You can configure the artifact and log retention period for your repository, org
## 禁用和启用工作流程
-You can enable and disable individual workflows in your repository on {% data variables.product.prodname_dotcom %}.
+您可以在 {% data variables.product.prodname_dotcom %} 上启用和禁用仓库中的个别工作流程。
{% data reusables.actions.scheduled-workflows-disabled %}
diff --git a/translations/zh-CN/content/actions/managing-workflow-runs/removing-workflow-artifacts.md b/translations/zh-CN/content/actions/managing-workflow-runs/removing-workflow-artifacts.md
index e08d27650c95..c93e99d754ef 100644
--- a/translations/zh-CN/content/actions/managing-workflow-runs/removing-workflow-artifacts.md
+++ b/translations/zh-CN/content/actions/managing-workflow-runs/removing-workflow-artifacts.md
@@ -22,7 +22,7 @@ shortTitle: Remove workflow artifacts
{% data reusables.repositories.permissions-statement-write %}
-{% data reusables.github-actions.artifact-log-retention-statement %}
+{% data reusables.actions.artifact-log-retention-statement %}
{% data reusables.repositories.navigate-to-repo %}
{% data reusables.repositories.actions-tab %}
diff --git a/translations/zh-CN/content/actions/migrating-to-github-actions/migrating-from-travis-ci-to-github-actions.md b/translations/zh-CN/content/actions/migrating-to-github-actions/migrating-from-travis-ci-to-github-actions.md
index 2e87302ae73c..37f4338fc7ab 100644
--- a/translations/zh-CN/content/actions/migrating-to-github-actions/migrating-from-travis-ci-to-github-actions.md
+++ b/translations/zh-CN/content/actions/migrating-to-github-actions/migrating-from-travis-ci-to-github-actions.md
@@ -179,7 +179,7 @@ git:
Travis CI 和 {% data variables.product.prodname_actions %} 可以将自定义环境变量添加到测试矩阵，这可让您在后面的步骤中引用该变量。
-在 {% data variables.product.prodname_actions %}中，您可以使用 `include` 键将自定义环境变量添加到矩阵中。 {% data reusables.github-actions.matrix-variable-example %}
+在 {% data variables.product.prodname_actions %}中，您可以使用 `include` 键将自定义环境变量添加到矩阵中。 {% data reusables.actions.matrix-variable-example %}
## {% data variables.product.prodname_actions %} 中的关键功能
diff --git a/translations/zh-CN/content/actions/monitoring-and-troubleshooting-workflows/about-monitoring-and-troubleshooting.md b/translations/zh-CN/content/actions/monitoring-and-troubleshooting-workflows/about-monitoring-and-troubleshooting.md
index 1996d4e8fcb8..8cfd4b57893c 100644
--- a/translations/zh-CN/content/actions/monitoring-and-troubleshooting-workflows/about-monitoring-and-troubleshooting.md
+++ b/translations/zh-CN/content/actions/monitoring-and-troubleshooting-workflows/about-monitoring-and-troubleshooting.md
@@ -18,7 +18,7 @@ miniTocMaxHeadingLevel: 3
{% if github-runner-dashboard %}
### 监控组织或企业中的当前作业
-{% data reusables.github-actions.github-hosted-runners-check-concurrency %}
+{% data reusables.actions.github-hosted-runners-check-concurrency %}
{% endif %}
diff --git a/translations/zh-CN/content/actions/monitoring-and-troubleshooting-workflows/enabling-debug-logging.md b/translations/zh-CN/content/actions/monitoring-and-troubleshooting-workflows/enabling-debug-logging.md
index c88c6e67017c..92bccf803c77 100644
--- a/translations/zh-CN/content/actions/monitoring-and-troubleshooting-workflows/enabling-debug-logging.md
+++ b/translations/zh-CN/content/actions/monitoring-and-troubleshooting-workflows/enabling-debug-logging.md
@@ -15,12 +15,12 @@ versions:
这些额外的日志将通过在包含工作流程的仓库中设置密码来启用，因此将应用相同的权限要求：
-- {% data reusables.github-actions.permissions-statement-secrets-repository %}
+- {% data reusables.actions.permissions-statement-secrets-repository %}
{% ifversion fpt or ghes > 3.0 or ghae or ghec %}
-- {% data reusables.github-actions.permissions-statement-secrets-environment %}
+- {% data reusables.actions.permissions-statement-secrets-environment %}
{% endif %}
-- {% data reusables.github-actions.permissions-statement-secrets-organization %}
-- {% data reusables.github-actions.permissions-statement-secrets-api %}
+- {% data reusables.actions.permissions-statement-secrets-organization %}
+- {% data reusables.actions.permissions-statement-secrets-api %}
有关设置密码的更多信息，请参阅“[创建和使用加密密码](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)”。
diff --git a/translations/zh-CN/content/actions/monitoring-and-troubleshooting-workflows/using-workflow-run-logs.md b/translations/zh-CN/content/actions/monitoring-and-troubleshooting-workflows/using-workflow-run-logs.md
index c5e2f7997aea..c55e060d1fe9 100644
--- a/translations/zh-CN/content/actions/monitoring-and-troubleshooting-workflows/using-workflow-run-logs.md
+++ b/translations/zh-CN/content/actions/monitoring-and-troubleshooting-workflows/using-workflow-run-logs.md
@@ -19,7 +19,7 @@ versions:
{% data variables.product.prodname_actions %} 使用 Checks API 来输出工作流程的状态、结果和日志。 {% data variables.product.prodname_dotcom %} 对每个工作流程创建新检查套件。 检查套件包含检查工作流程中每项作业的运行，而每项作业包含步骤。 {% data variables.product.prodname_actions %} 作为工作流程中的一个步骤运行。 有关检查 API 的详细信息，请参阅“[检查](/rest/reference/checks)”。
-{% data reusables.github-actions.invalid-workflow-files %}
+{% data reusables.actions.invalid-workflow-files %}
## 查看日志以诊断故障
diff --git a/translations/zh-CN/content/actions/publishing-packages/publishing-docker-images.md b/translations/zh-CN/content/actions/publishing-packages/publishing-docker-images.md
index 6c6deb58fd3b..1cbfcfefc482 100644
--- a/translations/zh-CN/content/actions/publishing-packages/publishing-docker-images.md
+++ b/translations/zh-CN/content/actions/publishing-packages/publishing-docker-images.md
@@ -50,7 +50,7 @@ topics:
## 将映像发布到 Docker Hub
-{% data reusables.github-actions.release-trigger-workflow %}
+{% data reusables.actions.release-trigger-workflow %}
在下面的示例工作流程中，我们使用 Docker `login-action` 和 `build-push-action` 操作构建 Docker 映像，如果构建成功，则将构建映像推送到 Docker Hub。
@@ -108,7 +108,7 @@ jobs:
## 发布映像到 {% data variables.product.prodname_registry %}
-{% data reusables.github-actions.release-trigger-workflow %}
+{% data reusables.actions.release-trigger-workflow %}
在下面的示例工作流程中，我们使用 Docker `login-action`{% ifversion fpt or ghec %}、`metadata-action`{% endif %} 和 `build-push-action` 操作构建 Docker 映像，如果构建成功，则将构建的映像推送到 {% data variables.product.prodname_registry %}。
diff --git a/translations/zh-CN/content/actions/publishing-packages/publishing-java-packages-with-gradle.md b/translations/zh-CN/content/actions/publishing-packages/publishing-java-packages-with-gradle.md
index a27d3bf76339..a9fd3019a188 100644
--- a/translations/zh-CN/content/actions/publishing-packages/publishing-java-packages-with-gradle.md
+++ b/translations/zh-CN/content/actions/publishing-packages/publishing-java-packages-with-gradle.md
@@ -23,7 +23,7 @@ shortTitle: 带有 Gradle 的 Java 包
## 简介
-{% data reusables.github-actions.publishing-java-packages-intro %}
+{% data reusables.actions.publishing-java-packages-intro %}
## 基本要求
@@ -104,7 +104,7 @@ jobs:
MAVEN_PASSWORD: {% raw %}${{ secrets.OSSRH_TOKEN }}{% endraw %}
```
-{% data reusables.github-actions.gradle-workflow-steps %}
+{% data reusables.actions.gradle-workflow-steps %}
1. Runs the [`gradle/gradle-build-action`](https://github.com/gradle/gradle-build-action) action with the `publish` argument to publish to the `OSSRH` Maven repository. `MAVEN_USERNAME` 环境变量将使用 `OSSRH_USERNAME` 密码的内容设置，而 `MAVEN_PASSWORD` 环境变量将使用 `OSSRH_TOKEN` 密码的内容设置。
有关在工作流程中使用密码的更多信息，请参阅“[创建和使用加密密码](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)”。
@@ -115,7 +115,7 @@ jobs:
您可以在 _build.gradle_ 文件的发布块中定义指向 {% data variables.product.prodname_registry %} 的新 Maven 仓库。 在仓库配置中，您也可以利用在 CI 工作流程运行中设置的环境变量。 您可以使用 `GITHUB_ACTOR` 环境变量作为用户名，并且可以使用 `GITHUB_TOKENN` 密码设置 `GITHUB_TOKEN` 环境变量。
-{% data reusables.github-actions.github-token-permissions %}
+{% data reusables.actions.github-token-permissions %}
例如，如果组织名为“octocat”且仓库名为“hello-world”，则 _build.gradle_ 中的 {% data variables.product.prodname_registry %} 配置看起来类似于以下示例。
@@ -174,7 +174,7 @@ jobs:
GITHUB_TOKEN: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
```
-{% data reusables.github-actions.gradle-workflow-steps %}
+{% data reusables.actions.gradle-workflow-steps %}
1. Runs the [`gradle/gradle-build-action`](https://github.com/gradle/gradle-build-action) action with the `publish` argument to publish to {% data variables.product.prodname_registry %}. `GITHUB_TOKEN` 环境变量将使用 `GITHUB_TOKEN` 密码的内容设置。 {% ifversion fpt or ghes > 3.1 or ghae or ghec %}The `permissions` key specifies the access that the `GITHUB_TOKEN` secret will allow.{% endif %}
有关在工作流程中使用密码的更多信息，请参阅“[创建和使用加密密码](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)”。
@@ -255,7 +255,7 @@ jobs:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}{% endraw %}
```
-{% data reusables.github-actions.gradle-workflow-steps %}
+{% data reusables.actions.gradle-workflow-steps %}
1. Runs the [`gradle/gradle-build-action`](https://github.com/gradle/gradle-build-action) action with the `publish` argument to publish to the `OSSRH` Maven repository and {% data variables.product.prodname_registry %}. `MAVEN_USERNAME` 环境变量将使用 `OSSRH_USERNAME` 密码的内容设置，而 `MAVEN_PASSWORD` 环境变量将使用 `OSSRH_TOKEN` 密码的内容设置。 `GITHUB_TOKEN` 环境变量将使用 `GITHUB_TOKEN` 密码的内容设置。 {% ifversion fpt or ghes > 3.1 or ghae or ghec %}The `permissions` key specifies the access that the `GITHUB_TOKEN` secret will allow.{% endif %}
有关在工作流程中使用密码的更多信息，请参阅“[创建和使用加密密码](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)”。
diff --git a/translations/zh-CN/content/actions/publishing-packages/publishing-java-packages-with-maven.md b/translations/zh-CN/content/actions/publishing-packages/publishing-java-packages-with-maven.md
index 7f24ca8840c9..9021c55fef4f 100644
--- a/translations/zh-CN/content/actions/publishing-packages/publishing-java-packages-with-maven.md
+++ b/translations/zh-CN/content/actions/publishing-packages/publishing-java-packages-with-maven.md
@@ -23,7 +23,7 @@ shortTitle: 带有 Maven 的 Java 包
## 简介
-{% data reusables.github-actions.publishing-java-packages-intro %}
+{% data reusables.actions.publishing-java-packages-intro %}
## 基本要求
@@ -105,7 +105,7 @@ jobs:
1. 检出项目仓库的副本。
1. 设置 Java JDK，同时使用 `MAVEN_USERNAME` 和 `MAVEN_PASSWORD` 环境变量配置 Maven _settings.xml_ 文件为 `ossrh` 仓库添加身份验证。
-1. {% data reusables.github-actions.publish-to-maven-workflow-step %}
+1. {% data reusables.actions.publish-to-maven-workflow-step %}
有关在工作流程中使用密码的更多信息，请参阅“[创建和使用加密密码](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)”。
@@ -115,7 +115,7 @@ jobs:
在此工作流程中，您可以使用 `setup-java` 操作。 此操作将给定版本的 JDK 安装到 `PATH`，并且设置 Maven _settings.xml_ 以将包发布到 {% data variables.product.prodname_registry %}。 生成的 _settings.xml_ 定义使用 `github` 的 `id` 向服务器验证，使用 `GITHUB_ACTOR` 环境变量作为用户名，`GITHUB_TOKEN` 环境变量作为密码。 `GITHUB_TOKEN` 环境变量将获分配特殊 `GITHUB_TOKEN` 密钥的值。
-{% data reusables.github-actions.github-token-permissions %}
+{% data reusables.actions.github-token-permissions %}
对于基于 Maven的项目，您可以通过在 _pom.xml_ 文件中创建分发仓库来使用这些设置，该文件以 `github` 的 `id` 指向 {% data variables.product.prodname_registry %} 端点。
@@ -165,7 +165,7 @@ jobs:
1. 检出项目仓库的副本。
1. 设置 Java JDK，同时自动配置 Maven _settings.xml_ 文件为 `github` Maven 仓库添加身份验证，以使用 `GITHUB_TOKEN` 环境变量。
-1. {% data reusables.github-actions.publish-to-packages-workflow-step %}
+1. {% data reusables.actions.publish-to-packages-workflow-step %}
有关在工作流程中使用密码的更多信息，请参阅“[创建和使用加密密码](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)”。
@@ -218,8 +218,8 @@ jobs:
1. 检出项目仓库的副本。
1. 第一次调用 `setup-java`。 这将为 `ossrh` 仓库配置 Maven _settings.xml_ 文件，并将身份验证选项设置为下一步定义的环境变量。
-1. {% data reusables.github-actions.publish-to-maven-workflow-step %}
+1. {% data reusables.actions.publish-to-maven-workflow-step %}
1. 第二次调用 `setup-java`。 这将自动为 {% data variables.product.prodname_registry %} 配置 Maven _settings.xml_ 文件。
-1. {% data reusables.github-actions.publish-to-packages-workflow-step %}
+1. {% data reusables.actions.publish-to-packages-workflow-step %}
有关在工作流程中使用密码的更多信息，请参阅“[创建和使用加密密码](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)”。
diff --git a/translations/zh-CN/content/actions/publishing-packages/publishing-nodejs-packages.md b/translations/zh-CN/content/actions/publishing-packages/publishing-nodejs-packages.md
index 206c9afdcfe7..da890b9c5c06 100644
--- a/translations/zh-CN/content/actions/publishing-packages/publishing-nodejs-packages.md
+++ b/translations/zh-CN/content/actions/publishing-packages/publishing-nodejs-packages.md
@@ -43,7 +43,7 @@ shortTitle: Node.js 包
*package.json* 文件中的 `name` 和 `version` 字段创建唯一标识符，供注册表用来将包链接到注册表。 您可以在 *package.json* 文件中添加 `description` 字段，从而为包列表页面添加一个摘要。 更多信息请参阅 npm 文档中的“[创建 package.json 文件](https://docs.npmjs.com/creating-a-package-json-file)”和“[创建 Node.js 模块](https://docs.npmjs.com/creating-node-js-modules)”。
-当本地 *.npmrc* 文件存在且指定了 `registry` 值时，`npm publish` 命令将使用 *.npmrc* 文件中配置的注册表。 {% data reusables.github-actions.setup-node-intro %}
+当本地 *.npmrc* 文件存在且指定了 `registry` 值时，`npm publish` 命令将使用 *.npmrc* 文件中配置的注册表。 {% data reusables.actions.setup-node-intro %}
您可以使用 `setup-node` 操作指定运行器上安装的 Node.js 版本。
@@ -115,7 +115,7 @@ Please note that you need to set the `registry-url` to `https://registry.npmjs.o
### 向目标仓库验证
-要根据 {% data variables.product.prodname_registry %} 注册表在工作流程中执行经验证的操作，可以使用 `GITHUB_TOKEN`。 {% data reusables.github-actions.github-token-permissions %}
+要根据 {% data variables.product.prodname_registry %} 注册表在工作流程中执行经验证的操作，可以使用 `GITHUB_TOKEN`。 {% data reusables.actions.github-token-permissions %}
如果要将包发布到其他仓库，您必须使用对目标仓库中的包具有写入权限的个人访问令牌 (PAT)。 更多信息请参阅“[创建个人访问令牌](/github/authenticating-to-github/creating-a-personal-access-token)”和“[加密密码](/actions/reference/encrypted-secrets)”。
diff --git a/translations/zh-CN/content/actions/security-guides/automatic-token-authentication.md b/translations/zh-CN/content/actions/security-guides/automatic-token-authentication.md
index 41764e7158d7..8ec43e6fa78f 100644
--- a/translations/zh-CN/content/actions/security-guides/automatic-token-authentication.md
+++ b/translations/zh-CN/content/actions/security-guides/automatic-token-authentication.md
@@ -39,11 +39,11 @@ shortTitle: Automatic token authentication
{% endnote %}
{% endif %}
-{% data reusables.github-actions.actions-do-not-trigger-workflows %}
+{% data reusables.actions.actions-do-not-trigger-workflows %}
### 示例 1：将 `GITHUB_TOKEN` 作为输入传递
-{% data reusables.github-actions.github_token-input-example %}
+{% data reusables.actions.github_token-input-example %}
### 例2：调用 REST API
@@ -121,7 +121,7 @@ jobs:
您可以在工作流文件中使用 `permissions` 键来修改 `GITHUB_TOKEN` 对于整个工作流或单个作业的权限。 这允许您为工作流程或作业配置所需的最小权限。 使用 `permissions` 键时，所有未指定的权限都设置为没有访问权限，`metadata`范围除外，该范围总是获得读取访问。
-{% data reusables.github-actions.forked-write-permission %}
+{% data reusables.actions.forked-write-permission %}
本文前面的两个工作流程示例显示了在工作流程级别和作业级别使用的 `permissions` 键。 在[例 1](#example-1-passing-the-github_token-as-an-input) 中，为整个工作流程指定了两个权限。 在[示例 2](#example-2-calling-the-rest-api) 中，为单个作业的单一范围授予写入访问权限。
diff --git a/translations/zh-CN/content/actions/security-guides/encrypted-secrets.md b/translations/zh-CN/content/actions/security-guides/encrypted-secrets.md
index 2ac837824376..cb7c2b333a2b 100644
--- a/translations/zh-CN/content/actions/security-guides/encrypted-secrets.md
+++ b/translations/zh-CN/content/actions/security-guides/encrypted-secrets.md
@@ -21,7 +21,7 @@ versions:
机密是您在组织{% ifversion fpt or ghes > 3.0 or ghae or ghec %}、仓库或者仓库环境{% else %} 或仓库{% endif %} 中创建的加密环境变量。 您创建的机密可用于 {% data variables.product.prodname_actions %} 工作流程。 在机密到达 {% data variables.product.prodname_dotcom %} 之前，{% data variables.product.prodname_dotcom %} 使用 [libsodium 密封盒](https://libsodium.gitbook.io/doc/public-key_cryptography/sealed_boxes)对机密加密，并且在您于工作流程中使用它们之前一直保持加密状态。
-{% data reusables.github-actions.secrets-org-level-overview %}
+{% data reusables.actions.secrets-org-level-overview %}
{% ifversion fpt or ghes > 3.0 or ghae or ghec %}
对于存储在环境级别的机密，您可以启用所需的审查者来控制对机密的访问。 在必要的审查者授予批准之前，工作流程作业无法访问环境机密。
@@ -53,7 +53,7 @@ versions:
如果您拥有编辑文件的权限，便可在工作流程文件中使用和读取加密密码。 更多信息请参阅“[{% data variables.product.prodname_dotcom %} 上的访问权限](/github/getting-started-with-github/access-permissions-on-github)”。
-{% data reusables.github-actions.secrets-redaction-warning %}
+{% data reusables.actions.secrets-redaction-warning %}
{% ifversion fpt or ghes > 3.0 or ghae or ghec %}
当工作流程运行排队时读取组织和仓库机密，在引用环境的作业开始时读取环境机密。
@@ -73,13 +73,13 @@ versions:
## 为仓库创建加密密码
-{% data reusables.github-actions.permissions-statement-secrets-repository %}
+{% data reusables.actions.permissions-statement-secrets-repository %}
{% webui %}
{% data reusables.repositories.navigate-to-repo %}
{% data reusables.repositories.sidebar-settings %}
-{% data reusables.github-actions.sidebar-secret %}
+{% data reusables.actions.sidebar-secret %}
1. 单击 **New repository secret（新仓库机密）**。
1. 在 **Name（名称）**输入框中键入密码的名称。
1. 输入密码的值。
@@ -113,13 +113,13 @@ gh secret set secret-name < secret.txt
## 为环境创建加密密码
-{% data reusables.github-actions.permissions-statement-secrets-environment %}
+{% data reusables.actions.permissions-statement-secrets-environment %}
{% webui %}
{% data reusables.repositories.navigate-to-repo %}
{% data reusables.repositories.sidebar-settings %}
-{% data reusables.github-actions.sidebar-environment %}
+{% data reusables.actions.sidebar-environment %}
1. 单击要向其添加机密的环境。
2. 在 **Environment secrets（环境机密）**下，单击 **Add secret（添加机密）**。
3. 在 **Name（名称）**输入框中键入密码的名称。
@@ -150,13 +150,13 @@ gh secret list --env environment-name
在组织中创建密码时，可以使用策略来限制可以访问该密码的仓库。 例如，您可以将访问权限授予所有仓库，也可以限制仅私有仓库或指定的仓库列表拥有访问权限。
-{% data reusables.github-actions.permissions-statement-secrets-organization %}
+{% data reusables.actions.permissions-statement-secrets-organization %}
{% webui %}
{% data reusables.organizations.navigate-to-org %}
{% data reusables.organizations.org_settings %}
-{% data reusables.github-actions.sidebar-secret %}
+{% data reusables.actions.sidebar-secret %}
1. 单击 **New organization secret（新组织机密）**。
1. 在 **Name（名称）**输入框中键入密码的名称。
1. 输入密码的 **Value（值）**。
@@ -209,7 +209,7 @@ gh secret list --org organization-name
{% data reusables.organizations.navigate-to-org %}
{% data reusables.organizations.org_settings %}
-{% data reusables.github-actions.sidebar-secret %}
+{% data reusables.actions.sidebar-secret %}
1. 密码列表包括任何已配置的权限和策略。 例如： 
1. 有关已为每个密码配置的权限的更多信息，请单击 **Update（更新）**。
diff --git a/translations/zh-CN/content/actions/using-containerized-services/about-service-containers.md b/translations/zh-CN/content/actions/using-containerized-services/about-service-containers.md
index 96be5cbaac8f..5d2b678210dd 100644
--- a/translations/zh-CN/content/actions/using-containerized-services/about-service-containers.md
+++ b/translations/zh-CN/content/actions/using-containerized-services/about-service-containers.md
@@ -25,7 +25,7 @@ topics:
您可以为工作流程中的每个作业配置服务容器。 {% data variables.product.prodname_dotcom %} 为工作流中配置的每个服务创建一个新的 Docker 容器，并在作业完成后销毁该服务容器。 作业中的步骤可与属于同一作业的所有服务容器通信。
-{% data reusables.github-actions.docker-container-os-support %}
+{% data reusables.actions.docker-container-os-support %}
## 与服务容器通信
diff --git a/translations/zh-CN/content/actions/using-containerized-services/creating-postgresql-service-containers.md b/translations/zh-CN/content/actions/using-containerized-services/creating-postgresql-service-containers.md
index 560d8746976a..b45e837b3a07 100644
--- a/translations/zh-CN/content/actions/using-containerized-services/creating-postgresql-service-containers.md
+++ b/translations/zh-CN/content/actions/using-containerized-services/creating-postgresql-service-containers.md
@@ -24,11 +24,11 @@ topics:
本指南演示了使用 Docker Hub `postgres` 映像配置服务容器的工作流程示例。 工作流程运行一个脚本，以连接到 PostgreSQL 服务，创建一个表，然后用数据填充该表。 为了测试工作流程是否创建并填充 PostgreSQL 表，脚本会将表中的数据打印到控制台。
-{% data reusables.github-actions.docker-container-os-support %}
+{% data reusables.actions.docker-container-os-support %}
## 基本要求
-{% data reusables.github-actions.service-container-prereqs %}
+{% data reusables.actions.service-container-prereqs %}
你可能还会发现它也有助于基本了解 YAML、{% data variables.product.prodname_actions %} 的语法和 PostgreSQL。 更多信息请参阅：
@@ -37,9 +37,9 @@ topics:
## 在容器中运行作业
-{% data reusables.github-actions.container-jobs-intro %}
+{% data reusables.actions.container-jobs-intro %}
-{% data reusables.github-actions.copy-workflow-file %}
+{% data reusables.actions.copy-workflow-file %}
{% raw %}
```yaml{:copy}
@@ -95,9 +95,9 @@ jobs:
### 配置运行器作业
-{% data reusables.github-actions.service-container-host %}
+{% data reusables.actions.service-container-host %}
-{% data reusables.github-actions.postgres-label-description %}
+{% data reusables.actions.postgres-label-description %}
```yaml{:copy}
jobs:
@@ -127,7 +127,7 @@ jobs:
### 配置步骤
-{% data reusables.github-actions.service-template-steps %}
+{% data reusables.actions.service-template-steps %}
```yaml{:copy}
steps:
@@ -153,7 +153,7 @@ steps:
POSTGRES_PORT: 5432
```
-{% data reusables.github-actions.postgres-environment-variables %}
+{% data reusables.actions.postgres-environment-variables %}
PostgreSQL 文档中的服务的主机名是您在工作流程中配置的标签，本例中为 `postgres`。 由于同一用户定义的网桥网络上的 Docker 容器默认打开所有端口，因此您将能够访问默认 PostgreSQL 端口 5432 上的服务容器。
@@ -161,7 +161,7 @@ PostgreSQL 文档中的服务的主机名是您在工作流程中配置的标签
直接在运行器机器上运行作业时，需要将服务容器上的端口映射到 Docker 主机上的端口。 您可以使用 `localhost` 和 Docker 主机端口号从 Docker 主机访问服务容器。
-{% data reusables.github-actions.copy-workflow-file %}
+{% data reusables.actions.copy-workflow-file %}
{% raw %}
```yaml{:copy}
@@ -219,9 +219,9 @@ jobs:
### 配置运行器作业
-{% data reusables.github-actions.service-container-host-runner %}
+{% data reusables.actions.service-container-host-runner %}
-{% data reusables.github-actions.postgres-label-description %}
+{% data reusables.actions.postgres-label-description %}
工作流程将 PostgreSQL 服务容器上的端口 5432 映射到 Docker 主机。 有关 `ports` 关键字的更多信息，请参阅“[关于服务容器](/actions/automating-your-workflow-with-github-actions/about-service-containers#mapping-docker-host-and-service-container-ports)”。
@@ -254,7 +254,7 @@ jobs:
### 配置步骤
-{% data reusables.github-actions.service-template-steps %}
+{% data reusables.actions.service-template-steps %}
```yaml{:copy}
steps:
@@ -280,9 +280,9 @@ steps:
POSTGRES_PORT: 5432
```
-{% data reusables.github-actions.postgres-environment-variables %}
+{% data reusables.actions.postgres-environment-variables %}
-{% data reusables.github-actions.service-container-localhost %}
+{% data reusables.actions.service-container-localhost %}
## 测试 PostgreSQL 服务容器
@@ -290,7 +290,7 @@ steps:
您可以修改 *client.js* 以包含工作流程需要的任何 PostgreSQL 操作。 在本例中，脚本连接到 PostgreSQL 服务，向 `postgres` 数据库添加一个表，插入一些占位符数据，然后检索数据。
-{% data reusables.github-actions.service-container-add-script %}
+{% data reusables.actions.service-container-add-script %}
```javascript{:copy}
const { Client } = require('pg');
diff --git a/translations/zh-CN/content/actions/using-containerized-services/creating-redis-service-containers.md b/translations/zh-CN/content/actions/using-containerized-services/creating-redis-service-containers.md
index dba2e77520b1..a3bb22b64b44 100644
--- a/translations/zh-CN/content/actions/using-containerized-services/creating-redis-service-containers.md
+++ b/translations/zh-CN/content/actions/using-containerized-services/creating-redis-service-containers.md
@@ -24,11 +24,11 @@ topics:
本指南演示了使用 Docker Hub `redis` 映像配置服务容器的工作流程示例。 工作流程运行脚本来创建 Redis 客户端并使用数据填充客户端。 要测试工作流程是否创建并填充 Redis 客户端，脚本会将客户端数据打印到控制台。
-{% data reusables.github-actions.docker-container-os-support %}
+{% data reusables.actions.docker-container-os-support %}
## 基本要求
-{% data reusables.github-actions.service-container-prereqs %}
+{% data reusables.actions.service-container-prereqs %}
你可能还会发现它也有助于基本了解 YAML、{% data variables.product.prodname_actions %} 的语法和 Redis。 更多信息请参阅：
@@ -37,9 +37,9 @@ topics:
## 在容器中运行作业
-{% data reusables.github-actions.container-jobs-intro %}
+{% data reusables.actions.container-jobs-intro %}
-{% data reusables.github-actions.copy-workflow-file %}
+{% data reusables.actions.copy-workflow-file %}
{% raw %}
```yaml{:copy}
@@ -92,9 +92,9 @@ jobs:
### 配置容器作业
-{% data reusables.github-actions.service-container-host %}
+{% data reusables.actions.service-container-host %}
-{% data reusables.github-actions.redis-label-description %}
+{% data reusables.actions.redis-label-description %}
```yaml{:copy}
jobs:
@@ -121,7 +121,7 @@ jobs:
### 配置步骤
-{% data reusables.github-actions.service-template-steps %}
+{% data reusables.actions.service-template-steps %}
```yaml{:copy}
steps:
@@ -146,7 +146,7 @@ steps:
REDIS_PORT: 6379
```
-{% data reusables.github-actions.redis-environment-variables %}
+{% data reusables.actions.redis-environment-variables %}
Redis 服务的主机名是您在工作流程中配置的标签，本例中为 `redis`。 由于同一用户定义的网桥网络上的 Docker 容器默认打开所有端口，因此您将能够访问默认 Redis 端口 6379 上的服务容器。
@@ -154,7 +154,7 @@ Redis 服务的主机名是您在工作流程中配置的标签，本例中为 `
直接在运行器机器上运行作业时，需要将服务容器上的端口映射到 Docker 主机上的端口。 您可以使用 `localhost` 和 Docker 主机端口号从 Docker 主机访问服务容器。
-{% data reusables.github-actions.copy-workflow-file %}
+{% data reusables.actions.copy-workflow-file %}
{% raw %}
```yaml{:copy}
@@ -209,9 +209,9 @@ jobs:
### 配置运行器作业
-{% data reusables.github-actions.service-container-host-runner %}
+{% data reusables.actions.service-container-host-runner %}
-{% data reusables.github-actions.redis-label-description %}
+{% data reusables.actions.redis-label-description %}
工作流程将 Redis 服务容器上的端口 6379 映射到 Docker 主机。 有关 `ports` 关键字的更多信息，请参阅“[关于服务容器](/actions/automating-your-workflow-with-github-actions/about-service-containers#mapping-docker-host-and-service-container-ports)”。
@@ -241,7 +241,7 @@ jobs:
### 配置步骤
-{% data reusables.github-actions.service-template-steps %}
+{% data reusables.actions.service-template-steps %}
```yaml{:copy}
steps:
@@ -267,9 +267,9 @@ steps:
REDIS_PORT: 6379
```
-{% data reusables.github-actions.redis-environment-variables %}
+{% data reusables.actions.redis-environment-variables %}
-{% data reusables.github-actions.service-container-localhost %}
+{% data reusables.actions.service-container-localhost %}
## 测试 Redis 服务容器
@@ -277,7 +277,7 @@ steps:
您可以修改 *client.js* 以包含工作流程需要的任何 Redis 操作。 在此示例中，脚本创建 Redis 客户端实例、添加占位符数据，然后检索数据。
-{% data reusables.github-actions.service-container-add-script %}
+{% data reusables.actions.service-container-add-script %}
```javascript{:copy}
const redis = require("redis");
diff --git a/translations/zh-CN/content/actions/using-github-hosted-runners/about-github-hosted-runners.md b/translations/zh-CN/content/actions/using-github-hosted-runners/about-github-hosted-runners.md
index 662d33b84ffa..0021f07728f9 100644
--- a/translations/zh-CN/content/actions/using-github-hosted-runners/about-github-hosted-runners.md
+++ b/translations/zh-CN/content/actions/using-github-hosted-runners/about-github-hosted-runners.md
@@ -29,7 +29,7 @@ You can specify the runner type for each job in a workflow. Each job in a workfl
{% ifversion not ghes %}
-{% data reusables.github-actions.runner-app-open-source %}
+{% data reusables.actions.runner-app-open-source %}
### Cloud hosts for {% data variables.product.prodname_dotcom %}-hosted runners
@@ -39,7 +39,7 @@ You can specify the runner type for each job in a workflow. Each job in a workfl
### Workflow continuity for {% data variables.product.prodname_dotcom %}-hosted runners
-{% data reusables.github-actions.runner-workflow-continuity %}
+{% data reusables.actions.runner-workflow-continuity %}
In addition, if the workflow run has been successfully queued, but has not been processed by a {% data variables.product.prodname_dotcom %}-hosted runner within 45 minutes, then the queued workflow run is discarded.
@@ -61,7 +61,7 @@ Hardware specification for macOS virtual machines:
- 14 GB of RAM memory
- 14 GB of SSD disk space
-{% data reusables.github-actions.supported-github-runners %}
+{% data reusables.actions.supported-github-runners %}
Workflow logs list the runner used to run a job. For more information, see "[Viewing workflow run history](/actions/managing-workflow-runs/viewing-workflow-run-history)."
diff --git a/translations/zh-CN/content/actions/using-github-hosted-runners/monitoring-your-current-jobs.md b/translations/zh-CN/content/actions/using-github-hosted-runners/monitoring-your-current-jobs.md
index ac5027e2afb7..f1d8a12e1fcf 100644
--- a/translations/zh-CN/content/actions/using-github-hosted-runners/monitoring-your-current-jobs.md
+++ b/translations/zh-CN/content/actions/using-github-hosted-runners/monitoring-your-current-jobs.md
@@ -13,8 +13,8 @@ shortTitle: Monitoring your current jobs
You can get a list of all jobs currently running on {% data variables.product.prodname_dotcom %}-hosted runners in your organization or enterprise.
-{% data reusables.github-actions.github-hosted-runners-navigate-to-repo-org-enterprise %}
-{% data reusables.github-actions.github-hosted-runners-table-entry %}
+{% data reusables.actions.github-hosted-runners-navigate-to-repo-org-enterprise %}
+{% data reusables.actions.github-hosted-runners-table-entry %}
1. Review the "Active jobs" section, which contains a list of all jobs currently running on {% data variables.product.prodname_dotcom %}-hosted runners.
@@ -25,6 +25,6 @@ You can get a list of all jobs currently running on {% data variables.product.pr
The following procedure demonstrates how to check the maximum number of concurrent jobs you can run.
-{% data reusables.github-actions.github-hosted-runners-navigate-to-repo-org-enterprise %}
-{% data reusables.github-actions.github-hosted-runners-table-entry %}
+{% data reusables.actions.github-hosted-runners-navigate-to-repo-org-enterprise %}
+{% data reusables.actions.github-hosted-runners-table-entry %}
1. Review the "All jobs usage" section, which lists the number of active jobs and the maximum number of jobs you can run. In this example, `9` jobs are currently running out of a maximum of `180`. 
diff --git a/translations/zh-CN/content/actions/using-jobs/using-concurrency.md b/translations/zh-CN/content/actions/using-jobs/using-concurrency.md
index d4f792b70713..9fcc88997fe3 100644
--- a/translations/zh-CN/content/actions/using-jobs/using-concurrency.md
+++ b/translations/zh-CN/content/actions/using-jobs/using-concurrency.md
@@ -20,5 +20,5 @@ miniTocMaxHeadingLevel: 4
{% if github-runner-dashboard %}
## 监控组织或企业中的当前作业
-{% data reusables.github-actions.github-hosted-runners-check-concurrency %}
+{% data reusables.actions.github-hosted-runners-check-concurrency %}
{% 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 6925a74d6dcd..c16f2cd0c657 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
@@ -37,7 +37,7 @@ Some events have multiple activity types. For these events, you can specify whic
{% endnote %}
-{% data reusables.github-actions.branch-requirement %}
+{% data reusables.actions.branch-requirement %}
Runs your workflow when branch protection rules in the workflow repository are changed. For more information about branch protection rules, see "[About protected branches](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches)." For information about the branch protection rule APIs, see "[BranchProtectionRule](/graphql/reference/objects#branchprotectionrule)" in the GraphQL API documentation or "[Branches](/rest/reference/branches)" in the REST API documentation.
@@ -64,7 +64,7 @@ on:
{% endnote %}
-{% data reusables.github-actions.branch-requirement %}
+{% data reusables.actions.branch-requirement %}
Runs your workflow when activity related to a check run occurs. 检查运行是检查套件中的单个测试。 For information, see "[Getting started with the Checks API](/rest/guides/getting-started-with-the-checks-api)." For information about the check run APIs, see "[CheckRun](/graphql/reference/objects#checkrun)" in the GraphQL API documentation or "[Checks](/rest/reference/checks#runs)" in the REST API documentation.
@@ -88,7 +88,7 @@ on:
{% endnote %}
-{% data reusables.github-actions.branch-requirement %}
+{% data reusables.actions.branch-requirement %}
{% note %}
@@ -133,7 +133,7 @@ on:
| ---------------------------------------------------------------------------------------- | ---- | ------------ | ------------ |
| [`delete`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads/#delete) | n/a | 默认分支上的最新提交 | 默认分支 |
-{% data reusables.github-actions.branch-requirement %}
+{% data reusables.actions.branch-requirement %}
{% note %}
@@ -199,7 +199,7 @@ on:
{% endnote %}
-{% data reusables.github-actions.branch-requirement %}
+{% data reusables.actions.branch-requirement %}
{% data reusables.webhooks.discussions-webhooks-beta %}
@@ -225,7 +225,7 @@ on:
{% endnote %}
-{% data reusables.github-actions.branch-requirement %}
+{% data reusables.actions.branch-requirement %}
{% data reusables.webhooks.discussions-webhooks-beta %}
@@ -247,7 +247,7 @@ on:
| ---------------------------------------------------------------------------------- | ---- | ------------ | ------------ |
| [`复刻`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads/#fork) | n/a | 默认分支上的最新提交 | 默认分支 |
-{% data reusables.github-actions.branch-requirement %}
+{% data reusables.actions.branch-requirement %}
Runs your workflow when someone forks a repository. 有关 REST API 的信息，请参阅“[创建复刻](/rest/reference/repos#create-a-fork)”。
@@ -264,7 +264,7 @@ on:
| ---------------------------------------------------------------------------------------- | ---- | ------------ | ------------ |
| [`gollum`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads/#gollum) | n/a | 默认分支上的最新提交 | 默认分支 |
-{% data reusables.github-actions.branch-requirement %}
+{% data reusables.actions.branch-requirement %}
Runs your workflow when someone creates or updates a Wiki page. 更多信息请参阅“[关于 wiki](/communities/documenting-your-project-with-wikis/about-wikis)”。
@@ -287,7 +287,7 @@ on:
{% endnote %}
-{% data reusables.github-actions.branch-requirement %}
+{% data reusables.actions.branch-requirement %}
Runs your workflow when an issue or pull request comment is created, edited, or deleted. For information about the issue comment APIs, see "[IssueComment](/graphql/reference/objects#issuecomment)" in the GraphQL API documentation or "[Issue comments](/developers/webhooks-and-events/webhook-events-and-payloads#issue_comment)" in the REST API documentation.
@@ -344,7 +344,7 @@ jobs:
{% endnote %}
-{% data reusables.github-actions.branch-requirement %}
+{% data reusables.actions.branch-requirement %}
Runs your workflow when an issue in the workflow's repository is created or modified. For activity related to comments in an issue, use the [`issue_comment`](#issue_comment) event. 有关议题的更多信息，请参阅“[关于议题](/issues/tracking-your-work-with-issues/about-issues)”。 For information about the issue APIs, see "[Issue](/graphql/reference/objects#issue)" in the GraphQL API documentation or "[Issues](/rest/reference/issues)" in the REST API documentation.
@@ -368,7 +368,7 @@ on:
{% endnote %}
-{% data reusables.github-actions.branch-requirement %}
+{% data reusables.actions.branch-requirement %}
Runs your workflow when a label in your workflow's repository is created or modified. For more information about labels, see "[Managing labels](/issues/using-labels-and-milestones-to-track-work/managing-labels)." For information about the label APIs, see "[Label](/graphql/reference/objects#label)" in the GraphQL API documentation or "[Labels](/rest/reference/issues#labels)" in the REST API documentation.
@@ -394,7 +394,7 @@ on:
{% endnote %}
-{% data reusables.github-actions.branch-requirement %}
+{% data reusables.actions.branch-requirement %}
Runs your workflow when a milestone in the workflow's repository is created or modified. For more information about milestones, see "[About milestones](/issues/using-labels-and-milestones-to-track-work/about-milestones)." For information about the milestone APIs, see "[Milestone](/graphql/reference/objects#milestone)" in the GraphQL API documentation or "[Milestones](/rest/reference/issues#milestones)" in the REST API documentation.
@@ -414,7 +414,7 @@ on:
| ------------------------------------------------------------------------------------------------ | ---- | ------------ | ------------ |
| [`page_build`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads/#page_build) | n/a | 默认分支上的最新提交 | n/a |
-{% data reusables.github-actions.branch-requirement %}
+{% data reusables.actions.branch-requirement %}
Runs your workflow when someone pushes to a branch that is the publishing source for {% data variables.product.prodname_pages %}, if {% data variables.product.prodname_pages %} is enabled for the repository. For more information about {% data variables.product.prodname_pages %} publishing sources, see "[Configuring a publishing source for your GitHub Pages site](/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site#choosing-a-publishing-source)." 有关 REST API 的信息，请参阅“[页面](/rest/reference/repos#pages)”。
@@ -437,7 +437,7 @@ on:
{% endnote %}
-{% data reusables.github-actions.branch-requirement %}
+{% data reusables.actions.branch-requirement %}
{% note %}
@@ -475,7 +475,7 @@ on:
{% endnote %}
-{% data reusables.github-actions.branch-requirement %}
+{% data reusables.actions.branch-requirement %}
{% note %}
@@ -513,7 +513,7 @@ on:
{% endnote %}
-{% data reusables.github-actions.branch-requirement %}
+{% data reusables.actions.branch-requirement %}
{% note %}
@@ -545,7 +545,7 @@ on:
| ---------------------------------------------------------------------------------------- | ---- | ------------ | ------------ |
| [`public`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads/#public) | n/a | 默认分支上的最新提交 | 默认分支 |
-{% data reusables.github-actions.branch-requirement %}
+{% data reusables.actions.branch-requirement %}
Runs your workflow when your workflow's repository changes from private to public. 有关 REST API 的信息，请参阅“[编辑仓库](/rest/reference/repos#edit)”。
@@ -625,7 +625,7 @@ on:
{% note %}
-**Note:** {% data reusables.github-actions.branch-paths-filter %} For example, the following workflow will only run when a pull request that includes a change to a JavaScript (`.js`) file is opened on a branch whose name starts with `releases/`:
+**Note:** {% data reusables.actions.branch-paths-filter %} For example, the following workflow will only run when a pull request that includes a change to a JavaScript (`.js`) file is opened on a branch whose name starts with `releases/`:
```yaml
on:
@@ -670,7 +670,7 @@ on:
{% note %}
-**Note:** {% data reusables.github-actions.branch-paths-filter %} For example, the following workflow will only run when a pull request that includes a change to a JavaScript (`.js`) file is opened on a branch whose name starts with `releases/`:
+**Note:** {% data reusables.actions.branch-paths-filter %} For example, the following workflow will only run when a pull request that includes a change to a JavaScript (`.js`) file is opened on a branch whose name starts with `releases/`:
```yaml
on:
@@ -828,7 +828,7 @@ on:
{% note %}
-**Note:** {% data reusables.github-actions.branch-paths-filter %} For example, the following workflow will only run when a pull request that includes a change to a JavaScript (`.js`) file is opened on a branch whose name starts with `releases/`:
+**Note:** {% data reusables.actions.branch-paths-filter %} For example, the following workflow will only run when a pull request that includes a change to a JavaScript (`.js`) file is opened on a branch whose name starts with `releases/`:
```yaml
on:
@@ -873,7 +873,7 @@ on:
{% note %}
-**Note:** {% data reusables.github-actions.branch-paths-filter %} For example, the following workflow will only run when a pull request that includes a change to a JavaScript (`.js`) file is opened on a branch whose name starts with `releases/`:
+**Note:** {% data reusables.actions.branch-paths-filter %} For example, the following workflow will only run when a pull request that includes a change to a JavaScript (`.js`) file is opened on a branch whose name starts with `releases/`:
```yaml
on:
@@ -950,7 +950,7 @@ on:
{% note %}
-**Note:** {% data reusables.github-actions.branch-paths-filter %} For example, the following workflow will only run when a push that includes a change to a JavaScript (`.js`) file is made to a branch whose name starts with `releases/`:
+**Note:** {% data reusables.actions.branch-paths-filter %} For example, the following workflow will only run when a push that includes a change to a JavaScript (`.js`) file is made to a branch whose name starts with `releases/`:
```yaml
on:
@@ -991,7 +991,7 @@ on:
{% note %}
-**Note:** {% data reusables.github-actions.branch-paths-filter %} For example, the following workflow will only run when a push that includes a change to a JavaScript (`.js`) file is made to a branch whose name starts with `releases/`:
+**Note:** {% data reusables.actions.branch-paths-filter %} For example, the following workflow will only run when a push that includes a change to a JavaScript (`.js`) file is made to a branch whose name starts with `releases/`:
```yaml
on:
@@ -1016,7 +1016,7 @@ on:
{% endnote %}
-{% data reusables.github-actions.branch-requirement %}
+{% data reusables.actions.branch-requirement %}
Runs your workflow when activity related to {% data variables.product.prodname_registry %} occurs in your repository. 更多信息请参阅“[{% data variables.product.prodname_registry %} 文档](/packages)”。
@@ -1068,7 +1068,7 @@ on:
| ---------------------------------------------------------------------------------------------------------------- | ---- | ------------ | ------------ |
| [repository_dispatch](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads/#repository_dispatch) | 自定义 | 默认分支上的最新提交 | 默认分支 |
-{% data reusables.github-actions.branch-requirement %}
+{% data reusables.actions.branch-requirement %}
当您想要触发在 {% data variables.product.product_name %} 外发生的活动的工作流程时，可以使用 {% data variables.product.product_name %} API 触发名为 [`repository_dispatch`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads/#repository_dispatch) 的 web 挂钩事件。 更多信息请参阅“[创建仓库调度事件](/rest/reference/repos#create-a-repository-dispatch-event)”。
@@ -1160,7 +1160,7 @@ jobs:
| ------------------------------------------------------------------------------------ | ---- | ------------ | ------------ |
| [`状态`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads/#status) | n/a | 默认分支上的最新提交 | n/a |
-{% data reusables.github-actions.branch-requirement %}
+{% data reusables.actions.branch-requirement %}
Runs your workflow when the status of a Git commit changes. For example, commits can be marked as `error`, `failure`, `pending`, or `success`. If you want to provide more details about the status change, you may want to use the [`check_run`](#check_run) event. For information about the commit status APIs, see "[Status](/graphql/reference/objects#statue)" in the GraphQL API documentation or "[Statuses](/rest/reference/commits#commit-statuses)" in the REST API documentation.
@@ -1201,7 +1201,7 @@ jobs:
{% endnote %}
-{% data reusables.github-actions.branch-requirement %}
+{% data reusables.actions.branch-requirement %}
Runs your workflow when the workflow's repository is starred. For information about the pull request APIs, see "[addStar](/graphql/reference/mutations#addstar)" in the GraphQL API documentation or "[Starring](/rest/reference/activity#starring)" in the REST API documentation.
@@ -1343,7 +1343,7 @@ jobs:
{% endnote %}
-{% data reusables.github-actions.branch-requirement %}
+{% data reusables.actions.branch-requirement %}
{% note %}
diff --git a/translations/zh-CN/content/actions/using-workflows/sharing-workflows-secrets-and-runners-with-your-organization.md b/translations/zh-CN/content/actions/using-workflows/sharing-workflows-secrets-and-runners-with-your-organization.md
index 41a61bec16b8..f95aa2f4cdff 100644
--- a/translations/zh-CN/content/actions/using-workflows/sharing-workflows-secrets-and-runners-with-your-organization.md
+++ b/translations/zh-CN/content/actions/using-workflows/sharing-workflows-secrets-and-runners-with-your-organization.md
@@ -50,11 +50,11 @@ Your organization can share workflows by reusing the workflows exactly or by cre
在组织中创建密码时，可以使用策略来限制可以访问该密码的仓库。 例如，您可以将访问权限授予所有仓库，也可以限制仅私有仓库或指定的仓库列表拥有访问权限。
-{% data reusables.github-actions.permissions-statement-secrets-organization %}
+{% data reusables.actions.permissions-statement-secrets-organization %}
{% data reusables.organizations.navigate-to-org %}
{% data reusables.organizations.org_settings %}
-{% data reusables.github-actions.sidebar-secret %}
+{% data reusables.actions.sidebar-secret %}
1. 单击 **New secret（新建密码）**。
1. 在 **Name（名称）**输入框中键入密码的名称。
1. 输入密码的 **Value（值）**。
diff --git a/translations/zh-CN/content/actions/using-workflows/storing-workflow-data-as-artifacts.md b/translations/zh-CN/content/actions/using-workflows/storing-workflow-data-as-artifacts.md
index d550fa861d52..e05fdb34574a 100644
--- a/translations/zh-CN/content/actions/using-workflows/storing-workflow-data-as-artifacts.md
+++ b/translations/zh-CN/content/actions/using-workflows/storing-workflow-data-as-artifacts.md
@@ -26,7 +26,7 @@ topics:
Artifacts allow you to persist data after a job has completed, and share that data with another job in the same workflow. An artifact is a file or collection of files produced during a workflow run. For example, you can use artifacts to save your build and test output after a workflow run has ended. {% data reusables.actions.reusable-workflow-artifacts %}
-{% data reusables.github-actions.artifact-log-retention-statement %} The retention period for a pull request restarts each time someone pushes a new commit to the pull request.
+{% data reusables.actions.artifact-log-retention-statement %} The retention period for a pull request restarts each time someone pushes a new commit to the pull request.
These are some of the common artifacts that you can upload:
@@ -37,7 +37,7 @@ These are some of the common artifacts that you can upload:
{% ifversion fpt or ghec %}
-Storing artifacts uses storage space on {% data variables.product.product_name %}. {% data reusables.github-actions.actions-billing %} For more information, see "[Managing billing for {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions)."
+Storing artifacts uses storage space on {% data variables.product.product_name %}. {% data reusables.actions.actions-billing %} For more information, see "[Managing billing for {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions)."
{% else %}
diff --git a/translations/zh-CN/content/actions/using-workflows/triggering-a-workflow.md b/translations/zh-CN/content/actions/using-workflows/triggering-a-workflow.md
index 7e27b44a36d5..ddfea0675bbb 100644
--- a/translations/zh-CN/content/actions/using-workflows/triggering-a-workflow.md
+++ b/translations/zh-CN/content/actions/using-workflows/triggering-a-workflow.md
@@ -41,9 +41,9 @@ Workflow triggers are defined with the `on` key. 更多信息请参阅“[{% dat
### Triggering a workflow from a workflow
-{% data reusables.github-actions.actions-do-not-trigger-workflows %} 更多信息请参阅“[使用 GITHUB_TOKEN 验证身份](/actions/configuring-and-managing-workflows/authenticating-with-the-github_token)”。
+{% data reusables.actions.actions-do-not-trigger-workflows %} For more information, see "[Authenticating with the GITHUB_TOKEN](/actions/configuring-and-managing-workflows/authenticating-with-the-github_token)."
-If you do want to trigger a workflow from within a workflow run, you can use a personal access token instead of `GITHUB_TOKEN` to trigger events that require a token. 您需要创建个人访问令牌并将其存储为密码。 为了最大限度地降低 {% data variables.product.prodname_actions %} 使用成本，请确保不要创建递归或意外的工作流程。 For more information about creating a personal access token, see "[Creating a personal access token](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)." For more information about storing a personal access token as a secret, see "[Creating and storing encrypted secrets](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets)."
+If you do want to trigger a workflow from within a workflow run, you can use a personal access token instead of `GITHUB_TOKEN` to trigger events that require a token. 您需要创建个人访问令牌并将其存储为密码。 为了最大限度地降低 {% data variables.product.prodname_actions %} 使用成本，请确保不要创建递归或意外的工作流程。 有关创建个人访问令牌的更多信息，请参阅“[创建个人访问令牌](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)”。 For more information about storing a personal access token as a secret, see "[Creating and storing encrypted secrets](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets)."
For example, the following workflow uses a personal access token (stored as a secret called `MY_TOKEN`) to add a label to an issue via {% data variables.product.prodname_cli %}. Any workflows that run when a label is added will run once this step is performed.
@@ -89,23 +89,23 @@ Use the `on` key to specify what events trigger your workflow. For more informat
### Using a single event
-{% data reusables.github-actions.on-single-example %}
+{% data reusables.actions.on-single-example %}
### Using multiple events
-{% data reusables.github-actions.on-multiple-example %}
+{% data reusables.actions.on-multiple-example %}
### Using activity types and filters with multiple events
-You can use activity types and filters to further control when your workflow will run. For more information, see [Using event activity types](#using-event-activity-types) and [Using filters](#using-filters). {% data reusables.github-actions.actions-multiple-types %}
+You can use activity types and filters to further control when your workflow will run. For more information, see [Using event activity types](#using-event-activity-types) and [Using filters](#using-filters). {% data reusables.actions.actions-multiple-types %}
## Using event activity types
-{% data reusables.github-actions.actions-activity-types %}
+{% data reusables.actions.actions-activity-types %}
## Using filters
-{% data reusables.github-actions.actions-filters %}
+{% data reusables.actions.actions-filters %}
### Using filters to target specific branches for pull request events
@@ -125,7 +125,7 @@ You can use activity types and filters to further control when your workflow wil
## Defining inputs for manually triggered workflows
-{% data reusables.github-actions.workflow-dispatch-inputs %}
+{% data reusables.actions.workflow-dispatch-inputs %}
{% ifversion fpt or ghes > 3.3 or ghae-issue-4757 or ghec %}
## Defining inputs, outputs, and secrets for reusable workflows
diff --git a/translations/zh-CN/content/actions/using-workflows/workflow-syntax-for-github-actions.md b/translations/zh-CN/content/actions/using-workflows/workflow-syntax-for-github-actions.md
index 09f0676a241b..bd19ee3f15d2 100644
--- a/translations/zh-CN/content/actions/using-workflows/workflow-syntax-for-github-actions.md
+++ b/translations/zh-CN/content/actions/using-workflows/workflow-syntax-for-github-actions.md
@@ -173,7 +173,7 @@ A boolean specifying whether the secret must be supplied.
## `on.workflow_dispatch.inputs`
-{% data reusables.github-actions.workflow-dispatch-inputs %}
+{% data reusables.actions.workflow-dispatch-inputs %}
{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
## `权限`
@@ -184,7 +184,7 @@ A boolean specifying whether the secret must be supplied.
## `env`
-A `map` of environment variables that are available to the steps of all jobs in the workflow. You can also set environment variables that are only available to the steps of a single job or to a single step. For more information, see [`jobs..env`](#jobsjob_idenv) and [`jobs..steps[*].env`](#jobsjob_idstepsenv).
+环境变量的 `map` 可用于工作流程中所有作业的步骤。 您还可以设置仅适用于单个作业的步骤或单个步骤的环境变量。 更多信息请参阅 [`jobs..env`](#jobsjob_idenv) and [`jobs..steps[*].env`](#jobsjob_idstepsenv)。
{% data reusables.repositories.actions-env-var-note %}
@@ -259,7 +259,7 @@ env:
## `jobs..env`
-A `map` of environment variables that are available to all steps in the job. You can also set environment variables for the entire workflow or an individual step. For more information, see [`env`](#env) and [`jobs..steps[*].env`](#jobsjob_idstepsenv).
+环境变量的 `map` 可用于作业中的所有步骤。 您也可以设置整个工作流程或单个步骤的环境变量。 更多信息请参阅 [`env`](#env) 和 [`jobs..steps[*].env`](#jobsjob_idstepsenv)。
{% data reusables.repositories.actions-env-var-note %}
@@ -282,9 +282,9 @@ jobs:
## `jobs..steps`
-A job contains a sequence of tasks called `steps`. Steps can run commands, run setup tasks, or run an action in your repository, a public repository, or an action published in a Docker registry. Not all steps run actions, but all actions run as a step. Each step runs in its own process in the runner environment and has access to the workspace and filesystem. Because steps run in their own process, changes to environment variables are not preserved between steps. {% data variables.product.prodname_dotcom %} provides built-in steps to set up and complete a job.
+作业包含一系列任务，称为 `steps`。 步骤可以运行命令、运行设置任务，或者运行您的仓库、公共仓库中的操作或 Docker 注册表中发布的操作。 并非所有步骤都会运行操作，但所有操作都会作为步骤运行。 每个步骤在运行器环境中以其自己的进程运行，且可以访问工作区和文件系统。 因为步骤以自己的进程运行，所以步骤之间不会保留环境变量的更改。 {% data variables.product.prodname_dotcom %} 提供内置的步骤来设置和完成作业。
-You can run an unlimited number of steps as long as you are within the workflow usage limits. For more information, see {% ifversion fpt or ghec or ghes %}"[Usage limits and billing](/actions/reference/usage-limits-billing-and-administration)" for {% data variables.product.prodname_dotcom %}-hosted runners and {% endif %}"[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners/#usage-limits){% ifversion fpt or ghec or ghes %}" for self-hosted runner usage limits.{% elsif ghae %}."{% endif %}
+在工作流程的使用限制之内可运行无限数量的步骤。 For more information, see {% ifversion fpt or ghec or ghes %}"[Usage limits and billing](/actions/reference/usage-limits-billing-and-administration)" for {% data variables.product.prodname_dotcom %}-hosted runners and {% endif %}"[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners/#usage-limits){% ifversion fpt or ghec or ghes %}" for self-hosted runner usage limits.{% elsif ghae %}."{% endif %}
### 示例
@@ -312,13 +312,13 @@ jobs:
### `jobs..steps[*].id`
-A unique identifier for the step. 您可以使用 `id` 引用上下文中的步骤。 更多信息请参阅“[上下文](/actions/learn-github-actions/contexts)”。
+步骤的唯一标识符。 您可以使用 `id` 引用上下文中的步骤。 更多信息请参阅“[上下文](/actions/learn-github-actions/contexts)”。
### `jobs..steps[*].if`
-You can use the `if` conditional to prevent a step from running unless a condition is met. 您可以使用任何支持上下文和表达式来创建条件。
+您可以使用 `if` 条件阻止步骤在条件得到满足之前运行。 您可以使用任何支持上下文和表达式来创建条件。
-{% data reusables.github-actions.expression-syntax-if %} For more information, see "[Expressions](/actions/learn-github-actions/expressions)."
+{% data reusables.actions.expression-syntax-if %} For more information, see "[Expressions](/actions/learn-github-actions/expressions)."
#### 示例：使用上下文
@@ -333,7 +333,7 @@ steps:
#### 示例：使用状态检查功能
-The `my backup step` only runs when the previous step of a job fails. For more information, see "[Expressions](/actions/learn-github-actions/expressions#job-status-check-functions)."
+`my backup step` 仅在作业的上一步失败时运行。 For more information, see "[Expressions](/actions/learn-github-actions/expressions#job-status-check-functions)."
```yaml
steps:
@@ -346,20 +346,20 @@ steps:
### `jobs..steps[*].name`
-A name for your step to display on {% data variables.product.prodname_dotcom %}.
+步骤显示在 {% data variables.product.prodname_dotcom %} 上的名称。
### `jobs..steps[*].uses`
-Selects an action to run as part of a step in your job. 操作是一种可重复使用的代码单位。 您可以使用工作流程所在仓库中、公共仓库中或[发布 Docker 容器映像](https://hub.docker.com/)中定义的操作。
+选择要作为作业中步骤的一部分运行的操作。 操作是一种可重复使用的代码单位。 您可以使用工作流程所在仓库中、公共仓库中或[发布 Docker 容器映像](https://hub.docker.com/)中定义的操作。
强烈建议指定 Git ref、SHA 或 Docker 标记编号来包含所用操作的版本。 如果不指定版本，在操作所有者发布更新时可能会中断您的工作流程或造成非预期的行为。
- 使用已发行操作版本的 SHA 对于稳定性和安全性是最安全的。
- 使用特定主要操作版本可在保持兼容性的同时接收关键修复和安全补丁。 还可确保您的工作流程继续工作。
- 使用操作的默认分支可能很方便，但如果有人新发布具有突破性更改的主要版本，您的工作流程可能会中断。
-Some actions require inputs that you must set using the [`with`](#jobsjob_idstepswith) keyword. 请查阅操作的自述文件，确定所需的输入。
+有些操作要求必须通过 [`with`](#jobsjob_idstepswith) 关键词设置输入。 请查阅操作的自述文件，确定所需的输入。
-Actions are either JavaScript files or Docker containers. If the action you're using is a Docker container you must run the job in a Linux environment. For more details, see [`runs-on`](#jobsjob_idruns-on).
+操作为 JavaScript 文件或 Docker 容器。 如果您使用的操作是 Docker 容器，则必须在 Linux 环境中运行作业。 更多详情请参阅 [`runs-on`](#jobsjob_idruns-on)。
#### 示例：使用版本化操作
@@ -379,7 +379,7 @@ steps:
`{owner}/{repo}@{ref}`
-You can specify a branch, ref, or SHA in a public {% data variables.product.prodname_dotcom %} repository.
+您可以指定公共 {% data variables.product.prodname_dotcom %} 仓库中的分支、引用或 SHA。
```yaml
jobs:
@@ -397,7 +397,7 @@ jobs:
`{owner}/{repo}/{path}@{ref}`
-A subdirectory in a public {% data variables.product.prodname_dotcom %} repository at a specific branch, ref, or SHA.
+公共 {% data variables.product.prodname_dotcom %} 仓库中特定分支、引用或 SHA 上的子目录。
```yaml
jobs:
@@ -411,7 +411,7 @@ jobs:
`./path/to/dir`
-The path to the directory that contains the action in your workflow's repository. You must check out your repository before using the action.
+包含工作流程的仓库中操作的目录路径。 在使用操作之前，必须检出仓库。
```yaml
jobs:
@@ -427,7 +427,7 @@ jobs:
`docker://{image}:{tag}`
-A Docker image published on [Docker Hub](https://hub.docker.com/).
+[Docker 中枢](https://hub.docker.com/)上发布的 Docker 映像。
```yaml
jobs:
@@ -442,7 +442,7 @@ jobs:
`docker://{host}/{image}:{tag}`
-A Docker image in the {% data variables.product.prodname_registry %} {% data variables.product.prodname_container_registry %}.
+{% data variables.product.prodname_registry %} {% data variables.product.prodname_container_registry %} 中的 Docker 映像。
```yaml
jobs:
@@ -456,7 +456,7 @@ jobs:
`docker://{host}/{image}:{tag}`
-A Docker image in a public registry. This example uses the Google Container Registry at `gcr.io`.
+公共注册表中的 Docker 映像。 此示例在 `gcr.io` 使用 Google Container Registry。
```yaml
jobs:
@@ -468,9 +468,9 @@ jobs:
#### 示例：在不同于工作流程的私有仓库中使用操作
-Your workflow must checkout the private repository and reference the action locally. Generate a personal access token and add the token as an encrypted secret. 更多信息请参阅“[创建个人访问令牌](/github/authenticating-to-github/creating-a-personal-access-token)”和“[加密密码](/actions/reference/encrypted-secrets)”。
+您的工作流程必须检出私有仓库，并在本地引用操作。 生成个人访问令牌并将该令牌添加为加密密钥。 更多信息请参阅“[创建个人访问令牌](/github/authenticating-to-github/creating-a-personal-access-token)”和“[加密密码](/actions/reference/encrypted-secrets)”。
-Replace `PERSONAL_ACCESS_TOKEN` in the example with the name of your secret.
+将示例中的 `PERSONAL_ACCESS_TOKEN` 替换为您的密钥名称。
{% raw %}
```yaml
@@ -491,11 +491,11 @@ jobs:
### `jobs..steps[*].run`
-Runs command-line programs using the operating system's shell. If you do not provide a `name`, the step name will default to the text specified in the `run` command.
+使用操作系统 shell 运行命令行程序。 如果不提供 `name`，步骤名称将默认为 `run` 命令中指定的文本。
-Commands run using non-login shells by default. You can choose a different shell and customize the shell used to run commands. For more information, see [`jobs..steps[*].shell`](#jobsjob_idstepsshell).
+命令默认使用非登录 shell 运行。 您可以选择不同的 shell，也可以自定义用于运行命令的 shell。 For more information, see [`jobs..steps[*].shell`](#jobsjob_idstepsshell).
-Each `run` keyword represents a new process and shell in the runner environment. When you provide multi-line commands, each line runs in the same shell. 例如：
+每个 `run` 关键词代表运行器环境中一个新的进程和 shell。 当您提供多行命令时，每行都在同一个 shell 中运行。 例如：
* 单行命令：
@@ -513,7 +513,7 @@ Each `run` keyword represents a new process and shell in the runner environment.
npm run build
```
-Using the `working-directory` keyword, you can specify the working directory of where to run the command.
+使用 `working-directory` 关键词，您可以指定运行命令的工作目录位置。
```yaml
- name: Clean temp directory
@@ -523,7 +523,7 @@ Using the `working-directory` keyword, you can specify the working directory of
### `jobs..steps[*].shell`
-You can override the default shell settings in the runner's operating system using the `shell` keyword. You can use built-in `shell` keywords, or you can define a custom set of shell options. The shell command that is run internally executes a temporary file that contains the commands specified in the `run` keyword.
+您可以使用 `shell` 关键词覆盖运行器操作系统中默认的 shell 设置。 您可以使用内置的 `shell` 关键词，也可以自定义 shell 选项集。 The shell command that is run internally executes a temporary file that contains the commands specified in the `run` keyword.
| 支持的平台 | `shell` 参数 | 描述 | 内部运行命令 |
| ------------- | ------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------- |
@@ -584,7 +584,7 @@ steps:
#### 自定义 shell
-You can set the `shell` value to a template string using `command […options] {0} [..more_options]`. {% data variables.product.prodname_dotcom %} interprets the first whitespace-delimited word of the string as the command, and inserts the file name for the temporary script at `{0}`.
+您可以使用 `command […options] {0} [..more_options]` 将 `shell` 值设置为模板字符串。 {% data variables.product.prodname_dotcom %} 将字符串的第一个用空格分隔的词解释为命令，并在 `{0}` 处插入临时脚本的文件名。
例如：
@@ -596,17 +596,17 @@ steps:
shell: perl {0}
```
-The command used, `perl` in this example, must be installed on the runner.
+此示例中使用的命令 `perl` 必须安装在运行器上。
{% ifversion ghae %}
{% data reusables.actions.self-hosted-runners-software %}
{% elsif fpt or ghec %}
-For information about the software included on GitHub-hosted runners, see "[Specifications for GitHub-hosted runners](/actions/reference/specifications-for-github-hosted-runners#supported-software)."
+有关 GitHub 托管运行器中所包含软件的信息，请参阅“[GitHub 托管运行器的规格](/actions/reference/specifications-for-github-hosted-runners#supported-software)”。
{% endif %}
#### 退出代码和错误操作首选项
-For built-in shell keywords, we provide the following defaults that are executed by {% data variables.product.prodname_dotcom %}-hosted runners. You should use these guidelines when running shell scripts.
+至于内置的 shell 关键词，我们提供由 {% data variables.product.prodname_dotcom %} 托管运行程序执行的以下默认值。 在运行 shell 脚本时，您应该使用这些指南。
- `bash`/`sh`：
- 使用 `set -eo pipefail` 的快速失败行为：`bash` 和内置 `shell` 的默认值。 它还是未在非 Windows 平台上提供选项时的默认值。
@@ -624,11 +624,11 @@ For built-in shell keywords, we provide the following defaults that are executed
### `jobs..steps[*].with`
-A `map` of the input parameters defined by the action. 每个输入参数都是一个键/值对。 输入参数被设置为环境变量。 The variable is prefixed with `INPUT_` and converted to upper case.
+输入参数的 `map` 由操作定义。 每个输入参数都是一个键/值对。 输入参数被设置为环境变量。 该变量的前缀为 `INPUT_`，并转换为大写。
#### 示例
-Defines the three input parameters (`first_name`, `middle_name`, and `last_name`) defined by the `hello_world` action. These input variables will be accessible to the `hello-world` action as `INPUT_FIRST_NAME`, `INPUT_MIDDLE_NAME`, and `INPUT_LAST_NAME` environment variables.
+定义 `hello_world` 操作所定义的三个输入参数（`first_name`、`middle_name` 和 `last_name`）。 这些输入变量将被 `hello-world` 操作作为 `INPUT_FIRST_NAME`、`INPUT_MIDDLE_NAME` 和 `INPUT_LAST_NAME` 环境变量使用。
```yaml
jobs:
@@ -644,7 +644,7 @@ jobs:
### `jobs..steps[*].with.args`
-A `string` that defines the inputs for a Docker container. {% data variables.product.prodname_dotcom %} 在容器启动时将 `args` 传递到容器的 `ENTRYPOINT`。 An `array of strings` is not supported by this parameter.
+`string` 定义 Docker 容器的输入。 {% data variables.product.prodname_dotcom %} 在容器启动时将 `args` 传递到容器的 `ENTRYPOINT`。 此参数不支持 `array of strings`。
#### 示例
@@ -667,7 +667,7 @@ steps:
### `jobs..steps[*].with.entrypoint`
-Overrides the Docker `ENTRYPOINT` in the `Dockerfile`, or sets it if one wasn't already specified. Unlike the Docker `ENTRYPOINT` instruction which has a shell and exec form, `entrypoint` keyword accepts only a single string defining the executable to be run.
+覆盖 `Dockerfile` 中的 Docker `ENTRYPOINT`，或在未指定时设置它。 与包含 shell 和 exec 表单的 Docker `ENTRYPOINT` 指令不同，`entrypoint` 关键词只接受定义要运行的可执行文件的单个字符串。
#### 示例
@@ -679,15 +679,15 @@ steps:
entrypoint: /a/different/executable
```
-The `entrypoint` keyword is meant to be used with Docker container actions, but you can also use it with JavaScript actions that don't define any inputs.
+`entrypoint` 关键词旨在用于 Docker 容器操作，但您也可以将其用于未定义任何输入的 JavaScript 操作。
### `jobs..steps[*].env`
-Sets environment variables for steps to use in the runner environment. You can also set environment variables for the entire workflow or a job. For more information, see [`env`](#env) and [`jobs..env`](#jobsjob_idenv).
+设置供步骤用于运行器环境的环境变量。 您也可以设置整个工作流程或某个作业的环境变量。 更多信息请参阅 [`env`](#env) 和 [`jobs..env`](#jobsjob_idenv)。
{% data reusables.repositories.actions-env-var-note %}
-Public actions may specify expected environment variables in the README file. If you are setting a secret in an environment variable, you must set secrets using the `secrets` context. For more information, see "[Using environment variables](/actions/automating-your-workflow-with-github-actions/using-environment-variables)" and "[Contexts](/actions/learn-github-actions/contexts)."
+公共操作可在自述文件中指定预期的环境变量。 如果要在环境变量中设置密码，必须使用 `secrets` 上下文进行设置。 For more information, see "[Using environment variables](/actions/automating-your-workflow-with-github-actions/using-environment-variables)" and "[Contexts](/actions/learn-github-actions/contexts)."
#### 示例
@@ -704,17 +704,17 @@ steps:
### `jobs..steps[*].continue-on-error`
-Prevents a job from failing when a step fails. Set to `true` to allow a job to pass when this step fails.
+防止步骤失败时作业也会失败。 设置为 `true` 以允许在此步骤失败时作业能够通过。
### `jobs..steps[*].timeout-minutes`
-The maximum number of minutes to run the step before killing the process.
+终止进程之前运行该步骤的最大分钟数。
## `jobs..timeout-minutes`
-The maximum number of minutes to let a job run before {% data variables.product.prodname_dotcom %} automatically cancels it. Default: 360
+在 {% data variables.product.prodname_dotcom %} 自动取消运行之前可让作业运行的最大分钟数。 默认值：360
-If the timeout exceeds the job execution time limit for the runner, the job will be canceled when the execution time limit is met instead. For more information about job execution time limits, see {% ifversion fpt or ghec or ghes %}"[Usage limits and billing](/actions/reference/usage-limits-billing-and-administration#usage-limits)" for {% data variables.product.prodname_dotcom %}-hosted runners and {% endif %}"[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners/#usage-limits){% ifversion fpt or ghec or ghes %}" for self-hosted runner usage limits.{% elsif ghae %}."{% endif %}
+如果超时超过运行器的作业执行时限，作业将在达到执行时限时取消。 For more information about job execution time limits, see {% ifversion fpt or ghec or ghes %}"[Usage limits and billing](/actions/reference/usage-limits-billing-and-administration#usage-limits)" for {% data variables.product.prodname_dotcom %}-hosted runners and {% endif %}"[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners/#usage-limits){% ifversion fpt or ghec or ghes %}" for self-hosted runner usage limits.{% elsif ghae %}."{% endif %}
## `jobs..strategy`
@@ -734,11 +734,11 @@ If the timeout exceeds the job execution time limit for the runner, the job will
## `jobs..continue-on-error`
-Prevents a workflow run from failing when a job fails. Set to `true` to allow a workflow run to pass when this job fails.
+防止工作流程运行在作业失败时失败。 设置为 `true` 以允许工作流程运行在此作业失败时通过。
### 示例：防止特定失败的矩阵作业无法运行工作流程
-You can allow specific jobs in a job matrix to fail without failing the workflow run. For example, if you wanted to only allow an experimental job with `node` set to `15` to fail without failing the workflow run.
+您可以允许作业矩阵中的特定任务失败，但工作流程运行不失败。 For example, if you wanted to only allow an experimental job with `node` set to `15` to fail without failing the workflow run.
{% raw %}
```yaml
@@ -759,7 +759,7 @@ strategy:
## `jobs..container`
-{% data reusables.github-actions.docker-container-os-support %}
+{% data reusables.actions.docker-container-os-support %}
{% data reusables.actions.jobs.section-running-jobs-in-a-container %}
@@ -789,19 +789,19 @@ strategy:
## `jobs..services`
-{% data reusables.github-actions.docker-container-os-support %}
+{% data reusables.actions.docker-container-os-support %}
-Used to host service containers for a job in a workflow. Service containers are useful for creating databases or cache services like Redis. The runner automatically creates a Docker network and manages the life cycle of the service containers.
+用于为工作流程中的作业托管服务容器。 服务容器可用于创建数据库或缓存服务（如 Redis）。 运行器自动创建 Docker 网络并管理服务容器的生命周期。
-If you configure your job to run in a container, or your step uses container actions, you don't need to map ports to access the service or action. Docker automatically exposes all ports between containers on the same Docker user-defined bridge network. You can directly reference the service container by its hostname. The hostname is automatically mapped to the label name you configure for the service in the workflow.
+如果将作业配置为在容器中运行，或者步骤使用容器操作，则无需映射端口来访问服务或操作。 Docker 会自动在同一个 Docker 用户定义的桥接网络上的容器之间显示所有端口。 您可以直接引用服务容器的主机名。 主机名自动映射到为工作流程中的服务配置的标签名称。
-If you configure the job to run directly on the runner machine and your step doesn't use a container action, you must map any required Docker service container ports to the Docker host (the runner machine). You can access the service container using localhost and the mapped port.
+如果配置作业直接在运行器机器上运行，且您的步骤不使用容器操作，则必须将任何必需的 Docker 服务容器端口映射到 Docker 主机（运行器机器）。 您可以使用 localhost 和映射的端口访问服务容器。
-For more information about the differences between networking service containers, see "[About service containers](/actions/automating-your-workflow-with-github-actions/about-service-containers)."
+有关网络服务容器之间差异的更多信息，请参阅“[关于服务容器](/actions/automating-your-workflow-with-github-actions/about-service-containers)”。
### 示例：使用 localhost
-This example creates two services: nginx and redis. 指定 Docker 主机端口但不指定容器端口时，容器端口将随机分配给空闲端口。 {% data variables.product.prodname_dotcom %} sets the assigned container port in the {% raw %}`${{job.services..ports}}`{% endraw %} context. In this example, you can access the service container ports using the {% raw %}`${{ job.services.nginx.ports['8080'] }}`{% endraw %} and {% raw %}`${{ job.services.redis.ports['6379'] }}`{% endraw %} contexts.
+此示例创建分别用于 nginx 和 redis 的两项服务。 指定 Docker 主机端口但不指定容器端口时，容器端口将随机分配给空闲端口。 {% data variables.product.prodname_dotcom %} 在 {% raw %}`${{job.services..ports}}`{% endraw %} 上下文中设置分配的容器端口。 在此示例中，可以使用 {% raw %}`${{ job.services.nginx.ports['8080'] }}`{% endraw %} 和 {% raw %}`${{ job.services.redis.ports['6379'] }}`{% endraw %} 上下文访问服务容器端口。
```yaml
services:
@@ -819,7 +819,7 @@ services:
### `jobs..services..image`
-The Docker image to use as the service container to run the action. The value can be the Docker Hub image name or a registry name.
+要用作运行操作的服务容器的 Docker 图像。 The value can be the Docker Hub image name or a registry name.
### `jobs..services..credentials`
@@ -845,15 +845,15 @@ services:
### `jobs..services..env`
-Sets a `map` of environment variables in the service container.
+在服务容器中设置环境变量的 `map`。
### `jobs..services..ports`
-Sets an `array` of ports to expose on the service container.
+设置要在服务容器上显示的端口 `array`。
### `jobs..services..volumes`
-Sets an `array` of volumes for the service container to use. 您可以使用卷分享作业中服务或其他步骤之间的数据。 可以指定命名的 Docker 卷、匿名的 Docker 卷或主机上的绑定挂载。
+设置要使用的服务容器卷的 `array`。 您可以使用卷分享作业中服务或其他步骤之间的数据。 可以指定命名的 Docker 卷、匿名的 Docker 卷或主机上的绑定挂载。
要指定卷，需指定来源和目标路径：
@@ -872,7 +872,7 @@ volumes:
### `jobs..services..options`
-Additional Docker container resource options. 有关选项列表，请参阅“[`docker create` options](https://docs.docker.com/engine/reference/commandline/create/#options)”。
+附加 Docker 容器资源选项。 有关选项列表，请参阅“[`docker create` options](https://docs.docker.com/engine/reference/commandline/create/#options)”。
{% warning %}
@@ -946,7 +946,7 @@ Allowed expression contexts: `github`, `needs`, and `secrets`.
## 过滤器模式备忘清单
-You can use special characters in path, branch, and tag filters.
+您可以在路径、分支和标记过滤器中使用特殊字符。
- `*`： 匹配零个或多个字符，但不匹配 `/` 字符。 例如，`Octo*` 匹配 `Octocat`。
- `**`： 匹配零个或多个任何字符。
@@ -955,7 +955,7 @@ You can use special characters in path, branch, and tag filters.
- `[]` 匹配列在括号中或包含在范围内的一个字符。 范围只能包含 `a-z`、`A-Z` 和 `0-9`。 例如，范围 `[0-9a-z]` 匹配任何数字或小写字母。 例如，`[CB]at` 匹配 `Cat` 或 `Bat`，`[1-2]00` 匹配 `100` 和 `200`。
- `!`：在模式开始时，它将否定以前的正模式。 如果不是第一个字符，它就没有特殊的意义。
-The characters `*`, `[`, and `!` are special characters in YAML. If you start a pattern with `*`, `[`, or `!`, you must enclose the pattern in quotes.
+字符 `*`、`[` 和 `!` 是 YAML 中的特殊字符。 如果模式以 `*`、`[` 或 `!` 开头，必须用引号括住模式。
```yaml
# Valid
@@ -983,7 +983,7 @@ For more information about branch, tag, and path filter syntax, see "[`on.
### 匹配文件路径的模式
-Path patterns must match the whole path, and start from the repository's root.
+路径模式必须匹配整个路径，并从仓库根开始。
| 模式 | 匹配描述 | 示例匹配 |
| ----------------------------------------------------------------------- | ---------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------ |
diff --git a/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md b/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md
index e92b04b449dd..dfa5276cbebf 100644
--- a/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md
+++ b/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md
@@ -114,7 +114,7 @@ Allows you to find the universally unique identifier (UUID) of your node in `clu
```
{% ifversion ghes %}
-Allows you to exempt a list of users from API rate limits. For more information, see "[Resources in the REST API](/rest/overview/resources-in-the-rest-api#rate-limiting)."
+Allows you to exempt a list of users from API rate limits. A hard limit of 120,000 requests will still apply to these users. For more information, see "[Resources in the REST API](/rest/overview/resources-in-the-rest-api#rate-limiting)."
``` shell
$ ghe-config app.github.rate-limiting-exempt-users "hubotgithub-actions"
diff --git a/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise.md b/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise.md
index 5d5911b6e72b..09da7fa90d5b 100644
--- a/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise.md
+++ b/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise.md
@@ -70,4 +70,4 @@ redirect_from:
## 对 {% data variables.product.prodname_actions %} 使用 IP 允许列表
-{% data reusables.github-actions.ip-allow-list-self-hosted-runners %}
+{% data reusables.actions.ip-allow-list-self-hosted-runners %}
diff --git a/translations/zh-CN/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises.md b/translations/zh-CN/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises.md
index 2845c1a1791d..58face01dba9 100644
--- a/translations/zh-CN/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises.md
+++ b/translations/zh-CN/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises.md
@@ -1,7 +1,7 @@
---
title: About GitHub Actions for enterprises
-shortTitle: 关于 GitHub Actions
-intro: '{% data variables.product.prodname_actions %} can improve developer productivity by automating your enterprise''s software development cycle.'
+shortTitle: About GitHub Actions
+intro: "{% data variables.product.prodname_actions %} can improve developer productivity by automating your enterprise's software development cycle."
versions:
ghec: '*'
ghes: '*'
@@ -12,31 +12,52 @@ topics:
- Enterprise
---
+{% ifversion ghes < 3.3 %}
+{% note %}
+
+**Note:** {% data reusables.enterprise.upgrade-ghes-for-actions %}
+
+{% endnote %}
+{% endif %}
+
+## About {% data variables.product.prodname_actions %} for enterprises
+
With {% data variables.product.prodname_actions %}, you can improve developer productivity by automating every phase of your enterprise's software development workflow.
-| 任务 | 更多信息 |
-| --------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Automatically test and build your application | "[关于持续集成](/actions/automating-builds-and-tests/about-continuous-integration)" |
-| Deploy your application | "[About continuous deployment](/actions/deployment/about-deployments/about-continuous-deployment)" |
-| Automatically and securely package code into artifacts and containers | "[About packaging with {% data variables.product.prodname_actions %}](/actions/publishing-packages/about-packaging-with-github-actions)" |
-| Automate your project management tasks | "[Using {% data variables.product.prodname_actions %} for project management](/actions/managing-issues-and-pull-requests/using-github-actions-for-project-management)" |
+| Task | More information |
+| ---- | ---------------- |
+| Automatically test and build your application | "[About continuous integration](/actions/automating-builds-and-tests/about-continuous-integration)" |
+| Deploy your application | "[About continuous deployment](/actions/deployment/about-deployments/about-continuous-deployment)" |
+| Automatically and securely package code into artifacts and containers | "[About packaging with {% data variables.product.prodname_actions %}](/actions/publishing-packages/about-packaging-with-github-actions)" |
+| Automate your project management tasks | "[Using {% data variables.product.prodname_actions %} for project management](/actions/managing-issues-and-pull-requests/using-github-actions-for-project-management)" |
{% data variables.product.prodname_actions %} helps your team work faster at scale. When large repositories start using {% data variables.product.prodname_actions %}, teams merge significantly more pull requests per day, and the pull requests are merged significantly faster. For more information, see "[Writing and shipping code faster](https://octoverse.github.com/writing-code-faster/#scale-through-automation)" in the State of the Octoverse.
-{% data variables.product.prodname_actions %} also provides greater control over deployments. For example, you can use environments to require approval for a job to proceed, restrict which branches can trigger a workflow, or limit access to secrets.{% ifversion ghec or ghae-issue-4856 %} If your workflows need to access resources from a cloud provider that supports OpenID Connect (OIDC), you can configure your workflows to authenticate directly to the cloud provider. This will allow you to stop storing credentials as long-lived secrets and provide other security benefits. For more information, see "[About security hardening with OpenID Connect](/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect)."{% endif %}
+You can create your own unique automations, or you can use and adapt workflows from our ecosystem of over 10,000 actions built by industry leaders and the open source community. For more information, see "[Finding and customizing actions](/actions/learn-github-actions/finding-and-customizing-actions)."
{% data variables.product.prodname_actions %} is developer friendly, because it's integrated directly into the familiar {% data variables.product.product_name %} experience.
-You can create your own unique automations, or you can use and adapt workflows from our ecosystem of over 10,000 actions built by industry leaders and the open source community. 更多信息请参阅“[查找和自定义操作](/actions/learn-github-actions/finding-and-customizing-actions)”。
-
{% ifversion ghec %}You can enjoy the convenience of {% data variables.product.company_short %}-hosted runners, which are maintained and upgraded by {% data variables.product.company_short %}, or you{% else %}You{% endif %} can control your own private CI/CD infrastructure by using self-hosted runners. Self-hosted runners allow you to determine the exact environment and resources that complete your builds, testing, and deployments, without exposing your software development cycle to the internet. For more information, see {% ifversion ghec %}"[About {% data variables.product.company_short %}-hosted runners](/actions/using-github-hosted-runners/about-github-hosted-runners)" and{% endif %} "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners)."
-{% data variables.product.prodname_actions %} also includes tools to govern your enterprise's software development cycle and meet compliance obligations. 更多信息请参阅“[在企业中执行 {% data variables.product.prodname_actions %} 的策略](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise)”。
+{% data variables.product.prodname_actions %} provides greater control over deployments. For example, you can use environments to require approval for a job to proceed, restrict which branches can trigger a workflow, or limit access to secrets.{% ifversion ghec or ghae-issue-4856 %} If your workflows need to access resources from a cloud provider that supports OpenID Connect (OIDC), you can configure your workflows to authenticate directly to the cloud provider. OIDC provides security benefits such as eliminating the need to store credentials as long-lived secrets. For more information, see "[About security hardening with OpenID Connect](/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect)."{% endif %}
+
+{% data variables.product.prodname_actions %} also includes tools to govern your enterprise's software development cycle and meet compliance obligations. For more information, see "[Enforcing policies for {% data variables.product.prodname_actions %} in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise)."
+
+## About getting started with {% data variables.product.prodname_actions %}
+
+{% data reusables.actions.introducing-enterprise %}
+
+{% data reusables.actions.migrating-enterprise %}
+
+{% ifversion ghes %}
+{% data reusables.actions.ghes-actions-not-enabled-by-default %} After you finish planning, you can follow the instructions for enabling {% data variables.product.prodname_actions %}. For example, you may need to upgrade the CPU and memory resources for {% data variables.product.product_location %}. For more information, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server)."
+{% else %}
+After you finish planning, you can follow the instructions for getting started with {% data variables.product.prodname_actions %}. For more information, see {% ifversion ghec %}"[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_cloud %}](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-cloud)."{% elsif ghae %}"[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_managed %}](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-ae)."{% endif %}
+{% endif %}
-To learn more about how you can successfully adopt {% data variables.product.prodname_actions %} for your enterprise, follow the "[Adopt {% data variables.product.prodname_actions %} for your enterprise](/admin/guides#adopt-github-actions-for-your-enterprise)" learning path.
-## 延伸阅读
+## Further reading
- "[Understanding {% data variables.product.prodname_actions %}](/actions/learn-github-actions/understanding-github-actions)"{% ifversion ghec %}
-- "[About billing for {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions/about-billing-for-github-actions)"{% endif %}
+- "[About billing for {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions/about-billing-for-github-actions)"{% endif %}
\ No newline at end of file
diff --git a/translations/zh-CN/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server.md b/translations/zh-CN/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server.md
index 8d5d97d5d6c2..e8eaeae8b1d1 100644
--- a/translations/zh-CN/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server.md
+++ b/translations/zh-CN/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server.md
@@ -25,7 +25,7 @@ This article explains how site administrators can configure {% data variables.pr
{% data reusables.enterprise.upgrade-ghes-for-actions %}
-{% data variables.product.prodname_actions %} is not enabled for {% data variables.product.prodname_ghe_server %} by default. You'll need to determine whether your instance has adequate CPU and memory resources to handle the load from {% data variables.product.prodname_actions %} without causing performance loss, and possibly increase those resources. You'll also need to decide which storage provider you'll use for the blob storage required to store artifacts generated by workflow runs. Then, you'll enable {% data variables.product.prodname_actions %} for your enterprise, manage access permissions, and add self-hosted runners to run workflows.
+{% data reusables.actions.ghes-actions-not-enabled-by-default %} You'll need to determine whether your instance has adequate CPU and memory resources to handle the load from {% data variables.product.prodname_actions %} without causing performance loss, and possibly increase those resources. You'll also need to decide which storage provider you'll use for the blob storage required to store artifacts generated by workflow runs. Then, you'll enable {% data variables.product.prodname_actions %} for your enterprise, manage access permissions, and add self-hosted runners to run workflows.
{% data reusables.actions.introducing-enterprise %}
diff --git a/translations/zh-CN/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md b/translations/zh-CN/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md
index 5ffc8bb19f95..9e11f3ddaf6a 100644
--- a/translations/zh-CN/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md
+++ b/translations/zh-CN/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md
@@ -85,6 +85,12 @@ Whenever your workflow developers want to use an action that's stored in a priva
You should plan for how you'll manage the resources required to use {% data variables.product.prodname_actions %}.
+{% ifversion ghes %}
+### Hardware requirements
+
+You may need to upgrade the CPU and memory resources for {% data variables.product.product_location %} to handle the load from {% data variables.product.prodname_actions %} without causing performance loss. For more information, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server#review-hardware-requirements)."
+{% endif %}
+
### 运行器
{% data variables.product.prodname_actions %} workflows require runners.{% ifversion ghec %} You can choose to use {% data variables.product.prodname_dotcom %}-hosted runners or self-hosted runners. {% data variables.product.prodname_dotcom %}-hosted runners are convenient because they are managed by {% data variables.product.company_short %}, who handles maintenance and upgrades for you. However, you may want to consider self-hosted runners if you need to run a workflow that will access resources behind your firewall or you want more control over the resources, configuration, or geographic location of your runner machines. For more information, see "[About {% data variables.product.prodname_dotcom %}-hosted runners](/actions/using-github-hosted-runners/about-github-hosted-runners)" and "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners)."{% else %} You will need to host your own runners by installing the {% data variables.product.prodname_actions %} self-hosted runner application on your own machines. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners)."{% endif %}
@@ -111,7 +117,7 @@ You must configure external blob storage for these artifacts. Decide which suppo
{% ifversion ghec or ghes %}
-{% data reusables.github-actions.artifact-log-retention-statement %}
+{% data reusables.actions.artifact-log-retention-statement %}
{% endif %}
diff --git a/translations/zh-CN/content/admin/guides.md b/translations/zh-CN/content/admin/guides.md
index 6192c8ef5033..923e43931b3e 100644
--- a/translations/zh-CN/content/admin/guides.md
+++ b/translations/zh-CN/content/admin/guides.md
@@ -136,5 +136,6 @@ includeGuides:
- /admin/user-management/requiring-two-factor-authentication-for-an-organization
- /admin/user-management/suspending-and-unsuspending-users
- /admin/overview/creating-an-enterprise-account
+ - /admin/user-management/managing-organizations-in-your-enterprise/restoring-a-deleted-organization
---
diff --git a/translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md b/translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md
index eab2fd84a1fa..36599a18be58 100644
--- a/translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md
+++ b/translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md
@@ -71,7 +71,7 @@ shortTitle: GitHub Actions policies
{% data reusables.enterprise-accounts.access-enterprise %}
{% data reusables.enterprise-accounts.policies-tab %}
{% data reusables.enterprise-accounts.actions-tab %}
-{% data reusables.github-actions.change-retention-period-for-artifacts-logs %}
+{% data reusables.actions.change-retention-period-for-artifacts-logs %}
{% endif %}
@@ -88,7 +88,7 @@ You can enforce policies to control how {% data variables.product.prodname_actio
{% data reusables.enterprise-accounts.access-enterprise %}
{% data reusables.enterprise-accounts.policies-tab %}
{% data reusables.enterprise-accounts.actions-tab %}
-{% data reusables.github-actions.workflows-from-public-fork-setting %}
+{% data reusables.actions.workflows-from-public-fork-setting %}
{% data reusables.actions.workflow-run-approve-link %}
@@ -98,16 +98,16 @@ You can enforce policies to control how {% data variables.product.prodname_actio
### Enforcing a policy for fork pull requests in private repositories
-{% data reusables.github-actions.private-repository-forks-overview %}
+{% data reusables.actions.private-repository-forks-overview %}
If a policy is enabled for an enterprise, the policy can be selectively disabled in individual organizations or repositories. If a policy is disabled for an enterprise, individual organizations or repositories cannot enable it.
-{% data reusables.github-actions.private-repository-forks-options %}
+{% data reusables.actions.private-repository-forks-options %}
{% data reusables.enterprise-accounts.access-enterprise %}
{% data reusables.enterprise-accounts.policies-tab %}
{% data reusables.enterprise-accounts.actions-tab %}
-{% data reusables.github-actions.private-repository-forks-configure %}
+{% data reusables.actions.private-repository-forks-configure %}
{% endif %}
@@ -115,11 +115,11 @@ If a policy is enabled for an enterprise, the policy can be selectively disabled
## Enforcing a policy for workflow permissions in your enterprise
-{% data reusables.github-actions.workflow-permissions-intro %}
+{% data reusables.actions.workflow-permissions-intro %}
您可以在企业、组织或仓库的设置中为 `GITHUB_TOKEN` 设置默认权限。 如果您在企业设置中选择受限制的选项为默认值，这将防止在组织或仓库设置中选择更多的允许设置。
-{% data reusables.github-actions.workflow-permissions-modifying %}
+{% data reusables.actions.workflow-permissions-modifying %}
{% data reusables.enterprise-accounts.access-enterprise %}
{% data reusables.enterprise-accounts.policies-tab %}
diff --git a/translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise.md b/translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise.md
index 7773d7867c00..5e19bc46d8cd 100644
--- a/translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise.md
+++ b/translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise.md
@@ -116,7 +116,7 @@ Enterprise owners can restrict access to assets owned by organizations in an ent
### 对 {% data variables.product.prodname_actions %} 使用 IP 允许列表
-{% data reusables.github-actions.ip-allow-list-self-hosted-runners %}
+{% data reusables.actions.ip-allow-list-self-hosted-runners %}
{% endif %}
@@ -126,9 +126,11 @@ Enterprise owners can restrict access to assets owned by organizations in an ent
You can use a SSH certificate authorities (CA) to allow members of any organization owned by your enterprise to access that organization's repositories using SSH certificates you provide. {% data reusables.organizations.can-require-ssh-cert %} 更多信息请参阅“[关于 SSH 认证中心](/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities)”。
+{% data reusables.organizations.add-extension-to-cert %}
+
### 添加 SSH 认证中心
-{% data reusables.organizations.add-extension-to-cert %}
+If you require SSH certificates for your enterprise, enterprise members should use a special URL for Git operations over SSH. 更多信息请参阅“[关于 SSH 认证中心](/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities#about-ssh-urls-with-ssh-certificates)”。
{% data reusables.enterprise-accounts.access-enterprise %}
{% data reusables.enterprise-accounts.settings-tab %}
diff --git a/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/index.md b/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/index.md
index 6ced953c8eb8..8ed3ae12ece7 100644
--- a/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/index.md
+++ b/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/index.md
@@ -27,6 +27,7 @@ children:
- /streaming-the-audit-logs-for-organizations-in-your-enterprise-account
- /removing-users-from-teams-and-organizations
- /removing-organizations-from-your-enterprise
+ - /restoring-a-deleted-organization
- /managing-projects-using-jira
- /continuous-integration-using-jenkins
shortTitle: 管理组织
diff --git a/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/restoring-a-deleted-organization.md b/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/restoring-a-deleted-organization.md
new file mode 100644
index 000000000000..eafc31b2b4d8
--- /dev/null
+++ b/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/restoring-a-deleted-organization.md
@@ -0,0 +1,53 @@
+---
+title: Restoring a deleted organization
+intro: 'You can partially restore an organization that was previously deleted on {% data variables.product.product_location %}.'
+versions:
+ ghes: '*'
+type: how_to
+topics:
+ - Administrator
+ - Enterprise
+ - Organizations
+shortTitle: Restore organization
+permissions: 'Site administers can restore an organization on {% data variables.product.product_name %}.'
+---
+
+## About organization restoration
+
+You can use the site admin dashboard to restore an organization that was previously deleted on {% data variables.product.product_location %}, as long as the audit log Elasticsearch indices contain the data for the `org.delete` event.
+
+Immediately after you restore an organization, the organization will not be exactly the same as it was prior to the deletion. You'll have to manually restore any repositories that were owned by the organization. 更多信息请参阅“[恢复删除的仓库](/admin/user-management/managing-repositories-in-your-enterprise/restoring-a-deleted-repository)”。
+
+You can also use the audit log to help you manually re-add teams and organization members. For more information, see "[Restoring members and teams](#restoring-members-and-teams)."
+
+## Restoring an organization
+
+{% data reusables.enterprise_site_admin_settings.access-settings %}
+1. Under "Search users, organizations, enterprises, teams, repositories, gists, and applications", search for the organization.
+
+ 
+
+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**.
+
+ 
+
+## Restoring members and teams
+
+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)."
+
+In all the search phrases below, replace ORGANIZATION with the name of the organization and TEAM with the name of the team.
+
+### Restoring organization members
+
+1. To find all users who were added to and removed from the organization, search the audit log for `action:org.add_member org:ORGANIZATION` and `action:org.remove_member org:ORGANIZATION`.
+1. Manually add to the organization each user that should still be a member. For more information, see "[Adding people to your organization](/organizations/managing-membership-in-your-organization/adding-people-to-your-organization)."
+
+### Restoring teams
+
+1. To find each team name, search the audit log for `action:team.create org:ORGANIZATION`.
+1. Manually recreate the team. For more information, see "[Creating a team](/organizations/organizing-members-into-teams/creating-a-team)."
+1. To find the members that have been added to each team, search for `action:team.add_member team:"ORGANIZATION/TEAM"`.
+1. Manually re-add the team members. For more information, see "[Adding organization members to a team](/organizations/organizing-members-into-teams/adding-organization-members-to-a-team)."
+1. To find the repositories that the team was granted access to, search for `action:team.add_repository team:"ORGANIZATION/TEAM"`.
+1. To find the access level that the team was granted for each repository, search for `action:team.update_repository_permission team:"ORGANIZATION/TEAM"`.
+1. Manually give the team access again. For more information, see "[Managing team access to an organization repository](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository)."
diff --git a/translations/zh-CN/content/authentication/managing-commit-signature-verification/checking-for-existing-gpg-keys.md b/translations/zh-CN/content/authentication/managing-commit-signature-verification/checking-for-existing-gpg-keys.md
index 7cd8bb07b506..310d430bf1f7 100644
--- a/translations/zh-CN/content/authentication/managing-commit-signature-verification/checking-for-existing-gpg-keys.md
+++ b/translations/zh-CN/content/authentication/managing-commit-signature-verification/checking-for-existing-gpg-keys.md
@@ -28,7 +28,12 @@ shortTitle: 现有 GPG 密钥
{% data reusables.gpg.list-keys-with-note %}
3. 检查命令输出以查看是否有 GPG 密钥对。
* 如果没有 GPG 密钥对，或者您不想使用任何可用于签名提交和标记的密钥对，则[生成新的 GPG 密钥](/articles/generating-a-new-gpg-key)。
- * 如果存在现有的 GPG 密钥对并且您要将其用于签名提交和标记，则[将 GPG 密钥添加到 GitHub 帐户](/articles/adding-a-new-gpg-key-to-your-github-account)。
+ * If there's an existing GPG key pair and you want to use it to sign commits and tags, you can display the public key using the following command, substituting in the GPG key ID you'd like to use. 在此例中，GPG 密钥 ID 是 `3AA5C34371567BD2`：
+ ```shell
+ $ gpg --armor --export 3AA5C34371567BD2
+ # Prints the GPG key ID, in ASCII armor format
+ ```
+ You can then [add your GPG key to your GitHub account](/articles/adding-a-new-gpg-key-to-your-github-account).
## 延伸阅读
diff --git a/translations/zh-CN/content/authentication/managing-commit-signature-verification/telling-git-about-your-signing-key.md b/translations/zh-CN/content/authentication/managing-commit-signature-verification/telling-git-about-your-signing-key.md
index b7cc743fbf06..a4d69a3dbefe 100644
--- a/translations/zh-CN/content/authentication/managing-commit-signature-verification/telling-git-about-your-signing-key.md
+++ b/translations/zh-CN/content/authentication/managing-commit-signature-verification/telling-git-about-your-signing-key.md
@@ -45,6 +45,12 @@ If you're using a GPG key that matches your committer identity and your verified
$ if [ -r ~/.bash_profile ]; then echo 'export GPG_TTY=$(tty)' >> ~/.bash_profile; \
else echo 'export GPG_TTY=$(tty)' >> ~/.profile; fi
```
+1. Optionally, to prompt you to enter a PIN or passphrase when required, install `pinentry-mac`. For example, using [Homebrew](https://brew.sh/):
+ ```shell
+ $ brew install pinentry-mac
+ $ echo "pinentry-program $(which pinentry-mac)" >> ~/.gnupg/gpg-agent.conf
+ $ killall gpg-agent
+ ```
{% data reusables.gpg.x-509-key %}
diff --git a/translations/zh-CN/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md b/translations/zh-CN/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md
index cc4f1864709b..fd21658b25a8 100644
--- a/translations/zh-CN/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md
+++ b/translations/zh-CN/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md
@@ -16,9 +16,9 @@ shortTitle: GitHub Actions 的计费
## 关于 {% data variables.product.prodname_actions %} 的计费
-{% data reusables.github-actions.actions-billing %}
+{% data reusables.actions.actions-billing %}
-{% data reusables.github-actions.actions-spending-limit-brief %} 更多信息请参阅“[关于支出限制](#about-spending-limits)”。
+{% data reusables.actions.actions-spending-limit-brief %} 更多信息请参阅“[关于支出限制](#about-spending-limits)”。
{% ifversion ghec %}
如果您通过 Microsoft 企业协议购买 {% data variables.product.prodname_enterprise %}，可以将 Azure 订阅 ID 连接到您的企业帐户，以便启用并支付超出您的帐户金额的 {% data variables.product.prodname_actions %} 使用费用。 更多信息请参阅“[将 Azure 订阅连接到您的企业](/billing/managing-billing-for-your-github-account/connecting-an-azure-subscription-to-your-enterprise)”。
@@ -99,7 +99,7 @@ shortTitle: GitHub Actions 的计费
## 关于支出限制
-{% data reusables.github-actions.actions-spending-limit-detailed %}
+{% data reusables.actions.actions-spending-limit-detailed %}
有关管理和更改帐户支出限制的信息，请参阅“[管理 {% data variables.product.prodname_actions %} 的支出限制](/billing/managing-billing-for-github-actions/managing-your-spending-limit-for-github-actions)”。
diff --git a/translations/zh-CN/content/billing/managing-billing-for-github-actions/managing-your-spending-limit-for-github-actions.md b/translations/zh-CN/content/billing/managing-billing-for-github-actions/managing-your-spending-limit-for-github-actions.md
index a367668018e0..53076c19ff69 100644
--- a/translations/zh-CN/content/billing/managing-billing-for-github-actions/managing-your-spending-limit-for-github-actions.md
+++ b/translations/zh-CN/content/billing/managing-billing-for-github-actions/managing-your-spending-limit-for-github-actions.md
@@ -19,9 +19,9 @@ shortTitle: Actions 支出限制
## 关于 {% data variables.product.prodname_actions %} 的支出限额
-{% data reusables.github-actions.actions-billing %}
+{% data reusables.actions.actions-billing %}
-{% data reusables.github-actions.actions-spending-limit-brief %}
+{% data reusables.actions.actions-spending-limit-brief %}
{% data reusables.actions.actions-packages-set-spending-limit %} 有关 {% data variables.product.prodname_actions %} 使用价格的更多信息，请参阅“[关于 {% data variables.product.prodname_actions %} 的计费](/billing/managing-billing-for-github-actions/about-billing-for-github-actions)”。
diff --git a/translations/zh-CN/content/billing/managing-billing-for-github-actions/viewing-your-github-actions-usage.md b/translations/zh-CN/content/billing/managing-billing-for-github-actions/viewing-your-github-actions-usage.md
index e6a272d49371..7d0578e2080b 100644
--- a/translations/zh-CN/content/billing/managing-billing-for-github-actions/viewing-your-github-actions-usage.md
+++ b/translations/zh-CN/content/billing/managing-billing-for-github-actions/viewing-your-github-actions-usage.md
@@ -43,7 +43,7 @@ shortTitle: 查看 Actions 使用情况
{% note %}
-**注：**企业帐户的计费详细信息不会汇总每个操作系统的使用分钟数。 {% data reusables.github-actions.enterprise-billing-details %}
+**注：**企业帐户的计费详细信息不会汇总每个操作系统的使用分钟数。 {% data reusables.actions.enterprise-billing-details %}
{% endnote %}
diff --git a/translations/zh-CN/content/billing/managing-billing-for-github-packages/viewing-your-github-packages-usage.md b/translations/zh-CN/content/billing/managing-billing-for-github-packages/viewing-your-github-packages-usage.md
index 8acd686c4fd6..76d2d0edc3db 100644
--- a/translations/zh-CN/content/billing/managing-billing-for-github-packages/viewing-your-github-packages-usage.md
+++ b/translations/zh-CN/content/billing/managing-billing-for-github-packages/viewing-your-github-packages-usage.md
@@ -42,7 +42,7 @@ shortTitle: 查看使用情况
{% note %}
-**注：**企业帐户的计费详细信息仅汇总每个组织的存储数据使用情况。 {% data reusables.github-actions.enterprise-billing-details %}
+**注：**企业帐户的计费详细信息仅汇总每个组织的存储数据使用情况。 {% data reusables.actions.enterprise-billing-details %}
{% endnote %}
diff --git a/translations/zh-CN/content/billing/managing-your-github-billing-settings/setting-your-billing-email.md b/translations/zh-CN/content/billing/managing-your-github-billing-settings/setting-your-billing-email.md
index aac126557c97..2f64dee4031d 100644
--- a/translations/zh-CN/content/billing/managing-your-github-billing-settings/setting-your-billing-email.md
+++ b/translations/zh-CN/content/billing/managing-your-github-billing-settings/setting-your-billing-email.md
@@ -64,3 +64,44 @@ shortTitle: 帐单邮箱
1. 针对列表中的用户条目，单击 **Edit（编辑）**。 
1. 在电子邮件地址的右侧，使用“Edit（编辑）”下拉菜单，然后单击 **Remove（删除）**。 
1. 查看确认提示，然后单击 **Remove（删除）**。
+
+{% ifversion ghec %}
+## Setting your enterprise's billing email
+
+Your enterprise's billing email is where {% data variables.product.product_name %} sends receipts and other billing-related communication. The email address does not need to be unique to the enterprise account.
+
+Only enterprise members with the owner or billing manager role can access or change billing settings for your enterprise. For more information, see "[Managing users in your enterprise](/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise)."
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.settings-tab %}
+{% data reusables.enterprise-accounts.billing-tab %}
+1. Click **Billing emails**.
+2. Under "Email recipients", to the right of the billing email address, click **Edit**. 
+2. 输入一个有效的电子邮件地址，然后点击 **Update（更新）**。 
+
+## Managing additional recipients for your enterprise's billing email
+
+如果您有用户希望接收帐单报告，您可以将他们的电子邮件地址添加为帐单邮箱收件人。
+
+Only enterprise members with the owner or billing manager role can access or change billing settings for your enterprise. For more information, see "[Managing users in your enterprise](/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise)."
+
+### 添加帐单通知的收件人
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.settings-tab %}
+{% data reusables.enterprise-accounts.billing-tab %}
+1. Click **Billing emails**.
+2. Under "Email recipients", to the right of the billing email address, click **Add**. 
+3. 输入收件人的电子邮件地址，然后单击 **Add（添加）**。 
+
+### 从帐单通知中删除收件人
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.settings-tab %}
+{% data reusables.enterprise-accounts.billing-tab %}
+1. Click **Billing emails**.
+2. 在“Email recipients（电子邮件收件人）”下，找到要删除的电子邮件地址。
+3. 针对列表中的用户条目，单击 **Edit（编辑）**。 
+4. 在电子邮件地址的右侧，使用“Edit（编辑）”下拉菜单，然后单击 **Remove（删除）**。 
+5. 查看确认提示，然后单击 **Remove（删除）**。
+{% endif %}
diff --git a/translations/zh-CN/content/code-security/code-scanning/integrating-with-code-scanning/uploading-a-sarif-file-to-github.md b/translations/zh-CN/content/code-security/code-scanning/integrating-with-code-scanning/uploading-a-sarif-file-to-github.md
index 8f21ec78dff1..0e33d7b940fb 100644
--- a/translations/zh-CN/content/code-security/code-scanning/integrating-with-code-scanning/uploading-a-sarif-file-to-github.md
+++ b/translations/zh-CN/content/code-security/code-scanning/integrating-with-code-scanning/uploading-a-sarif-file-to-github.md
@@ -86,7 +86,11 @@ jobs:
build:
runs-on: ubuntu-latest{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
permissions:
- security-events: write{% endif %}
+ # required for all workflows
+ security-events: write
+ # only required for workflows in private repositories
+ actions: read
+ contents: read{% endif %}
steps:
# This step checks out a copy of your repository.
- name: Checkout repository
@@ -123,7 +127,11 @@ jobs:
build:
runs-on: ubuntu-latest{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
permissions:
- security-events: write{% endif %}
+ # required for all workflows
+ security-events: write
+ # only required for workflows in private repositories
+ actions: read
+ contents: read{% endif %}
steps:
- uses: actions/checkout@v2
- name: Run npm install
diff --git a/translations/zh-CN/content/code-security/secret-scanning/secret-scanning-partners.md b/translations/zh-CN/content/code-security/secret-scanning/secret-scanning-partners.md
index 865808e0cb02..0b219bc8e39e 100644
--- a/translations/zh-CN/content/code-security/secret-scanning/secret-scanning-partners.md
+++ b/translations/zh-CN/content/code-security/secret-scanning/secret-scanning-partners.md
@@ -34,7 +34,7 @@ Organizations using {% data variables.product.prodname_ghe_cloud %} with {% data
{% ifversion ghes > 3.1 or ghae or ghec %}
{% note %}
-**Note:** You can also define custom {% data variables.product.prodname_secret_scanning %} patterns that only apply to your repository or organization. For more information, see "[Defining custom patterns for {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/defining-custom-patterns-for-secret-scanning)."
+**Note:** You can also define custom {% data variables.product.prodname_secret_scanning %} patterns that only apply to your repository or organization. 更多信息请参阅“[定义 {% data variables.product.prodname_secret_scanning %} 的自定义模式](/code-security/secret-security/defining-custom-patterns-for-secret-scanning)”。
{% endnote %}
{% endif %}
diff --git a/translations/zh-CN/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-encrypted-secrets-for-dependabot.md b/translations/zh-CN/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-encrypted-secrets-for-dependabot.md
index 133250543410..93db3c20f5ea 100644
--- a/translations/zh-CN/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-encrypted-secrets-for-dependabot.md
+++ b/translations/zh-CN/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-encrypted-secrets-for-dependabot.md
@@ -44,11 +44,11 @@ password: ${{secrets.MY_ARTIFACTORY_PASSWORD}}
## 为 {% data variables.product.prodname_dependabot %} 添加仓库密码
-{% data reusables.github-actions.permissions-statement-secrets-repository %}
+{% data reusables.actions.permissions-statement-secrets-repository %}
{% data reusables.repositories.navigate-to-repo %}
{% data reusables.repositories.sidebar-settings %}
-{% data reusables.github-actions.sidebar-secret %}
+{% data reusables.actions.sidebar-secret %}
{% data reusables.dependabot.dependabot-secrets-button %}
1. 单击 **New repository secret（新仓库机密）**。
1. 在 **Name（名称）**输入框中键入密码的名称。
@@ -63,11 +63,11 @@ password: ${{secrets.MY_ARTIFACTORY_PASSWORD}}
在组织中创建密码时，可以使用策略来限制可以访问该密码的仓库。 例如，您可以将访问权限授予所有仓库，也可以限制仅私有仓库或指定的仓库列表拥有访问权限。
-{% data reusables.github-actions.permissions-statement-secrets-organization %}
+{% data reusables.actions.permissions-statement-secrets-organization %}
{% data reusables.organizations.navigate-to-org %}
{% data reusables.organizations.org_settings %}
-{% data reusables.github-actions.sidebar-secret %}
+{% data reusables.actions.sidebar-secret %}
{% data reusables.dependabot.dependabot-secrets-button %}
1. 单击 **New organization secret（新组织机密）**。
1. 在 **Name（名称）**输入框中键入密码的名称。
diff --git a/translations/zh-CN/content/codespaces/customizing-your-codespace/index.md b/translations/zh-CN/content/codespaces/customizing-your-codespace/index.md
index ad7169107395..ca7d55dab304 100644
--- a/translations/zh-CN/content/codespaces/customizing-your-codespace/index.md
+++ b/translations/zh-CN/content/codespaces/customizing-your-codespace/index.md
@@ -1,6 +1,6 @@
---
-title: Customizing your codespace
-intro: '{% data variables.product.prodname_codespaces %} 是您专用的环境。 You can configure your repositories with a dev container to define their default Codespaces environment, and personalize your development experience across all of your codespaces with dotfiles and Settings Sync.'
+title: 自定义代码空间
+intro: '{% data variables.product.prodname_codespaces %} 是您专用的环境。 可以使用开发容器配置存储库以定义其默认 Codespaces 环境，并使用 dotfile 和“设置同步”在所有代码空间中个性化开发体验。'
product: '{% data reusables.gated-features.codespaces %}'
versions:
fpt: '*'
diff --git a/translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces.md b/translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces.md
index 7f55482cac10..265ca68f6b2d 100644
--- a/translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces.md
+++ b/translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces.md
@@ -51,7 +51,7 @@ topics:
在组织中创建密码时，可以使用策略来限制可以访问该密码的仓库。 例如，您可以将访问权限授予所有仓库，也可以限制仅私有仓库或指定的仓库列表拥有访问权限。
-{% data reusables.github-actions.permissions-statement-secrets-organization %}
+{% data reusables.actions.permissions-statement-secrets-organization %}
{% data reusables.organizations.navigate-to-org %}
{% data reusables.organizations.org_settings %}
@@ -68,7 +68,7 @@ topics:
{% data reusables.organizations.navigate-to-org %}
{% data reusables.organizations.org_settings %}
-{% data reusables.github-actions.sidebar-secret %}
+{% data reusables.actions.sidebar-secret %}
1. 密码列表包括任何已配置的权限和策略。 例如： 
1. 有关已为每个密码配置的权限的更多信息，请单击 **Update（更新）**。
diff --git a/translations/zh-CN/content/get-started/learning-about-github/githubs-products.md b/translations/zh-CN/content/get-started/learning-about-github/githubs-products.md
index 4961400aa7c5..9f24411b45ae 100644
--- a/translations/zh-CN/content/get-started/learning-about-github/githubs-products.md
+++ b/translations/zh-CN/content/get-started/learning-about-github/githubs-products.md
@@ -88,7 +88,7 @@ In addition to the features available with {% data variables.product.prodname_fr
{% data variables.product.company_short %} bills for {% data variables.product.prodname_team %} on a per-user basis. For more information, see "[About per-user pricing]({% ifversion not fpt %}/free-pro-team@latest{% endif %}/billing/managing-billing-for-your-github-account/about-per-user-pricing){% ifversion fpt %}."{% else %}" in the Free, Pro, & Team documentation.{% endif %}
-{% data reusables.github-actions.actions-billing %}
+{% data reusables.actions.actions-billing %}
## {% data variables.product.prodname_enterprise %}
diff --git a/translations/zh-CN/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md b/translations/zh-CN/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md
index ecf0b5d63e54..911ac9c6cd70 100644
--- a/translations/zh-CN/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md
+++ b/translations/zh-CN/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md
@@ -203,11 +203,11 @@ Members of your organization or enterprise can use GitHub's learning and support
### 1. Reading about {% data variables.product.prodname_ghe_cloud %} on {% data variables.product.prodname_docs %}
You can read documentation that reflects the features available with {% data variables.product.prodname_ghe_cloud %}. For more information, see "[About versions of {% data variables.product.prodname_docs %}](/get-started/learning-about-github/about-versions-of-github-docs)."
-### 2. Learning with {% data variables.product.prodname_learning %}
+### 2. 通过 {% data variables.product.prodname_learning %} 学习
Members of your organization or enterprise can learn new skills by completing fun, realistic projects in your very own GitHub repository with [{% data variables.product.prodname_learning %}](https://lab.github.com/). Each course is a hands-on lesson created by the GitHub community and taught by the friendly Learning Lab bot.
For more information, see "[Git and {% data variables.product.prodname_dotcom %} learning resources](/github/getting-started-with-github/quickstart/git-and-github-learning-resources)."
-### 3. Supporting the open source community
+### 3. 支持开源社区
{% data reusables.getting-started.sponsors %}
### 4. 联系 {% data variables.contact.github_support %}
diff --git a/translations/zh-CN/content/get-started/onboarding/getting-started-with-your-github-account.md b/translations/zh-CN/content/get-started/onboarding/getting-started-with-your-github-account.md
index 71e5b3d00831..245a75c61f6c 100644
--- a/translations/zh-CN/content/get-started/onboarding/getting-started-with-your-github-account.md
+++ b/translations/zh-CN/content/get-started/onboarding/getting-started-with-your-github-account.md
@@ -1,6 +1,6 @@
---
-title: 开始使用 GitHub 帐户
-intro: '使用 {% data variables.product.prodname_dotcom %} 上的用户帐户，您可以导入或创建存储库、与他人协作以及与 {% data variables.product.prodname_dotcom %} 社区联系。'
+title: Getting started with your GitHub account
+intro: 'With a user account on {% data variables.product.prodname_dotcom %}, you can import or create repositories, collaborate with others, and connect with the {% data variables.product.prodname_dotcom %} community.'
versions:
fpt: '*'
ghes: '*'
@@ -8,12 +8,12 @@ versions:
ghec: '*'
---
-本指南将引导您完成 {% data variables.product.company_short %} 帐户的设置，并开始使用 {% data variables.product.product_name %} 协作和社区功能。
+This guide will walk you through setting up your {% data variables.product.company_short %} account and getting started with {% data variables.product.product_name %}'s features for collaboration and community.
-## 第 1 部分：配置 {% data variables.product.prodname_dotcom %} 帐户
+## Part 1: Configuring your {% data variables.product.prodname_dotcom %} account
{% ifversion fpt or ghec %}
-开始使用 {% data variables.product.product_name %} 的第一步是创建一个帐户，选择最适合您需求的产品，验证您的电子邮件，设置双重身份验证以及查看您的个人资料。
+The first steps in starting with {% data variables.product.product_name %} are to create an account, choose a product that fits your needs best, verify your email, set up two-factor authentication, and view your profile.
{% elsif ghes %}
The first steps in starting with {% data variables.product.product_name %} are to access your account, set up two-factor authentication, and view your profile.
{% elsif ghae %}
@@ -23,18 +23,18 @@ The first steps in starting with {% data variables.product.product_name %} are t
{% ifversion fpt or ghec %}There are several types of accounts on {% data variables.product.prodname_dotcom %}. {% endif %} Every person who uses {% data variables.product.product_name %} has their own user account, which can be part of multiple organizations and teams. Your user account is your identity on {% data variables.product.product_location %} and represents you as an individual.
{% ifversion fpt or ghec %}
-### 1. 创建帐户
+### 1. Creating an account
To sign up for an account on {% data variables.product.product_location %}, navigate to https://github.com/ and follow the prompts.
-To keep your {% data variables.product.prodname_dotcom %} account secure you should use a strong and unique password. 更多信息请参阅“[创建强式密码](/github/authenticating-to-github/keeping-your-account-and-data-secure/creating-a-strong-password)”。
+To keep your {% data variables.product.prodname_dotcom %} account secure you should use a strong and unique password. For more information, see "[Creating a strong password](/github/authenticating-to-github/keeping-your-account-and-data-secure/creating-a-strong-password)."
### 2. Choosing your {% data variables.product.prodname_dotcom %} product
You can choose {% data variables.product.prodname_free_user %} or {% data variables.product.prodname_pro %} to get access to different features for your personal account. You can upgrade at any time if you are unsure at first which product you want.
For more information on all of {% data variables.product.prodname_dotcom %}'s plans, see "[{% data variables.product.prodname_dotcom %}'s products](/get-started/learning-about-github/githubs-products)."
-### 3. 验证电子邮件地址
-To ensure you can use all the features in your {% data variables.product.product_name %} plan, verify your email address after signing up for a new account. 更多信息请参阅“[验证电子邮件地址](/github/getting-started-with-github/signing-up-for-github/verifying-your-email-address)”。
+### 3. Verifying your email address
+To ensure you can use all the features in your {% data variables.product.product_name %} plan, verify your email address after signing up for a new account. For more information, see "[Verifying your email address](/github/getting-started-with-github/signing-up-for-github/verifying-your-email-address)."
{% endif %}
{% ifversion ghes %}
@@ -49,37 +49,37 @@ You will receive an email notification once your enterprise owner for {% data va
{% ifversion fpt or ghes or ghec %}
### {% ifversion fpt or ghec %}4.{% else %}2.{% endif %} Configuring two-factor authentication
-双重身份验证（或 2FA）是登录网站或应用时使用的额外保护层。 We strongly urge you to configure 2FA for the safety of your account. 更多信息请参阅“[关于双重身份验证](/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa/about-two-factor-authentication)”。
+Two-factor authentication, or 2FA, is an extra layer of security used when logging into websites or apps. We strongly urge you to configure 2FA for the safety of your account. For more information, see "[About two-factor authentication](/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa/about-two-factor-authentication)."
{% endif %}
### {% ifversion fpt or ghec %}5.{% elsif ghes %}3.{% else %}2.{% endif %} Viewing your {% data variables.product.prodname_dotcom %} profile and contribution graph
Your {% data variables.product.prodname_dotcom %} profile tells people the story of your work through the repositories and gists you've pinned, the organization memberships you've chosen to publicize, the contributions you've made, and the projects you've created. For more information, see "[About your profile](/github/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-profile)" and "[Viewing contributions on your profile](/github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/viewing-contributions-on-your-profile)."
## Part 2: Using {% data variables.product.product_name %}'s tools and processes
-To best use {% data variables.product.product_name %}, you'll need to set up Git. Git 负责在您计算机上本地发生的、与 {% data variables.product.prodname_dotcom %} 有关的所有内容。 To effectively collaborate on {% data variables.product.product_name %}, you'll write in issues and pull requests using {% data variables.product.prodname_dotcom %} Flavored Markdown.
+To best use {% data variables.product.product_name %}, you'll need to set up Git. Git is responsible for everything {% data variables.product.prodname_dotcom %}-related that happens locally on your computer. To effectively collaborate on {% data variables.product.product_name %}, you'll write in issues and pull requests using {% data variables.product.prodname_dotcom %} Flavored Markdown.
### 1. Learning Git
{% data variables.product.prodname_dotcom %}'s collaborative approach to development depends on publishing commits from your local repository to {% data variables.product.product_name %} for other people to view, fetch, and update using Git. For more information about Git, see the "[Git Handbook](https://guides.github.com/introduction/git-handbook/)" guide. For more information about how Git is used on {% data variables.product.product_name %}, see "[{% data variables.product.prodname_dotcom %} flow](/get-started/quickstart/github-flow)."
-### 2. 设置 Git
-If you plan to use Git locally on your computer, whether through the command line, an IDE or text editor, you will need to install and set up Git. 更多信息请参阅“[设置 Git](/get-started/quickstart/set-up-git)”。
+### 2. Setting up Git
+If you plan to use Git locally on your computer, whether through the command line, an IDE or text editor, you will need to install and set up Git. For more information, see "[Set up Git](/get-started/quickstart/set-up-git)."
-If you prefer to use a visual interface, you can download and use {% data variables.product.prodname_desktop %}. {% data variables.product.prodname_desktop %} comes packaged with Git, so there is no need to install Git separately. 更多信息请参阅“[开始使用 {% data variables.product.prodname_desktop %}](/desktop/installing-and-configuring-github-desktop/overview/getting-started-with-github-desktop)”。
+If you prefer to use a visual interface, you can download and use {% data variables.product.prodname_desktop %}. {% data variables.product.prodname_desktop %} comes packaged with Git, so there is no need to install Git separately. For more information, see "[Getting started with {% data variables.product.prodname_desktop %}](/desktop/installing-and-configuring-github-desktop/overview/getting-started-with-github-desktop)."
-Once you install Git, you can connect to {% data variables.product.product_name %} repositories from your local computer, whether your own repository or another user's fork. When you connect to a repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} from Git, you'll need to authenticate with {% data variables.product.product_name %} using either HTTPS or SSH. 更多信息请参阅“[关于远程仓库](/get-started/getting-started-with-git/about-remote-repositories)”。
+Once you install Git, you can connect to {% data variables.product.product_name %} repositories from your local computer, whether your own repository or another user's fork. When you connect to a repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} from Git, you'll need to authenticate with {% data variables.product.product_name %} using either HTTPS or SSH. For more information, see "[About remote repositories](/get-started/getting-started-with-git/about-remote-repositories)."
### 3. Choosing how to interact with {% data variables.product.product_name %}
Everyone has their own unique workflow for interacting with {% data variables.product.prodname_dotcom %}; the interfaces and methods you use depend on your preference and what works best for your needs.
For more information about how to authenticate to {% data variables.product.product_name %} with each of these methods, see "[About authentication to {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/keeping-your-account-and-data-secure/about-authentication-to-github)."
-| **方法** | **描述** | **Use cases** |
-| ------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Browse to {% data variables.product.prodname_dotcom_the_website %} | If you don't need to work with files locally, {% data variables.product.product_name %} lets you complete most Git-related actions directly in the browser, from creating and forking repositories to editing files and opening pull requests. | This method is useful if you want a visual interface and need to do quick, simple changes that don't require working locally. |
-| {% data variables.product.prodname_desktop %} | {% data variables.product.prodname_desktop %} 可扩展并简化您的 {% data variables.product.prodname_dotcom_the_website %} 工作流程，它使用可视界面，而不是在命令行上使用命令文本。 For more information on getting started with {% data variables.product.prodname_desktop %}, see "[Getting started with {% data variables.product.prodname_desktop %}](/desktop/installing-and-configuring-github-desktop/overview/getting-started-with-github-desktop)." | This method is best if you need or want to work with files locally, but prefer using a visual interface to use Git and interact with {% data variables.product.product_name %}. |
-| IDE or text editor | You can set a default text editor, like [Atom](https://atom.io/) or [Visual Studio Code](https://code.visualstudio.com/) to open and edit your files with Git, use extensions, and view the project structure. For more information, see "[Associating text editors with Git](/github/using-git/associating-text-editors-with-git)." | This is convenient if you are working with more complex files and projects and want everything in one place, since text editors or IDEs often allow you to directly access the command line in the editor. |
-| Command line, with or without {% data variables.product.prodname_cli %} | For the most granular control and customization of how you use Git and interact with {% data variables.product.product_name %}, you can use the command line. For more information on using Git commands, see "[Git cheatsheet](/github/getting-started-with-github/quickstart/git-cheatsheet)."
{% data variables.product.prodname_cli %} is a separate command-line tool you can install that brings pull requests, issues, {% data variables.product.prodname_actions %}, and other {% data variables.product.prodname_dotcom %} features to your terminal, so you can do all your work in one place. For more information, see "[{% data variables.product.prodname_cli %}](/github/getting-started-with-github/using-github/github-cli)." | This is most convenient if you are already working from the command line, allowing you to avoid switching context, or if you are more comfortable using the command line. |
-| {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API | {% data variables.product.prodname_dotcom %} has a REST API and GraphQL API that you can use to interact with {% data variables.product.product_name %}. For more information, see "[Getting started with the API](/github/extending-github/getting-started-with-the-api)." | The {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API would be most helpful if you wanted to automate common tasks, back up your data, or create integrations that extend {% data variables.product.prodname_dotcom %}. |
+| **Method** | **Description** | **Use cases** |
+| ------------- | ------------- | ------------- |
+| Browse to {% data variables.product.prodname_dotcom_the_website %} | If you don't need to work with files locally, {% data variables.product.product_name %} lets you complete most Git-related actions directly in the browser, from creating and forking repositories to editing files and opening pull requests.| This method is useful if you want a visual interface and need to do quick, simple changes that don't require working locally. |
+| {% data variables.product.prodname_desktop %} | {% data variables.product.prodname_desktop %} extends and simplifies your {% data variables.product.prodname_dotcom_the_website %} workflow, using a visual interface instead of text commands on the command line. For more information on getting started with {% data variables.product.prodname_desktop %}, see "[Getting started with {% data variables.product.prodname_desktop %}](/desktop/installing-and-configuring-github-desktop/overview/getting-started-with-github-desktop)." | This method is best if you need or want to work with files locally, but prefer using a visual interface to use Git and interact with {% data variables.product.product_name %}. |
+| IDE or text editor | You can set a default text editor, like [Atom](https://atom.io/) or [Visual Studio Code](https://code.visualstudio.com/) to open and edit your files with Git, use extensions, and view the project structure. For more information, see "[Associating text editors with Git](/github/using-git/associating-text-editors-with-git)." | This is convenient if you are working with more complex files and projects and want everything in one place, since text editors or IDEs often allow you to directly access the command line in the editor. |
+| Command line, with or without {% data variables.product.prodname_cli %} | For the most granular control and customization of how you use Git and interact with {% data variables.product.product_name %}, you can use the command line. For more information on using Git commands, see "[Git cheatsheet](/github/getting-started-with-github/quickstart/git-cheatsheet)."
{% data variables.product.prodname_cli %} is a separate command-line tool you can install that brings pull requests, issues, {% data variables.product.prodname_actions %}, and other {% data variables.product.prodname_dotcom %} features to your terminal, so you can do all your work in one place. For more information, see "[{% data variables.product.prodname_cli %}](/github/getting-started-with-github/using-github/github-cli)." | This is most convenient if you are already working from the command line, allowing you to avoid switching context, or if you are more comfortable using the command line. |
+| {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API | {% data variables.product.prodname_dotcom %} has a REST API and GraphQL API that you can use to interact with {% data variables.product.product_name %}. For more information, see "[Getting started with the API](/github/extending-github/getting-started-with-the-api)." | The {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API would be most helpful if you wanted to automate common tasks, back up your data, or create integrations that extend {% data variables.product.prodname_dotcom %}. |
### 4. Writing on {% data variables.product.product_name %}
-To make your communication clear and organized in issues and pull requests, you can use {% data variables.product.prodname_dotcom %} Flavored Markdown for formatting, which combines an easy-to-read, easy-to-write syntax with some custom functionality. 更多信息请参阅“[关于 {% data variables.product.prodname_dotcom %} 上的书写和格式化](/github/writing-on-github/about-writing-and-formatting-on-github)”。
+To make your communication clear and organized in issues and pull requests, you can use {% data variables.product.prodname_dotcom %} Flavored Markdown for formatting, which combines an easy-to-read, easy-to-write syntax with some custom functionality. For more information, see "[About writing and formatting on {% 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 "[Communicating using Markdown](https://lab.github.com/githubtraining/communicating-using-markdown)" course on {% data variables.product.prodname_learning %}.
@@ -96,56 +96,56 @@ Any number of people can work together in repositories across {% data variables.
### 1. Working with repositories
-#### 创建仓库
-仓库就像项目的文件夹。 You can have any number of public and private repositories in your user account. Repositories can contain folders and files, images, videos, spreadsheets, and data sets, as well as the revision history for all files in the repository. 更多信息请参阅“[关于仓库](/github/creating-cloning-and-archiving-repositories/about-repositories)”。
+#### Creating a repository
+A repository is like a folder for your project. You can have any number of public and private repositories in your user account. Repositories can contain folders and files, images, videos, spreadsheets, and data sets, as well as the revision history for all files in the repository. For more information, see "[About repositories](/github/creating-cloning-and-archiving-repositories/about-repositories)."
-When you create a new repository, you should initialize the repository with a README file to let people know about your project. 更多信息请参阅“[创建新仓库](/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/creating-a-new-repository)”。
+When you create a new repository, you should initialize the repository with a README file to let people know about your project. For more information, see "[Creating a new repository](/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/creating-a-new-repository)."
-#### 克隆仓库
-You can clone an existing repository from {% data variables.product.product_name %} to your local computer, making it easier to add or remove files, fix merge conflicts, or make complex commits. 克隆仓库将提取 {% data variables.product.prodname_dotcom %} 在当时拥有的所有仓库数据的完整副本，包括项目每个文件和文件夹的所有版本。 更多信息请参阅“[克隆仓库](/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github/cloning-a-repository)”。
+#### Cloning a repository
+You can clone an existing repository from {% data variables.product.product_name %} to your local computer, making it easier to add or remove files, fix merge conflicts, or make complex commits. Cloning a repository pulls down a full copy of all the repository data that {% data variables.product.prodname_dotcom %} has at that point in time, including all versions of every file and folder for the project. For more information, see "[Cloning a repository](/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github/cloning-a-repository)."
-#### 复刻仓库
-A fork is a copy of a repository that you manage, where any changes you make will not affect the original repository unless you submit a pull request to the project owner. 复刻最常见的用法是对其他人的项目提出更改或将其他人的项目用作自己创意的起点。 更多信息请参阅“[使用复刻](/github/collaborating-with-pull-requests/working-with-forks)”。
-### 2. 导入项目
+#### Forking a repository
+A fork is a copy of a repository that you manage, where any changes you make will not affect the original repository unless you submit a pull request to the project owner. Most commonly, forks are used to either propose changes to someone else's project or to use someone else's project as a starting point for your own idea. For more information, see "[Working with forks](/github/collaborating-with-pull-requests/working-with-forks)."
+### 2. Importing your projects
If you have existing projects you'd like to move over to {% data variables.product.product_name %} you can import projects using the {% data variables.product.prodname_dotcom %} Importer, the command line, or external migration tools. For more information, see "[Importing source code to {% data variables.product.prodname_dotcom %}](/github/importing-your-projects-to-github/importing-source-code-to-github)."
### 3. Managing collaborators and permissions
-您可以使用仓库议题、拉取请求及项目板与其他人协作处理您的项目。 You can invite other people to your repository as collaborators from the **Collaborators** tab in the repository settings. 更多信息请参阅“[邀请协作者参加个人仓库](/github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository)”。
+You can collaborate on your project with others using your repository's issues, pull requests, and project boards. You can invite other people to your repository as collaborators from the **Collaborators** tab in the repository settings. For more information, see "[Inviting collaborators to a personal repository](/github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository)."
-You are the owner of any repository you create in your user account and have full control of the repository. Collaborators have write access to your repository, limiting what they have permission to do. 更多信息请参阅“[用户帐户仓库的权限级别](/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-a-user-account-repository)”。
+You are the owner of any repository you create in your user account and have full control of the repository. Collaborators have write access to your repository, limiting what they have permission to do. For more information, see "[Permission levels for a user account repository](/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-a-user-account-repository)."
-### 4. 管理仓库设置
-As the owner of a repository you can configure several settings, including the repository's visibility, topics, and social media preview. 更多信息请参阅“[管理仓库设置](/github/administering-a-repository/managing-repository-settings)”。
+### 4. Managing repository settings
+As the owner of a repository you can configure several settings, including the repository's visibility, topics, and social media preview. For more information, see "[Managing repository settings](/github/administering-a-repository/managing-repository-settings)."
-### 5. 设置项目的健康贡献
+### 5. Setting up your project for healthy contributions
{% ifversion fpt or ghec %}
To encourage collaborators in your repository, you need a community that encourages people to use, contribute to, and evangelize your project. For more information, see "[Building Welcoming Communities](https://opensource.guide/building-community/)" in the Open Source Guides.
-By adding files like contributing guidelines, a code of conduct, and a license to your repository you can create an environment where it's easier for collaborators to make meaningful, useful contributions. 更多信息请参阅“[设置健康参与的项目](/communities/setting-up-your-project-for-healthy-contributions)”。
+By adding files like contributing guidelines, a code of conduct, and a license to your repository you can create an environment where it's easier for collaborators to make meaningful, useful contributions. For more information, see "[Setting up your project for healthy contributions](/communities/setting-up-your-project-for-healthy-contributions)."
{% endif %}
{% ifversion ghes or ghae %}
-By adding files like contributing guidelines, a code of conduct, and support resources to your repository you can create an environment where it's easier for collaborators to make meaningful, useful contributions. 更多信息请参阅“[设置健康参与的项目](/communities/setting-up-your-project-for-healthy-contributions)”。
+By adding files like contributing guidelines, a code of conduct, and support resources to your repository you can create an environment where it's easier for collaborators to make meaningful, useful contributions. For more information, see "[Setting up your project for healthy contributions](/communities/setting-up-your-project-for-healthy-contributions)."
{% endif %}
### 6. Using GitHub Issues and project boards
You can use GitHub Issues to organize your work with issues and pull requests and manage your workflow with project boards. For more information, see "[About issues](/issues/tracking-your-work-with-issues/about-issues)" and "[About project boards](/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)."
### 7. Managing notifications
-Notifications provide updates about the activity on {% data variables.product.prodname_dotcom %} you've subscribed to or participated in. 如果您的某项对话不再感兴趣，您可以取消订阅、取消关注或自定义以后接收的通知类型。 更多信息请参阅“[关于通知](/github/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications)”。
+Notifications provide updates about the activity on {% data variables.product.prodname_dotcom %} you've subscribed to or participated in. If you're no longer interested in a conversation, you can unsubscribe, unwatch, or customize the types of notifications you'll receive in the future. For more information, see "[About notifications](/github/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications)."
-### 8. 使用 {% data variables.product.prodname_pages %}
-You can use {% data variables.product.prodname_pages %} to create and host a website directly from a repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}. 更多信息请参阅“[关于 {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages)”。
+### 8. Working with {% data variables.product.prodname_pages %}
+You can use {% data variables.product.prodname_pages %} to create and host a website directly from a repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}. For more information, see "[About {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages)."
{% ifversion fpt or ghec %}
-### 9. 使用 {% data variables.product.prodname_discussions %}
-You can enable {% data variables.product.prodname_discussions %} for your repository to help build a community around your project. Maintainers, contributors and visitors can use discussions to share announcements, ask and answer questions, and participate in conversations around goals. 更多信息请参阅“[关于讨论](/discussions/collaborating-with-your-community-using-discussions/about-discussions)”。
+### 9. Using {% data variables.product.prodname_discussions %}
+You can enable {% data variables.product.prodname_discussions %} for your repository to help build a community around your project. Maintainers, contributors and visitors can use discussions to share announcements, ask and answer questions, and participate in conversations around goals. For more information, see "[About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions)."
{% endif %}
## Part 4: Customizing and automating your work on {% data variables.product.product_name %}
{% data reusables.getting-started.customizing-and-automating %}
{% ifversion fpt or ghec %}
-### 1. 使用 {% data variables.product.prodname_marketplace %}
+### 1. Using {% data variables.product.prodname_marketplace %}
{% data reusables.getting-started.marketplace %}
{% endif %}
### {% ifversion fpt or ghec %}2.{% else %}1.{% endif %} Using the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API
@@ -154,29 +154,29 @@ You can enable {% data variables.product.prodname_discussions %} for your reposi
### {% ifversion fpt or ghec %}3.{% else %}2.{% endif %} Building {% data variables.product.prodname_actions %}
{% data reusables.getting-started.actions %}
-### {% ifversion fpt or ghec %}4.{% else %}3.{% endif %} Publishing and managing {% data variables.product.prodname_registry %}
+### {% ifversion fpt or ghec %}4.{% else %}3.{% endif %} Publishing and managing {% data variables.product.prodname_registry %}
{% data reusables.getting-started.packages %}
## Part 5: Building securely on {% data variables.product.product_name %}
{% data variables.product.product_name %} has a variety of security features that help keep code and secrets secure in repositories. Some features are available for all repositories, while others are only available for public repositories and repositories with a {% data variables.product.prodname_GH_advanced_security %} license. For an overview of {% data variables.product.product_name %} security features, see "[{% data variables.product.prodname_dotcom %} security features](/code-security/getting-started/github-security-features)."
-### 1. 保护您的仓库
-As a repository administrator, you can secure your repositories by configuring repository security settings. These include managing access to your repository, setting a security policy, and managing dependencies. For public repositories, and for private repositories owned by organizations where {% data variables.product.prodname_GH_advanced_security %} is enabled, you can also configure code and secret scanning to automatically identify vulnerabilities and ensure tokens and keys are not exposed.
+### 1. Securing your repository
+As a repository administrator, you can secure your repositories by configuring repository security settings. These include managing access to your repository, setting a security policy, and managing dependencies. For public repositories, and for private repositories owned by organizations where {% data variables.product.prodname_GH_advanced_security %} is enabled, you can also configure code and secret scanning to automatically identify vulnerabilities and ensure tokens and keys are not exposed.
For more information on steps you can take to secure your repositories, see "[Securing your repository](/code-security/getting-started/securing-your-repository)."
{% ifversion fpt or ghec %}
### 2. Managing your dependencies
-A large part of building securely is maintaining your project's dependencies to ensure that all packages and applications you depend on are updated and secure. You can manage your repository's dependencies on {% data variables.product.product_name %} by exploring the dependency graph for your repository, using Dependabot to automatically raise pull requests to keep your dependencies up-to-date, and receiving Dependabot alerts and security updates for vulnerable dependencies.
+A large part of building securely is maintaining your project's dependencies to ensure that all packages and applications you depend on are updated and secure. You can manage your repository's dependencies on {% data variables.product.product_name %} by exploring the dependency graph for your repository, using Dependabot to automatically raise pull requests to keep your dependencies up-to-date, and receiving Dependabot alerts and security updates for vulnerable dependencies.
For more information, see "[Securing your software supply chain](/code-security/supply-chain-security)."
{% endif %}
-## 第 6 部分：参与 {% data variables.product.prodname_dotcom %} 的社区
+## Part 6: Participating in {% data variables.product.prodname_dotcom %}'s community
{% data reusables.getting-started.participating-in-community %}
-### 1. 为开源项目做贡献
+### 1. Contributing to open source projects
{% data reusables.getting-started.open-source-projects %}
### 2. Interacting with {% data variables.product.prodname_gcf %}
@@ -193,11 +193,11 @@ For more information, see "[Securing your software supply chain](/code-security/
### 5. Supporting the open source community
{% data reusables.getting-started.sponsors %}
-### 6. 联系 {% data variables.contact.github_support %}
+### 6. Contacting {% data variables.contact.github_support %}
{% data reusables.getting-started.contact-support %}
{% ifversion fpt %}
-## 延伸阅读
-- "[开始使用 {% data variables.product.prodname_team %}](/get-started/onboarding/getting-started-with-github-team)"
+## Further reading
+- "[Getting started with {% data variables.product.prodname_team %}](/get-started/onboarding/getting-started-with-github-team)"
{% endif %}
{% endif %}
diff --git a/translations/zh-CN/content/github-cli/github-cli/github-cli-reference.md b/translations/zh-CN/content/github-cli/github-cli/github-cli-reference.md
index 8ebd76264ce7..42ae410fd501 100644
--- a/translations/zh-CN/content/github-cli/github-cli/github-cli-reference.md
+++ b/translations/zh-CN/content/github-cli/github-cli/github-cli-reference.md
@@ -1,6 +1,6 @@
---
-title: GitHub CLI reference
-intro: 'You can view all of the {% data variables.product.prodname_cli %} commands in your terminal or in the {% data variables.product.prodname_cli %} manual.'
+title: GitHub CLI 引用
+intro: '您可以在终端或 {% data variables.product.prodname_cli %} 手册中查看所有 {% data variables.product.prodname_cli %} 命令。'
versions:
fpt: '*'
ghes: '*'
@@ -11,25 +11,25 @@ topics:
type: reference
---
-To view all top-level {% data variables.product.prodname_cli %} commands, see the [{% data variables.product.prodname_cli %} manual](https://cli.github.com/manual/gh) or call `gh` without arguments.
+要查看所有顶层 {% data variables.product.prodname_cli %} 命令，请参阅 [{% data variables.product.prodname_cli %} 手册](https://cli.github.com/manual/gh)或调用不带参数的 `gh`。
```shell
gh
```
-To list all commands under a specific group, use the top-level command without arguments. For example, to list [commands for managing repositories](https://cli.github.com/manual/gh_repo):
+要列出特定组下的所有命令，请使用不带参数的顶层命令。 例如，要列出[用于管理存储库的命令](https://cli.github.com/manual/gh_repo)：
```shell
gh repo
```
-To view the environment variables that can be used with {% data variables.product.prodname_cli %}, see the [{% data variables.product.prodname_cli %} manual](https://cli.github.com/manual/gh_help_environment) or use the `environment` command.
+要查看可与 {% data variables.product.prodname_cli %} 一起使用的环境变量，请参阅 [{% data variables.product.prodname_cli %} 手册](https://cli.github.com/manual/gh_help_environment) 或使用 `environment` 命令。
```shell
gh environment
```
-To view the configuration settings that can be used with {% data variables.product.prodname_cli %}, see the [{% data variables.product.prodname_cli %} manual](https://cli.github.com/manual/gh_config) or use the `config` command.
+要查看可与 {% data variables.product.prodname_cli %}一起使用的配置设置，请参阅 [{% data variables.product.prodname_cli %} 手册](https://cli.github.com/manual/gh_config) 或使用 `config` 命令。
```shell
gh config
diff --git a/translations/zh-CN/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-allowed-ip-addresses-for-your-organization.md b/translations/zh-CN/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-allowed-ip-addresses-for-your-organization.md
index 365e0a9e9dc0..d720d1d2d02c 100644
--- a/translations/zh-CN/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-allowed-ip-addresses-for-your-organization.md
+++ b/translations/zh-CN/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-allowed-ip-addresses-for-your-organization.md
@@ -82,4 +82,4 @@ shortTitle: 管理允许的 IP 地址
## 对 {% data variables.product.prodname_actions %} 使用 IP 允许列表
-{% data reusables.github-actions.ip-allow-list-self-hosted-runners %}
+{% data reusables.actions.ip-allow-list-self-hosted-runners %}
diff --git a/translations/zh-CN/content/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities.md b/translations/zh-CN/content/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities.md
index 0e758434ef46..5f5d90e93124 100644
--- a/translations/zh-CN/content/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities.md
+++ b/translations/zh-CN/content/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities.md
@@ -28,9 +28,15 @@ SSH 证书是一种机制：一个 SSH 密钥对另一个 SSH 密钥签名。
即使您实施了 SAML 单点登录，组织成员也可使用其签名的证书进行身份验证。 除非您将 SSH 证书设为要求，组织成员可继续使用其他验证方式通过 Git 访问组织的资源，包括他们的用户名和密码、个人访问令牌及其自己的 SSH 密钥。
{% endif %}
-成员将无法使用其证书访问其用户帐户拥有的仓库的复刻。
+Members will not be able to use their certificates to access forks of your repositories that are owned by their personal accounts.
-为防止身份验证错误，组织成员应使用包含组织 ID 的特殊 URL，以使用签名证书克隆仓库。 对仓库具有读取权限的任何人都可在仓库页面上找到此 URL。 更多信息请参阅“[克隆仓库](/articles/cloning-a-repository)”。
+## About SSH URLs with SSH certificates
+
+If your organization requires SSH certificates, to prevent authentication errors, organization members should use a special URL that includes the organization ID when performing Git operations over SSH. This special URL allows the client and server to more easily negotiate which key on the member's computer should be used for authentication. If a member uses the normal URL, which starts with `git@github.com`, the SSH client might offer the wrong key, causing the operation to fail.
+
+Anyone with read access to the repository can find this URL by selecting the **Code** dropdown menu on the main page of the repository, then clicking **Use SSH**.
+
+If your organization doesn't require SSH certificates, members can continue to use their own SSH keys, or other means of authentication. In that case, either the special URL or the normal URL, which starts with `git@github.com`, will work.
## 颁发证书
diff --git a/translations/zh-CN/content/organizations/managing-git-access-to-your-organizations-repositories/managing-your-organizations-ssh-certificate-authorities.md b/translations/zh-CN/content/organizations/managing-git-access-to-your-organizations-repositories/managing-your-organizations-ssh-certificate-authorities.md
index 47563450b84f..be5cc1995525 100644
--- a/translations/zh-CN/content/organizations/managing-git-access-to-your-organizations-repositories/managing-your-organizations-ssh-certificate-authorities.md
+++ b/translations/zh-CN/content/organizations/managing-git-access-to-your-organizations-repositories/managing-your-organizations-ssh-certificate-authorities.md
@@ -20,9 +20,11 @@ shortTitle: 管理 SSH 机构
您可以通过向组织添加 SSH CA 来允许成员使用提供的 SSH 证书访问组织的仓库。 {% data reusables.organizations.can-require-ssh-cert %} 更多信息请参阅“[关于 SSH 认证中心](/articles/about-ssh-certificate-authorities)”。
+{% data reusables.organizations.add-extension-to-cert %}
+
## 添加 SSH 认证中心
-{% data reusables.organizations.add-extension-to-cert %}
+If you require SSH certificates for your enterprise, enterprise members should use a special URL for Git operations over SSH. 更多信息请参阅“[关于 SSH 认证中心](/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities#about-ssh-urls-with-ssh-certificates)”。
{% data reusables.profile.access_org %}
{% data reusables.profile.org_settings %}
diff --git a/translations/zh-CN/content/organizations/managing-organization-settings/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-organization.md b/translations/zh-CN/content/organizations/managing-organization-settings/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-organization.md
index e33d572b7b28..54362fb17b51 100644
--- a/translations/zh-CN/content/organizations/managing-organization-settings/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-organization.md
+++ b/translations/zh-CN/content/organizations/managing-organization-settings/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-organization.md
@@ -21,4 +21,4 @@ shortTitle: 配置保留期
{% data reusables.organizations.navigate-to-org %}
{% data reusables.organizations.org_settings %}
{% data reusables.organizations.settings-sidebar-actions %}
-{% data reusables.github-actions.change-retention-period-for-artifacts-logs %}
+{% data reusables.actions.change-retention-period-for-artifacts-logs %}
diff --git a/translations/zh-CN/content/organizations/managing-organization-settings/deleting-an-organization-account.md b/translations/zh-CN/content/organizations/managing-organization-settings/deleting-an-organization-account.md
index 962b2030ac78..bde6389e87bc 100644
--- a/translations/zh-CN/content/organizations/managing-organization-settings/deleting-an-organization-account.md
+++ b/translations/zh-CN/content/organizations/managing-organization-settings/deleting-an-organization-account.md
@@ -12,7 +12,7 @@ versions:
topics:
- Organizations
- Teams
-shortTitle: 删除组织帐户
+shortTitle: Delete organization
---
{% ifversion fpt or ghec %}
@@ -26,7 +26,15 @@ shortTitle: 删除组织帐户
## 1. 备份组织内容
-删除组织后，GitHub **无法恢复内容**。 因此，在删除组织之前，请确保您拥有该帐户中所有仓库、wiki、议题和项目板的副本。
+{% ifversion not ghes %} After you delete an organization, {% data variables.product.company_short %} **cannot restore your content**. Therefore, before{% else %}Before{% endif %} you delete your organization, make sure you have a copy of all repositories, wikis, issues, and project boards from the account.
+
+{% ifversion ghes %}
+{% note %}
+
+**Note:** If necessary, a site administrator for {% data variables.product.product_location %} may be able to partially restore a deleted organization. For more information, see "[Restoring a deleted organization](/admin/user-management/managing-organizations-in-your-enterprise/restoring-a-deleted-organization)."
+
+{% endnote %}
+{% endif %}
## 2. 删除组织
diff --git a/translations/zh-CN/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md b/translations/zh-CN/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md
index 53904df98e89..226cd076dce4 100644
--- a/translations/zh-CN/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md
+++ b/translations/zh-CN/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md
@@ -19,11 +19,11 @@ shortTitle: 禁用或限制操作
## 关于组织的 {% data variables.product.prodname_actions %} 权限
-{% data reusables.github-actions.disabling-github-actions %} 有关 {% data variables.product.prodname_actions %} 的更多信息，请参阅“[关于 {% data variables.product.prodname_actions %}](/actions/getting-started-with-github-actions/about-github-actions)”。
+{% data reusables.actions.disabling-github-actions %} 有关 {% data variables.product.prodname_actions %} 的更多信息，请参阅“[关于 {% data variables.product.prodname_actions %}](/actions/getting-started-with-github-actions/about-github-actions)”。
-您可以对组织中的所有仓库启用 {% data variables.product.prodname_actions %}。 {% data reusables.github-actions.enabled-actions-description %} 您可以对组织中的所有仓库禁用 {% data variables.product.prodname_actions %}。 {% data reusables.github-actions.disabled-actions-description %}
+您可以对组织中的所有仓库启用 {% data variables.product.prodname_actions %}。 {% data reusables.actions.enabled-actions-description %} 您可以对组织中的所有仓库禁用 {% data variables.product.prodname_actions %}。 {% data reusables.actions.disabled-actions-description %}
-此外，您可以对组织中的所有仓库启用 {% data variables.product.prodname_actions %}，但限制工作流程可以运行的操作。 {% data reusables.github-actions.enabled-local-github-actions %}
+此外，您可以对组织中的所有仓库启用 {% data variables.product.prodname_actions %}，但限制工作流程可以运行的操作。 {% data reusables.actions.enabled-local-github-actions %}
## 管理组织的 {% data variables.product.prodname_actions %} 权限
@@ -68,7 +68,7 @@ shortTitle: 禁用或限制操作
{% data reusables.profile.access_org %}
{% data reusables.profile.org_settings %}
{% data reusables.organizations.settings-sidebar-actions %}
-{% data reusables.github-actions.workflows-from-public-fork-setting %}
+{% data reusables.actions.workflows-from-public-fork-setting %}
{% data reusables.actions.workflow-run-approve-link %}
{% endif %}
@@ -76,28 +76,28 @@ shortTitle: 禁用或限制操作
{% ifversion fpt or ghes or ghec %}
## 为私有仓库复刻启用工作流程
-{% data reusables.github-actions.private-repository-forks-overview %}
+{% data reusables.actions.private-repository-forks-overview %}
{% ifversion ghec or ghae or ghes %}如果对企业禁用了某个策略，则无法对组织启用该策略。{% endif %} 如果对组织禁用了某个策略，则无法对仓库启用该策略。 如果组织启用了某个策略，则可以对个别仓库禁用该策略。
-{% data reusables.github-actions.private-repository-forks-options %}
+{% data reusables.actions.private-repository-forks-options %}
### 为组织配置私有复刻策略
{% data reusables.profile.access_org %}
{% data reusables.profile.org_settings %}
{% data reusables.organizations.settings-sidebar-actions %}
-{% data reusables.github-actions.private-repository-forks-configure %}
+{% data reusables.actions.private-repository-forks-configure %}
{% endif %}
{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
## 为您的组织设置 `GITHUB_TOKENN` 的权限
-{% data reusables.github-actions.workflow-permissions-intro %}
+{% data reusables.actions.workflow-permissions-intro %}
您可以在组织或仓库的设置中为 `GITHUB_TOKEN` 设置默认权限。 如果您在组织设置中选择受限制的选项为默认值，则在您的组织内仓库的设置中，自动选择相同的选项，允许选项也会被禁用。 如果您的组织属于 {% data variables.product.prodname_enterprise %} 帐户，并且在企业设置中选择了更受限制的默认值，则您将无法在组织设置中选择更宽松的默认值。
-{% data reusables.github-actions.workflow-permissions-modifying %}
+{% data reusables.actions.workflow-permissions-modifying %}
### 配置默认 `GITHUB_TOKENN` 权限
diff --git a/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork.md b/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork.md
index dde9ca7cc1fc..5124c25f5711 100644
--- a/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork.md
+++ b/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork.md
@@ -13,6 +13,7 @@ versions:
ghec: '*'
topics:
- Pull requests
+permissions: People with write access for a forked repository can sync the fork to the upstream repository.
---
{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
@@ -20,8 +21,8 @@ topics:
## 从 web UI 同步复刻
1. 在 {% data variables.product.product_name %} 上，导航到您想要与上游版本库同步的复刻仓库主页。
-1. 选择 **Fetch upstream（提取上游）**下拉菜单。 
-1. 查看上游仓库中有关提交的细节，然后单击“**提取并合并**”。 
+2. 选择 **Fetch upstream（提取上游）**下拉菜单。 
+3. 查看上游仓库中有关提交的细节，然后单击“**提取并合并**”。 
如果上游仓库的更改导致冲突，{% data variables.product.company_short %} 将提示您创建拉取请求以解决冲突。
@@ -33,6 +34,7 @@ topics:
{% data reusables.command_line.open_the_multi_os_terminal %}
2. 将当前工作目录更改为您的本地仓库。
3. 从上游仓库获取分支及其各自的提交。 对 `BRANCHNAME` 的提交将存储在本地分支 `upstream/BRANCHNAME` 中。
+
```shell
$ git fetch upstream
> remote: Counting objects: 75, done.
@@ -42,12 +44,16 @@ topics:
> From https://{% data variables.command_line.codeblock %}/ORIGINAL_OWNER/ORIGINAL_REPOSITORY
> * [new branch] main -> upstream/main
```
+
4. 检出复刻的本地默认分支 - 在本例中，我们使用 `main`。
+
```shell
$ git checkout main
> Switched to branch 'main'
```
+
5. 将上游默认分支 - 本例中为 `upstream/main` - 的更改合并到本地默认分支。 这会使复刻的默认分支与上游仓库同步，而不会丢失本地更改。
+
```shell
$ git merge upstream/main
> Updating a422352..5fdff0f
diff --git a/translations/zh-CN/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/about-commits.md b/translations/zh-CN/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/about-commits.md
index 5c29a5c876f5..39cff7a415b5 100644
--- a/translations/zh-CN/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/about-commits.md
+++ b/translations/zh-CN/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/about-commits.md
@@ -6,6 +6,7 @@ redirect_from:
- /github/committing-changes-to-your-project/why-are-my-commits-in-the-wrong-order
- /github/committing-changes-to-your-project/about-commits
- /github/committing-changes-to-your-project/creating-and-editing-commits/about-commits
+ - /pull-requests/committing-changes-to-your-project/viewing-and-comparing-commits/commit-branch-and-tag-labels
versions:
fpt: '*'
ghes: '*'
@@ -24,5 +25,20 @@ versions:
变基允许您更改一系列提交，并且可以修改时间表中的提交顺序。 更多信息请参阅“[关于 Git 变基](/github/getting-started-with-github/about-git-rebase)”。
+## About commit branches and tag labels
+
+You can see which branch a commit is on by looking at the labels beneath the commit on the commit page.
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.navigate-to-commit-page %}
+1. 通过单击提交消息链接导航到提交。 
+2. To see what branch the commit is on, check the label below the commit message. 
+
+If your commit is not on the default branch (`main`), the label will show the branches which contain the commit. If the commit is part of an unmerged pull request, you can click the link to go to the pull request.
+
+如果提交在默认分支上，将显示包含提交的任何标记，并且默认分支将是列出的唯一分支。 For more information on tags, see "[Git Basics - Tagging](https://git-scm.com/book/en/v2/Git-Basics-Tagging)" in the Git documentation.
+
+
+
## 延伸阅读
- {% data variables.product.prodname_desktop %} 上的“[提交和审查对项目的更改](/desktop/contributing-to-projects/committing-and-reviewing-changes-to-your-project#about-commits)”
diff --git a/translations/zh-CN/content/pull-requests/committing-changes-to-your-project/viewing-and-comparing-commits/commit-branch-and-tag-labels.md b/translations/zh-CN/content/pull-requests/committing-changes-to-your-project/viewing-and-comparing-commits/commit-branch-and-tag-labels.md
deleted file mode 100644
index 7722a54c6362..000000000000
--- a/translations/zh-CN/content/pull-requests/committing-changes-to-your-project/viewing-and-comparing-commits/commit-branch-and-tag-labels.md
+++ /dev/null
@@ -1,27 +0,0 @@
----
-title: 提交分支和标记标签
-intro: 通过在提交页面上查看提交下方的标签，可轻松找出提交所在的分支。
-redirect_from:
- - /articles/commit-branch-and-tag-labels
- - /github/committing-changes-to-your-project/commit-branch-and-tag-labels
- - /github/committing-changes-to-your-project/viewing-and-comparing-commits/commit-branch-and-tag-labels
-versions:
- fpt: '*'
- ghes: '*'
- ghae: '*'
- ghec: '*'
-shortTitle: 分支和标记标签
----
-
-如果您的提交不在默认分支上，则指示符将显示包含提交的分支。 如果提交是未合并拉取请求的一部分，它将显示一个链接。
-
-
-
-如果提交在默认分支上，将显示包含提交的任何标记，并且默认分支将是列出的唯一分支。
-
-
-
-## 延伸阅读
-
-* "[对提交签名](/articles/signing-commits)"
-* "[对标记签名](/articles/signing-tags)"
diff --git a/translations/zh-CN/content/pull-requests/committing-changes-to-your-project/viewing-and-comparing-commits/index.md b/translations/zh-CN/content/pull-requests/committing-changes-to-your-project/viewing-and-comparing-commits/index.md
index a5c8e3f70253..9d681bff26d3 100644
--- a/translations/zh-CN/content/pull-requests/committing-changes-to-your-project/viewing-and-comparing-commits/index.md
+++ b/translations/zh-CN/content/pull-requests/committing-changes-to-your-project/viewing-and-comparing-commits/index.md
@@ -10,7 +10,6 @@ versions:
ghae: '*'
ghec: '*'
children:
- - /commit-branch-and-tag-labels
- /comparing-commits
- /differences-between-commit-views
shortTitle: 查看和比较提交
diff --git a/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/enabling-or-disabling-github-discussions-for-a-repository.md b/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/enabling-or-disabling-github-discussions-for-a-repository.md
index 496ee53485af..099ad3de0ded 100644
--- a/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/enabling-or-disabling-github-discussions-for-a-repository.md
+++ b/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/enabling-or-disabling-github-discussions-for-a-repository.md
@@ -1,6 +1,6 @@
---
title: 启用或禁用仓库的 GitHub 讨论
-intro: 'You can use {% data variables.product.prodname_discussions %} in a repository as a place for your community to have conversations, ask questions, and post answers without scoping work in an issue.'
+intro: '您可以将存储库中的 {% data variables.product.prodname_discussions %} 用作社区进行对话、提出问题和发布答案的位置，而无需界定议题的范围。'
product: '{% data reusables.gated-features.discussions %}'
permissions: 'People with admin permissions to a repository can enable {% data variables.product.prodname_discussions %} for the repository.'
versions:
@@ -11,10 +11,10 @@ topics:
redirect_from:
- /github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository
- /github/administering-a-repository/managing-repository-settings/enabling-or-disabling-github-discussions-for-a-repository
-shortTitle: 讨论
+shortTitle: Discussions
---
-## Enabling or disabling {% data variables.product.prodname_discussions %} for your repository
+## 为存储库启用或禁用 {% data variables.product.prodname_discussions %}
{% data reusables.discussions.enabling-or-disabling-github-discussions-for-your-repository %}
1. 要禁用讨论，请在“Features（功能）”下，取消选择 **Discussions（讨论）**。
diff --git a/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md b/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md
index d43b4c742177..d9dfad26e27a 100644
--- a/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md
+++ b/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md
@@ -24,11 +24,11 @@ shortTitle: 管理 GitHub Actions 设置
## 关于仓库的 {% data variables.product.prodname_actions %} 权限
-{% data reusables.github-actions.disabling-github-actions %} 有关 {% data variables.product.prodname_actions %} 的更多信息，请参阅“[关于 {% data variables.product.prodname_actions %}](/actions/getting-started-with-github-actions/about-github-actions)”。
+{% data reusables.actions.disabling-github-actions %} 有关 {% data variables.product.prodname_actions %} 的更多信息，请参阅“[关于 {% data variables.product.prodname_actions %}](/actions/getting-started-with-github-actions/about-github-actions)”。
-您可以对您的仓库启用 {% data variables.product.prodname_actions %}。 {% data reusables.github-actions.enabled-actions-description %} 您可以对您的仓库完全禁用 {% data variables.product.prodname_actions %}。 {% data reusables.github-actions.disabled-actions-description %}
+您可以对您的仓库启用 {% data variables.product.prodname_actions %}。 {% data reusables.actions.enabled-actions-description %} 您可以对您的仓库完全禁用 {% data variables.product.prodname_actions %}。 {% data reusables.actions.disabled-actions-description %}
-此外，您可以在您的仓库中启用 {% data variables.product.prodname_actions %}，但限制工作流程可以运行的操作。 {% data reusables.github-actions.enabled-local-github-actions %}
+此外，您可以在您的仓库中启用 {% data variables.product.prodname_actions %}，但限制工作流程可以运行的操作。 {% data reusables.actions.enabled-local-github-actions %}
## 管理仓库的 {% data variables.product.prodname_actions %} 权限
@@ -78,34 +78,34 @@ shortTitle: 管理 GitHub Actions 设置
{% data reusables.repositories.navigate-to-repo %}
{% data reusables.repositories.sidebar-settings %}
{% data reusables.repositories.settings-sidebar-actions %}
-{% data reusables.github-actions.workflows-from-public-fork-setting %}
+{% data reusables.actions.workflows-from-public-fork-setting %}
{% data reusables.actions.workflow-run-approve-link %}
{% endif %}
## 为私有仓库复刻启用工作流程
-{% data reusables.github-actions.private-repository-forks-overview %}
+{% data reusables.actions.private-repository-forks-overview %}
如果为 {% ifversion ghec or ghae or ghes %}企业或{% endif %} 组织禁用了某个策略，则无法为存储库启用该策略。
-{% data reusables.github-actions.private-repository-forks-options %}
+{% data reusables.actions.private-repository-forks-options %}
### 为仓库配置私有复刻策略
{% data reusables.repositories.navigate-to-repo %}
{% data reusables.repositories.sidebar-settings %}
{% data reusables.repositories.settings-sidebar-actions %}
-{% data reusables.github-actions.private-repository-forks-configure %}
+{% data reusables.actions.private-repository-forks-configure %}
{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
## 为您的仓库设置 `GITHUB_TOKENN` 的权限
-{% data reusables.github-actions.workflow-permissions-intro %}
+{% data reusables.actions.workflow-permissions-intro %}
默认权限也可以在组织设置中配置。 如果在组织设置中选择了更受限制的默认值，则在仓库设置中自动选择相同的选项，并禁用许可的选项。
-{% data reusables.github-actions.workflow-permissions-modifying %}
+{% data reusables.actions.workflow-permissions-modifying %}
### 配置默认 `GITHUB_TOKENN` 权限
@@ -152,4 +152,4 @@ shortTitle: 管理 GitHub Actions 设置
{% data reusables.repositories.navigate-to-repo %}
{% data reusables.repositories.sidebar-settings %}
{% data reusables.repositories.settings-sidebar-actions %}
-{% data reusables.github-actions.change-retention-period-for-artifacts-logs %}
+{% data reusables.actions.change-retention-period-for-artifacts-logs %}
diff --git a/translations/zh-CN/content/rest/overview/index.md b/translations/zh-CN/content/rest/overview/index.md
index 72708734170f..f794a035a3de 100644
--- a/translations/zh-CN/content/rest/overview/index.md
+++ b/translations/zh-CN/content/rest/overview/index.md
@@ -18,5 +18,6 @@ children:
- /libraries
- /openapi-description
- /endpoints-available-for-github-apps
+ - /permissions-required-for-github-apps
---
diff --git a/translations/zh-CN/content/rest/reference/permissions-required-for-github-apps.md b/translations/zh-CN/content/rest/overview/permissions-required-for-github-apps.md
similarity index 99%
rename from translations/zh-CN/content/rest/reference/permissions-required-for-github-apps.md
rename to translations/zh-CN/content/rest/overview/permissions-required-for-github-apps.md
index 7bd5f733f1ac..e30225240753 100644
--- a/translations/zh-CN/content/rest/reference/permissions-required-for-github-apps.md
+++ b/translations/zh-CN/content/rest/overview/permissions-required-for-github-apps.md
@@ -3,6 +3,7 @@ title: GitHub 应用程序所需的权限
intro: '您可以找到每个 {% data variables.product.prodname_github_app %} 兼容端点所需的权限。'
redirect_from:
- /v3/apps/permissions
+ - /rest/reference/permissions-required-for-github-apps
versions:
fpt: '*'
ghes: '*'
diff --git a/translations/zh-CN/content/rest/reference/actions.md b/translations/zh-CN/content/rest/reference/actions.md
index ce79dfaffc00..ffdc12e11fec 100644
--- a/translations/zh-CN/content/rest/reference/actions.md
+++ b/translations/zh-CN/content/rest/reference/actions.md
@@ -13,93 +13,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-
-{% data variables.product.prodname_actions %} API 允许您使用 REST API 来管理 {% data variables.product.prodname_actions %}。 {% data reusables.actions.actions-authentication %} {% data variables.product.prodname_github_apps %} 需要在每个端点中提及的权限。 更多信息请参阅“[{% data variables.product.prodname_actions %} 文档](/actions)”。
-
-{% for operation in currentRestOperations %}
- {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
-{% endfor %}
-
-## 构件
-
-构件 API 允许您下载、删除和检索有关工作流程构件的信息。 {% data reusables.actions.about-artifacts %}更多信息请参阅“[使用构件持久化工作流程](/actions/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)”。
-
-{% data reusables.actions.actions-authentication %} {% data reusables.actions.actions-app-actions-permissions-api %}
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'artifacts' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% ifversion fpt or ghes > 2.22 or ghae or ghec %}
-## 权限
-
-Permissions API 允许您为允许哪些企业、组织和存储库运行 {% data variables.product.prodname_actions %} 以及允许运行哪些操作设置权限。{% ifversion fpt or ghec or ghes %} 更多信息请参阅“[使用限制、计费和管理](/actions/reference/usage-limits-billing-and-administration#disabling-or-limiting-github-actions-for-your-repository-or-organization)”。{% endif %}
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'permissions' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-{% endif %}
-
-## 密码
-
-密码 API 允许您创建、更新、删除和检索有关加密密码的信息。 {% data reusables.actions.about-secrets %}更多信息请参阅“[创建和使用加密密码](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)”。
-
-{% data reusables.actions.actions-authentication %} {% data variables.product.prodname_github_apps %} 必须具有`密码`权限才可使用此 API。 经过身份验证的用户必须对仓库具有协作者权限才可创建、更新或读取密码。
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'secrets' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## 自托管运行器
-
-{% data reusables.actions.ae-self-hosted-runners-notice %}
-
-自托管运行器 API 允许您注册、查看和删除自托管的运行器。 {% data reusables.actions.about-self-hosted-runners %} 更多信息请参阅“[托管您自己的运行器](/actions/hosting-your-own-runners)”。
-
-{% data reusables.actions.actions-authentication %} {% data variables.product.prodname_github_apps %} 必须对仓库具有`管理`权限，或者对组织具有 `organization_self_hosted_runners` 权限。 经过身份验证的用户必须具有对存储库或组织的管理员访问权限或者企业的 `manage_runners:enterprise` 作用域才能使用此 API。
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'self-hosted-runners' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## 自托管运行器组
-
-{% data reusables.actions.ae-self-hosted-runners-notice %}
-
-自托管运行器组 API 允许您管理自托运行器组。 更多信息请参阅“[使用组管理对自托管运行器的访问](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups)”。
-
-{% data reusables.actions.actions-authentication %} {% data variables.product.prodname_github_apps %} 必须对仓库具有`管理`权限，或者对组织具有 `organization_self_hosted_runners` 权限。 经过身份验证的用户必须具有对存储库或组织的管理员访问权限或者企业的 `manage_runners:enterprise` 作用域才能使用此 API。
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'self-hosted-runner-groups' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## 工作流程
-
-工作流程 API 允许您查看仓库的工作流程。 {% data reusables.actions.about-workflows %} 更多信息请参阅“[使用 GitHub Actions 自动化工作流程](/actions/automating-your-workflow-with-github-actions)”。
-
-{% data reusables.actions.actions-authentication %} {% data reusables.actions.actions-app-actions-permissions-api %}
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'workflows' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## 工作流程作业
-
-工作流程作业 API 允许您查看日志和工作流程作业。 {% data reusables.actions.about-workflow-jobs %} 更多信息请参阅“[GitHub Actions 的工作流程语法](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions)”。
-
-{% data reusables.actions.actions-authentication %} {% data reusables.actions.actions-app-actions-permissions-api %}
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'workflow-jobs' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## 工作流程运行
-
-工作流程运行 API 允许您查看、重新运行、取消和查看工作流程运行的日志。 {% data reusables.actions.about-workflow-runs %} 更多信息请参阅“[管理工作流程运行](/actions/automating-your-workflow-with-github-actions/managing-a-workflow-run)”。
-
-{% data reusables.actions.actions-authentication %} {% data reusables.actions.actions-app-actions-permissions-api %}
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'workflow-runs' %}{% include rest_operation %}{% endif %}
-{% endfor %}
+
diff --git a/translations/zh-CN/content/rest/reference/activity.md b/translations/zh-CN/content/rest/reference/activity.md
index 804b4094d240..39b7b738a775 100644
--- a/translations/zh-CN/content/rest/reference/activity.md
+++ b/translations/zh-CN/content/rest/reference/activity.md
@@ -1,6 +1,6 @@
---
-title: Activity
-intro: 'The Activity API allows you to list events and feeds and manage notifications, starring, and watching for the authenticated user.'
+title: 活动
+intro: Activity API 允许您列出事件和订阅，并管理通知、星标和关注认证用户。
redirect_from:
- /v3/activity
versions:
@@ -13,186 +13,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-{% for operation in currentRestOperations %}
- {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
-{% endfor %}
-
-## Events
-
-The Events API is a read-only API to the {% data variables.product.prodname_dotcom %} events. These events power the various activity streams on the site.
-
-The Events API can return different types of events triggered by activity on {% data variables.product.product_name %}. For more information about the specific events that you can receive from the Events API, see "[{% data variables.product.prodname_dotcom %} Event types](/developers/webhooks-and-events/github-event-types)." An events API for repository issues is also available. For more information, see the "[Issue Events API](/rest/reference/issues#events)."
-
-Events are optimized for polling with the "ETag" header. If no new events have been triggered, you will see a "304 Not Modified" response, and your current rate limit will be untouched. There is also an "X-Poll-Interval" header that specifies how often (in seconds) you are allowed to poll. In times of high server load, the time may increase. Please obey the header.
-
-``` shell
-$ curl -I {% data variables.product.api_url_pre %}/users/tater/events
-> HTTP/2 200
-> X-Poll-Interval: 60
-> ETag: "a18c3bded88eb5dbb5c849a489412bf3"
-
-# The quotes around the ETag value are important
-$ curl -I {% data variables.product.api_url_pre %}/users/tater/events \
-$ -H 'If-None-Match: "a18c3bded88eb5dbb5c849a489412bf3"'
-> HTTP/2 304
-> X-Poll-Interval: 60
-```
-
-Only events created within the past 90 days will be included in timelines. Events older than 90 days will not be included (even if the total number of events in the timeline is less than 300).
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'events' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## Feeds
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'feeds' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-### Example of getting an Atom feed
-
-To get a feed in Atom format, you must specify the `application/atom+xml` type in the `Accept` header. For example, to get the Atom feed for GitHub security advisories:
-
- curl -H "Accept: application/atom+xml" https://github.com/security-advisories
-
-#### Response
-
-```shell
-HTTP/2 200
-```
-
-```xml
-
-
- tag:github.com,2008:/security-advisories
-
- GitHub Security Advisory Feed
-
- GitHub
-
- 2019-01-14T19:34:52Z
-
- tag:github.com,2008:GHSA-abcd-12ab-23cd
- 2018-07-26T15:14:52Z
- 2019-01-14T19:34:52Z
- [GHSA-abcd-12ab-23cd] Moderate severity vulnerability that affects Octoapp
-
-
- <p>Octoapp node module before 4.17.5 suffers from a Modification of Assumed-Immutable Data (MAID) vulnerability via defaultsDeep, merge, and mergeWith functions, which allows a malicious user to modify the prototype of "Object" via <strong>proto</strong>, causing the addition or modification of an existing property that will exist on all objects.</p>
- <p><strong>Affected Packages</strong></p>
-
- <dl>
- <dt>Octoapp</dt>
- <dd>Ecosystem: npm</dd>
- <dd>Severity: moderate</dd>
- <dd>Versions: < 4.17.5</dd>
- <dd>Fixed in: 4.17.5</dd>
- </dl>
-
- <p><strong>References</strong></p>
-
- <ul>
- <li>https://nvd.nist.gov/vuln/detail/CVE-2018-123</li>
- </ul>
-
-
-
-
-```
-
-## Notifications
-
-Users receive notifications for conversations in repositories they watch including:
-
-* Issues and their comments
-* Pull Requests and their comments
-* Comments on any commits
-
-Notifications are also sent for conversations in unwatched repositories when the user is involved including:
-
-* **@mentions**
-* Issue assignments
-* Commits the user authors or commits
-* Any discussion in which the user actively participates
-
-All Notification API calls require the `notifications` or `repo` API scopes. Doing this will give read-only access to some issue and commit content. You will still need the `repo` scope to access issues and commits from their respective endpoints.
-
-Notifications come back as "threads". A thread contains information about the current discussion of an issue, pull request, or commit.
-
-Notifications are optimized for polling with the `Last-Modified` header. If there are no new notifications, you will see a `304 Not Modified` response, leaving your current rate limit untouched. There is an `X-Poll-Interval` header that specifies how often (in seconds) you are allowed to poll. In times of high server load, the time may increase. Please obey the header.
-
-``` shell
-# Add authentication to your requests
-$ curl -I {% data variables.product.api_url_pre %}/notifications
-HTTP/2 200
-Last-Modified: Thu, 25 Oct 2012 15:16:27 GMT
-X-Poll-Interval: 60
-
-# Pass the Last-Modified header exactly
-$ curl -I {% data variables.product.api_url_pre %}/notifications
-$ -H "If-Modified-Since: Thu, 25 Oct 2012 15:16:27 GMT"
-> HTTP/2 304
-> X-Poll-Interval: 60
-```
-
-### Notification reasons
-
-When retrieving responses from the Notifications API, each payload has a key titled `reason`. These correspond to events that trigger a notification.
-
-Here's a list of potential `reason`s for receiving a notification:
-
-Reason Name | Description
-------------|------------
-`assign` | You were assigned to the issue.
-`author` | You created the thread.
-`comment` | You commented on the thread.
-`ci_activity` | A {% data variables.product.prodname_actions %} workflow run that you triggered was completed.
-`invitation` | You accepted an invitation to contribute to the repository.
-`manual` | You subscribed to the thread (via an issue or pull request).
-`mention` | You were specifically **@mentioned** in the content.
-`review_requested` | You, or a team you're a member of, were requested to review a pull request.{% ifversion fpt or ghec %}
-`security_alert` | {% data variables.product.prodname_dotcom %} discovered a [security vulnerability](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies) in your repository.{% endif %}
-`state_change` | You changed the thread state (for example, closing an issue or merging a pull request).
-`subscribed` | You're watching the repository.
-`team_mention` | You were on a team that was mentioned.
-
-Note that the `reason` is modified on a per-thread basis, and can change, if the `reason` on a later notification is different.
-
-For example, if you are the author of an issue, subsequent notifications on that issue will have a `reason` of `author`. If you're then **@mentioned** on the same issue, the notifications you fetch thereafter will have a `reason` of `mention`. The `reason` remains as `mention`, regardless of whether you're ever mentioned again.
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'notifications' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## Starring
-
-Repository starring is a feature that lets users bookmark repositories. Stars are shown next to repositories to show an approximate level of interest. Stars have no effect on notifications or the activity feed.
-
-### Starring vs. Watching
-
-In August 2012, we [changed the way watching
-works](https://github.com/blog/1204-notifications-stars) on {% data variables.product.prodname_dotcom %}. Many API
-client applications may be using the original "watcher" endpoints for accessing
-this data. You can now start using the "star" endpoints instead (described
-below). For more information, see the [Watcher API Change post](https://developer.github.com/changes/2012-09-05-watcher-api/) and the "[Repository Watching API](/rest/reference/activity#watching)."
-
-### Custom media types for starring
-
-There is one supported custom media type for the Starring REST API. When you use this custom media type, you will receive a response with the `starred_at` timestamp property that indicates the time the star was created. The response also has a second property that includes the resource that is returned when the custom media type is not included. The property that contains the resource will be either `user` or `repo`.
-
- application/vnd.github.v3.star+json
-
-For more information about media types, see "[Custom media types](/rest/overview/media-types)."
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'starring' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## Watching
-
-Watching a repository registers the user to receive notifications on new discussions, as well as events in the user's activity feed. For simple repository bookmarks, see "[Repository starring](/rest/reference/activity#starring)."
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'watching' %}{% include rest_operation %}{% endif %}
-{% endfor %}
+
diff --git a/translations/zh-CN/content/rest/reference/apps.md b/translations/zh-CN/content/rest/reference/apps.md
index fe8a5dc5ffa8..156e662afe70 100644
--- a/translations/zh-CN/content/rest/reference/apps.md
+++ b/translations/zh-CN/content/rest/reference/apps.md
@@ -1,6 +1,6 @@
---
-title: Apps
-intro: 'The GitHub Apps API enables you to retrieve the information about the installation as well as specific information about GitHub Apps.'
+title: 应用
+intro: GitHub Apps API 使您能够检索有关安装的信息以及有关 GitHub 应用程序的特定信息。
redirect_from:
- /v3/apps
versions:
@@ -13,66 +13,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-{% data reusables.apps.general-apps-restrictions %}
-
-This page lists endpoints that you can access while authenticated as a GitHub App. See "[Authenticating as a GitHub App](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-a-github-app)" to learn more.
-
-When authenticated as a GitHub App, the GitHub Apps API enables you to get high-level information about a GitHub App as well as specific information about installations of an app.
-
-You can access REST API v3 endpoints while authenticated as a GitHub App. These endpoints have a "Notes" section that contains a bullet point that says "Works with GitHub Apps." You can also access these endpoints while authenticated as a user.
-
-A subset of REST API v3 endpoints requires authenticating as a GitHub App installation. See [Installations](/rest/reference/apps#installations) for a list of these endpoints.
-
-{% for operation in currentRestOperations %}
- {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
-{% endfor %}
-
-## OAuth Applications API
-
-You can use this API to manage the OAuth tokens an OAuth application uses to access people's accounts on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}.
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'oauth-applications' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## Installations
-
-The Installations API enables you to get information about installations of your GitHub App and perform actions within those installations. An _installation_ refers to any user or organization account that has installed the app. For information on how to authenticate as an installation and limit access to specific repositories, see "[Authenticating as an installation](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation)."
-
-To list all GitHub App installations for an organization, see "[List app installations for an organization](/rest/reference/orgs#list-app-installations-for-an-organization)."
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'installations' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% ifversion fpt or ghec %}
-## Marketplace
-
-For more information about {% data variables.product.prodname_marketplace %}, see "[GitHub Marketplace](/marketplace/)."
-
-The {% data variables.product.prodname_marketplace %} API allows you to see which customers are using a pricing plan, see a customer's purchases, and see if an account has an active subscription.
-
-### Testing with stubbed endpoints
-
-This API includes endpoints that allow you to [test your {% data variables.product.prodname_github_app %}](/marketplace/integrating-with-the-github-marketplace-api/testing-github-marketplace-apps/) with **stubbed data**. Stubbed data is hard-coded, fake data that will not change based on actual subscriptions.
-
-To test with stubbed data, use a stubbed endpoint in place of its production counterpart. This allows you to test whether API logic succeeds before listing {% data variables.product.prodname_github_apps %} on {% data variables.product.prodname_marketplace %}.
-
-Be sure to replace stubbed endpoints with production endpoints before deploying your {% data variables.product.prodname_github_app %}.
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'marketplace' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% endif %}
-
-{% ifversion fpt or ghes > 2.22 or ghae or ghec %}
-## Webhooks
-
-A {% data variables.product.prodname_github_app %}'s webhook allows you to receive HTTP `POST` payloads whenever certain events happen for an app. {% data reusables.webhooks.webhooks-rest-api-links %}
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'webhooks' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% endif %}
+
diff --git a/translations/zh-CN/content/rest/reference/billing.md b/translations/zh-CN/content/rest/reference/billing.md
index 6136986e5086..441b78aed177 100644
--- a/translations/zh-CN/content/rest/reference/billing.md
+++ b/translations/zh-CN/content/rest/reference/billing.md
@@ -10,8 +10,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-您可以获取企业的帐单信息。 更多信息请参阅“[{% data variables.product.prodname_dotcom %} Enterprise 管理](/rest/reference/enterprise-admin#billing)”REST API。
-
-{% for operation in currentRestOperations %}
- {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
-{% endfor %}
+
diff --git a/translations/zh-CN/content/rest/reference/branches.md b/translations/zh-CN/content/rest/reference/branches.md
index ab8cfe944c43..14dc2b718382 100644
--- a/translations/zh-CN/content/rest/reference/branches.md
+++ b/translations/zh-CN/content/rest/reference/branches.md
@@ -12,11 +12,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-{% for operation in currentRestOperations %}
- {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
-{% endfor %}
-
-## 受保护分支
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'branch-protection' %}{% include rest_operation %}{% endif %}
-{% endfor %}
+
diff --git a/translations/zh-CN/content/rest/reference/checks.md b/translations/zh-CN/content/rest/reference/checks.md
index 88cf892caada..74fe8fccbf65 100644
--- a/translations/zh-CN/content/rest/reference/checks.md
+++ b/translations/zh-CN/content/rest/reference/checks.md
@@ -13,26 +13,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-您可以创建应用程序以执行持续集成 、代码分析或代码扫描服务，并提供有关提交的详细反馈。 更多信息请参阅“[检查 API 入门指南](/rest/guides/getting-started-with-the-checks-api)”和“[使用检查 API 创建 CI 测试](/apps/quickstart-guides/creating-ci-tests-with-the-checks-api/)”。
-
-{% for operation in currentRestOperations %}
- {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
-{% endfor %}
-
-## 检查运行
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'runs' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## 检查套件
-
-{% note %}
-
- **注：**GitHub 应用程序针对每个提交 SHA 只接收一个 [`check_suite`](/webhooks/event-payloads/#check_suite) 事件，即使您将提交 SHA 推送到多个分支。 要了解提交 SHA 何时推送到分支，您可以订阅分支 [`create`](/webhooks/event-payloads/#create) 事件。
-
-{% endnote %}
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'suites' %}{% include rest_operation %}{% endif %}
-{% endfor %}
+
diff --git a/translations/zh-CN/content/rest/reference/code-scanning.md b/translations/zh-CN/content/rest/reference/code-scanning.md
index 91630168a321..84228437b090 100644
--- a/translations/zh-CN/content/rest/reference/code-scanning.md
+++ b/translations/zh-CN/content/rest/reference/code-scanning.md
@@ -17,20 +17,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-{% data reusables.code-scanning.beta %}
-
-{% data variables.product.prodname_code_scanning %} API 可让您从仓库检索和更新 {% data variables.product.prodname_code_scanning %} 警报。 您可以使用端点为组织中的 {% data variables.product.prodname_code_scanning %} 警报创建自动报告，或上传使用离线 {% data variables.product.prodname_code_scanning %} 工具生成的分析结果。 更多信息请参阅“[查找代码中的安全漏洞和错误](/github/finding-security-vulnerabilities-and-errors-in-your-code)”。
-
-{% ifversion fpt or ghes > 3.0 or ghae or ghec %}
-### {% data variables.product.prodname_code_scanning %} 的自定义媒体类型
-
-{% data variables.product.prodname_code_scanning %} REST API 有一种支持的自定义媒体类型。
-
- application/sarif+json
-
-您可以将此请求与发送到 `/analyses/{analysis_id}` 端点的 `GET` 请求一起使用。 有关此操作的更多信息，请参阅“[获取仓库的 {% data variables.product.prodname_code_scanning %} 分析](#get-a-code-scanning-analysis-for-a-repository)”。 当您使用此媒体类型进行此操作时，响应包括上传用于指定分析的实际数据的子集，而不是使用默认媒体类型时返回的分析摘要。 响应还包括其他数据，如 `github/alertNumber` 和 `github/alertUrl` 属性。 数据格式为 [SARIF 版本 2.1.0](https://docs.oasis-open.org/sarif/sarif/v2.1.0/cs01/sarif-v2.1.0-cs01.html)。
-
-更多信息请参阅“[媒体类型](/rest/overview/media-types)”。
-{% endif %}
-
-{% include rest_operations_at_current_path %}
+
diff --git a/translations/zh-CN/content/rest/reference/codes-of-conduct.md b/translations/zh-CN/content/rest/reference/codes-of-conduct.md
index 1b32335c4647..08b8c5f1bbff 100644
--- a/translations/zh-CN/content/rest/reference/codes-of-conduct.md
+++ b/translations/zh-CN/content/rest/reference/codes-of-conduct.md
@@ -14,6 +14,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-您可以使用行为准则 API 检索有关仓库行为准则的信息。 要获取仓库的行为准则，请使用“[获取仓库](/rest/reference/repos#get-a-repository)”端点。
-
-{% include rest_operations_at_current_path %}
+
diff --git a/translations/zh-CN/content/rest/reference/codespaces.md b/translations/zh-CN/content/rest/reference/codespaces.md
index 7902c7409796..11f28ca6432e 100644
--- a/translations/zh-CN/content/rest/reference/codespaces.md
+++ b/translations/zh-CN/content/rest/reference/codespaces.md
@@ -10,24 +10,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-{% data reusables.codespaces.codespaces-api-beta-note %}
-
-{% data variables.product.prodname_codespaces %} API 允许您使用 REST API 来管理 {% data variables.product.prodname_codespaces %}。 This API is available for authenticated users and OAuth Apps, but not GitHub Apps. For more information, see "[{% data variables.product.prodname_codespaces %}](/codespaces)."
-
-{% for operation in currentRestOperations %}
- {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
-{% endfor %}
-
-## Machines
-The Machines API allows a user to determine which machine types are available to create a codespace, either on a given repository or as an authenticated user. For more information, see "[About machine types](/codespaces/developing-in-codespaces/changing-the-machine-type-for-your-codespace#about-machine-types)."
-
-You can also use this information when changing the machine of an existing codespace by updating its `machine` property. The machine update will take place the next time the codespace is restarted. For more information, see "[Changing the machine type for your codespace](/codespaces/developing-in-codespaces/changing-the-machine-type-for-your-codespace)."
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'machines' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## 密码
-The Secrets API allows a user to create, list, and delete secrets (such as access tokens for cloud services) as well as assign secrets to repositories that the user has access to. These secrets are made available to the codespace at runtime. For more information, see "[Managing encrypted secrets for your codespaces](/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces)."
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'secrets' %}{% include rest_operation %}{% endif %}
-{% endfor %}
+
\ No newline at end of file
diff --git a/translations/zh-CN/content/rest/reference/collaborators.md b/translations/zh-CN/content/rest/reference/collaborators.md
index b2e53c7d05ab..a4551b91128e 100644
--- a/translations/zh-CN/content/rest/reference/collaborators.md
+++ b/translations/zh-CN/content/rest/reference/collaborators.md
@@ -12,20 +12,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-{% for operation in currentRestOperations %}
- {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
-{% endfor %}
-
-## 邀请
-
-仓库邀请 API 允许用户或外部服务邀请其他用户参与仓库协作。 受邀用户（或代表受邀用户的外部服务）可以选择接受或拒绝邀请。
-
-请注意，`repo:invite` [OAuth 作用域](/developers/apps/scopes-for-oauth-apps)授予对邀请的定向访问权限，但**不**授予对仓库代码的访问权限，而 `repo` 作用域同时授予对代码和邀请的权限。
-
-### 邀请用户参与仓库
-
-使用 API 端点来添加协作者。 更多信息请参阅“[添加仓库协作者](/rest/reference/collaborators#add-a-repository-collaborator)”。
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'invitations' %}{% include rest_operation %}{% endif %}
-{% endfor %}
+
diff --git a/translations/zh-CN/content/rest/reference/commits.md b/translations/zh-CN/content/rest/reference/commits.md
index 30fe07f1cab7..30267fb4de1f 100644
--- a/translations/zh-CN/content/rest/reference/commits.md
+++ b/translations/zh-CN/content/rest/reference/commits.md
@@ -12,41 +12,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-{% for operation in currentRestOperations %}
- {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
-{% endfor %}
-
-## 提交注释
-
-### 提交评论的自定义媒体类型
-
-以下是提交评论支持的媒体类型。 您可以在[此处](/rest/overview/media-types)阅读有关 API 中媒体类型使用情况的更多信息。
-
- application/vnd.github-commitcomment.raw+json
- application/vnd.github-commitcomment.text+json
- application/vnd.github-commitcomment.html+json
- application/vnd.github-commitcomment.full+json
-
-更多信息请参阅“[自定义媒体类型](/rest/overview/media-types)”。
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'comments' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## 提交状态
-
-状态 API 允许外部服务将提交标记为 `error`、`failure`、`pending` 或 `success` 状态，然后将其反映在涉及这些提交的拉取请求中。
-
-状态还可以包含可选的 `description` 和 `target_url`，强烈建议使用它们，因为它们使状态在 GitHub UI 中更有用。
-
-一种常见用例是持续集成服务使用状态将提交标记为构建成功或失败。 `target_url` 是构建输出的完整 URL，`description` 是关于构建过程中所发生情况的高级摘要。
-
-状态可以包括 `context` 以指示提供该状态的服务是什么。 例如，您可以让持续集成服务推送上下文为 `ci` 的状态，让安全审核工具推送上下文为 `security` 的状态。 然后，您可以使用[获取特定引用的组合状态](/rest/reference/commits#get-the-combined-status-for-a-specific-reference)来检索提交的整个状态。
-
-请注意，`repo:status` [OAuth 作用域](/developers/apps/scopes-for-oauth-apps)授予对状态的定向访问权限，但**不**授予对仓库代码的访问权限，而 `repo` 作用域同时授予对代码和状态的权限。
-
-如果您正在开发 GitHub 应用程序，希望提供有关外部服务的更多信息，则可能需要使用[检查 API](/rest/reference/checks)。
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'statuses' %}{% include rest_operation %}{% endif %}
-{% endfor %}
+
diff --git a/translations/zh-CN/content/rest/reference/dependabot.md b/translations/zh-CN/content/rest/reference/dependabot.md
index 7a59833f3dcc..5fe2940b7c99 100644
--- a/translations/zh-CN/content/rest/reference/dependabot.md
+++ b/translations/zh-CN/content/rest/reference/dependabot.md
@@ -10,10 +10,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-The {% data variables.product.prodname_dependabot %} Secrets API lets you create, update, delete, and retrieve information about encrypted secrets. {% data reusables.actions.about-secrets %} For more information, see "[Managing encrypted secrets for Dependabot](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-encrypted-secrets-for-dependabot)."
-
-{% data reusables.actions.actions-authentication %} {% data variables.product.prodname_github_apps %} must have the `dependabot_secrets` permission to use this API. 经过身份验证的用户必须对仓库具有协作者权限才可创建、更新或读取密码。
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'secrets' %}{% include rest_operation %}{% endif %}
-{% endfor %}
+
\ No newline at end of file
diff --git a/translations/zh-CN/content/rest/reference/deployments.md b/translations/zh-CN/content/rest/reference/deployments.md
index 5098506d454b..0b4daf9c5e11 100644
--- a/translations/zh-CN/content/rest/reference/deployments.md
+++ b/translations/zh-CN/content/rest/reference/deployments.md
@@ -12,81 +12,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-部署是部署特定引用（分支、SHA、标记）的请求。 GitHub 分发一个 [`deployment` 事件](/developers/webhooks-and-events/webhook-events-and-payloads#deployment)，使外部服务可以在创建新部署时侦听并采取行动。 部署使开发者和组织能够围绕部署构建松散耦合的工具，而不必担心交付不同类型的应用程序（例如 Web 和本地应用程序）的实现细节。
-
-部署状态允许外部服务将部署标记为 `error`、`failure`、`pending`、`in_progress`、`queued` 或 `success` 状态，以供侦听 [`deployment_status` 事件](/developers/webhooks-and-events/webhook-events-and-payloads#deployment_status)的系统使用。
-
-部署状态还可以包含可选的 `description` 和 `log_url`，强烈建议使用它们，因为它们使部署状态更有用。 `log_url` 是部署输出的完整 URL，`description` 是关于部署过程中所发生情况的高级摘要。
-
-在创建新的部署和部署状态时，GitHub 将分发 `deployment` 和 `deployment_status` 事件。 这些事件允许第三方集成接收对部署请求的响应，并在取得进展时更新部署的状态。
-
-下面是一个说明这些交互的工作方式的简单序列图。
-
-```
-+---------+ +--------+ +-----------+ +-------------+
-| Tooling | | GitHub | | 3rd Party | | Your Server |
-+---------+ +--------+ +-----------+ +-------------+
- | | | |
- | Create Deployment | | |
- |--------------------->| | |
- | | | |
- | Deployment Created | | |
- |<---------------------| | |
- | | | |
- | | Deployment Event | |
- | |---------------------->| |
- | | | SSH+Deploys |
- | | |-------------------->|
- | | | |
- | | Deployment Status | |
- | |<----------------------| |
- | | | |
- | | | Deploy Completed |
- | | |<--------------------|
- | | | |
- | | Deployment Status | |
- | |<----------------------| |
- | | | |
-```
-
-请记住，GitHub 从未真正访问过您的服务器。 与部署事件的交互取决于第三方集成。 多个系统可以侦听部署事件，由其中每个系统来决定它们是否负责将代码推送到服务器、构建本地代码等。
-
-请注意，`repo_deployment` [OAuth 作用域](/developers/apps/scopes-for-oauth-apps)授予对部署和部署状态的定向访问权限，但**不**授予对仓库代码的访问权限，而 {% ifversion not ghae %}`public_repo` 和{% endif %}`repo` 作用域还授予对代码的权限。
-
-### 非活动部署
-
-当您将部署状态设置为 `success` 时，同一仓库中所有先前的非瞬态、非生产环境部署将变成 `inactive`。 为避免这种情况，您可以在创建部署状态时将 `auto_inactive` 设置为 `false`。
-
-您可以通过将 `state` 设为 `inactive` 来表示某个瞬态环境不再存在。 将 `state` 设为 `inactive`，表示部署在 {% data variables.product.prodname_dotcom %} 中 `destroyed` 并删除对它的访问权限。
-
-{% for operation in currentRestOperations %}
- {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
-{% endfor %}
-
-## 部署状态
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'statuses' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## 部署密钥
-
-{% data reusables.repositories.deploy-keys %}
-
-部署密钥可以使用以下 API 端点进行设置，也可以使用 GitHub 进行设置。 要了解如何在 GitHub 中设置部署密钥，请参阅“[管理部署密钥](/developers/overview/managing-deploy-keys)”。
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'keys' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
-## 环境
-
-环境 API 允许您创建、配置和删除环境。 有关环境的更多信息，请参阅“[使用环境进行部署](/actions/deployment/using-environments-for-deployment)”。 要管理环境密码，请参阅“[密码](/rest/reference/actions#secrets)”。
-
-{% data reusables.gated-features.environments %}
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'environments' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-{% endif %}
+
diff --git a/translations/zh-CN/content/rest/reference/emojis.md b/translations/zh-CN/content/rest/reference/emojis.md
index d2d3a1da6782..05b0229fe39a 100644
--- a/translations/zh-CN/content/rest/reference/emojis.md
+++ b/translations/zh-CN/content/rest/reference/emojis.md
@@ -14,4 +14,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-{% include rest_operations_at_current_path %}
+
diff --git a/translations/zh-CN/content/rest/reference/enterprise-admin.md b/translations/zh-CN/content/rest/reference/enterprise-admin.md
index 303f997677e8..c1f2d237c5fd 100644
--- a/translations/zh-CN/content/rest/reference/enterprise-admin.md
+++ b/translations/zh-CN/content/rest/reference/enterprise-admin.md
@@ -16,309 +16,6 @@ miniTocMaxHeadingLevel: 3
shortTitle: Enterprise administration
---
-{% ifversion fpt or ghec %}
-
-{% note %}
-
-**Note:** This article applies to {% data variables.product.prodname_ghe_cloud %}. To see the {% data variables.product.prodname_ghe_managed %} or {% data variables.product.prodname_ghe_server %} version, use the **{% data ui.pages.article_version %}** drop-down menu.
-
-{% endnote %}
-
-{% endif %}
-
-### Endpoint URLs
-
-REST API endpoints{% ifversion ghes %}—except [Management Console](#management-console) API endpoints—{% endif %} are prefixed with the following URL:
-
-```shell
-{% data variables.product.api_url_pre %}
-```
-
-{% ifversion fpt or ghec %}
-When endpoints include `{enterprise}`, replace `{enterprise}` with the handle for your enterprise account, which is included in the URL for your enterprise settings. For example, if your enterprise account is located at `https://github.com/enterprises/octo-enterprise`, replace `{enterprise}` with `octo-enterprise`.
-{% endif %}
-
-{% ifversion ghes %}
-[Management Console](#management-console) API endpoints are only prefixed with a hostname:
-
-```shell
-http(s)://hostname/
-```
-{% endif %}
-{% ifversion ghae or ghes %}
-### Authentication
-
-Your {% data variables.product.product_name %} installation's API endpoints accept [the same authentication methods](/rest/overview/resources-in-the-rest-api#authentication) as the GitHub.com API. You can authenticate yourself with **[OAuth tokens](/apps/building-integrations/setting-up-and-registering-oauth-apps/)** {% ifversion ghes %}(which can be created using the [Authorizations API](/rest/reference/oauth-authorizations#create-a-new-authorization)) {% endif %}or **[basic authentication](/rest/overview/resources-in-the-rest-api#basic-authentication)**. {% ifversion ghes %}
-OAuth tokens must have the `site_admin` [OAuth scope](/developers/apps/scopes-for-oauth-apps#available-scopes) when used with Enterprise-specific endpoints.{% endif %}
-
-Enterprise administration API endpoints are only accessible to authenticated {% data variables.product.product_name %} site administrators{% ifversion ghes %}, except for the [Management Console](#management-console) API, which requires the [Management Console password](/enterprise/admin/articles/accessing-the-management-console/){% endif %}.
-
-{% endif %}
-
-{% ifversion ghae or ghes %}
-### Version information
-
-The current version of your enterprise is returned in the response header of every API:
-`X-GitHub-Enterprise-Version: {{currentVersion}}.0`
-You can also read the current version by calling the [meta endpoint](/rest/reference/meta/).
-
-{% for operation in currentRestOperations %}
- {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
-{% endfor %}
-
-{% endif %}
-
-{% ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5528 %}
-
-## Audit log
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'audit-log' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% endif %}
-
-{% ifversion fpt or ghec or ghes > 3.3 %}
-## Billing
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'billing' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% endif %}
-
-{% ifversion ghae or ghes %}
-## Admin stats
-
-The Admin Stats API provides a variety of metrics about your installation. *It is only available to [authenticated](/rest/overview/resources-in-the-rest-api#authentication) site administrators.* Normal users will receive a `404` response if they try to access it.
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'admin-stats' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% endif %}
-
-{% ifversion ghae or ghes > 2.22 %}
-
-## Announcements
-
-The Announcements API allows you to manage the global announcement banner in your enterprise. For more information, see "[Customizing user messages for your enterprise](/admin/user-management/customizing-user-messages-for-your-enterprise#creating-a-global-announcement-banner)."
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'announcement' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% endif %}
-
-{% ifversion ghae or ghes %}
-
-## Global webhooks
-
-Global webhooks are installed on your enterprise. You can use global webhooks to automatically monitor, respond to, or enforce rules for users, organizations, teams, and repositories on your enterprise. Global webhooks can subscribe to the [organization](/developers/webhooks-and-events/webhook-events-and-payloads#organization), [user](/developers/webhooks-and-events/webhook-events-and-payloads#user), [repository](/developers/webhooks-and-events/webhook-events-and-payloads#repository), [team](/developers/webhooks-and-events/webhook-events-and-payloads#team), [member](/developers/webhooks-and-events/webhook-events-and-payloads#member), [membership](/developers/webhooks-and-events/webhook-events-and-payloads#membership), [fork](/developers/webhooks-and-events/webhook-events-and-payloads#fork), and [ping](/developers/webhooks-and-events/about-webhooks#ping-event) event types.
-
-*This API is only available to [authenticated](/rest/overview/resources-in-the-rest-api#authentication) site administrators.* Normal users will receive a `404` response if they try to access it. To learn how to configure global webhooks, see [About global webhooks](/enterprise/admin/user-management/about-global-webhooks).
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'global-webhooks' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% endif %}
-
-{% ifversion ghes %}
-
-## LDAP
-
-You can use the LDAP API to update account relationships between a {% data variables.product.product_name %} user or team and its linked LDAP entry or queue a new synchronization.
-
-With the LDAP mapping endpoints, you're able to update the Distinguished Name (DN) that a user or team maps to. Note that the LDAP endpoints are generally only effective if your {% data variables.product.product_name %} appliance has [LDAP Sync enabled](/enterprise/admin/authentication/using-ldap). The [Update LDAP mapping for a user](#update-ldap-mapping-for-a-user) endpoint can be used when LDAP is enabled, even if LDAP Sync is disabled.
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'ldap' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% endif %}
-
-{% ifversion ghae or ghes %}
-## License
-
-The License API provides information on your Enterprise license. *It is only available to [authenticated](/rest/overview/resources-in-the-rest-api#authentication) site administrators.* Normal users will receive a `404` response if they try to access it.
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'license' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% endif %}
-
-{% ifversion ghes %}
-
-## Management console
-
-The Management Console API helps you manage your {% data variables.product.product_name %} installation.
-
-{% tip %}
-
-You must explicitly set the port number when making API calls to the Management Console. If TLS is enabled on your enterprise, the port number is `8443`; otherwise, the port number is `8080`.
-
-If you don't want to provide a port number, you'll need to configure your tool to automatically follow redirects.
-
-You may also need to add the [`-k` flag](http://curl.haxx.se/docs/manpage.html#-k) when using `curl`, since {% data variables.product.product_name %} uses a self-signed certificate before you [add your own TLS certificate](/enterprise/admin/guides/installation/configuring-tls/).
-
-{% endtip %}
-
-### Authentication
-
-You need to pass your [Management Console password](/enterprise/admin/articles/accessing-the-management-console/) as an authentication token to every Management Console API endpoint except [`/setup/api/start`](#create-a-github-enterprise-server-license).
-
-Use the `api_key` parameter to send this token with each request. For example:
-
-```shell
-$ curl -L 'https://hostname:admin_port/setup/api?api_key=your-amazing-password'
-```
-
-You can also use standard HTTP authentication to send this token. For example:
-
-```shell
-$ curl -L -u "api_key:your-amazing-password" 'https://hostname:admin_port/setup/api'
-```
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'management-console' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% endif %}
-
-{% ifversion ghae or ghes %}
-## Organizations
-
-The Organization Administration API allows you to create organizations on your enterprise. *It is only available to [authenticated](/rest/overview/resources-in-the-rest-api#authentication) site administrators.* Normal users will receive a `404` response if they try to access it.
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'orgs' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% endif %}
-
-{% ifversion ghes %}
-## Organization pre-receive hooks
-
-The Organization Pre-receive Hooks API allows you to view and modify
-enforcement of the pre-receive hooks that are available to an organization.
-
-### Object attributes
-
-| Name | Type | Description |
-|----------------------------------|-----------|-----------------------------------------------------------|
-| `name` | `string` | The name of the hook. |
-| `enforcement` | `string` | The state of enforcement for the hook on this repository. |
-| `allow_downstream_configuration` | `boolean` | Whether repositories can override enforcement. |
-| `configuration_url` | `string` | URL for the endpoint where enforcement is set. |
-
-Possible values for *enforcement* are `enabled`, `disabled` and`testing`. `disabled` indicates the pre-receive hook will not run. `enabled` indicates it will run and reject
-any pushes that result in a non-zero status. `testing` means the script will run but will not cause any pushes to be rejected.
-
-`configuration_url` may be a link to this endpoint or this hook's global
-configuration. Only site admins are able to access the global configuration.
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'org-pre-receive-hooks' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% endif %}
-
-{% ifversion ghes %}
-
-## Pre-receive environments
-
-The Pre-receive Environments API allows you to create, list, update and delete environments for pre-receive hooks. *It is only available to [authenticated](/rest/overview/resources-in-the-rest-api#authentication) site administrators.* Normal users will receive a `404` response if they try to access it.
-
-### Object attributes
-
-#### Pre-receive Environment
-
-| Name | Type | Description |
-|-----------------------|-----------|----------------------------------------------------------------------------|
-| `name` | `string` | The name of the environment as displayed in the UI. |
-| `image_url` | `string` | URL to the tarball that will be downloaded and extracted. |
-| `default_environment` | `boolean` | Whether this is the default environment that ships with {% data variables.product.product_name %}. |
-| `download` | `object` | This environment's download status. |
-| `hooks_count` | `integer` | The number of pre-receive hooks that use this environment. |
-
-#### Pre-receive Environment Download
-
-| Name | Type | Description |
-|-----------------|----------|---------------------------------------------------------|
-| `state` | `string` | The state of the most recent download. |
-| `downloaded_at` | `string` | The time when the most recent download started. |
-| `message` | `string` | On failure, this will have any error messages produced. |
-
-Possible values for `state` are `not_started`, `in_progress`, `success`, `failed`.
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'pre-receive-environments' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% endif %}
-
-{% ifversion ghes %}
-## Pre-receive hooks
-
-The Pre-receive Hooks API allows you to create, list, update and delete pre-receive hooks. *It is only available to
-[authenticated](/rest/overview/resources-in-the-rest-api#authentication) site administrators.* Normal users will receive a `404` response if they try to access it.
-
-### Object attributes
-
-#### Pre-receive Hook
-
-| Name | Type | Description |
-|----------------------------------|-----------|-----------------------------------------------------------------|
-| `name` | `string` | The name of the hook. |
-| `script` | `string` | The script that the hook runs. |
-| `script_repository` | `object` | The GitHub repository where the script is kept. |
-| `environment` | `object` | The pre-receive environment where the script is executed. |
-| `enforcement` | `string` | The state of enforcement for this hook. |
-| `allow_downstream_configuration` | `boolean` | Whether enforcement can be overridden at the org or repo level. |
-
-Possible values for *enforcement* are `enabled`, `disabled` and`testing`. `disabled` indicates the pre-receive hook will not run. `enabled` indicates it will run and reject
-any pushes that result in a non-zero status. `testing` means the script will run but will not cause any pushes to be rejected.
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'pre-receive-hooks' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% endif %}
-
-{% ifversion ghes %}
-
-## Repository pre-receive hooks
-
-The Repository Pre-receive Hooks API allows you to view and modify
-enforcement of the pre-receive hooks that are available to a repository.
-
-### Object attributes
-
-| Name | Type | Description |
-|---------------------|----------|-----------------------------------------------------------|
-| `name` | `string` | The name of the hook. |
-| `enforcement` | `string` | The state of enforcement for the hook on this repository. |
-| `configuration_url` | `string` | URL for the endpoint where enforcement is set. |
-
-Possible values for *enforcement* are `enabled`, `disabled` and`testing`. `disabled` indicates the pre-receive hook will not run. `enabled` indicates it will run and reject any pushes that result in a non-zero status. `testing` means the script will run but will not cause any pushes to be rejected.
-
-`configuration_url` may be a link to this repository, it's organization owner or global configuration. Authorization to access the endpoint at `configuration_url` is determined at the owner or site admin level.
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'repo-pre-receive-hooks' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% endif %}
-
-{% ifversion ghae or ghes %}
-## Users
-
-The User Administration API allows you to suspend{% ifversion ghes %}, unsuspend, promote, and demote{% endif %}{% ifversion ghae %} and unsuspend{% endif %} users on your enterprise. *It is only available to [authenticated](/rest/overview/resources-in-the-rest-api#authentication) site administrators.* Normal users will receive a `403` response if they try to access it.
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'users' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% endif %}
+
\ No newline at end of file
diff --git a/translations/zh-CN/content/rest/reference/gists.md b/translations/zh-CN/content/rest/reference/gists.md
index 88992a2cadb6..f478255f6b61 100644
--- a/translations/zh-CN/content/rest/reference/gists.md
+++ b/translations/zh-CN/content/rest/reference/gists.md
@@ -13,44 +13,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-### 身份验证
-
-您可以匿名读取公开 Gist {% ifversion ghae or ghes %}并为没有令牌的匿名用户创建它们。{% else %}，但是您必须登录到 GitHub 才能创建 Gist。{% endif %} 要代表用户读取或写入 Gist，您需要 Gist OAuth 作用域和令牌。 更多信息请参阅“[OAuth 应用程序的作用域](/developers/apps/scopes-for-oauth-apps)”。
-
-
-
-### 截断
-
-Gist API 为 Gist 中的每个文件提供最多一兆字节的内容。 通过 API 返回的每个 Gist 文件都有一个名为 `truncated` 的键。 如果 `truncated` 为 `true`，则说明文件太大，`content` 中只返回部分内容。
-
-如果您需要文件的全部内容，您可以向 `raw_url` 指定的 URL 提出 `GET` 请求。 请注意，对于超过十兆字节的文件，您需要通过 `git_pull_url` 提供的 URL 克隆 Gist。
-
-除了特定文件的内容被截断外，如果文件总数超过 300 个，则整个文件列表也可能被截断。 如果顶层 `truncated` 键为 `true`，则说明文件列表中只返回了前 300 个文件。 如果需要获取 Gist 的所有文件，您需要通过 `git_pull_url` 提供的 URL 克隆 Gist。
-
-### Gist 的自定义媒体类型
-
-以下是获取 Gist 内容所支持的媒体类型。
-
- application/vnd.github.VERSION.raw
- application/vnd.github.VERSION.base64
-
-更多信息请参阅“[媒体类型](/rest/overview/media-types)”。
-
-{% for operation in currentRestOperations %}
- {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
-{% endfor %}
-
-## 评论
-
-### Gist 评论的自定义媒体类型
-
-以下是 Gist 评论支持的媒体类型。
-
- application/vnd.github.VERSION.raw
- application/vnd.github.VERSION.base64
-
-有关媒体类型的更多信息，请参阅“[自定义媒体类型](/rest/overview/media-types)”。
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'comments' %}{% include rest_operation %}{% endif %}
-{% endfor %}
+
diff --git a/translations/zh-CN/content/rest/reference/git.md b/translations/zh-CN/content/rest/reference/git.md
index c44ac635e873..8aee10ba77d7 100644
--- a/translations/zh-CN/content/rest/reference/git.md
+++ b/translations/zh-CN/content/rest/reference/git.md
@@ -14,72 +14,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-Git 数据库 API 使您能够在 {% data variables.product.product_name %} 上的 Git 数据库中读取和写入原始 Git 对象，并列出和更新您的引用（分支头部和标记）。 有关使用 Git 数据库 API 的更多信息，请参阅“[Git 数据库 API 入门指南](/rest/guides/getting-started-with-the-git-database-api)”。
-
-{% for operation in currentRestOperations %}
- {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
-{% endfor %}
-
-## Blob
-
-Git Blob（二进制大对象）是用于将每个文件的内容存储在仓库中的对象类型。 文件的 SHA-1 哈希在 Blob 对象中计算和存储。 这些端点允许您在 {% data variables.product.product_name %} 上的 Git 数据库中读取和写入 [blob 对象](https://git-scm.com/book/en/v1/Git-Internals-Git-Objects)。 Blob 使用[这些自定义媒体类型](#custom-media-types-for-blobs)。 您可以在[此处](/rest/overview/media-types)阅读有关 API 中媒体类型使用情况的更多信息。
-
-### Blob 的自定义媒体类型
-
-以下是 blob 支持的媒体类型。
-
- application/json
- application/vnd.github.VERSION.raw
-
-更多信息请参阅“[媒体类型](/rest/overview/media-types)”。
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'blobs' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## 提交
-
-Git 提交是 Git 仓库中层次结构（[Git 树](/rest/reference/git#trees)）和文件内容 (
-Git blob
-
-{% for operation in currentRestOperations %}
-
-{% if operation.subcategory == 'commits' %}{% include rest_operation %}{% endif %}
-
-{% endfor %}
-
-
-
-## 引用
-
-Git 引用 (`git ref`) 只是一个包含 Git 提交 SHA-1 哈希的文件。 当引用 Git 提交时，您可以使用 Git 引用，这是一个易于记住的名称，而不是哈希。 可以重写 Git 引用指向新的提交。 分支只是存储新 Git 提交哈希的 Git 引用。 这些端点允许您在 {% data variables.product.product_name %} 上的 Git 数据库中读取和写入[引用](https://git-scm.com/book/en/v1/Git-Internals-Git-References)。
-
-{% for operation in currentRestOperations %}
-
-{% if operation.subcategory == 'refs' %}{% include rest_operation %}{% endif %}
-
-{% endfor %}
-
-
-
-## 标记
-
-Git 标记类似于 [Git 引用](/rest/reference/git#refs)，但它指向的 Git 提交永远不变。 当您想要指向特定发行版时，Git 标记非常有用。 这些端点允许您在 {% data variables.product.product_name %} 上的 Git 数据库中读取和写入[标记对象](https://git-scm.com/book/en/v1/Git-Internals-Git-References#Tags)。 Git 标记 API 只支持[标注的标记对象](https://git-scm.com/book/en/v1/Git-Internals-Git-References#Tags)，而不支持轻量级标记。
-
-{% for operation in currentRestOperations %}
-
-{% if operation.subcategory == 'tags' %}{% include rest_operation %}{% endif %}
-
-{% endfor %}
-
-
-
-## 树
-
-Git 树对象在 Git 仓库中的文件之间创建层次结构。 您可以使用 Git 树对象创建目录与其包含的文件之间的关系。 这些端点允许您在 {% data variables.product.product_name %} 上的 Git 数据库中读取和写入[树对象](https://git-scm.com/book/en/v1/Git-Internals-Git-Objects#Tree-Objects)。
-
-{% for operation in currentRestOperations %}
-
-{% if operation.subcategory == 'trees' %}{% include rest_operation %}{% endif %}
-
-{% endfor %}
+
diff --git a/translations/zh-CN/content/rest/reference/gitignore.md b/translations/zh-CN/content/rest/reference/gitignore.md
index e18301cc7473..8cdd487cfbaf 100644
--- a/translations/zh-CN/content/rest/reference/gitignore.md
+++ b/translations/zh-CN/content/rest/reference/gitignore.md
@@ -13,14 +13,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-当您通过 API 在 {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} 上创建新仓库时，您可以指定一个 [.gitignore 模板](/github/getting-started-with-github/ignoring-files) 在创建时应用于仓库。 .gitignore 模板 API 可列出 {% data variables.product.product_name %} [.gitignore 仓库](https://github.com/github/gitignore)并从中获取模板。
-
-### gitignore 的自定义媒体类型
-
-获取 gitignore 模板时，您可以使用以下自定义媒体类型。
-
- application/vnd.github.VERSION.raw
-
-更多信息请参阅“[媒体类型](/rest/overview/media-types)”。
-
-{% include rest_operations_at_current_path %}
+
diff --git a/translations/zh-CN/content/rest/reference/index.md b/translations/zh-CN/content/rest/reference/index.md
index 5e0f47957ceb..ffd7a7674d48 100644
--- a/translations/zh-CN/content/rest/reference/index.md
+++ b/translations/zh-CN/content/rest/reference/index.md
@@ -51,6 +51,5 @@ children:
- /teams
- /users
- /webhooks
- - /permissions-required-for-github-apps
---
diff --git a/translations/zh-CN/content/rest/reference/interactions.md b/translations/zh-CN/content/rest/reference/interactions.md
index 1979ad53dafd..6d3b542fae85 100644
--- a/translations/zh-CN/content/rest/reference/interactions.md
+++ b/translations/zh-CN/content/rest/reference/interactions.md
@@ -11,50 +11,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-用户通过评论、开设议题和创建拉取请求与仓库进行交互。 交互 API 允许具有公共仓库所有者或具有管理员访问权限的用户临时将与公共仓库的交互限于特定类型的用户。
-
-{% for operation in currentRestOperations %}
- {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
-{% endfor %}
-
-## 组织
-
-组织交互 API 允许组织所有者临时限制哪类用户可以在组织的公共仓库中发表评论、开设议题或创建拉取请求。 {% data reusables.interactions.interactions-detail %} 以下是有关 {% data variables.product.product_name %} 用户类型的更多信息：
-
-* 组织中的 {% data reusables.interactions.existing-user-limit-definition %}。
-* 组织中的 {% data reusables.interactions.contributor-user-limit-definition %}。
-* 组织中的 {% data reusables.interactions.collaborator-user-limit-definition %}。
-
-在组织级别设置交互限制将覆盖为组织拥有的各个仓库设置的任何交互限制。 要为组织拥有的各个仓库设置不同的交互限制，请改用[仓库](#repository)交互端点。
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'orgs' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## 仓库
-
-仓库交互 API 允许具有所有者或管理员权限的用户临时限制哪类用户可以在公共仓库中发表评论、开设议题或创建拉取请求。 {% data reusables.interactions.interactions-detail %} 以下是有关 {% data variables.product.product_name %} 用户类型的更多信息：
-
-* 仓库中的 {% data reusables.interactions.existing-user-limit-definition %}。
-* 仓库中的 {% data reusables.interactions.contributor-user-limit-definition %}。
-* 仓库中的 {% data reusables.interactions.collaborator-user-limit-definition %}。
-
-如果对拥有该仓库的用户或组织启用了交互限制，单个仓库的限制就不能更改。 而应使用[用户](#user)或[组织](#organization)交互端点来更改交互限制。
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'repos' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## 用户
-
-用户交互 API 允许您临时限制哪类用户可以在公共仓库上发表评论、开设问题或创建拉取请求。 {% data reusables.interactions.interactions-detail %} 以下是有关 {% data variables.product.product_name %} 用户类型的更多信息：
-
-* 与仓库交互产生的 {% data reusables.interactions.existing-user-limit-definition %}。
-* 与仓库交互产生的 {% data reusables.interactions.contributor-user-limit-definition %}。
-* 与仓库交互产生的 {% data reusables.interactions.collaborator-user-limit-definition %}。
-
-在用户级别设置交互限制将覆盖为用户拥有的各个仓库设置的任何交互限制。 要为用户拥有的个别仓库设置不同的交互限制，请使用[仓库](#repository)交互端点。
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'user' %}{% include rest_operation %}{% endif %}
-{% endfor %}
+
diff --git a/translations/zh-CN/content/rest/reference/issues.md b/translations/zh-CN/content/rest/reference/issues.md
index 961b091be409..2b6978ce5a7b 100644
--- a/translations/zh-CN/content/rest/reference/issues.md
+++ b/translations/zh-CN/content/rest/reference/issues.md
@@ -13,63 +13,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-### 议题的自定义媒体类型
-
-以下是议题支持的媒体类型。
-
- application/vnd.github.VERSION.raw+json
- application/vnd.github.VERSION.text+json
- application/vnd.github.VERSION.html+json
- application/vnd.github.VERSION.full+json
-
-有关媒体类型的更多信息，请参阅“[自定义媒体类型](/rest/overview/media-types)”。
-
-{% for operation in currentRestOperations %}
- {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
-{% endfor %}
-
-## 受理人
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'assignees' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## 评论
-
-议题评论 API 支持列出、查看、编辑和创建对议题和拉取请求的评论。
-
-议题评论使用[这些自定义媒体类型](#custom-media-types)。 您可以在[此处](/rest/overview/media-types)阅读有关 API 中媒体类型使用情况的更多信息。
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'comments' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## 事件
-
-议题事件 API 可以返回议题和拉取请求中的活动所触发的不同类型的事件。 议题事件 API 可以返回议题和拉取请求中的活动所触发的不同类型的事件。 有关可以从议题事件 API 接收的特定事件的更多信息，请参阅“[议题事件类型](/developers/webhooks-and-events/issue-event-types)”。 更多信息请参阅“[事件 API](/developers/webhooks-and-events/github-event-types)”。
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'events' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## 标签
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'labels' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## 里程碑
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'milestones' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## 时间表
-
-时间表事件 API 可以返回议题和拉取请求中的时间表活动所触发的不同类型的事件。 议题事件 API 可以返回议题和拉取请求中的活动所触发的不同类型的事件。 有关可以从议题事件 API 接收的特定事件的更多信息，请参阅“[议题事件类型](/developers/webhooks-and-events/issue-event-types)”。 更多信息请参阅“[GitHub 事件 API](/developers/webhooks-and-events/github-event-types)”。
-
-您可以使用此 API 显示有关议题和拉取请求的信息，或确定应向谁通知议题评论。
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'timeline' %}{% include rest_operation %}{% endif %}
-{% endfor %}
+
diff --git a/translations/zh-CN/content/rest/reference/licenses.md b/translations/zh-CN/content/rest/reference/licenses.md
index a9b0b89b67a9..bd4be4a41133 100644
--- a/translations/zh-CN/content/rest/reference/licenses.md
+++ b/translations/zh-CN/content/rest/reference/licenses.md
@@ -13,27 +13,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-许可 API 返回有关热门开源许可的元数据，以及有关特定项目许可文件的信息。
-
-许可证 API 使用[开源 Ruby Gem 许可](https://github.com/benbalter/licensee)来尝试识别项目的许可。 被许可人将项目 `LICENSE` 文件（如果有）的内容与已知许可的简短列表相匹配。 因此，API 不考虑项目依赖项的许可或其他记录项目许可的方式，例如对文档中许可名称的引用。
-
-如果许可匹配，则返回的许可密钥和名称符合 [SPDX 规格](https://spdx.org/)。
-
-**注：**这些端点还将返回仓库的许可信息：
-
-- [获取仓库](/rest/reference/repos#get-a-repository)
-- [列出用户的仓库](/rest/reference/repos#list-repositories-for-a-user)
-- [列出组织仓库](/rest/reference/repos#list-organization-repositories)
-- [列出复刻](/rest/reference/repos#list-forks)
-- [列出用户关注的仓库](/rest/reference/activity#list-repositories-watched-by-a-user)
-- [列出团队仓库](/rest/reference/teams#list-team-repositories)
-
-{% warning %}
-
-GitHub 有很多功能， 但它不是律师事务所。 因此，GitHub 不提供法律建议。 使用许可 API 或向我们发送电子邮件并不构成法律意见，也不形成律师-客户关系。 如果您对特定许可可以做什么和不能做什么有任何疑问，您应该在继续之前先咨询自己的法律顾问。 事实上，在做出任何可能具有法律后果或影响您合法权利的决定之前，您都应该咨询自己的律师。
-
-GitHub 创建了许可 API，旨在帮助用户获取有关开源许可以及使用它们的项目的信息。 我们希望它有帮助，但请记住，我们不是律师（至少大多数人不是），像其他人一样，我们也会犯错。 因此，GitHub“按原样”提供 API，对提供或通过其提供的任何信息或许可不做任何保证，并对使用 API 所造成的损害不承担责任。
-
-{% endwarning %}
-
-{% include rest_operations_at_current_path %}
+
diff --git a/translations/zh-CN/content/rest/reference/markdown.md b/translations/zh-CN/content/rest/reference/markdown.md
index 9d67d5fb4242..e2bc098377ed 100644
--- a/translations/zh-CN/content/rest/reference/markdown.md
+++ b/translations/zh-CN/content/rest/reference/markdown.md
@@ -13,4 +13,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-{% include rest_operations_at_current_path %}
+
diff --git a/translations/zh-CN/content/rest/reference/meta.md b/translations/zh-CN/content/rest/reference/meta.md
index 065cd730246b..99ac3f9bd2ec 100644
--- a/translations/zh-CN/content/rest/reference/meta.md
+++ b/translations/zh-CN/content/rest/reference/meta.md
@@ -13,4 +13,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-{% include rest_operations_at_current_path %}
+
diff --git a/translations/zh-CN/content/rest/reference/metrics.md b/translations/zh-CN/content/rest/reference/metrics.md
index 0531cdb330e2..4d174aec373d 100644
--- a/translations/zh-CN/content/rest/reference/metrics.md
+++ b/translations/zh-CN/content/rest/reference/metrics.md
@@ -14,47 +14,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-{% for operation in currentRestOperations %}
- {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
-{% endfor %}
-
-{% ifversion fpt or ghec %}
-## 社区
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'community' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% endif %}
-
-## 统计
-
-仓库统计 API 允许您获取 {% data variables.product.product_name %} 用于可视化不同类型仓库活动的数据。
-
-### 谈一谈缓存
-
-计算仓库统计信息是一项昂贵的操作，所以我们尽可能返回缓存的数据。 如果您查询仓库的统计信息时，数据尚未缓存，您将会收到 `202` 响应；同时触发后台作业以开始编译这些统计信息。 稍等片刻，待作业完成，然后再次提交请求。 如果作业已完成，该请求将返回 `200` 响应，响应正文中包含统计信息。
-
-仓库统计信息由仓库默认分支的 SHA 缓存；推送到默认分支将重置统计信息缓存。
-
-### 统计排除某些类型的提交
-
-API 公开的统计信息与[各种仓库图](/github/visualizing-repository-data-with-graphs/about-repository-graphs)显示的统计信息相匹配。
-
-总结：
-- 所有统计信息都排除合并提交。
-- 参与者统计信息还排除空提交。
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'statistics' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% ifversion fpt or ghec %}
-## 流量
-
-对于您具有推送权限的仓库，流量 API 提供对仓库图中所示信息的访问权限。 更多信息请参阅“查看仓库的流量”。
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'traffic' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-{% endif %}
+
\ No newline at end of file
diff --git a/translations/zh-CN/content/rest/reference/migrations.md b/translations/zh-CN/content/rest/reference/migrations.md
index b73c56059654..682027b25634 100644
--- a/translations/zh-CN/content/rest/reference/migrations.md
+++ b/translations/zh-CN/content/rest/reference/migrations.md
@@ -15,116 +15,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-{% for operation in currentRestOperations %}
- {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
-{% endfor %}
-
-## 组织
-
-迁移 API 仅适用于经过身份验证的组织所有者。 更多信息请参阅“[组织中的角色](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#permission-levels-for-an-organization)”和“[其他身份验证方法](/rest/overview/other-authentication-methods)”。
-
-{% data variables.migrations.organization_migrations_intro %}
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'orgs' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% ifversion fpt or ghec %}
-## 源导入
-
-{% data variables.migrations.source_imports_intro %}
-
-如果导入中存在大型文件，则典型的源导入将开始导入，然后（可选）更新作者和/或更新使用 Git LFS 的首选项。 您也可以创建侦听 [`RepositoryImportEvent`](/developers/webhooks-and-events/webhook-events-and-payloads#repository_import) 的 web 挂钩来了解导入的状态。
-
-在此图中可以看到更详细的示例：
-
-```
-+---------+ +--------+ +---------------------+
-| Tooling | | GitHub | | Original Repository |
-+---------+ +--------+ +---------------------+
- | | |
- | Start import | |
- |----------------------------->| |
- | | |
- | | Download source data |
- | |--------------------------------------------->|
- | | Begin streaming data |
- | |<---------------------------------------------|
- | | |
- | Get import progress | |
- |----------------------------->| |
- | "status": "importing" | |
- |<-----------------------------| |
- | | |
- | Get commit authors | |
- |----------------------------->| |
- | | |
- | Map a commit author | |
- |----------------------------->| |
- | | |
- | | |
- | | Finish streaming data |
- | |<---------------------------------------------|
- | | |
- | | Rewrite commits with mapped authors |
- | |------+ |
- | | | |
- | |<-----+ |
- | | |
- | | Update repository on GitHub |
- | |------+ |
- | | | |
- | |<-----+ |
- | | |
- | Map a commit author | |
- |----------------------------->| |
- | | Rewrite commits with mapped authors |
- | |------+ |
- | | | |
- | |<-----+ |
- | | |
- | | Update repository on GitHub |
- | |------+ |
- | | | |
- | |<-----+ |
- | | |
- | Get large files | |
- |----------------------------->| |
- | | |
- | opt_in to Git LFS | |
- |----------------------------->| |
- | | Rewrite commits for large files |
- | |------+ |
- | | | |
- | |<-----+ |
- | | |
- | | Update repository on GitHub |
- | |------+ |
- | | | |
- | |<-----+ |
- | | |
- | Get import progress | |
- |----------------------------->| |
- | "status": "complete" | |
- |<-----------------------------| |
- | | |
- | | |
-```
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'source-imports' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-{% endif %}
-## 用户
-
-用户迁移 API 仅适用于经过身份验证的帐户所有者。 更多信息请参阅“[其他身份验证方法](/rest/overview/other-authentication-methods)”。
-
-{% data variables.migrations.user_migrations_intro %} 有关可下载的迁移数据列表，请参阅“[下载用户迁移存档](#download-a-user-migration-archive)”。
-
-要下载存档，您需要先开始用户迁移。 在迁移状态为 `exported` 后，便可下载迁移。
-
-创建迁移存档后，该存档可供下载七天。 但是，如果您喜欢，您可以更早删除用户迁移存档。 当迁移为 `exported` 时，您可以解锁仓库以便再次开始使用，如果你不再需要源数据，则可删除您的仓库。
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'users' %}{% include rest_operation %}{% endif %}
-{% endfor %}
+
diff --git a/translations/zh-CN/content/rest/reference/oauth-authorizations.md b/translations/zh-CN/content/rest/reference/oauth-authorizations.md
index b318106377f6..f374ea55b70b 100644
--- a/translations/zh-CN/content/rest/reference/oauth-authorizations.md
+++ b/translations/zh-CN/content/rest/reference/oauth-authorizations.md
@@ -8,8 +8,6 @@ versions:
miniTocMaxHeadingLevel: 3
---
-您可以使用此 API 来管理 OAuth 应用程序对您帐户的访问权限。 您只能使用您的用户名和密码（而不是令牌），通过[基本身份验证](/rest/overview/other-authentication-methods#basic-authentication)访问此 API。
-
-如果您或您的用户启用了双重身份验证，请务必了解如何[使用双重身份验证](/rest/overview/other-authentication-methods#working-with-two-factor-authentication)。
-
-{% include rest_operations_at_current_path %}
+
diff --git a/translations/zh-CN/content/rest/reference/orgs.md b/translations/zh-CN/content/rest/reference/orgs.md
index d1dd70dc52dd..25f7b8f567c4 100644
--- a/translations/zh-CN/content/rest/reference/orgs.md
+++ b/translations/zh-CN/content/rest/reference/orgs.md
@@ -14,66 +14,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-{% for operation in currentRestOperations %}
- {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
-{% endfor %}
-
-{% ifversion fpt or ghec %}
-## 阻止用户
-
-用于对调用进行身份验证的令牌必须具有 `admin:org` 作用域才可对组织进行任何阻止调用。 否则，响应将返回 `HTTP 404`。
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'blocking' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% endif %}
-
-## 成员
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'members' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## 外部协作者
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'outside-collaborators' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% ifversion fpt or ghes > 3.4 %}
-## Custom repository roles
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'custom_roles' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-{% endif %}
-
-## Web 挂钩
-
-组织 web 挂钩允许您在组织内发生特定事件时接收 HTTP `POST` 有效负载。 {% data reusables.webhooks.webhooks-rest-api-links %}
-
-有关您可以订阅的操作的更多信息，请参阅“[{% data variables.product.prodname_dotcom %} 事件类型](/developers/webhooks-and-events/github-event-types)”。
-
-### 范围和限制
-
-对组织 web 挂钩的所有操作都需要经过身份验证的用户是所管理组织的管理员。 此外，OAuth 令牌需要 `admin:org_hook` 作用域。 更多信息请参阅“[OAuth 应用程序的作用域](/developers/apps/scopes-for-oauth-apps)”。
-
-为了保护 web 挂钩配置中可能存在的敏感数据，我们还强制实施以下访问控制规则：
-
-- OAuth 应用程序无法列出、查看或编辑不是它们创建的 web 挂钩。
-- 用户无法列出、查看或编辑由 OAuth 应用程序创建的 web 挂钩。
-
-### 接收 web 挂钩
-
-为了让 {% data variables.product.product_name %} 发送 web 挂钩有效负载，您的服务器需要能够从 Internet 访问。 我们还强烈建议使用 SSL，以便我们可以通过 HTTPS 发送加密的有效负载。
-
-有关更多最佳实践，[请参阅我们的指南](/guides/best-practices-for-integrators/)。
-
-#### Web 挂钩标头
-
-{% data variables.product.product_name %} 发送时将附带几个 HTTP 标头，以区分事件类型和有效负载标识符。 更多信息请参阅 [web 挂钩标头](/webhooks/event-payloads/#delivery-headers)。
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'webhooks' %}{% include rest_operation %}{% endif %}
-{% endfor %}
+
diff --git a/translations/zh-CN/content/rest/reference/packages.md b/translations/zh-CN/content/rest/reference/packages.md
index 8af15e78f917..57b9faaf6929 100644
--- a/translations/zh-CN/content/rest/reference/packages.md
+++ b/translations/zh-CN/content/rest/reference/packages.md
@@ -1,6 +1,6 @@
---
title: Packages
-intro: 'With the {% data variables.product.prodname_registry %} API, you can manage packages for your {% data variables.product.prodname_dotcom %} repositories and organizations.'
+intro: '通过 {% data variables.product.prodname_registry %} API，您可以管理 {% data variables.product.prodname_dotcom %} 仓库和组织的软件包。'
product: '{% data reusables.gated-features.packages %}'
versions:
fpt: '*'
@@ -10,17 +10,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-The {% data variables.product.prodname_registry %} API enables you to manage packages using the REST API. To learn more about restoring or deleting packages, see "[Restoring and deleting packages](/packages/learn-github-packages/deleting-and-restoring-a-package)."
-
-To use this API, you must authenticate using a personal access token.
- - To access package metadata, your token must include the `read:packages` scope.
- - To delete packages and package versions, your token must include the `read:packages` and `delete:packages` scopes.
- - To restore packages and package versions, your token must include the `read:packages` and `write:packages` scopes.
-
-If your `package_type` is `npm`, `maven`, `rubygems`, or `nuget`, then your token must also include the `repo` scope since your package inherits permissions from a {% data variables.product.prodname_dotcom %} repository. If your package is in the {% data variables.product.prodname_container_registry %}, then your `package_type` is `container` and your token does not need the `repo` scope to access or manage this `package_type`. `container` packages offer granular permissions separate from a repository. For more information, see "[About permissions for {% data variables.product.prodname_registry %}](/packages/learn-github-packages/about-permissions-for-github-packages#about-scopes-and-permissions-for-package-registries)."
-
-If you want to use the {% data variables.product.prodname_registry %} API to access resources in an organization with SSO enabled, then you must enable SSO for your personal access token. For more information, see "[Authorizing a personal access token for use with SAML single sign-on](/github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}
-
-{% for operation in currentRestOperations %}
- {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
-{% endfor %}
+
diff --git a/translations/zh-CN/content/rest/reference/pages.md b/translations/zh-CN/content/rest/reference/pages.md
index 238ec7512a88..4eb593bcbe8d 100644
--- a/translations/zh-CN/content/rest/reference/pages.md
+++ b/translations/zh-CN/content/rest/reference/pages.md
@@ -12,22 +12,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-{% data variables.product.prodname_pages %} API 可检索关于您的 {% data variables.product.prodname_pages %} 配置以及构建状态的信息。 只有经过验证的所有者才能访问有关网站和构建的信息{% ifversion not ghae %}，即使网站是公开的也一样{% endif %}。 更多信息请参阅“[关于 {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages)”。
-
-在其响应中包含 `status` 键的 {% data variables.product.prodname_pages %} API 端点中，其值可能是以下值之一：
-* `null`：站点尚未构建。
-* `queued`：已请求构建，但尚未开始。
-* `building`：正在构建中。
-* `built`：站点已构建。
-* `errored`：表示构建过程中发生错误。
-
-在返回 GitHub Pages 站点信息的 {% data variables.product.prodname_pages %} API 端点中，JSON 响应包括以下字段：
-* `html_url`：所渲染的 Pages 站点的绝对 URL（包括模式）。 例如，`https://username.github.io`。
-* `source`：包含所渲染 Pages 站点的源分支和目录的对象。 这包括：
- - `branch`：用于发布[站点源文件](/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site)的仓库分支。 例如，_main_ 或 _gh-pages_。
- - `path`：提供站点发布内容的仓库目录。 可能是 `/` 或 `/docs`。
-
-{% comment %}An extra blank line is needed here to make sure the operations below don't continue the list above.{% endcomment %}
-{% for operation in currentRestOperations %}
- {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
-{% endfor %}
+
diff --git a/translations/zh-CN/content/rest/reference/projects.md b/translations/zh-CN/content/rest/reference/projects.md
index 412097c09ff0..fa1f47dc111f 100644
--- a/translations/zh-CN/content/rest/reference/projects.md
+++ b/translations/zh-CN/content/rest/reference/projects.md
@@ -13,26 +13,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-{% for operation in currentRestOperations %}
- {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
-{% endfor %}
-
-## 卡
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'cards' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## 协作者
-
-此 API 允许您与组织的项目进行交互。
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'collaborators' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## 列
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'columns' %}{% include rest_operation %}{% endif %}
-{% endfor %}
+
diff --git a/translations/zh-CN/content/rest/reference/pulls.md b/translations/zh-CN/content/rest/reference/pulls.md
index 4a5e75bf2171..096a48f6b3be 100644
--- a/translations/zh-CN/content/rest/reference/pulls.md
+++ b/translations/zh-CN/content/rest/reference/pulls.md
@@ -13,75 +13,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-拉取请求 API 允许您列出、查看、编辑、创建甚至合并拉取请求。 可以通过[议题评论 API](/rest/reference/issues#comments) 管理对拉取请求的评论。
-
-每个拉取请求都是一个议题，但并非每个议题都是拉取请求。 因此，在[议题 API](/rest/reference/issues) 中为这两项功能提供了“共享”操作，如操作受理人、标签和里程碑。
-
-### 拉取请求的自定义媒体类型
-
-以下是拉取请求支持的媒体类型。
-
- application/vnd.github.VERSION.raw+json
- application/vnd.github.VERSION.text+json
- application/vnd.github.VERSION.html+json
- application/vnd.github.VERSION.full+json
- application/vnd.github.VERSION.diff
- application/vnd.github.VERSION.patch
-
-更多信息请参阅“[自定义媒体类型](/rest/overview/media-types)”。
-
-如果 diff 损坏，请联系 {% data variables.contact.contact_support %}。 在您的消息中包括仓库名称和拉取请求 ID。
-
-### 链接关系
-
-拉取请求具有以下可能的链接关系：
-
-| 名称 | 描述 |
-| ----------------- | ---------------------------------------------------------------------------------------- |
-| `self` | 此拉取请求的 API 位置。 |
-| `html` | 此拉取请求的 HTML 位置。 |
-| `议题` | 此拉取请求的[议题](/rest/reference/issues)的 API 位置。 |
-| `comments` | 此拉取请求的[议题评论](/rest/reference/issues#comments)的 API 位置。 |
-| `review_comments` | 此拉取请求的[审查评论](/rest/reference/pulls#comments)的 API 位置。 |
-| `review_comment` | 用于为此拉取请求仓库中的[审查评论](/rest/reference/pulls#comments)构建 API 位置的 [URL 模板](/rest#hypermedia)。 |
-| `commits` | 此拉取请求的[提交](#list-commits-on-a-pull-request)的 API 位置。 |
-| `状态` | 此拉取请求的[提交状态](/rest/reference/commits#commit-statuses)的 API 位置，即其`头部`分支的状态。 |
-
-{% for operation in currentRestOperations %}
- {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
-{% endfor %}
-
-## 审查
-
-拉取请求审查是拉取请求上的拉取请求审查评论组，与状态和可选的正文注释一起分组。
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'reviews' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## 审查评论
-
-拉取请求审查评论是在拉取请求审查期间对统一差异的一部分所发表的评论。 提交评论和议题评论不同于拉取请求审查评论。 将提交评论直接应用于提交，然后应用议题评论而不引用统一差异的一部分。 更多信息请参阅“[创建提交评论](/rest/reference/commits#create-a-commit-comment)”和“[创建议题评论](/rest/reference/issues#create-an-issue-comment)”。
-
-### 拉取请求审查评论的自定义媒体类型
-
-以下是拉取请求审查评论支持的媒体类型。
-
- application/vnd.github.VERSION.raw+json
- application/vnd.github.VERSION.text+json
- application/vnd.github.VERSION.html+json
- application/vnd.github.VERSION.full+json
-
-更多信息请参阅“[自定义媒体类型](/rest/overview/media-types)”。
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'comments' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## 审查请求
-
-拉取请求作者以及仓库所有者和协作者可以向具有仓库写入权限的任何人请求拉取请求审查。 每个被请求的审查者将收到您要求他们审查拉取请求的通知。
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'review-requests' %}{% include rest_operation %}{% endif %}
-{% endfor %}
+
diff --git a/translations/zh-CN/content/rest/reference/rate-limit.md b/translations/zh-CN/content/rest/reference/rate-limit.md
index f671823d3b8d..a11860eb49e7 100644
--- a/translations/zh-CN/content/rest/reference/rate-limit.md
+++ b/translations/zh-CN/content/rest/reference/rate-limit.md
@@ -14,22 +14,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-REST API 概述文档描述了[速率限制规则](/rest/overview/resources-in-the-rest-api#rate-limiting)。 您可以随时使用下面描述的速率限制 API 来检查您当前的速率限制状态。
-
-### 了解您的速率限制状态
-
-搜索 API 具有[自定义速率限制](/rest/reference/search#rate-limit)，与管理 REST API 其余部分的速率限制不同。 GraphQL API 也有[自定义速率限制]({% ifversion ghec%}/free-pro-team@latest{% endif %}/graphql/overview/resource-limitations#rate-limit)，它与 REST API 中的速率限制不同且分开计算。
-
-出于这些原因，速率限制 API 响应对速率限制进行分类。 在`资源`下，您会看到四个 对象：
-
-* `核心`对象提供 REST API 中所有非搜索相关资源的速率限制状态。
-
-* `搜索`对象提供[搜索 API](/rest/reference/search) 的速率限制状态。
-
-* `graphql`对象提供 [GraphQL API]({% ifversion ghec%}/free-pro-team@latest{% endif %}/graphql) 的速率限制状态。
-
-* `integration_manifest` 对象提供 [GitHub 应用程序清单代码转换](/apps/building-github-apps/creating-github-apps-from-a-manifest/#3-you-exchange-the-temporary-code-to-retrieve-the-app-configuration)端点的速率限制状态。
-
-有关速率限制响应中标头和值的更多信息，请参阅“[REST API 中的资源](/rest/overview/resources-in-the-rest-api#rate-limit-http-headers)”。
-
-{% include rest_operations_at_current_path %}
+
diff --git a/translations/zh-CN/content/rest/reference/reactions.md b/translations/zh-CN/content/rest/reference/reactions.md
index 87ff75793e01..9cf4549090c9 100644
--- a/translations/zh-CN/content/rest/reference/reactions.md
+++ b/translations/zh-CN/content/rest/reference/reactions.md
@@ -13,10 +13,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-### 反应类型
-
-创建反应时，`content` 参数的允许值如下（带有相应的表情符号供参考）：
-
-{% data reusables.repositories.reaction_list %}
-
-{% include rest_operations_at_current_path %}
+
diff --git a/translations/zh-CN/content/rest/reference/releases.md b/translations/zh-CN/content/rest/reference/releases.md
index c3847909f909..6a337a939836 100644
--- a/translations/zh-CN/content/rest/reference/releases.md
+++ b/translations/zh-CN/content/rest/reference/releases.md
@@ -12,18 +12,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-{% note %}
-
-**注：**发布 API 取代了下载 API。 您可以从返回发行版和发行版资产的 API 端点检索下载次数和浏览器下载 URL。
-
-{% endnote %}
-
-{% for operation in currentRestOperations %}
- {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
-{% endfor %}
-
-## Release assets
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'assets' %}{% include rest_operation %}{% endif %}
-{% endfor %}
+
diff --git a/translations/zh-CN/content/rest/reference/repos.md b/translations/zh-CN/content/rest/reference/repos.md
index 4d668cec73bc..c25d17028358 100644
--- a/translations/zh-CN/content/rest/reference/repos.md
+++ b/translations/zh-CN/content/rest/reference/repos.md
@@ -14,63 +14,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-{% for operation in currentRestOperations %}
- {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
-{% endfor %}
-
-{% ifversion fpt or ghec or ghes > 3.2 or ghae-issue-4742 %}
-## 自动链接
-
-为了帮助简化您的工作流程，您可以使用 API 向外部资源（如 JIRA 问题和 Zendesk 事件单）添加自动链接。 更多信息请参阅“[配置自动链接以引用外部资源](/github/administering-a-repository/configuring-autolinks-to-reference-external-resources)”。
-
-{% data variables.product.prodname_github_apps %} 需要有读写权限的仓库管理权限才能使用 Autolinks API。
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'autolinks' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-{% endif %}
-
-
-## 内容
-
-此 API 端点允许您在仓库中创建、修改和删除 Base64 编码的内容。 要请求原始格式或渲染的 HTML（如果支持），请对仓库内容使用自定义媒体类型。
-
-### 仓库内容的自定义媒体类型
-
-[自述文件](/rest/reference/repos#get-a-repository-readme)、[文件](/rest/reference/repos#get-repository-content)和[符号链接](/rest/reference/repos#get-repository-content)支持以下自定义媒体类型：
-
- application/vnd.github.VERSION.raw
- application/vnd.github.VERSION.html
-
-使用 `.raw` 媒体类型检索文件内容。
-
-对于 Markdown 或 AsciiDoc 等标记文件，您可以使用 `.html` 媒体类型检索渲染的 HTML。 使用我们的开源[标记库](https://github.com/github/markup)将标记语言渲染为 HTML。
-
-[所有对象](/rest/reference/repos#get-repository-content)都支持以下自定义媒体类型：
-
- application/vnd.github.VERSION.object
-
-使用 `object` 媒体类型参数以一致的对象格式检索内容，而不考虑内容类型。 例如，响应将是包含对象数组的 `entries` 属性的对象，而不是目录的对象数组。
-
-您可以在[此处](/rest/overview/media-types)阅读有关 API 中媒体类型使用情况的更多信息。
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'contents' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## 复刻
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'forks' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% ifversion fpt or ghae or ghes > 3.2 or ghec %}
-
-## Git LFS
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'lfs' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% endif %}
-
+
diff --git a/translations/zh-CN/content/rest/reference/scim.md b/translations/zh-CN/content/rest/reference/scim.md
index 8a884ec24d65..04db551e47b6 100644
--- a/translations/zh-CN/content/rest/reference/scim.md
+++ b/translations/zh-CN/content/rest/reference/scim.md
@@ -11,46 +11,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-### 组织的 SCIM 预配
-
-SCIM API 由 SCIM 启用的身份提供程序 (IdP) 用来自动预配 {% data variables.product.product_name %} 组织成员身份。 {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API 基于 2.0 版的 [SCIM 标准](http://www.simplecloud.info/)。 IdP 应使用的 {% data variables.product.product_name %} SCIM 端点是：`{% data variables.product.api_url_code %}/scim/v2/organisation/{org}/`。
-
-{% note %}
-
-**注意：**
- - SCIM API 仅适用于 [{% data variables.product.prodname_ghe_cloud %}](/billing/managing-billing-for-your-github-account/about-billing-for-github-accounts) 上启用了 [SAML SSO](/rest/overview/other-authentication-methods#authenticating-for-saml-sso) 的组织。 {% data reusables.scim.enterprise-account-scim %} 有关 SCIM 的更多信息，请参阅“[关于 SCIM](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim)”。
- - SCIM API 不能与 {% data variables.product.prodname_emus %} 一起使用。
-
-{% endnote %}
-
-### 向 SCIM API 验证调用
-
-您必须验证为 {% data variables.product.product_name %} 组织的所有者才可使用其 SCIM API。 API 预期 [OAuth 2.0 Bearer](/developers/apps/authenticating-with-github-apps) 令牌包含在`授权`标头中。 您也可以使用个人访问令牌，但必须先[授权它与您的 SAML SSO 组织一起使用](/github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)。
-
-### SAML 和 SCIM 数据的映射
-
-{% data reusables.scim.nameid-and-username-must-match %}
-
-### 支持的 SCIM 用户属性
-
-| 名称 | 类型 | 描述 |
-| ----------------- | ----- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `userName` | `字符串` | 用户的用户名。 |
-| `name.givenName` | `字符串` | 用户的名字 |
-| `name.familyName` | `字符串` | 用户的姓氏。 |
-| `emails` | `数组` | 用户电子邮件列表。 |
-| `externalId` | `字符串` | 此标识符由 SAML 提供程序生成，并且被 SAML 提供程序用作唯一 ID 来匹配 GitHub 用户。 您可以在 SAML 提供程序上查找用户的 `externalID`，或者使用 [List SCIM 预配的身份](#list-scim-provisioned-identities)端点并过滤其他已知的属性，如用户的 GitHub 用户名或电子邮件地址。 |
-| `id` | `字符串` | GitHub SCIM 端点生成的标识符。 |
-| `active` | `布尔值` | 用于表示身份是处于活动状态 (true) 还是应解除预配 (false)。 |
-
-{% note %}
-
-**注：**SCIM API 的端点 URL 区分大小写。 例如，`Users` 端点中的第一个字母必须大写：
-
-```shell
-GET /scim/v2/organizations/{org}/Users/{scim_user_id}
-```
-
-{% endnote %}
-
-{% include rest_operations_at_current_path %}
+
diff --git a/translations/zh-CN/content/rest/reference/search.md b/translations/zh-CN/content/rest/reference/search.md
index 3d50fc832db7..e7eaa865abbc 100644
--- a/translations/zh-CN/content/rest/reference/search.md
+++ b/translations/zh-CN/content/rest/reference/search.md
@@ -13,150 +13,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-搜索 API 可帮助您搜索要查找的特定条目。 例如，您可以在仓库中找到用户或特定文件。 就像您在 Google 上执行搜索一样。 它旨在帮助您找到要查找的一个或几个结果。 就像在 Google 上搜索一样，有时您希望查看几页搜索结果，以便找到最能满足您需求的条目。 为了满足这一需求， {% data variables.product.product_name %} 搜索 API **为每个搜索提供最多 1,000 个结果**。
-
-您可以使用查询缩小搜索范围。 要了解有关搜索查询语法的更多信息，请查看“[构建搜索查询](/rest/reference/search#constructing-a-search-query)”。
-
-### 排列搜索结果
-
-除非提供另一个排序选项作为查询参数，否则将按照最佳匹配的原则对结果进行降序排列。 多种因素相结合，将最相关的条目顶到结果列表的顶部。
-
-### 速率限制
-
-{% data reusables.enterprise.rate_limit %}
-
-搜索 API 有自定义速率限制。 对于使用[基本身份验证](/rest#authentication)、[OAuth](/rest#authentication) 或[客户端 ID 和密码](/rest#increasing-the-unauthenticated-rate-limit-for-oauth-applications)的请求，您每分钟最多可以提出 30 个请求。 对于未经身份验证的请求，速率限制允许您每分钟最多提出 10 个请求。
-
-请参阅[速率限制文档](/rest/reference/rate-limit)，以详细了解如何确定您的当前速率限制状态。
-
-### 构造搜索查询
-
-搜索 API 中的每个端点都使用[查询参数](https://en.wikipedia.org/wiki/Query_string)对 {% data variables.product.product_name %} 进行搜索。 有关包含端点和查询参数的示例，请参阅搜索 API 中的各个端点。
-
-查询可以包含在 {% data variables.product.product_name %} 上支持的搜索限定符的任意组合中。 搜索查询的格式为：
-
-```
-SEARCH_KEYWORD_1 SEARCH_KEYWORD_N QUALIFIER_1 QUALIFIER_N
-```
-
-例如，如果您要搜索 `defunkt` 拥有的在自述文件中包含单词 `GitHub` 和 `Octocat` 的所有_仓库_，您可以在_搜索仓库_端点中使用以下查询：
-
-```
-GitHub Octocat in:readme user:defunkt
-```
-
-**注意：** 请务必使用语言的首选 HTML 编码器构造查询字符串。 例如：
-```javascript
-// JavaScript
-const queryString = 'q=' + encodeURIComponent('GitHub Octocat in:readme user:defunkt');
-```
-
-有关可用限定符及其格式的完整列表和使用示例，请参阅“[在 GitHub 上搜索](/search-github/searching-on-github)”。 有关如何使用运算符匹配特定数量、日期或排除结果，请参阅“[了解搜索语法](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax/)”。
-
-### 查询长度限制
-
-搜索 API 不支持以下查询：
-- 超过 256 个字符（不包括运算符或限定符）。
-- 超过五个 `AND`、`OR` 或 `NOT` 运算符。
-
-这些搜索查询将返回“验证失败”错误消息。
-
-### 超时和不完整的结果
-
-为了让所有人都能快速使用搜索 API，我们限制任何单个查询能够运行的时长。 对于[超出时间限制](https://developer.github.com/changes/2014-04-07-understanding-search-results-and-potential-timeouts/)的查询，API 将返回在超时之前已找到的匹配项，并且响应的 `incomplete_results` 属性设为 `true`。
-
-达到超时并不意味着搜索结果不完整， 可能已找到更多结果，也可能没有找到。
-
-### 访问错误或缺少搜索结果
-
-您需要成功完成身份验证并且对您搜索查询的仓库具有访问权限，否则，您将看到 `422 Unprocessible Entry` 错误和“验证失败”消息。 例如，如果您的查询中包含 `repo:`、`user:` 或 `org:` 限定符，但它们请求的资源是您登录 {% data variables.product.prodname_dotcom %} 后无权访问的资源，则搜索将失败。
-
-当您的搜索查询请求多个资源时，响应将只包含您有权访问的资源，并且**不会**提供列出未返回资源的错误消息。
-
-例如，如果您的搜索查询要搜索 `octocat/test` 和 `codertocat/test` 仓库，但您只拥有对 `octocat/test` 的访问权限，则您的响应将显示对 `octocat/test` 的搜索结果，而不会显示对 `codertocat/test` 的搜索结果。 此行为类似于 {% data variables.product.prodname_dotcom %} 上的搜索方式。
-
-{% include rest_operations_at_current_path %}
-
-
-### 文本匹配元数据
-
-在 GitHub 上，您可以使用搜索结果中的代码段和高亮显示提供的上下文。 搜索 API 提供额外的元数据，允许您在显示搜索结果时高亮显示匹配搜索词。
-
-
-
-请求可以选择在响应中接收这些文本片段，并且每个片段都附带数字偏移，以标识每个匹配搜索词的确切位置。
-
-要在搜索结果中获取这种元数据，请在 `Accept` 标头中指定 `text-match` 媒体类型。
-
-```shell
-application/vnd.github.v3.text-match+json
-```
-
-提供 `text-match` 媒体类型时，您将在 JSON 有效负载中收到一个额外的键，名为 `text_matches`，它提供有关搜索词在文本中的位置以及包含该搜索词的 `property` 的信息。 在 `text_matches` 数组中，每个对象包含以下属性：
-
-| 名称 | 描述 |
-| ------------- | -------------------------------------------------------------------------------------------------------- |
-| `object_url` | 包含匹配某个搜索词的字符串属性的资源 URL。 |
-| `object_type` | 在给定 `object_url` 中存在的资源类型的名称。 |
-| `属性` | 在 `object_url` 中存在的资源属性的名称。 属性是与某个搜索词相匹配的字符串。 （在从 `object_url` 返回的 JSON 中，`fragment` 的完整内容存在于具有此名称的属性中。） |
-| `分段` | `property` 值的子集。 这是与一个或多个搜索词匹配的文本片段。 |
-| `matches` | 存在于 `fragment` 中的一个或多个搜索词的数组。 索引（即“偏移量”）与片段相关。 （它们与 `property` 的_完整_内容无关。） |
-
-#### 示例
-
-使用 cURL 和上面的[示例议题搜索](#search-issues-and-pull-requests)时，我们的 API 请求如下所示：
-
-``` shell
-curl -H 'Accept: application/vnd.github.v3.text-match+json' \
-'{% data variables.product.api_url_pre %}/search/issues?q=windows+label:bug+language:python+state:open&sort=created&order=asc'
-```
-
-对于每个搜索结果，响应将包含一个 `text_matches` 数组。 在下面的 JSON 中，我们在 `text_matches` 数组中有两个对象。
-
-第一个文本匹配出现在议题的 `body` 属性中。 我们从议题正文中看到了文本片段。 搜索词 (`windows`) 在该片段中出现了两次，我们有每次出现时的索引。
-
-第二个文本匹配出现在其中一个议题注释的 `body` 属性中。 我们有议题注释的 URL。 当然，我们从注释正文中看到了文本片段。 搜索词 (`windows`) 在该片段中出现了一次。
-
-```json
-{
- "text_matches": [
- {
- "object_url": "https://api.github.com/repositories/215335/issues/132",
- "object_type": "Issue",
- "property": "body",
- "fragment": "comprehensive windows font I know of).\n\nIf we can find a commonly distributed windows font that supports them then no problem (we can use html font tags) but otherwise the '(21)' style is probably better.\n",
- "matches": [
- {
- "text": "windows",
- "indices": [
- 14,
- 21
- ]
- },
- {
- "text": "windows",
- "indices": [
- 78,
- 85
- ]
- }
- ]
- },
- {
- "object_url": "https://api.github.com/repositories/215335/issues/comments/25688",
- "object_type": "IssueComment",
- "property": "body",
- "fragment": " right after that are a bit broken IMHO :). I suppose we could have some hack that maxes out at whatever the font does...\n\nI'll check what the state of play is on Windows.\n",
- "matches": [
- {
- "text": "Windows",
- "indices": [
- 163,
- 170
- ]
- }
- ]
- }
- ]
-}
-```
+
diff --git a/translations/zh-CN/content/rest/reference/secret-scanning.md b/translations/zh-CN/content/rest/reference/secret-scanning.md
index 2cb0e7cdf523..689a1352e5b0 100644
--- a/translations/zh-CN/content/rest/reference/secret-scanning.md
+++ b/translations/zh-CN/content/rest/reference/secret-scanning.md
@@ -1,6 +1,6 @@
---
-title: Secret scanning
-intro: 'To retrieve and update the secret alerts from a private repository, you can use Secret Scanning API.'
+title: 秘密扫描
+intro: 要检索和更新来自私有仓库的秘密警报，您可以使用秘密扫描 API。
versions:
fpt: '*'
ghes: '>=3.1'
@@ -9,14 +9,6 @@ versions:
miniTocMaxHeadingLevel: 3
---
-{% data reusables.secret-scanning.api-beta %}
-
-The {% data variables.product.prodname_secret_scanning %} API lets you{% ifversion fpt or ghec or ghes > 3.1 or ghae %}:
-
-- Enable or disable {% data variables.product.prodname_secret_scanning %} for a repository. For more information, see "[Repositories](/rest/reference/repos#update-a-repository)" in the REST API documentation.
-- Retrieve and update {% data variables.product.prodname_secret_scanning %} alerts from a {% ifversion fpt or ghec %}private {% endif %}repository. For futher details, see the sections below.
-{%- else %} retrieve and update {% data variables.product.prodname_secret_scanning %} alerts from a {% ifversion fpt or ghec %}private {% endif %}repository.{% endif %}
-
-For more information about {% data variables.product.prodname_secret_scanning %}, see "[About {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/about-secret-scanning)."
-
-{% include rest_operations_at_current_path %}
+
diff --git a/translations/zh-CN/content/rest/reference/teams.md b/translations/zh-CN/content/rest/reference/teams.md
index 59f72586c43f..2e421abcbd6f 100644
--- a/translations/zh-CN/content/rest/reference/teams.md
+++ b/translations/zh-CN/content/rest/reference/teams.md
@@ -13,84 +13,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-此 API 仅适用于团队[组织](/rest/reference/orgs)中经过身份验证的成员。 OAuth 访问令牌需要 `read:org` [scope](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/)。 {% data variables.product.prodname_dotcom %} 从团队 `name` 生成团队的 `slug`。
-
-{% for operation in currentRestOperations %}
- {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
-{% endfor %}
-
-## 讨论
-
-团队讨论 API 允许您获取、创建、编辑和删除团队页面上的讨论帖子。 您可以使用团队讨论进行不特定于存储库或项目的对话。 团队[组织](/rest/reference/orgs)的任何成员都可以创建和阅读公共讨论帖子。 更多信息请参阅“[关于团队讨论](//organizations/collaborating-with-your-team/about-team-discussions/)”。 要详细了解对讨论帖子的评论，请参阅[团队讨论评论 API](/rest/reference/teams#discussion-comments)。 此 API 仅适用于团队组织中经过身份验证的成员。
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'discussions' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## 讨论评论
-
-团队讨论评论 API 允许您在[团队讨论](/rest/reference/teams#discussions)帖子上获取、 创建、编辑和删除讨论评论。 团队[组织](/rest/reference/orgs)的任何成员都可以创建和阅读公共讨论上的评论。 更多信息请参阅“[关于团队讨论](/organizations/collaborating-with-your-team/about-team-discussions/)”。 此 API 仅适用于团队组织中经过身份验证的成员。
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'discussion-comments' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## 成员
-
-此 API 仅适用于团队组织中经过身份验证的成员。 OAuth 访问令牌需要 `read:org` [scope](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/)。
-
-{% ifversion fpt or ghes or ghec %}
-{% note %}
-
-**注：**当您为具有组织身份提供程序 (IdP) 的团队设置了团队同步时，如果尝试使用 API 更改团队的成员身份，则会看到错误。 如果您有权访问 IdP 中的组成员身份，可以通过身份提供程序管理 GitHub 团队成员身份，该提供程序会自动添加和删除组织的成员。 更多信息请参阅“在身份提供程序与 GitHub 之间同步团队”。
-
-{% endnote %}
-
-{% endif %}
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'members' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% ifversion ghec or ghae %}
-## 外部组
-
-外部组 API 允许您查看可用于组织的外部身份提供程序组，并管理组织中外部组和团队之间的连接。
-
-要使用此 API，经过身份验证的用户必须是团队维护员或与团队关联的组织的所有者。
-
-{% ifversion ghec %}
-{% note %}
-
-**注意：**
-
-- 外部组 API 仅适用于属于使用 {% data variables.product.prodname_emus %} 的企业中的组织。 更多信息请参阅“[关于企业管理用户](/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)”。
-- 如果您的组织使用团队同步，则可以使用团队同步 API。 更多信息请参阅“[团队同步 API](#team-synchronization)”。
-
-{% endnote %}
-{% endif %}
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'external-groups' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% endif %}
-
-{% ifversion fpt or ghes or ghec %}
-## 团队同步
-
-团队同步 API 允许您管理 {% data variables.product.product_name %} 团队与外部身份提供程序 (IdP) 组之间的连接。 要使用此 API，经过身份验证的用户必须是团队维护员或与团队关联的组织的所有者。 用于身份验证的令牌还需要获得授权才能与 IdP (SSO) 提供程序一起使用。 更多信息请参阅“授权个人访问令牌用于 SAML 单点登录组织”。
-
-您可以通过 IdP 通过团队同步管理 GitHub 团队成员。 必须启用团队同步才能使用团队同步 API。 更多信息请参阅“在身份提供程序与 GitHub 之间同步团队”。
-
-{% note %}
-
-**注意：** 团队同步 API 不能与 {% data variables.product.prodname_emus %} 一起使用。 要了解有关管理 {% data variables.product.prodname_emu_org %} 的更多信息，请参阅“[外部组 API](/enterprise-cloud@latest/rest/reference/teams#external-groups)”。
-
-{% endnote %}
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'team-sync' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% endif %}
+
diff --git a/translations/zh-CN/content/rest/reference/users.md b/translations/zh-CN/content/rest/reference/users.md
index c5470ab1bb89..dedfb4471a2c 100644
--- a/translations/zh-CN/content/rest/reference/users.md
+++ b/translations/zh-CN/content/rest/reference/users.md
@@ -13,48 +13,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-用户 API 上的许多资源提供了快捷方式，可用于获取有关当前经过身份验证的用户的信息。 如果请求 URL 不含 `{username}` 参数，则响应将是登录用户的响应（您必须随请求传递[身份验证信息](/rest/overview/resources-in-the-rest-api#authentication)）。{% ifversion fpt or ghes or ghec %} 在通过基本身份验证或作用域为 `user` 的 OAuth 进行身份验证时，将包含其他私有信息，例如用户是否启用双重身份验证。{% endif %}
-
-{% for operation in currentRestOperations %}
- {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
-{% endfor %}
-
-{% ifversion fpt or ghec %}
-## 阻止用户
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'blocking' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% endif %}
-
-{% ifversion fpt or ghes or ghec %}
-## Emails
-
-通过 API 管理电子邮件地址要求您通过基本身份验证进行验证，或者使用端点的正确范围通过 OAuth 进行身份验证。
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'emails' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% endif %}
-
-## 关注者
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'followers' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## Git SSH 密钥
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'keys' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## GPG keys
-
-在 `public_key` 响应字段中返回的数据不是 GPG 格式化的密钥。 当用户上传 GPG 密钥时，将对密钥进行剖析，然后提取并存储加密公钥。 此加密密钥是本页面上的 API 所返回的密钥。 此密钥不适合直接用于 GPG 等程序。
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'gpg-keys' %}{% include rest_operation %}{% endif %}
-{% endfor %}
+
diff --git a/translations/zh-CN/content/rest/reference/webhooks.md b/translations/zh-CN/content/rest/reference/webhooks.md
index d72146d8e543..8d5d0c9326d3 100644
--- a/translations/zh-CN/content/rest/reference/webhooks.md
+++ b/translations/zh-CN/content/rest/reference/webhooks.md
@@ -12,83 +12,6 @@ topics:
miniTocMaxHeadingLevel: 3
---
-仓库 web 挂钩允许您在仓库内发生特定事件时接收 HTTP `POST` 有效负载。 {% data reusables.webhooks.webhooks-rest-api-links %}
-
-如果您要设置一个 web 挂钩来接收来自组织所有仓库的事件，请参阅关于[组织 web 挂钩](/rest/reference/orgs#webhooks)的 API 文档。
-
-除了 REST API 之外， {% data variables.product.prodname_dotcom %} 还可以作为仓库的 [PubSubHubbub](#pubsubhubbub) 枢纽。
-
-{% for operation in currentRestOperations %}
- {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
-{% endfor %}
-
-## 仓库 web 挂钩
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'repos' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## Repository webhook configuration
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'repo-config' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## Repository webhook deliveries
-
-{% for operation in currentRestOperations %}
- {% if operation.subcategory == 'repo-deliveries' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## 接收 web 挂钩
-
-为了让 {% data variables.product.product_name %} 发送 web 挂钩有效负载，您的服务器需要能够从 Internet 访问。 我们还强烈建议使用 SSL，以便我们可以通过 HTTPS 发送加密的有效负载。
-
-### Web 挂钩标头
-
-{% data variables.product.product_name %} 发送时将附带几个 HTTP 标头，以区分事件类型和有效负载标识符。 更多信息请参阅 [web 挂钩标头](/developers/webhooks-and-events/webhook-events-and-payloads#delivery-headers)。
-
-## PubSubHubbub
-
-GitHub 还可以作为所有仓库的 [PubSubHubbabub](https://github.com/pubsubhubbub/PubSubHubbub) 枢纽。 PSHB 是一个简单的发布/订阅协议，允许服务器注册在主题更新时接收更新。 这些更新随 HTTP POST 请求一起发送到回调 URL。 GitHub 仓库推送的主题 URL 采用以下格式：
-
-`https://github.com/{owner}/{repo}/events/{event}`
-
-事件可以是任何可用的 web 挂钩事件。 更多信息请参阅“[web 挂钩事件和有效负载](/developers/webhooks-and-events/webhook-events-and-payloads)”。
-
-### 响应格式
-
-默认格式为[现有接收后挂钩应具有的格式](/post-receive-hooks/)：作为 POST 中的 `payload` 参数发送的 JSON 正文。 您还可以指定接收带有 `Accept` 标头或 `.json` 扩展名的原始 JSON 正文。
-
- Accept: application/json
- https://github.com/{owner}/{repo}/events/push.json
-
-### 回调 URL
-
-回调 URL 可以使用 `http://` 协议。
-
- # Send updates to postbin.org
- http://postbin.org/123
-
-### 订阅
-
-GitHub PubSubHubbub 端点为：`{% data variables.product.api_url_code %}/hub`。 使用 cURL 的成功请求如下所示：
-
-``` shell
-curl -u "user" -i \
- {% data variables.product.api_url_pre %}/hub \
- -F "hub.mode=subscribe" \
- -F "hub.topic=https://github.com/{owner}/{repo}/events/push" \
- -F "hub.callback=http://postbin.org/123"
-```
-
-PubSubHubbub 请求可以多次发送。 如果挂钩已经存在，它将根据请求进行修改。
-
-#### 参数
-
-| 名称 | 类型 | 描述 |
-| -------------- | ----- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `hub.mode` | `字符串` | **必填**。 值为 `subscribe` 或 `unsubscribe`。 |
-| `hub.topic` | `字符串` | **必填**。 要订阅的 GitHub 仓库的 URI。 路径格式必须为 `/{owner}/{repo}/events/{event}`。 |
-| `hub.callback` | `字符串` | 要接收主题更新的 URI。 |
-| `hub.secret` | `字符串` | 用于生成传出正文内容的哈希签名的共享密钥。 您可以通过比较原始请求正文与 {% ifversion fpt or ghes > 2.22 or ghec %}`X-Hub-Signature` 或 `X-Hub-Signature-256` 标头{% elsif ghes < 3.0 %}`X-Hub-Signature` 标头{% elsif ghae %}`X-Hub-Signature-256` 标头{% endif %} 的内容来验证来自 GitHub 的推送。 您可以查看 [PubSubHubbub 文档](https://pubsubhubbub.github.io/PubSubHubbub/pubsubhubbub-core-0.4.html#authednotify)了解详情。 |
+
diff --git a/translations/zh-CN/data/graphql/ghae/graphql_upcoming_changes.public-ghae.yml b/translations/zh-CN/data/graphql/ghae/graphql_upcoming_changes.public-ghae.yml
index b0d87df97a19..c3b7cd551398 100644
--- a/translations/zh-CN/data/graphql/ghae/graphql_upcoming_changes.public-ghae.yml
+++ b/translations/zh-CN/data/graphql/ghae/graphql_upcoming_changes.public-ghae.yml
@@ -112,3 +112,17 @@ upcoming_changes:
date: '2021-10-01T00:00:00+00:00'
criticality: 重大
owner: synthead
+ -
+ location: PullRequest.viewerCanOverrideMergeQueue
+ description: '`viewerCanOverrideMergeQueue` will be removed. Use PullRequest.viewerCanMergeAsAdmin instead.'
+ reason: '`viewer_can_override_merge_queue` will be removed'
+ date: '2022-04-01'
+ criticality: 重大
+ owner: cbeaman
+ -
+ location: Repository.defaultMergeQueue
+ description: '`defaultMergeQueue` will be removed. Use `Repository.mergeQueue` instead.'
+ reason: '`defaultMergeQueue` will be removed.'
+ date: '2022-04-01'
+ criticality: 重大
+ owner: colinshum
diff --git a/translations/zh-CN/data/graphql/ghec/graphql_upcoming_changes.public.yml b/translations/zh-CN/data/graphql/ghec/graphql_upcoming_changes.public.yml
index a53f558d9c4c..73e4d962a512 100644
--- a/translations/zh-CN/data/graphql/ghec/graphql_upcoming_changes.public.yml
+++ b/translations/zh-CN/data/graphql/ghec/graphql_upcoming_changes.public.yml
@@ -126,3 +126,24 @@ upcoming_changes:
date: '2021-10-01T00:00:00+00:00'
criticality: 重大
owner: synthead
+ -
+ location: PullRequest.viewerCanOverrideMergeQueue
+ description: '`viewerCanOverrideMergeQueue` will be removed. Use PullRequest.viewerCanMergeAsAdmin instead.'
+ reason: '`viewer_can_override_merge_queue` will be removed'
+ date: '2022-04-01'
+ criticality: 重大
+ owner: cbeaman
+ -
+ location: Repository.defaultMergeQueue
+ description: '`defaultMergeQueue` will be removed. Use `Repository.mergeQueue` instead.'
+ reason: '`defaultMergeQueue` will be removed.'
+ date: '2022-04-01'
+ criticality: 重大
+ owner: colinshum
+ -
+ location: Query.sponsorables.dependencyEcosystem
+ description: '`dependencyEcosystem` will be removed. Use the ecosystem argument instead.'
+ reason: The type is switching from SecurityAdvisoryEcosystem to DependencyGraphEcosystem.
+ date: '2022-07-01T00:00:00+00:00'
+ criticality: 重大
+ owner: cheshire137
diff --git a/translations/zh-CN/data/graphql/graphql_upcoming_changes.public.yml b/translations/zh-CN/data/graphql/graphql_upcoming_changes.public.yml
index a53f558d9c4c..73e4d962a512 100644
--- a/translations/zh-CN/data/graphql/graphql_upcoming_changes.public.yml
+++ b/translations/zh-CN/data/graphql/graphql_upcoming_changes.public.yml
@@ -126,3 +126,24 @@ upcoming_changes:
date: '2021-10-01T00:00:00+00:00'
criticality: 重大
owner: synthead
+ -
+ location: PullRequest.viewerCanOverrideMergeQueue
+ description: '`viewerCanOverrideMergeQueue` will be removed. Use PullRequest.viewerCanMergeAsAdmin instead.'
+ reason: '`viewer_can_override_merge_queue` will be removed'
+ date: '2022-04-01'
+ criticality: 重大
+ owner: cbeaman
+ -
+ location: Repository.defaultMergeQueue
+ description: '`defaultMergeQueue` will be removed. Use `Repository.mergeQueue` instead.'
+ reason: '`defaultMergeQueue` will be removed.'
+ date: '2022-04-01'
+ criticality: 重大
+ owner: colinshum
+ -
+ location: Query.sponsorables.dependencyEcosystem
+ description: '`dependencyEcosystem` will be removed. Use the ecosystem argument instead.'
+ reason: The type is switching from SecurityAdvisoryEcosystem to DependencyGraphEcosystem.
+ date: '2022-07-01T00:00:00+00:00'
+ criticality: 重大
+ owner: cheshire137
diff --git a/translations/zh-CN/data/reusables/github-actions/actions-activity-types.md b/translations/zh-CN/data/reusables/actions/actions-activity-types.md
similarity index 100%
rename from translations/zh-CN/data/reusables/github-actions/actions-activity-types.md
rename to translations/zh-CN/data/reusables/actions/actions-activity-types.md
diff --git a/translations/zh-CN/data/reusables/github-actions/actions-billing.md b/translations/zh-CN/data/reusables/actions/actions-billing.md
similarity index 100%
rename from translations/zh-CN/data/reusables/github-actions/actions-billing.md
rename to translations/zh-CN/data/reusables/actions/actions-billing.md
diff --git a/translations/zh-CN/data/reusables/github-actions/actions-do-not-trigger-workflows.md b/translations/zh-CN/data/reusables/actions/actions-do-not-trigger-workflows.md
similarity index 100%
rename from translations/zh-CN/data/reusables/github-actions/actions-do-not-trigger-workflows.md
rename to translations/zh-CN/data/reusables/actions/actions-do-not-trigger-workflows.md
diff --git a/translations/zh-CN/data/reusables/github-actions/actions-filters.md b/translations/zh-CN/data/reusables/actions/actions-filters.md
similarity index 100%
rename from translations/zh-CN/data/reusables/github-actions/actions-filters.md
rename to translations/zh-CN/data/reusables/actions/actions-filters.md
diff --git a/translations/zh-CN/data/reusables/github-actions/actions-multiple-types.md b/translations/zh-CN/data/reusables/actions/actions-multiple-types.md
similarity index 100%
rename from translations/zh-CN/data/reusables/github-actions/actions-multiple-types.md
rename to translations/zh-CN/data/reusables/actions/actions-multiple-types.md
diff --git a/translations/zh-CN/data/reusables/actions/actions-on-examples.md b/translations/zh-CN/data/reusables/actions/actions-on-examples.md
new file mode 100644
index 000000000000..80c7fc67d29b
--- /dev/null
+++ b/translations/zh-CN/data/reusables/actions/actions-on-examples.md
@@ -0,0 +1,19 @@
+### Using a single event
+
+{% data reusables.actions.on-single-example %}
+
+### Using multiple events
+
+{% data reusables.actions.on-multiple-example %}
+
+### Using activity types
+
+{% data reusables.actions.actions-activity-types %}
+
+### Using filters
+
+{% data reusables.actions.actions-filters %}
+
+### Using activity types and filters with multiple events
+
+{% data reusables.actions.actions-multiple-types %}
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/github-actions/actions-spending-limit-brief.md b/translations/zh-CN/data/reusables/actions/actions-spending-limit-brief.md
similarity index 100%
rename from translations/zh-CN/data/reusables/github-actions/actions-spending-limit-brief.md
rename to translations/zh-CN/data/reusables/actions/actions-spending-limit-brief.md
diff --git a/translations/zh-CN/data/reusables/github-actions/actions-spending-limit-detailed.md b/translations/zh-CN/data/reusables/actions/actions-spending-limit-detailed.md
similarity index 85%
rename from translations/zh-CN/data/reusables/github-actions/actions-spending-limit-detailed.md
rename to translations/zh-CN/data/reusables/actions/actions-spending-limit-detailed.md
index ac30fe774408..1c81f272f593 100644
--- a/translations/zh-CN/data/reusables/github-actions/actions-spending-limit-detailed.md
+++ b/translations/zh-CN/data/reusables/actions/actions-spending-limit-detailed.md
@@ -1,3 +1,3 @@
-{% data reusables.github-actions.actions-spending-limit-brief %}
+{% data reusables.actions.actions-spending-limit-brief %}
如果您的支出限额无限或大于 0 美元，将对您超出帐户所含金额的任何额外使用分钟数或存储计帐，也称为超限费用。 {% data variables.product.prodname_dotcom %} 向拥有其中运行工作流程的仓库的帐户收取使用费。 您帐户中的任何优惠券都不适用于 {% data variables.product.prodname_actions %} 超额费用。
diff --git a/translations/zh-CN/data/reusables/github-actions/actions-unused-labels.md b/translations/zh-CN/data/reusables/actions/actions-unused-labels.md
similarity index 100%
rename from translations/zh-CN/data/reusables/github-actions/actions-unused-labels.md
rename to translations/zh-CN/data/reusables/actions/actions-unused-labels.md
diff --git a/translations/zh-CN/data/reusables/github-actions/artifact-log-retention-statement.md b/translations/zh-CN/data/reusables/actions/artifact-log-retention-statement.md
similarity index 100%
rename from translations/zh-CN/data/reusables/github-actions/artifact-log-retention-statement.md
rename to translations/zh-CN/data/reusables/actions/artifact-log-retention-statement.md
diff --git a/translations/zh-CN/data/reusables/github-actions/branch-paths-filter.md b/translations/zh-CN/data/reusables/actions/branch-paths-filter.md
similarity index 100%
rename from translations/zh-CN/data/reusables/github-actions/branch-paths-filter.md
rename to translations/zh-CN/data/reusables/actions/branch-paths-filter.md
diff --git a/translations/zh-CN/data/reusables/github-actions/branch-requirement.md b/translations/zh-CN/data/reusables/actions/branch-requirement.md
similarity index 100%
rename from translations/zh-CN/data/reusables/github-actions/branch-requirement.md
rename to translations/zh-CN/data/reusables/actions/branch-requirement.md
diff --git a/translations/zh-CN/data/reusables/github-actions/change-retention-period-for-artifacts-logs.md b/translations/zh-CN/data/reusables/actions/change-retention-period-for-artifacts-logs.md
similarity index 100%
rename from translations/zh-CN/data/reusables/github-actions/change-retention-period-for-artifacts-logs.md
rename to translations/zh-CN/data/reusables/actions/change-retention-period-for-artifacts-logs.md
diff --git a/translations/zh-CN/data/reusables/github-actions/contacting-support.md b/translations/zh-CN/data/reusables/actions/contacting-support.md
similarity index 100%
rename from translations/zh-CN/data/reusables/github-actions/contacting-support.md
rename to translations/zh-CN/data/reusables/actions/contacting-support.md
diff --git a/translations/zh-CN/data/reusables/github-actions/container-jobs-intro.md b/translations/zh-CN/data/reusables/actions/container-jobs-intro.md
similarity index 100%
rename from translations/zh-CN/data/reusables/github-actions/container-jobs-intro.md
rename to translations/zh-CN/data/reusables/actions/container-jobs-intro.md
diff --git a/translations/zh-CN/data/reusables/github-actions/context-injection-warning.md b/translations/zh-CN/data/reusables/actions/context-injection-warning.md
similarity index 100%
rename from translations/zh-CN/data/reusables/github-actions/context-injection-warning.md
rename to translations/zh-CN/data/reusables/actions/context-injection-warning.md
diff --git a/translations/zh-CN/data/reusables/github-actions/copy-workflow-file.md b/translations/zh-CN/data/reusables/actions/copy-workflow-file.md
similarity index 100%
rename from translations/zh-CN/data/reusables/github-actions/copy-workflow-file.md
rename to translations/zh-CN/data/reusables/actions/copy-workflow-file.md
diff --git a/translations/zh-CN/data/reusables/github-actions/defaults-override.md b/translations/zh-CN/data/reusables/actions/defaults-override.md
similarity index 100%
rename from translations/zh-CN/data/reusables/github-actions/defaults-override.md
rename to translations/zh-CN/data/reusables/actions/defaults-override.md
diff --git a/translations/zh-CN/data/reusables/github-actions/disabled-actions-description.md b/translations/zh-CN/data/reusables/actions/disabled-actions-description.md
similarity index 100%
rename from translations/zh-CN/data/reusables/github-actions/disabled-actions-description.md
rename to translations/zh-CN/data/reusables/actions/disabled-actions-description.md
diff --git a/translations/zh-CN/data/reusables/github-actions/disabling-github-actions.md b/translations/zh-CN/data/reusables/actions/disabling-github-actions.md
similarity index 100%
rename from translations/zh-CN/data/reusables/github-actions/disabling-github-actions.md
rename to translations/zh-CN/data/reusables/actions/disabling-github-actions.md
diff --git a/translations/zh-CN/data/reusables/github-actions/docker-container-os-support.md b/translations/zh-CN/data/reusables/actions/docker-container-os-support.md
similarity index 100%
rename from translations/zh-CN/data/reusables/github-actions/docker-container-os-support.md
rename to translations/zh-CN/data/reusables/actions/docker-container-os-support.md
diff --git a/translations/zh-CN/data/reusables/github-actions/dockerfile-guidelines.md b/translations/zh-CN/data/reusables/actions/dockerfile-guidelines.md
similarity index 100%
rename from translations/zh-CN/data/reusables/github-actions/dockerfile-guidelines.md
rename to translations/zh-CN/data/reusables/actions/dockerfile-guidelines.md
diff --git a/translations/zh-CN/data/reusables/github-actions/enabled-actions-description.md b/translations/zh-CN/data/reusables/actions/enabled-actions-description.md
similarity index 100%
rename from translations/zh-CN/data/reusables/github-actions/enabled-actions-description.md
rename to translations/zh-CN/data/reusables/actions/enabled-actions-description.md
diff --git a/translations/zh-CN/data/reusables/github-actions/enabled-local-github-actions.md b/translations/zh-CN/data/reusables/actions/enabled-local-github-actions.md
similarity index 100%
rename from translations/zh-CN/data/reusables/github-actions/enabled-local-github-actions.md
rename to translations/zh-CN/data/reusables/actions/enabled-local-github-actions.md
diff --git a/translations/zh-CN/data/reusables/github-actions/enterprise-billing-details.md b/translations/zh-CN/data/reusables/actions/enterprise-billing-details.md
similarity index 100%
rename from translations/zh-CN/data/reusables/github-actions/enterprise-billing-details.md
rename to translations/zh-CN/data/reusables/actions/enterprise-billing-details.md
diff --git a/translations/zh-CN/data/reusables/github-actions/example-github-runner.md b/translations/zh-CN/data/reusables/actions/example-github-runner.md
similarity index 100%
rename from translations/zh-CN/data/reusables/github-actions/example-github-runner.md
rename to translations/zh-CN/data/reusables/actions/example-github-runner.md
diff --git a/translations/zh-CN/data/reusables/github-actions/expression-syntax-if.md b/translations/zh-CN/data/reusables/actions/expression-syntax-if.md
similarity index 100%
rename from translations/zh-CN/data/reusables/github-actions/expression-syntax-if.md
rename to translations/zh-CN/data/reusables/actions/expression-syntax-if.md
diff --git a/translations/zh-CN/data/reusables/github-actions/forked-write-permission.md b/translations/zh-CN/data/reusables/actions/forked-write-permission.md
similarity index 100%
rename from translations/zh-CN/data/reusables/github-actions/forked-write-permission.md
rename to translations/zh-CN/data/reusables/actions/forked-write-permission.md
diff --git a/translations/zh-CN/data/reusables/actions/ghes-actions-not-enabled-by-default.md b/translations/zh-CN/data/reusables/actions/ghes-actions-not-enabled-by-default.md
new file mode 100644
index 000000000000..04afb9489221
--- /dev/null
+++ b/translations/zh-CN/data/reusables/actions/ghes-actions-not-enabled-by-default.md
@@ -0,0 +1 @@
+{% data variables.product.prodname_actions %} is not enabled for {% data variables.product.prodname_ghe_server %} by default.
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/github-actions/github-context-warning.md b/translations/zh-CN/data/reusables/actions/github-context-warning.md
similarity index 100%
rename from translations/zh-CN/data/reusables/github-actions/github-context-warning.md
rename to translations/zh-CN/data/reusables/actions/github-context-warning.md
diff --git a/translations/zh-CN/data/reusables/github-actions/github-hosted-runners-check-concurrency.md b/translations/zh-CN/data/reusables/actions/github-hosted-runners-check-concurrency.md
similarity index 100%
rename from translations/zh-CN/data/reusables/github-actions/github-hosted-runners-check-concurrency.md
rename to translations/zh-CN/data/reusables/actions/github-hosted-runners-check-concurrency.md
diff --git a/translations/zh-CN/data/reusables/github-actions/github-hosted-runners-navigate-to-repo-org-enterprise.md b/translations/zh-CN/data/reusables/actions/github-hosted-runners-navigate-to-repo-org-enterprise.md
similarity index 100%
rename from translations/zh-CN/data/reusables/github-actions/github-hosted-runners-navigate-to-repo-org-enterprise.md
rename to translations/zh-CN/data/reusables/actions/github-hosted-runners-navigate-to-repo-org-enterprise.md
diff --git a/translations/zh-CN/data/reusables/github-actions/github-hosted-runners-table-entry.md b/translations/zh-CN/data/reusables/actions/github-hosted-runners-table-entry.md
similarity index 100%
rename from translations/zh-CN/data/reusables/github-actions/github-hosted-runners-table-entry.md
rename to translations/zh-CN/data/reusables/actions/github-hosted-runners-table-entry.md
diff --git a/translations/es-ES/data/reusables/github-actions/github-token-available-permissions.md b/translations/zh-CN/data/reusables/actions/github-token-available-permissions.md
similarity index 57%
rename from translations/es-ES/data/reusables/github-actions/github-token-available-permissions.md
rename to translations/zh-CN/data/reusables/actions/github-token-available-permissions.md
index 5337f345e207..5af40196917d 100644
--- a/translations/es-ES/data/reusables/github-actions/github-token-available-permissions.md
+++ b/translations/zh-CN/data/reusables/actions/github-token-available-permissions.md
@@ -1,4 +1,4 @@
-Alcances y valores de acceso disponibles:
+Available scopes and access values:
```yaml
permissions:
@@ -17,15 +17,15 @@ permissions:
statuses: read|write|none
```
-Si especificas el acceso para cualquiera de estos alcances, todos aquellos que no se especifiquen se configuran como `none`.
+If you specify the access for any of these scopes, all of those that are not specified are set to `none`.
-Puedes utilizar la siguiente sintaxis para definir el acceso de lectura o escritura para todos los alcances disponibles:
+You can use the following syntax to define read or write access for all of the available scopes:
```yaml
permissions: read-all|write-all
```
-Puedes utilizar la siguiente sintaxis para inhabilitar los permisos para todos los alcances disponibles:
+You can use the following syntax to disable permissions for all of the available scopes:
```yaml
permissions: {}
diff --git a/translations/zh-CN/data/reusables/github-actions/github-token-permissions.md b/translations/zh-CN/data/reusables/actions/github-token-permissions.md
similarity index 100%
rename from translations/zh-CN/data/reusables/github-actions/github-token-permissions.md
rename to translations/zh-CN/data/reusables/actions/github-token-permissions.md
diff --git a/translations/zh-CN/data/reusables/github-actions/github_token-input-example.md b/translations/zh-CN/data/reusables/actions/github_token-input-example.md
similarity index 100%
rename from translations/zh-CN/data/reusables/github-actions/github_token-input-example.md
rename to translations/zh-CN/data/reusables/actions/github_token-input-example.md
diff --git a/translations/zh-CN/data/reusables/github-actions/gradle-workflow-steps.md b/translations/zh-CN/data/reusables/actions/gradle-workflow-steps.md
similarity index 100%
rename from translations/zh-CN/data/reusables/github-actions/gradle-workflow-steps.md
rename to translations/zh-CN/data/reusables/actions/gradle-workflow-steps.md
diff --git a/translations/zh-CN/data/reusables/github-actions/hosted-runner-configure-runner-group-access.md b/translations/zh-CN/data/reusables/actions/hosted-runner-configure-runner-group-access.md
similarity index 100%
rename from translations/zh-CN/data/reusables/github-actions/hosted-runner-configure-runner-group-access.md
rename to translations/zh-CN/data/reusables/actions/hosted-runner-configure-runner-group-access.md
diff --git a/translations/zh-CN/data/reusables/github-actions/hosted-runner-labels-view-assigned-labels.md b/translations/zh-CN/data/reusables/actions/hosted-runner-labels-view-assigned-labels.md
similarity index 100%
rename from translations/zh-CN/data/reusables/github-actions/hosted-runner-labels-view-assigned-labels.md
rename to translations/zh-CN/data/reusables/actions/hosted-runner-labels-view-assigned-labels.md
diff --git a/translations/zh-CN/data/reusables/github-actions/hosted-runner-list-group.md b/translations/zh-CN/data/reusables/actions/hosted-runner-list-group.md
similarity index 100%
rename from translations/zh-CN/data/reusables/github-actions/hosted-runner-list-group.md
rename to translations/zh-CN/data/reusables/actions/hosted-runner-list-group.md
diff --git a/translations/zh-CN/data/reusables/github-actions/hosted-runner-list.md b/translations/zh-CN/data/reusables/actions/hosted-runner-list.md
similarity index 100%
rename from translations/zh-CN/data/reusables/github-actions/hosted-runner-list.md
rename to translations/zh-CN/data/reusables/actions/hosted-runner-list.md
diff --git a/translations/zh-CN/data/reusables/github-actions/invalid-workflow-files.md b/translations/zh-CN/data/reusables/actions/invalid-workflow-files.md
similarity index 100%
rename from translations/zh-CN/data/reusables/github-actions/invalid-workflow-files.md
rename to translations/zh-CN/data/reusables/actions/invalid-workflow-files.md
diff --git a/translations/zh-CN/data/reusables/actions/ip-allow-list-self-hosted-runners.md b/translations/zh-CN/data/reusables/actions/ip-allow-list-self-hosted-runners.md
new file mode 100644
index 000000000000..58faf9fd6e22
--- /dev/null
+++ b/translations/zh-CN/data/reusables/actions/ip-allow-list-self-hosted-runners.md
@@ -0,0 +1,11 @@
+{% ifversion ghae %}
+要允许自托管运行器与 {% data variables.product.prodname_dotcom %} 通信，请将自托管运行器的 IP 地址或 IP 地址范围添加到 IP 允许列表。 更多信息请参阅“[添加允许的 IP 地址](#adding-an-allowed-ip-address)”。
+{% else %}
+{% warning %}
+
+**警告**：如果您使用 IP 允许列表，并且还希望使用 {% data variables.product.prodname_actions %}，则必须使用自托管运行器。 更多信息请参阅“[托管您自己的运行器](/actions/automating-your-workflow-with-github-actions/about-self-hosted-runners)”。
+
+{% endwarning %}
+
+要允许自托管运行器与 {% data variables.product.prodname_dotcom %} 通信，请将自托管运行器的 IP 地址或 IP 地址范围添加到 IP 允许列表。 更多信息请参阅“[添加允许的 IP 地址](#adding-an-allowed-ip-address)”。
+{% endif %}
diff --git a/translations/zh-CN/data/reusables/github-actions/java-jvm-architecture.md b/translations/zh-CN/data/reusables/actions/java-jvm-architecture.md
similarity index 100%
rename from translations/zh-CN/data/reusables/github-actions/java-jvm-architecture.md
rename to translations/zh-CN/data/reusables/actions/java-jvm-architecture.md
diff --git a/translations/zh-CN/data/reusables/actions/jobs/section-assigning-permissions-to-jobs-specific.md b/translations/zh-CN/data/reusables/actions/jobs/section-assigning-permissions-to-jobs-specific.md
index c7a45e7ba977..52d734bfd411 100644
--- a/translations/zh-CN/data/reusables/actions/jobs/section-assigning-permissions-to-jobs-specific.md
+++ b/translations/zh-CN/data/reusables/actions/jobs/section-assigning-permissions-to-jobs-specific.md
@@ -2,8 +2,8 @@ For a specific job, you can use `jobs..permissions` to modify the defaul
通过在工作定义中指定权限，您可以根据需要为每个作业的 `GITHUB_TOKEN` 配置一组不同的权限。 或者，您也可以为工作流程中的所有作业指定权限。 有关在工作流程级别定义权限的信息，请参阅 [`permissions`](/actions/using-workflows/workflow-syntax-for-github-actions#permissions)。
-{% data reusables.github-actions.github-token-available-permissions %}
-{% data reusables.github-actions.forked-write-permission %}
+{% data reusables.actions.github-token-available-permissions %}
+{% data reusables.actions.forked-write-permission %}
#### Example: Setting permissions for a specific job
diff --git a/translations/zh-CN/data/reusables/actions/jobs/section-assigning-permissions-to-jobs.md b/translations/zh-CN/data/reusables/actions/jobs/section-assigning-permissions-to-jobs.md
index a1cc41658554..885d27b526ef 100644
--- a/translations/zh-CN/data/reusables/actions/jobs/section-assigning-permissions-to-jobs.md
+++ b/translations/zh-CN/data/reusables/actions/jobs/section-assigning-permissions-to-jobs.md
@@ -2,8 +2,8 @@ You can use `permissions` to modify the default permissions granted to the `GITH
您可以使用 `permissions` 作为顶级密钥，以应用于工作流程中的所有作业，或特定的作业。 当您在特定作业中添加 `permissions` 键时，该作业中的所有操作和运行命令使用 `GITHUB_TOKEN` 获取您指定的访问权限。 更多信息请参阅 [`jobs..permissions`](/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idpermissions)。
-{% data reusables.github-actions.github-token-available-permissions %}
-{% data reusables.github-actions.forked-write-permission %}
+{% data reusables.actions.github-token-available-permissions %}
+{% data reusables.actions.forked-write-permission %}
### Example: Assigning permissions to GITHUB_TOKEN
diff --git a/translations/zh-CN/data/reusables/actions/jobs/section-choosing-the-runner-for-a-job.md b/translations/zh-CN/data/reusables/actions/jobs/section-choosing-the-runner-for-a-job.md
index 70ca12a81e2c..769d478b9657 100644
--- a/translations/zh-CN/data/reusables/actions/jobs/section-choosing-the-runner-for-a-job.md
+++ b/translations/zh-CN/data/reusables/actions/jobs/section-choosing-the-runner-for-a-job.md
@@ -10,7 +10,7 @@ Use `jobs..runs-on` to define the type of machine to run the job on. {%
可用的 {% data variables.product.prodname_dotcom %} 托管的运行器类型包括：
-{% data reusables.github-actions.supported-github-runners %}
+{% data reusables.actions.supported-github-runners %}
#### Example: Specifying an operating system
@@ -27,7 +27,7 @@ runs-on: ubuntu-latest
{% data reusables.actions.ae-self-hosted-runners-notice %}
-{% data reusables.github-actions.self-hosted-runner-labels-runs-on %}
+{% data reusables.actions.self-hosted-runner-labels-runs-on %}
#### Example: Using labels for runner selection
diff --git a/translations/zh-CN/data/reusables/actions/jobs/section-using-a-build-matrix-for-your-jobs-matrix.md b/translations/zh-CN/data/reusables/actions/jobs/section-using-a-build-matrix-for-your-jobs-matrix.md
index 69849f1483a9..4b8ab65aed18 100644
--- a/translations/zh-CN/data/reusables/actions/jobs/section-using-a-build-matrix-for-your-jobs-matrix.md
+++ b/translations/zh-CN/data/reusables/actions/jobs/section-using-a-build-matrix-for-your-jobs-matrix.md
@@ -1,7 +1,7 @@
Use `jobs..strategy.matrix` to define a matrix of different job configurations. 矩阵允许您通过在单个作业定义中执行变量替换来创建多个作业。 例如，可以使用矩阵为多个受支持的编程语言、操作系统或工具版本创建作业。 矩阵重新使用作业的配置，并为您配置的每个矩阵创建作业。
-{% data reusables.github-actions.usage-matrix-limits %}
+{% data reusables.actions.usage-matrix-limits %}
您在 `matrix` 中定义的每个选项都有键和值。 定义的键将成为 `matrix` 上下文中的属性，您可以在工作流程文件的其他区域中引用该属性。 例如，如果定义包含操作系统数组的键 `os`，您可以使用 `matrix.os` 属性作为 `runs-on` 关键字的值，为每个操作系统创建一个作业。 更多信息请参阅“[上下文](/actions/learn-github-actions/contexts)”。
@@ -123,4 +123,4 @@ strategy:
您可以使用 `include` 键为每个测试组合添加自定义环境变量。 然后，您可以在后面的步骤中引用自定义环境变量。
-{% data reusables.github-actions.matrix-variable-example %}
+{% data reusables.actions.matrix-variable-example %}
diff --git a/translations/zh-CN/data/reusables/actions/jobs/section-using-conditions-to-control-job-execution.md b/translations/zh-CN/data/reusables/actions/jobs/section-using-conditions-to-control-job-execution.md
index aafdced0e3f2..93f0f3e33817 100644
--- a/translations/zh-CN/data/reusables/actions/jobs/section-using-conditions-to-control-job-execution.md
+++ b/translations/zh-CN/data/reusables/actions/jobs/section-using-conditions-to-control-job-execution.md
@@ -1,6 +1,6 @@
You can use the `jobs..if` conditional to prevent a job from running unless a condition is met. 您可以使用任何支持上下文和表达式来创建条件。
-{% data reusables.github-actions.expression-syntax-if %} For more information, see "[Expressions](/actions/learn-github-actions/expressions)."
+{% data reusables.actions.expression-syntax-if %} For more information, see "[Expressions](/actions/learn-github-actions/expressions)."
### Example: Only run job for specific repository
diff --git a/translations/zh-CN/data/reusables/actions/jobs/setting-default-values-for-jobs-defaults-job-run.md b/translations/zh-CN/data/reusables/actions/jobs/setting-default-values-for-jobs-defaults-job-run.md
index f2eaf3db50c7..8ebb1e30d497 100644
--- a/translations/zh-CN/data/reusables/actions/jobs/setting-default-values-for-jobs-defaults-job-run.md
+++ b/translations/zh-CN/data/reusables/actions/jobs/setting-default-values-for-jobs-defaults-job-run.md
@@ -2,7 +2,7 @@ Use `jobs..defaults.run` to provide default `shell` and `working-directo
您可以为作业中的所有 [`run`](/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idstepsrun) 步骤提供默认的 `shell` 和 `working-directory` 选项。 您也可以为整个工作流程设置 `run` 的默认设置。 更多信息请参阅 [`jobs.defaults.run`](/actions/using-workflows/workflow-syntax-for-github-actions#defaultsrun)。 您不能在此关键词中使用上下文或表达式。
-{% data reusables.github-actions.defaults-override %}
+{% data reusables.actions.defaults-override %}
#### Example: Setting default `run` step options for a job
diff --git a/translations/zh-CN/data/reusables/actions/jobs/setting-default-values-for-jobs-defaults-job.md b/translations/zh-CN/data/reusables/actions/jobs/setting-default-values-for-jobs-defaults-job.md
index a9e3e14df949..74dd3403715e 100644
--- a/translations/zh-CN/data/reusables/actions/jobs/setting-default-values-for-jobs-defaults-job.md
+++ b/translations/zh-CN/data/reusables/actions/jobs/setting-default-values-for-jobs-defaults-job.md
@@ -1,3 +1,3 @@
Use `jobs..defaults` to create a `map` of default settings that will apply to all steps in the job. 您也可以设置整个工作流程的默认设置。 For more information, see [`defaults`](/actions/using-workflows/workflow-syntax-for-github-actions#defaults).
-{% data reusables.github-actions.defaults-override %}
\ No newline at end of file
+{% data reusables.actions.defaults-override %}
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/actions/jobs/setting-default-values-for-jobs-defaults-run.md b/translations/zh-CN/data/reusables/actions/jobs/setting-default-values-for-jobs-defaults-run.md
index 75559be69ff9..8405aa76ae17 100644
--- a/translations/zh-CN/data/reusables/actions/jobs/setting-default-values-for-jobs-defaults-run.md
+++ b/translations/zh-CN/data/reusables/actions/jobs/setting-default-values-for-jobs-defaults-run.md
@@ -1,6 +1,6 @@
You can use `defaults.run` to provide default `shell` and `working-directory` options for all [`run`](/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idstepsrun) steps in a workflow. 您也可以设置只可用于作业的 `run` 默认设置。 更多信息请参阅 [`jobs..defaults.run`](/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_iddefaultsrun)。 您不能在此关键词中使用上下文或表达式。
-{% data reusables.github-actions.defaults-override %}
+{% data reusables.actions.defaults-override %}
#### Example: Set the default shell and working directory
diff --git a/translations/zh-CN/data/reusables/actions/jobs/setting-default-values-for-jobs-defaults.md b/translations/zh-CN/data/reusables/actions/jobs/setting-default-values-for-jobs-defaults.md
index 471109737c06..9b9a00119b19 100644
--- a/translations/zh-CN/data/reusables/actions/jobs/setting-default-values-for-jobs-defaults.md
+++ b/translations/zh-CN/data/reusables/actions/jobs/setting-default-values-for-jobs-defaults.md
@@ -1,3 +1,3 @@
Use `defaults` to create a `map` of default settings that will apply to all jobs in the workflow. 您也可以设置只可用于作业的默认设置。 更多信息请参阅 [`jobs..defaults`](/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_iddefaults)。
-{% data reusables.github-actions.defaults-override %}
\ No newline at end of file
+{% data reusables.actions.defaults-override %}
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/github-actions/macos-runner-preview.md b/translations/zh-CN/data/reusables/actions/macos-runner-preview.md
similarity index 100%
rename from translations/zh-CN/data/reusables/github-actions/macos-runner-preview.md
rename to translations/zh-CN/data/reusables/actions/macos-runner-preview.md
diff --git a/translations/zh-CN/data/reusables/github-actions/matrix-variable-example.md b/translations/zh-CN/data/reusables/actions/matrix-variable-example.md
similarity index 100%
rename from translations/zh-CN/data/reusables/github-actions/matrix-variable-example.md
rename to translations/zh-CN/data/reusables/actions/matrix-variable-example.md
diff --git a/translations/zh-CN/data/reusables/github-actions/name-environment.md b/translations/zh-CN/data/reusables/actions/name-environment.md
similarity index 100%
rename from translations/zh-CN/data/reusables/github-actions/name-environment.md
rename to translations/zh-CN/data/reusables/actions/name-environment.md
diff --git a/translations/zh-CN/data/reusables/github-actions/new-environment.md b/translations/zh-CN/data/reusables/actions/new-environment.md
similarity index 100%
rename from translations/zh-CN/data/reusables/github-actions/new-environment.md
rename to translations/zh-CN/data/reusables/actions/new-environment.md
diff --git a/translations/zh-CN/data/reusables/github-actions/on-multiple-example.md b/translations/zh-CN/data/reusables/actions/on-multiple-example.md
similarity index 100%
rename from translations/zh-CN/data/reusables/github-actions/on-multiple-example.md
rename to translations/zh-CN/data/reusables/actions/on-multiple-example.md
diff --git a/translations/zh-CN/data/reusables/github-actions/on-single-example.md b/translations/zh-CN/data/reusables/actions/on-single-example.md
similarity index 100%
rename from translations/zh-CN/data/reusables/github-actions/on-single-example.md
rename to translations/zh-CN/data/reusables/actions/on-single-example.md
diff --git a/translations/zh-CN/data/reusables/github-actions/permissions-statement-environment.md b/translations/zh-CN/data/reusables/actions/permissions-statement-environment.md
similarity index 100%
rename from translations/zh-CN/data/reusables/github-actions/permissions-statement-environment.md
rename to translations/zh-CN/data/reusables/actions/permissions-statement-environment.md
diff --git a/translations/zh-CN/data/reusables/github-actions/permissions-statement-secrets-api.md b/translations/zh-CN/data/reusables/actions/permissions-statement-secrets-api.md
similarity index 100%
rename from translations/zh-CN/data/reusables/github-actions/permissions-statement-secrets-api.md
rename to translations/zh-CN/data/reusables/actions/permissions-statement-secrets-api.md
diff --git a/translations/zh-CN/data/reusables/github-actions/permissions-statement-secrets-environment.md b/translations/zh-CN/data/reusables/actions/permissions-statement-secrets-environment.md
similarity index 100%
rename from translations/zh-CN/data/reusables/github-actions/permissions-statement-secrets-environment.md
rename to translations/zh-CN/data/reusables/actions/permissions-statement-secrets-environment.md
diff --git a/translations/zh-CN/data/reusables/github-actions/permissions-statement-secrets-organization.md b/translations/zh-CN/data/reusables/actions/permissions-statement-secrets-organization.md
similarity index 100%
rename from translations/zh-CN/data/reusables/github-actions/permissions-statement-secrets-organization.md
rename to translations/zh-CN/data/reusables/actions/permissions-statement-secrets-organization.md
diff --git a/translations/zh-CN/data/reusables/github-actions/permissions-statement-secrets-repository.md b/translations/zh-CN/data/reusables/actions/permissions-statement-secrets-repository.md
similarity index 100%
rename from translations/zh-CN/data/reusables/github-actions/permissions-statement-secrets-repository.md
rename to translations/zh-CN/data/reusables/actions/permissions-statement-secrets-repository.md
diff --git a/translations/zh-CN/data/reusables/github-actions/postgres-environment-variables.md b/translations/zh-CN/data/reusables/actions/postgres-environment-variables.md
similarity index 100%
rename from translations/zh-CN/data/reusables/github-actions/postgres-environment-variables.md
rename to translations/zh-CN/data/reusables/actions/postgres-environment-variables.md
diff --git a/translations/zh-CN/data/reusables/github-actions/postgres-label-description.md b/translations/zh-CN/data/reusables/actions/postgres-label-description.md
similarity index 100%
rename from translations/zh-CN/data/reusables/github-actions/postgres-label-description.md
rename to translations/zh-CN/data/reusables/actions/postgres-label-description.md
diff --git a/translations/zh-CN/data/reusables/github-actions/private-repository-forks-configure.md b/translations/zh-CN/data/reusables/actions/private-repository-forks-configure.md
similarity index 100%
rename from translations/zh-CN/data/reusables/github-actions/private-repository-forks-configure.md
rename to translations/zh-CN/data/reusables/actions/private-repository-forks-configure.md
diff --git a/translations/zh-CN/data/reusables/github-actions/private-repository-forks-options.md b/translations/zh-CN/data/reusables/actions/private-repository-forks-options.md
similarity index 100%
rename from translations/zh-CN/data/reusables/github-actions/private-repository-forks-options.md
rename to translations/zh-CN/data/reusables/actions/private-repository-forks-options.md
diff --git a/translations/zh-CN/data/reusables/github-actions/private-repository-forks-overview.md b/translations/zh-CN/data/reusables/actions/private-repository-forks-overview.md
similarity index 100%
rename from translations/zh-CN/data/reusables/github-actions/private-repository-forks-overview.md
rename to translations/zh-CN/data/reusables/actions/private-repository-forks-overview.md
diff --git a/translations/zh-CN/data/reusables/github-actions/publish-to-maven-workflow-step.md b/translations/zh-CN/data/reusables/actions/publish-to-maven-workflow-step.md
similarity index 100%
rename from translations/zh-CN/data/reusables/github-actions/publish-to-maven-workflow-step.md
rename to translations/zh-CN/data/reusables/actions/publish-to-maven-workflow-step.md
diff --git a/translations/zh-CN/data/reusables/github-actions/publish-to-packages-workflow-step.md b/translations/zh-CN/data/reusables/actions/publish-to-packages-workflow-step.md
similarity index 100%
rename from translations/zh-CN/data/reusables/github-actions/publish-to-packages-workflow-step.md
rename to translations/zh-CN/data/reusables/actions/publish-to-packages-workflow-step.md
diff --git a/translations/zh-CN/data/reusables/github-actions/publishing-java-packages-intro.md b/translations/zh-CN/data/reusables/actions/publishing-java-packages-intro.md
similarity index 100%
rename from translations/zh-CN/data/reusables/github-actions/publishing-java-packages-intro.md
rename to translations/zh-CN/data/reusables/actions/publishing-java-packages-intro.md
diff --git a/translations/zh-CN/data/reusables/github-actions/pure-javascript.md b/translations/zh-CN/data/reusables/actions/pure-javascript.md
similarity index 100%
rename from translations/zh-CN/data/reusables/github-actions/pure-javascript.md
rename to translations/zh-CN/data/reusables/actions/pure-javascript.md
diff --git a/translations/zh-CN/data/reusables/github-actions/redis-environment-variables.md b/translations/zh-CN/data/reusables/actions/redis-environment-variables.md
similarity index 100%
rename from translations/zh-CN/data/reusables/github-actions/redis-environment-variables.md
rename to translations/zh-CN/data/reusables/actions/redis-environment-variables.md
diff --git a/translations/zh-CN/data/reusables/github-actions/redis-label-description.md b/translations/zh-CN/data/reusables/actions/redis-label-description.md
similarity index 100%
rename from translations/zh-CN/data/reusables/github-actions/redis-label-description.md
rename to translations/zh-CN/data/reusables/actions/redis-label-description.md
diff --git a/translations/zh-CN/data/reusables/github-actions/release-trigger-workflow.md b/translations/zh-CN/data/reusables/actions/release-trigger-workflow.md
similarity index 100%
rename from translations/zh-CN/data/reusables/github-actions/release-trigger-workflow.md
rename to translations/zh-CN/data/reusables/actions/release-trigger-workflow.md
diff --git a/translations/zh-CN/data/reusables/github-actions/run_id_description.md b/translations/zh-CN/data/reusables/actions/run_id_description.md
similarity index 100%
rename from translations/zh-CN/data/reusables/github-actions/run_id_description.md
rename to translations/zh-CN/data/reusables/actions/run_id_description.md
diff --git a/translations/zh-CN/data/reusables/github-actions/run_number_description.md b/translations/zh-CN/data/reusables/actions/run_number_description.md
similarity index 100%
rename from translations/zh-CN/data/reusables/github-actions/run_number_description.md
rename to translations/zh-CN/data/reusables/actions/run_number_description.md
diff --git a/translations/zh-CN/data/reusables/github-actions/runner-app-open-source.md b/translations/zh-CN/data/reusables/actions/runner-app-open-source.md
similarity index 100%
rename from translations/zh-CN/data/reusables/github-actions/runner-app-open-source.md
rename to translations/zh-CN/data/reusables/actions/runner-app-open-source.md
diff --git a/translations/zh-CN/data/reusables/github-actions/runner-group-assign-policy-org.md b/translations/zh-CN/data/reusables/actions/runner-group-assign-policy-org.md
similarity index 100%
rename from translations/zh-CN/data/reusables/github-actions/runner-group-assign-policy-org.md
rename to translations/zh-CN/data/reusables/actions/runner-group-assign-policy-org.md
diff --git a/translations/zh-CN/data/reusables/github-actions/runner-group-assign-policy-repo.md b/translations/zh-CN/data/reusables/actions/runner-group-assign-policy-repo.md
similarity index 100%
rename from translations/zh-CN/data/reusables/github-actions/runner-group-assign-policy-repo.md
rename to translations/zh-CN/data/reusables/actions/runner-group-assign-policy-repo.md
diff --git a/translations/zh-CN/data/reusables/github-actions/runner-label-settings.md b/translations/zh-CN/data/reusables/actions/runner-label-settings.md
similarity index 100%
rename from translations/zh-CN/data/reusables/github-actions/runner-label-settings.md
rename to translations/zh-CN/data/reusables/actions/runner-label-settings.md
diff --git a/translations/zh-CN/data/reusables/github-actions/runner-workflow-continuity.md b/translations/zh-CN/data/reusables/actions/runner-workflow-continuity.md
similarity index 100%
rename from translations/zh-CN/data/reusables/github-actions/runner-workflow-continuity.md
rename to translations/zh-CN/data/reusables/actions/runner-workflow-continuity.md
diff --git a/translations/zh-CN/data/reusables/github-actions/secrets-org-level-overview.md b/translations/zh-CN/data/reusables/actions/secrets-org-level-overview.md
similarity index 100%
rename from translations/zh-CN/data/reusables/github-actions/secrets-org-level-overview.md
rename to translations/zh-CN/data/reusables/actions/secrets-org-level-overview.md
diff --git a/translations/zh-CN/data/reusables/github-actions/secrets-redaction-warning.md b/translations/zh-CN/data/reusables/actions/secrets-redaction-warning.md
similarity index 100%
rename from translations/zh-CN/data/reusables/github-actions/secrets-redaction-warning.md
rename to translations/zh-CN/data/reusables/actions/secrets-redaction-warning.md
diff --git a/translations/zh-CN/data/reusables/github-actions/self-hosted-runner-auto-removal.md b/translations/zh-CN/data/reusables/actions/self-hosted-runner-auto-removal.md
similarity index 100%
rename from translations/zh-CN/data/reusables/github-actions/self-hosted-runner-auto-removal.md
rename to translations/zh-CN/data/reusables/actions/self-hosted-runner-auto-removal.md
diff --git a/translations/zh-CN/data/reusables/github-actions/self-hosted-runner-check-installation-success.md b/translations/zh-CN/data/reusables/actions/self-hosted-runner-check-installation-success.md
similarity index 89%
rename from translations/zh-CN/data/reusables/github-actions/self-hosted-runner-check-installation-success.md
rename to translations/zh-CN/data/reusables/actions/self-hosted-runner-check-installation-success.md
index 1a54eb0a74e8..a1355c42a954 100644
--- a/translations/zh-CN/data/reusables/github-actions/self-hosted-runner-check-installation-success.md
+++ b/translations/zh-CN/data/reusables/actions/self-hosted-runner-check-installation-success.md
@@ -5,6 +5,6 @@ After completing the steps to add a self-hosted runner, the runner and its statu
必须激活自托管运行器应用程序，运行器才能接受作业。 当运行器应用程序连接到 {% data variables.product.product_name %} 并准备接收作业时，您将在机器的终端上看到以下消息。
-{% data reusables.github-actions.self-hosted-runner-connected-output %}
+{% data reusables.actions.self-hosted-runner-connected-output %}
更多信息请参阅“[自托管运行器监控和故障排除](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners)”。
diff --git a/translations/zh-CN/data/reusables/github-actions/self-hosted-runner-check-mac-linux.md b/translations/zh-CN/data/reusables/actions/self-hosted-runner-check-mac-linux.md
similarity index 100%
rename from translations/zh-CN/data/reusables/github-actions/self-hosted-runner-check-mac-linux.md
rename to translations/zh-CN/data/reusables/actions/self-hosted-runner-check-mac-linux.md
diff --git a/translations/zh-CN/data/reusables/github-actions/self-hosted-runner-configure-runner-group-access.md b/translations/zh-CN/data/reusables/actions/self-hosted-runner-configure-runner-group-access.md
similarity index 89%
rename from translations/zh-CN/data/reusables/github-actions/self-hosted-runner-configure-runner-group-access.md
rename to translations/zh-CN/data/reusables/actions/self-hosted-runner-configure-runner-group-access.md
index 31389bddcc0a..a0f66371adb6 100644
--- a/translations/zh-CN/data/reusables/github-actions/self-hosted-runner-configure-runner-group-access.md
+++ b/translations/zh-CN/data/reusables/actions/self-hosted-runner-configure-runner-group-access.md
@@ -6,7 +6,7 @@
**警告**
- {% indented_data_reference reusables.github-actions.self-hosted-runner-security spaces=3 %}
+ {% indented_data_reference reusables.actions.self-hosted-runner-security spaces=3 %}
更多信息请参阅“[关于自托管运行器](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)”。
diff --git a/translations/zh-CN/data/reusables/github-actions/self-hosted-runner-configure.md b/translations/zh-CN/data/reusables/actions/self-hosted-runner-configure.md
similarity index 100%
rename from translations/zh-CN/data/reusables/github-actions/self-hosted-runner-configure.md
rename to translations/zh-CN/data/reusables/actions/self-hosted-runner-configure.md
diff --git a/translations/zh-CN/data/reusables/github-actions/self-hosted-runner-connected-output.md b/translations/zh-CN/data/reusables/actions/self-hosted-runner-connected-output.md
similarity index 100%
rename from translations/zh-CN/data/reusables/github-actions/self-hosted-runner-connected-output.md
rename to translations/zh-CN/data/reusables/actions/self-hosted-runner-connected-output.md
diff --git a/translations/zh-CN/data/reusables/github-actions/self-hosted-runner-create-group.md b/translations/zh-CN/data/reusables/actions/self-hosted-runner-create-group.md
similarity index 100%
rename from translations/zh-CN/data/reusables/github-actions/self-hosted-runner-create-group.md
rename to translations/zh-CN/data/reusables/actions/self-hosted-runner-create-group.md
diff --git a/translations/zh-CN/data/reusables/github-actions/self-hosted-runner-description.md b/translations/zh-CN/data/reusables/actions/self-hosted-runner-description.md
similarity index 100%
rename from translations/zh-CN/data/reusables/github-actions/self-hosted-runner-description.md
rename to translations/zh-CN/data/reusables/actions/self-hosted-runner-description.md
diff --git a/translations/zh-CN/data/reusables/github-actions/self-hosted-runner-groups-navigate-to-repo-org-enterprise.md b/translations/zh-CN/data/reusables/actions/self-hosted-runner-groups-navigate-to-repo-org-enterprise.md
similarity index 100%
rename from translations/zh-CN/data/reusables/github-actions/self-hosted-runner-groups-navigate-to-repo-org-enterprise.md
rename to translations/zh-CN/data/reusables/actions/self-hosted-runner-groups-navigate-to-repo-org-enterprise.md
diff --git a/translations/zh-CN/data/reusables/github-actions/self-hosted-runner-labels-runs-on.md b/translations/zh-CN/data/reusables/actions/self-hosted-runner-labels-runs-on.md
similarity index 100%
rename from translations/zh-CN/data/reusables/github-actions/self-hosted-runner-labels-runs-on.md
rename to translations/zh-CN/data/reusables/actions/self-hosted-runner-labels-runs-on.md
diff --git a/translations/zh-CN/data/reusables/github-actions/self-hosted-runner-labels-view-assigned-labels.md b/translations/zh-CN/data/reusables/actions/self-hosted-runner-labels-view-assigned-labels.md
similarity index 100%
rename from translations/zh-CN/data/reusables/github-actions/self-hosted-runner-labels-view-assigned-labels.md
rename to translations/zh-CN/data/reusables/actions/self-hosted-runner-labels-view-assigned-labels.md
diff --git a/translations/zh-CN/data/reusables/github-actions/self-hosted-runner-list-group.md b/translations/zh-CN/data/reusables/actions/self-hosted-runner-list-group.md
similarity index 100%
rename from translations/zh-CN/data/reusables/github-actions/self-hosted-runner-list-group.md
rename to translations/zh-CN/data/reusables/actions/self-hosted-runner-list-group.md
diff --git a/translations/zh-CN/data/reusables/github-actions/self-hosted-runner-list.md b/translations/zh-CN/data/reusables/actions/self-hosted-runner-list.md
similarity index 100%
rename from translations/zh-CN/data/reusables/github-actions/self-hosted-runner-list.md
rename to translations/zh-CN/data/reusables/actions/self-hosted-runner-list.md
diff --git a/translations/zh-CN/data/reusables/github-actions/self-hosted-runner-management-permissions-required.md b/translations/zh-CN/data/reusables/actions/self-hosted-runner-management-permissions-required.md
similarity index 100%
rename from translations/zh-CN/data/reusables/github-actions/self-hosted-runner-management-permissions-required.md
rename to translations/zh-CN/data/reusables/actions/self-hosted-runner-management-permissions-required.md
diff --git a/translations/zh-CN/data/reusables/github-actions/self-hosted-runner-navigate-repo-and-org.md b/translations/zh-CN/data/reusables/actions/self-hosted-runner-navigate-repo-and-org.md
similarity index 100%
rename from translations/zh-CN/data/reusables/github-actions/self-hosted-runner-navigate-repo-and-org.md
rename to translations/zh-CN/data/reusables/actions/self-hosted-runner-navigate-repo-and-org.md
diff --git a/translations/zh-CN/data/reusables/github-actions/self-hosted-runner-navigate-to-org-enterprise.md b/translations/zh-CN/data/reusables/actions/self-hosted-runner-navigate-to-org-enterprise.md
similarity index 100%
rename from translations/zh-CN/data/reusables/github-actions/self-hosted-runner-navigate-to-org-enterprise.md
rename to translations/zh-CN/data/reusables/actions/self-hosted-runner-navigate-to-org-enterprise.md
diff --git a/translations/zh-CN/data/reusables/github-actions/self-hosted-runner-navigate-to-repo-org-enterprise.md b/translations/zh-CN/data/reusables/actions/self-hosted-runner-navigate-to-repo-org-enterprise.md
similarity index 100%
rename from translations/zh-CN/data/reusables/github-actions/self-hosted-runner-navigate-to-repo-org-enterprise.md
rename to translations/zh-CN/data/reusables/actions/self-hosted-runner-navigate-to-repo-org-enterprise.md
diff --git a/translations/zh-CN/data/reusables/github-actions/self-hosted-runner-public-repo-access.md b/translations/zh-CN/data/reusables/actions/self-hosted-runner-public-repo-access.md
similarity index 100%
rename from translations/zh-CN/data/reusables/github-actions/self-hosted-runner-public-repo-access.md
rename to translations/zh-CN/data/reusables/actions/self-hosted-runner-public-repo-access.md
diff --git a/translations/zh-CN/data/reusables/github-actions/self-hosted-runner-removal-impact.md b/translations/zh-CN/data/reusables/actions/self-hosted-runner-removal-impact.md
similarity index 100%
rename from translations/zh-CN/data/reusables/github-actions/self-hosted-runner-removal-impact.md
rename to translations/zh-CN/data/reusables/actions/self-hosted-runner-removal-impact.md
diff --git a/translations/zh-CN/data/reusables/github-actions/self-hosted-runner-removing-a-runner-updated.md b/translations/zh-CN/data/reusables/actions/self-hosted-runner-removing-a-runner-updated.md
similarity index 100%
rename from translations/zh-CN/data/reusables/github-actions/self-hosted-runner-removing-a-runner-updated.md
rename to translations/zh-CN/data/reusables/actions/self-hosted-runner-removing-a-runner-updated.md
diff --git a/translations/zh-CN/data/reusables/github-actions/self-hosted-runner-removing-a-runner.md b/translations/zh-CN/data/reusables/actions/self-hosted-runner-removing-a-runner.md
similarity index 100%
rename from translations/zh-CN/data/reusables/github-actions/self-hosted-runner-removing-a-runner.md
rename to translations/zh-CN/data/reusables/actions/self-hosted-runner-removing-a-runner.md
diff --git a/translations/zh-CN/data/reusables/github-actions/self-hosted-runner-reqs-docker.md b/translations/zh-CN/data/reusables/actions/self-hosted-runner-reqs-docker.md
similarity index 100%
rename from translations/zh-CN/data/reusables/github-actions/self-hosted-runner-reqs-docker.md
rename to translations/zh-CN/data/reusables/actions/self-hosted-runner-reqs-docker.md
diff --git a/translations/zh-CN/data/reusables/github-actions/self-hosted-runner-reusing.md b/translations/zh-CN/data/reusables/actions/self-hosted-runner-reusing.md
similarity index 100%
rename from translations/zh-CN/data/reusables/github-actions/self-hosted-runner-reusing.md
rename to translations/zh-CN/data/reusables/actions/self-hosted-runner-reusing.md
diff --git a/translations/zh-CN/data/reusables/github-actions/self-hosted-runner-security.md b/translations/zh-CN/data/reusables/actions/self-hosted-runner-security.md
similarity index 100%
rename from translations/zh-CN/data/reusables/github-actions/self-hosted-runner-security.md
rename to translations/zh-CN/data/reusables/actions/self-hosted-runner-security.md
diff --git a/translations/zh-CN/data/reusables/github-actions/service-container-add-script.md b/translations/zh-CN/data/reusables/actions/service-container-add-script.md
similarity index 100%
rename from translations/zh-CN/data/reusables/github-actions/service-container-add-script.md
rename to translations/zh-CN/data/reusables/actions/service-container-add-script.md
diff --git a/translations/zh-CN/data/reusables/github-actions/service-container-host-runner.md b/translations/zh-CN/data/reusables/actions/service-container-host-runner.md
similarity index 100%
rename from translations/zh-CN/data/reusables/github-actions/service-container-host-runner.md
rename to translations/zh-CN/data/reusables/actions/service-container-host-runner.md
diff --git a/translations/zh-CN/data/reusables/github-actions/service-container-host.md b/translations/zh-CN/data/reusables/actions/service-container-host.md
similarity index 100%
rename from translations/zh-CN/data/reusables/github-actions/service-container-host.md
rename to translations/zh-CN/data/reusables/actions/service-container-host.md
diff --git a/translations/zh-CN/data/reusables/github-actions/service-container-localhost.md b/translations/zh-CN/data/reusables/actions/service-container-localhost.md
similarity index 100%
rename from translations/zh-CN/data/reusables/github-actions/service-container-localhost.md
rename to translations/zh-CN/data/reusables/actions/service-container-localhost.md
diff --git a/translations/zh-CN/data/reusables/github-actions/service-container-prereqs.md b/translations/zh-CN/data/reusables/actions/service-container-prereqs.md
similarity index 100%
rename from translations/zh-CN/data/reusables/github-actions/service-container-prereqs.md
rename to translations/zh-CN/data/reusables/actions/service-container-prereqs.md
diff --git a/translations/zh-CN/data/reusables/github-actions/service-template-steps.md b/translations/zh-CN/data/reusables/actions/service-template-steps.md
similarity index 100%
rename from translations/zh-CN/data/reusables/github-actions/service-template-steps.md
rename to translations/zh-CN/data/reusables/actions/service-template-steps.md
diff --git a/translations/zh-CN/data/reusables/github-actions/settings-sidebar-actions-runner-groups-selection.md b/translations/zh-CN/data/reusables/actions/settings-sidebar-actions-runner-groups-selection.md
similarity index 100%
rename from translations/zh-CN/data/reusables/github-actions/settings-sidebar-actions-runner-groups-selection.md
rename to translations/zh-CN/data/reusables/actions/settings-sidebar-actions-runner-groups-selection.md
diff --git a/translations/zh-CN/data/reusables/github-actions/settings-sidebar-actions-runner-groups.md b/translations/zh-CN/data/reusables/actions/settings-sidebar-actions-runner-groups.md
similarity index 100%
rename from translations/zh-CN/data/reusables/github-actions/settings-sidebar-actions-runner-groups.md
rename to translations/zh-CN/data/reusables/actions/settings-sidebar-actions-runner-groups.md
diff --git a/translations/zh-CN/data/reusables/github-actions/settings-sidebar-actions-runner-selection.md b/translations/zh-CN/data/reusables/actions/settings-sidebar-actions-runner-selection.md
similarity index 100%
rename from translations/zh-CN/data/reusables/github-actions/settings-sidebar-actions-runner-selection.md
rename to translations/zh-CN/data/reusables/actions/settings-sidebar-actions-runner-selection.md
diff --git a/translations/zh-CN/data/reusables/github-actions/settings-sidebar-actions-runners-updated.md b/translations/zh-CN/data/reusables/actions/settings-sidebar-actions-runners-updated.md
similarity index 100%
rename from translations/zh-CN/data/reusables/github-actions/settings-sidebar-actions-runners-updated.md
rename to translations/zh-CN/data/reusables/actions/settings-sidebar-actions-runners-updated.md
diff --git a/translations/zh-CN/data/reusables/github-actions/settings-sidebar-actions-runners.md b/translations/zh-CN/data/reusables/actions/settings-sidebar-actions-runners.md
similarity index 100%
rename from translations/zh-CN/data/reusables/github-actions/settings-sidebar-actions-runners.md
rename to translations/zh-CN/data/reusables/actions/settings-sidebar-actions-runners.md
diff --git a/translations/zh-CN/data/reusables/github-actions/settings-sidebar-actions.md b/translations/zh-CN/data/reusables/actions/settings-sidebar-actions.md
similarity index 100%
rename from translations/zh-CN/data/reusables/github-actions/settings-sidebar-actions.md
rename to translations/zh-CN/data/reusables/actions/settings-sidebar-actions.md
diff --git a/translations/zh-CN/data/reusables/github-actions/setup-node-intro.md b/translations/zh-CN/data/reusables/actions/setup-node-intro.md
similarity index 100%
rename from translations/zh-CN/data/reusables/github-actions/setup-node-intro.md
rename to translations/zh-CN/data/reusables/actions/setup-node-intro.md
diff --git a/translations/zh-CN/data/reusables/github-actions/sidebar-environment.md b/translations/zh-CN/data/reusables/actions/sidebar-environment.md
similarity index 100%
rename from translations/zh-CN/data/reusables/github-actions/sidebar-environment.md
rename to translations/zh-CN/data/reusables/actions/sidebar-environment.md
diff --git a/translations/zh-CN/data/reusables/github-actions/sidebar-secret.md b/translations/zh-CN/data/reusables/actions/sidebar-secret.md
similarity index 100%
rename from translations/zh-CN/data/reusables/github-actions/sidebar-secret.md
rename to translations/zh-CN/data/reusables/actions/sidebar-secret.md
diff --git a/translations/zh-CN/data/reusables/github-actions/supported-github-runners.md b/translations/zh-CN/data/reusables/actions/supported-github-runners.md
similarity index 94%
rename from translations/zh-CN/data/reusables/github-actions/supported-github-runners.md
rename to translations/zh-CN/data/reusables/actions/supported-github-runners.md
index a23bc3e85155..f4832c7a02da 100644
--- a/translations/zh-CN/data/reusables/github-actions/supported-github-runners.md
+++ b/translations/zh-CN/data/reusables/actions/supported-github-runners.md
@@ -12,10 +12,10 @@
Windows Server 2022
-windows-2022
+windows-latest 或 windows-2022
-The windows-latest label currently uses the Windows Server 2019 runner image.
+The windows-latest label currently uses the Windows Server 2022 runner image.
@@ -23,7 +23,7 @@ The windows-latest label currently uses the Windows Server 2019 run
Windows Server 2019
-windows-latest 或 windows-2019
+windows-2019
diff --git a/translations/zh-CN/data/reusables/github-actions/usage-api-requests.md b/translations/zh-CN/data/reusables/actions/usage-api-requests.md
similarity index 100%
rename from translations/zh-CN/data/reusables/github-actions/usage-api-requests.md
rename to translations/zh-CN/data/reusables/actions/usage-api-requests.md
diff --git a/translations/zh-CN/data/reusables/github-actions/usage-matrix-limits.md b/translations/zh-CN/data/reusables/actions/usage-matrix-limits.md
similarity index 100%
rename from translations/zh-CN/data/reusables/github-actions/usage-matrix-limits.md
rename to translations/zh-CN/data/reusables/actions/usage-matrix-limits.md
diff --git a/translations/zh-CN/data/reusables/github-actions/usage-workflow-queue-limits.md b/translations/zh-CN/data/reusables/actions/usage-workflow-queue-limits.md
similarity index 100%
rename from translations/zh-CN/data/reusables/github-actions/usage-workflow-queue-limits.md
rename to translations/zh-CN/data/reusables/actions/usage-workflow-queue-limits.md
diff --git a/translations/zh-CN/data/reusables/github-actions/usage-workflow-run-time.md b/translations/zh-CN/data/reusables/actions/usage-workflow-run-time.md
similarity index 100%
rename from translations/zh-CN/data/reusables/github-actions/usage-workflow-run-time.md
rename to translations/zh-CN/data/reusables/actions/usage-workflow-run-time.md
diff --git a/translations/zh-CN/data/reusables/github-actions/using-context-or-environment-variables.md b/translations/zh-CN/data/reusables/actions/using-context-or-environment-variables.md
similarity index 100%
rename from translations/zh-CN/data/reusables/github-actions/using-context-or-environment-variables.md
rename to translations/zh-CN/data/reusables/actions/using-context-or-environment-variables.md
diff --git a/translations/zh-CN/data/reusables/github-actions/workflow-dispatch-inputs.md b/translations/zh-CN/data/reusables/actions/workflow-dispatch-inputs.md
similarity index 100%
rename from translations/zh-CN/data/reusables/github-actions/workflow-dispatch-inputs.md
rename to translations/zh-CN/data/reusables/actions/workflow-dispatch-inputs.md
diff --git a/translations/zh-CN/data/reusables/github-actions/workflow-permissions-intro.md b/translations/zh-CN/data/reusables/actions/workflow-permissions-intro.md
similarity index 100%
rename from translations/zh-CN/data/reusables/github-actions/workflow-permissions-intro.md
rename to translations/zh-CN/data/reusables/actions/workflow-permissions-intro.md
diff --git a/translations/zh-CN/data/reusables/github-actions/workflow-permissions-modifying.md b/translations/zh-CN/data/reusables/actions/workflow-permissions-modifying.md
similarity index 100%
rename from translations/zh-CN/data/reusables/github-actions/workflow-permissions-modifying.md
rename to translations/zh-CN/data/reusables/actions/workflow-permissions-modifying.md
diff --git a/translations/zh-CN/data/reusables/github-actions/workflows-from-public-fork-setting.md b/translations/zh-CN/data/reusables/actions/workflows-from-public-fork-setting.md
similarity index 100%
rename from translations/zh-CN/data/reusables/github-actions/workflows-from-public-fork-setting.md
rename to translations/zh-CN/data/reusables/actions/workflows-from-public-fork-setting.md
diff --git a/translations/zh-CN/data/reusables/actions/workflows/section-triggering-a-workflow.md b/translations/zh-CN/data/reusables/actions/workflows/section-triggering-a-workflow.md
index 9774dfa64fe5..591d940be73c 100644
--- a/translations/zh-CN/data/reusables/actions/workflows/section-triggering-a-workflow.md
+++ b/translations/zh-CN/data/reusables/actions/workflows/section-triggering-a-workflow.md
@@ -3,4 +3,4 @@ To automatically trigger a workflow, use `on` to define which events can cause t
You can define single or multiple events that can a trigger workflow, or set a time schedule. You can also restrict the execution of a workflow to only occur for specific files, tags, or branch changes. 以下各节介绍了这些选项。
-{% data reusables.github-actions.actions-on-examples %}
+{% data reusables.actions.actions-on-examples %}
diff --git a/translations/zh-CN/data/reusables/github-actions/actions-on-examples.md b/translations/zh-CN/data/reusables/github-actions/actions-on-examples.md
deleted file mode 100644
index 26d4a25747f6..000000000000
--- a/translations/zh-CN/data/reusables/github-actions/actions-on-examples.md
+++ /dev/null
@@ -1,19 +0,0 @@
-### Using a single event
-
-{% data reusables.github-actions.on-single-example %}
-
-### Using multiple events
-
-{% data reusables.github-actions.on-multiple-example %}
-
-### Using activity types
-
-{% data reusables.github-actions.actions-activity-types %}
-
-### Using filters
-
-{% data reusables.github-actions.actions-filters %}
-
-### Using activity types and filters with multiple events
-
-{% data reusables.github-actions.actions-multiple-types %}
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/github-actions/ip-allow-list-self-hosted-runners.md b/translations/zh-CN/data/reusables/github-actions/ip-allow-list-self-hosted-runners.md
deleted file mode 100644
index dcf717caf0ed..000000000000
--- a/translations/zh-CN/data/reusables/github-actions/ip-allow-list-self-hosted-runners.md
+++ /dev/null
@@ -1,13 +0,0 @@
-{% ifversion ghae %}
-要允许您的自行托管运行器与
-{% data variables.product.prodname_dotcom %} 通信，请将自托管运行器的 IP 地址或 IP 地址范围添加到 IP 允许列表。 更多信息请参阅“[添加允许的 IP 地址](#adding-an-allowed-ip-address)”。
-{% else %}
-{% warning %}
-
-**警告**：如果您使用 IP 允许列表，并且还希望使用 {% data variables.product.prodname_actions %}，则必须使用自托管运行器。 更多信息请参阅“[托管您自己的运行器](/actions/automating-your-workflow-with-github-actions/about-self-hosted-runners)”。
-
-{% endwarning %}
-要允许您的自行托管运行器与
-
-{% data variables.product.prodname_dotcom %} 通信，请将自托管运行器的 IP 地址或 IP 地址范围添加到 IP 允许列表。 更多信息请参阅“[添加允许的 IP 地址](#adding-an-allowed-ip-address)”。
-{% endif %}
diff --git a/translations/zh-CN/data/reusables/repositories/navigate-to-commit-page.md b/translations/zh-CN/data/reusables/repositories/navigate-to-commit-page.md
new file mode 100644
index 000000000000..bec770c79066
--- /dev/null
+++ b/translations/zh-CN/data/reusables/repositories/navigate-to-commit-page.md
@@ -0,0 +1 @@
+1. On the main page of the repository, click the commits to navigate to the commits page. 
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/rest-reference/actions/actions.md b/translations/zh-CN/data/reusables/rest-reference/actions/actions.md
new file mode 100644
index 000000000000..53d0e206f463
--- /dev/null
+++ b/translations/zh-CN/data/reusables/rest-reference/actions/actions.md
@@ -0,0 +1 @@
+{% data variables.product.prodname_actions %} API 允许您使用 REST API 来管理 {% data variables.product.prodname_actions %}。 {% data reusables.actions.actions-authentication %} {% data variables.product.prodname_github_apps %} 需要在每个端点中提及的权限。 更多信息请参阅“[{% data variables.product.prodname_actions %} 文档](/actions)”。
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/rest-reference/actions/artifacts.md b/translations/zh-CN/data/reusables/rest-reference/actions/artifacts.md
new file mode 100644
index 000000000000..b475672a9145
--- /dev/null
+++ b/translations/zh-CN/data/reusables/rest-reference/actions/artifacts.md
@@ -0,0 +1,5 @@
+## 构件
+
+构件 API 允许您下载、删除和检索有关工作流程构件的信息。 {% data reusables.actions.about-artifacts %}更多信息请参阅“[使用构件持久化工作流程](/actions/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)”。
+
+{% data reusables.actions.actions-authentication %} {% data reusables.actions.actions-app-actions-permissions-api %}
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/rest-reference/actions/permissions.md b/translations/zh-CN/data/reusables/rest-reference/actions/permissions.md
new file mode 100644
index 000000000000..b6e3adf3d6aa
--- /dev/null
+++ b/translations/zh-CN/data/reusables/rest-reference/actions/permissions.md
@@ -0,0 +1,3 @@
+## 权限
+
+Permissions API 允许您为允许哪些企业、组织和存储库运行 {% data variables.product.prodname_actions %} 以及允许运行哪些操作设置权限。{% ifversion fpt or ghec or ghes %} 更多信息请参阅“[使用限制、计费和管理](/actions/reference/usage-limits-billing-and-administration#disabling-or-limiting-github-actions-for-your-repository-or-organization)”。{% endif %}
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/rest-reference/actions/secrets.md b/translations/zh-CN/data/reusables/rest-reference/actions/secrets.md
new file mode 100644
index 000000000000..8ef7afefd0e6
--- /dev/null
+++ b/translations/zh-CN/data/reusables/rest-reference/actions/secrets.md
@@ -0,0 +1,5 @@
+## 密码
+
+密码 API 允许您创建、更新、删除和检索有关加密密码的信息。 {% data reusables.actions.about-secrets %}更多信息请参阅“[创建和使用加密密码](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)”。
+
+{% data reusables.actions.actions-authentication %} {% data variables.product.prodname_github_apps %} 必须具有`密码`权限才可使用此 API。 经过身份验证的用户必须对仓库具有协作者权限才可创建、更新或读取密码。
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/rest-reference/actions/self-hosted-runner-groups.md b/translations/zh-CN/data/reusables/rest-reference/actions/self-hosted-runner-groups.md
new file mode 100644
index 000000000000..cb08218f2ba1
--- /dev/null
+++ b/translations/zh-CN/data/reusables/rest-reference/actions/self-hosted-runner-groups.md
@@ -0,0 +1,7 @@
+## 自托管运行器组
+
+{% data reusables.actions.ae-self-hosted-runners-notice %}
+
+自托管运行器组 API 允许您管理自托运行器组。 更多信息请参阅“[使用组管理对自托管运行器的访问](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups)”。
+
+{% data reusables.actions.actions-authentication %} {% data variables.product.prodname_github_apps %} 必须对仓库具有`管理`权限，或者对组织具有 `organization_self_hosted_runners` 权限。 经过身份验证的用户必须具有对存储库或组织的管理员访问权限或者企业的 `manage_runners:enterprise` 作用域才能使用此 API。
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/rest-reference/actions/self-hosted-runners.md b/translations/zh-CN/data/reusables/rest-reference/actions/self-hosted-runners.md
new file mode 100644
index 000000000000..8b1246a5f08a
--- /dev/null
+++ b/translations/zh-CN/data/reusables/rest-reference/actions/self-hosted-runners.md
@@ -0,0 +1,7 @@
+## 自托管运行器
+
+{% data reusables.actions.ae-self-hosted-runners-notice %}
+
+自托管运行器 API 允许您注册、查看和删除自托管的运行器。 {% data reusables.actions.about-self-hosted-runners %} 更多信息请参阅“[托管您自己的运行器](/actions/hosting-your-own-runners)”。
+
+{% data reusables.actions.actions-authentication %} {% data variables.product.prodname_github_apps %} 必须对仓库具有`管理`权限，或者对组织具有 `organization_self_hosted_runners` 权限。 经过身份验证的用户必须具有对存储库或组织的管理员访问权限或者企业的 `manage_runners:enterprise` 作用域才能使用此 API。
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/rest-reference/actions/workflow-jobs.md b/translations/zh-CN/data/reusables/rest-reference/actions/workflow-jobs.md
new file mode 100644
index 000000000000..251262b96fe1
--- /dev/null
+++ b/translations/zh-CN/data/reusables/rest-reference/actions/workflow-jobs.md
@@ -0,0 +1,5 @@
+## 工作流程作业
+
+工作流程作业 API 允许您查看日志和工作流程作业。 {% data reusables.actions.about-workflow-jobs %} 更多信息请参阅“[GitHub Actions 的工作流程语法](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions)”。
+
+{% data reusables.actions.actions-authentication %} {% data reusables.actions.actions-app-actions-permissions-api %}
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/rest-reference/actions/workflow-runs.md b/translations/zh-CN/data/reusables/rest-reference/actions/workflow-runs.md
new file mode 100644
index 000000000000..0f38e2b7a2d9
--- /dev/null
+++ b/translations/zh-CN/data/reusables/rest-reference/actions/workflow-runs.md
@@ -0,0 +1,5 @@
+## Workflow runs
+
+The Workflow Runs API allows you to view, re-run, cancel, and view logs for workflow runs. {% data reusables.actions.about-workflow-runs %} For more information, see "[Managing a workflow run](/actions/automating-your-workflow-with-github-actions/managing-a-workflow-run)."
+
+{% data reusables.actions.actions-authentication %} {% data reusables.actions.actions-app-actions-permissions-api %}
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/rest-reference/actions/workflows.md b/translations/zh-CN/data/reusables/rest-reference/actions/workflows.md
new file mode 100644
index 000000000000..53443d4f005e
--- /dev/null
+++ b/translations/zh-CN/data/reusables/rest-reference/actions/workflows.md
@@ -0,0 +1,5 @@
+## 工作流程
+
+工作流程 API 允许您查看仓库的工作流程。 {% data reusables.actions.about-workflows %} 更多信息请参阅“[使用 GitHub Actions 自动化工作流程](/actions/automating-your-workflow-with-github-actions)”。
+
+{% data reusables.actions.actions-authentication %} {% data reusables.actions.actions-app-actions-permissions-api %}
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/rest-reference/activity/events.md b/translations/zh-CN/data/reusables/rest-reference/activity/events.md
new file mode 100644
index 000000000000..78f65cef3653
--- /dev/null
+++ b/translations/zh-CN/data/reusables/rest-reference/activity/events.md
@@ -0,0 +1,22 @@
+## Events
+
+The Events API is a read-only API to the {% data variables.product.prodname_dotcom %} events. These events power the various activity streams on the site.
+
+The Events API can return different types of events triggered by activity on {% data variables.product.product_name %}. For more information about the specific events that you can receive from the Events API, see "[{% data variables.product.prodname_dotcom %} Event types](/developers/webhooks-and-events/github-event-types)." An events API for repository issues is also available. For more information, see the "[Issue Events API](/rest/reference/issues#events)."
+
+Events are optimized for polling with the "ETag" header. If no new events have been triggered, you will see a "304 Not Modified" response, and your current rate limit will be untouched. There is also an "X-Poll-Interval" header that specifies how often (in seconds) you are allowed to poll. In times of high server load, the time may increase. Please obey the header.
+
+``` shell
+$ curl -I {% data variables.product.api_url_pre %}/users/tater/events
+> HTTP/2 200
+> X-Poll-Interval: 60
+> ETag: "a18c3bded88eb5dbb5c849a489412bf3"
+
+# The quotes around the ETag value are important
+$ curl -I {% data variables.product.api_url_pre %}/users/tater/events \
+$ -H 'If-None-Match: "a18c3bded88eb5dbb5c849a489412bf3"'
+> HTTP/2 304
+> X-Poll-Interval: 60
+```
+
+Only events created within the past 90 days will be included in timelines. Events older than 90 days will not be included (even if the total number of events in the timeline is less than 300).
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/rest-reference/activity/feeds.md b/translations/zh-CN/data/reusables/rest-reference/activity/feeds.md
new file mode 100644
index 000000000000..2710feab44f4
--- /dev/null
+++ b/translations/zh-CN/data/reusables/rest-reference/activity/feeds.md
@@ -0,0 +1,52 @@
+## 馈送
+
+### Example of getting an Atom feed
+
+To get a feed in Atom format, you must specify the `application/atom+xml` type in the `Accept` header. For example, to get the Atom feed for GitHub security advisories:
+
+ curl -H "Accept: application/atom+xml" https://github.com/security-advisories
+
+#### 响应
+
+```shell
+HTTP/2 200
+```
+
+```xml
+
+
+ tag:github.com,2008:/security-advisories
+
+ GitHub Security Advisory Feed
+
+ GitHub
+
+ 2019-01-14T19:34:52Z
+
+ tag:github.com,2008:GHSA-abcd-12ab-23cd
+ 2018-07-26T15:14:52Z
+ 2019-01-14T19:34:52Z
+ [GHSA-abcd-12ab-23cd] Moderate severity vulnerability that affects Octoapp
+
+
+ <p>Octoapp node module before 4.17.5 suffers from a Modification of Assumed-Immutable Data (MAID) vulnerability via defaultsDeep, merge, and mergeWith functions, which allows a malicious user to modify the prototype of "Object" via <strong>proto</strong>, causing the addition or modification of an existing property that will exist on all objects.</p>
+ <p><strong>Affected Packages</strong></p>
+
+ <dl>
+ <dt>Octoapp</dt>
+ <dd>Ecosystem: npm</dd>
+ <dd>Severity: moderate</dd>
+ <dd>Versions: < 4.17.5</dd>
+ <dd>Fixed in: 4.17.5</dd>
+ </dl>
+
+ <p><strong>References</strong></p>
+
+ <ul>
+ <li>https://nvd.nist.gov/vuln/detail/CVE-2018-123</li>
+ </ul>
+
+
+
+
+```
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/rest-reference/activity/notifications.md b/translations/zh-CN/data/reusables/rest-reference/activity/notifications.md
new file mode 100644
index 000000000000..8c0be957d8d4
--- /dev/null
+++ b/translations/zh-CN/data/reusables/rest-reference/activity/notifications.md
@@ -0,0 +1,59 @@
+## 通知
+
+用户将收到其关注的仓库中各种对话的通知，包括：
+
+* 议题及其评论
+* 拉取请求及其评论
+* 对任何提交的评论
+
+当用户涉及未关注仓库中的对话时也会发送通知，包括：
+
+* **@提及**
+* 议题分配
+* 提交用户作者或提交
+* 用户积极参与的任何讨论
+
+所有通知 API 调用都需要 `notifications` 或 `repo` API 作用域。 这将赋予对某些议题和提交内容的只读权限。 您仍需要 `repo` 作用域才能从相应的端点访问议题和提交。
+
+通知以“帖子”的形式返回。 帖子包含当前对议题、拉取请求或提交的讨论信息。
+
+通知通过 `Last-Modified` 标头对轮询进行了优化。 如果没有新的通知，您将看到 `304 Not Modified` 响应，您的当前速率限制不受影响。 有一个 `X-Poll-Interval` 标头用于指定允许您轮询的间隔时间（以秒为单位）。 在服务器负载较高时，该时间可能会增加。 请遵循标头指示。
+
+``` shell
+# Add authentication to your requests
+$ curl -I {% data variables.product.api_url_pre %}/notifications
+HTTP/2 200
+Last-Modified: Thu, 25 Oct 2012 15:16:27 GMT
+X-Poll-Interval: 60
+
+# Pass the Last-Modified header exactly
+$ curl -I {% data variables.product.api_url_pre %}/notifications
+$ -H "If-Modified-Since: Thu, 25 Oct 2012 15:16:27 GMT"
+> HTTP/2 304
+> X-Poll-Interval: 60
+```
+
+### 通知原因
+
+从通知 API 检索响应时，每个有效负载都有一个名为 `reason` 的键。 这些键对应于触发通知的事件。
+
+以下是收到通知的可能 `reason` 列表：
+
+| 原因名称 | 描述 |
+| ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `assign` | 您被分配到议题。 |
+| `作者` | 您创建了帖子。 |
+| `注释，评论` | 您评论了帖子。 |
+| `ci_activity` | 当 {% data variables.product.prodname_actions %} 工作流程运行被请求或完成时。 |
+| `邀请` | 您接受了参与仓库的邀请。 |
+| `manual` | 您订阅了帖子（通过议题或拉取请求） |
+| `提及` | 您在内容中被特别 **@提及**。 |
+| `review_requested` | 您或您所属的团队被请求审查拉取请求。{% ifversion fpt or ghec %}
+| `security_alert` | {% data variables.product.prodname_dotcom %} 在您的仓库中发现了[安全漏洞](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)。{% endif %}
+| `state_change` | 您更改了帖子主题（例如关闭议题或合并拉取请求）。 |
+| `subscribed` | 您在关注仓库。 |
+| `team_mention` | 您所属的团队被提及。 |
+
+请注意，`reason` 根据每个帖子而修改，如果在以后的通知中，`reason` 不同，其值可能会变更。
+
+例如，如果您是某个议题的作者，则有关该议题的后续通知中，其 `reason` 值为 `author`。 如果后来您在这个议题上被 **@提及**，则您此后收到的通知中，其 `reason` 值为 `mention`。 无论您此后是否被再次提及，`reason` 值将保持 `mention` 不变。
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/rest-reference/activity/starring.md b/translations/zh-CN/data/reusables/rest-reference/activity/starring.md
new file mode 100644
index 000000000000..004107b34606
--- /dev/null
+++ b/translations/zh-CN/data/reusables/rest-reference/activity/starring.md
@@ -0,0 +1,15 @@
+## 标星
+
+仓库标星是允许用户为仓库添加书签的功能。 显示在仓库旁边的星标表示大致的兴趣程度。 星标对通知或活动馈送没有影响。
+
+### 标星与 关注
+
+2012 年 8 月，我们[更改了 {% data variables.product.prodname_dotcom %} 上的关注方式](https://github.com/blog/1204-notifications-stars)。 许多 API 客户端应用程序可能在使用原始的“关注者”端点来访问此数据。 现在，您可以开始使用“星标”端点了（如下所述）。 更多信息请参阅[关注者 API 更改帖子](https://developer.github.com/changes/2012-09-05-watcher-api/)和“[仓库关注 API](/rest/reference/activity#watching)”。
+
+### 标星的自定义媒体类型
+
+标星 REST API 有一个支持的自定义媒体类型。 使用此自定义媒体类型时，您将收到带有 `starred_at` 时间戳属性的响应，该属性指示星标创建的时间。 该响应还有第二个属性，该属性包括在不使用自定义媒体类型时返回的资源。 包含资源的属性为 `user` 或 `repo`。
+
+ application/vnd.github.v3.star+json
+
+有关媒体类型的更多信息，请参阅“[自定义媒体类型](/rest/overview/media-types)”。
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/rest-reference/activity/watching.md b/translations/zh-CN/data/reusables/rest-reference/activity/watching.md
new file mode 100644
index 000000000000..f9912b100e28
--- /dev/null
+++ b/translations/zh-CN/data/reusables/rest-reference/activity/watching.md
@@ -0,0 +1,3 @@
+## 关注
+
+关注仓库会注册用户接收有关新讨论的通知以及用户活动馈送中的事件。 有关简单的仓库书签制作，请参阅“[仓库标星](/rest/reference/activity#starring)”。
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/rest-reference/apps/apps.md b/translations/zh-CN/data/reusables/rest-reference/apps/apps.md
new file mode 100644
index 000000000000..481a8892d21f
--- /dev/null
+++ b/translations/zh-CN/data/reusables/rest-reference/apps/apps.md
@@ -0,0 +1,9 @@
+{% data reusables.apps.general-apps-restrictions %}
+
+本页列出了验证为 GitHub 应用程序后可访问的端点。 更多信息请参阅“[验证为 GitHub 应用程序](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-a-github-app)”。
+
+验证为 GitHub 应用程序后，GitHub 应用程序 API 使您能够获取有关 GitHub 应用程序的高层次信息以及有关应用程序安装的特定信息。
+
+验证为 GitHub 应用程序后，您可以访问 REST API v3 端点。 这些端点带有“备注”部分，即“与 GitHub 应用程序结合使用”。 验证为用户后也可以访问这些端点。
+
+某些 REST API v3 端点需要验证为 GitHub 应用程序安装设施。 有关这些端点的列表，请参阅[安装设施](/rest/reference/apps#installations)。
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/rest-reference/apps/installations.md b/translations/zh-CN/data/reusables/rest-reference/apps/installations.md
new file mode 100644
index 000000000000..35e1614059f2
--- /dev/null
+++ b/translations/zh-CN/data/reusables/rest-reference/apps/installations.md
@@ -0,0 +1,5 @@
+## 安装设施
+
+安装设施 API 使您能够获取有关 GitHub 应用程序安装设施的信息并在这些安装设施中执行操作。 _安装设施_是指已安装该应用程序的任何用户或组织帐户。 有关如何验证为安装设施和限制访问特定仓库的信息，请参阅“[验证为安装设施](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation)”。
+
+要列出组织的所有 GitHub 应用程序安装设施，请参阅“[列出组织的应用程序安装设施](/rest/reference/orgs#list-app-installations-for-an-organization)”。
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/rest-reference/apps/marketplace.md b/translations/zh-CN/data/reusables/rest-reference/apps/marketplace.md
new file mode 100644
index 000000000000..1aae73d87ff2
--- /dev/null
+++ b/translations/zh-CN/data/reusables/rest-reference/apps/marketplace.md
@@ -0,0 +1,13 @@
+## Marketplace
+
+For more information about {% data variables.product.prodname_marketplace %}, see "[GitHub Marketplace](/marketplace/)."
+
+The {% data variables.product.prodname_marketplace %} API allows you to see which customers are using a pricing plan, see a customer's purchases, and see if an account has an active subscription.
+
+### Testing with stubbed endpoints
+
+This API includes endpoints that allow you to [test your {% data variables.product.prodname_github_app %}](/marketplace/integrating-with-the-github-marketplace-api/testing-github-marketplace-apps/) with **stubbed data**. Stubbed data is hard-coded, fake data that will not change based on actual subscriptions.
+
+To test with stubbed data, use a stubbed endpoint in place of its production counterpart. This allows you to test whether API logic succeeds before listing {% data variables.product.prodname_github_apps %} on {% data variables.product.prodname_marketplace %}.
+
+Be sure to replace stubbed endpoints with production endpoints before deploying your {% data variables.product.prodname_github_app %}.
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/rest-reference/apps/oauth-applications.md b/translations/zh-CN/data/reusables/rest-reference/apps/oauth-applications.md
new file mode 100644
index 000000000000..b3925cf335d4
--- /dev/null
+++ b/translations/zh-CN/data/reusables/rest-reference/apps/oauth-applications.md
@@ -0,0 +1,3 @@
+## OAuth 应用程序 API
+
+您可以使用此 API 来管理 OAuth 应用程序用于访问人们在 {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} 上的帐户的 OAuth 令牌。
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/rest-reference/apps/webhooks.md b/translations/zh-CN/data/reusables/rest-reference/apps/webhooks.md
new file mode 100644
index 000000000000..e0d392c02a86
--- /dev/null
+++ b/translations/zh-CN/data/reusables/rest-reference/apps/webhooks.md
@@ -0,0 +1,3 @@
+## Web 挂钩
+
+A {% data variables.product.prodname_github_app %}'s webhook allows you to receive HTTP `POST` payloads whenever certain events happen for an app. {% data reusables.webhooks.webhooks-rest-api-links %}
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/rest-reference/billing/billing.md b/translations/zh-CN/data/reusables/rest-reference/billing/billing.md
new file mode 100644
index 000000000000..01eb32258814
--- /dev/null
+++ b/translations/zh-CN/data/reusables/rest-reference/billing/billing.md
@@ -0,0 +1 @@
+您可以获取企业的帐单信息。 更多信息请参阅“[{% data variables.product.prodname_dotcom %} Enterprise 管理](/rest/reference/enterprise-admin#billing)”REST API。
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/rest-reference/branches/branch-protection.md b/translations/zh-CN/data/reusables/rest-reference/branches/branch-protection.md
new file mode 100644
index 000000000000..f3817c570b33
--- /dev/null
+++ b/translations/zh-CN/data/reusables/rest-reference/branches/branch-protection.md
@@ -0,0 +1 @@
+## 受保护分支
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/rest-reference/checks/checks.md b/translations/zh-CN/data/reusables/rest-reference/checks/checks.md
new file mode 100644
index 000000000000..55d93f1b22e4
--- /dev/null
+++ b/translations/zh-CN/data/reusables/rest-reference/checks/checks.md
@@ -0,0 +1 @@
+您可以创建应用程序以执行持续集成 、代码分析或代码扫描服务，并提供有关提交的详细反馈。 更多信息请参阅“[检查 API 入门指南](/rest/guides/getting-started-with-the-checks-api)”和“[使用检查 API 创建 CI 测试](/apps/quickstart-guides/creating-ci-tests-with-the-checks-api/)”。
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/rest-reference/checks/runs.md b/translations/zh-CN/data/reusables/rest-reference/checks/runs.md
new file mode 100644
index 000000000000..5d251205a4d0
--- /dev/null
+++ b/translations/zh-CN/data/reusables/rest-reference/checks/runs.md
@@ -0,0 +1 @@
+## 检查运行
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/rest-reference/checks/suites.md b/translations/zh-CN/data/reusables/rest-reference/checks/suites.md
new file mode 100644
index 000000000000..10c4e220c547
--- /dev/null
+++ b/translations/zh-CN/data/reusables/rest-reference/checks/suites.md
@@ -0,0 +1,7 @@
+## 检查套件
+
+{% note %}
+
+ **注：**GitHub 应用程序针对每个提交 SHA 只接收一个 [`check_suite`](/webhooks/event-payloads/#check_suite) 事件，即使您将提交 SHA 推送到多个分支。 要了解提交 SHA 何时推送到分支，您可以订阅分支 [`create`](/webhooks/event-payloads/#create) 事件。
+
+{% endnote %}
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/rest-reference/code-scanning/code-scanning.md b/translations/zh-CN/data/reusables/rest-reference/code-scanning/code-scanning.md
new file mode 100644
index 000000000000..d1cb1b1c31df
--- /dev/null
+++ b/translations/zh-CN/data/reusables/rest-reference/code-scanning/code-scanning.md
@@ -0,0 +1,15 @@
+{% data reusables.code-scanning.beta %}
+
+{% data variables.product.prodname_code_scanning %} API 可让您从仓库检索和更新 {% data variables.product.prodname_code_scanning %} 警报。 您可以使用端点为组织中的 {% data variables.product.prodname_code_scanning %} 警报创建自动报告，或上传使用离线 {% data variables.product.prodname_code_scanning %} 工具生成的分析结果。 更多信息请参阅“[查找代码中的安全漏洞和错误](/github/finding-security-vulnerabilities-and-errors-in-your-code)”。
+
+{% ifversion fpt or ghes > 3.0 or ghae or ghec %}
+### {% data variables.product.prodname_code_scanning %} 的自定义媒体类型
+
+{% data variables.product.prodname_code_scanning %} REST API 有一种支持的自定义媒体类型。
+
+ application/sarif+json
+
+您可以将此请求与发送到 `/analyses/{analysis_id}` 端点的 `GET` 请求一起使用。 有关此操作的更多信息，请参阅“[获取仓库的 {% data variables.product.prodname_code_scanning %} 分析](#get-a-code-scanning-analysis-for-a-repository)”。 当您使用此媒体类型进行此操作时，响应包括上传用于指定分析的实际数据的子集，而不是使用默认媒体类型时返回的分析摘要。 响应还包括其他数据，如 `github/alertNumber` 和 `github/alertUrl` 属性。 数据格式为 [SARIF 版本 2.1.0](https://docs.oasis-open.org/sarif/sarif/v2.1.0/cs01/sarif-v2.1.0-cs01.html)。
+
+更多信息请参阅“[媒体类型](/rest/overview/media-types)”。
+{% endif %}
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/rest-reference/codes-of-conduct/codes-of-conduct.md b/translations/zh-CN/data/reusables/rest-reference/codes-of-conduct/codes-of-conduct.md
new file mode 100644
index 000000000000..e5b03b383954
--- /dev/null
+++ b/translations/zh-CN/data/reusables/rest-reference/codes-of-conduct/codes-of-conduct.md
@@ -0,0 +1,2 @@
+
+您可以使用行为准则 API 检索有关仓库行为准则的信息。 要获取仓库的行为准则，请使用“[获取仓库](/rest/reference/repos#get-a-repository)”端点。
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/rest-reference/codespaces/codespaces.md b/translations/zh-CN/data/reusables/rest-reference/codespaces/codespaces.md
new file mode 100644
index 000000000000..d85570d3ac28
--- /dev/null
+++ b/translations/zh-CN/data/reusables/rest-reference/codespaces/codespaces.md
@@ -0,0 +1,3 @@
+{% data reusables.codespaces.codespaces-api-beta-note %}
+
+{% data variables.product.prodname_codespaces %} API 允许您使用 REST API 来管理 {% data variables.product.prodname_codespaces %}。 This API is available for authenticated users and OAuth Apps, but not GitHub Apps. 更多信息请参阅“[{% data variables.product.prodname_codespaces %}](/codespaces)”。
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/rest-reference/codespaces/machines.md b/translations/zh-CN/data/reusables/rest-reference/codespaces/machines.md
new file mode 100644
index 000000000000..e8bc5519dade
--- /dev/null
+++ b/translations/zh-CN/data/reusables/rest-reference/codespaces/machines.md
@@ -0,0 +1,4 @@
+## Machines
+The Machines API allows a user to determine which machine types are available to create a codespace, either on a given repository or as an authenticated user. For more information, see "[About machine types](/codespaces/developing-in-codespaces/changing-the-machine-type-for-your-codespace#about-machine-types)."
+
+You can also use this information when changing the machine of an existing codespace by updating its `machine` property. The machine update will take place the next time the codespace is restarted. For more information, see "[Changing the machine type for your codespace](/codespaces/developing-in-codespaces/changing-the-machine-type-for-your-codespace)."
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/rest-reference/codespaces/secrets.md b/translations/zh-CN/data/reusables/rest-reference/codespaces/secrets.md
new file mode 100644
index 000000000000..19d4fd3fff2e
--- /dev/null
+++ b/translations/zh-CN/data/reusables/rest-reference/codespaces/secrets.md
@@ -0,0 +1,2 @@
+## 密码
+The Secrets API allows a user to create, list, and delete secrets (such as access tokens for cloud services) as well as assign secrets to repositories that the user has access to. These secrets are made available to the codespace at runtime. For more information, see "[Managing encrypted secrets for your codespaces](/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces)."
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/rest-reference/collaborators/invitations.md b/translations/zh-CN/data/reusables/rest-reference/collaborators/invitations.md
new file mode 100644
index 000000000000..49a5931f4efd
--- /dev/null
+++ b/translations/zh-CN/data/reusables/rest-reference/collaborators/invitations.md
@@ -0,0 +1,9 @@
+## 邀请
+
+仓库邀请 API 允许用户或外部服务邀请其他用户参与仓库协作。 受邀用户（或代表受邀用户的外部服务）可以选择接受或拒绝邀请。
+
+请注意，`repo:invite` [OAuth 作用域](/developers/apps/scopes-for-oauth-apps)授予对邀请的定向访问权限，但**不**授予对仓库代码的访问权限，而 `repo` 作用域同时授予对代码和邀请的权限。
+
+### 邀请用户参与仓库
+
+使用 API 端点来添加协作者。 更多信息请参阅“[添加仓库协作者](/rest/reference/collaborators#add-a-repository-collaborator)”。
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/rest-reference/commits/comments.md b/translations/zh-CN/data/reusables/rest-reference/commits/comments.md
new file mode 100644
index 000000000000..2e2ab9006c57
--- /dev/null
+++ b/translations/zh-CN/data/reusables/rest-reference/commits/comments.md
@@ -0,0 +1,12 @@
+## 提交注释
+
+### 提交评论的自定义媒体类型
+
+以下是提交评论支持的媒体类型。 您可以在[此处](/rest/overview/media-types)阅读有关 API 中媒体类型使用情况的更多信息。
+
+ application/vnd.github-commitcomment.raw+json
+ application/vnd.github-commitcomment.text+json
+ application/vnd.github-commitcomment.html+json
+ application/vnd.github-commitcomment.full+json
+
+更多信息请参阅“[自定义媒体类型](/rest/overview/media-types)”。
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/rest-reference/commits/statuses.md b/translations/zh-CN/data/reusables/rest-reference/commits/statuses.md
new file mode 100644
index 000000000000..067c92587990
--- /dev/null
+++ b/translations/zh-CN/data/reusables/rest-reference/commits/statuses.md
@@ -0,0 +1,13 @@
+## 提交状态
+
+状态 API 允许外部服务将提交标记为 `error`、`failure`、`pending` 或 `success` 状态，然后将其反映在涉及这些提交的拉取请求中。
+
+状态还可以包含可选的 `description` 和 `target_url`，强烈建议使用它们，因为它们使状态在 GitHub UI 中更有用。
+
+一种常见用例是持续集成服务使用状态将提交标记为构建成功或失败。 `target_url` 是构建输出的完整 URL，`description` 是关于构建过程中所发生情况的高级摘要。
+
+状态可以包括 `context` 以指示提供该状态的服务是什么。 例如，您可以让持续集成服务推送上下文为 `ci` 的状态，让安全审核工具推送上下文为 `security` 的状态。 然后，您可以使用[获取特定引用的组合状态](/rest/reference/commits#get-the-combined-status-for-a-specific-reference)来检索提交的整个状态。
+
+请注意，`repo:status` [OAuth 作用域](/developers/apps/scopes-for-oauth-apps)授予对状态的定向访问权限，但**不**授予对仓库代码的访问权限，而 `repo` 作用域同时授予对代码和状态的权限。
+
+如果您正在开发 GitHub 应用程序，希望提供有关外部服务的更多信息，则可能需要使用[检查 API](/rest/reference/checks)。
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/rest-reference/dependabot/dependabot.md b/translations/zh-CN/data/reusables/rest-reference/dependabot/dependabot.md
new file mode 100644
index 000000000000..85c08d3787cf
--- /dev/null
+++ b/translations/zh-CN/data/reusables/rest-reference/dependabot/dependabot.md
@@ -0,0 +1,3 @@
+The {% data variables.product.prodname_dependabot %} Secrets API lets you create, update, delete, and retrieve information about encrypted secrets. {% data reusables.actions.about-secrets %} For more information, see "[Managing encrypted secrets for Dependabot](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-encrypted-secrets-for-dependabot)."
+
+{% data reusables.actions.actions-authentication %} {% data variables.product.prodname_github_apps %} must have the `dependabot_secrets` permission to use this API. 经过身份验证的用户必须对仓库具有协作者权限才可创建、更新或读取密码。
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/rest-reference/deployments/deployments.md b/translations/zh-CN/data/reusables/rest-reference/deployments/deployments.md
new file mode 100644
index 000000000000..8a43e8024ea0
--- /dev/null
+++ b/translations/zh-CN/data/reusables/rest-reference/deployments/deployments.md
@@ -0,0 +1,46 @@
+部署是部署特定引用（分支、SHA、标记）的请求。 GitHub 分发一个 [`deployment` 事件](/developers/webhooks-and-events/webhook-events-and-payloads#deployment)，使外部服务可以在创建新部署时侦听并采取行动。 部署使开发者和组织能够围绕部署构建松散耦合的工具，而不必担心交付不同类型的应用程序（例如 Web 和本地应用程序）的实现细节。
+
+部署状态允许外部服务将部署标记为 `error`、`failure`、`pending`、`in_progress`、`queued` 或 `success` 状态，以供侦听 [`deployment_status` 事件](/developers/webhooks-and-events/webhook-events-and-payloads#deployment_status)的系统使用。
+
+部署状态还可以包含可选的 `description` 和 `log_url`，强烈建议使用它们，因为它们使部署状态更有用。 `log_url` 是部署输出的完整 URL，`description` 是关于部署过程中所发生情况的高级摘要。
+
+在创建新的部署和部署状态时，GitHub 将分发 `deployment` 和 `deployment_status` 事件。 这些事件允许第三方集成接收对部署请求的响应，并在取得进展时更新部署的状态。
+
+下面是一个说明这些交互的工作方式的简单序列图。
+
+```
++---------+ +--------+ +-----------+ +-------------+
+| Tooling | | GitHub | | 3rd Party | | Your Server |
++---------+ +--------+ +-----------+ +-------------+
+ | | | |
+ | Create Deployment | | |
+ |--------------------->| | |
+ | | | |
+ | Deployment Created | | |
+ |<---------------------| | |
+ | | | |
+ | | Deployment Event | |
+ | |---------------------->| |
+ | | | SSH+Deploys |
+ | | |-------------------->|
+ | | | |
+ | | Deployment Status | |
+ | |<----------------------| |
+ | | | |
+ | | | Deploy Completed |
+ | | |<--------------------|
+ | | | |
+ | | Deployment Status | |
+ | |<----------------------| |
+ | | | |
+```
+
+请记住，GitHub 从未真正访问过您的服务器。 与部署事件的交互取决于第三方集成。 多个系统可以侦听部署事件，由其中每个系统来决定它们是否负责将代码推送到服务器、构建本地代码等。
+
+请注意，`repo_deployment` [OAuth 作用域](/developers/apps/scopes-for-oauth-apps)授予对部署和部署状态的定向访问权限，但**不**授予对仓库代码的访问权限，而 {% ifversion not ghae %}`public_repo` 和{% endif %}`repo` 作用域还授予对代码的权限。
+
+### 非活动部署
+
+当您将部署状态设置为 `success` 时，同一仓库中所有先前的非瞬态、非生产环境部署将变成 `inactive`。 为避免这种情况，您可以在创建部署状态时将 `auto_inactive` 设置为 `false`。
+
+您可以通过将 `state` 设为 `inactive` 来表示某个瞬态环境不再存在。 将 `state` 设为 `inactive`，表示部署在 {% data variables.product.prodname_dotcom %} 中 `destroyed` 并删除对它的访问权限。
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/rest-reference/deployments/environments.md b/translations/zh-CN/data/reusables/rest-reference/deployments/environments.md
new file mode 100644
index 000000000000..71659dfb82fe
--- /dev/null
+++ b/translations/zh-CN/data/reusables/rest-reference/deployments/environments.md
@@ -0,0 +1,5 @@
+## 环境
+
+环境 API 允许您创建、配置和删除环境。 有关环境的更多信息，请参阅“[使用环境进行部署](/actions/deployment/using-environments-for-deployment)”。 要管理环境密码，请参阅“[密码](/rest/reference/actions#secrets)”。
+
+{% data reusables.gated-features.environments %}
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/rest-reference/deployments/keys.md b/translations/zh-CN/data/reusables/rest-reference/deployments/keys.md
new file mode 100644
index 000000000000..7ae7efa109c1
--- /dev/null
+++ b/translations/zh-CN/data/reusables/rest-reference/deployments/keys.md
@@ -0,0 +1,5 @@
+## 部署密钥
+
+{% data reusables.repositories.deploy-keys %}
+
+部署密钥可以使用以下 API 端点进行设置，也可以使用 GitHub 进行设置。 要了解如何在 GitHub 中设置部署密钥，请参阅“[管理部署密钥](/developers/overview/managing-deploy-keys)”。
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/rest-reference/deployments/statuses.md b/translations/zh-CN/data/reusables/rest-reference/deployments/statuses.md
new file mode 100644
index 000000000000..107f9155309f
--- /dev/null
+++ b/translations/zh-CN/data/reusables/rest-reference/deployments/statuses.md
@@ -0,0 +1 @@
+## 部署状态
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/rest-reference/enterprise-admin/admin-stats.md b/translations/zh-CN/data/reusables/rest-reference/enterprise-admin/admin-stats.md
new file mode 100644
index 000000000000..94fd14dc73eb
--- /dev/null
+++ b/translations/zh-CN/data/reusables/rest-reference/enterprise-admin/admin-stats.md
@@ -0,0 +1,3 @@
+## 管理统计
+
+管理统计 API 提供有关安装设施的各种指标。 *它只适用于[经过身份验证的](/rest/overview/resources-in-the-rest-api#authentication)站点管理员。*普通用户尝试访问它时会收到 `404` 响应。
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/rest-reference/enterprise-admin/announcements.md b/translations/zh-CN/data/reusables/rest-reference/enterprise-admin/announcements.md
new file mode 100644
index 000000000000..b956d0e32a68
--- /dev/null
+++ b/translations/zh-CN/data/reusables/rest-reference/enterprise-admin/announcements.md
@@ -0,0 +1,3 @@
+## 公告
+
+公告 API 允许您管理企业中的全局公告横幅。 更多信息请参阅“[自定义企业的用户消息](/admin/user-management/customizing-user-messages-for-your-enterprise#creating-a-global-announcement-banner)”。
diff --git a/translations/zh-CN/data/reusables/rest-reference/enterprise-admin/audit-log.md b/translations/zh-CN/data/reusables/rest-reference/enterprise-admin/audit-log.md
new file mode 100644
index 000000000000..3948a31a4eca
--- /dev/null
+++ b/translations/zh-CN/data/reusables/rest-reference/enterprise-admin/audit-log.md
@@ -0,0 +1 @@
+## 审核日志
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/rest-reference/enterprise-admin/billing.md b/translations/zh-CN/data/reusables/rest-reference/enterprise-admin/billing.md
new file mode 100644
index 000000000000..8be8ef8795c1
--- /dev/null
+++ b/translations/zh-CN/data/reusables/rest-reference/enterprise-admin/billing.md
@@ -0,0 +1 @@
+## 计费
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/rest-reference/enterprise-admin/enterprise-admin.md b/translations/zh-CN/data/reusables/rest-reference/enterprise-admin/enterprise-admin.md
new file mode 100644
index 000000000000..129d76eb3b15
--- /dev/null
+++ b/translations/zh-CN/data/reusables/rest-reference/enterprise-admin/enterprise-admin.md
@@ -0,0 +1,44 @@
+{% ifversion fpt or ghec %}
+
+{% note %}
+
+**注：** 本文章适用于 {% data variables.product.prodname_ghe_cloud %}。 要查看 {% data variables.product.prodname_ghe_managed %} 或 {% data variables.product.prodname_ghe_server %} 版本，请使用 **{% data ui.pages.article_version %}** 下拉菜单。
+
+{% endnote %}
+
+{% endif %}
+
+### 端点 URL
+
+REST API 端点{% ifversion ghes %}— [管理控制台](#management-console) API 端点除外—{% endif %} 是以下 URL 的前缀：
+
+```shell
+{% data variables.product.api_url_pre %}
+```
+
+{% ifversion fpt or ghec %}
+当端点包含 `{enterprise}` 时，将 `{enterprise}` 替换为企业帐户的句柄，该句柄包含在企业设置的 URL 中。 例如，如果您的企业帐户位于 `https://github.com/enterprises/octo-enterprise`，则将 `{enterprise}` 替换为 `octo-enterprises`。
+{% endif %}
+
+{% ifversion ghes %}
+[管理控制台](#management-console) API 端点是唯一以主机名为前缀的端点：
+
+```shell
+http(s)://hostname/
+```
+{% endif %}
+{% ifversion ghae or ghes %}
+### 身份验证
+
+{% data variables.product.product_name %} 安装设施的 API 端点接受与 GitHub.com [相同的身份验证方法](/rest/overview/resources-in-the-rest-api#authentication)。 您可以使用 **[OAuth 令牌](/apps/building-integrations/setting-up-and-registering-oauth-apps/)**{% ifversion ghes %}（可使用[授权 API](/rest/reference/oauth-authorizations#create-a-new-authorization) 创建）{% endif %}或**[基本身份验证](/rest/overview/resources-in-the-rest-api#basic-authentication)**来验证自己。 {% ifversion ghes %} OAuth 令牌用于企业特定的端点时必须具有 `site_admin` [OAuth 作用域](/developers/apps/scopes-for-oauth-apps#available-scopes)。{% endif %}
+
+企业管理 API 端点只有经过身份验证的 {% data variables.product.product_name %} 站点管理员可以访问{% ifversion ghes %}，但[管理控制台](#management-console) API 例外，它需要[管理控制台密码](/enterprise/admin/articles/accessing-the-management-console/){% endif %}。
+
+{% endif %}
+
+{% ifversion ghae or ghes %}
+### 版本信息
+
+每个 API 的响应标头中都会返回企业的当前版本：`X-GitHub-Enterprise-Version: {{currentVersion}}.0` 您也可以通过调用[元端点](/rest/reference/meta/)来读取当前版本。
+
+{% endif %}
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/rest-reference/enterprise-admin/global-webhooks.md b/translations/zh-CN/data/reusables/rest-reference/enterprise-admin/global-webhooks.md
new file mode 100644
index 000000000000..e9ede7370be9
--- /dev/null
+++ b/translations/zh-CN/data/reusables/rest-reference/enterprise-admin/global-webhooks.md
@@ -0,0 +1,5 @@
+## 全局 web 挂钩
+
+全局 web 挂钩安装在企业上。 您可以使用全局 web 挂钩来自动监视、响应或实施针对企业上的用户、组织、团队和仓库的规则。 全局 web 挂钩可以订阅[组织](/developers/webhooks-and-events/webhook-events-and-payloads#organization)、[用户](/developers/webhooks-and-events/webhook-events-and-payloads#user)、[仓库](/developers/webhooks-and-events/webhook-events-and-payloads#repository)、[团队](/developers/webhooks-and-events/webhook-events-and-payloads#team)、[成员](/developers/webhooks-and-events/webhook-events-and-payloads#member)、[成员身份](/developers/webhooks-and-events/webhook-events-and-payloads#membership)、[复刻](/developers/webhooks-and-events/webhook-events-and-payloads#fork)和 [ping](/developers/webhooks-and-events/about-webhooks#ping-event) 事件类型。
+
+*此 API 只适用于[经过身份验证的](/rest/overview/resources-in-the-rest-api#authentication)站点管理员。*普通用户尝试访问它时会收到 `404` 响应。 要了解如何配置全局 web 挂钩，请参阅[关于全局 web 挂钩](/enterprise/admin/user-management/about-global-webhooks)。
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/rest-reference/enterprise-admin/ldap.md b/translations/zh-CN/data/reusables/rest-reference/enterprise-admin/ldap.md
new file mode 100644
index 000000000000..adae6c4e793a
--- /dev/null
+++ b/translations/zh-CN/data/reusables/rest-reference/enterprise-admin/ldap.md
@@ -0,0 +1,5 @@
+## LDAP
+
+您可以使用 LDAP API 来更新 {% data variables.product.product_name %} 用户或团队与其关联的 LDAP 条目之间的帐户关系，或者排队新同步。
+
+通过 LDAP 映射端点，您可以更新用户或团队所映射的识别名称 (DN) 。 请注意，LDAP 端点通常只在您的 {% data variables.product.product_name %} 设备[启用了 LDAP 同步](/enterprise/admin/authentication/using-ldap)时才有效。 启用了 LDAP 后，即使禁用 LDAP 同步，也可以使用[更新用户的 LDAP 映射](#update-ldap-mapping-for-a-user)端点。
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/rest-reference/enterprise-admin/license.md b/translations/zh-CN/data/reusables/rest-reference/enterprise-admin/license.md
new file mode 100644
index 000000000000..3e236e74c7ab
--- /dev/null
+++ b/translations/zh-CN/data/reusables/rest-reference/enterprise-admin/license.md
@@ -0,0 +1,3 @@
+## 许可
+
+许可 API 提供有关企业许可的信息。 *它只适用于[经过身份验证的](/rest/overview/resources-in-the-rest-api#authentication)站点管理员。*普通用户尝试访问它时会收到 `404` 响应。
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/rest-reference/enterprise-admin/management-console.md b/translations/zh-CN/data/reusables/rest-reference/enterprise-admin/management-console.md
new file mode 100644
index 000000000000..6d6afed062e0
--- /dev/null
+++ b/translations/zh-CN/data/reusables/rest-reference/enterprise-admin/management-console.md
@@ -0,0 +1,29 @@
+## 管理控制台
+
+管理控制台 API 可帮助您管理 {% data variables.product.product_name %} 安装设施。
+
+{% tip %}
+
+在对管理控制台进行 API 调用时，必须明确设置端口号。 如果在企业上启用了 TLS，则端口号为 `8443`；否则，端口号为 `8080`。
+
+如果您不想提供端口号，则需要将工具配置为自动遵循重定向。
+
+使用 `curl` 时，您可能还需要添加 [`-k` 标志](http://curl.haxx.se/docs/manpage.html#-k)，因为 {% data variables.product.product_name %} 在您[添加自己的 TLS 证书](/enterprise/admin/guides/installation/configuring-tls/)之前会使用自签名证书。
+
+{% endtip %}
+
+### 身份验证
+
+您需要将[管理控制台密码](/enterprise/admin/articles/accessing-the-management-console/)作为身份验证令牌传递给除 [`/setup/api/start`](#create-a-github-enterprise-server-license) 之外的每个管理控制台 API 端点。
+
+使用 `api_key` 参数在每个请求中发送此令牌。 例如：
+
+```shell
+$ curl -L 'https://hostname:admin_port/setup/api?api_key=your-amazing-password'
+```
+
+还可以使用标准 HTTP 身份验证发送此令牌。 例如：
+
+```shell
+$ curl -L -u "api_key:your-amazing-password" 'https://hostname:admin_port/setup/api'
+```
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/rest-reference/enterprise-admin/org-pre-receive-hooks.md b/translations/zh-CN/data/reusables/rest-reference/enterprise-admin/org-pre-receive-hooks.md
new file mode 100644
index 000000000000..1c645dd04fc5
--- /dev/null
+++ b/translations/zh-CN/data/reusables/rest-reference/enterprise-admin/org-pre-receive-hooks.md
@@ -0,0 +1,16 @@
+## 组织预接收挂钩
+
+组织预接收挂钩 API 允许您查看和修改组织可用的预接收挂钩的实施。
+
+### 对象属性
+
+| 名称 | 类型 | 描述 |
+| -------------------------------- | ----- | ------------ |
+| `name` | `字符串` | 挂钩的名称。 |
+| `enforcement` | `字符串` | 此仓库中挂钩的实施状态。 |
+| `allow_downstream_configuration` | `布尔值` | 仓库是否可以覆盖实施。 |
+| `configuration_url` | `字符串` | 设置实施的端点 URL。 |
+
+*enforcement* 的可能值包括 `enabled`、`disabled` 和 `testing`。 `disabled` 表示预接收挂钩不会运行。 `enabled` 表示它将运行并拒绝会导致非零状态的任何推送。 `testing` 表示脚本将运行，但不会导致任何推送被拒绝。
+
+`configuration_url` 可能是此端点或此挂钩的全局配置的链接。 只有站点管理员才能访问全局配置。
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/rest-reference/enterprise-admin/orgs.md b/translations/zh-CN/data/reusables/rest-reference/enterprise-admin/orgs.md
new file mode 100644
index 000000000000..25935bc5c8dd
--- /dev/null
+++ b/translations/zh-CN/data/reusables/rest-reference/enterprise-admin/orgs.md
@@ -0,0 +1,3 @@
+## 组织
+
+组织管理 API 允许您在企业上创建组织。 *它只适用于[经过身份验证的](/rest/overview/resources-in-the-rest-api#authentication)站点管理员。*普通用户尝试访问它时会收到 `404` 响应。
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/rest-reference/enterprise-admin/pre-receive-environments.md b/translations/zh-CN/data/reusables/rest-reference/enterprise-admin/pre-receive-environments.md
new file mode 100644
index 000000000000..c7314273a844
--- /dev/null
+++ b/translations/zh-CN/data/reusables/rest-reference/enterprise-admin/pre-receive-environments.md
@@ -0,0 +1,25 @@
+## 预接收环境
+
+预接收环境 API 允许您创建、列出、更新和删除预接收挂钩的环境。 *它只适用于[经过身份验证的](/rest/overview/resources-in-the-rest-api#authentication)站点管理员。*普通用户尝试访问它时会收到 `404` 响应。
+
+### 对象属性
+
+#### 预接收环境
+
+| 名称 | 类型 | 描述 |
+| --------------------- | ----- | ------------------------------------------------------- |
+| `name` | `字符串` | UI 中显示的环境名称。 |
+| `image_url` | `字符串` | 将要下载并解压缩的 tarball 的 URL。 |
+| `default_environment` | `布尔值` | 这是否是 {% data variables.product.product_name %} 附带的默认环境。 |
+| `download` | `对象` | 此环境的下载状态。 |
+| `hooks_count` | `整数` | 使用此环境的预接收挂钩数量。 |
+
+#### 预接收环境下载
+
+| 名称 | 类型 | 描述 |
+| --------------- | ----- | ------------- |
+| `state` | `字符串` | 最近下载的状态。 |
+| `downloaded_at` | `字符串` | 最近下载开始的时间。 |
+| `message` | `字符串` | 在失败时生成任何错误消息。 |
+
+`state` 的可能值包括 `not_started`、`in_progress`、`success`、`failed`。
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/rest-reference/enterprise-admin/pre-receive-hooks.md b/translations/zh-CN/data/reusables/rest-reference/enterprise-admin/pre-receive-hooks.md
new file mode 100644
index 000000000000..d24b3c05ed15
--- /dev/null
+++ b/translations/zh-CN/data/reusables/rest-reference/enterprise-admin/pre-receive-hooks.md
@@ -0,0 +1,18 @@
+## 预接收挂钩
+
+预接收挂钩 API 允许您创建、列出、更新和删除预接收挂钩。 *它只适用于[经过身份验证的](/rest/overview/resources-in-the-rest-api#authentication)站点管理员。*普通用户尝试访问它时会收到 `404` 响应。
+
+### 对象属性
+
+#### 预接收挂钩
+
+| 名称 | 类型 | 描述 |
+| -------------------------------- | ----- | ------------------ |
+| `name` | `字符串` | 挂钩的名称。 |
+| `script` | `字符串` | 挂钩运行的脚本。 |
+| `script_repository` | `对象` | 保存脚本的 GitHub 仓库。 |
+| `environment` | `对象` | 执行脚本的预接收环境。 |
+| `enforcement` | `字符串` | 此挂钩的实施状态。 |
+| `allow_downstream_configuration` | `布尔值` | 是否可以在组织或仓库级别上覆盖实施。 |
+
+*enforcement* 的可能值包括 `enabled`、`disabled` 和 `testing`。 `disabled` 表示预接收挂钩不会运行。 `enabled` 表示它将运行并拒绝会导致非零状态的任何推送。 `testing` 表示脚本将运行，但不会导致任何推送被拒绝。
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/rest-reference/enterprise-admin/repo-pre-receive-hooks.md b/translations/zh-CN/data/reusables/rest-reference/enterprise-admin/repo-pre-receive-hooks.md
new file mode 100644
index 000000000000..dda07f63b115
--- /dev/null
+++ b/translations/zh-CN/data/reusables/rest-reference/enterprise-admin/repo-pre-receive-hooks.md
@@ -0,0 +1,15 @@
+## 仓库预接收挂钩
+
+仓库预接收挂钩 API 允许您查看和修改仓库可用的预接收挂钩的实施。
+
+### 对象属性
+
+| 名称 | 类型 | 描述 |
+| ------------------- | ----- | ------------ |
+| `name` | `字符串` | 挂钩的名称。 |
+| `enforcement` | `字符串` | 此仓库中挂钩的实施状态。 |
+| `configuration_url` | `字符串` | 设置实施的端点 URL。 |
+
+*enforcement* 的可能值包括 `enabled`、`disabled` 和 `testing`。 `disabled` 表示预接收挂钩不会运行。 `enabled` 表示它将运行并拒绝会导致非零状态的任何推送。 `testing` 表示脚本将运行，但不会导致任何推送被拒绝。
+
+`configuration_url` 可能是此仓库、其组织所有者或全局配置的链接。 `configuration_url` 端点的访问授权在所有者或站点管理员级别确定。
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/rest-reference/enterprise-admin/users.md b/translations/zh-CN/data/reusables/rest-reference/enterprise-admin/users.md
new file mode 100644
index 000000000000..627d12b7fc11
--- /dev/null
+++ b/translations/zh-CN/data/reusables/rest-reference/enterprise-admin/users.md
@@ -0,0 +1,3 @@
+## 用户
+
+用户管理 API 允许您暂停{% ifversion ghes %}、取消暂停、升级和降级{% endif %}{% ifversion ghae %} 以及取消暂停{% endif %} 企业上的用户。 *它只适用于[经过身份验证的](/rest/overview/resources-in-the-rest-api#authentication)站点管理员。*普通用户尝试访问它时会收到 `403` 响应。
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/rest-reference/gists/comments.md b/translations/zh-CN/data/reusables/rest-reference/gists/comments.md
new file mode 100644
index 000000000000..c7698dc4025a
--- /dev/null
+++ b/translations/zh-CN/data/reusables/rest-reference/gists/comments.md
@@ -0,0 +1,10 @@
+## 评论
+
+### Gist 评论的自定义媒体类型
+
+以下是 Gist 评论支持的媒体类型。
+
+ application/vnd.github.VERSION.raw
+ application/vnd.github.VERSION.base64
+
+有关媒体类型的更多信息，请参阅“[自定义媒体类型](/rest/overview/media-types)”。
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/rest-reference/gists/gists.md b/translations/zh-CN/data/reusables/rest-reference/gists/gists.md
new file mode 100644
index 000000000000..f0f2c035e48a
--- /dev/null
+++ b/translations/zh-CN/data/reusables/rest-reference/gists/gists.md
@@ -0,0 +1,22 @@
+### 身份验证
+
+您可以匿名读取公开 Gist {% ifversion ghae or ghes %}并为没有令牌的匿名用户创建它们。{% else %}，但是您必须登录到 GitHub 才能创建 Gist。{% endif %} 要代表用户读取或写入 Gist，您需要 Gist OAuth 作用域和令牌。 更多信息请参阅“[OAuth 应用程序的作用域](/developers/apps/scopes-for-oauth-apps)”。
+
+
+
+### 截断
+
+Gist API 为 Gist 中的每个文件提供最多一兆字节的内容。 通过 API 返回的每个 Gist 文件都有一个名为 `truncated` 的键。 如果 `truncated` 为 `true`，则说明文件太大，`content` 中只返回部分内容。
+
+如果您需要文件的全部内容，您可以向 `raw_url` 指定的 URL 提出 `GET` 请求。 请注意，对于超过十兆字节的文件，您需要通过 `git_pull_url` 提供的 URL 克隆 Gist。
+
+除了特定文件的内容被截断外，如果文件总数超过 300 个，则整个文件列表也可能被截断。 如果顶层 `truncated` 键为 `true`，则说明文件列表中只返回了前 300 个文件。 如果需要获取 Gist 的所有文件，您需要通过 `git_pull_url` 提供的 URL 克隆 Gist。
+
+### Gist 的自定义媒体类型
+
+以下是获取 Gist 内容所支持的媒体类型。
+
+ application/vnd.github.VERSION.raw
+ application/vnd.github.VERSION.base64
+
+更多信息请参阅“[媒体类型](/rest/overview/media-types)”。
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/rest-reference/git/blobs.md b/translations/zh-CN/data/reusables/rest-reference/git/blobs.md
new file mode 100644
index 000000000000..26a1b4893efd
--- /dev/null
+++ b/translations/zh-CN/data/reusables/rest-reference/git/blobs.md
@@ -0,0 +1,12 @@
+## Blob
+
+Git Blob（二进制大对象）是用于将每个文件的内容存储在仓库中的对象类型。 文件的 SHA-1 哈希在 Blob 对象中计算和存储。 这些端点允许您在 {% data variables.product.product_name %} 上的 Git 数据库中读取和写入 [blob 对象](https://git-scm.com/book/en/v1/Git-Internals-Git-Objects)。 Blob 使用[这些自定义媒体类型](#custom-media-types-for-blobs)。 您可以在[此处](/rest/overview/media-types)阅读有关 API 中媒体类型使用情况的更多信息。
+
+### Blob 的自定义媒体类型
+
+以下是 blob 支持的媒体类型。
+
+ application/json
+ application/vnd.github.VERSION.raw
+
+更多信息请参阅“[媒体类型](/rest/overview/media-types)”。
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/rest-reference/git/commits.md b/translations/zh-CN/data/reusables/rest-reference/git/commits.md
new file mode 100644
index 000000000000..5eea52343f94
--- /dev/null
+++ b/translations/zh-CN/data/reusables/rest-reference/git/commits.md
@@ -0,0 +1,3 @@
+## 提交
+
+A Git commit is a snapshot of the hierarchy ([Git tree](/rest/reference/git#trees)) and the contents of the files ([Git blob](/rest/reference/git#blobs)) in a Git repository. 这些端点允许您在 {% data variables.product.product_name %} 上的 Git 数据库中读取和写入[提交对象](https://git-scm.com/book/en/v1/Git-Internals-Git-Objects#Commit-Objects)。
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/rest-reference/git/git.md b/translations/zh-CN/data/reusables/rest-reference/git/git.md
new file mode 100644
index 000000000000..a76071074090
--- /dev/null
+++ b/translations/zh-CN/data/reusables/rest-reference/git/git.md
@@ -0,0 +1 @@
+Git 数据库 API 使您能够在 {% data variables.product.product_name %} 上的 Git 数据库中读取和写入原始 Git 对象，并列出和更新您的引用（分支头部和标记）。 有关使用 Git 数据库 API 的更多信息，请参阅“[Git 数据库 API 入门指南](/rest/guides/getting-started-with-the-git-database-api)”。
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/rest-reference/git/refs.md b/translations/zh-CN/data/reusables/rest-reference/git/refs.md
new file mode 100644
index 000000000000..c83bf9b48450
--- /dev/null
+++ b/translations/zh-CN/data/reusables/rest-reference/git/refs.md
@@ -0,0 +1,3 @@
+## 引用
+
+Git 引用 (`git ref`) 只是一个包含 Git 提交 SHA-1 哈希的文件。 当引用 Git 提交时，您可以使用 Git 引用，这是一个易于记住的名称，而不是哈希。 可以重写 Git 引用指向新的提交。 分支只是存储新 Git 提交哈希的 Git 引用。 这些端点允许您在 {% data variables.product.product_name %} 上的 Git 数据库中读取和写入[引用](https://git-scm.com/book/en/v1/Git-Internals-Git-References)。
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/rest-reference/git/tags.md b/translations/zh-CN/data/reusables/rest-reference/git/tags.md
new file mode 100644
index 000000000000..51300212af89
--- /dev/null
+++ b/translations/zh-CN/data/reusables/rest-reference/git/tags.md
@@ -0,0 +1,3 @@
+## 标记
+
+Git 标记类似于 [Git 引用](/rest/reference/git#refs)，但它指向的 Git 提交永远不变。 当您想要指向特定发行版时，Git 标记非常有用。 这些端点允许您在 {% data variables.product.product_name %} 上的 Git 数据库中读取和写入[标记对象](https://git-scm.com/book/en/v1/Git-Internals-Git-References#Tags)。 Git 标记 API 只支持[标注的标记对象](https://git-scm.com/book/en/v1/Git-Internals-Git-References#Tags)，而不支持轻量级标记。
diff --git a/translations/zh-CN/data/reusables/rest-reference/git/trees.md b/translations/zh-CN/data/reusables/rest-reference/git/trees.md
new file mode 100644
index 000000000000..3f24d5c9ddc7
--- /dev/null
+++ b/translations/zh-CN/data/reusables/rest-reference/git/trees.md
@@ -0,0 +1,3 @@
+## 树
+
+Git 树对象在 Git 仓库中的文件之间创建层次结构。 您可以使用 Git 树对象创建目录与其包含的文件之间的关系。 这些端点允许您在 {% data variables.product.product_name %} 上的 Git 数据库中读取和写入[树对象](https://git-scm.com/book/en/v1/Git-Internals-Git-Objects#Tree-Objects)。
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/rest-reference/gitignore/gitignore.md b/translations/zh-CN/data/reusables/rest-reference/gitignore/gitignore.md
new file mode 100644
index 000000000000..76c6993bd1d7
--- /dev/null
+++ b/translations/zh-CN/data/reusables/rest-reference/gitignore/gitignore.md
@@ -0,0 +1,9 @@
+当您通过 API 在 {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} 上创建新仓库时，您可以指定一个 [.gitignore 模板](/github/getting-started-with-github/ignoring-files) 在创建时应用于仓库。 .gitignore 模板 API 可列出 {% data variables.product.product_name %} [.gitignore 仓库](https://github.com/github/gitignore)并从中获取模板。
+
+### gitignore 的自定义媒体类型
+
+获取 gitignore 模板时，您可以使用以下自定义媒体类型。
+
+ application/vnd.github.VERSION.raw
+
+更多信息请参阅“[媒体类型](/rest/overview/media-types)”。
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/rest-reference/interactions/interactions.md b/translations/zh-CN/data/reusables/rest-reference/interactions/interactions.md
new file mode 100644
index 000000000000..6bef85c509bd
--- /dev/null
+++ b/translations/zh-CN/data/reusables/rest-reference/interactions/interactions.md
@@ -0,0 +1 @@
+用户通过评论、开设议题和创建拉取请求与仓库进行交互。 交互 API 允许具有公共仓库所有者或具有管理员访问权限的用户临时将与公共仓库的交互限于特定类型的用户。
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/rest-reference/interactions/orgs.md b/translations/zh-CN/data/reusables/rest-reference/interactions/orgs.md
new file mode 100644
index 000000000000..c9de508fa03b
--- /dev/null
+++ b/translations/zh-CN/data/reusables/rest-reference/interactions/orgs.md
@@ -0,0 +1,9 @@
+## 组织
+
+组织交互 API 允许组织所有者临时限制哪类用户可以在组织的公共仓库中发表评论、开设议题或创建拉取请求。 {% data reusables.interactions.interactions-detail %} 以下是有关 {% data variables.product.product_name %} 用户类型的更多信息：
+
+* 组织中的 {% data reusables.interactions.existing-user-limit-definition %}。
+* 组织中的 {% data reusables.interactions.contributor-user-limit-definition %}。
+* 组织中的 {% data reusables.interactions.collaborator-user-limit-definition %}。
+
+在组织级别设置交互限制将覆盖为组织拥有的各个仓库设置的任何交互限制。 要为组织拥有的各个仓库设置不同的交互限制，请改用[仓库](#repository)交互端点。
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/rest-reference/interactions/repos.md b/translations/zh-CN/data/reusables/rest-reference/interactions/repos.md
new file mode 100644
index 000000000000..41258d64a43c
--- /dev/null
+++ b/translations/zh-CN/data/reusables/rest-reference/interactions/repos.md
@@ -0,0 +1,9 @@
+## 仓库
+
+仓库交互 API 允许具有所有者或管理员权限的用户临时限制哪类用户可以在公共仓库中发表评论、开设议题或创建拉取请求。 {% data reusables.interactions.interactions-detail %} 以下是有关 {% data variables.product.product_name %} 用户类型的更多信息：
+
+* 仓库中的 {% data reusables.interactions.existing-user-limit-definition %}。
+* 仓库中的 {% data reusables.interactions.contributor-user-limit-definition %}。
+* 仓库中的 {% data reusables.interactions.collaborator-user-limit-definition %}。
+
+如果对拥有该仓库的用户或组织启用了交互限制，单个仓库的限制就不能更改。 而应使用[用户](#user)或[组织](#organization)交互端点来更改交互限制。
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/rest-reference/interactions/users.md b/translations/zh-CN/data/reusables/rest-reference/interactions/users.md
new file mode 100644
index 000000000000..0d30e5a0ce24
--- /dev/null
+++ b/translations/zh-CN/data/reusables/rest-reference/interactions/users.md
@@ -0,0 +1,9 @@
+## 用户
+
+The User Interactions API allows you to temporarily restrict which type of user can comment, open issues, or create pull requests on your public repositories. {% data reusables.interactions.interactions-detail %} 以下是有关 {% data variables.product.product_name %} 用户类型的更多信息：
+
+* {% data reusables.interactions.existing-user-limit-definition %} from interacting with your repositories.
+* {% data reusables.interactions.contributor-user-limit-definition %} from interacting with your repositories.
+* {% data reusables.interactions.collaborator-user-limit-definition %} from interacting with your repositories.
+
+Setting the interaction limit at the user level will overwrite any interaction limits that are set for individual repositories owned by the user. To set different interaction limits for individual repositories owned by the user, use the [Repository](#repository) interactions endpoints instead.
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/rest-reference/issues/assignees.md b/translations/zh-CN/data/reusables/rest-reference/issues/assignees.md
new file mode 100644
index 000000000000..9de131ee0579
--- /dev/null
+++ b/translations/zh-CN/data/reusables/rest-reference/issues/assignees.md
@@ -0,0 +1 @@
+## 受理人
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/rest-reference/issues/comments.md b/translations/zh-CN/data/reusables/rest-reference/issues/comments.md
new file mode 100644
index 000000000000..268f00e88735
--- /dev/null
+++ b/translations/zh-CN/data/reusables/rest-reference/issues/comments.md
@@ -0,0 +1,5 @@
+## 评论
+
+议题评论 API 支持列出、查看、编辑和创建对议题和拉取请求的评论。
+
+议题评论使用[这些自定义媒体类型](#custom-media-types)。 您可以在[此处](/rest/overview/media-types)阅读有关 API 中媒体类型使用情况的更多信息。
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/rest-reference/issues/events.md b/translations/zh-CN/data/reusables/rest-reference/issues/events.md
new file mode 100644
index 000000000000..856241c077bf
--- /dev/null
+++ b/translations/zh-CN/data/reusables/rest-reference/issues/events.md
@@ -0,0 +1,3 @@
+## 事件
+
+The Issue Events API can return different types of events triggered by activity in issues and pull requests. For more information about the specific events that you can receive from the Issue Events API, see "[Issue event types](/developers/webhooks-and-events/issue-event-types)." 有关可以从议题事件 API 接收的特定事件的更多信息，请参阅“[议题事件类型](/developers/webhooks-and-events/issue-event-types)”。 For more information, see the "[Events API](/developers/webhooks-and-events/github-event-types)."
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/rest-reference/issues/issues.md b/translations/zh-CN/data/reusables/rest-reference/issues/issues.md
new file mode 100644
index 000000000000..f948cd3e545a
--- /dev/null
+++ b/translations/zh-CN/data/reusables/rest-reference/issues/issues.md
@@ -0,0 +1,10 @@
+### 议题的自定义媒体类型
+
+以下是议题支持的媒体类型。
+
+ application/vnd.github.VERSION.raw+json
+ application/vnd.github.VERSION.text+json
+ application/vnd.github.VERSION.html+json
+ application/vnd.github.VERSION.full+json
+
+有关媒体类型的更多信息，请参阅“[自定义媒体类型](/rest/overview/media-types)”。
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/rest-reference/issues/labels.md b/translations/zh-CN/data/reusables/rest-reference/issues/labels.md
new file mode 100644
index 000000000000..7c6f27ea86c3
--- /dev/null
+++ b/translations/zh-CN/data/reusables/rest-reference/issues/labels.md
@@ -0,0 +1 @@
+## 标签
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/rest-reference/issues/milestones.md b/translations/zh-CN/data/reusables/rest-reference/issues/milestones.md
new file mode 100644
index 000000000000..e08048c9e0f9
--- /dev/null
+++ b/translations/zh-CN/data/reusables/rest-reference/issues/milestones.md
@@ -0,0 +1 @@
+## 里程碑
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/rest-reference/issues/timeline.md b/translations/zh-CN/data/reusables/rest-reference/issues/timeline.md
new file mode 100644
index 000000000000..d499f7e8c779
--- /dev/null
+++ b/translations/zh-CN/data/reusables/rest-reference/issues/timeline.md
@@ -0,0 +1,5 @@
+## 时间表
+
+时间表事件 API 可以返回议题和拉取请求中的时间表活动所触发的不同类型的事件。 For more information about the specific events that you can receive from the Issue Events API, see "[Issue event types](/developers/webhooks-and-events/issue-event-types)." 有关可以从议题事件 API 接收的特定事件的更多信息，请参阅“[议题事件类型](/developers/webhooks-and-events/issue-event-types)”。 更多信息请参阅“[GitHub 事件 API](/developers/webhooks-and-events/github-event-types)”。
+
+您可以使用此 API 显示有关议题和拉取请求的信息，或确定应向谁通知议题评论。
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/rest-reference/licenses/licenses.md b/translations/zh-CN/data/reusables/rest-reference/licenses/licenses.md
new file mode 100644
index 000000000000..ba554c3d2589
--- /dev/null
+++ b/translations/zh-CN/data/reusables/rest-reference/licenses/licenses.md
@@ -0,0 +1,22 @@
+许可 API 返回有关热门开源许可的元数据，以及有关特定项目许可文件的信息。
+
+许可证 API 使用[开源 Ruby Gem 许可](https://github.com/benbalter/licensee)来尝试识别项目的许可。 被许可人将项目 `LICENSE` 文件（如果有）的内容与已知许可的简短列表相匹配。 因此，API 不考虑项目依赖项的许可或其他记录项目许可的方式，例如对文档中许可名称的引用。
+
+如果许可匹配，则返回的许可密钥和名称符合 [SPDX 规格](https://spdx.org/)。
+
+**注：**这些端点还将返回仓库的许可信息：
+
+- [获取仓库](/rest/reference/repos#get-a-repository)
+- [列出用户的仓库](/rest/reference/repos#list-repositories-for-a-user)
+- [列出组织仓库](/rest/reference/repos#list-organization-repositories)
+- [列出复刻](/rest/reference/repos#list-forks)
+- [列出用户关注的仓库](/rest/reference/activity#list-repositories-watched-by-a-user)
+- [列出团队仓库](/rest/reference/teams#list-team-repositories)
+
+{% warning %}
+
+GitHub 有很多功能， 但它不是律师事务所。 因此，GitHub 不提供法律建议。 使用许可 API 或向我们发送电子邮件并不构成法律意见，也不形成律师-客户关系。 如果您对特定许可可以做什么和不能做什么有任何疑问，您应该在继续之前先咨询自己的法律顾问。 事实上，在做出任何可能具有法律后果或影响您合法权利的决定之前，您都应该咨询自己的律师。
+
+GitHub 创建了许可 API，旨在帮助用户获取有关开源许可以及使用它们的项目的信息。 我们希望它有帮助，但请记住，我们不是律师（至少大多数人不是），像其他人一样，我们也会犯错。 因此，GitHub“按原样”提供 API，对提供或通过其提供的任何信息或许可不做任何保证，并对使用 API 所造成的损害不承担责任。
+
+{% endwarning %}
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/rest-reference/metrics/community.md b/translations/zh-CN/data/reusables/rest-reference/metrics/community.md
new file mode 100644
index 000000000000..876545fa54cc
--- /dev/null
+++ b/translations/zh-CN/data/reusables/rest-reference/metrics/community.md
@@ -0,0 +1 @@
+## 社区
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/rest-reference/metrics/statistics.md b/translations/zh-CN/data/reusables/rest-reference/metrics/statistics.md
new file mode 100644
index 000000000000..2b8bd89c786c
--- /dev/null
+++ b/translations/zh-CN/data/reusables/rest-reference/metrics/statistics.md
@@ -0,0 +1,17 @@
+## 统计
+
+仓库统计 API 允许您获取 {% data variables.product.product_name %} 用于可视化不同类型仓库活动的数据。
+
+### 谈一谈缓存
+
+计算仓库统计信息是一项昂贵的操作，所以我们尽可能返回缓存的数据。 如果您查询仓库的统计信息时，数据尚未缓存，您将会收到 `202` 响应；同时触发后台作业以开始编译这些统计信息。 稍等片刻，待作业完成，然后再次提交请求。 如果作业已完成，该请求将返回 `200` 响应，响应正文中包含统计信息。
+
+仓库统计信息由仓库默认分支的 SHA 缓存；推送到默认分支将重置统计信息缓存。
+
+### 统计排除某些类型的提交
+
+API 公开的统计信息与[各种仓库图](/github/visualizing-repository-data-with-graphs/about-repository-graphs)显示的统计信息相匹配。
+
+总结：
+- 所有统计信息都排除合并提交。
+- 参与者统计信息还排除空提交。
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/rest-reference/metrics/traffic.md b/translations/zh-CN/data/reusables/rest-reference/metrics/traffic.md
new file mode 100644
index 000000000000..6df9444cbd84
--- /dev/null
+++ b/translations/zh-CN/data/reusables/rest-reference/metrics/traffic.md
@@ -0,0 +1,3 @@
+## 流量
+
+对于您具有推送权限的仓库，流量 API 提供对仓库图中所示信息的访问权限。 更多信息请参阅“查看仓库的流量”。
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/rest-reference/migrations/orgs.md b/translations/zh-CN/data/reusables/rest-reference/migrations/orgs.md
new file mode 100644
index 000000000000..68964cc40b0e
--- /dev/null
+++ b/translations/zh-CN/data/reusables/rest-reference/migrations/orgs.md
@@ -0,0 +1,5 @@
+## 组织
+
+迁移 API 仅适用于经过身份验证的组织所有者。 更多信息请参阅“[组织中的角色](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#permission-levels-for-an-organization)”和“[其他身份验证方法](/rest/overview/other-authentication-methods)”。
+
+{% data variables.migrations.organization_migrations_intro %}
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/rest-reference/migrations/source-imports.md b/translations/zh-CN/data/reusables/rest-reference/migrations/source-imports.md
new file mode 100644
index 000000000000..cb4701f8e109
--- /dev/null
+++ b/translations/zh-CN/data/reusables/rest-reference/migrations/source-imports.md
@@ -0,0 +1,80 @@
+## 源导入
+
+{% data variables.migrations.source_imports_intro %}
+
+如果导入中存在大型文件，则典型的源导入将开始导入，然后（可选）更新作者和/或更新使用 Git LFS 的首选项。 您也可以创建侦听 [`RepositoryImportEvent`](/developers/webhooks-and-events/webhook-events-and-payloads#repository_import) 的 web 挂钩来了解导入的状态。
+
+在此图中可以看到更详细的示例：
+
+```
++---------+ +--------+ +---------------------+
+| Tooling | | GitHub | | Original Repository |
++---------+ +--------+ +---------------------+
+ | | |
+ | Start import | |
+ |----------------------------->| |
+ | | |
+ | | Download source data |
+ | |--------------------------------------------->|
+ | | Begin streaming data |
+ | |<---------------------------------------------|
+ | | |
+ | Get import progress | |
+ |----------------------------->| |
+ | "status": "importing" | |
+ |<-----------------------------| |
+ | | |
+ | Get commit authors | |
+ |----------------------------->| |
+ | | |
+ | Map a commit author | |
+ |----------------------------->| |
+ | | |
+ | | |
+ | | Finish streaming data |
+ | |<---------------------------------------------|
+ | | |
+ | | Rewrite commits with mapped authors |
+ | |------+ |
+ | | | |
+ | |<-----+ |
+ | | |
+ | | Update repository on GitHub |
+ | |------+ |
+ | | | |
+ | |<-----+ |
+ | | |
+ | Map a commit author | |
+ |----------------------------->| |
+ | | Rewrite commits with mapped authors |
+ | |------+ |
+ | | | |
+ | |<-----+ |
+ | | |
+ | | Update repository on GitHub |
+ | |------+ |
+ | | | |
+ | |<-----+ |
+ | | |
+ | Get large files | |
+ |----------------------------->| |
+ | | |
+ | opt_in to Git LFS | |
+ |----------------------------->| |
+ | | Rewrite commits for large files |
+ | |------+ |
+ | | | |
+ | |<-----+ |
+ | | |
+ | | Update repository on GitHub |
+ | |------+ |
+ | | | |
+ | |<-----+ |
+ | | |
+ | Get import progress | |
+ |----------------------------->| |
+ | "status": "complete" | |
+ |<-----------------------------| |
+ | | |
+ | | |
+```
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/rest-reference/migrations/users.md b/translations/zh-CN/data/reusables/rest-reference/migrations/users.md
new file mode 100644
index 000000000000..e5509e6488d9
--- /dev/null
+++ b/translations/zh-CN/data/reusables/rest-reference/migrations/users.md
@@ -0,0 +1,9 @@
+## 用户
+
+用户迁移 API 仅适用于经过身份验证的帐户所有者。 更多信息请参阅“[其他身份验证方法](/rest/overview/other-authentication-methods)”。
+
+{% data variables.migrations.user_migrations_intro %} 有关可下载的迁移数据列表，请参阅“[下载用户迁移存档](#download-a-user-migration-archive)”。
+
+要下载存档，您需要先开始用户迁移。 在迁移状态为 `exported` 后，便可下载迁移。
+
+创建迁移存档后，该存档可供下载七天。 但是，如果您喜欢，您可以更早删除用户迁移存档。 当迁移为 `exported` 时，您可以解锁仓库以便再次开始使用，如果你不再需要源数据，则可删除您的仓库。
diff --git a/translations/zh-CN/data/reusables/rest-reference/oauth-authorizations/oauth-authorizations.md b/translations/zh-CN/data/reusables/rest-reference/oauth-authorizations/oauth-authorizations.md
new file mode 100644
index 000000000000..93a21aa41584
--- /dev/null
+++ b/translations/zh-CN/data/reusables/rest-reference/oauth-authorizations/oauth-authorizations.md
@@ -0,0 +1,3 @@
+您可以使用此 API 来管理 OAuth 应用程序对您帐户的访问权限。 您只能使用您的用户名和密码（而不是令牌），通过[基本身份验证](/rest/overview/other-authentication-methods#basic-authentication)访问此 API。
+
+如果您或您的用户启用了双重身份验证，请务必了解如何[使用双重身份验证](/rest/overview/other-authentication-methods#working-with-two-factor-authentication)。
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/rest-reference/orgs/blocking.md b/translations/zh-CN/data/reusables/rest-reference/orgs/blocking.md
new file mode 100644
index 000000000000..bd773fef35ef
--- /dev/null
+++ b/translations/zh-CN/data/reusables/rest-reference/orgs/blocking.md
@@ -0,0 +1,3 @@
+## 阻止用户
+
+用于对调用进行身份验证的令牌必须具有 `admin:org` 作用域才可对组织进行任何阻止调用。 否则，响应将返回 `HTTP 404`。
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/rest-reference/orgs/custom_roles.md b/translations/zh-CN/data/reusables/rest-reference/orgs/custom_roles.md
new file mode 100644
index 000000000000..310339895f00
--- /dev/null
+++ b/translations/zh-CN/data/reusables/rest-reference/orgs/custom_roles.md
@@ -0,0 +1 @@
+## Custom repository roles
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/rest-reference/orgs/members.md b/translations/zh-CN/data/reusables/rest-reference/orgs/members.md
new file mode 100644
index 000000000000..216967442f0b
--- /dev/null
+++ b/translations/zh-CN/data/reusables/rest-reference/orgs/members.md
@@ -0,0 +1 @@
+## 成员
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/rest-reference/orgs/outside-collaborators.md b/translations/zh-CN/data/reusables/rest-reference/orgs/outside-collaborators.md
new file mode 100644
index 000000000000..2373a171cd6d
--- /dev/null
+++ b/translations/zh-CN/data/reusables/rest-reference/orgs/outside-collaborators.md
@@ -0,0 +1 @@
+## 外部协作者
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/rest-reference/orgs/webhooks.md b/translations/zh-CN/data/reusables/rest-reference/orgs/webhooks.md
new file mode 100644
index 000000000000..cad13730b513
--- /dev/null
+++ b/translations/zh-CN/data/reusables/rest-reference/orgs/webhooks.md
@@ -0,0 +1,24 @@
+## Web 挂钩
+
+组织 web 挂钩允许您在组织内发生特定事件时接收 HTTP `POST` 有效负载。 {% data reusables.webhooks.webhooks-rest-api-links %}
+
+有关您可以订阅的操作的更多信息，请参阅“[{% data variables.product.prodname_dotcom %} 事件类型](/developers/webhooks-and-events/github-event-types)”。
+
+### 范围和限制
+
+对组织 web 挂钩的所有操作都需要经过身份验证的用户是所管理组织的管理员。 此外，OAuth 令牌需要 `admin:org_hook` 作用域。 更多信息请参阅“[OAuth 应用程序的作用域](/developers/apps/scopes-for-oauth-apps)”。
+
+为了保护 web 挂钩配置中可能存在的敏感数据，我们还强制实施以下访问控制规则：
+
+- OAuth 应用程序无法列出、查看或编辑不是它们创建的 web 挂钩。
+- 用户无法列出、查看或编辑由 OAuth 应用程序创建的 web 挂钩。
+
+### 接收 web 挂钩
+
+为了让 {% data variables.product.product_name %} 发送 web 挂钩有效负载，您的服务器需要能够从 Internet 访问。 我们还强烈建议使用 SSL，以便我们可以通过 HTTPS 发送加密的有效负载。
+
+有关更多最佳实践，[请参阅我们的指南](/guides/best-practices-for-integrators/)。
+
+#### Web 挂钩标头
+
+{% data variables.product.product_name %} 发送时将附带几个 HTTP 标头，以区分事件类型和有效负载标识符。 更多信息请参阅 [web 挂钩标头](/webhooks/event-payloads/#delivery-headers)。
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/rest-reference/packages/packages.md b/translations/zh-CN/data/reusables/rest-reference/packages/packages.md
new file mode 100644
index 000000000000..32c478f7c869
--- /dev/null
+++ b/translations/zh-CN/data/reusables/rest-reference/packages/packages.md
@@ -0,0 +1,10 @@
+The {% data variables.product.prodname_registry %} API enables you to manage packages using the REST API. To learn more about restoring or deleting packages, see "[Restoring and deleting packages](/packages/learn-github-packages/deleting-and-restoring-a-package)."
+
+To use this API, you must authenticate using a personal access token.
+ - To access package metadata, your token must include the `read:packages` scope.
+ - To delete packages and package versions, your token must include the `read:packages` and `delete:packages` scopes.
+ - To restore packages and package versions, your token must include the `read:packages` and `write:packages` scopes.
+
+If your `package_type` is `npm`, `maven`, `rubygems`, or `nuget`, then your token must also include the `repo` scope since your package inherits permissions from a {% data variables.product.prodname_dotcom %} repository. If your package is in the {% data variables.product.prodname_container_registry %}, then your `package_type` is `container` and your token does not need the `repo` scope to access or manage this `package_type`. `container` packages offer granular permissions separate from a repository. For more information, see "[About permissions for {% data variables.product.prodname_registry %}](/packages/learn-github-packages/about-permissions-for-github-packages#about-scopes-and-permissions-for-package-registries)."
+
+If you want to use the {% data variables.product.prodname_registry %} API to access resources in an organization with SSO enabled, then you must enable SSO for your personal access token. For more information, see "[Authorizing a personal access token for use with SAML single sign-on](/github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/rest-reference/pages/pages.md b/translations/zh-CN/data/reusables/rest-reference/pages/pages.md
new file mode 100644
index 000000000000..94a09ce18e2c
--- /dev/null
+++ b/translations/zh-CN/data/reusables/rest-reference/pages/pages.md
@@ -0,0 +1,14 @@
+{% data variables.product.prodname_pages %} API 可检索关于您的 {% data variables.product.prodname_pages %} 配置以及构建状态的信息。 只有经过验证的所有者才能访问有关网站和构建的信息{% ifversion not ghae %}，即使网站是公开的也一样{% endif %}。 更多信息请参阅“[关于 {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages)”。
+
+在其响应中包含 `status` 键的 {% data variables.product.prodname_pages %} API 端点中，其值可能是以下值之一：
+* `null`：站点尚未构建。
+* `queued`：已请求构建，但尚未开始。
+* `building`：正在构建中。
+* `built`：站点已构建。
+* `errored`：表示构建过程中发生错误。
+
+在返回 GitHub Pages 站点信息的 {% data variables.product.prodname_pages %} API 端点中，JSON 响应包括以下字段：
+* `html_url`：所渲染的 Pages 站点的绝对 URL（包括模式）。 例如，`https://username.github.io`。
+* `source`：包含所渲染 Pages 站点的源分支和目录的对象。 这包括：
+ - `branch`：用于发布[站点源文件](/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site)的仓库分支。 例如，_main_ 或 _gh-pages_。
+ - `path`：提供站点发布内容的仓库目录。 可能是 `/` 或 `/docs`。
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/rest-reference/projects/cards.md b/translations/zh-CN/data/reusables/rest-reference/projects/cards.md
new file mode 100644
index 000000000000..74e8cff73685
--- /dev/null
+++ b/translations/zh-CN/data/reusables/rest-reference/projects/cards.md
@@ -0,0 +1 @@
+## 卡
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/rest-reference/projects/collaborators.md b/translations/zh-CN/data/reusables/rest-reference/projects/collaborators.md
new file mode 100644
index 000000000000..a0d31226b3ee
--- /dev/null
+++ b/translations/zh-CN/data/reusables/rest-reference/projects/collaborators.md
@@ -0,0 +1,3 @@
+## 协作者
+
+此 API 允许您与组织的项目进行交互。
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/rest-reference/projects/columns.md b/translations/zh-CN/data/reusables/rest-reference/projects/columns.md
new file mode 100644
index 000000000000..893d68007ea5
--- /dev/null
+++ b/translations/zh-CN/data/reusables/rest-reference/projects/columns.md
@@ -0,0 +1 @@
+## 列
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/rest-reference/pulls/comments.md b/translations/zh-CN/data/reusables/rest-reference/pulls/comments.md
new file mode 100644
index 000000000000..0760292a8163
--- /dev/null
+++ b/translations/zh-CN/data/reusables/rest-reference/pulls/comments.md
@@ -0,0 +1,14 @@
+## 审查评论
+
+拉取请求审查评论是在拉取请求审查期间对统一差异的一部分所发表的评论。 提交评论和议题评论不同于拉取请求审查评论。 将提交评论直接应用于提交，然后应用议题评论而不引用统一差异的一部分。 更多信息请参阅“[创建提交评论](/rest/reference/commits#create-a-commit-comment)”和“[创建议题评论](/rest/reference/issues#create-an-issue-comment)”。
+
+### 拉取请求审查评论的自定义媒体类型
+
+以下是拉取请求审查评论支持的媒体类型。
+
+ application/vnd.github.VERSION.raw+json
+ application/vnd.github.VERSION.text+json
+ application/vnd.github.VERSION.html+json
+ application/vnd.github.VERSION.full+json
+
+更多信息请参阅“[自定义媒体类型](/rest/overview/media-types)”。
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/rest-reference/pulls/pulls.md b/translations/zh-CN/data/reusables/rest-reference/pulls/pulls.md
new file mode 100644
index 000000000000..657240e030e9
--- /dev/null
+++ b/translations/zh-CN/data/reusables/rest-reference/pulls/pulls.md
@@ -0,0 +1,33 @@
+拉取请求 API 允许您列出、查看、编辑、创建甚至合并拉取请求。 可以通过[议题评论 API](/rest/reference/issues#comments) 管理对拉取请求的评论。
+
+每个拉取请求都是一个议题，但并非每个议题都是拉取请求。 因此，在[议题 API](/rest/reference/issues) 中为这两项功能提供了“共享”操作，如操作受理人、标签和里程碑。
+
+### 拉取请求的自定义媒体类型
+
+以下是拉取请求支持的媒体类型。
+
+ application/vnd.github.VERSION.raw+json
+ application/vnd.github.VERSION.text+json
+ application/vnd.github.VERSION.html+json
+ application/vnd.github.VERSION.full+json
+ application/vnd.github.VERSION.diff
+ application/vnd.github.VERSION.patch
+
+更多信息请参阅“[自定义媒体类型](/rest/overview/media-types)”。
+
+如果 diff 损坏，请联系 {% data variables.contact.contact_support %}。 在您的消息中包括仓库名称和拉取请求 ID。
+
+### 链接关系
+
+拉取请求具有以下可能的链接关系：
+
+| 名称 | 描述 |
+| ----------------- | ---------------------------------------------------------------------------------------- |
+| `self` | 此拉取请求的 API 位置。 |
+| `html` | 此拉取请求的 HTML 位置。 |
+| `议题` | 此拉取请求的[议题](/rest/reference/issues)的 API 位置。 |
+| `comments` | 此拉取请求的[议题评论](/rest/reference/issues#comments)的 API 位置。 |
+| `review_comments` | 此拉取请求的[审查评论](/rest/reference/pulls#comments)的 API 位置。 |
+| `review_comment` | 用于为此拉取请求仓库中的[审查评论](/rest/reference/pulls#comments)构建 API 位置的 [URL 模板](/rest#hypermedia)。 |
+| `commits` | 此拉取请求的[提交](#list-commits-on-a-pull-request)的 API 位置。 |
+| `状态` | 此拉取请求的[提交状态](/rest/reference/commits#commit-statuses)的 API 位置，即其`头部`分支的状态。 |
diff --git a/translations/zh-CN/data/reusables/rest-reference/pulls/review-requests.md b/translations/zh-CN/data/reusables/rest-reference/pulls/review-requests.md
new file mode 100644
index 000000000000..b1fc94e60573
--- /dev/null
+++ b/translations/zh-CN/data/reusables/rest-reference/pulls/review-requests.md
@@ -0,0 +1,3 @@
+## 审查请求
+
+拉取请求作者以及仓库所有者和协作者可以向具有仓库写入权限的任何人请求拉取请求审查。 每个被请求的审查者将收到您要求他们审查拉取请求的通知。
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/rest-reference/pulls/reviews.md b/translations/zh-CN/data/reusables/rest-reference/pulls/reviews.md
new file mode 100644
index 000000000000..4ac87913571a
--- /dev/null
+++ b/translations/zh-CN/data/reusables/rest-reference/pulls/reviews.md
@@ -0,0 +1,3 @@
+## 审查
+
+拉取请求审查是拉取请求上的拉取请求审查评论组，与状态和可选的正文注释一起分组。
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/rest-reference/rate-limit/rate-limit.md b/translations/zh-CN/data/reusables/rest-reference/rate-limit/rate-limit.md
new file mode 100644
index 000000000000..5c6bd1030918
--- /dev/null
+++ b/translations/zh-CN/data/reusables/rest-reference/rate-limit/rate-limit.md
@@ -0,0 +1,17 @@
+REST API 概述文档描述了[速率限制规则](/rest/overview/resources-in-the-rest-api#rate-limiting)。 您可以随时使用下面描述的速率限制 API 来检查您当前的速率限制状态。
+
+### 了解您的速率限制状态
+
+搜索 API 具有[自定义速率限制](/rest/reference/search#rate-limit)，与管理 REST API 其余部分的速率限制不同。 GraphQL API 也有[自定义速率限制]({% ifversion ghec%}/free-pro-team@latest{% endif %}/graphql/overview/resource-limitations#rate-limit)，它与 REST API 中的速率限制不同且分开计算。
+
+出于这些原因，速率限制 API 响应对速率限制进行分类。 在`资源`下，您会看到四个 对象：
+
+* `核心`对象提供 REST API 中所有非搜索相关资源的速率限制状态。
+
+* `搜索`对象提供[搜索 API](/rest/reference/search) 的速率限制状态。
+
+* `graphql`对象提供 [GraphQL API]({% ifversion ghec%}/free-pro-team@latest{% endif %}/graphql) 的速率限制状态。
+
+* `integration_manifest` 对象提供 [GitHub 应用程序清单代码转换](/apps/building-github-apps/creating-github-apps-from-a-manifest/#3-you-exchange-the-temporary-code-to-retrieve-the-app-configuration)端点的速率限制状态。
+
+有关速率限制响应中标头和值的更多信息，请参阅“[REST API 中的资源](/rest/overview/resources-in-the-rest-api#rate-limit-http-headers)”。
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/rest-reference/reations/reactions.md b/translations/zh-CN/data/reusables/rest-reference/reations/reactions.md
new file mode 100644
index 000000000000..d2feff37dd76
--- /dev/null
+++ b/translations/zh-CN/data/reusables/rest-reference/reations/reactions.md
@@ -0,0 +1,5 @@
+### Reaction types
+
+When creating a reaction, the allowed values for the `content` parameter are as follows (with the corresponding emoji for reference):
+
+{% data reusables.repositories.reaction_list %}
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/rest-reference/releases/assets.md b/translations/zh-CN/data/reusables/rest-reference/releases/assets.md
new file mode 100644
index 000000000000..902620cfeba1
--- /dev/null
+++ b/translations/zh-CN/data/reusables/rest-reference/releases/assets.md
@@ -0,0 +1 @@
+## Release assets
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/rest-reference/releases/releases.md b/translations/zh-CN/data/reusables/rest-reference/releases/releases.md
new file mode 100644
index 000000000000..5ac238aa7c79
--- /dev/null
+++ b/translations/zh-CN/data/reusables/rest-reference/releases/releases.md
@@ -0,0 +1,5 @@
+{% note %}
+
+**注：**发布 API 取代了下载 API。 您可以从返回发行版和发行版资产的 API 端点检索下载次数和浏览器下载 URL。
+
+{% endnote %}
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/rest-reference/repos/autolinks.md b/translations/zh-CN/data/reusables/rest-reference/repos/autolinks.md
new file mode 100644
index 000000000000..1533ea887d03
--- /dev/null
+++ b/translations/zh-CN/data/reusables/rest-reference/repos/autolinks.md
@@ -0,0 +1,5 @@
+## 自动链接
+
+为了帮助简化您的工作流程，您可以使用 API 向外部资源（如 JIRA 问题和 Zendesk 事件单）添加自动链接。 更多信息请参阅“[配置自动链接以引用外部资源](/github/administering-a-repository/configuring-autolinks-to-reference-external-resources)”。
+
+{% data variables.product.prodname_github_apps %} 需要有读写权限的仓库管理权限才能使用 Autolinks API。
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/rest-reference/repos/contents.md b/translations/zh-CN/data/reusables/rest-reference/repos/contents.md
new file mode 100644
index 000000000000..8317e1bd8859
--- /dev/null
+++ b/translations/zh-CN/data/reusables/rest-reference/repos/contents.md
@@ -0,0 +1,22 @@
+## 内容
+
+此 API 端点允许您在仓库中创建、修改和删除 Base64 编码的内容。 要请求原始格式或渲染的 HTML（如果支持），请对仓库内容使用自定义媒体类型。
+
+### 仓库内容的自定义媒体类型
+
+[自述文件](/rest/reference/repos#get-a-repository-readme)、[文件](/rest/reference/repos#get-repository-content)和[符号链接](/rest/reference/repos#get-repository-content)支持以下自定义媒体类型：
+
+ application/vnd.github.VERSION.raw
+ application/vnd.github.VERSION.html
+
+使用 `.raw` 媒体类型检索文件内容。
+
+对于 Markdown 或 AsciiDoc 等标记文件，您可以使用 `.html` 媒体类型检索渲染的 HTML。 使用我们的开源[标记库](https://github.com/github/markup)将标记语言渲染为 HTML。
+
+[所有对象](/rest/reference/repos#get-repository-content)都支持以下自定义媒体类型：
+
+ application/vnd.github.VERSION.object
+
+使用 `object` 媒体类型参数以一致的对象格式检索内容，而不考虑内容类型。 例如，响应将是包含对象数组的 `entries` 属性的对象，而不是目录的对象数组。
+
+您可以在[此处](/rest/overview/media-types)阅读有关 API 中媒体类型使用情况的更多信息。
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/rest-reference/repos/forks.md b/translations/zh-CN/data/reusables/rest-reference/repos/forks.md
new file mode 100644
index 000000000000..7a45135c08f9
--- /dev/null
+++ b/translations/zh-CN/data/reusables/rest-reference/repos/forks.md
@@ -0,0 +1 @@
+## 复刻
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/rest-reference/repos/lfs.md b/translations/zh-CN/data/reusables/rest-reference/repos/lfs.md
new file mode 100644
index 000000000000..5a48e59434d8
--- /dev/null
+++ b/translations/zh-CN/data/reusables/rest-reference/repos/lfs.md
@@ -0,0 +1,2 @@
+
+## Git LFS
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/rest-reference/scim/scim.md b/translations/zh-CN/data/reusables/rest-reference/scim/scim.md
new file mode 100644
index 000000000000..6b13a5e06ac2
--- /dev/null
+++ b/translations/zh-CN/data/reusables/rest-reference/scim/scim.md
@@ -0,0 +1,41 @@
+### 组织的 SCIM 预配
+
+SCIM API 由 SCIM 启用的身份提供程序 (IdP) 用来自动预配 {% data variables.product.product_name %} 组织成员身份。 {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API 基于 2.0 版的 [SCIM 标准](http://www.simplecloud.info/)。 IdP 应使用的 {% data variables.product.product_name %} SCIM 端点是：`{% data variables.product.api_url_code %}/scim/v2/organisation/{org}/`。
+
+{% note %}
+
+**注意：**
+ - SCIM API 仅适用于 [{% data variables.product.prodname_ghe_cloud %}](/billing/managing-billing-for-your-github-account/about-billing-for-github-accounts) 上启用了 [SAML SSO](/rest/overview/other-authentication-methods#authenticating-for-saml-sso) 的组织。 {% data reusables.scim.enterprise-account-scim %} 有关 SCIM 的更多信息，请参阅“[关于 SCIM](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim)”。
+ - SCIM API 不能与 {% data variables.product.prodname_emus %} 一起使用。
+
+{% endnote %}
+
+### 向 SCIM API 验证调用
+
+您必须验证为 {% data variables.product.product_name %} 组织的所有者才可使用其 SCIM API。 API 预期 [OAuth 2.0 Bearer](/developers/apps/authenticating-with-github-apps) 令牌包含在`授权`标头中。 您也可以使用个人访问令牌，但必须先[授权它与您的 SAML SSO 组织一起使用](/github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)。
+
+### SAML 和 SCIM 数据的映射
+
+{% data reusables.scim.nameid-and-username-must-match %}
+
+### 支持的 SCIM 用户属性
+
+| 名称 | 类型 | 描述 |
+| ----------------- | ----- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `userName` | `字符串` | 用户的用户名。 |
+| `name.givenName` | `字符串` | 用户的名字 |
+| `name.familyName` | `字符串` | 用户的姓氏。 |
+| `emails` | `数组` | 用户电子邮件列表。 |
+| `externalId` | `字符串` | 此标识符由 SAML 提供程序生成，并且被 SAML 提供程序用作唯一 ID 来匹配 GitHub 用户。 您可以在 SAML 提供程序上查找用户的 `externalID`，或者使用 [List SCIM 预配的身份](#list-scim-provisioned-identities)端点并过滤其他已知的属性，如用户的 GitHub 用户名或电子邮件地址。 |
+| `id` | `字符串` | GitHub SCIM 端点生成的标识符。 |
+| `active` | `布尔值` | 用于表示身份是处于活动状态 (true) 还是应解除预配 (false)。 |
+
+{% note %}
+
+**注：**SCIM API 的端点 URL 区分大小写。 例如，`Users` 端点中的第一个字母必须大写：
+
+```shell
+GET /scim/v2/organizations/{org}/Users/{scim_user_id}
+```
+
+{% endnote %}
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/rest-reference/search/search.md b/translations/zh-CN/data/reusables/rest-reference/search/search.md
new file mode 100644
index 000000000000..1b3ce8235c97
--- /dev/null
+++ b/translations/zh-CN/data/reusables/rest-reference/search/search.md
@@ -0,0 +1,144 @@
+搜索 API 可帮助您搜索要查找的特定条目。 例如，您可以在仓库中找到用户或特定文件。 就像您在 Google 上执行搜索一样。 它旨在帮助您找到要查找的一个或几个结果。 就像在 Google 上搜索一样，有时您希望查看几页搜索结果，以便找到最能满足您需求的条目。 为了满足这一需求， {% data variables.product.product_name %} 搜索 API **为每个搜索提供最多 1,000 个结果**。
+
+您可以使用查询缩小搜索范围。 要了解有关搜索查询语法的更多信息，请查看“[构建搜索查询](/rest/reference/search#constructing-a-search-query)”。
+
+### 排列搜索结果
+
+除非提供另一个排序选项作为查询参数，否则将按照最佳匹配的原则对结果进行降序排列。 多种因素相结合，将最相关的条目顶到结果列表的顶部。
+
+### 速率限制
+
+{% data reusables.enterprise.rate_limit %}
+
+搜索 API 有自定义速率限制。 对于使用[基本身份验证](/rest#authentication)、[OAuth](/rest#authentication) 或[客户端 ID 和密码](/rest#increasing-the-unauthenticated-rate-limit-for-oauth-applications)的请求，您每分钟最多可以提出 30 个请求。 对于未经身份验证的请求，速率限制允许您每分钟最多提出 10 个请求。
+
+请参阅[速率限制文档](/rest/reference/rate-limit)，以详细了解如何确定您的当前速率限制状态。
+
+### 构造搜索查询
+
+搜索 API 中的每个端点都使用[查询参数](https://en.wikipedia.org/wiki/Query_string)对 {% data variables.product.product_name %} 进行搜索。 有关包含端点和查询参数的示例，请参阅搜索 API 中的各个端点。
+
+查询可以包含在 {% data variables.product.product_name %} 上支持的搜索限定符的任意组合中。 搜索查询的格式为：
+
+```
+SEARCH_KEYWORD_1 SEARCH_KEYWORD_N QUALIFIER_1 QUALIFIER_N
+```
+
+例如，如果您要搜索 `defunkt` 拥有的在自述文件中包含单词 `GitHub` 和 `Octocat` 的所有_仓库_，您可以在_搜索仓库_端点中使用以下查询：
+
+```
+GitHub Octocat in:readme user:defunkt
+```
+
+**注意：** 请务必使用语言的首选 HTML 编码器构造查询字符串。 例如：
+```javascript
+// JavaScript
+const queryString = 'q=' + encodeURIComponent('GitHub Octocat in:readme user:defunkt');
+```
+
+有关可用限定符及其格式的完整列表和使用示例，请参阅“[在 GitHub 上搜索](/search-github/searching-on-github)”。 有关如何使用运算符匹配特定数量、日期或排除结果，请参阅“[了解搜索语法](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax/)”。
+
+### 查询长度限制
+
+搜索 API 不支持以下查询：
+- 超过 256 个字符（不包括运算符或限定符）。
+- 超过五个 `AND`、`OR` 或 `NOT` 运算符。
+
+这些搜索查询将返回“验证失败”错误消息。
+
+### 超时和不完整的结果
+
+为了让所有人都能快速使用搜索 API，我们限制任何单个查询能够运行的时长。 对于[超出时间限制](https://developer.github.com/changes/2014-04-07-understanding-search-results-and-potential-timeouts/)的查询，API 将返回在超时之前已找到的匹配项，并且响应的 `incomplete_results` 属性设为 `true`。
+
+达到超时并不意味着搜索结果不完整， 可能已找到更多结果，也可能没有找到。
+
+### 访问错误或缺少搜索结果
+
+您需要成功完成身份验证并且对您搜索查询的仓库具有访问权限，否则，您将看到 `422 Unprocessible Entry` 错误和“验证失败”消息。 例如，如果您的查询中包含 `repo:`、`user:` 或 `org:` 限定符，但它们请求的资源是您登录 {% data variables.product.prodname_dotcom %} 后无权访问的资源，则搜索将失败。
+
+当您的搜索查询请求多个资源时，响应将只包含您有权访问的资源，并且**不会**提供列出未返回资源的错误消息。
+
+例如，如果您的搜索查询要搜索 `octocat/test` 和 `codertocat/test` 仓库，但您只拥有对 `octocat/test` 的访问权限，则您的响应将显示对 `octocat/test` 的搜索结果，而不会显示对 `codertocat/test` 的搜索结果。 此行为类似于 {% data variables.product.prodname_dotcom %} 上的搜索方式。
+
+### 文本匹配元数据
+
+在 GitHub 上，您可以使用搜索结果中的代码段和高亮显示提供的上下文。 搜索 API 提供额外的元数据，允许您在显示搜索结果时高亮显示匹配搜索词。
+
+
+
+请求可以选择在响应中接收这些文本片段，并且每个片段都附带数字偏移，以标识每个匹配搜索词的确切位置。
+
+要在搜索结果中获取这种元数据，请在 `Accept` 标头中指定 `text-match` 媒体类型。
+
+```shell
+application/vnd.github.v3.text-match+json
+```
+
+提供 `text-match` 媒体类型时，您将在 JSON 有效负载中收到一个额外的键，名为 `text_matches`，它提供有关搜索词在文本中的位置以及包含该搜索词的 `property` 的信息。 在 `text_matches` 数组中，每个对象包含以下属性：
+
+| 名称 | 描述 |
+| ------------- | -------------------------------------------------------------------------------------------------------- |
+| `object_url` | 包含匹配某个搜索词的字符串属性的资源 URL。 |
+| `object_type` | 在给定 `object_url` 中存在的资源类型的名称。 |
+| `属性` | 在 `object_url` 中存在的资源属性的名称。 属性是与某个搜索词相匹配的字符串。 （在从 `object_url` 返回的 JSON 中，`fragment` 的完整内容存在于具有此名称的属性中。） |
+| `分段` | `property` 值的子集。 这是与一个或多个搜索词匹配的文本片段。 |
+| `matches` | 存在于 `fragment` 中的一个或多个搜索词的数组。 索引（即“偏移量”）与片段相关。 （它们与 `property` 的_完整_内容无关。） |
+
+#### 示例
+
+使用 cURL 和上面的[示例议题搜索](#search-issues-and-pull-requests)时，我们的 API 请求如下所示：
+
+``` shell
+curl -H 'Accept: application/vnd.github.v3.text-match+json' \
+'{% data variables.product.api_url_pre %}/search/issues?q=windows+label:bug+language:python+state:open&sort=created&order=asc'
+```
+
+对于每个搜索结果，响应将包含一个 `text_matches` 数组。 在下面的 JSON 中，我们在 `text_matches` 数组中有两个对象。
+
+第一个文本匹配出现在议题的 `body` 属性中。 我们从议题正文中看到了文本片段。 搜索词 (`windows`) 在该片段中出现了两次，我们有每次出现时的索引。
+
+第二个文本匹配出现在其中一个议题注释的 `body` 属性中。 我们有议题注释的 URL。 当然，我们从注释正文中看到了文本片段。 搜索词 (`windows`) 在该片段中出现了一次。
+
+```json
+{
+ "text_matches": [
+ {
+ "object_url": "https://api.github.com/repositories/215335/issues/132",
+ "object_type": "Issue",
+ "property": "body",
+ "fragment": "comprehensive windows font I know of).\n\nIf we can find a commonly distributed windows font that supports them then no problem (we can use html font tags) but otherwise the '(21)' style is probably better.\n",
+ "matches": [
+ {
+ "text": "windows",
+ "indices": [
+ 14,
+ 21
+ ]
+ },
+ {
+ "text": "windows",
+ "indices": [
+ 78,
+ 85
+ ]
+ }
+ ]
+ },
+ {
+ "object_url": "https://api.github.com/repositories/215335/issues/comments/25688",
+ "object_type": "IssueComment",
+ "property": "body",
+ "fragment": " right after that are a bit broken IMHO :). I suppose we could have some hack that maxes out at whatever the font does...\n\nI'll check what the state of play is on Windows.\n",
+ "matches": [
+ {
+ "text": "Windows",
+ "indices": [
+ 163,
+ 170
+ ]
+ }
+ ]
+ }
+ ]
+}
+```
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/rest-reference/secret-scanning/secret-scanning.md b/translations/zh-CN/data/reusables/rest-reference/secret-scanning/secret-scanning.md
new file mode 100644
index 000000000000..02d84249bbe4
--- /dev/null
+++ b/translations/zh-CN/data/reusables/rest-reference/secret-scanning/secret-scanning.md
@@ -0,0 +1,9 @@
+{% data reusables.secret-scanning.api-beta %}
+
+The {% data variables.product.prodname_secret_scanning %} API lets you{% ifversion fpt or ghec or ghes > 3.1 or ghae %}:
+
+- Enable or disable {% data variables.product.prodname_secret_scanning %} for a repository. For more information, see "[Repositories](/rest/reference/repos#update-a-repository)" in the REST API documentation.
+- Retrieve and update {% data variables.product.prodname_secret_scanning %} alerts from a {% ifversion fpt or ghec %}private {% endif %}repository. For futher details, see the sections below.
+{%- else %} retrieve and update {% data variables.product.prodname_secret_scanning %} alerts from a {% ifversion fpt or ghec %}private {% endif %}repository.{% endif %}
+
+For more information about {% data variables.product.prodname_secret_scanning %}, see "[About {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/about-secret-scanning)."
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/rest-reference/teams/discussion-comments.md b/translations/zh-CN/data/reusables/rest-reference/teams/discussion-comments.md
new file mode 100644
index 000000000000..9206fe9fd3be
--- /dev/null
+++ b/translations/zh-CN/data/reusables/rest-reference/teams/discussion-comments.md
@@ -0,0 +1,3 @@
+## 讨论评论
+
+团队讨论评论 API 允许您在[团队讨论](/rest/reference/teams#discussions)帖子上获取、 创建、编辑和删除讨论评论。 团队[组织](/rest/reference/orgs)的任何成员都可以创建和阅读公共讨论上的评论。 更多信息请参阅“[关于团队讨论](/organizations/collaborating-with-your-team/about-team-discussions/)”。 此 API 仅适用于团队组织中经过身份验证的成员。
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/rest-reference/teams/discussions.md b/translations/zh-CN/data/reusables/rest-reference/teams/discussions.md
new file mode 100644
index 000000000000..2de153f1e6bc
--- /dev/null
+++ b/translations/zh-CN/data/reusables/rest-reference/teams/discussions.md
@@ -0,0 +1,3 @@
+## Discussions
+
+团队讨论 API 允许您获取、创建、编辑和删除团队页面上的讨论帖子。 您可以使用团队讨论进行不特定于存储库或项目的对话。 团队[组织](/rest/reference/orgs)的任何成员都可以创建和阅读公共讨论帖子。 更多信息请参阅“[关于团队讨论](//organizations/collaborating-with-your-team/about-team-discussions/)”。 要详细了解对讨论帖子的评论，请参阅[团队讨论评论 API](/rest/reference/teams#discussion-comments)。 此 API 仅适用于团队组织中经过身份验证的成员。
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/rest-reference/teams/external-groups.md b/translations/zh-CN/data/reusables/rest-reference/teams/external-groups.md
new file mode 100644
index 000000000000..f50adc151826
--- /dev/null
+++ b/translations/zh-CN/data/reusables/rest-reference/teams/external-groups.md
@@ -0,0 +1,16 @@
+## 外部组
+
+外部组 API 允许您查看可用于组织的外部身份提供程序组，并管理组织中外部组和团队之间的连接。
+
+要使用此 API，经过身份验证的用户必须是团队维护员或与团队关联的组织的所有者。
+
+{% ifversion ghec %}
+{% note %}
+
+**注意：**
+
+- 外部组 API 仅适用于属于使用 {% data variables.product.prodname_emus %} 的企业中的组织。 更多信息请参阅“[关于企业管理用户](/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)”。
+- 如果您的组织使用团队同步，则可以使用团队同步 API。 更多信息请参阅“[团队同步 API](#team-synchronization)”。
+
+{% endnote %}
+{% endif %}
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/rest-reference/teams/members.md b/translations/zh-CN/data/reusables/rest-reference/teams/members.md
new file mode 100644
index 000000000000..8faf0a4efd70
--- /dev/null
+++ b/translations/zh-CN/data/reusables/rest-reference/teams/members.md
@@ -0,0 +1,12 @@
+## 成员
+
+此 API 仅适用于团队组织中经过身份验证的成员。 OAuth 访问令牌需要 `read:org` [scope](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/)。
+
+{% ifversion fpt or ghes or ghec %}
+{% note %}
+
+**注：**当您为具有组织身份提供程序 (IdP) 的团队设置了团队同步时，如果尝试使用 API 更改团队的成员身份，则会看到错误。 如果您有权访问 IdP 中的组成员身份，可以通过身份提供程序管理 GitHub 团队成员身份，该提供程序会自动添加和删除组织的成员。 更多信息请参阅“在身份提供程序与 GitHub 之间同步团队”。
+
+{% endnote %}
+
+{% endif %}
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/rest-reference/teams/team-sync.md b/translations/zh-CN/data/reusables/rest-reference/teams/team-sync.md
new file mode 100644
index 000000000000..4a656a194d25
--- /dev/null
+++ b/translations/zh-CN/data/reusables/rest-reference/teams/team-sync.md
@@ -0,0 +1,11 @@
+## 团队同步
+
+团队同步 API 允许您管理 {% data variables.product.product_name %} 团队与外部身份提供程序 (IdP) 组之间的连接。 要使用此 API，经过身份验证的用户必须是团队维护员或与团队关联的组织的所有者。 用于身份验证的令牌还需要获得授权才能与 IdP (SSO) 提供程序一起使用。 更多信息请参阅“授权个人访问令牌用于 SAML 单点登录组织”。
+
+您可以通过 IdP 通过团队同步管理 GitHub 团队成员。 必须启用团队同步才能使用团队同步 API。 更多信息请参阅“在身份提供程序与 GitHub 之间同步团队”。
+
+{% note %}
+
+**注意：** 团队同步 API 不能与 {% data variables.product.prodname_emus %} 一起使用。 要了解有关管理 {% data variables.product.prodname_emu_org %} 的更多信息，请参阅“[外部组 API](/enterprise-cloud@latest/rest/reference/teams#external-groups)”。
+
+{% endnote %}
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/rest-reference/teams/teams.md b/translations/zh-CN/data/reusables/rest-reference/teams/teams.md
new file mode 100644
index 000000000000..1afcead51aa8
--- /dev/null
+++ b/translations/zh-CN/data/reusables/rest-reference/teams/teams.md
@@ -0,0 +1 @@
+此 API 仅适用于团队[组织](/rest/reference/orgs)中经过身份验证的成员。 OAuth 访问令牌需要 `read:org` [scope](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/)。 {% data variables.product.prodname_dotcom %} 从团队 `name` 生成团队的 `slug`。
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/rest-reference/users/blocking.md b/translations/zh-CN/data/reusables/rest-reference/users/blocking.md
new file mode 100644
index 000000000000..fb0a4d7ca66f
--- /dev/null
+++ b/translations/zh-CN/data/reusables/rest-reference/users/blocking.md
@@ -0,0 +1 @@
+## 阻止用户
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/rest-reference/users/emails.md b/translations/zh-CN/data/reusables/rest-reference/users/emails.md
new file mode 100644
index 000000000000..3b47fc873e53
--- /dev/null
+++ b/translations/zh-CN/data/reusables/rest-reference/users/emails.md
@@ -0,0 +1,3 @@
+## Emails
+
+通过 API 管理电子邮件地址要求您通过基本身份验证进行验证，或者使用端点的正确范围通过 OAuth 进行身份验证。
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/rest-reference/users/followers.md b/translations/zh-CN/data/reusables/rest-reference/users/followers.md
new file mode 100644
index 000000000000..e8ba3b53711c
--- /dev/null
+++ b/translations/zh-CN/data/reusables/rest-reference/users/followers.md
@@ -0,0 +1 @@
+## 关注者
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/rest-reference/users/gpg-keys.md b/translations/zh-CN/data/reusables/rest-reference/users/gpg-keys.md
new file mode 100644
index 000000000000..dea7f7256001
--- /dev/null
+++ b/translations/zh-CN/data/reusables/rest-reference/users/gpg-keys.md
@@ -0,0 +1,3 @@
+## GPG keys
+
+在 `public_key` 响应字段中返回的数据不是 GPG 格式化的密钥。 当用户上传 GPG 密钥时，将对密钥进行剖析，然后提取并存储加密公钥。 此加密密钥是本页面上的 API 所返回的密钥。 此密钥不适合直接用于 GPG 等程序。
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/rest-reference/users/keys.md b/translations/zh-CN/data/reusables/rest-reference/users/keys.md
new file mode 100644
index 000000000000..4a328fb1b085
--- /dev/null
+++ b/translations/zh-CN/data/reusables/rest-reference/users/keys.md
@@ -0,0 +1 @@
+## Git SSH 密钥
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/rest-reference/users/users.md b/translations/zh-CN/data/reusables/rest-reference/users/users.md
new file mode 100644
index 000000000000..de6fca23a71c
--- /dev/null
+++ b/translations/zh-CN/data/reusables/rest-reference/users/users.md
@@ -0,0 +1 @@
+用户 API 上的许多资源提供了快捷方式，可用于获取有关当前经过身份验证的用户的信息。 如果请求 URL 不含 `{username}` 参数，则响应将是登录用户的响应（您必须随请求传递[身份验证信息](/rest/overview/resources-in-the-rest-api#authentication)）。{% ifversion fpt or ghes or ghec %} 在通过基本身份验证或作用域为 `user` 的 OAuth 进行身份验证时，将包含其他私有信息，例如用户是否启用双重身份验证。{% endif %}
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/rest-reference/webhooks/repo-config.md b/translations/zh-CN/data/reusables/rest-reference/webhooks/repo-config.md
new file mode 100644
index 000000000000..055bbb9fa1fe
--- /dev/null
+++ b/translations/zh-CN/data/reusables/rest-reference/webhooks/repo-config.md
@@ -0,0 +1 @@
+## Repository webhook configuration
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/rest-reference/webhooks/repo-deliveries.md b/translations/zh-CN/data/reusables/rest-reference/webhooks/repo-deliveries.md
new file mode 100644
index 000000000000..bd0366dee6a4
--- /dev/null
+++ b/translations/zh-CN/data/reusables/rest-reference/webhooks/repo-deliveries.md
@@ -0,0 +1 @@
+## Repository webhook deliveries
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/rest-reference/webhooks/repos.md b/translations/zh-CN/data/reusables/rest-reference/webhooks/repos.md
new file mode 100644
index 000000000000..719e1894eadd
--- /dev/null
+++ b/translations/zh-CN/data/reusables/rest-reference/webhooks/repos.md
@@ -0,0 +1 @@
+## 仓库 web 挂钩
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/rest-reference/webhooks/webhooks.md b/translations/zh-CN/data/reusables/rest-reference/webhooks/webhooks.md
new file mode 100644
index 000000000000..01585aedd781
--- /dev/null
+++ b/translations/zh-CN/data/reusables/rest-reference/webhooks/webhooks.md
@@ -0,0 +1,58 @@
+仓库 web 挂钩允许您在仓库内发生特定事件时接收 HTTP `POST` 有效负载。 {% data reusables.webhooks.webhooks-rest-api-links %}
+
+如果您要设置一个 web 挂钩来接收来自组织所有仓库的事件，请参阅关于[组织 web 挂钩](/rest/reference/orgs#webhooks)的 API 文档。
+
+除了 REST API 之外， {% data variables.product.prodname_dotcom %} 还可以作为仓库的 [PubSubHubbub](#pubsubhubbub) 枢纽。
+
+## 接收 web 挂钩
+
+为了让 {% data variables.product.product_name %} 发送 web 挂钩有效负载，您的服务器需要能够从 Internet 访问。 我们还强烈建议使用 SSL，以便我们可以通过 HTTPS 发送加密的有效负载。
+
+### Web 挂钩标头
+
+{% data variables.product.product_name %} 发送时将附带几个 HTTP 标头，以区分事件类型和有效负载标识符。 更多信息请参阅 [web 挂钩标头](/developers/webhooks-and-events/webhook-events-and-payloads#delivery-headers)。
+
+## PubSubHubbub
+
+GitHub 还可以作为所有仓库的 [PubSubHubbabub](https://github.com/pubsubhubbub/PubSubHubbub) 枢纽。 PSHB 是一个简单的发布/订阅协议，允许服务器注册在主题更新时接收更新。 这些更新随 HTTP POST 请求一起发送到回调 URL。 GitHub 仓库推送的主题 URL 采用以下格式：
+
+`https://github.com/{owner}/{repo}/events/{event}`
+
+事件可以是任何可用的 web 挂钩事件。 更多信息请参阅“[web 挂钩事件和有效负载](/developers/webhooks-and-events/webhook-events-and-payloads)”。
+
+### 响应格式
+
+默认格式为[现有接收后挂钩应具有的格式](/post-receive-hooks/)：作为 POST 中的 `payload` 参数发送的 JSON 正文。 您还可以指定接收带有 `Accept` 标头或 `.json` 扩展名的原始 JSON 正文。
+
+ Accept: application/json
+ https://github.com/{owner}/{repo}/events/push.json
+
+### 回调 URL
+
+回调 URL 可以使用 `http://` 协议。
+
+ # Send updates to postbin.org
+ http://postbin.org/123
+
+### 订阅
+
+GitHub PubSubHubbub 端点为：`{% data variables.product.api_url_code %}/hub`。 使用 cURL 的成功请求如下所示：
+
+``` shell
+curl -u "user" -i \
+ {% data variables.product.api_url_pre %}/hub \
+ -F "hub.mode=subscribe" \
+ -F "hub.topic=https://github.com/{owner}/{repo}/events/push" \
+ -F "hub.callback=http://postbin.org/123"
+```
+
+PubSubHubbub 请求可以多次发送。 如果挂钩已经存在，它将根据请求进行修改。
+
+#### 参数
+
+| 名称 | 类型 | 描述 |
+| -------------- | ----- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `hub.mode` | `字符串` | **必填**。 值为 `subscribe` 或 `unsubscribe`。 |
+| `hub.topic` | `字符串` | **必填**。 要订阅的 GitHub 仓库的 URI。 路径格式必须为 `/{owner}/{repo}/events/{event}`。 |
+| `hub.callback` | `字符串` | 要接收主题更新的 URI。 |
+| `hub.secret` | `字符串` | 用于生成传出正文内容的哈希签名的共享密钥。 您可以通过比较原始请求正文与 {% ifversion fpt or ghes > 2.22 or ghec %}`X-Hub-Signature` 或 `X-Hub-Signature-256` 标头{% elsif ghes < 3.0 %}`X-Hub-Signature` 标头{% elsif ghae %}`X-Hub-Signature-256` 标头{% endif %} 的内容来验证来自 GitHub 的推送。 您可以查看 [PubSubHubbub 文档](https://pubsubhubbub.github.io/PubSubHubbub/pubsubhubbub-core-0.4.html#authednotify)了解详情。 |
\ No newline at end of file
diff --git a/translations/zh-CN/data/ui.yml b/translations/zh-CN/data/ui.yml
index 4f502e6456b2..65426b33a929 100644
--- a/translations/zh-CN/data/ui.yml
+++ b/translations/zh-CN/data/ui.yml
@@ -1,4 +1,6 @@
---
+meta:
+ default_description: Get started, troubleshoot, and make the most of GitHub. Documentation for new users, developers, administrators, and all of GitHub's products.
header:
github_docs: GitHub Docs
contact: 联系我们
@@ -92,6 +94,7 @@ products:
deprecation_notice: 废弃通知
rest:
reference:
+ notes: 注：
parameters: 参数
response: 响应
code_sample: 代码示例
@@ -101,6 +104,7 @@ products:
see_preview_notice: 查看预览通知
see_preview_notices: 查看预览通知
preview_header_is_required: 此标头必填
+ works_with_github_apps: Works with GitHub Apps
footer:
all_rights_reserved: 保留所有权利
terms: 条款